A P P E N D I X A

Notifications, Fault Management, and Probable Cause Mapping

This appendix includes information on CTM GateWay/CORBA’s notifications, fault management, and probable cause mapping. This appendix includes the following sections:

A.1 Overview of Notifications, page A-1

A.2 Resolving the Notification Service, page A-2

A.3 Tips to Improve Notification Throughput, page A-2

A.4 Supported Events, page A-3

A.5 Probable Cause Mapping, page A-12

A.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 CTM 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. CTM must configure the notification service listening port number to allow OSS clients to communicate with the notification service.

CTM creates the notification channel with the QoS parameters shown in the following table.

Table A-1

QoS Parameters for the Notification Channel

 

 

 

Parameter

 

Value

 

 

ConnectionReliability

BestEffort

 

 

StartTimeSupported

false

 

 

 

OrderPolicy

 

FifoOrder

 

 

 

DiscardPolicy

 

FifoOrder

 

 

MaxEventsPerConsumer1

10000

1.The MaxEventsPerConsumer value is configurable. To modify this value, see B.8 Location of the Naming Service IOR File, page B-6. All other parameter values are defined by the TMF and cannot be changed.

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

 

OL-14253-01

A-1

 

Page 1
Image 1
Cisco Systems OL-14253-01 appendix Notifications, Fault Management, and Probable Cause Mapping