Cisco Cisco Prime Optical 10.6 Technical References
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
getAllCallsAndTopLevelConnectionsAn
dSNCsWithTP
dSNCsWithTP
O
getAllCallIdsWithTP O
getAllCallIdsWithSNPPOrTNAName O
getCallAndTopLevelConnectionsAndSN
Cs
Cs
O
getCallAndTopLevelConnections
O
establishCall O
modifyCall O
releaseCall O
getCall O
addConnections O
removeConnections O
getConnectionsAndRouteDetails O
modifyDiversityAndCorouting O
2.19.3 Notifications
To be provided by the organization preparing an interoperability statement
2.20 NMS Session Module
2.20.1 Data Types
This module has no data types that represent second level objects.
2.20.2 Interfaces
Table Error! No text of specified style in document.-48. NmsSession
Operation Status
Support
Exception/
Error Reason
Comments
eventLossCleared M
eventLossOccurred M
Version 3.0 Additions
alarmLossOccurred M
These operations are
mandatory in the sense that
the NMS can not throw any
exceptions.
However, what the NMS does
when these methods are called
is entirely up to the NMS. The
NMS could, for example, do
nothing when receiving either
of these operations.
mandatory in the sense that
the NMS can not throw any
exceptions.
However, what the NMS does
when these methods are called
is entirely up to the NMS. The
NMS could, for example, do
nothing when receiving either
of these operations.
2.20.3 Notifications
There are no specific notifications associated with the data types in this module.
TMF814Av3.1
TeleManagement Forum 2007
Page 53 of 115