cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
18661
Views
15
Helpful
12
Replies

UCS Manager - internal system backup failed [FSM:FAILED]

pwojtachnio
Level 1
Level 1

 

Hello,

 

I have UCS Manager Version 2.2(1c)

 

I set up configuration backup via SCP, and Im getting error.

Destination is accessible from other computer in same VLAN via WinSCP.

 

I need help what exactly is causing that error from UCS Manager, and how to solve this issue.

 

I tried to delete and again add backup  job operation.

 

Severity: Critical 
[FWS:FAILED]: internal system backup 
Type: fsm 
Cause: fsm-failed 
Code: F999723

 

I am waiting for quick replay.

Cheers.

1 Accepted Solution

Accepted Solutions

Looking at the logs you posted there is a mismatch in algorithms betwen scp server and ucs system. Server is accepting aes-ctr and ucs is using aes-cbc ?
Maybe try adding

"Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc"  to /etc/ssh/sshd_conf

View solution in original post

12 Replies 12

Walter Dey
VIP Alumni
VIP Alumni

Does scp work from the host you connect to UCSM ?

What OS for scp server

any firewall ?

I assume you never get to the point, where you have to enter a pw ?

 

Hello wdey,

 

I am able to connect from some other server (Windows Server) to that SCP backup server (Linux)

 

Both hosts I mean UCS Manager, Backup Linux server, and Windows Server are in the same VLAN. (management). So there is no firewall.

 

What do you mean 

 

"I assume you never get to the point, where you have to enter a pw ?"

 

Cheers and I am waiting for quick replay.

Can you please post a screenshot of the backup configuration, as well as the full error message !

Would you mind trying this with CLI

 

SSH to the Fabric Interconnect

Change to the system scope by typing “scope system”

create backup scp://ucsbackup@ucs-allbackup.domain.com/home/ucsbackup/fabricInterconnectName_all_configuration.bak all-configuration enabled

Go back to the scope system (type exit)

Note: ucsbackup is the username you login to your SCP server with. After each create backup command is issued you will be required to put in the password, this is a onetime process.

Hey wdey,

 

Yes, I sorry, i forgot provide output from CLI.

 

I tried to push 

 

 

FABRIC(local-mgmt)# copy workspace:/techsupport/some_date_here.tar scp://ucsbackup@some_IP_address
no matching cipher found: client aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se server aes128-ctr,aes192-ctr,aes256-ctr
lost connection

 

 

With your hints, i did and ...

 

FABRIC  /system # create backup scp://ucsbackup@here_is_IP_ADDRESS/home/ucsbacku                                        p/fabricInterconnectName_all_configuration.bak all-configuration enabled
Password:    [here i typed password of course]
FABRIC /system/backup* #
FABRIC /system/backup* # exit

 

from server 

[ucsbackup@some_backup_server ~]$ ls -la
total 28
drwx------  3 ucsbackup ucsbackup 4096 Jul  8 16:41 .
drwxr-xr-x. 9 root      root      4096 Jul  3 14:30 ..
-rw-------  1 ucsbackup ucsbackup  176 Jul  9 19:56 .bash_history
-rw-r--r--  1 ucsbackup ucsbackup   18 Jul  9  2013 .bash_logout
-rw-r--r--  1 ucsbackup ucsbackup  176 Jul  9  2013 .bash_profile
-rw-r--r--  1 ucsbackup ucsbackup  124 Jul  9  2013 .bashrc
 

 

As you can see, empty

 

 

 

Hi

If I understand you correctly, with CLI, you can connect to the scp server (therefore network connectivity is ok), enter a pw, and the backup finishes without an error message, the proper file is created, but it is empty ? correct ?

 

Hey,

 

Wdey, that is correct, after typed password i suppose t see some progress % % %

 

But I didnt see....

Not sure, that one sees a progress bar !

Did you just out of curiosity try another method, like ftp, tftp,.....or even to the local system.

I know scp has been done in the past; not myself however !

Hi Wdey,

 

I didnt check other methods.

 

Could you provide some example of local system...

 

Maybe there is a problem with ssh certificates ? on ucs side ? maybe same linux side, i dont know.... 

 

 

Looking at the logs you posted there is a mismatch in algorithms betwen scp server and ucs system. Server is accepting aes-ctr and ucs is using aes-cbc ?
Maybe try adding

"Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc"  to /etc/ssh/sshd_conf

 

Wdey, take a look on error log

pwojtachnio
Level 1
Level 1

any idea ?

I would open a TAC case ! strange that CLI doesn't bring you the same error !

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: