Post by account_disabled on Oct 28, 2017 5:39:27 GMT -5
Hi,
Had an AP (3702, driven by a Wism2) fail in our environment. Another AP got the failed AP's IP address. Prime now shows two AP's as registered. Both have the same IP but different hostnames. The controller does not show the failed AP as associated though.
Deleting the AP from Prime fails - says still associated to the controller. Placing it in maintenance mode says it's successful but it really isn't. Deleting it afterwords still fails in the same manner. I've taken the AP that got the same IP offline manually. It's disappeared out of Prime. The failed AP (which is now physically disconnected from the network) still shows as registered.
I've synched the controller manually several times. Any thoughts?
Please help.
Thanks!
I didn't find the right solution from the Internet.
References supportforums.cisco.com/t5/network-management/ap-quot-stuck-quot-in-prime/td-p/3205890
best advertisements
Had an AP (3702, driven by a Wism2) fail in our environment. Another AP got the failed AP's IP address. Prime now shows two AP's as registered. Both have the same IP but different hostnames. The controller does not show the failed AP as associated though.
Deleting the AP from Prime fails - says still associated to the controller. Placing it in maintenance mode says it's successful but it really isn't. Deleting it afterwords still fails in the same manner. I've taken the AP that got the same IP offline manually. It's disappeared out of Prime. The failed AP (which is now physically disconnected from the network) still shows as registered.
I've synched the controller manually several times. Any thoughts?
Please help.
Thanks!
I didn't find the right solution from the Internet.
References supportforums.cisco.com/t5/network-management/ap-quot-stuck-quot-in-prime/td-p/3205890
best advertisements