Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

Layer 3 access point loses connectivity and constantly reboots after assigning new AP profile

« Go Back

Information

 
TitleLayer 3 access point loses connectivity and constantly reboots after assigning new AP profile
Symptoms
  • Layer 3 AP loses connectivity after creating new AP profile
  • Layer 3 AP constantly rebooting
  • Unable to ping AP after profile change
Environment
  • Summit WM3000 Series
  • Altitude AP
  • WiNG 5.X
  • Layer 3 AP Adoption
Cause
There was no  IP address configured on the control VLAN in the assigned profile. An IP address is required for layer 3 communication and adoption.
Resolution
An IP address and default gateway must be statically configured on each individual access point via its device configuration or DHCP IP assignment must be configured in the AP profile.

To configure a static IP address on a single AP from the WM controller CLI enter the following commands:
connect <AP_NAME>
enable
self
interface vlan <CONTROL_VLAN_ID>
ip address <IP_ADDRESS>/<NETMASK> 
..
ip default-gateway <GATEWAY_IP>
commit write

To configure DHCP based assignment on the AP profile from the WM controller CLI enter the following commands:
enable
configure t
profile <AP_MODEL> <PROFILE_NAME>
interface vlan <CONTROL_VLAN_ID>
ip address DHCP
ip dhcp client request options all #This can only be enabled on one interface on the AP
commit write

 
Additional notes
If DHCP assignment is used the default gateway must be sent via DHCP options.  The controller IP address must also be sent to the AP via DHCP option 189 or 191

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255