4.4. Report

Every time NSG server generates monitoring variables for a device, it creates a report that you can find in the UI if click “Reports” in the navigation bar.

The report lists monitoring variables and corresponding OIDs that will be polled on the device, as well as some summary information. It looks like this:

Monitoring variables collected from device router1.rd

Report generated 2015-08-29T13:10:39.887-07:00

Total number of OIDs for this device: 2385
Number of queries for this device: (max 30 OIDs per query, max PDU payload size 480 bytes): 86

-------------------------------------------------------------------

bgpPeerAdminStatus (category 'Protocol'): total 8 instances
-----------------------------------------------------------------
bgpPeerAdminStatus.76.174285569          | AS36323 10.99.99.1   |  INTEGER | 1.3.6.1.2.1.15.3.1.3.10.99.99.1
bgpPeerAdminStatus.76.174285570          | AS36323 10.99.99.2   |  INTEGER | 1.3.6.1.2.1.15.3.1.3.10.99.99.2
bgpPeerAdminStatus.76.174285571          | AS36323 10.99.99.3   |  INTEGER | 1.3.6.1.2.1.15.3.1.3.10.99.99.3
bgpPeerAdminStatus.76.174285572          | AS36323 10.99.99.4   |  INTEGER | 1.3.6.1.2.1.15.3.1.3.10.99.99.4

At the bottom of the report you can find actual batch queries that will be sent to the device. Sometimes the order and number of OIDs in a batch query is important and this part of the report can be used to troubleshoot certain class of problems with SNMP polling of the device. Lists of OIDs in the example below have been truncated to make them fit on the page:

Batch queries:
Batch    0: [1.3.6.1.2.1.1.3.0, 1.3.6.1.2.1.2.2.1.5.33, 1.3.6.1.2.1.2.2.1.5.34, 1.3.6.1.2.1.2.2.1.5.35, ( and more ... )
Batch    1: [1.3.6.1.2.1.2.2.1.5.241, 1.3.6.1.2.1.2.2.1.5.244, 1.3.6.1.2.1.2.2.1.5.245, 1.3.6.1.2.1.2.2.1.5.246,