Point fails to load

The following are the most common reasons why the interface fails to load a point into its list of points to service.

Cannot Translate OID

Before sending a request to a network device, the interface translates textual OIDs (for example, system.sysUptime.0) into their numeric format (for example, .1.3.6.1.2.1.1.3.0). If it cannot do so, it prints the out a message such as the following:

The interface - 1> Cannot translate OID: interfaces.ifTable.ifEntry.ifInOctects.3;
cannot add Tag: router_ rx_Ethernet0/0

Make sure that the spelling of the OID is correct. In the above example, ifInOctects is a misspelling of ifInOctets. Note that some SNMP tools display OIDs incorrectly, for example, omitting the final zero.

Confirm that the directory where the PI Interface for SNMP program is located contains a mibs directory containing MIB definition files. If it does not, messages such as the following appear:

Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (IF MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
Cannot find module (UDP-MIB): At line 0 in (none)
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (SNMPv2-SMI): At line 0 in (none)

Matching community string not found in pisnmp#.pwd

If pwd or enc appear in the startup command line, the interface looks in either the pisnmp#.pwd or pisnmp#.enc file for a matching device name. The interface needs to find either a community string or a set of SNMPv3 security attributes that correspond to the given device name specified in the PI point's instrumenttag attribute.

OID field not found

The interface requires an OID specification in the instrumenttag or exdesc attribute.

Host not found

The interface requires the host parameter to be specified in a point's instrumenttag attribute.

OID not valid

If the interface cannot translate a textual OID into its numeric form, it does not load the point.