Follow

Not all tests being discovered due to timeout (Cisco Nexus)

This article is to make the reader aware of a known limitation where a partial list of available SNMP tests are presented during test discovery ('Create New Standard Tests' > snmp monitor) due to a webapp timeout. The timeout would not be obvious as the discovery will simply finish (after about 10-15 minutes) and display the list of tests it discovered within the time limit. 

This known limitation is not specifically limited to the Cisco Nexus device, but seems to be the more common large switches that contain large numbers of tests (6000+ tests) as evidenced by the output of TRAVERSE_HOME\utils\probeSnmpTests.pl ... | grep MONITOR or may be slow to respond to SNMP queries (due to router/switch system prioritization).

Many of the tests discovered in the large number of tests appear to be tests that may not be relevant to most customers. These tests are found to be the following test subTypes:

snmp/cbqos_policy_traffic_before
snmp/cbqos_policy_traffic_after
snmp/cbqos_policy_traffic_dropped
snmp/cbqos_policy_pkts_before
snmp/cbqos_policy_pkts_dropped
snmp/cbqos_policy_pkts_nobuf
snmp/cportqos_enqueue
snmp/cportqos_drop

Should you wish to avoid these tests from contributing to the long discovery time when using 'Create New Standard Tests' > snmp monitor and ignore these cbqos_* test subTypes, please review the following steps:

  • On the DGE(x) directly monitoring the device in question, please create the file device.exclude under <TRAVERSE_HOME>\etc\typedef (i.e. <TRAVERSE_HOME>\etc\typedef\device.exclude)
  • Within the file simply add the following lines

snmp/cbqos_policy_traffic_before
snmp/cbqos_policy_traffic_after
snmp/cbqos_policy_traffic_dropped
snmp/cbqos_policy_pkts_before
snmp/cbqos_policy_pkts_dropped
snmp/cbqos_policy_pkts_nobuf
snmp/cportqos_enqueue
snmp/cportqos_drop

Once the file is in place with those snmp test subType entries, please run another discovery using 'Create New Standard Tests > snmp monitor'. If you are able to discover the tests you need, you may subsequently delete the device.exclude file.

An alternate solution is to use the Bulk Provisioning tool (TRAVERSE_HOME\utils\provisionDevices.pl) described in the KB article 'https://kaseya.zendesk.com/entries/100802693'

Note: The bulk provisioning script must be run from the DGE or DGE extension where the devices will be monitored. The script requires that the BVE API component is running on the BVE server and that there be connectivity between the same DGE or DGE extension server and the BVE server (port 7661) in order to create the devices and tests.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.