Cisco Cisco Prime Optical 10.3 Technical References
TM FORUM Implementation Statement (IS) Template and Guidelines
Table Error! No text of specified
-79. CORBA Version
style in document.
Version of Vendor Product
OMG Version
Comments
CORBA
e.g., CORBA
2.2
Naming Service
e.g., Version
2.2
e.g., Vendor X Version 5.1 (of
OMG Version 2.2 Naming
Service)
OMG Version 2.2 Naming
Service)
Notification
Service
Service
Note that a vendor could use an OMG
compliant Telecom Log Service to support
the MTNM notifications requirements.
compliant Telecom Log Service to support
the MTNM notifications requirements.
Telecom Log
Service
Service
2.33.2 Usage of the OMG Notification Service
A number of parameters are associated with the usage of the Notification Service. The supporting document to
the MTNM IDL, entitled Notification Service Usage, recommends values for the various Notification Service
parameters. Table E
the MTNM IDL, entitled Notification Service Usage, recommends values for the various Notification Service
parameters. Table E
is used by the vendor or service provider
to indicate any variances from the recommendations in the Notification Service Usage document.
style in document.
Table Error! No text of specified
-80. Usage of the Notification Service
Notification Service
Characteristic
Vendor Support (Service Provider
Requirement)
Comment
Push or Pull
The MTNM Notification Service
usage guidelines stipulate that Push
should be used
usage guidelines stipulate that Push
should be used
Number of
Notifications Channel
Notifications Channel
The MTNM Notification Service
usage guidelines recommend one
channel per EMS
usage guidelines recommend one
channel per EMS
Instances of
Notification Service
Notification Service
The MTNM Notification Service
usage guidelines recommend one
per EMS
usage guidelines recommend one
per EMS
EventReliability
ConnectionReliability
The use of Persistency is
recommended in both cases
recommended in both cases
Usage of Event
Priority
Priority
The same priority for all events is
recommended
recommended
Discard Policy
Delivery Order Policy
FIFO is recommended in both cases
Start Time Supported
The recommended value is “FALSE.”
Maximum Batch Size
Batch delivery is not recommended.
Thus, the recommended value is “0.”
Thus, the recommended value is “0.”
Pacing Interval
The recommended value is “0.”
RejectNewEvents
The recommended value is “TRUE.”
TimeOut
The recommended value is 30
minutes for NT_TCA and
NT_ALARM events, and 24 hours for
all other events.
minutes for NT_TCA and
NT_ALARM events, and 24 hours for
all other events.
Page 80 of 115
TeleManagement Forum 2007
TMF814Av3.1