Transferring configuration to new identical switch Catalyst 3850+

[pdenableetoavit19698]

Hi there,

I have 2 3850 Catalyst configured together but defective.

I want to transfer their working configuration to two identical 3850.

What is the best way to proceed?

Save the configuration file of the main switch and to transfer it to the new main one? (if so what is the best procedure to do it properly?)

Or use the CLI copying and pasting configuration? (if so what is the best procedure to do it properly?)

Or the web interface (how to reach it and what is the best procedure to do it properly?)

Or TFTP/SSH/USB? (if so what is the best procedure to do it properly?)

Thank you for any tip/links etc.

All the best!

[Leo Laohoo · Accepted solution]

Switch 1 is the good switch.  Switch 2 is a secondary switch.  And you want to "copy" the firmware and the IOS from Switch 1 to Switch 2?  This is how you do it: 

1.  Switch 1:  In configuration mode, enter the command "software auto-upgrade enable" and save the config. 
2.  Make sure Switch 2 is POWERED OFF. 
3.  Connect the stacking cable from Switch 1 to Switch 2.  
4.  Power up Switch 2.  
5.  Wait for Switch 1 to push the firmware and config down to Switch 2. 
6.  Do not remove Switch 2 from the stacking cable. 

Leave Switch 2 connected to Switch 1.  Any config changes to Switch 1 gets pushed to Switch 2.  

[pdenableetoavit19698]

Hi there @Leo Laohoo 

thanks again for this comments

I have been trying this. For some reason when I do it the SW2 get stuck on the booting line :

"All packages are digitally signed 

Starting system services"

I have waited for more than 30 min but nothing else happens.

Is there a problem if SW2 has newer software version than SW1? 

thanks

[Leo Laohoo]

Console into Switch 2 and reboot.

Post the entire boot-up process.

[pdenableetoavit19698]

thanks @Leo Laohoo 

it gets stuck here... been waiting 30min now:

"

Base ethernet MAC Address: 

Interface GE 0 link down***ERROR: PHY link is down

Initializing Flash...

flashfs[7]: 0 files, 1 directories

flashfs[7]: 0 orphaned files, 0 orphaned directories

flashfs[7]: Total bytes: 6784000

flashfs[7]: Bytes used: 1024

flashfs[7]: Bytes available: 6782976

flashfs[7]: flashfs fsck took 1 seconds....done Initializing Flash.

Getting rest of image

Reading full image into memory....done

Reading full base package into memory...: done = 79113792

Nova Bundle Image

--------------------------------------

Kernel Address    : 0x6042d350

Kernel Size       : 0x402ecf/4206287

Initramfs Address : 0x60830220

Initramfs Size    : 0xdb9420/14390304

Compression Format: .mzip

Bootable image at @ ram:0x6042d350

Bootable image segment 0 address range [0x81100000, 0x82110000] is in range [0x80180000, 0x90000000].

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@boot_system: 380

Loading Linux kernel with entry point 0x81653a10 ...

Bootloader: Done loading app on core_mask: 0xf

### Launching Linux Kernel (flags = 0x5)

All packages are Digitally Signed

Starting System Services"

[Leo Laohoo]

Boot the switch into ROMMON and then perform an emergency install of the OS using the command "emergency-install usbflash0:filename.bin". 

WARNING:  emergency-install will completely wipe the switch of any data.

[pdenableetoavit19698]

thanks. what do you think the problem is? 

how do you boot the switch into ROMMON?

thanks so much

[pdenableetoavit19698]

For some reasons, doing it this way, something did not work. SW 2 will stay stuck as indicated above in the console lines, and the configuration of SW1 got changed and systems stopped working. Fixed by loading again the backup file of the original startup-config. Not sure what happened but I did follow the details above.

[Joseph W. Doherty]

"I have 2 3850 Catalyst configured together but defective.

I want to transfer their working configuration to two identical 3850."

If they are defective, how will you be able to obtain their configs?

[pdenableetoavit19698]

sorry @Joseph W. Doherty didnt write correctly.

1 SW is the good one and the other SW is the defective/not configured properly one. so how to transfer from SW1 to SW2

thanks

[guruvignesh]

Hello ,

1. On the source switch:

   • Access the command line interface.
   • Type (show running-config) to view the configuration.
   • Copy and paste the configuration into a text file.

2. On the target switch:

   • Access the command line interface.
   • Enter configuration mode using (config terminal).
   • Paste the configuration from the text file into the terminal.
   • Save the configuration with ( write memory)

[doss270423]

A.

Saving the configuration file and transferring it to the new main switch:
1. Connect to the main defective switch using a console cable or SSH.
2. Enter the following command to save the configuration file:

copy running-config tftp://<ip-address-of-tftp-server>/<filename>
​3. Connect to the new main switch using a console cable or SSH.
4. Enter the following command to transfer the configuration file from the TFTP server:

copy tftp://<ip-address-of-tftp-server>/<filename> running-config
​

5. Verify the configuration by entering the following command:

show running-config

B. 

Using the CLI to copy and paste the configuration:
1. Connect to the main defective switch using a console cable or SSH.
2. configure terminal
​3. Enter the following command to copy the running configuration: copy running-config
​4. Connect to the new main switch using a console cable or SSH.
configure terminal
​paste
​show running-config

C.

Using the web interface:

1. Connect to the main defective switch using a web browser.

2. Enter the IP address of the switch in the address bar.

3. Enter the username and password when prompted.

4. Click on the "Configuration" tab.

5. Click on the "Save" button to save the configuration file.

6. Connect to the new main switch using a web browser.

7. Enter the IP address of the switch in the address bar.

8. Enter the username and password when prompted.

9. Click on the "Configuration" tab.

10. Click on the "Restore" button and select the configuration file that you saved in step 5.