Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Cisco Employee

vWLC serial number can change if using disaster recovery.

I know this was published before but I cannot find it at the moment so I will republish.

 

If  a person is running DRS for VMWare or any type of disater recovery  solution that moves the vWLC to another host, the serial number of the  vWLC will change. Since our SN is node-locked to the UUID in VMWare, if  the UUID changes, the UDI (and serial number) of the controller will  also change. The only way to avoid this from happening is to maintain  the UUID in VMware .

Here are a couple of VMWare KB articles:

Changing or keeping a UUID for a moved virtual machine (1541)
 
Virtual Machine Identifier - UUID
 

Ray Garner, CCNP

Cisco Wireless TAC

 

EDIT:

https://tools.cisco.com/bugsearch/bug/CSCun11124

https://tools.cisco.com/bugsearch/bug/CSCun11108

 

Both bugs now fixed as of wlc release 8.0.100.

5 REPLIES
Hall of Fame Super Silver

Re: vWLC serial number can change if using disaster recovery.

Thanks for the info!

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
Hall of Fame Super Silver

Re: vWLC serial number can change if using disaster recovery.

I'm guessing this would be good for PI and MSE also.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
New Member

On the line w/ Cisco

On the line w/ Cisco Licensing right now.  VMotioned my vWLC running 7.6.100.0 to another node in the ESXI cluster.  After I had rebooted, poof... all licensing was missing.   Luckily we should have the license keys rehosted here shortly so I can get my APs back online.

I don't see version 8.0.115.0 listed as a version with the known fixes, just the 8.0(100.0), and 8.0(72.160).   Can anyone confirm the bug is fixed in 8.0(115.0) as well please?  I would prefer not to vMotion again and repeat this entire licensing exercise if unnecessary.   ;)  Thanks for the posting!

Cisco Employee

Hi, the bug is fixed in 8.0

Hi, the bug is fixed in 8.0.115.

Please upgrade to the latest

Please upgrade to the latest version as the bug is now fixed in the latest one.

1015
Views
0
Helpful
5
Replies