[Fixed in 0.2.2] 0.2.0 Comware v.5: ssh_backup_download_failed

Beta release announcements and discussion around them
Post Reply
Itcoop
Posts: 32
Joined: Tue Aug 02, 2016 12:39 am

Mon Aug 29, 2016 9:13 pm

Comware syslogs every valid command. The last valid command I see in syslog after successful Unimus login is: "Command is display version" followed by "logged out because the SSH client closed the connection."

What method of configuration backup does Unimus use? A scrape of 'display current-configuration', an scp/sftp download? I hope it's a scrape. If not, I'll have to configure scp or sftp on each device.

Another interesting syslog:
AccessType=login-UsernName=unimus-ssh-test; Authentication is failed. User not found.
User 'unimus-ssh-test' is trying to login from x.x.x.x

This is interesting because user 'unimus-ssh-test' is not in my valid credentials list...
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Mon Aug 29, 2016 9:23 pm

1) Its a scrape of 'display current-configuration', or appropriate versions of that for other vendors.
I found a bug in the Comware backup driver, fixed for 0.2.2.

2) 'unimus-ssh-test' user is an internal user to test SSH connection during discovery.
This is done before attempts to log in with configured credentials are tried, to test if SSH connection is establishable at all (this is here to weed out 'unsupported SSH algorithm' and similar SSH issues)
Itcoop
Posts: 32
Joined: Tue Aug 02, 2016 12:39 am

Wed Aug 31, 2016 2:23 pm

That explains it. Thanks for the quick fix. My stacked Comware 5.20.99 5501P25 devices are being backed up successfully.
Itcoop
Posts: 32
Joined: Tue Aug 02, 2016 12:39 am

Wed Aug 31, 2016 3:37 pm

My backups are going well; however, on the Devices screen some of the Comware devices note the model as "with":
unimus1.png
unimus1.png (9.88 KiB) Viewed 8464 times
Discovery is probably enumerating a word of the 'display version':

<switch>dis version
HPE Comware Platform Software
Comware Software, Version 5.20.99, Release 5501P25
Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP
HP 5500-24G-PoE+-4SFP HI Switch with 2 Interface Slots uptime is 3 weeks, 6 days, 18 hours, 41 minutes

HP 5500-24G-PoE+-4SFP HI Switch with 2 Interface Slots with 2 Processors
1024M bytes SDRAM
4096K bytes Nor Flash Memory

512M bytes Nand Flash Memory
Hardware Version is REV.A
CPLD Version is 003
Bootrom Version is 215
[SubSlot 0] 24GE+4SFP+2SFP PLUS+POE PLUS Hardware Version is REV.A
[SubSlot 1] 2 SFP+ Hardware Version is REV.A

Because many of my deployments are stacked using IRF, this makes the configs per "slot" identical *unless* the stack fails. It may be beneficial to enumerate using 'display device manuinfo'. This will give Unimus the entire picture of the configs and whether this device is stacked with more than one device:

<switch>dis dev manu
Slot 1:
DEVICE_NAME : 5500-24G-PoE+-4SFP JG541A
DEVICE_SERIAL_NUMBER : xxxxxxxxxxxx
MAC_ADDRESS : xxxx-xxxx-xxxx
MANUFACTURING_DATE : 2015-05-30
VENDOR_NAME : HP
Subslot 1:
DEVICE_NAME : HP A5500/A5120 2-port 10-GbE SFP+ Module JD368B
DEVICE_SERIAL_NUMBER : xxxxxxxxxx
MANUFACTURING_DATE : 2015-05-17
VENDOR_NAME : HP


Power 1:
DEVICE_NAME : HP X362 1110W AC PoE Power Supply JG545A
DEVICE_SERIAL_NUMBER : xxxxxxxxx
MANUFACTURING_DATE : 2015-06-24
VENDOR_NAME : HP

Power 2:

This Power does not exist!

Slot 2:
DEVICE_NAME : 5500-24G-PoE+-4SFP JG541A
DEVICE_SERIAL_NUMBER : xxxxxxxxx
MAC_ADDRESS : xxxx-xxxx-xxxx
MANUFACTURING_DATE : 2015-06-19
VENDOR_NAME : HP
Subslot 1:
DEVICE_NAME : HP A5500/A5120 2-port 10-GbE SFP+ Module JD368B
DEVICE_SERIAL_NUMBER : xxxxxxxxxx
MANUFACTURING_DATE : 2015-05-16
VENDOR_NAME : HP


Power 1:
DEVICE_NAME : HP X362 1110W AC PoE Power Supply JG545A
DEVICE_SERIAL_NUMBER : xxxxxxxxxx
MANUFACTURING_DATE : 2015-06-24
VENDOR_NAME : HP

Power 2:

This Power does not exist!
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Thu Sep 01, 2016 9:53 am

Should also be fixed in 0.2.2.
Post Reply