Buy or Renew
Buy or Renew
NOTICE: You can now engage in the community. Learn about the great new Cisco Umbrella content.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4010
Views
0
Helpful
17
Replies

Migrating from old WLC to new vWLC

Richard Klinkbeil
Level 1
Level 1

‎12-22-2016 01:34 PM - edited ‎07-05-2021 06:16 AM

Hello all,

I currently have 2x 3502i-A-K9 Ap's connected to a WLC-4402. AP FW is 7.0.252.0 and the WLC FW is 12.4(23c)JA10.

I recently got a Virtual WLC and have it initially configured. I would like to migrate those AP's over to it. I tried setting the new WLC as the master WLC and rebooted a single AP and waited to see if it would connect to the new one. It took awhile but didnt connect and ended up going back to the old 4402.

The vWLC is running FW 8.2.141.0. I also tried setting a secondary WLC in the AP settings to the new vWLC and a simple reboot of the AP didnt have any positive results.

How would I go about migrating these AP's over to the new vWLC? compatibility matrix says the 3500i is supported on the current VWLC firmware?

Labels:
0 Helpful
17 Replies 17

Leo Laohoo
Hall of Fame
Hall of Fame
In response to Richard Klinkbeil

‎12-22-2016 06:14 PM

Hmmmm ... 


Read THIS.

0 Helpful

aesmaeil
Cisco Employee
Cisco Employee
In response to Richard Klinkbeil

‎12-23-2016 03:58 AM

Maybe the issue is vWLC is trying to authorize APs against MIC database. You can disable this feature by using this command:

config auth-list ap-policy authorize-ap disable

0 Helpful

Richard Klinkbeil
Level 1
Level 1
In response to Leo Laohoo

‎12-22-2016 05:56 PM

Oh also, When I ran a debug of capwap, I can see both AP's send requests, but I do see a message that says:

osapiBsnTimer: Dec 23 01:53:11.037: Same gateway prevails

*spamApTask0: Dec 23 01:54:36.917: 50:3d:e5:d9:cf:71 CAPWAP Control Msg Received from 192.168.2.16:40184

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 packet received of length 118 from 192.168.2.16:40184

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Msg Type = 19 Capwap state = 0

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Primary Discovery Request from 192.168.2.16:40184

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 msgEleLength = 1 msgEleType = 20

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Total msgEleLen = 89

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 msgEleLength = 40 msgEleType = 39

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Total msgEleLen = 45

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 msgEleLength = 1 msgEleType = 41

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Total msgEleLen = 40

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 msgEleLength = 1 msgEleType = 44

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Total msgEleLen = 35

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 msgEleLength = 10 msgEleType = 37

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Vendor specific payload from AP C0:62:6B:D5:02:10 validated

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Total msgEleLen = 21

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 msgEleLength = 17 msgEleType = 37

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Vendor specific payload from AP C0:62:6B:D5:02:10 validated

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Total msgEleLen = 0

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 1. 0 0

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 2. 232 3

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 3. 0 0

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 4. 200 0

*spamApTask0: Dec 23 01:54:36.917: apModel:

*spamApTask0: Dec 23 01:54:36.917: apType = 64 apModel:

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Discovery resp: AC Descriptor message element len = 40

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 acName = vWLC

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Discovery resp:AC Name message element length = 48

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Discovery resp: WTP Radio Information msg length = 57

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Discovery resp: CAPWAP Control IPV4 Address len = 67

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Discovery resp: CAPWAP Control IPV6 Address len = 67

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Discovery resp: Mwar type payload len = 78

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Discovery resp: Expire MIC type payload len = 92

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Discovery resp: Time sync payload len = 107

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Primary Discovery Response sent to 192.168.2.16:40184

*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 WTP already released
*spamApTask0: Dec 23 01:54:36.917: c0:62:6b:d5:02:10 Received LWAPP PRIMARY_DISCOVERY_REQ from AP
*spamApTask0: Dec 23 01:54:36.917: 50:3d:e5:d9:cf:71 LWAPP Primary Discovery Request AP Software Version: 0x700fc00
*spamApTask0: Dec 23 01:54:36.917: 50:3d:e5:d9:cf:71 Discarding Primary discovery request in LWAPP from AP supporting CAPWAP

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card