DiagnosticsMonitor

All MIBs › DiagnosticsMonitor

Category: Domain: System Management

Description: Diagnostics monitoring MIB providing objects for triggering and retrieving diagnostic tests and health check results.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is DiagnosticsMonitor?

DiagnosticsMonitor (part of the Concord/NetHealth "netHealthMib" enterprise tree) is a network-management vendor schema used by Concord Communications' NetHealth application to represent diagnostic test triggers and exception/health-check results for monitored network elements. It exposes objects identifying the managed element being diagnosed (nhElementIp, nhElementName, nhElementId), the diagnostic/monitoring server issuing the check (nhServerIp, nhServerName, nhServerPort), and exception details (nhExceptionType, nhVariable, nhSeverity, nhStartTime, nhGroup/nhGroupList). Its core purpose is fault/health-status monitoring: it lets an NMS retrieve which diagnostic exception occurred, its severity, the specific metric that triggered it, and when it started, effectively surfacing software/hardware health-check failures across whatever devices NetHealth is polling. As a Concord NetHealth-specific schema it depends on data collected from other MIBs (interfaces, system, vendor-specific health MIBs) that NetHealth itself polls and correlates into these diagnostic events. It is deployed as part of the Concord NetHealth network performance/availability management platform, monitoring a variety of network element types on behalf of NOC operators. Network engineers evaluating or troubleshooting this functionality can download the DiagnosticsMonitor file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in DiagnosticsMonitor. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Concord NetHealth diagnostic/monitoring platform
any network element polled by NetHealth (routers, switches, servers) -- not tied to one manufacturer

Monitoring Examples

An operator would poll the diagnostic exception objects for a monitored element (identified by nhElementIp/nhElementName/nhElementId) -- nhExceptionType and nhSeverity reveal the nature and criticality of a detected problem, nhVariable identifies which underlying metric triggered it, and nhStartTime shows when the condition began, letting the NOC correlate a NetHealth-raised alarm (grouped via nhGroup/nhGroupList) back to a specific failing element and metric.

What Can Be Monitored

diagnostic exception type
exception severity
triggering variable/metric
exception start time
monitored element identity (IP/name/ID)
diagnostic server identity

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

IpAddress
enterprises

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
concord	1.3.6.1.4.1.149
NTF netHealthInfo	1.3.6.1.4.1.149.0.15			An event (not an error) has occurred in Network Health. This trap is an informational message from the Network Health Diagnostic Monitor. No action is required.
NTF netHealthWarning	1.3.6.1.4.1.149.0.16			An error has occurred in Network Health. Polling will continue, please investigate as soon as possible. This trap is sent from the Network Health Diagnostic Monitor.
NTF netHealthReset	1.3.6.1.4.1.149.0.17			A system critical error has occurred in Network Health. Polling may not occur. Restart the Network Health servers as soon as possible. This trap is sent from the Network Health Diagnostic Monitor.
NTF netHealthUrgent	1.3.6.1.4.1.149.0.18			A system critical error has occurred in Network Health. Polling may not occur. System administrator intervention is required. This trap is sent from the Network Health Diagnostic Monitor.
NTF netHealthException	1.3.6.1.4.1.149.0.19			A scheduled Network Health report has detected one or more health exceptions for an element.
NTF nhLiveException	1.3.6.1.4.1.149.0.20			A Network Health exception has occurred. This trap sends generic information about an exception when it first becomes active.
NTF nhLiveAlarm	1.3.6.1.4.1.149.0.21			A Network Health alarm has occurred. This trap sends detailed information about an alarm.
NTF nhLiveClearException	1.3.6.1.4.1.149.0.22			A Network Health exception has been cleared. The conditions causing the corresponding exception no longer exist.
NTF nhLiveClearAlarm	1.3.6.1.4.1.149.0.23			A Network Health alarm has been cleared. The conditions causing the corresponding alarm no longer exist.
NTF nhLiveUpdateException	1.3.6.1.4.1.149.0.24			The severity of a Network Health exception has changed.
NTF nhLiveResetExceptions	1.3.6.1.4.1.149.0.25			The LiveExceptions server has restarted. All LiveExceptions alarms and exceptions sent before this time will NOT be cleared automatically. All trap destinations should reset any pre-existing Network Health exceptions and alarms by setting them to a clear state or unhighlighting any icons.
netHealth	1.3.6.1.4.1.149.2
netHealthMib	1.3.6.1.4.1.149.2.1
nhdTraps	1.3.6.1.4.1.149.2.1.1
nhdServer	1.3.6.1.4.1.149.2.1.1.1
IP nhdServerIp	1.3.6.1.4.1.149.2.1.1.1.1	IpAddress	read-only	This object is the IP address of the element that has the exception.
OCT nhdServerName	1.3.6.1.4.1.149.2.1.1.1.2	OCTET STRING	read-only	This object is the name of the element that has the exception.
nhdError	1.3.6.1.4.1.149.2.1.1.2
OCT nhdErrorDate	1.3.6.1.4.1.149.2.1.1.2.1	OCTET STRING	read-only	This object is the date the exception occurred.
OCT nhdErrorTime	1.3.6.1.4.1.149.2.1.1.2.2	OCTET STRING	read-only	This object is the time the exception occurred.
OCT nhdErrorCode	1.3.6.1.4.1.149.2.1.1.2.3	OCTET STRING	read-only	This object is the variable that has caused the exception.
OCT nhdErrorMessage	1.3.6.1.4.1.149.2.1.1.2.5	OCTET STRING	read-only	This object describes the reason for the exception.
nhSysInfo	1.3.6.1.4.1.149.2.2
IP nhServerIp	1.3.6.1.4.1.149.2.2.1	IpAddress	read-only	This object specifies the IP address of the Network Health server.
STR nhServerName	1.3.6.1.4.1.149.2.2.2	DisplayString	read-only	This object specifies the name of the Network Health server.
INT nhServerPort	1.3.6.1.4.1.149.2.2.3	INTEGER	read-only	This object specifies the port number of the Network Health server.
nhArgs	1.3.6.1.4.1.149.2.3
IP nhElementIp	1.3.6.1.4.1.149.2.3.1	IpAddress	read-only	This object specifies the IP address of a Network Health element.
STR nhElementName	1.3.6.1.4.1.149.2.3.2	DisplayString	read-only	This object specifies the name of a Network Health element.
INT nhElementId	1.3.6.1.4.1.149.2.3.3	INTEGER	read-only	This object specifies the database identifier of a Network Health element.
INT nhStartTime	1.3.6.1.4.1.149.2.3.4	INTEGER	read-only	This object is the UTC time that the exception or alarm was detected by LiveExceptions.
STR nhExceptionType	1.3.6.1.4.1.149.2.3.5	DisplayString	read-only	This object specifies the algorithm(s) used to detect the alarm. They could include Time Over Threshold, Deviation From Normal, Dynamic Threshold, Availability < 100% and Reachability < 100%.
STR nhVariable	1.3.6.1.4.1.149.2.3.6	DisplayString	read-only	This object defines the variable(s) used in the rule that created the alarm.
INT nhSeverity	1.3.6.1.4.1.149.2.3.7	INTEGER	read-only	This object is the severity level of the alarm. The user can view/modify the severity of a rule in the LiveExceptions Rule Editor.
STR nhGroup	1.3.6.1.4.1.149.2.3.8	DisplayString	read-only	This object defines the group that LiveExceptions is monitoring and that contains the element that has an alarm or exception. This object value will be blank if LiveExceptions is monitoring a group list.
STR nhGroupList	1.3.6.1.4.1.149.2.3.9	DisplayString	read-only	This object defines the group list that LiveExceptions is monitoring and that contains the element that has an alarm or exception. This object value will be blank if LiveExceptions is monitoring a group.
STR nhDisplayStr	1.3.6.1.4.1.149.2.3.10	DisplayString	read-only	This object describes the rule which triggered the alarm. This field is blank for exceptions. The Rule Message can be viewed/modified in the LiveExceptions Rule Editor.
INT nhExceptionId	1.3.6.1.4.1.149.2.3.11	INTEGER	read-only	This object defines a unique ID for the exception (Profile ID) or the alarm (Alarm ID). It is used to run Network Health reports.
STR nhTechType	1.3.6.1.4.1.149.2.3.12	DisplayString	read-only	This object defines the technology type of the group or group list.
INT nhResetTime	1.3.6.1.4.1.149.2.3.13	INTEGER	read-only	This object is the UTC time that the LiveExceptions server started.
STR nhProfile	1.3.6.1.4.1.149.2.3.14	DisplayString	read-only	This object is the name of the profile for this alarm or exception.
INT nhProblemStartTime	1.3.6.1.4.1.149.2.3.15	INTEGER	read-only	This object is the UTC time when the threshold was first crossed and that later resulted in an alarm or exception for that element.
INT nhProblemDuration	1.3.6.1.4.1.149.2.3.16	INTEGER	read-only	This object is the amount of time (in seconds) spent over the threshold since the problem start time (the time the threshold was first crossed).

RFC description

Monitors network health diagnostics with exception traps and performance reports from Concord systems.

Start monitoring Concord NetHealth diagnostic/monitoring platform (polled network elements) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download DiagnosticsMonitor

What Is DiagnosticsMonitor?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description