cisco-nms-appl-health-mib.mib object
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2025 can import MIB file cisco-nms-appl-health-mib and use it to monitor vendor specific OID's.
cisco-nms-appl-health-mib file content
Object view of cisco-nms-appl-health-mib:
| Scalar Object |
| cnaHealthNotifSeqNum |
.1.3.6.1.4.1.9.9.237.1.1.1 |
|
The value of this object indicates the sequence number of
notifications in order for the NMS/OSS to detect missing
notification(s).
|
| cnaHealthTableEntry |
.1.3.6.1.4.1.9.9.237.1.1.2.1 |
|
Entries appear in this table for each possible alarm state.
|
| Tabular Object |
| cnaHealthTableIndex |
.1.3.6.1.4.1.9.9.237.1.1.2.1.1 |
|
This acts as the index to the cnaHealthTable.
|
| cnaHealthStatusChangeTime |
.1.3.6.1.4.1.9.9.237.1.1.2.1.2 |
|
The time when a change in the health status of Cisco NMS
Application occurs.
|
| cnaHealthName |
.1.3.6.1.4.1.9.9.237.1.1.2.1.3 |
|
The value of this object indicates the name of the NMS application,
the notification is about.
|
| cnaHealthStatus |
.1.3.6.1.4.1.9.9.237.1.1.2.1.4 |
|
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
|
| cnaHealthSevLevel |
.1.3.6.1.4.1.9.9.237.1.1.2.1.5 |
|
Indicates the severity level of the cna health status Notifications.
|
| cnaHealthComLineArgs |
.1.3.6.1.4.1.9.9.237.1.1.2.1.6 |
|
The value of this object indicates the command-line arguments of
the NMS application being reported about in the notifications.
|
| cnaHealthStatusDesc |
.1.3.6.1.4.1.9.9.237.1.1.2.1.7 |
|
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.
|
| Table |
| cnaHealthTable |
.1.3.6.1.4.1.9.9.237.1.1.2 |
|
A table of information about the health of one or more
Cisco NMS application(s).
|
| Trap |
| 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.
|
| Object Identifier |
| 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 |
| ciscoNmsApplHealthMIBObjects |
.1.3.6.1.4.1.9.9.237.1 |
| ciscoNmsApplHealthMIBConforms |
.1.3.6.1.4.1.9.9.237.2 |
| cnaHealthObj |
.1.3.6.1.4.1.9.9.237.1.1 |
| cnaHealthMIBCompliances |
.1.3.6.1.4.1.9.9.237.2.1 |
| cnaHealthMIBGroups |
.1.3.6.1.4.1.9.9.237.2.2 |
| Group |
| 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.
|
