Cisco Cisco Transport Manager 9.1 テクニカルリファレンス

MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES  

TMF 814Av3.0 

  TeleManagement Forum 2003 

93 

EquipmentInventory Mgr: getAllSupportingE 59ms 5 

secs 

 

 

 

 

 

 

A similar table is needed for each notification type. There may be delays in delivering a 
notification. Once a notification has reached a particular age without being delivered to the NMS, 
it may make no sense for the Notification service to deliver the notification. The parties 
representing the NMS and EMS  need to agree on a timeout period for each notification type.  

The following table is needed to specify the heartbeat time constraints for the session supervision 
from NMS to EMS, and vice versa. It should be noted that Table 3-2 refers to pings that are sent 
from the NMS to the EMS and vice versa, in order to make sure the connection between the NMS 
and EMS is still up. Table 3-3, on the other hand, refers to NT_HEARTBEAT notifications sent 
from the notification service to the NMS (this allows the NMS to know that its connection to the 
notification service is up.  

Table 3-2 Heartbeat Time Constraints 

NMS 

 

 

The NMS may use 
requests/responses for 
supervision instead of 
heartbeats.  

EMS 

Configurable. It can range from 60 
seconds to 1440 seconds (24 
hours). 

 

 

 

 

In Version 3.0, the EMS may send heartbeat notifications (NT_HEARTBEAT) when it has not 
sent any notifications for a period of time. The EMS supplier should indicate how often heartbeat 
notifications are sent (in the absence of other notifications). The EMS supplier should also 
indicate the number of consecutively missed heartbeat notifications after which the NMS should 
consider its association with the notification service has been lost. 

 

Table 3-3. Heartbeat Notification Time Constraints