ceemHistoryMaxEventEntries
1.3.6.1.4.1.9.10.134.1.2.1
Integer32 (0..50)
The maximum number of entries that can be held in ceemHistoryEventTable.
CISCO-EMBEDDED-EVENT-MGR-MIB
2006-11-07
The MIB module to describe and store events generated by the Cisco Embedded Event Manager. The Cisco Embedded Event Manager detects hardware and software faults, and other events (such as OIRs) for the system. It also enables users to configure fault recovery services for system wide components. The Embedded Event Manager also provides process reliability statistics. The Embedded Event Manager is a policy driven process through which faults in the system are reported through a defined API. The Embedded Event Manager policy engine receives notifications when faults and other events occur. Embedded Event Manager policies implement recovery based on the current state of the system and the actions specified in the policy for a given event. Recovery actions are triggered when the policy is run. Developers write and customize Embedded Event Manager policies to handle faults and events.
Download CISCO-EMBEDDED-EVENT-MGR-MIB.txt Open CISCO-EMBEDDED-EVENT-MGR-MIB.txt in a new tab
SCALARS (2) · TABLES (3) · TRAPS (2)
Scalars (2)
| Name | OID |
|---|---|
| ceemHistoryMaxEventEntries | 1.3.6.1.4.1.9.10.134.1.2.1 |
| ceemHistoryLastEventEntry | 1.3.6.1.4.1.9.10.134.1.2.2 |
Tables (3)
| Name | OID |
|---|---|
| ceemEventMapTable | 1.3.6.1.4.1.9.10.134.1.1.1 |
| ceemHistoryEventTable | 1.3.6.1.4.1.9.10.134.1.2.3 |
| ceemRegisteredPolicyTable | 1.3.6.1.4.1.9.10.134.1.3.1 |
Traps (2)
| Name | OID |
|---|---|
| cEventMgrServerEvent | 1.3.6.1.4.1.9.10.134.0.1 |
| cEventMgrPolicyEvent | 1.3.6.1.4.1.9.10.134.0.2 |
END OF TOC
Scalar details
ceemHistoryLastEventEntry
1.3.6.1.4.1.9.10.134.1.2.2
Unsigned32 (1..4294967295)
Index of last entry created in ceemHistoryEventTable.
Table details
ceemEventMapTable
1.3.6.1.4.1.9.10.134.1.1.1
Index: ceemEventIndex
A table containing information about ceemEventIndex value mapping. Each conceptual row specifies a unique mapping between a ceemEventIndex value, and a Embedded Event Manager event type. Rows are added dynamically as the Embedded Event Manager server learns of new event types. This occurs when Embedded Event Manager Event Detectors register with the Embedded Event Manager server.
ceemEventIndex
1.3.6.1.4.1.9.10.134.1.1.1.1.1
Unsigned32
This object uniquely identifies an event. Events are not persisted across reloads.
ceemEventName
1.3.6.1.4.1.9.10.134.1.1.1.1.2
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..128) · OCTET STRING · hint 255t
The name of the Embedded Event Manager event.
ceemEventDescrText
1.3.6.1.4.1.9.10.134.1.1.1.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 (0..255) · OCTET STRING · hint 255t
This object specifies a human-readable message describing information about the Embedded Event Manager event.
ceemHistoryEventTable
1.3.6.1.4.1.9.10.134.1.2.3
Index: ceemHistoryEventIndex
A table of Embedded Event Manager events generated by this router. Conceptual row entries are dynamically added into this table when Embedded Event Manager events occur. Entries are stored in FIFO order. When the maximum number of entries has been reached in the table, the oldest entry in the table is removed immediately. When a table is reduced to a smaller size N, the oldest entries are immediately removed from the table leaving a maximum of N entries.
ceemHistoryEventIndex
1.3.6.1.4.1.9.10.134.1.2.3.1.1
Unsigned32 (1..4294967295)
A monotonically increasing non-zero integer uniquely identifying a generated event. When it reaches the maximum value, the agent wraps the value back to 1 and may flush all existing entries in the event table.
ceemHistoryEventType1
1.3.6.1.4.1.9.10.134.1.2.3.1.2
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType2
1.3.6.1.4.1.9.10.134.1.2.3.1.3
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType3
1.3.6.1.4.1.9.10.134.1.2.3.1.4
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType4
1.3.6.1.4.1.9.10.134.1.2.3.1.5
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryPolicyPath
1.3.6.1.4.1.9.10.134.1.2.3.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..128) · OCTET STRING · hint 255t
The file path on the router where the Embedded Event Manager policy that was triggered is stored. If the size of the file path string is larger than 128, the end characters will be truncated.
ceemHistoryPolicyName
1.3.6.1.4.1.9.10.134.1.2.3.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..128) · OCTET STRING · hint 255t
The name of the Embedded Event Manager policy that was triggered because of an Embedded Event Manager event. The name must be a valid Embedded Event Manager policy name. It must be in the form of a valid Posix filename.
ceemHistoryPolicyExitStatus
1.3.6.1.4.1.9.10.134.1.2.3.1.8
Integer32
Reference: Posix 1003.1 Specification.
The exit status of the Embedded Event Manager policy execution. This value corresponds to the Posix process exit status.
ceemHistoryPolicyIntData1
1.3.6.1.4.1.9.10.134.1.2.3.1.9
Integer32
Arbitrary integer data that the Embedded Event Manager policy can use. Use of this object is optional. If unused by a policy, this object will not be instantiated for that policy.
ceemHistoryPolicyIntData2
1.3.6.1.4.1.9.10.134.1.2.3.1.10
Integer32
Arbitrary integer data that the Embedded Event Manager policy can use. Use of this object is optional. If unused by a policy, this object will not be instantiated for that policy.
ceemHistoryPolicyStrData
1.3.6.1.4.1.9.10.134.1.2.3.1.11
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
Arbitrary string data the Embedded Event Manager policy can use. Use of this object is optional. If unused by a policy, this object will not be instantiated for that policy.
ceemHistoryNotifyType
1.3.6.1.4.1.9.10.134.1.2.3.1.12
NotifySource1 = server2 = policyThe notification source of the history entry. server - Notification was sent by the Embedded Event Manager server. policy - Notification was sent from within an Embedded Event Manager policy. · Integer32
The notification type that was sent from the Embedded Event Manager. The valid values are server or policy.
ceemHistoryEventType5
1.3.6.1.4.1.9.10.134.1.2.3.1.13
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType6
1.3.6.1.4.1.9.10.134.1.2.3.1.14
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType7
1.3.6.1.4.1.9.10.134.1.2.3.1.15
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType8
1.3.6.1.4.1.9.10.134.1.2.3.1.16
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemRegisteredPolicyTable
1.3.6.1.4.1.9.10.134.1.3.1
Index: ceemRegisteredPolicyIndex
A table of Embedded Event Manager policies registered on a system. The number of entries depends on the configuration of the system. The maximum number is implementation dependent.
ceemRegisteredPolicyIndex
1.3.6.1.4.1.9.10.134.1.3.1.1.1
Unsigned32
A monotonically increasing non-zero integer uniquely identifying a policy registration. When it reaches the maximum value, the agent wraps the value back to 1 upon receiving the next policy registration.
ceemRegisteredPolicyName
1.3.6.1.4.1.9.10.134.1.3.1.1.2
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 Embedded Event Manager policy that was registered. The name must be a valid Embedded Event Manager policy name. It must be in the form of a valid Posix filename.
ceemRegisteredPolicyEventType1
1.3.6.1.4.1.9.10.134.1.3.1.1.3
Unsigned32
The type of Embedded Event Manager event which was registered by the policy. The value corresponds to an entry in the ceemEventMapTable.
ceemRegisteredPolicyEventType2
1.3.6.1.4.1.9.10.134.1.3.1.1.4
Unsigned32
The type of Embedded Event Manager event which was registered by the policy. The value corresponds to an entry in the ceemEventMapTable.
ceemRegisteredPolicyEventType3
1.3.6.1.4.1.9.10.134.1.3.1.1.5
Unsigned32
The type of Embedded Event Manager event which was registered by the policy. The value corresponds to an entry in the ceemEventMapTable.
ceemRegisteredPolicyEventType4
1.3.6.1.4.1.9.10.134.1.3.1.1.6
Unsigned32
The type of Embedded Event Manager event which was registered by the policy. The value corresponds to an entry in the ceemEventMapTable.
ceemRegisteredPolicyStatus
1.3.6.1.4.1.9.10.134.1.3.1.1.7
INTEGER1 = enabled2 = disabled · Integer32
This status indicates whether the policy is enabled or disabled.
ceemRegisteredPolicyType
1.3.6.1.4.1.9.10.134.1.3.1.1.8
INTEGER1 = user2 = system · Integer32
This variable indicates whether this is a user or system policy.
ceemRegisteredPolicyNotifFlag
1.3.6.1.4.1.9.10.134.1.3.1.1.9
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This flag indicates if an SNMP notification will be sent when policy is triggered.
ceemRegisteredPolicyRegTime
1.3.6.1.4.1.9.10.134.1.3.1.1.10
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 the policy was registered. It is stored as a 32-bit count of seconds since 0000 UTC, 1 January, 1970.
ceemRegisteredPolicyEnabledTime
1.3.6.1.4.1.9.10.134.1.3.1.1.11
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 the policy was last enabled. It is stored as a 32-bit count of seconds since 0000 UTC, 1 January, 1970.
ceemRegisteredPolicyRunTime
1.3.6.1.4.1.9.10.134.1.3.1.1.12
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 last time the policy was run. It is stored as a 32-bit count of seconds since 0000 UTC, 1 January, 1970.
ceemRegisteredPolicyRunCount
1.3.6.1.4.1.9.10.134.1.3.1.1.13
Counter32
The number of times the policy has been run.
ceemRegisteredPolicyEventType5
1.3.6.1.4.1.9.10.134.1.3.1.1.14
Unsigned32
The type of Embedded Event Manager event which was registered by the policy. The value corresponds to an entry in the ceemEventMapTable.
ceemRegisteredPolicyEventType6
1.3.6.1.4.1.9.10.134.1.3.1.1.15
Unsigned32
The type of Embedded Event Manager event which was registered by the policy. The value corresponds to an entry in the ceemEventMapTable.
ceemRegisteredPolicyEventType7
1.3.6.1.4.1.9.10.134.1.3.1.1.16
Unsigned32
The type of Embedded Event Manager event which was registered by the policy. The value corresponds to an entry in the ceemEventMapTable.
ceemRegisteredPolicyEventType8
1.3.6.1.4.1.9.10.134.1.3.1.1.17
Unsigned32
The type of Embedded Event Manager event which was registered by the policy. The value corresponds to an entry in the ceemEventMapTable.
Trap details
cEventMgrServerEvent
1.3.6.1.4.1.9.10.134.0.1
This notification is sent by the Embedded Event Manager server after it has run a policy associated with the event ceemHistoryEventType that was received.
ceemHistoryEventType1
1.3.6.1.4.1.9.10.134.1.2.3.1.2
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType2
1.3.6.1.4.1.9.10.134.1.2.3.1.3
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType3
1.3.6.1.4.1.9.10.134.1.2.3.1.4
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType4
1.3.6.1.4.1.9.10.134.1.2.3.1.5
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryPolicyPath
1.3.6.1.4.1.9.10.134.1.2.3.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..128) · OCTET STRING · hint 255t
The file path on the router where the Embedded Event Manager policy that was triggered is stored. If the size of the file path string is larger than 128, the end characters will be truncated.
ceemHistoryPolicyName
1.3.6.1.4.1.9.10.134.1.2.3.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..128) · OCTET STRING · hint 255t
The name of the Embedded Event Manager policy that was triggered because of an Embedded Event Manager event. The name must be a valid Embedded Event Manager policy name. It must be in the form of a valid Posix filename.
ceemHistoryPolicyExitStatus
1.3.6.1.4.1.9.10.134.1.2.3.1.8
Integer32
Reference: Posix 1003.1 Specification.
The exit status of the Embedded Event Manager policy execution. This value corresponds to the Posix process exit status.
cEventMgrPolicyEvent
1.3.6.1.4.1.9.10.134.0.2
This notification is configured to be sent from within an Embedded Event Manager policy after an Embedded Event Manager event ceemHistoryEventType has occurred. If one or more of the objects ceemHistoryPolicyIntData1, ceemHistoryPolicyIntData2, and ceemHistoryPolicyStrData are not instantiated, then the varbind for the object(s) not instantiated will contain the value 'noSuchInstance'.
ceemHistoryEventType1
1.3.6.1.4.1.9.10.134.1.2.3.1.2
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType2
1.3.6.1.4.1.9.10.134.1.2.3.1.3
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType3
1.3.6.1.4.1.9.10.134.1.2.3.1.4
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryEventType4
1.3.6.1.4.1.9.10.134.1.2.3.1.5
Unsigned32
The type of Embedded Event Manager event which was detected. The value corresponds to an entry in the ceemEventTable.
ceemHistoryPolicyPath
1.3.6.1.4.1.9.10.134.1.2.3.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..128) · OCTET STRING · hint 255t
The file path on the router where the Embedded Event Manager policy that was triggered is stored. If the size of the file path string is larger than 128, the end characters will be truncated.
ceemHistoryPolicyName
1.3.6.1.4.1.9.10.134.1.2.3.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..128) · OCTET STRING · hint 255t
The name of the Embedded Event Manager policy that was triggered because of an Embedded Event Manager event. The name must be a valid Embedded Event Manager policy name. It must be in the form of a valid Posix filename.
ceemHistoryPolicyIntData1
1.3.6.1.4.1.9.10.134.1.2.3.1.9
Integer32
Arbitrary integer data that the Embedded Event Manager policy can use. Use of this object is optional. If unused by a policy, this object will not be instantiated for that policy.
ceemHistoryPolicyIntData2
1.3.6.1.4.1.9.10.134.1.2.3.1.10
Integer32
Arbitrary integer data that the Embedded Event Manager policy can use. Use of this object is optional. If unused by a policy, this object will not be instantiated for that policy.
ceemHistoryPolicyStrData
1.3.6.1.4.1.9.10.134.1.2.3.1.11
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
Arbitrary string data the Embedded Event Manager policy can use. Use of this object is optional. If unused by a policy, this object will not be instantiated for that policy.