CISCO-OUTAGE-MONITOR-MIB

Unsigned32

An arbitrary non-zero integer value that uniquely identifies a COutageHistoryEntry in the table. The value of this table starts at '1' and monotonically increases for each object failure and recovery event received by the agent. If the value of this object is '4294967295', the agent will reset it to '1' upon receiving the next event.

OutageMonObjectType1 = interface2 = physicalEntity3 = swProcess4 = remoteObject5 = logicalEntityRepresents different monitored object types: interface - this object supports monitoring of both physical and logical interfaces, which is defined in IF-MIB. physicalEntity - this object supports monitoring of physical entities contained by the system, including chassis, slots, modules, ports, power supplies, and fan, which is defined in ENTITY-MIB. swProcess - this object supports monitoring of software processes, which is defined in CISCO-PROCESS-MIB. remoteObject - this object supports monitoring of remote objects including remote customer devices or interfaces. The object is defined by users via CLI configuration. logicalEntity - this object supports monitoring of any logical entities contained by the system, including router device, IOS software on each LC or RP, and CPU utilization object, which can be defined by outage monitoring program. · Integer32

This object specifies the monitored object's type. It comprises interface(1), physicalEntity(2), swProcess(3), remoteObject(4), and logicalEntity(5). The detailed description has been presented above in the OutageMonObjectType definition.

Unsigned32

This object identifies a specific index of the monitored object based upon the cOutageEventObjectType. If it is interface(1), it correlates the object with ifIndex in ifTable in the IF-MIB. If it is physicalEntity(2), it correlates the object with entPhysicalIndex in entPhysicalTable in the ENTITY-MIB. If it is swProcess(3), the value corresponds to an entry in the cOutageCpmMapTable, which correlates the object with cpmCPUTotalIndex and cpmProcessPID in cpmProcessTable in the CISCO-PROCESS-MIB. If it is remoteObject(4), the value corresponds to an entry in the cOutageRemoteObjMapTable, which correlates the object with its ID and description. If it is logicalEntity(5), the value corresponds to an entry in the cOutageLogicalObjMapTable, which correlates the object with the description. It also correlates the event entry with a specific entry in cOutageObjectTable.

Unsigned32

The type of outage related event. The value corresponds to an entry in the cOutageEventTypeMapTable.

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

This object specifies the date and time of the event was generated. The value of sysUpTime, which is reinitialized during the router boot-up, is not sufficient, since it shall be able to measure the outage time of the router failure over the measurement period.

Unsigned32

Object that identifies the time duration between transitions in available state of a component. According to the cOutageEventTypeIndex, If the event type is up, the interval time from the last down time is TTR (Time To Recovery). Otherwise, the interval time from the last up is TTF (Time To Failure).

Unsigned32

This object uniquely identifies an event description.

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..128) · OCTET STRING · hint 255t

The name of the outage related event.

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

This object specifies a human-readable message describing information about the outage related event.

OutageMonObjectType1 = interface2 = physicalEntity3 = swProcess4 = remoteObject5 = logicalEntityRepresents different monitored object types: interface - this object supports monitoring of both physical and logical interfaces, which is defined in IF-MIB. physicalEntity - this object supports monitoring of physical entities contained by the system, including chassis, slots, modules, ports, power supplies, and fan, which is defined in ENTITY-MIB. swProcess - this object supports monitoring of software processes, which is defined in CISCO-PROCESS-MIB. remoteObject - this object supports monitoring of remote objects including remote customer devices or interfaces. The object is defined by users via CLI configuration. logicalEntity - this object supports monitoring of any logical entities contained by the system, including router device, IOS software on each LC or RP, and CPU utilization object, which can be defined by outage monitoring program. · Integer32

This object specifies the monitored object's type. It comprises interface(1), physicalEntity(2), swProcess(3), remoteObject(4), and logicalEntity(5). The detailed description has been presented above in the OutageMonObjectType definition.

Unsigned32

This object identifies a specific index of the monitored object based upon the cOutageObjectType. If it is interface(1), it correlates the object with ifIndex in ifTable in the IF-MIB. If it is PhysicalEntity(2), it correlates the object with entPhysicalIndex in entPhysicalTable in the ENTITY-MIB. If it is SWProcess(3), the value corresponds to an entry in the cOutageCpmMapTable, which correlates the object with cpmCPUTotalIndex and cpmProcessPID in cpmProcessTable in the CISCO-PROCESS-MIB. If it is remoteObject(4), the value corresponds to an entry in the cOutageRemoteObjMapTable, which correlates the object with its ID and description. If it is logicalEntity(5), the value corresponds to an entry in the cOutageLogicalObjMapTable, which correlates the object with the description.

INTEGER1 = up2 = down · Integer32

The current operational state of the monitored object. The Up(1) state indicates that the monitored object is actively or passively running in the normal condition. The Down(2) state indicates that the monitored object is experiencing some degree of outage.

Unsigned32

The total outage time in second of a component from the beginning of the measurement. The table stores the outage time up to the last recovery event. However, a request comes in during the down status of a component, the report adds the outage time between the last failure to the current.

Unsigned32

The total number of failure instances from the beginning of the measurement. Every failure event of a component adds 1 to this object.

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

This object specifies the date and time of the object to start outage recording. The instance value of this cOutageRecordingStartTime value is initialized to the time when the monitored object is added into this cOutageObjectTable.

Unsigned32

This object uniquely identifies cpmCPUTotalIndex and cpmProcessPID in CISCO-PROCESS-MIB. The cpmCPUTotalIndex is used for the cpmCPUTotalTable reference. A pair of { cpmCPUTotalIndex, cpmProcessPID } is used for the cpmProcessTable reference.

Unsigned32

An index that uniquely represents a CPU in cpmCPUTotalTable in CISCO-PROCESS-MIB.

Unsigned32

This object contains the process ID. It identifies an entry combined with cpmCPUTotalIndex in cpmProcessTable in CISCO-PROCESS-MIB.

Unsigned32

This object uniquely identifies a remote object description.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

Represents the type of address stored in cOutageRemoteObjID.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object represents the Network Layer Address of the remote object, which is configured by users via configuration file or CLI. It could be an IP address or DNS depends on users input.

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

This object specifies a human-readable message describing information about the monitored remote components such as router name or interface name, etc.

Unsigned32

This object uniquely identifies a logical entity object description.

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

This object specifies a human-readable message describing a detailed information about the monitored logical entity.