Reset Search
 

 

Article

How to switch AP5xx APs from WiNG to Identify for adoption by the ExtremeCloud Appliance in a Centralized deployment

« Go Back

Information

 
TitleHow to switch AP5xx APs from WiNG to Identify for adoption by the ExtremeCloud Appliance in a Centralized deployment
Objective
To switch AP505 and AP510 APs from a WiNG to an Identify interface, and configure them for adoption by the ExtremeCloud Appliance in a centralized deployment. 
Environment
  • AP510
  • AP505
  • WiNG
  • Identify (Centralized Deployment)
  • FW: 7.2.1.1-006R
  • SSH
  • CLI
  • ExtremeCloud 04.56.02.0030
Procedure
Right out of the box, the AP5xx (505/510) series APs boot up into "Discovery Mode"; however, the existence of any WiNG device in the same broadcast domain will cause them to automatically switch over to the WiNG interface which will prevent them from working in a centralized ExtremeCloud deployment. In such a case the following steps have to be followed to switch them back to the Identify CLI and configure them for adoption using the correct interface:
  1. Make sure the AP os powered up BUT not connected to your corporate network (completely segregated) 
  2. Reset the AP by pressing the reset button for about 20 seconds. 
  3. Log in using the following credentials:
  • Login as: admin
  • Password: admin123
  1. Once logged in, the AP should be in discovery mode:
AP adoption discovery process in progress...
To cancel and boot in Standalone mode, type (s):
  1. You have the following boot up options to choose from:
  • Type "s" for Standalone. This will boot the unit up into WiNG 
  • Type "CCC" for Centralized. This will boot the AP up into Identify
  • Type "PPP" for service personnel. This will bring up the AP shell which can be used to perform an upgrade
  1. Type "CCC" to boot the AP up into Identify:
AP adoption discovery process in progress...
To cancel and boot in Standalone mode, type (s):CCC

AP booting in Centralized mode...
  1. At this point, check to make sure that the AP is pulling the correct DHCP IP address and VID (VLAN id). If not, follow these steps to troubleshoot the issue:
  • To verify IP address and VID information:
# cget config global | grep -i vid
# cget config global | grep -i ip
#cset factory
The AP will automatically reboot and pull a DHCP IP address. Verify that the AP can ping the ExtremeCloud appliance and vice versa. 
  1. Log back into the AP to point it to the ExtremeCloud appliance:
#Cset authipaddr 1 <ip of ExtremeCloud Appliance>
#Capply
#Csave
#Reboot
  1. Once rebooted, check to see if the AP has been adopted and that the correct IP address information acquired:
Example:
# cget config global | grep -i ip
lastAcIp 192.168.10.140
dnsIpAddress 1 192.168.10.10
dnsIpAddress 2 207.164.244.123
wipsMode 0
authIpAddr 1 192.168.10.140
failover bmIp [1] 192.168.10.140 Home
ip 192.168.10.40
High Throughput HT capability for WEP and TKIP is disable (0)
lbsSrcIp 0.0.0.0
lbsDstIp 0.0.0.0
#
Additional notes
Another way to change WING AP personality
During a factory reset, we were not able to catch the “AP adoption discovery in process…

Console to Wing AP
  1. resetDeep
  2. enter password
  3. set-personality IdentiFi
  4. commit write memory
  5. reload

confirm you can ping the XMC

you may still have to hard code the XMC ip.
  1. cset authIpAddr 1 <IP of XMC>
  2. capply
  3. csave
  4. reboot

When you see the yellow tringle of the AP in the XMC, assign it to a site
 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255