Reset Search
 

 

Article

CLI command for layer 3 adoption of WiNG access points

« Go Back

Information

 
TitleCLI command for layer 3 adoption of WiNG access points
Symptoms
Remote APs are not adopting to the controller. APs have not been pre-staged and DHCP option 191 is not implemented. 
Environment
  • AP76xx series
  • AP75xx series
  • AP65xx series
  • Legacy AP650
  • Legacy AP71xx series
  • WiNG 5.x
  • Layer 3 switch/s
  • Mint level 1 and level 2 deployments
  • SSH (Secure Shell) client or console port access using baud rate (speed) 19200 or 115200
Cause
In a routed environment, when DHCP option 191 has not been implemented and the APs have not been pre-staged, they will not know how to look for the adoptive controller. 
Resolution
Depending on your networks Mint level deployment, here are the commands to run on the APs:
  • Log into the AP via SSH or console port and run the following commands:
  1. Mint level 1 deployment - No cluster
>en
#self
Enter configuration commands, one per line.  End with CNTL/Z.
#controller host <controller-IP-address>        
#com wr
[OK]
#show adoption status

- <controller-IP-address> Enter IP address of the adoptive controller
  1. Mint level 1 deployment - with cluster
>en
#self
Enter configuration commands, one per line.  End with CNTL/Z.
#controller host <master-controller-IP-address> pool 1
#controller host <standby-controller-IP-address> pool 1    
#com wr
[OK]
#show adoption status

- <controller-IP-address> Enter IP address of the adoptive controllers
  1. Mint level 2 deployment - No cluster 
>en
#self
Enter configuration commands, one per line.  End with CNTL/Z.
#controller host <controller-IP-address> level 2
#com wr
[OK]
#show adoption status

- <controller-IP-address> Enter IP address of the adoptive controller
  1. Mint level 2 deployment - with cluster
>en
#self
Enter configuration commands, one per line.  End with CNTL/Z.
#controller host <master-controller-IP-address> pool 1 level 2
#controller host <standby-controller-IP-address> pool 1 level 2    
#com wr
[OK]
#show adoption status

- <controller-IP-address> Enter IP address of the adoptive controllers
  • You can automate the process of checking adoption status by running the following commands:
#watch <time-in-seconds> show adoption status 

Example: 
#watch 5 show adoption status

- The command "show adoption status" will be automatically executed every 5 seconds
- Use the CTRL-c keys ​to cancel 
Additional notes
  • It is recommended to create a profile for each AP on the controller. Both, primary and standby controllers have to be listed in the profile. 
  • Depending on the size of the deployment, give the APs a little time to adopt.

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255