OSS Integration Guide for Cisco Mobile Wireless Transport Manager 6.1.6

Book Contents

Find Matches in This Book

Available Languages

Download Options

Book Title

OSS Integration Guide for Cisco Mobile Wireless Transport Manager 6.1.6

Chapter Title

MWTM Northbound Traps

PDF - Complete Book (32.28 MB) PDF - This Chapter (120.0 KB)
View with Adobe Reader on a variety of devices

Results

Chapter: MWTM Northbound Traps

CISCO-SYSLOG-MIB :: clogMessageGenerated
CISCO-EPM-NOTIFICATION-MIB :: ciscoEmpNotificationAlarmRev1
ciscoEmpNotificationAlarmRev2

MWTM Northbound Traps

MWTM can be configured to send traps to the Northbound OSS.

To configure MWTM to send traps, you must first configure MWTM using the MWTM Event Editor (see the User Guide for the Mobile Wireless Transport Manager 6.1.6 for details on how to use the MWTM Event Editor).

MWTM 6.1.6 can be configured to send either of the following two types of traps:

•CISCO-SYSLOG-MIB :: clogMessageGenerated

•CISCO-EPM-NOTIFICATION-MIB :: ciscoEpmNotificationAlarmRev1

CISCO-SYSLOG-MIB :: clogMessageGenerated

MWTM 6.1.6 can generate the CISCO-SYSLOG-MIB :: clogMessageGenerated trap, but this trap does not support the updating/deleting of existing events.

To support the updating/deleting of events and allow the Northbound OSS and MWTM 6.1.6 to maintain a consistent view of events, you should configure the MWTM 6.1.6 to send the CISCO-EPM-NOTIFICATION-MIB :: ciscoEpmNotificationAlarmRev1.

Table 7-1 describes the Clog attributes.

Table 7-1 Clog Attributes
Attribute Name	OID	Value
clogHistFacility	1.3.6.1.4.1.9.9.41.1.2.3.1.2	Name of the facility that generated this message.
clogHistSeverity	1.3.6.1.4.1.9.9.41.1.2.3.1.3	The severity of the message.
clogHistMsgName	1.3.6.1.4.1.9.9.41.1.2.3.1.4	Text identification for the message type. Note The default value is MWTM. You can customize this field using the MWTM Event Editor.
clogHistMsgText	1.3.6.1.4.1.9.9.41.1.2.3.1.5	The text of the message.
clogHistTimestamp	1.3.6.1.4.1.9.9.41.1.2.3.1.6	The value of sysUpTime when this message was generated.

CISCO-EPM-NOTIFICATION-MIB :: ciscoEmpNotificationAlarmRev1

The CISCO-EPM-NOTIFICATION-MIB :: ciscoEpmNotificationAlarm supports new/updating/deleting events. This trap type is preferred for MWTM 6.1.6/Northbound OSS integration.

Table 7-2 describes the Notification attributes.

Table 7-2 Notification Attributes
Attribute Name	OID	Value
cenAlarmVersion	1.3.6.1.4.1.9.9.311.1.1.2.1.2	Unused
cenAlarmTimestamp	1.3.6.1.4.1.9.9.311.1.1.2.1.3	Unused
cenAlarmUpdatedTimestamp	1.3.6.1.4.1.9.9.311.1.1.2.1.4	Unused
cenAlarmInstanceID	1.3.6.1.4.1.9.9.311.1.1.2.1.5	Unique event ID
cenAlarmStatus	1.3.6.1.4.1.9.9.311.1.1.2.1.6	0, 1, or 2 Corresponds to New, Update, or Delete
cenAlarmStatusDefinition	1.3.6.1.4.1.9.9.311.1.1.2.1.7	0, 1, or 2 Corresponds to New, Update, or Delete
cenAlarmType	1.3.6.1.4.1.9.9.311.1.1.2.1.8	Unused
cenAlarmCategory	1.3.6.1.4.1.9.9.311.1.1.2.1.9	Integer corresponding to user defined event category.
cenAlarmCategoryDefinition	1.3.6.1.4.1.9.9.311.1.1.2.1.10	String representation of user defined event category.
cenAlarmServerAddressType	1.3.6.1.4.1.9.9.311.1.1.2.1.11	Always ipv4
cenAlarmServerAddress	1.3.6.1.4.1.9.9.311.1.1.2.1.12	MWTM Server IP address.
cenAlarmManagedObjectClass	1.3.6.1.4.1.9.9.311.1.1.2.1.13	The classification of the modeled NE. For example, MWR node, ITP node, ONS node, SP, Linkset, Link, AS, ASPA, SGMP, and Interface.
cenAlarmManagedObjectAddressType	1.3.6.1.4.1.9.9.311.1.1.2.1.14	Always ipv4.
cenAlarmManagedObjectAddress	1.3.6.1.4.1.9.9.311.1.1.2.1.15	The IP address of the managed object. Values are either the IP address of the router or the IP address of the MWTM 6.1.6 server.
cenAlarmDescription	1.3.6.1.4.1.9.9.311.1.1.2.1.16	Event message text.
cenAlarmSeverity	1.3.6.1.4.1.9.9.311.1.1.2.1.17	Integer corresponding to user defined event severity.
cenAlarmSeverityDefinition	1.3.6.1.4.1.9.9.311.1.1.2.1.18	String representation of user defined event severity. The set of alarm severity values are: 0 - Normal 1 - Indeterminate 2 - Informational 3 - Warning 4 - Minor 5 - Major 6 - Critical There is not a separate OID that indicates a clear alarm. Instead a clear alarm is indicated by this OID when the severity is 0, Normal.
cenAlarmTriageValue	1.3.6.1.4.1.9.9.311.1.1.2.1.19	Unused (Always 0).
cenEventIDList	1.3.6.1.4.1.9.9.311.1.1.2.1.20	Communication.
cenUserMessage1	1.3.6.1.4.1.9.9.311.1.1.2.1.21	This is the event/alarm name.
cenUserMessage2	1.3.6.1.4.1.9.9.311.1.1.2.1.22	UNIX time when event occurred. See cenAlarmTimestamp. Example: 2030-04-14, 16:05:05.369,0400
cenUserMessage3	1.3.6.1.4.1.9.9.311.1.1.2.1.23	UNIX time when event changed. See cenAlarmUpdatedTimestamp. Example: 2030-04-14, 16:05:05.369,0400
cenAlarmMode	1.3.6.1.4.1.9.9.311.1.1.2.1.24	Either 2 for alert or 3 for event.
cenPartitionNumber	1.3.6.1.4.1.9.9.311.1.1.2.1.25	Count of the number of times this event or alert has occurred.
cenPartitionName	1.3.6.1.4.1.9.9.311.1.1.2.1.26	Correlation key
cenCustomerIdentification	1.3.6.1.4.1.9.9.311.1.1.2.1.27	Network element name
cenCustomerRevision	1.3.6.1.4.1.9.9.311.1.1.2.1.28	Acknowledged by user name.
cenAlertID	1.3.6.1.4.1.9.9.311.1.1.2.1.29	Unique event ID.

ciscoEmpNotificationAlarmRev2

The CISCO-EPM-NOTIFICATION-MIB :: ciscoEpmNotificationAlarmRev2 supports new/updating/deleting events. This trap type is preferred for MWTM 6.1.6/Northbound OSS integration.

Table 7-3 describes the Notification attributes.

Table 7-3 Notification Attributes
Attribute Name	OID	Value
cenAlarmVersion	1.3.6.1.4.1.9.9.311.1.1.2.1.2	EPM version number EPM(1), EPM-2(2)
cenAlarmTimestamp	1.3.6.1.4.1.9.9.311.1.1.2.1.3	Unused
cenAlarmUpdatedTimestamp	1.3.6.1.4.1.9.9.311.1.1.2.1.4	Unused
cenAlarmInstanceID	1.3.6.1.4.1.9.9.311.1.1.2.1.5	Unique event ID
cenAlarmStatus	1.3.6.1.4.1.9.9.311.1.1.2.1.6	0, 1, or 2 Corresponds to New, Update, or Delete
cenAlarmStatusDefinition	1.3.6.1.4.1.9.9.311.1.1.2.1.7	0, 1, or 2 Corresponds to New, Update, or Delete
cenAlarmType	1.3.6.1.4.1.9.9.311.1.1.2.1.8	AlarmNature (Undefined(0), ADAC(1), ADMC(2))
cenAlarmCategory	1.3.6.1.4.1.9.9.311.1.1.2.1.9	Integer corresponding to user defined event category.
cenAlarmCategoryDefinition	1.3.6.1.4.1.9.9.311.1.1.2.1.10	String representation of user defined event category.
cenAlarmServerAddressType	1.3.6.1.4.1.9.9.311.1.1.2.1.11	Always ipv4
cenAlarmServerAddress	1.3.6.1.4.1.9.9.311.1.1.2.1.12	MWTM Server IP address.
cenAlarmManagedObjectClass	1.3.6.1.4.1.9.9.311.1.1.2.1.13	The classification of the modeled NE. For example, MWR node, ITP node, ONS node, SP, Linkset, Link, AS, ASPA, SGMP, and Interface.
cenAlarmManagedObjectAddressType	1.3.6.1.4.1.9.9.311.1.1.2.1.14	Always ipv4.
cenAlarmManagedObjectAddress	1.3.6.1.4.1.9.9.311.1.1.2.1.15	The IP address of the managed object. Values are either the IP address of the router or the IP address of the MWTM 6.1.6 server.
cenAlarmDescription	1.3.6.1.4.1.9.9.311.1.1.2.1.16	Event message text.
cenAlarmSeverity	1.3.6.1.4.1.9.9.311.1.1.2.1.17	Integer corresponding to user defined event severity.
cenAlarmSeverityDefinition	1.3.6.1.4.1.9.9.311.1.1.2.1.18	String representation of user defined event severity. The set of alarm severity values are: 0 - Normal 1 - Indeterminate 2 - Informational 3 - Warning 4 - Minor 5 - Major 6 - Critical There is not a separate OID that indicates a clear alarm. Instead a clear alarm is indicated by this OID when the severity is 0, Normal.
cenAlarmTriageValue	1.3.6.1.4.1.9.9.311.1.1.2.1.19	Unused (Always 0).
cenEventIDList	1.3.6.1.4.1.9.9.311.1.1.2.1.20	List of key/value pairs to accommodate alarm attributes not included in other EPM notification varbinds. Includes timestamps in the managed device time zone. NodeCreateTime=2010-06-17,23:25:44.65,-2202 NodeChangeTime=2010-06-17,23:31:41.517,-2202 NodeClearTime=2010-06-17,23:31:41.516,-2202 NodeAckTime=2010-06-17,23:28:38.337,-2202
cenUserMessage1	1.3.6.1.4.1.9.9.311.1.1.2.1.21	This is the event/alarm name.
cenUserMessage2	1.3.6.1.4.1.9.9.311.1.1.2.1.22	UNIX time when event occurred. See cenAlarmTimestamp. Example: 2030-04-14, 16:05:05.369,0400
cenUserMessage3	1.3.6.1.4.1.9.9.311.1.1.2.1.23	UNIX time when event changed. See cenAlarmUpdatedTimestamp. Example: 2030-04-14, 16:05:05.369,0400
cenAlarmMode	1.3.6.1.4.1.9.9.311.1.1.2.1.24	Either 2 for alert or 3 for event.
cenPartitionNumber	1.3.6.1.4.1.9.9.311.1.1.2.1.25	Count of the number of times this event or alert has occurred.
cenPartitionName	1.3.6.1.4.1.9.9.311.1.1.2.1.26	Correlation key
cenCustomerIdentification	1.3.6.1.4.1.9.9.311.1.1.2.1.27	Network element name
cenCustomerRevision	1.3.6.1.4.1.9.9.311.1.1.2.1.28	Format: AckUserName;Timestamp AckUserName is one of: •< MWTM Client Name > - the mwtm client name if user access is disabled •< MWTM User Name > - the mwtm user name if user access is enabled
cenAlertID	1.3.6.1.4.1.9.9.311.1.1.2.1.29	Format: ClearUserName;Timestamp ClearUserName is one of: •< MWTM Client Name > - manual clear: the mwtm client name if user access is disabled •< MWTM User Name > - manual clear: the mwtm user name if user access is enabled •< AutoClear > - auto clear: the string value "AutoClear"