Hi all
We have several clusters of Cisco Catalyst 9800-CL Wireless Controller (16.12.3) running on
From time to time we have seen uplanned reloads of the WLCs.
It turns out that the WLC reloads itself when the VMs are moved with vMotion.
According to Cisco this should (of course) not happen.
"Flexibility in deployment—You can easily move a VM from one server to another. Thus, you can move the controller from a server in one physical location to a server in another physical location without moving any hardware resources. "
(https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/9800-cloud/installation/b-c9800-cl-install-guide/controller_overview.html(https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/9800-cloud/installation/b-c9800-cl-install-guide/controller_overview.html)
Guest OS: Other 3.x or later Linux (64-bit)
Compatibility: ESXi 6.5 and later (VM version 13)
VMware Tools: Running, version:2147483647 (Guest Managed)
Anybody else seen this?
Solved! Go to Solution.
That’s expected. Cold vmotion is supported but hot vmotion is not, meaning, it is supported if the 9800-CL VM powered off in the entire duration of migration.
There is “enhancement” bug for that CSCvw24185, check it here: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvw24185
That’s expected. Cold vmotion is supported but hot vmotion is not, meaning, it is supported if the 9800-CL VM powered off in the entire duration of migration.
There is “enhancement” bug for that CSCvw24185, check it here: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvw24185