Monitoring, Management & Location Tracking

Strategies for adding APs into AMP

Aruba Employee

1. Complete adding all of the APs to the appropriate groups. 
2. Get the APs into an UP and error free state. 

- If an AP is down that means AMP cant ping or snmp walk it. Make sure AMP can reach the devices and that we are using the correct SNMP credentials. The credentials AMP is using can be verified on the APs/Devices -> Manage page for that AP. 
- Make sure the configuration returns either Good or Mismatched. The AP might have an error in its Configuration Status. There are two common reasons why template-based APs (for example Cisco IOS and Aruba devices) might be in an error state: a telnet error or no template is saved for the group. If there is a telnet error you will want to fix it before you start looking at configurations. If the devices are not configured via templates (ie Proxim, HP, Airespace, etc), the most common cause of an error is a community string that doesn't have read/write credentials.

3. Work down the mismatches group by group. 

- Decide on a standard firmware version. On the AMP Setup -> General page, under firmware options find the Allow Firmware Upgrades in monitor-only mode and select yes. Upgrade all APs not on the desired firmware. 
- Make sure there is a template defined for the group that looks good. 
- Read through the mismatches using the device config audit report for the group. Make sure you understand them. 
- To get rid of the last few mismatches you will need to manage the APs. To manage the APs go to the Groups -> Monitor page. Click modify devices. Click check all to select all of the APs in the group. Place the APs in Managed mode and AMP will push the config out to the APs.

Version history
Revision #:
1 of 1
Last update:
‎06-09-2014 03:56 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.