Migration 2106 to 2504 controller

[Erik Boss]

I have a question to migrate a customer from a 2106 controller to a 2504 controller.

Can I use the configuration file with both controllers having the same version?

Or is there another way not having to do it again manually?

The old configuration is OK, only the hardware is end of sale.

Thanks in advance.

Erik

[George Stefanick]

Hi Erik,

yes, you should be able to do this without any issue. make sure the code rev is the same and you will be good to go. Ive done this myself in my home lab ..

__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
__________________________________________________________________________________________
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

[George Stefanick]

One this to note -- If you have more controllers sharing the same mob group that will need to be updated.

__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
__________________________________________________________________________________________
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

[Erik Boss]

Thanks!

Gonna try this tomorrowevening.

[Erik Boss]

Hi George,

I just downgraded the 2504 controller to 7.0.235.3, same as my current 2106 version.

After that I copied my backup file locally and I put the file with TFTP onto the new controller.

He automatically reboots.

Then I want to login due to CLI, I couldn't login locally. Both local management users with are current, I couldn't login with it.

Do you know what this could be?

Regards,

Erik

[Scott Fella · Accepted solution]

You will need to reboot the WLC and then break out by hitting esc when promted during the boot.  Erase the configuration on the 2504 and start again.... What I normally do is edit the management username so its not hashed.  So take your 2106 config and open it up in a text editor and remove the hased username and add this:

config mgmtuser add read-write

EX.

config mgmtuser add Cisco Password read-write Description

MAKE SURE YOU LEAVE A TRAILING BLANK SPACE AT THE END.  IF YOU NOTICE, THERE IS A TRAILING BLANK SPACE AFTER EACH COMMAND!!!!!!!!!

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

[Erik Boss]

I'll try this Scott. Thanks.

I didn't know about the blank space after each command.

I already erased the config by pressing 4 during the startup.

Hope this will work

Regards,

Erik

[Scott Fella · Accepted solution]

Keep us posted:)

Sent from Cisco Technical Support iPhone App

[Erik Boss]

works great! Tnx!

[Scott Fella]

Thaks for the follow up.. good to know!

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

[Erik Boss]

Hi Scott,

all I did works fine now. Just shutdown all wlans on the new controller, add a new wlan with psk to test my config with the serial interface

Works fine.

But when I want to connect to the GUI, telnet, ssh, I can't connect. Only ping works fine.

Switchport is in trunking mode, nothing else configured with access-lists or something like that.

The clients receives an IP-address from an external DHCP-server.

old controller 2106: 10.0.100.250 (vlan 100)

new controller 2504: 10.0.100.249 (vlan 100)

DHCP server 10.0.0.146 (vlan 20)

an Cisco router is default gateway.

switchport is in trunking mode.

With the CLI I checked the network config. Saw SSH, telnet, secureweb disabled. I enabled it, rebooted it 3 times with no luck.

Even when I connect port 1 from the controller to my laptop within the same IP-range, no connection.

Firewall disabled, even no remote connection.

Working with 7.0.235.3.

Also tested mobility anchor between my old 2106 and new 2504 controller. Stays down. I can understand that with these problems.

Do you have any idea?

In the mean time, I should have configured it by hand

Tnx.

[Scott Fella]

You testing from a wired device not a wireless device correct?

Sent from Cisco Technical Support iPhone App

[Erik Boss]

I tried wired directly connected to the controller.

I also tried it wireless connected via an SSID on the old controller.

Old and new controller on the same IP-range... sounds strange to me.

Also doing a telnet from my router on 443 to the new controller.

PS: also enabled wireless via dynamic and management interface...

Regards,

Erik

[Scott Fella]

Not wired directly into the WLC , but from a wired machine on the network.

Sent from Cisco Technical Support iPhone App

[Erik Boss]

I tried it from the router with a telnet 10.0.100.249 443 source vlan 100

no response.

It's the same as I connect my laptop wired to the switchport in vlan 100.

Regards,

Erik