Owners Manual

Monitoring Network Availability | Performance Monitoring
OMNM 6.5.2 User Guide 415
SNMP Interfaces
The SNMP Interface Monitor Entity editor supports the following entity types: group, equipment
manager, port and interface. It also supports port and interface filters on groups and equipment
manager objects.
If you check the
Collect from ifXTable checkbox, then OpenManage Network Manager attempts to
fetch attributes from the ifXTable. These attributes are ifHighSpeed, ifHCInOctets,
ifHCInUcastPkts, ifHCOutOctets and ifHCOutUcastPkts. If any of these attributes are not
available, then it fetches from ifTable.
If an interface does not support ifxTable, SNMP get typically retrieves an error and OpenManage
Network Manager uses the ifTable instead. Some ATM ports do not send errors from the ifxTable
oids, so OpenManage Network Manager also uses the ifTable values if ifHighSpeed is 0.
NOTE:
The SNMP V1 protocol does not support 64bit counters located in ifXtable. This means OpenManage
Network Manager monitors only collect performance data from ifTable when a device is discovered
using the SNMP V1 protocol. Best practice: Discover devices using snmpV2c or snmpV3 protocols to
collect performance data located in ifXtable.
Even with this checked, OpenManage Network Manager defaulting to 32-bit counters if 64-bit is
not available.
OpenManage Network Manager now supports multiple indexes in the SNMP Interface monitor.
Specify them in the instance field, separated by dots. For
sfpTxPowerValue
1.3.6.1.4.1.28458.7.2.4.6.7.1.22.Y.Z
, where Y is the slot and Z is the @ifindex,
specify
@slotNumber.@ifIndex as the instance. You can also specify a constant string. For
sonetLineIntervalUASs 1.3.6.1.2.1.10.39.1.3.2.1.5. X.16 Where X is the
@ifindex and 16 is the last record, specify @ifIndex.16 .
The variable name following the “@” must correspond to an attribute in the port or interface bean.