Cisco EPM Notification MIB

This section contains the following topics:

Cisco EPM Notification MIB

The following table shows the mapping of event fields to the alarm model in CISCO-EPM-NOTIFICATION-MIB.


Note


Some of the values in the following table may appear truncated in a PDF. Please refer to the HTML version for clarity.


Table 1. Cisco-EPM-Notification-MIB

Event Field

Snmpvarbind

OID

Description

TimeStamp

cenAlarmTimestamp

1.3.6.1.4.1.9.9.311.1.1.2.1.3

The time when the event was raised

Example: 1639759929

AlarmId

cenAlarmInstanceID

1.3.6.1.4.1.9.9.311.1.1.2.1.5

The unique alarm instance ID

Example: 57e3ef70-1597

Type

cenAlarmType

1.3.6.1.4.1.9.9.311.1.1.2.1.8

Type of Event

Example : 2001

Category

cenAlarmCategory

1.3.6.1.4.9.9.311.1.1.2.1.9

The category of the event generated represented in an integer value

System = 3, Network = 7, Audit = 13; Security = 4, External = 1

Example: 3

Category Definition

cenAlarmCategoryDefinition

1.3.6.1.4.9.9.311.1.1.2.1.10

The short description of the category of the event. The String is formatted in '<integer, eventCategory description>

Example: 3, System

Address Type

cenAlarmServerAddressType

1.3.6.1.4.9.9.311.1.1.2.1.11

The type of internet address of the CW alarm centre (VIP)

Example: 1:ipv4, 2:ipv6

Address

cenAlarmServerAddress

1.3.6.1.4.9.9.311.1.1.2.1.12

The IP Address of the CW alarm centre (VIP)

Example:

10.127.101.145

OriginAppId

cenAlarmManagedObjectClass

1.3.6.1.4.1.9.9.311.1.1.2.1.13

This attribute contains the OriginAppId of the application which generated the Event

Example: DLM

Description

cenAlarmDescription

1.3.6.1.4.9.9.311.1.1.2.1.16

A detailed description of the event

Example:Reachability request did not receive any response from CDG

Severity

cenAlarmSeverity

1.3.6.1.4.9.9.311.1.1.2.1.17

The alarm severity indicates the severity of the event in an integer value.

Critical=2; Major=3; Warning=4; Minor=5, Info=6, Clear=7

Example: 5

Severity definition

cenAlarmSeverityDefinition

1.3.6.1.4.9.9.311.1.1.2.1.18

The short description of the severity of the event. The String is formatted in '<integer, eventSeverity description>'

Example: 3,Major

ObjectDescription, ObjectId

cenUserMessage1

1.3.6.1.4.1.9.9.311.1.1.2.1.21

Information about the Event ObjectDescription, ObjectId. The string is formatted in '<ObjectDescription=xx, ObjectId=xx>'

Example: ObjectDescription= Node<xrvr9k>, ObjectId= NodeData [4a16368]

OriginServiceId

cenUserMessage2

1.3.6.1.4.1.9.9.311.1.1.2.1.22

Information about the Event OriginServiceId

Example: 0

EventId

cenAlertID

1.3.6.1.4.9.9.311.1.1.2.1.29

This attribute will contain the event id of the generated Event

Example: 9f19e5a9-a64c

cenAlarmVersion SnmpAdminString 1.3.6.1.4.9.9.311.1.1.2.1.2 The release version of this MIB.

Example: 1.0

Timestamp

cenAlarmTimestamp

1.3.6.1.4.9.9.311.1.1.2.1.3

The time when the alarm/event was raised.

Note :This is the number of seconds since Jan 1st 1970 (since epoch) in UTC

Example:1523608787

Timestamp

cenAlarmUpdatedTimestamp

1.3.6.1.4.9.9.311.1.1.2.1.4

Alarms/events persist over time and its value is updated automatically when the field(s) is changed. The updated time denotes a time. Each alarm is identified by the unique alarm instance id,

For example, cenAlarmInstanceID

cenAlarmInstanceID

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.5

The Unique Alarm Instance ID.

Example: c2afd3c1-d4e5-46db-84b2-

86d0d43f2056

cenAlarmStatus

Integer

1.3.6.1.4.9.9.311.1.1.2.1.6

The alarm status indicates the status of the alarm in integer value.

Example: Active=2, Cleared=3

cenAlarmStatus

Definition

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.7

The short description of the status of the alarm. The string is formatted in ',' tuples.

The value is the same value that the 'cenAlarmStatus'attribute holds. Contains one line description of the alarm status generated.

Example: 2, ACTIVE 3, CLEARED

cenAlarmType

Integer

1.3.6.1.4.9.9.311.1.1.2.1.8

  • unknown(1) —When the value for this attribute could not be determined.

  • direct(2)— Denotes an alarm generated by a set of events where all events are reported by an observation(s) of a managed object.

  • indirect(3)—Denotes an alarm generated by a set of events where all events were deduced or inferred by the status of managed objects as determined by the network management system..

  • mixed(4)—Denotes an alarm generated by a set of events which were either direct or indirect.

Example: 2

cenAlarmCategory

Integer

1.3.6.1.4.9.9.311.1.1.2.1.9

The category of the alarm/event generated represented in integer value.

Note: This integer field is not used in CNC. Use cenAlarmCategoryDefinition instead, which is a string.

cenAlarmCategory

Definition

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.10

The short description of the category of the alarm/event generated.. The String is formatted in ',' tuples. The value is the same value that the 'cenAlarmCategory' attribute holds. Contains one line description of the alarm category generated. For a list of alarm types, refer Alarms and Events.

Example: "LINK_DOWN", "SWT_AUTH_FAIL", "LINK_UP"

cenAlarmServer

AddressType

InetAddressType

1.3.6.1.4.9.9.311.1.1.2.1.11

The type of Internet address by which the server is reachable.

The server is the server that is generating this trap.

Example:

0: unknown

1: ipv4

2: ipv6

cenAlarmServerAddress

InetAddress

1.3.6.1.4.9.9.311.1.1.2.1.12

The IP Address or the DNS name of the Management. Server that raised this alarm will be notified.

Example: 10.127.101.145

cenAlarmManaged

ObjectClass

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.13

The class of the managed object for which this alarm/event was generated. For example, Router, Switch etc.

For a list of alarm types, refer Alarms and Events.

Example: "Optical", "Carrier Ethernet"

cenAlarmManagedObject

AddressType

InetAddressType

1.3.6.1.4.9.9.311.1.1.2.1.14

The type of Internet address by which the managed object is reachable.

Example:

0: unknown

1: ipv4

2: ipv6

cenAlarmManaged

ObjectAddress

InetAddress

1.3.6.1.4.9.9.311.1.1.2.1.15

The IP Address or the DNS name of the Managed Object.

Example: 2405:200:204:138:

172:30:9:121

cenAlarmDescription

OctetString

1.3.6.1.4.9.9.311.1.1.2.1.16

A detailed description of the alarm/event.

Example:

Port 'GigabitEthernet0/0/6'

(Description: ' # TO GigabitEthernet0/0/7 #') is down on device '2405:200:204:138:

172:30:9:121'.

:Lost Carrier

cenAlarmSeverity

Integer

1.3.6.1.4.9.9.311.1.1.2.1.17

The alarm severity indicates the severity of the alarm in integer value.

  • 1—Critical

  • 2—Major

  • 3—Minor

  • 4—Warning

  • 5—Clear

  • 6—Info

cenAlarmSeverity

Definition

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.18

The short description of the severity of the alarm generated. The String is formatted in ',' tuples. The value is the same value that the 'cenAlarmSeverity ' attribute holds. Contains one line description of the alarm severity generated.

  • 1—Critical

  • 2—Major

  • 3—Minor

  • 4—Warning

  • 5—Clear

  • 6—Info

cenAlarmTriageValue

Integer

1.3.6.1.4.9.9.311.1.1.2.1.19

The triage value of an alarm is a hierarchical weighting value (applied by the application, and more importantly customizable by the end user) to allow an artificial form of evaluating impact, interest, or other user-determined functions between alarms. The value is a positive number or zero, which denotes an undetermined or uncomputable value.

Note : CNC does not support this field.

cenEventIDList

OctetString

1.3.6.1.4.9.9.311.1.1.2.1.20

Comma separated list of the Unique Event identifiers that led to the generation of this Alarm.

Note : CNC does not support this field.

cenUserMessage1

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.21

User input message. Information about the alarm including whether the alarm/event is a root cause alarm or a service - impacting alarm.

srcObjectDisplayName=

GigabitEthernet0/0/0/18,

rootCauseId=0,

hostName=ASR9001 156.156.cisco,

serviceImpacting=0,

applicationSpecificAlarmID=

LINK_DOWN:10.127.101.156:

If: GigabitEthernet0/0/0/18##SubAlarm@@_7,

correlationType=UNKNOWN,

srcObjectBusinessKey=

4c2b8aa7

[1589721133_10.127.101.156,

GigabitEthernet0/0/0/18

chassisId = 0.

srcObjectDisplayName refers to the Location in UI. chassisId refers to Satellite Id.

If any of the above information is not populated, then corresponding value is not sent to NBI.

cenUserMessage2

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.22

User input message. This value can be configured.

Note : CNC does not support this field.

cenUserMessage3

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.23

User input message. This value can be configured.

Note : CNC does not support this field.

cenAlarmMode

Integer

1.3.6.1.4.9.9.311.1.1.2.1.24

  • unknown(1) —When the value for this attribute could not be determined

  • alert(2) — Denotes an alarm generated by a set of events where all events are reported by polling of managed objects and/or listening to SNMP notifications

  • event(3) — Denotes an event generated by polling of managed objects and/or listening to SNMP notifications

Example: 2

cenPartitionNumber

Integer

1.3.6.1.4.9.9.311.1.1.2.1.24

In traps generated by the management application that support multiple partitions, the attribute will carry the integer value assigned to identify the logical group where the managed device resides.

Note : CNC does not support this field.

cenPartitionName

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.26

In traps generated by the management application that support multiple partitions, the attribute will carry the name assigned to identify the logical group where the managed device resides.

cenCustomer

Identification

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.27

User input message. The attribute takes in a free format text. This attribute can be used by advanced management applications to sort responses from the fault management server.

Note: Crosswork Network Controller does not support this field.

cenCustomerRevision

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.28

User input message. The attribute takes in a free format text. This attribute can be used by advanced management applications to sort responses from the fault management server.

Note: Crosswork Network Controller does not support this field.

cenAlertID

SnmpAdminString

1.3.6.1.4.9.9.311.1.1.2.1.29

In event based notification, this attribute will contain the alert id to which the generated event has been rolled upto. In alert based notification, the cenAlarmInstanceId and cenAlertID will be identical.

Example:1185098114