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
  • FW: 7.1.2
  • SSH
  • CLI
  • ExtremeCloud 4.36.03.0006
  • Centralized Deployment
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. Log into the WiNG AP and run the following commands:
>en
#set-personality identify
#reload
Alternatively, you can press the reset button on the side of the AP for about 20-30 seconds to get it back into discovery mode, but only use this method if no other WiNG devices are present in the same broadcast domain. 
Once fully rebooted, the AP should have reverted back to the Identify CLI
  1. Log in using the following credentials:
  • Login as: admin
  • Password: admin123
  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 and 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

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255