Reset Search
 

 

Article

AP's connect to foreign controller after they are upgraded with secure tunnel enabled

« Go Back

Information

 
TitleAP's connect to foreign controller after they are upgraded with secure tunnel enabled
Symptoms
  • AP's show connect to their foreign controller rather than their local after a reboot.
Environment
  • IdentiFi Wireless
  • Extremewireless
  • Any model AP
  • Local vs Foreign controller
  • acinfo.conf file in the AP's configuration is populated with wrong local controller address
Cause
Before secure tunnel was added as a feature, the foreign controller would not accept the AP if the availability link was up. With the secure tunnel design it was decided that the controllers would accept the AP as long as the IPsec connection was established and there was no consideration whether the AP was foreign or local. Engineering is stating this is functioning as designed. 
Resolution
A simple work around to correct the acinfo files on the AP is to use multi-edit and toggle the secure tunnel setting to off. The secure tunnel setting is also saved in the acinfo.conf file and when the file is rewritten the current controller is also written out to the file.  
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255