Simple Network Management Protocol Object Identifiers
The aim of this blog is to briefly define what simple network management protocol object identifiers are, and how these are utilized by Statseeker’s network monitoring software. This will be done by describing the default objects which are monitored, as well as the additional new features which were added to Statseeker Version 4.0. These new features include the ability to monitor additional simple network management protocol object identifiers, and a new reporting feature which enables a user greater flexibility in defining what they want to view.
Firstly, a number of terms will be defined. What is SNMP? SNMP is the acronym for Simple Network Management Protocol. This protocol is used by network devices (SNMP agent) and network management software as a way to communicate with each other to configure or report on various performance metrics. What is an SNMP OID? An SNMP OID is an Object Identifier which is defined within SNMP and identifies a metric or configuration item on a network device. The way network management software knows what is accessible on each network device (SNMP agent) is by what is defined within the SNMP OIDs in a SNMP MIB (Management Information Base). These MIBs define what each OID consists of (eg. whether they are read-only/read-write and what type of variable they are (counters, gauges, timeticks, strings, etc.), as well as defining the structures (eg. MIB tables). For further information, view the Wikipedia definition of Simple Network Management Protocol.
Statseeker has predominantly focused on SNMP monitoring of network interface metrics whilst also including device generic metrics like Filesystem, CPU, Temperature, and Memory details. Below is a list of default SNMP MIBs/Tables/OIDs which are used by Statseeker’s default SNMP monitoring configuration:
|MIB||SNMP Tables/SNMP OIDs|
|ALCATEL-IND1-HEALTH-MIB||healthDeviceCpu1MinAvg, healthDeviceInfo, healthDeviceMemory1MinAvg, healthDeviceTemperatureChasLatest|
|CISCO-ENHANCED-MEMPOOL-MIB||cempMemPoolFree, cempMemPoolName, cempMemPoolTable, cempMemPoolUsed|
|CISCO-ENVMON-MIB||ciscoEnvMonMIB, ciscoEnvMonTemperatureState, ciscoEnvMonTemperatureStatusDescr, ciscoEnvMonTemperatureStatusValue|
|CISCO-MEMORY-POOL-MIB||ciscoMemoryPoolFree, ciscoMemoryPoolMIB, ciscoMemoryPoolName, ciscoMemoryPoolUsed|
|CISCO-PROCESS-MIB||cpmCPUMemoryFree, cpmCPUMemoryUsed, cpmCPUTotal1min, cpmCPUTotal1minRev, cpmCPUTotalTable|
|CISCO-RTTMON-MIB||ciscoRttMonMIB, rttMonCtrlAdminFrequency, rttMonCtrlAdminOwner, rttMonCtrlAdminRttType, rttMonCtrlAdminStatus, rttMonCtrlAdminTag, rttMonCtrlAdminThreshold, rttMonCtrlAdminTimeout, rttMonEchoAdminProtocol, rttMonLatestRttOperCompletionTime|
|CISCO-STACK-MIB||portIfIndex, portIfIndex, portName,portName|
|EtherLike-MIB||dot3StatsDuplexStatus, dot3StatsIndex, dot3StatsTable|
|FOUNDRY-SN-AGENT-MIB||snAgentCpuUtilValue, snAgentGbl, snAgentTempSensorDescr, snAgentTempTable, snAgentTempValue, snAgGblCpuUtil1MinAvg, snAgGblDynMemFree, snAgGblDynMemTotal, snAgGblDynMemUtil, snChasActualTemperature|
|FRAME-RELAY-DTE-MIB||frCircuitCommittedBurst, frCircuitDiscards, frCircuitDlci, frCircuitExcessBurst, frCircuitIfIndex, frCircuitLogicalIfIndex, frCircuitReceivedBECNs, frCircuitReceivedDEs, frCircuitReceivedFECNs, frCircuitReceivedFrames, frCircuitReceivedOctets, frCircuitSentDEs, frCircuitSentFrames, frCircuitSentOctets, frCircuitState, frCircuitTable, frCircuitThroughput|
|HOST-RESOURCES-MIB||hrDevice, hrDeviceDescr, hrDeviceType, hrMemorySize, hrProcessorLoad, hrStorage, hrStorageAllocationUnits, hrStorageDescr, hrStorageSize, hrStorageType, hrStorageUsed|
|HOST-RESOURCES-TYPES||hrDeviceProcessor, hrFSBerkeleyFFS, hrFSLinuxExt2, hrFSNTFS, hrStorageFixedDisk, hrStorageRam, hrStorageVirtualMemory|
|IF-MIB||ifAdminStatus, ifAlias, ifDescr, ifHCInBroadcastPkts, ifHCInMulticastPkts, ifHCInOctets, ifHCInUcastPkts, ifHCOutBroadcastPkts, ifHCOutMulticastPkts, ifHCOutOctets, ifHCOutUcastPkts, ifHighSpeed, ifInBroadcastPkts, ifIndex, ifInDiscards, ifInErrors, ifInMulticastPkts, ifInNUcastPkts, ifInOctets, ifInUcastPkts, ifName, ifOperStatus, ifOutBroadcastPkts, ifOutDiscards, ifOutErrors, ifOutMulticastPkts, ifOutNUcastPkts, ifOutOctets, ifOutUcastPkts, ifPhysAddress, ifSpeed, ifTable, ifType, ifXTable|
|JUNIPER-MIB||jnxOperatingBuffer, jnxOperatingCPU, jnxOperatingDescr, jnxOperatingDRAMSize, jnxOperatingTable, jnxOperatingTemp|
|NETSCREEN-RESOURCE-MIB||nsResCpuLast1Min, nsResMemAllocate, nsResMemLeft|
|NETSWITCH-MIB||hpGlobalMemEntry, hpGlobalMemFreeBytes, hpGlobalMemTotalBytes|
|PowerNet-MIB||apc, memSensorsTemperature, upsAdvBatteryActualVoltage, upsAdvBatteryCapacity, upsAdvBatteryCurrent, upsAdvBatteryReplaceIndicator, upsAdvInputLineVoltage, upsAdvOutputCurrent, upsAdvOutputVoltage, upsPhaseInputCurrent, upsPhaseInputVoltage, upsPhaseOutputCurrent, upsPhaseOutputVoltage|
|Printer-MIB||printmib, prtGeneralPrinterName, prtGeneralSerialNumber, prtMarkerSuppliesLevel, prtMarkerSuppliesMaxCapacity|
|SNMPv2-MIB||sysContact, sysDescr, sysLocation, sysName, sysObjectID, sysServices, system,sysUpTime|
|UPS-MIB||upsBatteryCurrent, upsBatteryStatus, upsBatteryVoltage, upsEstimatedChargeRemaining, upsInputCurrent, upsInputVoltage, upsMIB, upsOutputCurrent, upsOutputSource, upsOutputVoltage|
Statseeker Version 4.0 introduced some exciting new features, one of which provides the ability to add additional SNMP MIBs/OIDs and reports to the product so that they can be monitored and reported on. Statseeker has defined and called this new feature Custom Data Types (CDTs). These CDTs are added into the product by utilizing Statseeker’s existing Custom Script (SCS) mechanism. Since Statseeker Version 4.0 was released, more than a dozen CDTs have been created and made available for general download. These include BGP Peer, Checkpoint Firewall, Ubiquiti M5 Wireless AP, Cisco class-based QoS and many more. View the full list of Custom Data Files available for download.
As these new data types are defined as outside Statseeker’s original licensing structure, a new license mechanism has been introduced to cater for these new data types. This new license type is called an “Entity” license. The entity license is similar to the interface license, where 1 entity license is used for each entry within that data type. (eg. all SNMP OIDs which relate to a single instance of the defined data type).
Once a CDT has been downloaded and installed, Statseeker will need to be configured to discover them. This is achieved by defining IP Address range scopes to be discovered via the “Custom Data Ranges” user interface within the “Administration Tool”. In addition, you can use the auto grouping rules to enable or disable polling of Custom Data Types, which provides the user with some level of control. Once these custom data ranges have been defined, discovery is run as per Statseeker’s normal discovery mechanism. The custom data ranges and auto grouping polling rules can be used to further control your entity license usage. Full details on how this is done is described in the Version 4.0 Custom Data Types Guide.
Within each Custom Data Type SCS package is a set of default reporting configurations. These enable reports to be generated shortly after a discovery has run without creating customized personalized reports. These reports highlight the actual SNMP data that can be reported on within the CDT. These reports can then be personalized to include more or less data via the new “Custom Reporting Console” interface. This new Custom Reporting Console provides more flexibility for the user in terms of what data they need displayed based on their reporting requirements. Further information about the Custom Reporting Console can be found in the Version 4.0 Custom Reporting Guide.
These features include:
- Generating Tabular or Graph Reports
- Filtering based on entity, device, group, entity attribute, and time
- When displaying timeseries data, different time filters can be used apart from the global setting
- Timeseries data can have total, average, minimum, maximum, as well as strip charts displayed in columns
- Each cell in a tabular report can be configured to drilldown to another report within Statseeker, or even another product/tool
- Multiple data types can be configured to be displayed on a single graph
Statseeker’s CDT library is being continually updated and expanded. However, if there is an additional requirement, Statseeker has a structured process for adding new or adjusting existing CDTs. This structured process is defined as a “Custom Data Request” (CDR), which is currently managed via logging a support case using our Technical Support request form.
To aid us in implementing these new CDTs or adjusting existing CDTs, we require the following information:
- SNMP MIB
- What SNMP OIDs are required to be monitored?
- Polling frequency that is required for new SNMP OIDs
- SNMP Walks from devices which support this SNMP MIB
As a company we always strive to improve and add value for our customers and would appreciate any feedback you may have. If you have any suggestions or feedback please contact our Customer Satisfaction team.
Thoughts? Can you see the benefits of simple network management protocol object identifiers utilized by Statseeker’s network monitoring software? Share your thoughts with us in the comments below.