EZ5 MIB Catalog

CISCO-NMS-APPL-HEALTH-MIB

2019-09-03

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.

Download CISCO-NMS-APPL-HEALTH-MIB.txt Open CISCO-NMS-APPL-HEALTH-MIB.txt in a new tab

SCALARS (1) · TABLES (2) · TRAPS (1)

Scalars (1)

NameOID
cnaHealthNotifSeqNum1.3.6.1.4.1.9.9.237.1.1.1

Tables (2)

NameOID
cnaHealthTable1.3.6.1.4.1.9.9.237.1.1.2
cnahPerformanceTable1.3.6.1.4.1.9.9.237.1.1.3

Traps (1)

NameOID
cnaHealthNotif1.3.6.1.4.1.9.9.237.0.1

END OF TOC

Scalar details

cnaHealthNotifSeqNum

1.3.6.1.4.1.9.9.237.1.1.1

Counter32

The value of this object indicates the sequence number of notifications in order for the NMS/OSS to detect missing notification(s).

Table details

cnaHealthTable

1.3.6.1.4.1.9.9.237.1.1.2

Index: cnaHealthTableIndex

A table of information about the health of one or more Cisco NMS application(s).

cnaHealthTableIndex

1.3.6.1.4.1.9.9.237.1.1.2.1.1

Unsigned32 (1..4294967295)

This acts as the index to the cnaHealthTable.

cnaHealthStatusChangeTime

1.3.6.1.4.1.9.9.237.1.1.2.1.2

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

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

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..32) · OCTET STRING · hint 255t

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

INTEGER1 = started2 = stopped3 = busy4 = failed5 = exited · Integer32

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

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

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

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

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

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

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.

cnaHealthUpTime

1.3.6.1.4.1.9.9.237.1.1.2.1.8

TimeIntervalSecA period of time, measured in units of 1 second. · Unsigned32 · Seconds

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

Index: cnaHealthTableIndex

A table of information about the performance of one or more Cisco NMS application(s).

cnahPerfCpuUtilization

1.3.6.1.4.1.9.9.237.1.1.3.1.1

PercentAn integer that is in the range of a percent value. (0..100) · Integer32 · %

The CPU utilization of the application.

cnahPerfMemoryUtilization

1.3.6.1.4.1.9.9.237.1.1.3.1.2

PercentAn integer that is in the range of a percent value. (0..100) · Integer32 · %

The memory utilization of the application.

cnahPerfLatency

1.3.6.1.4.1.9.9.237.1.1.3.1.3

CiscoMilliSecondsRepresents time unit value in milliseconds. · Unsigned32 · msec

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.

cnahPerfHeapUsed

1.3.6.1.4.1.9.9.237.1.1.3.1.4

Gauge32 · KBytes

The snapshot of memory heap used of the application, the sampling interval is agent dependent.

cnahPerfDataIn

1.3.6.1.4.1.9.9.237.1.1.3.1.5

Gauge32 · KBytes

The snapshot of the number of kilobytes received on the application, the sampling interval is agent dependent.

cnahPerfDataOut

1.3.6.1.4.1.9.9.237.1.1.3.1.6

Gauge32 · KBytes

The snapshot of the number of kilobytes transmitted out of the application, the sampling interval is agent dependent.

cnahPerfMessageIn

1.3.6.1.4.1.9.9.237.1.1.3.1.7

Gauge32 · messages

The snapshot of the number of messages received on the application from the network, the sampling interval is agent dependent.

cnahPerfMessageOut

1.3.6.1.4.1.9.9.237.1.1.3.1.8

Gauge32 · messages

The snapshot of the number of messages transmitted out of the application to the network, the sampling interval is agent dependent.

cnahPerfDiskRead

1.3.6.1.4.1.9.9.237.1.1.3.1.9

Gauge32 · KBytes

The snapshot of the number of kilobytes read by the application from the local storage, the sampling interval is agent dependent.

cnahPerfDiskWrite

1.3.6.1.4.1.9.9.237.1.1.3.1.10

Gauge32 · KBytes

The snapshot of the number of kilobytes written by the application to the local storage, the sampling interval is agent dependent.

cnahPerfDiskUsage

1.3.6.1.4.1.9.9.237.1.1.3.1.11

PercentAn integer that is in the range of a percent value. (0..100) · Integer32 · %

The snapshot of the usage of local storage used by the application, the sampling interval is agent dependent.

cnahPerfDiskTotal

1.3.6.1.4.1.9.9.237.1.1.3.1.12

Gauge32 · KBytes

The snapshot of the total local storage used by the application, the sampling interval is agent dependent.

Trap details

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.

cnaHealthNotifSeqNum

1.3.6.1.4.1.9.9.237.1.1.1

Counter32

The value of this object indicates the sequence number of notifications in order for the NMS/OSS to detect missing notification(s).

cnaHealthStatusChangeTime

1.3.6.1.4.1.9.9.237.1.1.2.1.2

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

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

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..32) · OCTET STRING · hint 255t

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

INTEGER1 = started2 = stopped3 = busy4 = failed5 = exited · Integer32

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

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

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

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

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

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

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.

↑ To TOC