Cisco Cisco Prime Optical 10.6 Developer's Guide
Cisco Prime Optical 10.6 GateWay/CORBA Programmer Reference Guide
563
5 Notifications, Fault Management, and Probable Cause Mapping
This chapter includes information on Cisco Prime Optical Gateway/CORBA’s notifications, fault
management, and probable cause mapping. This chapter includes the following sections:
management, and probable cause mapping. This chapter includes the following sections:
•
•
•
•
•
5.1 Overview of Notifications
The notification service forwards all fault notifications received from managed NEs to the network
management system (NMS). The notification service also forwards object creation, object deletion,
attribute change, protection switch, and threshold crossing alert (TCA) events. TMF 814 defines the
structure and format of attributes for all events and alarms.
The Prime Optical server and the Operations Support System (OSS) host must have Domain Name
System (DNS) enabled in order to receive notifications. OSS clients running behind a firewall must
configure an IIOP listening port to enable the TCP connection with the notification server. Prime Optical
must configure the notification service listening port number to allow OSS clients to communicate with
the notification service.
Prime Optical creates the notification channel with the QoS parameters shown in the following table.
management system (NMS). The notification service also forwards object creation, object deletion,
attribute change, protection switch, and threshold crossing alert (TCA) events. TMF 814 defines the
structure and format of attributes for all events and alarms.
The Prime Optical server and the Operations Support System (OSS) host must have Domain Name
System (DNS) enabled in order to receive notifications. OSS clients running behind a firewall must
configure an IIOP listening port to enable the TCP connection with the notification server. Prime Optical
must configure the notification service listening port number to allow OSS clients to communicate with
the notification service.
Prime Optical creates the notification channel with the QoS parameters shown in the following table.
Table 5-1: QoS Parameters for the Notification Channel
Parameter
Value
ConnectionReliability
BestEffort
StartTimeSupported
false
OrderPolicy
FifoOrder
DiscardPolicy
FifoOrder
MaxEventsPerConsumer 10000
Prime Optical sets the RejectNewEvents administration property of the channel to true, as defined by the
TMF.
Every notification that Prime Optical generates has the QoS parameters listed in the following table.
These parameter values are defined by the TMF and cannot be changed.
Table 5-2: QoS Parameters for Notifications
Parameter
Value
EventReliability BestEffort
Priority
DefaultPriority
Timeout
30 minutes for alarms and TCAs; 24 hours for all other notifications
The NMS retrieves all active alarms on the Element Management System (EMS) and on managed
element objects. The NMS filters alarms based on probable cause and managed element name.
GateWay/CORBA forwards Prime Optical-specific alarms to the NMS.
For NE-related alarms, Prime Optical inserts the original probable cause in the alarm’s
nativeProbableCause field. The TMF-mapped probable cause is available in the probableCause field.
element objects. The NMS filters alarms based on probable cause and managed element name.
GateWay/CORBA forwards Prime Optical-specific alarms to the NMS.
For NE-related alarms, Prime Optical inserts the original probable cause in the alarm’s
nativeProbableCause field. The TMF-mapped probable cause is available in the probableCause field.