Cisco Systems OL-14253-01 appendix Resolving the Notification Service

Appendix A Notifications, Fault Management, and Probable Cause Mapping

Resolving the Notification Service

	CTM sets the RejectNewEvents administration property of the channel to true, as defined by the TMF.
	Every notification that CTM generates has the QoS parameters listed in the following table. These
	parameter values are defined by the TMF and cannot be changed.
Table A-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.
	CTM GateWay/CORBA forwards CTM-specific alarms to the NMS.
	For NE-related alarms, CTM inserts the original probable cause in the alarm’s nativeProbableCause
	field. The TMF-mapped probable cause is available in the probableCause field.

A.2 Resolving the Notification Service

CTM GateWay/CORBA can integrate with external notification services. When CTM GateWay/CORBA starts, a reference to EventNotifyChannelFactory is resolved. CTM GateWay/CORBA makes the following attempts to resolve the object:

1.Resolve initial references with the default service name of NotificationService to resolve the object. You can change the service name by setting the corbagw.notification.ServiceName property in the corbagw.properties file.

2.Resolve the object through the naming service. The default naming service entry is services.NotifyChannelFactory. You can change the naming service entry by setting the corbagw.notification.NamingContext property in the corbagw.properties file.

3.Resolve the object directly through the Interoperable Object Reference (IOR). You can change the URL of the IOR file by setting the corbagw.notification.FactoryIORFile property in the corbagw.properties file. The default location for the IOR file is file://localhost/CTM_baseDir/cfg/NotificationService.ior. You can specify a URL that points to a remote web server.

A.3 Tips to Improve Notification Throughput

While CTM GateWay/CORBA and the bundled notification server are developed and tuned to provide high throughput, you might want to take additional steps to improve throughput and avoid any loss of notifications. You should implement the StructuredPushConsumer interface defined by the Object Management Group (OMG) and implement the push_structured_event method. The notification server invokes this method on the NMS.

Caution Because all CORBA calls are blocking, the notification server thread blocks until the push_structured_event method completes. If you try to perform a time-consuming task before the method completes, you will block the notification server.

Cisco Transport Manager Release 8.5 GateWay/CORBA User Guide and Programmer Manual

A-2 OL-14253-01