Unexpected AP adoption by another controller (VC) in the same subnet
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-28-2019 12:07 PM
Hi,
I have a setup with a VX9000 and three 7522 APs which are adopted by the VX9000.
In the same subnet I setup two 7532 one as VC and the other as adopted AP by the VC to test stuff.
When I rebooted the VX9000, all three 7522APs got adopted by the 7532VC !
when the VX9000 was back up it re-adopted the three 7522 but things were not working well because the 7532 had a newer firmware and upgraded thet 7522 APs, resulting version missmatch when the VX9000 re-adopted them.
Is this normal? Is there any way to prevent this from happening and have two isolated controller in the same subnet?
thank you in advance.
I have a setup with a VX9000 and three 7522 APs which are adopted by the VX9000.
In the same subnet I setup two 7532 one as VC and the other as adopted AP by the VC to test stuff.
When I rebooted the VX9000, all three 7522APs got adopted by the 7532VC !
when the VX9000 was back up it re-adopted the three 7522 but things were not working well because the 7532 had a newer firmware and upgraded thet 7522 APs, resulting version missmatch when the VX9000 re-adopted them.
Is this normal? Is there any way to prevent this from happening and have two isolated controller in the same subnet?
thank you in advance.
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-28-2019 12:48 PM
Here is the WiNG Best Practice Doc it will give more detail.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-28-2019 12:46 PM
yes, its normal
One way you can prevent this by configuring 'controller host IP-addresses' on the AP profile.
In current state ssh via cli to APs and run below commands:
en
self
controller host "The IP address, hostname or host alias of the controller"
com write
One way you can prevent this by configuring 'controller host IP-addresses' on the AP profile.
In current state ssh via cli to APs and run below commands:
en
self
controller host "The IP address, hostname or host alias of the controller"
com write
