Cisco Cisco Transport Manager 9.1 Technical References

Page of 151
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES  
TMF 814Av3.0 
  TeleManagement Forum 2003 
83 
Table 2-60. Usage of the Notification Service  
Notification Service 
Characteristic 
Vendor Support (Service Provider 
Requirement) 
Comment 
Push or Pull 
Push 
The MTNM Notification 
Service usage guidelines 
stipulate that Push should be 
used 
Number of 
Notifications 
Channel 
One 
The MTNM Notification 
Service usage guidelines 
recommend one channel per 
EMS 
Instances of 
Notification 
Service  
One 
The MTNM Notification 
Service usage guidelines 
recommend one per EMS 
EventReliability BestEffort 
ConnectionRelia
bility 
BestEffort 
In the case of 
EventReliability, BestEffort 
means that the Notification 
Service may lose events 
during a crash. However, 
persistent events will be re-
delivered to their proxy 
queues after the crash (proxy 
queues ignore events that 
have already been delivered 
to the connected consumer). 
For ConnectionReliability
BestEffort means that 
connections will be lost when 
the Notification Service fails 
to deliver or receive events 
from a client. 
The use of Persistency is 
recommended (by TMF) in 
both cases 
Usage of Event 
Priority 
Default Priority (0) 
Default priority implies the 
same priority for all events  
Discard Policy 
FifoOrder 
Delivery Order 
Policy 
FifoOrder 
FIFO is recommended in both 
cases 
Start Time 
Supported 
false 
The recommended value is 
“FALSE.” 
Maximum Batch 
Size 
Batch delivery is not 
recommended. Thus, the 
recommended value is “0.” 
Pacing Interval 
The recommended value is 
“0.” 
RejectNewEvent
true 
The recommended value is 
“TRUE.”