CISCO-NMS-APPL-HEALTH-MIB
The CISCO-NMS-APPL-HEALTH-MIB monitors the runtime state and health status of Cisco Network Management System (NMS) applications, specifically tracking lifecycle events such as start, stop, failure, and abnormal exits to generate SNMP notifications for Operations Support Systems.
Imported Objects
Objects
18 total| Object Name |
|---|
ciscoNmsApplHealthMIBThis 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. MODULE-IDENTITY .1.3.6.1.4.1.9.9.237 |
ciscoNmsApplHealthNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.237.0 |
cnaHealthNotifThis notification is sent out to notify normal startup, shutdown,
intermediate health/status (ex: busy etc.), failed or exit status. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.237.0.1 |
ciscoNmsApplHealthMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.237.1 |
cnaHealthObj OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.237.1.1 |
cnaHealthNotifSeqNumThe value of this object indicates the sequence number of
notifications in order for the NMS/OSS to detect missing
notification(s).ro Counter32 .1.3.6.1.4.1.9.9.237.1.1.1 |
cnaHealthTableA table of information about the health of one or more
Cisco NMS application(s). SEQUENCE OF CnaHealthTableEntry .1.3.6.1.4.1.9.9.237.1.1.2 |
cnaHealthTableEntryEntries appear in this table for each possible alarm state. CnaHealthTableEntry .1.3.6.1.4.1.9.9.237.1.1.2.1 |
cnaHealthTableIndexThis acts as the index to the cnaHealthTable.ro Unsigned32 .1.3.6.1.4.1.9.9.237.1.1.2.1.1 |
cnaHealthStatusChangeTimeThe time when a change in the health status of Cisco NMS
Application occurs.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.237.1.1.2.1.2 |
cnaHealthNameThe value of this object indicates the name of the NMS application,
the notification is about.ro SnmpAdminString .1.3.6.1.4.1.9.9.237.1.1.2.1.3 |
cnaHealthStatusThe 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 loggingro Enumeration .1.3.6.1.4.1.9.9.237.1.1.2.1.4 |
cnaHealthSevLevelIndicates the severity level of the cna health status Notifications.ro CiscoAlarmSeverity (CISCO-TC) .1.3.6.1.4.1.9.9.237.1.1.2.1.5 |
cnaHealthComLineArgsThe value of this object indicates the command-line arguments of
the NMS application being reported about in the notifications.ro SnmpAdminString .1.3.6.1.4.1.9.9.237.1.1.2.1.6 |
cnaHealthStatusDescThe 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.ro SnmpAdminString .1.3.6.1.4.1.9.9.237.1.1.2.1.7 |
ciscoNmsApplHealthMIBConforms OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.237.2 |
cnaHealthMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.237.2.1 |
cnaHealthMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.237.2.2 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.