Monitoring, Management & Location Tracking

How does AMP communicate with Cisco WLC controllers?

To communicate with Cisco WLC controllers the AMP uses SNMP for all monitoring, config management, and firmware upgrades (in the form of SNMP bulk gets and sets). You can use SNMP v1, v2c, or v3.

NOTE: The controller must be configured (from the controller's web UI or command line interface) to enable SNMP communication from the AMP. On the controller's web UI you can configure this on the Manage > SNMP > Communities page. You will need to give AMP Read/Write privileges If you want to manage the controller's and AP's configurations from AMP.

After adding the controller to AMP, AMP will discover all of the APs associated with the controller. Then do an Import Settings to populate the Groups > Cisco WLC page for the group containing the controller.

For firmware upgrades AMP uses SNMP to set up and execute an FTP transfer. FTP is then used to transfer the firmware image from the AMP to the controller.

On Cisco WLC controllers there are two locations available where a firmware image can be stored: the primary and the secondary. By default AMP will place the image in the primary location. If you would like to have the image stored in the secondary location, telnet or SSH (rather than SNMP) can be used to set up the FTP transfer. Please contact Customer Support if you would like to do this.

Some customers have reported having problems when using firmware versions 4.2.x. We recommend using at least version 5.2.x.

Version History
Revision #:
1 of 1
Last update:
‎06-17-2014 09:26 AM
Updated by:
 
Contributors
Search Airheads
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.