User guide

3-208
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 3 Using CTM GateWay/CORBA Interfaces
3.12 nmsSession::NmsSession_I
3.12 nmsSession::NmsSession_I
The nmsSession module enables the EMS to inform the NMS of problems with notifications. When CTM
fails to push an event, it notifies all connected NMSs by invoking the eventLossOccurred method on
every active NmsSession_I. When the event loss period is over, CTM invokes the eventLossCleared
method on NmsSession_I.
Both methods are implemented by the NMS.
NmsSession also implements all methods defined in 3.15 session::Session_I, page 3-287.
CTM requires that NmsSession implement two new methods that are used by CTM to notify NmsSession
that the call to the getCTMHistoryPMData method has failed or succeeded.
3.12.1 historyPMDataCompleted
Synopsis
void historyPMDataCompleted(
in string fileName)
Description
When getCTMHistoryPMData completes successfully, CTM invokes this method on the NMS session.
At that time, NMS can retrieve the performance monitoring (PM) file from the CTM server.
Parameters
Throws
None.
Compliance
CTM-defined.
3.12.2 historyPMDataFailed
Synopsis
void historyPMDataFailed(
out string errorReason)
Description
When getCTMHistoryPMData fails, CTM invokes this method on the NMS session. Errors encountered
by CTM are stored in the errorReason parameter.
Name Type Input/Output Description
fileName string In Name of the file created by CTM in response to the
getCTMHistoryPMData call made by the NMS. This name is the
absolute path on CTM server.