1832649 Members
3103 Online
110043 Solutions
New Discussion

Backup switches config FAILED

 
Daniel96
Advisor

Backup switches config FAILED

Hi,

After upgrading to iMC PLAT 7.3 (E0705P10) 

the backups failed with an error: SSH authenticated failure

I tested in all the switches the SSH credentials and the test working. Also the SNMP credentials correct.

The transfer protocol is SFTP.

this part of the log:

ActionName = backup_running_config
InputParam = TFTPFile=C:/Program Files/iMC/server/tmp/running_3332637252.cfg?_?TFTPServer=10.1.0.29?_?UnitList=?_?VpnName=
OutputParam =
CmdResp =
ErrorMessage =
ActionResult = 19

2021-05-23 10:11:54.411 [WARNING (32)] [THREAD(11140)] [CComponentAdapter::checkAccessTypeMatchTransferProtocol()] transfer protocol does not match access type,iTransferProtocol=3,iAccessType=3
2021-05-23 10:11:54.411 [WARNING (32)] [THREAD(11140)] [CComponentAdapter::isDevSupportServiceAction()] transfer protocol does not match access type,ServiceName = ConfigBackup,commandName=Custom,iTransferProtocol=3,iAccessType=3
2021-05-23 10:11:54.441 [WARNING (2023)] [THREAD(11140)] [CScriptTool::getDevAdapterNameFromDB()] reader no data, sql: select vendor_name,adapter_name,error_code from tbl_dev_adapter where component_name = 'Custom' and dev_id = 78 and adapter_type = 0
2021-05-23 10:11:54.452 [INFO (0)] [THREAD(11140)] [CComponentAdapter::discoverDeviceAdapter()] H3C oem HP device,try HP vendor adapter again.
2021-05-23 10:11:54.452 [ERROR (18)] [THREAD(11140)] [CComponentAdapter::getDevAdapterName()] fail to call discoverDeviceAdapter()
2021-05-23 10:11:54.452 [ERROR (18)] [THREAD(11140)] [CComponentAdapter::isDevSupportServiceAction()] fail to call getDevAdapterName().DevID=78,ServiceName = ConfigBackup
2021-05-23 10:11:54.457 [INFO (0)] [THREAD(11124)] [isH3CXrnDevice()] Device: 10.1.0.85 get vb list failed, iRet:-102
2021-05-23 10:11:54.457 [INFO (0)] [THREAD(11124)] [CThirdPartCfgfileMgr::backupRunning()] Begin to backup running cfgfile ...
2021-05-23 10:11:54.457 [WARNING (32)] [THREAD(11140)] [CComponentAdapter::checkAccessTypeMatchTransferProtocol()] transfer protocol does not match access type,iTransferProtocol=3,iAccessType=3
2021-05-23 10:11:54.457 [WARNING (32)] [THREAD(11140)] [CComponentAdapter::isDevSupportServiceAction()] transfer protocol does not match access type,ServiceName = ConfigBackup,commandName=ICC,iTransferProtocol=3,iAccessType=3
2021-05-23 10:11:54.461 [INFO (0)] [THREAD(11124)] [CScriptProcessor::exec()] Begin to execute, data: ServiceName = ConfigBackup
ActionName = backup_running_config
InputParam = TFTPFile=C:/Program Files/iMC/server/tmp/running_3332637254.cfg?_?TFTPServer=10.1.0.29?_?UnitList=?_?VpnName=
OutputParam =
CmdResp =
ErrorMessage =
ActionResult = 19

2021-05-23 10:11:54.466 [INFO (0)] [THREAD(11112)] [isH3CXrnDevice()] Device: 10.1.0.49 get vb list failed, iRet:-102
2021-05-23 10:11:54.466 [INFO (0)] [THREAD(11112)] [CThirdPartCfgfileMgr::backupRunning()] Begin to backup running cfgfile ...
2021-05-23 10:11:54.468 [WARNING (32)] [THREAD(11124)] [CComponentAdapter::checkAccessTypeMatchTransferProtocol()] transfer protocol does not match access type,iTransferProtocol=3,iAccessType=3
2021-05-23 10:11:54.468 [WARNING (32)] [THREAD(11124)] [CComponentAdapter::isDevSupportServiceAction()] transfer protocol does not match access type,ServiceName = ConfigBackup,commandName=Custom,iTransferProtocol=3,iAccessType=3
2021-05-23 10:11:54.469 [INFO (0)] [THREAD(11140)] [CComponentAdapter::isDevSupportServiceAction] dev_id: 78, adapter_name: H3CCommon
2021-05-23 10:11:54.469 [INFO (0)] [THREAD(11140)] [CScriptProcessor::exec()] Begin to execute by cli.
2021-05-23 10:11:54.471 [INFO (0)] [THREAD(11112)] [CScriptProcessor::exec()] Begin to execute, data: ServiceName = ConfigBackup

17 REPLIES 17
jguse
HPE Pro

Re: Backup switches config FAILED

Hello,

The SSH Test works with a different SSH Client than the Config Backup (which uses putty/plink.exe), so you may see one working but not the other. The reason SSH authentication failed when attempting the backup is possibly due to no matching SSH encryption or MAC algorithms on either side, which I've seen a few times recently with devices that only support SHA2 MACs (like hmac-sha2-256).

Could you please try this workaround to enable Putty Release 0.7 in iMC 7.3 E0705P10:

  1. Create a file putty07 with no extension in <IMC>/server/conf.
  2. Restart IMC.
  3. Test the backup again.

The putty 0.7 supports SHA2 MACs for SSH and should work if this was the reason for the authentication failure.

PS. The errors shown in the logs you shared are not really relevant. You may want to look further, as the logs generally also show you the CLI output up to the point of failure, soon after 'Begin to run by cli', and that is key to understanding what went wrong.

Best regards,
Justin

Working @ HPE
Accept or Kudo
Daniel96
Advisor

Re: Backup switches config FAILED

Hi,

First of all thanks for your response.

I have a question about what you mean to create putty file? can you give example?

thanks

 

Daniel96
Advisor

Re: Backup switches config FAILED

I added additional text from what you asked.

2021-05-24 20:00:03.692 [INFO (0)] [THREAD(11104)] [isH3CXrnDevice()] Device: 10.1.0.85 get vb list failed, iRet:-102
2021-05-24 20:00:03.692 [INFO (0)] [THREAD(11104)] [CThirdPartCfgfileMgr::backupRunning()] Begin to backup running cfgfile ...
2021-05-24 20:00:03.693 [INFO (0)] [THREAD(11108)] [CComponentAdapter::isDevSupportServiceAction] dev_id: 78, adapter_name: H3CCommon
2021-05-24 20:00:03.693 [INFO (0)] [THREAD(11108)] [CScriptProcessor::exec()] Begin to execute by cli.
2021-05-24 20:00:03.694 [WARNING (32)] [THREAD(11120)] [CComponentAdapter::checkAccessTypeMatchTransferProtocol()] transfer protocol does not match access type,iTransferProtocol=3,iAccessType=3
2021-05-24 20:00:03.694 [WARNING (32)] [THREAD(11120)] [CComponentAdapter::isDevSupportServiceAction()] transfer protocol does not match access type,ServiceName = ConfigBackup,commandName=Custom,iTransferProtocol=3,iAccessType=3
2021-05-24 20:00:03.695 [INFO (0)] [THREAD(11132)] [isH3CXrnDevice()] Device: 10.1.0.90 get vb list failed, iRet:-102
2021-05-24 20:00:03.695 [INFO (0)] [THREAD(11132)] [CThirdPartCfgfileMgr::backupRunning()] Begin to backup running cfgfile ...
2021-05-24 20:00:03.698 [INFO (0)] [THREAD(11104)] [CScriptProcessor::exec()] Begin to execute, data: ServiceName = ConfigBackup
ActionName = backup_running_config
InputParam = TFTPFile=C:/Program Files/iMC/server/tmp/running_3333854146.cfg?_?TFTPServer=10.1.0.29?_?UnitList=?_?VpnName=
OutputParam =
CmdResp =
ErrorMessage =
ActionResult = 19

2021-05-24 20:00:03.699 [INFO (0)] [THREAD(11116)] [CComponentAdapter::discoverDeviceAdapter()] H3C oem HP device,try HP vendor adapter again.
2021-05-24 20:00:03.699 [ERROR (18)] [THREAD(11116)] [CComponentAdapter::getDevAdapterName()] fail to call discoverDeviceAdapter()
2021-05-24 20:00:03.699 [ERROR (18)] [THREAD(11116)] [CComponentAdapter::isDevSupportServiceAction()] fail to call getDevAdapterName().DevID=111,ServiceName = ConfigBackup
2021-05-24 20:00:03.702 [INFO (0)] [THREAD(11132)] [CScriptProcessor::exec()] Begin to execute, data: ServiceName = ConfigBackup
ActionName = backup_running_config
InputParam = TFTPFile=C:/Program Files/iMC/server/tmp/running_3333854147.cfg?_?TFTPServer=10.1.0.29?_?UnitList=?_?VpnName=
OutputParam =
CmdResp =
ErrorMessage =
ActionResult = 19

jguse
HPE Pro

Re: Backup switches config FAILED

Hello,

I mean to create a blank file with no extension called putty07 in that directory, which will tell iMC to use this version of putty for config backups/restores etc. Please give that a try.

Best regards,
Justin

Working @ HPE
Accept or Kudo
Daniel96
Advisor

Re: Backup switches config FAILED

You mean like that right?

IMC putty07.PNG

jguse
HPE Pro

Re: Backup switches config FAILED

That looks correct.

Best regards,
Justin

Working @ HPE
Accept or Kudo
Daniel96
Advisor

Re: Backup switches config FAILED

It didn't help. still got on all switches SSH authentication failed.

which more info you need?

 

jguse
HPE Pro

Re: Backup switches config FAILED

Hello,

in that case, please check if you can find entries like the following in the imccfgbakdm log:

2021-05-06 10:40:01.820 [ERROR (13)] [THREAD(13744)] [CScriptProcessor::exec()] Failed to run by cli method.
2021-05-06 10:40:01.820 [INFO (13)] [THREAD(13744)] [CScriptProcessor::exec()] Finished to run , result:

Beneath that, you should find some text that includes the CLI log from when iMC tried to connect to the device CLI with SSH. Can you share that please?

Best regards,
Justin

Working @ HPE
Accept or Kudo
Daniel96
Advisor

Re: Backup switches config FAILED

Where i found this log?

Daniel96
Advisor

Re: Backup switches config FAILED

It's in the same log file?

jguse
HPE Pro

Re: Backup switches config FAILED

Hello,

It's under iMC\server\conf\log\imccfgbakdm<date>.txt, where you were already posting logs from.

Best regards,
Justin

Working @ HPE
Accept or Kudo
Daniel96
Advisor

Re: Backup switches config FAILED

I need to check with our sys Admin if i can share this part of the log

Daniel96
Advisor

Re: Backup switches config FAILED

Hi,

I added the log you asked for. 
i just change the tftp server ip to : x.x.x.x

2021-05-25 12:29:11.464 [ERROR (7)] [THREAD(8760)] [CScriptProcessor::exec()] Failed to execute by cli method.
2021-05-25 12:29:11.464 [INFO (7)] [THREAD(8760)] [CScriptProcessor::exec()] Finished to execute, result:
ServiceName = ConfigBackup
ActionName = backup_running_config
InputParam = DevName=B58-Hinuch-Mahar2?_?TFTPFile=C:/Program Files/iMC/server/tmp/running_3334447485.cfg?_?TFTPServer=x.x.x.x?_?UnitList=?_?VpnName=
OutputParam = ERROR_MESSAGE=FATAL.
CmdResp = Passphrase for key "rsa-key-20180111":
******************************************************************************
* Copyright (c) 2010-2015 Hewlett-Packard Development Company, L.P. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<B58-Hinuch-Mahar2>delete /unreserved iccrunning.cfg
The contents cannot be restored!!! Delete flash:/iccrunning.cfg?[Y/N]:y
Deleting a file permanently will take a long time. Please wait...
%Delete file flash:/iccrunning.cfg...Done.
<B58-Hinuch-Mahar2>delete /unreserved iccrunning.zip
% Execution failure
<B58-Hinuch-Mahar2>save iccrunning.cfg
The current configuration will be saved to flash:/iccrunning.cfg. Continue? [Y/N]:y
Now saving current configuration to the device.
Saving configuration flash:/iccrunning.cfg. Please wait...
.
Configuration is saved to flash successfully.
<B58-Hinuch-Mahar2>Passphrase for key "rsa-key-20180111":
Using username "User".
Fatal: Server sent disconnect message
type 2 (protocol error):
"The connection is closed by SSH Server."

ErrorMessage = FATAL.
ActionResult = 7

2021-05-25 12:29:11.465 [ERROR (7)] [THREAD(8760)] [CThirdPartCfgfileMgr::__backup()] Failed to call CScriptProcessor::exec().step_detail: Passphrase for key "rsa-key-20180111":
******************************************************************************
* Copyright (c) 2010-2015 Hewlett-Packard Development Company, L.P. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<B58-Hinuch-Mahar2>delete /unreserved iccrunning.cfg
The contents cannot be restored!!! Delete flash:/iccrunning.cfg?[Y/N]:y
Deleting a file permanently will take a long time. Please wait...
%Delete file flash:/iccrunning.cfg...Done.
<B58-Hinuch-Mahar2>delete /unreserved iccrunning.zip
% Execution failure
<B58-Hinuch-Mahar2>save iccrunning.cfg
The current configuration will be saved to flash:/iccrunning.cfg. Continue? [Y/N]:y
Now saving current configuration to the device.
Saving configuration flash:/iccrunning.cfg. Please wait...
.
Configuration is saved to flash successfully.
<B58-Hinuch-Mahar2>Passphrase for key "rsa-key-20180111":
Using username "User".
Fatal: Server sent disconnect message
type 2 (protocol error):
"The connection is closed by SSH Server."

Daniel96
Advisor

Re: Backup switches config FAILED

@jguse 

I added the log you been asked for.

 

jguse
HPE Pro

Re: Backup switches config FAILED

Thanks for the logs. iMC is failing backup due to the device prompting for Passphrase for key "rsa-key-20180111": which it seems iMC cannot respond to, and that results in the disconnect seen after:

Fatal: Server sent disconnect message
type 2 (protocol error):
"The connection is closed by SSH Server."

Since you are using a private key with passphrase here, have you configured your SSH Template for the device (in iMC's SSH Settings) with an option that includes Private Key and its passphrase as well?

Alternatively you could also test re-creating the SSH key without a passphrase, and then see if you still get the same error in the logs after a backup.

Best regards,
Justin

Working @ HPE
Accept or Kudo
Daniel96
Advisor

Re: Backup switches config FAILED

Thanks for the answer.

I entered one of the switches and open the log buffer. I adding the log from the time of backup.

I switch of course the user to "User" and the imc IP to x.x.x.x

I run "display log buffer reverse"

%Jun 2 12:33:03:800 2021 B51_LIB_IRF SSH/6/SSH_CONNECTION_CLOSE: STEL user "User" (IP: x.x.x.x) logged out because the SSH client closed the connection.
%Jun 2 12:33:03:791 2021 B51_LIB_IRF SHELL/5/SHELL_LOGOUT: "User" logged out from x.x.x.x.
%Jun 2 12:33:03:589 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is dis time-range all
%Jun 2 12:32:57:278 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is dis current-configuration
%Jun 2 12:32:57:114 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is display acl all
%Jun 2 12:32:45:889 2021 B51_LIB_IRF SHELL/5/SHELL_LOGIN: "User" logged in from x.x.x.x.
%Jun 2 12:32:45:783 2021 B51_LIB_IRF SSH/6/SSH_LOGIN: STEL user "User" (IP: x.x.x.x) logged in successfully.
%Jun 2 12:22:39:031 2021 B51_LIB_IRF LLDP/6/LLDP_CREATE_NEIGHBOR: New neighbor created on Port GigabitEthernet1/0/41 (IfIndex 9437224), Chassis ID is 001a-a0e1-1e3d, Port ID is 001a-a0e1-1e3d.
%Jun 2 12:22:34:205 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: Instance 0's port GigabitEthernet1/0/41 has been set to forwarding state.
%Jun 2 12:22:34:205 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/41 link status is UP.
%Jun 2 12:22:31:458 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/41 link status is DOWN.
%Jun 2 12:22:23:311 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: Instance 0's port GigabitEthernet1/0/41 has been set to forwarding state.
%Jun 2 12:22:23:311 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/41 link status is UP.
%Jun 2 12:22:20:741 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/41 link status is DOWN.
%Jun 2 12:22:19:550 2021 B51_LIB_IRF LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=4; New neighbor created on Port GigabitEthernet4/0/21 (IfIndex 34603028), Chassis ID is 001a-a0e1-27e8, Port ID is 001a-a0e1-27e8.
%Jun 2 12:22:15:956 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=4; Instance 0's port GigabitEthernet4/0/21 has been set to forwarding state.
%Jun 2 12:22:15:889 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet4/0/21 link status is UP.
%Jun 2 12:22:13:386 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet4/0/21 link status is DOWN.
%Jun 2 12:22:11:276 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: Instance 0's port GigabitEthernet1/0/41 has been set to forwarding state.
%Jun 2 12:22:11:275 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/41 link status is UP.
%Jun 2 12:22:08:452 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/41 link status is DOWN.
%Jun 2 12:22:04:461 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=4; Instance 0's port GigabitEthernet4/0/21 has been set to forwarding state.
%Jun 2 12:22:04:424 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet4/0/21 link status is UP.
%Jun 2 12:22:01:717 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet4/0/21 link status is DOWN.
%Jun 2 12:21:52:463 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=4; Instance 0's port GigabitEthernet4/0/21 has been set to forwarding state.
%Jun 2 12:21:52:377 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet4/0/21 link status is UP.
%Jun 2 12:21:49:479 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet4/0/21 link status is DOWN.
%Jun 2 12:08:20:573 2021 B51_LIB_IRF LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=3; New neighbor created on Port GigabitEthernet3/0/8 (IfIndex 26214407), Chassis ID is f04d-a20e-7823, Port ID is f04d-a20e-7823.
%Jun 2 12:08:20:443 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=3; Instance 0's port GigabitEthernet3/0/8 has been set to forwarding state.
%Jun 2 12:08:20:442 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet3/0/8 link status is UP.
%Jun 2 12:08:17:749 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet3/0/8 link status is DOWN.
%Jun 2 12:08:10:106 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=3; Instance 0's port GigabitEthernet3/0/8 has been set to forwarding state.
%Jun 2 12:08:10:055 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet3/0/8 link status is UP.
%Jun 2 12:06:15:228 2021 B51_LIB_IRF LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; New neighbor created on Port GigabitEthernet2/0/42 (IfIndex 17825833), Chassis ID is f04d-a20e-b737, Port ID is f04d-a20e-b737.
%Jun 2 12:06:14:060 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=2; Instance 0's port GigabitEthernet2/0/42 has been set to forwarding state.
%Jun 2 12:06:13:992 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/42 link status is UP.
%Jun 2 12:06:11:353 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/42 link status is DOWN.
%Jun 2 12:06:04:190 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=2; Instance 0's port GigabitEthernet2/0/42 has been set to forwarding state.
%Jun 2 12:06:04:081 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/42 link status is UP.
%Jun 2 11:33:14:948 2021 B51_LIB_IRF LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; New neighbor created on Port GigabitEthernet2/0/32 (IfIndex 17825823), Chassis ID is 001e-4fa9-69df, Port ID is 001e-4fa9-69df.
%Jun 2 11:33:12:353 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=2; Instance 0's port GigabitEthernet2/0/32 has been set to forwarding state.
%Jun 2 11:33:12:310 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/32 link status is UP.
%Jun 2 11:33:09:934 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/32 link status is DOWN.
%Jun 2 11:33:02:741 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=2; Instance 0's port GigabitEthernet2/0/32 has been set to forwarding state.
%Jun 2 11:33:02:701 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/32 link status is UP.
%Jun 2 11:33:00:177 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/32 link status is DOWN.
%Jun 2 11:32:53:662 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=2; Instance 0's port GigabitEthernet2/0/32 has been set to forwarding state.
%Jun 2 11:32:53:616 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/32 link status is UP.
%Jun 2 11:32:50:831 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet2/0/32 link status is DOWN.
%Jun 2 11:10:55:759 2021 B51_LIB_IRF LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=3; New neighbor created on Port GigabitEthernet3/0/22 (IfIndex 26214421), Chassis ID is 1866-da3c-6f25, Port ID is 1866-da3c-6f25.
%Jun 2 11:10:55:137 2021 B51_LIB_IRF MSTP/6/MSTP_FORWARDING: -Slot=3; Instance 0's port GigabitEthernet3/0/22 has been set to forwarding state.
%Jun 2 11:10:55:073 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet3/0/22 link status is UP.
%Jun 2 11:10:40:738 2021 B51_LIB_IRF IFNET/3/LINK_UPDOWN: GigabitEthernet3/0/22 link status is DOWN.
%Jun 2 11:00:23:956 2021 B51_LIB_IRF MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port Bridge-Aggregation29 was notified of a topology change.
%Jun 2 11:00:23:543 2021 B51_LIB_IRF MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port Bridge-Aggregation29 was notified of a topology change.
%Jun 2 10:56:13:969 2021 B51_LIB_IRF SSH/6/SSH_LOGOUT: SFTP user "User" (IP: x.x.x.x) logged out.
%Jun 2 10:56:13:254 2021 B51_LIB_IRF SSH/6/SSH_CONNECTION_CLOSE: STEL user "User" (IP: x.x.x.x) logged out because the SSH client closed the connection.
%Jun 2 10:56:13:247 2021 B51_LIB_IRF SHELL/5/SHELL_LOGOUT: "User" logged out from x.x.x.x.
%Jun 2 10:56:13:246 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is quit
%Jun 2 10:56:13:115 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is display startup
%Jun 2 10:56:12:873 2021 B51_LIB_IRF SHELL/5/SHELL_LOGIN: "User" logged in from x.x.x.x.
%Jun 2 10:56:12:759 2021 B51_LIB_IRF SSH/6/SSH_LOGIN: STEL user "User" (IP: x.x.x.x) logged in successfully.
%Jun 2 10:56:09:566 2021 B51_LIB_IRF SSH/6/SSH_LOGOUT: SFTP user "User" (IP: x.x.x.x) logged out.
%Jun 2 10:56:08:865 2021 B51_LIB_IRF SSH/6/SSH_CONNECTION_CLOSE: STEL user "User" (IP: x.x.x.x) logged out because the SSH client closed the connection.
%Jun 2 10:56:08:832 2021 B51_LIB_IRF SHELL/5/SHELL_LOGOUT: "User" logged out from x.x.x.x.
%Jun 2 10:56:08:832 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is quit
%Jun 2 10:56:08:791 2021 B51_LIB_IRF CFM/5/CFM_SAVECONFIG_SUCCESSFULLY: Configuration is saved successfully.
%Jun 2 10:56:08:790 2021 B51_LIB_IRF CFGMAN/5/CFGMAN_CFGCHANGED: -EventIndex=1401-CommandSource=1-ConfigSource=2-ConfigDestination=5; Configuration is changed.
%Jun 2 10:55:23:407 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is save iccrunning.cfg
%Jun 2 10:55:18:343 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is delete /unreserved iccrunning.zip
%Jun 2 10:55:14:129 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is delete /unreserved iccrunning.cfg
%Jun 2 10:55:14:034 2021 B51_LIB_IRF SHELL/5/SHELL_LOGIN: "User" logged in from x.x.x.x.
%Jun 2 10:55:13:925 2021 B51_LIB_IRF SSH/6/SSH_LOGIN: STEL user "User" (IP: x.x.x.x) logged in successfully.
%Jun 2 10:54:35:010 2021 B51_LIB_IRF SSH/6/SSH_LOGOUT: SFTP user "User" (IP: x.x.x.x) logged out.
%Jun 2 10:54:34:123 2021 B51_LIB_IRF SSH/6/SSH_CONNECTION_CLOSE: STEL user "User" (IP: x.x.x.x) logged out because the SSH client closed the connection.
%Jun 2 10:54:34:113 2021 B51_LIB_IRF SHELL/5/SHELL_LOGOUT: "User" logged out from x.x.x.x.
%Jun 2 10:54:34:112 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User=x.x.x.x; Command is quit
%Jun 2 10:54:33:991 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User="User"; Command is display startup
%Jun 2 10:54:33:501 2021 B51_LIB_IRF SHELL/5/SHELL_LOGIN: "User" logged in from x.x.x.x.
%Jun 2 10:54:33:393 2021 B51_LIB_IRF SSH/6/SSH_LOGIN: STEL user "User" (IP: x.x.x.x) logged in successfully.
%Jun 2 10:54:26:241 2021 B51_LIB_IRF SSH/6/SSH_LOGOUT: SFTP user "User" (IP: x.x.x.x) logged out.
%Jun 2 10:54:26:207 2021 B51_LIB_IRF SSH/6/SSH_CONNECTION_CLOSE: STEL user "User" (IP: x.x.x.x) logged out because the SSH client closed the connection.
%Jun 2 10:54:26:194 2021 B51_LIB_IRF SHELL/5/SHELL_LOGOUT: "User" logged out from x.x.x.x.
%Jun 2 10:54:26:193 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User=User; Command is quit
%Jun 2 10:54:25:381 2021 B51_LIB_IRF CFM/5/CFM_SAVECONFIG_SUCCESSFULLY: Configuration is saved successfully.
%Jun 2 10:53:39:655 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User=User; Command is save iccrunning.cfg
%Jun 2 10:53:34:583 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User=User; Command is delete /unreserved iccrunning.zip
%Jun 2 10:53:29:688 2021 B51_LIB_IRF SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=x.x.x.x-User=User; Command is delete /unreserved iccrunning.cfg
%Jun 2 10:53:29:509 2021 B51_LIB_IRF SHELL/5/SHELL_LOGIN: "User" logged in from x.x.x.x.

Daniel96
Advisor

Re: Backup switches config FAILED

I changed the SSH to user and password, and the backup worked successfully.

When I change to " Password + private key" the backup not working. But when I connected to the switch with the private key and password I connecting successfully  , just the backup not working.