Monitoring, Management & Location Tracking

AMP 5.3 SNMP fetching and Aruba controller performance

- AMP monitoring causes a high load on the controllers. This issue is fixed by slowing down the fetching of SNMP tables from Aruba controllers. This fix is part of 6.0 and had not been ported over to 5.3.x. We found that this issue happens on all firmware of the Aruba controllers and especially worse on controllers running 2.5 firmware. There will be a flag on the AMP GUI which will enable the slow fetching. Once this flag is enabled snmp fetching on ALL devices will be slowed down. 

- Bump max_repetitions to 30. This is part of 6.0. 


- Set retries to 1 and SNMP timeout to "60secs" while monitoring Aruba devices. AMP 6.0 allows retries to be set at 1. 


- Use new OIDs for client SNR and bandwidth oids. This is part of 6.0. In order to use the new bandwidth oids, the customer will need to provision some commands on the controllers for the counters to be populated. These commands are different for 2.5 firmware and 3.x firmware. This change is part of 6.0. 


- AMP is slow in authorizing and monitoring a lot of Aruba devices. We saw this issue at Google. Darrell has a patch and will be patching the customer AMP today. It is not part of 6.0 and we will work on adding it to 6.0 later this week. 


- AMP monitoring causes a high load on the controllers. This issue is fixed by slowing down the fetching of SNMP tables from Aruba controllers. This fix is part of 6.0 and had not been ported over to 5.3.x. We found that this issue happens on all firmware of the Aruba controllers and especially worse on controllers running 2.5 firmware. There will be a flag on the AMP GUI which will enable the slow fetching. Once this flag is enabled snmp fetching on ALL devices will be slowed down. 


- Bump max_repetitions to 30. This is part of 6.0. 


- Set retries to 1 and SNMP timeout to "60secs" while monitoring Aruba devices. AMP 6.0 allows retries to be set at 1. 


- Use new OIDs for client SNR and bandwidth oids. This is part of 6.0. In order to use the new bandwidth oids, the customer will need to provision some commands on the controllers for the counters to be populated. These commands are different for 2.5 firmware and 3.x firmware. This change is part of 6.0. 


- AMP is slow in authorizing and monitoring a lot of Aruba devices. We saw this issue at Google. Darrell has a patch and will be patching the customer AMP today. It is not part of 6.0 and we will work on adding it to 6.0 later this week.

Version history
Revision #:
1 of 1
Last update:
‎06-09-2014 09:42 AM
Updated by:
 
Labels (1)
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.