This document is a guide to serve as a first-step when troubleshooting basic access-point/access-controller inter-connectivity and configuration issues with the NetVanta 160 series Access-Points. This guide will also cover the basic requirements for a NetVanta 160 series AP to connect to an AOS controller and properly function in an environment with multiple VLANs. Note that before starting this, make sure you are on AOS version R10.4.0 or higher as the NetVanta 160 series will not function correctly without this firmware.
The NetVanta 160 series AP requirements are covered below along with an explanation:
- Dot11ap access-point-control must be turned on globally inside the AOS controller.
- Inside the CLI this command is dot11 access-point-control which can be entered in global configuration mode.
- Inside the GUI, navigate to the "Data" tab and then under "Wireless" you will find "AC/AP Discovery". Inside this page, make sure "Access Controller" is checked.
- AWCP must be on in the VLAN/Ethernet IP interface you are using to control this AP.
- Inside the CLI, you can check this by looking at the interface you are using to control the AP and making sure the no awcp command does not show up under that interface's configuration (it is on by default so you will only see it show up if it is off).
- Inside the GUI, navigate to the appropriate interface under the "Data" tab, and "IP Interfaces". Inside that interface, there is a check box called "Enabled AWCP". Make sure it is checked.
- AWCP can only function properly in the Native VLAN.
- AWCP is never tagged as a Layer 2 protocol, so the AP's cannot tag management traffic as it leaves the interface towards the controller. Because of this, AWCP can only work in the Native VLAN - meaning that you must have it on a trunk port whose native VLAN is the same as the APs control VLAN (By default, a trunk port's native VLAN is 1). For example: The AP will be managed in VLAN 3. The port configuration for the port the AP will be plugged into would look like the below:
interface sw 0/1
switchport mode trunk
switchport trunk native vlan 3
Note: If a layer 2 switch (or multiple switches) is installed between the AP and the controller, the native VLAN must be preserved through each trunk connecting to the AP.
4. An AOS Controller must have an IP address assigned to the management VLAN/Ethernet interface being used between the AP and the controller.
- Though AWCP does not use Layer 3/IP to communicate with the controller, the the AP must be able to communicate to a Layer 3 interface on the controller. (Hence AWCP would not be on otherwise).
Note: If you are using a Layer 2 only switch, only a single layer 3 VLAN interface can be configured, and an AP must be able to communicate to that particular VLAN interface.
5. If your AP will be carrying multiple VLANs, the controller interface connecting to the AP must be configured as an 802.1q trunk. The AP must also be configured with 802.1q encapsulation.
- Trying to use VLANs without actually configuring them in the AP config itself can cause problems with AP transmission.
- You can configure VLANs properly in the AP by referring to page 20 in this guide.
Verifying your AP has connectivity with the controller
If you have verified the above steps, you should be able to properly communicate with the NetVanta 160 series AP. To verify:
- In the GUI, navigate to "AC/AP Discovery" under the "Data" tab and verify you see the AP in question listed under "Dynamically Discovered Access-Points" as well as making sure the control status says "Uncontrolled" or "Controlled by this AC".
- In the CLI, you can check this by running the show command show dot11 access-points:
Wireless Access Points:
Name MAC-Address AP Status Cfg'd Control Status
------------------------ ----------------- ----------- ----- -----------------
ADTN295743 00:A0:C8:29:57:43 Session Y Ctl_by_This_AC
ADTN695560 00:A0:C8:69:55:60 Session Y Ctl_by_This_AC
Note: If your AP is reporting that it is in "Recovery Mode", follow the steps inside this document to recover the AP: