CISCO-EPM-NOTIFICATION-MIB
AI MIB Summary
The CISCO-EPM-NOTIFICATION-MIB defines SNMP trap structures for Cisco Event Processor Manager (EPM) to report the status and identity of managed objects across multiple logical partitions within a system. These notifications enable consolidated monitoring of Cisco and non-Cisco devices by forwarding hardware and software event data to external management applications without supporting direct object queries.
Notifications directly from hardware and software and processed notifications from various management applications can be further processed and forwarded by still other management applications to indicate the status of devices and software (managed objects). The status of these managed objects can be reported by traps.
The CISCO-EPM-NOTIFICATION-MIB contains the trap structure which carries the identity and status info of the managed object as analyzed by such an event processor. It is not possible for receivers of these traps to query the mib objects.
A unique but optional feature of the application generating the trap defined in this mib is the ability to contain multiple partitions in the same system running the application. A 'Partition' is a logical grouping of a set of managed devices. These devices can belong to only one partition at any given time. The trap structure will contain information on the exact partition number and the partition name of the device where it resides.
The need for trap generation is to enable multiple management applications in the network to have a consolidated view of the whole network of Cisco and non-Cisco devices.
Main OID:
ciscoEpmNotificationMIB.1.3.6.1.4.1.9.9.311
41
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
41 total| Object Name |
|---|
ciscoEpmNotificationMIBNotifications directly from hardware and software and processed
notifications from various management applications can be further
processed and forwarded by still other management applications to
indicate the status of devices and software (managed objects).
The status of these managed objects can be reported by traps.
The CISCO-EPM-NOTIFICATION-MIB contains the trap structure which
carries the identity and status info of the managed object as
analyzed by such an event processor. It is not possible for
receivers of these traps to query the mib objects.
A unique but optional feature of the application generating the
trap defined in this mib is the ability to contain multiple
partitions in the same system running the application. A
'Partition' is a logical grouping of a set of managed devices.
These devices can belong to only one partition at any given
time. The trap structure will contain information on the exact
partition number and the partition name of the device where it
resides.
The need for trap generation is to enable multiple management
applications in the network to have a consolidated view of the
whole network of Cisco and non-Cisco devices. MODULE-IDENTITY .1.3.6.1.4.1.9.9.311 |
ciscoEpmNotificationMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.311.0 |
ciscoEpmNotificationAlarmNotification of the status of the managed object as
generated by the management server.
New attributes are added to the ciscoEpmNotificationAlarmRev1.
Hence this notification is deprecated. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.311.0.1 |
ciscoEpmNotificationAlarmRev1Notification of the status of the managed object as
generated by the management server. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.311.0.2 |
ciscoEpmNotificationMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.311.1 |
cenAlarmData OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.311.1.1 |
cenAlarmTableMaxLengthMaximum number of entries permissible in the cenAlarmTable.rw Unsigned32 ( 1..4294967295 ) .1.3.6.1.4.1.9.9.311.1.1.1 |
cenAlarmTableA table containing the device identification and
alarm value. The maximum number of entries permissible
in this table is defined by cenAlarmTableMaxLength. When
the number of entries in the table reaches the maximum
limit, the next entry would replace the oldest existing
entry in the table. SEQUENCE OF CenAlarmEntry .1.3.6.1.4.1.9.9.311.1.1.2 |
cenAlarmEntryThe information regarding a single device status alarm.
An entry is created when an alarm is processed. CenAlarmEntry .1.3.6.1.4.1.9.9.311.1.1.2.1 |
cenAlarmIndexA monotonically increasing integer for the sole
purpose of indexing the attributes in
ciscoEpmNotificationMIBObjects. When the maximum value is
reached, this value wraps back to 1. Unsigned32 .1.3.6.1.4.1.9.9.311.1.1.2.1.1 |
cenAlarmVersionThe release version of this MIB. The version string will
be of the form <major version>.<minorversion>.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.2 |
cenAlarmTimestampThe time when the alarm was raised.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.311.1.1.2.1.3 |
cenAlarmUpdatedTimestampAlarms persist over time and can have their field(s)
change values. The last time a field(s) changed, this
alarm is updated. The updated time denotes this time.
Each alarm is identified by the unique alarm instance
id, cenAlarmInstanceID.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.311.1.1.2.1.4 |
cenAlarmInstanceIDThe Unique Alarm Instance ID.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.5 |
cenAlarmStatusThe alarm status indicates the status of the alarm
in integer value.ro Integer32 .1.3.6.1.4.1.9.9.311.1.1.2.1.6 |
cenAlarmStatusDefinitionThe short description of the status of the alarm.
The string is formatted in
'<integer>,<alarmStatus description>' tuples. The <integer>
value is the same value that the 'cenAlarmStatus'
attribute holds. <alarmStatus description> contains one line
description of the alarm status generated.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.7 |
cenAlarmTypeunknown: When the value for this attribute could not be
determined.
direct: Denotes an alarm generated by a set of events where
all events are reported by an observation(s) of a
managed object.
indirect: 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: Denotes an alarm generated by a set of events which
were either direct or indirect.ro Enumeration .1.3.6.1.4.1.9.9.311.1.1.2.1.8 |
cenAlarmCategoryThe category of the alarm generated represented in
integer value.ro Integer32 .1.3.6.1.4.1.9.9.311.1.1.2.1.9 |
cenAlarmCategoryDefinitionThe short description of the category of the alarm
generated. The String is formatted in
'<integer>,<alarmCategory description>' tuples. The <integer>
value is the same value that the 'cenAlarmCategory'
attribute holds. <alarmCategory description> contains one
line description of the alarm category generated.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.10 |
cenAlarmServerAddressTypeThe type of Internet address by which the server
is reachable. The Server is the server
that is generating this trap.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.311.1.1.2.1.11 |
cenAlarmServerAddressThe IP Address or the DNS name of the Management
Server that raised this alarm to be notified.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.311.1.1.2.1.12 |
cenAlarmManagedObjectClassThe class of the managed object for which this
alarm was generated. For example, Router, Switch,
GateKeeper and VoicePort.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.13 |
cenAlarmManagedObjectAddressTypeThe type of Internet address by which the managed
object is reachable.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.311.1.1.2.1.14 |
cenAlarmManagedObjectAddressThe IP Address or the DNS name of the Managed Object.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.311.1.1.2.1.15 |
cenAlarmDescriptionA detailed description of the alarm.ro OCTET STRING .1.3.6.1.4.1.9.9.311.1.1.2.1.16 |
cenAlarmSeverityThe alarm severity indicates the severity of the alarm
in integer value.ro Integer32 .1.3.6.1.4.1.9.9.311.1.1.2.1.17 |
cenAlarmSeverityDefinitionThe short description of the severity of the alarm
generated. The String is formatted in
'<integer>,<alarmSeverity description>' tuples. The <integer>
value is the same value that the 'cenAlarmSeverity '
attribute holds. <alarmSeverity description> contains one line
description of the alarm severity generated.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.18 |
cenAlarmTriageValueThe 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 where zero
denotes an undetermined or uncomputable value.ro Integer32 .1.3.6.1.4.1.9.9.311.1.1.2.1.19 |
cenEventIDListComma separated list of the Unique Event identifiers
that led to the generation of this Alarm.ro OCTET STRING .1.3.6.1.4.1.9.9.311.1.1.2.1.20 |
cenUserMessage1User input message. This value can be configured.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.21 |
cenUserMessage2User input message. This value can be configured.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.22 |
cenUserMessage3User input message. This value can be configured.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.23 |
cenAlarmModeunknown: When the value for this attribute could not be
determined.
alert: 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: Denotes an event generated by polling of managed
ojects and/or listening to SNMP notifications.ro Enumeration .1.3.6.1.4.1.9.9.311.1.1.2.1.24 |
cenPartitionNumberIn 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.ro Unsigned32 .1.3.6.1.4.1.9.9.311.1.1.2.1.25 |
cenPartitionNameIn 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.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.26 |
cenCustomerIdentificationUser 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.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.27 |
cenCustomerRevisionUser 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.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.28 |
cenAlertIDIn event based notification, this attribute will contain the
alert id to which the generated event has been rolled up
to. In alert based notification, the cenAlarmInstanceId and
cenAlertID would be identical.ro SnmpAdminString .1.3.6.1.4.1.9.9.311.1.1.2.1.29 |
ciscoEpmNotificationMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.311.2 |
ciscoEpmNotificationMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.311.2.1 |
ciscoEpmNotificationMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.311.2.2 |