Cisco Cisco Prime Optical 10.6 Developer's Guide
Cisco Prime Optical 10.6 GateWay/CORBA Programmer Reference Guide
317
3.12.3 operationInfo
Synopsis
Description
The EMS invokes this interface on the NMS session when configConnLessInfos or configConnLessInfos
is complete. The error encountered by the EMS is included in the errorReason parameter.
Parameters
Name
The EMS invokes this interface on the NMS session when configConnLessInfos or configConnLessInfos
is complete. The error encountered by the EMS is included in the errorReason parameter.
Parameters
Name
Type
Input/Output Description
opname
string
in
Name of the operation performed or completed.
additionalInfo NVSList_T in
List of names and values that reports the operation status.
Throws
None.
Compliance
Prime Optical-defined.
None.
Compliance
Prime Optical-defined.
3.12.4 alarmLossOccurred
Synopsis
Description
When the EMS fails to discard an alarm, TCA, file transfer status, or protection switch notification, it
notifies all connected NMSs by invoking this method on every active NmsSession_I. This interface is
also invoked on any new NmsSession_I set up during the event loss period.
When the EMS invokes this method on the NmsSession_I, it sets an internal flag to indicate that it has
informed the NMSs of the alarm loss. As long as this flag is set, the EMS does not invoke this method
again. However, the EMS might invoke eventLossOccurred if it fails to push a different type of event.
When this method is invoked on an NmsSession_I, the NMS learns whether the EMS failed to push one
or more alarms, TCAs, file transfers, or protection switch notifications. The NMS is out-of-sync with the
EMS for these types of notifications. The NSM waits until the EMS calls eventLossCleared before
resynchronizing alarms, TCAs, file transfers, and protection switch data with the EMS.
Parameters
Name
When the EMS fails to discard an alarm, TCA, file transfer status, or protection switch notification, it
notifies all connected NMSs by invoking this method on every active NmsSession_I. This interface is
also invoked on any new NmsSession_I set up during the event loss period.
When the EMS invokes this method on the NmsSession_I, it sets an internal flag to indicate that it has
informed the NMSs of the alarm loss. As long as this flag is set, the EMS does not invoke this method
again. However, the EMS might invoke eventLossOccurred if it fails to push a different type of event.
When this method is invoked on an NmsSession_I, the NMS learns whether the EMS failed to push one
or more alarms, TCAs, file transfers, or protection switch notifications. The NMS is out-of-sync with the
EMS for these types of notifications. The NSM waits until the EMS calls eventLossCleared before
resynchronizing alarms, TCAs, file transfers, and protection switch data with the EMS.
Parameters
Name
Type
Input/Output Description
startTime
globaldefs::Time_T In
Time of the first lost notification.
notificationId string
In
ID of the first lost notification.
Throws
None.
Compliance
TMF-defined.
None.
Compliance
TMF-defined.
3.13 performance::PerformanceManagementMgr_I
This interface accesses operations that deal with performance element monitoring. A handle to an
instance of this interface is gained through the getManager operation in emsSession. This interface is
inherited from
instance of this interface is gained through the getManager operation in emsSession. This interface is
inherited from
This interface also implements the getCapabilities method. Operations described in the following sections
are returned to the NMS when it invokes getCapabilities.
are returned to the NMS when it invokes getCapabilities.