Cisco Cisco Prime Optical 10.6 Developer's Guide

Page of 665
Cisco Prime Optical 10.6 GateWay/CORBA Programmer Reference Guide 
 
 
316
 
  The TestRevert operation in the Prime Optical client can be implemented by setting the 
gmplsRestoration  attribute to false. 
3.12  nmsSession::NmsSession_I 
The nmsSession module enables the EMS to inform the NMS of problems with notifications. When 
Prime Optical 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, Prime Optical invokes the 
eventLossCleared method on NmsSession_I. 
Both methods are implemented by the NMS. 
NmsSession also implements all methods defined i
. 
Prime Optical requires that NmsSession implement two new methods that are used by Prime Optical to 
notify NmsSession that the call to the getCTMHistoryPMData method has failed or succeeded. 
3.12.1  historyPMDataCompleted 
Synopsis 
Description 
When getCTMHistoryPMData completes successfully, Prime Optical invokes this method on the NMS 
session. At that time, NMS can retrieve the performance monitoring (PM) file from the Prime Optical 
server. 
Parameters 
Name 
Type 
Input/ 
Output 
Description 
fileName  string  In 
Name of the file created by Prime Optical in response to the 
getCTMHistoryPMData call made by the NMS. This name is the 
absolute path on Prime Optical server. 
Throws 
None. 
Compliance 
Prime Optical-defined. 
3.12.2  historyPMDataFailed 
Synopsis 
Description 
When getCTMHistoryPMData fails, Prime Optical invokes this method on the NMS session. Errors 
encountered by Prime Optical are stored in the errorReason parameter. 
Parameters 
Name 
Type  Input/Output  Description 
errorReason  string  Out 
Error string to indicate to the NMS the reason for the failure. 
Throws 
None. 
 
Compliance 
Prime Optical-defined.