SNMP Reports
Why is the response time slow when querying for SNMP reports ?
If the controller is busy collecting data for other tables and if the time taken is longer than the timeout setting for SNMP reports, then the SNMP client tool displays the Timeout No Response error.
Following are the solutions for the response time being slow.
- Increase the interval of the query scripts or tools to make sure there is only one SNMP client tool to query the controller at a time. Adjust the query interval of the query scripts or tools by the loading of the controller. Otherwise, SNMP daemon takes longer to complete all queries. It is recommended that you do not run multiple queries at the same time.
- Do not use MIB browser to monitor the APs. Most MIB browsers can only provide snmpwalk which is not an efficient for querying large volume of data and are unable to store large volumes of data.
- Increase the timeout value of the SNMP client tools. Always try to increase the timeout value of the SNMP MIB browser or SNMP CLI commands based on the number of APs and UEs on the controller.
- Get the table index by using snmpwalk and use snmpget to get multiple entries of same
index at a time.
- Step 1 - Use a script to query the index of the table using snmpwalk as seen in the
below example.
Example: snmpwalk <options> <IP> <table index 1 OID>snmpwalk <options> <IP> <table index 2 OID>
- Step 2 - Use a script to query multiple table entries for same index at a time using
snmpget as seen in the below example.
Example: snmpget <options> <IP> <table entry 1 OID>.index1 <table entry 2 OID>.index1 ... <table entry N OID>.index1
- Step 1 - Use a script to query the index of the table using snmpwalk as seen in the
below example.