Cisco Cisco Prime Optical 10.6 Developer's Guide
Cisco Prime Optical 10.6 GateWay/CORBA Programmer Reference Guide
378
Name
Type
Input/Output Description
tcaParameter TCAParameters_T
Out
Result of the operation.
For a list of supported layer rates and parameter values, see
Throws
Compliance
TMF-defined.
TMF-defined.
3.13.5 getCTMHistoryPMData
Synopsis
Description
This interface instructs the EMS to store historical PM data in a file, and to notify the NMS when the
request is complete. Within the request a list of TP/layerRate measurement points and a time frame are
specified. For each measurement point, the granularity (15-minute, 24-hour) and location
(PML_NEAR_END_RX, PML_FAR_END_RX) can be specified. A filtered set (scoped by the input
parameter pmParameters) of PM parameters collected for a particular TP/layer rate measurement point for
the specified granularity, location, and time window is made available.
Measurement intervals and the time frame are considered as closed intervals (that is, [startTime <= t
endTime] ).
Performance monitoring data on multiple TPs of multiple MEs is transferred in one data file. The PM file
format is defined by the TMF. Prime Optical generates a unique filename and saves the file in the CTMS-
home/pmData/username/ directory. This file is retained for six hours after Prime Optical finishes writing
the requested PM data. After six hours, the file is deleted. When GateWay/CORBA restarts, it retrieves a
list of all existing PM files and deletes them after six hours.
This is an asynchronous operation. Once Prime Optical receives the request, it validates it and the call
returns. In the background, Prime Optical begins writing to the file. Upon successful completion, it
notifies the NMS session by invoking nmsSession::NmsSession_I::historyPMDataCompleted. If Prime
Optical fails to create this file or write into the file, the NMS is notified by invoking
nmsSession::NmsSession_I::historyPMDataFailed.
Prime Optical allows only one request from each NMS session at a time.
For ONS 15454 SDH NEs, this operation is not supported on low-order STM-path, but is supported on
path parameters on E3 and DS3 cards.
This interface instructs the EMS to store historical PM data in a file, and to notify the NMS when the
request is complete. Within the request a list of TP/layerRate measurement points and a time frame are
specified. For each measurement point, the granularity (15-minute, 24-hour) and location
(PML_NEAR_END_RX, PML_FAR_END_RX) can be specified. A filtered set (scoped by the input
parameter pmParameters) of PM parameters collected for a particular TP/layer rate measurement point for
the specified granularity, location, and time window is made available.
Measurement intervals and the time frame are considered as closed intervals (that is, [startTime <= t
endTime] ).
Performance monitoring data on multiple TPs of multiple MEs is transferred in one data file. The PM file
format is defined by the TMF. Prime Optical generates a unique filename and saves the file in the CTMS-
home/pmData/username/ directory. This file is retained for six hours after Prime Optical finishes writing
the requested PM data. After six hours, the file is deleted. When GateWay/CORBA restarts, it retrieves a
list of all existing PM files and deletes them after six hours.
This is an asynchronous operation. Once Prime Optical receives the request, it validates it and the call
returns. In the background, Prime Optical begins writing to the file. Upon successful completion, it
notifies the NMS session by invoking nmsSession::NmsSession_I::historyPMDataCompleted. If Prime
Optical fails to create this file or write into the file, the NMS is notified by invoking
nmsSession::NmsSession_I::historyPMDataFailed.
Prime Optical allows only one request from each NMS session at a time.
For ONS 15454 SDH NEs, this operation is not supported on low-order STM-path, but is supported on
path parameters on E3 and DS3 cards.