Monitoring complex instances of the SNMP counters

Sometimes the SNMP counter identifier is placed in a different table than a counter. NetCrunch 10.5 introduced a new way of monitoring such complex instances.

Scenario

Table Memory Allocated (cpmProcessExtEntry.cpmProcExtMemAllocated; OID: 1.3.6.1.4.1.9.9.109.1.2.2.1.1) is one of the tables that contains names of the processes that allocate memory in a completely different table (cpmProcessEntry.cpmProcessName; OID: 1.3.6.1.4.1.9.9.109.1.2.1.1.2)

Reading such a table without the possibility of joining names with ID's is difficult and it takes a lot of time to get to know which number represents which process.

Adding counter

Joining two columns is really simple, the only requirement is that the index of the rows in both tables must be the same.

Based on the example above we will create counters with values from one column and names from the other.

(Please note that you need Cisco device to follow steps below if you don't have such device you can try to find different oid's that represent the same scenario)

1. Open node settings of your cisco device and click on Custom tile under SNMP section
2. Switch to data collectors and click on Add Collector
3. Switch to Status tab and double-click on
4. Set a name and click on Add counter
5. Paste OID (1.3.6.1.4.1.9.9.109.1.2.2.1.1) and click next
6. If your device has such counters - you should be able to see values right away The only problem is Keys which are represented as numbers
7. Click on Key Column drop down menu, scroll to the bottom and select
8. Click on Select from MIB button, after MIB browser is loaded paste 1.3.6.1.4.1.9.9.109.1.2.1.1.2 in the search box. Double-click on result
9. After the table is read, you should see the proper names of the Keys, the last thing to do is select which of the rows should be monitored (Selectable from Rows drop down)
10. Save everything - new counter should appear as monitored on the node (depends on monitoring time)

Result

Such a scenario can be added as an individual counter for a node or monitoring pack - it can be set as a collector or alert.

This feature requires NetCrunch version 10.5 or newer

snmpsnmp counterssnmp monitoring