restore config from backup

[Isar1]

Hi,

I'm trying to transfer a backup from a 3549GTS-PWR+ to another 3549GTS-PWR+, but I get an error “Cannot use configuration data from a different type of Baystack module.
Operation aborted.”

I use FW:5.3.0.10 and SW:5.3.12.009 on both switches.

The only difference I see is that one is HW:03 and the other is HW:06

Is this the Problem?

Thx for your answers

[EXTR_Paul]

 glad you sorted it out.  You are correct in your method. I actually learnt something new.  In 18 years of messing with ERS’s I never used this BOOT DEFAULT command.  I only ever use the restore factory….

 But just mindful that you did have this part quoted incorrect.

 Copy Config backs up the binary.  Copy Run backs up the ascii. 

[Isar1 · Accepted solution]

I fixed the problem

Yesterday I got the next 3 ERS3549 to configure and I tried a few things.

The problem is the command “boot default”, after that it’s not possible to restore the backup.

The solution is the command “restore factory-default”, after that I have no problem to install the backup.

Thanks for your help

[EXTR_Paul]

“Copy config” will backup the binary config file.

“Copy running-config” will backup the ASCII config.

Then to restore a switch you need to use the “CONFIG NETWORK ?” commands.   Inside the CONFIG NETWORK sub commands will be your options to load the binary config to the switch.

This is really easy with ERS’s that have a USB port, but because the ERS3500 don’t have a USB port you need to do a network file transfer and TTBOMK you can ONLY do that with the binary file. 

When working  with the ASCII file its probably easiest to just CUT and PASTE it into the CLI.

[SamPirok]

Thank you for your patience here. There are some configuration settings that can be enabled that require a reboot to take effect before you can configure them further, it’s possible we’re trying to move configuration over to the new switches that require extra steps to enable. Some of the configuration options that have these requirements are: spb vs non-spb, spanning tree, rear ports set to stack vs ports not set to stack, etc. I think at this point your best coarse of action would be to open a support case so we can review the configuration with you to see if there is anything in there that may cause this failure.