CISCO-NMS-APPL-HEALTH-MIB

All MIBs › CISCO-NMS-APPL-HEALTH-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2019-09-03

Category: Cisco Devices, Device Management, Network Monitoring (RMON)

Description: Tracks the health and availability of Cisco NMS application components, including process and service status.

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 CISCO-NMS-APPL-HEALTH-MIB?

CISCO-NMS-APPL-HEALTH-MIB defines health-status notifications and objects for Cisco Network Management System (NMS) application components themselves, informing an upstream OSS/NMS when a managed application starts, stops, fails, or becomes busy. It belongs to the software/application-health monitoring area within Cisco's management-station ecosystem, rather than device hardware management. Its data is explicitly software-status focused: cnaHealthStatus and cnaHealthSevLevel report the current state and severity of a monitored NMS application/process, cnaHealthUpTime tracks how long that application component has been running, and cnahPerformanceTable adds performance metrics for the monitored process—together giving a direct process/service-status monitoring capability analogous to hardware health monitoring but for software components. cnaHealthComLineArgs and cnaHealthStatusDesc provide diagnostic context (command-line arguments, descriptive status text) for troubleshooting an abnormal exit. This MIB is deployed within Cisco NMS platforms themselves (e.g., management server processes) to let operators monitor the management system's own application health, not the network devices it manages, typically after operators download the CISCO-NMS-APPL-HEALTH-MIB file for use in their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-NMS-APPL-HEALTH-MIB. 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

Cisco NMS/OSS management server application

Monitoring Examples

An operations team subscribes to notifications keyed on cnaHealthNotifSeqNum and polls cnaHealthTable/cnaHealthTableEntry for cnaHealthStatus and cnaHealthSevLevel to detect when a critical NMS backend process transitions to a 'failed' state. Checking cnaHealthUpTime alongside cnaHealthStatusDesc reveals whether a process crashed shortly after restart (a crash-loop) versus running stably, guiding whether to escalate to the NMS vendor's support team.

What Can Be Monitored

application/process status (started, stopped, failed, busy)
severity level of health events
application uptime
command-line arguments and status description
application performance metrics

Imported Objects

From CISCO-QOS-PIB-MIB

Percent

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-TC

CiscoAlarmSeverity
CiscoMilliSeconds
TimeIntervalSec

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime

How to Use in IPNetwork Monitor

Example using cnaHealthNotifSeqNum OID:

Select a Cisco NMS/OSS management server as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cnaHealthNotifSeqNum into the Find box to locate it in the OID tree, then select it and click OK. The value of this object indicates the sequence number of notifications in order for the NMS/OSS to detect missing notification(s). On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoNmsApplHealthMIB	1.3.6.1.4.1.9.9.237			This MIB defines Cisco NMS Application (cna) Health Status Notifications and the related objects. These notifications will be sent to the OSS/NMS to inform them about the NMS application status (started, stopped, failed, busy etc.) or any abnormal exit of applications.
ciscoNmsApplHealthNotifs	1.3.6.1.4.1.9.9.237.0
NTF cnaHealthNotif	1.3.6.1.4.1.9.9.237.0.1			This notification is sent out to notify normal startup, shutdown, intermediate health/status (ex: busy etc.), failed or exit status.
ciscoNmsApplHealthMIBObjects	1.3.6.1.4.1.9.9.237.1
cnaHealthObj	1.3.6.1.4.1.9.9.237.1.1
C32 cnaHealthNotifSeqNumEx	1.3.6.1.4.1.9.9.237.1.1.1	Counter32	read-only	The value of this object indicates the sequence number of notifications in order for the NMS/OSS to detect missing notification(s).
cnaHealthTable	1.3.6.1.4.1.9.9.237.1.1.2		not-accessible	A table of information about the health of one or more Cisco NMS application(s).
cnaHealthTableEntry	1.3.6.1.4.1.9.9.237.1.1.2.1		not-accessible	Entries appear in this table for each possible alarm state.
U32 cnaHealthTableIndex	1.3.6.1.4.1.9.9.237.1.1.2.1.1	Unsigned32	read-only	This acts as the index to the cnaHealthTable.
DAT cnaHealthStatusChangeTime	1.3.6.1.4.1.9.9.237.1.1.2.1.2	DateAndTime	read-only	The time when a change in the health status of Cisco NMS Application occurs.
STR cnaHealthName	1.3.6.1.4.1.9.9.237.1.1.2.1.3	SnmpAdminString	read-only	The value of this object indicates the name of the NMS application, the notification is about.
INT cnaHealthStatus	1.3.6.1.4.1.9.9.237.1.1.2.1.4	INTEGER	read-only	The value of this object indicates the health/status of the NMS application, the notification is reporting about. The possible values are: started(1) : started & initialized successfully stopped(2) : stopped successfully busy(3) : not able to respond to any request from health monitor until the status changed to started failed(4) : upon detecting error condition, logged and exited exited(5) : abnormally exited without logging
CIS cnaHealthSevLevel	1.3.6.1.4.1.9.9.237.1.1.2.1.5	CiscoAlarmSeverity	read-only	Indicates the severity level of the cna health status Notifications.
STR cnaHealthComLineArgs	1.3.6.1.4.1.9.9.237.1.1.2.1.6	SnmpAdminString	read-only	The value of this object indicates the command-line arguments of the NMS application being reported about in the notifications.
STR cnaHealthStatusDesc	1.3.6.1.4.1.9.9.237.1.1.2.1.7	SnmpAdminString	read-only	The value of this object gives a detailed description of the health/status of the application being reported in a notification. In case of failed(4) status, this field must indicate the error description. For any other cnaStatus, this field may contain a description to qualify the cnaStatus, like 'Started & initialized succesfully' or an empty string.
NUM cnaHealthUpTime	1.3.6.1.4.1.9.9.237.1.1.2.1.8	TimeIntervalSec	read-only	The time (in seconds) since the entire application was last re-initialized as a result of restart.
cnahPerformanceTable	1.3.6.1.4.1.9.9.237.1.1.3		not-accessible	A table of information about the performance of one or more Cisco NMS application(s).
cnahPerformanceEntry	1.3.6.1.4.1.9.9.237.1.1.3.1		not-accessible	Performance information about one Cisco NMS application.
PER cnahPerfCpuUtilization	1.3.6.1.4.1.9.9.237.1.1.3.1.1	Percent	read-only	The CPU utilization of the application.
PER cnahPerfMemoryUtilization	1.3.6.1.4.1.9.9.237.1.1.3.1.2	Percent	read-only	The memory utilization of the application.
CIS cnahPerfLatency	1.3.6.1.4.1.9.9.237.1.1.3.1.3	CiscoMilliSeconds	read-only	Network latency of the traffic sending in and out from the application. This is the time interval after which the frames are dropped if they are not delivered in the order they were transmitted.
G32 cnahPerfHeapUsed	1.3.6.1.4.1.9.9.237.1.1.3.1.4	Gauge32	read-only	The snapshot of memory heap used of the application, the sampling interval is agent dependent.
G32 cnahPerfDataIn	1.3.6.1.4.1.9.9.237.1.1.3.1.5	Gauge32	read-only	The snapshot of the number of kilobytes received on the application, the sampling interval is agent dependent.
G32 cnahPerfDataOut	1.3.6.1.4.1.9.9.237.1.1.3.1.6	Gauge32	read-only	The snapshot of the number of kilobytes transmitted out of the application, the sampling interval is agent dependent.
G32 cnahPerfMessageIn	1.3.6.1.4.1.9.9.237.1.1.3.1.7	Gauge32	read-only	The snapshot of the number of messages received on the application from the network, the sampling interval is agent dependent.
G32 cnahPerfMessageOut	1.3.6.1.4.1.9.9.237.1.1.3.1.8	Gauge32	read-only	The snapshot of the number of messages transmitted out of the application to the network, the sampling interval is agent dependent.
G32 cnahPerfDiskRead	1.3.6.1.4.1.9.9.237.1.1.3.1.9	Gauge32	read-only	The snapshot of the number of kilobytes read by the application from the local storage, the sampling interval is agent dependent.
G32 cnahPerfDiskWrite	1.3.6.1.4.1.9.9.237.1.1.3.1.10	Gauge32	read-only	The snapshot of the number of kilobytes written by the application to the local storage, the sampling interval is agent dependent.
PER cnahPerfDiskUsage	1.3.6.1.4.1.9.9.237.1.1.3.1.11	Percent	read-only	The snapshot of the usage of local storage used by the application, the sampling interval is agent dependent.
G32 cnahPerfDiskTotal	1.3.6.1.4.1.9.9.237.1.1.3.1.12	Gauge32	read-only	The snapshot of the total local storage used by the application, the sampling interval is agent dependent.
ciscoNmsApplHealthMIBConforms	1.3.6.1.4.1.9.9.237.2
cnaHealthMIBCompliances	1.3.6.1.4.1.9.9.237.2.1
cnaHealthMIBCompliance	1.3.6.1.4.1.9.9.237.2.1.1			The compliance statement for entities which implement (1..4294967295)thc Cisco NMS Application Health Monitor MIB.
cnaHealthMIBCompliance2	1.3.6.1.4.1.9.9.237.2.1.2			The compliance statement for entities which implement the Cisco NMS Application Health Monitor MIB.
cnaHealthMIBGroups	1.3.6.1.4.1.9.9.237.2.2
cnaHealthMIBGroup	1.3.6.1.4.1.9.9.237.2.2.1			A collection of objects providing Cisco NMS Application normal health info
cnaHealthNotifGroup	1.3.6.1.4.1.9.9.237.2.2.2			The set of notification events a Cisco NMS application supports.
cnaHealthMIBGroup2	1.3.6.1.4.1.9.9.237.2.2.3			A collection of objects providing Cisco NMS Application uptime information.
cnahPerformanceGroup	1.3.6.1.4.1.9.9.237.2.2.4			A collection of objects providing Cisco NMS Application performance information.

RFC description

Monitors health and availability of Cisco NMS application components including process and service status.

Start monitoring Cisco NMS/OSS management servers 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 CISCO-NMS-APPL-HEALTH-MIB