-
Cisco Transport Manager GateWay/CORBA User's Guide and Programmer Manual, 7.2
-
Preface
-
Chapter 1: Overview of CTM GateWay/CORBA
-
Chapter 2: NE- and CTM-Specific Details
-
Chapter 3: Using CTM GateWay/CORBA Interfaces
-
Appendix A: Notifications, Fault Management, and Probable Cause Mapping
-
Appendix B: Server Administration and Configuration
-
Appendix C: OSS Client Development and Use Cases
-
Appendix D: ONS 15501, ONS 15530, and ONS 15540 Equipment List
-
Table Of Contents
Using CTM GateWay/CORBA Interfaces
3.1.1 common::Common_I::getCapabilities
3.2.1 emsMgr::EMSMgr_I::getAllEMSAndMEActiveAlarms
3.2.2 emsMgr::EMSMgr_I::getAllEMSSystemActiveAlarms
3.2.3 emsMgr::EMSMgr_I::getAllTopLevelSubnetworks
3.2.4 emsMgr::EMSMgr_I::getAllTopLevelSubnetworkNames
3.2.5 emsMgr::EMSMgr_I::getAllTopLevelTopologicalLinks
3.2.6 emsMgr::EMSMgr_I::getAllTopLevelTopologicalLinkNames
3.2.7 emsMgr::EMSMgr_I::getTopLevelTopologicalLink
3.2.8 emsMgr::EMSMgr_I::createTopologicalLink
3.2.9 emsMgr::EMSMgr_I::createTopologicalLinkWithYCableProtection
3.2.10 emsMgr::EMSMgr_I::deleteTopologicalLink
3.2.11 emsMgr::EMSMgr_I::modifyTopologicalLink
3.2.12 emsMgr::EMSMgr_I::getEMS
3.2.13 emsMgr::EMSMgr_I::getAllL2Topologies
3.2.14 emsMgr::EMSMgr_I::getAllQoSTemplateNames
3.2.15 emsMgr::EMSMgr_I::getAllQoSTemplates
3.2.16 emsMgr::EMSMgr_I::getQoSTemplate
3.2.17 emsMgr::EMSMgr_I::getAllEMSandMEClearedAlarms
3.2.18 emsMgr::EMSMgr_I::getAllEMSSystemClearedAlarms
3.2.19 emsMgr::EMSMgr_I::createServerTrailLink
3.2.20 emsMgr::EMSMgr_I::deleteServerTrailLink
3.2.21 emsMgr::EMSMgr_I::addManagedElement
3.2.22 emsMgr::EMSMgr_I::addNetworkPartition
3.2.23 emsMgr::EMSMgr_I::addMultiLayerSubnetwork
3.2.24 emsMgr::EMSMgr_I::deleteAndPurgeManagedElement
3.2.25 emsMgr::EMSMgr_I::deleteNetworkPartition
3.2.26 emsMgr::EMSMgr_I::deleteMultiLayerSubnetwork
3.2.27 emsMgr::EMSMgr_I::addSWVersion
3.2.28 emsMgr::EMSMgr_I::getAllSupportedMESoftwareVersions
3.3.1 emsSession::EmsSession_I::getEventChannel
3.3.2 emsSession::EmsSession_I::getManager
3.3.3 emsSession::EmsSession_I::getSupportedManagers
3.4 emsSessionFactory::EmsSessionFactory_I
3.4.1 emsSessionFactory::EmsSessionFactory_I::getEmsSession
3.4.2 emsSessionFactory::EmsSessionFactory_I::getEmsPublicKey
3.4.3 emsSessionFactory::EmsSessionFactory_I::getEmsPublicKeyPair
3.5 equipment::EquipmentInventoryMgr_I
3.5.1 equipment::EquipmentInventoryMgr_I::getAllEquipment
3.5.2 equipment::EquipmentInventoryMgr_I::getAllEquipmentNames
3.5.3 equipment::EquipmentInventoryMgr_I::getAllSupportedPTPs
3.5.4 equipment::EquipmentInventoryMgr_I::getAllSupportedPTPNames
3.5.5 equipment::EquipmentInventoryMgr_I::getAllSupportingEquipment
3.5.6 equipment::EquipmentInventoryMgr_I::getAllSupportingEquipment
Names3.5.7 equipment::EquipmentInventoryMgr_I::getContainedEquipment
3.5.8 equipment::EquipmentInventoryMgr_I::getEquipment
3.5.9 equipment::EquipmentInventoryMgr_I::provisionEquipment
3.5.10 equipment::EquipmentInventoryMgr_I::setAlarmReportingOff
3.5.11 equipment::EquipmentInventoryMgr_I::setAlarmReportingOn
3.5.12 equipment::EquipmentInventoryMgr_I::unprovisionEquipment
3.5.13 equipment::EquipmentInventoryMgr_I::configureMLParameters
3.6 maintenanceOps::MaintenanceManager_I
3.6.1 maintenanceOps::MaintenanceMgr_I::getActiveMaintenanceOperations
3.6.2 maintenanceOps::MaintenanceMgr_I::performMaintenanceOperation
3.7 managedElementManager::ManagedElementManager_I
3.7.1 managedElementManager::ManagedElementManager_I::getAllActiveAlarms
3.7.2 managedElementManager::ManagedElementManager_I::getAllSNCs
3.7.3 managedElementManager::ManagedElementManager_I::
getAllManagedElements3.7.4 managedElementManager::ManagedElementManager_I::
getAllManagedElementNames3.7.5 managedElementManager::ManagedElementManager_I::getAllPTPs
3.7.6 managedElementManager::ManagedElementManager_I::
getAllPTPNames3.7.7 managedElementManager::ManagedElementManager_I::
getContainedInUseTPs3.7.8 managedElementManager::ManagedElementManager_I::
getContainedInUseTPNames3.7.9 managedElementManager::ManagedElementManager_I::
getContainedPotentialTPs3.7.10 managedElementManager::ManagedElementManager_I::
getContainedPotentialTPNames3.7.11 managedElementManager::ManagedElementManager_I::
getContainingSubnetworkNames3.7.12 managedElementManager::ManagedElementManager_I::
getManagedElement3.7.13 managedElementManager::ManagedElementManager_I::getTP
3.7.14 managedElementManager::ManagedElementManager_I::
getAssociatedTopologicalLinks3.7.15 managedElementManager::ManagedElementManager_I::setTPData
3.7.16 managedElementManager::ManagedElementManager_I::
getAllSrcPTPsForSNCProvisioning3.7.17 managedElementManager::ManagedElementManager_I::
getAllSrcCTPsForSNCProvisioning3.7.18 managedElementManager::ManagedElementManager_I::
getAllDestPTPsForSNCProvisioning3.7.19 managedElementManager::ManagedElementManager_I::
getAllDestCTPsForSNCProvisioning3.7.20 managedElementManager::ManagedElementManager_I::
getAllSrcFTPsForSNCProvisioning3.7.21 managedElementManager::ManagedElementManager_I::
getAllDestFTPsForSNCProvisioning3.7.22 managedElementManager::ManagedElementManager_I::
forceNEResync3.7.23 managedElementManager::ManagedElementManager_I::
getAllTopologicalLinksForME3.7.24 managedElementManager::ManagedElementManager_I::
getAllRolls3.7.25 managedElementManager::ManagedElementManager_I::
getAllRollNames3.7.26 managedElementManager::ManagedElementManager_I::
getRoll3.7.27 managedElementManager::ManagedElementManager_I::
getRollToPTPs3.7.28 managedElementManager::ManagedElementManager_I::
getRollToCTPs3.7.29 managedElementManager::ManagedElementManager_I::
getRollFromCTPs3.7.30 managedElementManager::ManagedElementManager_I::setPortName
3.7.31 managedElementManager::ManagedElementManager_I::getPortName
3.7.32 managedElementManager::ManagedElementManager_I::
getAllClearedAlarms3.7.33 managedElementManager::ManagedElementManager_I::
getAllSrcPTPsForSTProvisioning3.7.34 managedElementManager::ManagedElementManager_I::
getAllSrcCTPsForSTProvisioning3.7.35 managedElementManager::ManagedElementManager_I::
getAllDestPTPsForSTProvisioning3.7.36 managedElementManager::ManagedElementManager_I::
getAllDestCTPsForSTProvisioning3.7.37 managedElementManager::ManagedElementManager_I::
getAllCrossConnections3.7.38 managedElementManager::DownloadMESoftware
3.7.39 managedElementManager::getAllSoftwareDownloadJobs
3.8 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I
3.8.1 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllEdgePoints
3.8.2 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllEdgePointNames3.8.3 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllManagedElement3.8.4 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllManagedElementNames
3.8.5 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllSubnetworkConnections3.8.6 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllSubnetworkConnectionsWithTP3.8.7 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllSubnetworkConnectionNames3.8.8 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllSubnetworkConnectionNamesWithTP3.8.9 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllTopologicalLinks
3.8.10 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllTopologicalLinkNames3.8.11 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getMultiLayerSubnetwork3.8.12 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getCTPsAndTopologicalLinks
3.8.13 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getSNC3.8.14 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getSNCsByUserLabel3.8.15 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getTopologicalLink3.8.16 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
createAndActivateSNCFromUserLabel3.8.17 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::createAndActivateSNC
3.8.18 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::addDrops
3.8.19 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::deactivateAndDeleteSNC
3.8.20 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getVCATSNC
3.8.21 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllVCATSNCs
3.8.22 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllVCATSNCNames
3.8.23 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllVCATMemberSNCs
3.8.24 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllVCATMemberSNCNames3.8.25 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::createVCAT
3.8.26 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::deleteVCAT
3.8.27 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::addMemberSNCsToVCAT
3.8.28 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
deleteMemberSNCsFromVCAT3.8.29 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
deleteAllMemberSNCFromVCAT3.8.30 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getValidSubnetworkConnectionsForMerge3.8.31 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::upgrade
3.8.32 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::createRoll
3.8.33 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::deleteRoll
3.8.34 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::cancelRoll
3.8.35 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::forceValidSignal
3.8.36 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::completeRoll
3.8.37 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::finishRoll
3.8.38 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllRolls
3.8.39 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllRollNames
3.8.40 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAssociatedRollNamesForSNC3.8.41 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAssociatedSNCNamesForRoll3.8.42 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::createAndActivateSNCOnDRI
3.9.1 nmsSession::NmsSession_I::historyPMDataCompleted
3.9.2 nmsSession::NmsSession_I::historyPMDataFailed
3.10 performance::PerformanceManagementMgr_I
3.10.1 performance::PerformanceManagementMgr_I::disablePMData
3.10.2 performance::PerformanceManagementMgr_I::enablePMData
3.10.3 performance::PerformanceManagementMgr_I::setTCATPParameter
3.10.4 performance::PerformanceManagementMgr_I::getTCATPParameter
3.10.5 performance::PerformanceManagementMgr_I::getCTMHistoryPMData
3.10.6 performance::PerformanceManagementMgr_I::
deleteHistoryPMDataFile3.10.7 performance::PerformanceManagementMgr_I::getTPHistoryPMData
3.10.8 performance::PerformanceManagementMgr_I::getHoldingTime
3.10.9 performance::PerformanceManagementMgr_I::getAllCurrentPMData
3.11 protection::ProtectionMgr_I
3.11.1 protection::ProtectionMgr_I::getAllProtectedTPNames
3.11.2 protection::ProtectionMgr_I::getAllProtectionGroups
3.11.3 protection::ProtectionMgr_I::getProtectionGroup
3.11.4 protection::ProtectionMgr_I::performProtectionCommand
3.11.5 protection::ProtectionMgr_I::createProtectionGroup
3.11.6 protection::ProtectionMgr_I::deleteProtectionGroup
3.11.7 protection::ProtectionMgr_I::getAssociatedProtectionGroup
3.12.1 session::Session_I::endSession
3.12.2 session::Session_I::ping
3.13.1 mtnmVersion::Version_I::getVersion
3.14 L2 Topology and MLVLAN for ML-Series Ethernet Cards
3.14.1 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::createMLVLAN
3.14.2 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
modifyMLVLANAddFrontPorts3.14.3 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
modifyMLVLANDropFrontPorts3.14.4 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
modifyMLVLANPortState3.14.5 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::modifyMLVLANRSTPState
3.14.6 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::modifyMLVLANTPQOS
3.14.7 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
modifyMLVLANCustomerIDServiceID3.14.8 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getMLVLAN
3.14.9 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::deleteMLVLAN
3.14.10 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllMLVLANs
3.14.11 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllMLVLANNames
3.14.12 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllAssociatedSNCs3.14.13 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getL2Topology
3.14.14 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAssociatedL2TopologyForSNC3.14.15 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAssociatedL2TopologyForMLVLAN3.14.16 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::createL2
Topology3.14.17 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
deleteL2Topology3.14.18 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
modifyL2Topology3.14.19 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::
getAllAvailableMLEquipmentOrTPNames3.15.1 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::createVLAN
3.15.2 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::deleteVLAN
3.15.3 multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::getAllVLANs
Using CTM GateWay/CORBA Interfaces
The following sections describe each interface that CTM supports, including TeleManagement Forum (TMF)-specific and Cisco-proprietary interfaces. These interfaces are:
•
emsSessionFactory::EmsSessionFactory_I
•
•
•
•
•
•
Note
3.1 common::Common_I
The Common_I interface is a set of services and utilities that each manager interface inherits. CTM supports only one method from this interface.
3.1.1 common::Common_I::getCapabilities
Synopsis
void getCapabilities(out CapabilityList_T capabilities)raises(globaldefs::ProcessingFailureException);Description
This service retrieves the capabilities of the manager. All nonspecified capabilities are assumed to be unsupported.
Parameters
A Capability_T value is used to identify a functionality supported by the EMS across the NML-EML interface. It is a name/value pair, in which the name represents the feature/capability name and the value represents the support or nonsupport of the specified feature/capability.
The EMS capabilities for this release include individual IDL operation support. The feature/capability name part is used to identify an IDL operation using the following convention:
module_name::interface_name::operation_name
The currently defined values are as follows:
•
•
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.Compliance
TMF-defined.
3.2 emsMgr::EMSMgr_I
The EMSMgr_I interface accesses operations that deal with the Element Management System (EMS) itself. A handle to an instance of this interface is gained through the emsSession::EmsSession_I::getManager operation in emsSession. This interface is inherited from common::Common_I.
interface EMSMgr_I:common::Common_IThis interface implements the getCapabilities method. Operations described in the following sections are returned to the network management system (NMS) when it invokes getCapabilities.
3.2.1 emsMgr::EMSMgr_I::getAllEMSAndMEActiveAlarms
Synopsis
void getAllEMSAndMEActiveAlarms(in notifications::ProbableCauseList_T excludeProbCauseList,in notifications::PerceivedSeverityList_T excludeSeverityList,in unsigned long how_many,out notifications::EventList_T eventList,out notifications::EventIterator_I eventIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request active alarms that are under the control of the EMS (alarms raised by the NEs and alarms raised by the EMS itself). Some alarms might be filtered out (excluded) by specifying their probable causes or severities.
Due to performance concerns, only one OSS client is allowed to invoke this operation at a time. Otherwise, CTM throws an EXCPT_UNABLE_TO_COMPLY exception.
The result of this operation is independent of the filtering set up by the NMS for the notification service.
ONS 15310, ONS 15327, ONS 15454 SDH, ONS 15454 SONET, ONS 15600 SONET, and ONS 15600 SDH
Cisco ONS 15310, ONS 15327, ONS 15454 SDH, ONS 15454 SONET, ONS 15600 SONET, and ONS 15600 SDH do not send a "clear" for the TCA events. The TCAs are not reported in the eventList returned by this method.
ONS 15540, ONS15530, and ONS 15501
TCAs are also reported in the eventList returned by this method as ONS 15540 sends a "clear" for the threshold crossing alarms.
ONS 15800, ONS 15801, and ONS 15808
ONS 15800, ONS 15801, and ONS 15808 alarms that are retrieved using the CTM GateWay/CORBA have OT_EQUIPMENT as the object_type field.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_UNABLE_TO_COMPLY - Raised when this method is being used by another OSS Client.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.2.2 emsMgr::EMSMgr_I::getAllEMSSystemActiveAlarms
Synopsis
void getAllEMSSystemActiveAlarms(in notifications::PerceivedSeverityList_T excludeSeverityList,in unsigned long how_many,out notifications::EventList_T eventList,out notifications::EventIterator_I eventIt) raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request all active alarms for the EMS. Some alarms can be filtered out (excluded) by specifying their severities.
The result of this operation is independent of the filtering set up by the NMS for the notification service.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.2.3 emsMgr::EMSMgr_I::getAllTopLevelSubnetworks
Synopsis
void getAllTopLevelSubnetworks(in unsigned long how_many,out multiLayerSubnetwork::SubnetworkList_T sList,out multiLayerSubnetwork::SubnetworkIterator_I sIt)raises(globaldefs::ProcessingFailureException);Description
This enables an NMS to request all subnetworks that are under the control of the EMS.
Parameters
CTM support for MultiLayerSubnetwork_T is as follows:
•
–
•
–
•
–
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.2.4 emsMgr::EMSMgr_I::getAllTopLevelSubnetworkNames
Synopsis
void getAllTopLevelSubnetworkNames(in unsigned long how_many,out globaldefs::NamingAttributesList_T nameList,out globaldefs::NamingAttributesIterator_I nameIt)raises(globaldefs::ProcessingFailureException);Description
This operation has exactly the same behavior as the operation described in emsMgr::EMSMgr_I::getAllTopLevelSubnetworks, but instead of returning the entire object structures, this operation returns their names.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.2.5 emsMgr::EMSMgr_I::getAllTopLevelTopologicalLinks
Synopsis
void getAllTopLevelTopologicalLinks(in unsigned long how_many,out topologicalLink::TopologicalLinkList_T topoList,out topologicalLink::TopologicalLinkIterator_I topoIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request all of the top-level topological links that are under the control of the EMS. A top-level topological link is a topological link in which the end-points of the topological link exist in two different multilayer subnetworks.
If the link is under the control of the EMS and then removed from the NE, the ProvType parameter is reported as INVALID.
Parameters
CTM support for TopologicalLink_T structure is as follows:
•
–
•
–
•
–
•
–
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_NOT_IMPLEMENTED - Raised if EMS cannot support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.2.6 emsMgr::EMSMgr_I::getAllTopLevelTopologicalLinkNames
Synopsis
void getAllTopLevelTopologicalLinkNames(in unsigned long how_many,out globaldefs::NamingAttributesList_T nameList,out globaldefs::NamingAttributesIterator_I nameIt)raises(globaldefs::ProcessingFailureException);Description
This operation has exactly the same behavior as the operation described in emsMgr::EMSMgr_I::getAllTopLevelTopologicalLinks, but instead of returning the entire object structures, this operation returns their names.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_NOT_IMPLEMENTED - Raised if EMS cannot support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.2.7 emsMgr::EMSMgr_I::getTopLevelTopologicalLink
Synopsis
void getTopLevelTopologicalLink(in globaldefs::NamingAttributes_T topoLinkName,out topologicalLink::TopologicalLink_T topoLink)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request the top-level topological link given that its name is under the control of the EMS.
If the link is under the control of the EMS and then removed from the NE, the ProvType parameter is reported as INVALID.
Parameters
topoLinkName
globaldefs::NamingAttributes_T
In
Name of the topological link
topoLink
TopologicalLink::TopologicalLink_T
Out
Top-level topological link
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when topoLinkName does not reference a top level topological link object.EXCPT_ENTITY_NOT_FOUND - Raised when topoLinkName references a top level topological link object that does not exist in the EMS.Compliance
TMF-defined.
3.2.8 emsMgr::EMSMgr_I::createTopologicalLink
Synopsis
void createTopologicalLink(in topologicalLink::TLCreateData_T createData,out topologicalLink::TopologicalLink_T topologicalLink)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to create a topological link manually between two ManagedElements. CTM supports topological link creation between MEs belonging to the same multiLayer subnetwork. If CTM auto discovers a topological link between two end-points on which a manually created link exists, then CTM overwrites the manually created topological link information with the autodiscovered topological link information. CTM generates an AttributeValueChange event when a manually created link is overwritten with auto discovered topological link information. CTM supports topological link creation between two unmanaged NEs, and also between a managed NE and an unmanaged NE. CTM ignores the topological link layer rate if the topological link creation is between two unmanaged NEs.
CTM generates an ObjectCreation event notification when a new topological link is created.
Note
Note
Note
This operation is supported for CRS-1, ONS 15216, ONS 15310, ONS 15327, ONS 15454 SDH, ONS 15454 SONET, ONS 15600 SONET, ONS 15600 SDH, ONS155xx, and unmanaged NEs.
Parameters
CTM support for TLCreateData_T structure is as follows:
•
–
•
–
•
–
•
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_NOT_IMPLEMENTED - Raised if input createData is not valid.EXCPT_INVALID_INPUT - Raised if EMS cannot support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.Compliance
CTM-defined. This interface is already proposed in TMF and will be included in TMF Release 3.0.
3.2.9 emsMgr::EMSMgr_I::createTopologicalLinkWithYCableProtection
Synopsis
void createTopologicalLinkWithYCableProtection(in topologicalLink::MTLCreateData_T createData,out topologicalLink::TopologicalLink_T topologicalLink)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to create a Y-Cable topological link manually between two ManagedElements. A Y-Cable link is a bidirectional link with one PTP source and two PTP destinations. Because of the limitation in TMF for TopologicalLinks having one PTP source and one PTP destination, CTM will report two TopologicalLinks for a Y-Cable link. These two topological links will have the same nativeEMSName. See 2.2.5.8 TopologicalLink, page 2-70 for the naming convention for the Y-Cable TopologicalLink object name. The destination of the Y-Cable link must be on a DWDM card on an ONS15454SONET/SDH or on an ONS155xx NE.
CTM generates two ObjectCreationEvent notifications when a new Y-Cable topological link is created.
The TopologicalLink returned from this method is one leg of the Y-Cable.
This interface is supported for ONS 15454 SONET, ONS 15454 SDH, and ONS155xx NEs.
Parameters
CTM support for MTLCreateData_T structure is as follows:
•
–
•
–
•
–
•
–
•
–
–
–
–
–
–
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_NOT_IMPLEMENTED - Raised if input createData is not valid.EXCPT_INVALID_INPUT - Raised if EMS cannot support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.Compliance
CTM-defined.
3.2.10 emsMgr::EMSMgr_I::deleteTopologicalLink
Synopsis
void deleteTopologicalLink(in globaldefs::NamingAttributes_T topoLinkName)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to delete a topological link manually between two ManagedElements. CTM throws the EXCPT_UNABLE_TO_COMPLY exception if an attempt was made to delete an autodiscovered topological link or if the topological link could not be deleted in the current state. CTM generates an ObjectDeletion event notification when a topological link is deleted.
Note
This operation is supported for CRS-1, ONS 15216, ONS 15310, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS155xx, ONS 15600 SONET, ONS 15600 SDH, and unmanaged NEs.
Parameters
topoLinkName
globaldefs::NamingAttributes_T
In
The name of the topological link to be deleted
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INVALID_INPUT - Raised if input topological link name is invalid.EXCPT_ENTITY_NOT_FOUND - Raised if the specified topological link name does not exist in CTM.EXCPT_NOT_IMPLEMENTED - Raised if EMS cannot support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_UNABLE_TO_COMPLY - Raised if attempt is made to delete an auto-discovered topological linkCompliance
CTM-defined. This interface is already proposed in TMF and will be included TMF Release 3.0.
3.2.11 emsMgr::EMSMgr_I::modifyTopologicalLink
Synopsis
void modifyTopologicalLink(in topologicalLink::TLCreateData_T newTLCreateData,out topologicalLink::TopologicalLink_T newTopologicalLink)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to modify some of the parameters of the existing topological links. The following parameters can be modified using modifyTopologicalLink API.
•
•
•
Parameters
CTM support for TLCreateData_T structure is as follows:
•
–
•
–
•
–
•
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_NOT_IMPLEMENTED - Raised if input createData is not valid.EXCPT_INVALID_INPUT - Raised if EMS cannot support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.Compliance
CTM-defined.
3.2.12 emsMgr::EMSMgr_I::getEMS
Synopsis
void getEMS(out EMS_T emsInfo)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request the EMS information.
Parameters
CTM supports EMS_T is as follows:
•
–
•
–
•
–
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.Compliance
TMF-defined.
3.2.13 emsMgr::EMSMgr_I::getAllL2Topologies
Synopsis
void getAllL2Topologies(in multiLayerSubnetwork::L2TopoType_T l2TopoType,in unsigned long how_many,out multiLayerSubnetwork::L2TopologyList_T l2TopoList,out multiLayerSubnetwork::L2TopologyIterator_I l2TopoIt)raises(globaldefs::ProcessingFailureException);Description
This interface lists all L2 topologies of a particular topology type in the EMS. The L2 topology has a scope in EMS. CTM supports only Resilient Packet Ring (RPR) and point-to-point L2 topology types.
Note
Parameters
CTM support for L2Topology_T structure is as follows:
•
–
•
–
•
–
•
–
•
–
•
•
•
LR_STS1_and_AU3_High_Order_VC3
LR_STS3c_and_AU4_VC4
LR_STS6c_and_VC4_2c
LR_STS9c_and_VC4_3c
LR_STS12c_and_VC4_4c
LR_STS24c_and_VC4_8c
LR_Not_Applicable (if the L2 topology contains L1 SNCs with different layer rates or if the L2 topology contains mix of CCAT and VCAT L1 SNCs)
•
–
•
–
•
–
•
–
•
•
•
•
•
•
•
–
–
•
•
•
•
•
•
•
•
•
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INVALID_INPUT - Raised when a l2TopoType is invalid.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators that the EMS can support has been reached.Compliance
CTM-defined.
3.2.14 emsMgr::EMSMgr_I::getAllQoSTemplateNames
Synopsis
void getAllQoSTemplateNames( in unsigned long how_many,out globaldefs::NamingAttributesList_T qosTempNameList,out globaldefs::NamingAttributesIterator_I qosTempNameIt)raises(globaldefs::ProcessingFailureException);Description
This interface lists all QoSTemplate names in the EMS. The QoSTemplate has a scope in EMS.
CTM supports this operation only for ONS 15454 SONET and ONS 15454 SDH NEs.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators that the EMS can support has been reached.Compliance
CTM-defined.
3.2.15 emsMgr::EMSMgr_I::getAllQoSTemplates
Synopsis
void getAllQoSTemplatesin unsigned long how_many,out QoSTemplateList_T qosTempListout QoSTemplateIterator_I qosTempIt)raises(globaldefs::ProcessingFailureException);Description
This interface lists all QoSTemplate in the EMS. The QoSTemplate has a scope in EMS.
CTM supports this operation only for ONS 15454 SONET and ONS 15454 SDH NEs.
Parameters
CTM support for QoSTemplate structure is as follows:
•
•
•
–
–
–
•
•
–
–
Each QoSClass_T has the following members:
•
•
Classification_T.MATCH_ANY
Classification_T.MATCH_DSCP
Classification_T.MATCH_IP
Classification_T.MATCH_COS
string value—This field is a string value. Multiple values should be separated by spaces.
•
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
–
–
–
–
–
–
•
•
–
–
•
–
–
Note
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators that the EMS can support has been reached.Compliance
CTM-defined.
3.2.16 emsMgr::EMSMgr_I::getQoSTemplate
Synopsis
void getAllQoSTemplates(in globaldefs::NamingAttribute_T QoSTemplateName,out QoSTemplate_T qosTemp )raises(globaldefs::ProcessingFailureException);Description
This interface lists the complete QoSTemplate information given the QoSTemplate name. The QoSTemplate has a scope in EMS.
CTM supports this operation only for ONS 15454 SONET and ONS 15454 SDH NEs.
Parameters
qosTemplateName
globaldefs::NamingAttributes_T
In
QoS template name
qosTemp
QoSTemplate_T
Out
QoS template giving the complete information
For details on QoSTemplate_T structure, see emsMgr::EMSMgr_I::getAllQoSTemplateNames.
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when QoSTemplate name is not valid.EXCPT_ENTITY_NOT_FOUND - Raised when QoSTemplate name does not exist on the EMS.Compliance
CTM-defined.
3.2.17 emsMgr::EMSMgr_I::getAllEMSandMEClearedAlarms
Synopsis
void getAllEMSandMEClearedAlarms(in notifications::ProbableCauseList_T excludeProbCauseList,in notifications::PerceivedSeverityList_T excludeSeverityList,in unsigned long how_manyout notifications::EventList_T eventList,out notifications::EventIterator_I eventIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request all of the cleared and acknowledged alarms that are under the control of this EMS (both those raised by the NEs and those raised by the EMS itself). Some alarms may be filtered out (excluded) by specifying their probable causes or severities.
Due to performance concerns, this operation is restricted to enable only one OSS client to access it at one time. Otherwise, CTM throws EXCPT_UNABLE_TO_COMPLY exception.
The result of this operation is independent of the filtering set up by the NMS for the notification service.
ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15600 SDH, and ONS 15310
Cisco ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15600 SDH, and ONS 15310 do not send a "clear" for TCA events. Therefore, TCAs are not reported in the eventList that is returned by this method.
ONS 15540, ONS15530, and ONS 15501
TCAs are also reported in the eventList that is returned by this method as ONS 15540 sends a "clear" for threshold crossing alarms.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_UNABLE_TO_COMPLY - Raised when this method is being used by another OSS Client.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
CTM-defined.
3.2.18 emsMgr::EMSMgr_I::getAllEMSSystemClearedAlarms
Synopsis
void getAllEMSSystemClearedAlarms(in notifications::PerceivedSeverityList_T excludeSeverityList,in unsigned long how_manyout notifications::EventList_T eventList,out notifications::EventIterator_I eventIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request all of the cleared and acknowledged alarms that are for the EMS itself. Some alarms may be filtered out (excluded) by specifying their severities.
The result of this operation is independent of the filtering set up by the NMS for the notification service.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
CTM-defined.
3.2.19 emsMgr::EMSMgr_I::createServerTrailLink
Synopsis
void createServerTrailLink(in serverTrailLink::STLCreateData_T createDataout serverTrailLink::ServerTrailLink_T serverTrailLink)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to create a ServerTrail link manually between two ManagedElements. CTM supports the ServerTrail link creation between ManagedElements belonging to the same multiLayer subnetwork. CTM generates an ObjectCreation Event notification when a new ServerTrail link is created.
Note
Note
Parameters
CTM support for STLCreateData_T structure is as follows:
•
Not supported. The value of this field is assigned to the name of the newly created ServerTrailLink.
•
Not supported.
•
Not supported.
•
CTM will support only CD_BI for bidirectional links.
•
Supported layer rates are:
–
–
–
–
–
–
•
Supported.
•
Supported.
•
Supported. The supported parameters are listed in the table below.
•
Supported. This field holds the SRLG group values. This is an optional parameter you can include in the SRLG group during the Link creation. A maximum of five SRLG groups are supported for a given Link. SRLG groups are only supported for SONET/SDH serverTrailLinks.
CTM support for ServerTrailLink_T structure is as follows:
•
Supported. This field will have two tuples. The first tuple is for EMS. The second one is for ServerTrailLink. The value in the second tuple is the same as the nativeEMSName field.
•
Not supported.
•
Not supported
•
Not supported.
•
CTM will support only CD_BI for bidirectional links.
•
Supported layer rates are:
–
–
–
–
–
–
•
Supported. The CTP for the serverTrailLink aEnd.
•
Supported. The CTP for the serverTrailLink zEnd.
•
Supported. The supported parameters are listed in the table below.
•
Supported. This field holds the SRLG group values. This is an optional parameter you can include in the SRLG group during the link creation. A maximum of five SRLG groups are supported for a given link. SRLG groups are only supported for SONET/SDH serverTrailLinks.
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INVALID_INPUT - Raised if input createData is not valid.EXCPT_NOT_IMPLEMENTED - Raised if EMS cannot support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.Compliance
CTM-defined.
3.2.20 emsMgr::EMSMgr_I::deleteServerTrailLink
Synopsis
void deleteServerTrailLink(in globaldefs::NamingAttributes_T serverTrailLinkName)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to delete a serverTrail Link manually between two ManagedElements. CTM throws the EXCPT_UNABLE_TO_COMPLY exception if the server trail link cannot be deleted in the current state. CTM generates an ObjectDeletion Event notification when a serverTrail link is deleted.
This operation is supported for ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600 SONET, ONS 15600 SDH, and ONS 15310 NEs.
Parameters
serverTrailLinkName
globaldefs::NamingAttributes_T
In
The name of the serverTrail link to be deleted
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INVALID_INPUT - Raised if input serverTrail link name is invalid.EXCPT_ENTITY_NOT_FOUND - Raised if the specified serverTrail link name does not exist in CTM.EXCPT_NOT_IMPLEMENTED - Raised if EMS cannot support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_UNABLE_TO_COMPLY - Raised if attempt is made to delete a serverTrail which cannot be deleted.Compliance
CTM-defined.
3.2.21 emsMgr::EMSMgr_I::addManagedElement
Synopsis
void addManagedElement(in MEAdditionData_T neData)raises(globaldefs::ProcessingFailureException);Description
This operation enables the OSS to add a network element. All types of elements are supported except MGX and IOX.
Parameters
neData
MEAdditionData_T
in
Input data needed for the addition of the Network Element
The structure of MEAdditionalData_T is as follows:
struct MEAdditionData_T{MEModel model;string ipadd;string nwPartitionName;string multiLayerSubnetworkName;string neUsername;string nePasswd;string neLocationName;string neDescription;string snmpCommunityString;string neVendorName;boolean isGNE;};The description of each field is as follows:
enum MEModel{CISCO_ONS_15327, CISCO_ONS_15454, CISCO_ONS_15540_ESP, CISCO_ONS_15540_ESPx,CISCO_ONS_15530, CISCO_ONS_15501, CISCO_ONS_15800, CISCO_ONS_15801, CISCO_ONS_15808,CISCO_ONS_15454_SDH, CISCO_ONS_15216_EDFA2, CISCO_ONS_15216_OADM,CISCO_ONS_15216_DWDM_Filter, CISCO_ONS_15600, CISCO_ONS_15600_SDH, CISCO_ONS_15216_OSC,CISCO_ONS_15216_DCU, CISCO_ONS_15302, CISCO_ONS_15305, CISCO_ONS_15305_CTC,CISCO_ONS_15216_FlexLayer, Not_Managed_Other_Vendor, CISCO_ONS_15216_EDFA3,CISCO_ONS_15310_CL, CISCO_CRS_1, CISCO_XR_12000, CISCO_CAT_6509, CISCO_ONS_15216_EDFA1,CISCO_MDS_9000, CISCO_MGX_8880_8850, CISCO_ONS_15310MA,CISCO_7600};Throws
globaldefs::ProcessingFailureExceptionCompliance
CTM-defined.
3.2.22 emsMgr::EMSMgr_I::addNetworkPartition
Synopsis
void addNetworkPartition(in string name, in string description) raises(globaldefs::ProcessingFailureException);Description
This API enables the OSS to add a new network partition.
Parameters
name
string
In
Network partition name
description
string
In
Description for the new partition
Throws
globaldefs::ProcessingFailureExceptionCompliance
CTM-defined.
3.2.23 emsMgr::EMSMgr_I::addMultiLayerSubnetwork
Synopsis
void addMultiLayerSubnetwork(in MultiLayerSubnetworkData_T npData)raises(globaldefs::ProcessingFailureException);This API enables the OSS to add a new subnet partition.
Parameters
npData
MultiLayerSubnetworkData_T
—
—
in
Subnet partition data
—
—
The structure for SubNetworkPartitionData_T is as follows:
struct MultiLayerSubnetworkData_T{string name;string title;string userLabel;SubNetType_T type;SubnetToplogy_T topology;string npId;};The description of each parameter is as follows:
enum SubNetType_T{ SONET, SDH, OTHER, UNKNOWNSUBNETTYPE};enum SubnetToplogy_T{OTHER_SUBNET_TYPE, POINT_TO_POINT, LINEAR, UPSR, SNC, BLSR, MSSP, OPEN_UPSR, OPEN_SNC, HYBRID, MESH, SINGLETON, UNKNOWN_SUBNET_TYPE};Throws
globaldefs::ProcessingFailureExceptionCompliance
CTM-defined.
3.2.24 emsMgr::EMSMgr_I::deleteAndPurgeManagedElement
Synopsis
boolean deleteAndPurgeManagedElement(in string neName) raises(globaldefs::ProcessingFailureException);Description
This API enables the OSS to delete a NE.
Parameters
Throws
globaldefs::ProcessingFailureExceptionCompliance
CTM-defined.
3.2.25 emsMgr::EMSMgr_I::deleteNetworkPartition
Synopsis
void deleteNetworkPartition(in string name) raises(globaldefs::ProcessingFailureException);This API enables the OSS to delete an existing network partition.
Parameters
Throws
globaldefs::ProcessingFailureExceptionCompliance
CTM-defined.
3.2.26 emsMgr::EMSMgr_I::deleteMultiLayerSubnetwork
Synopsis
void deleteMultiLayerSubnetwork(in string subnetworkName)raises(globaldefs::ProcessingFailureException);Description
This API enables the OSS to delete an existing network partition.
Parameters
Throws
globaldefs::ProcessingFailureExceptionCompliance
CTM-defined.
3.2.27 emsMgr::EMSMgr_I::addSWVersion
Synopsis
void addSWVersion (in SoftwareVersionTable_T versionData) raises(globaldefs::ProcessingFailureException);Description
This API enables the OSS to add a new software version to the supported NE version table.
Parameters
versionData
SoftwareVersionTable_T
In
The input details for the addition of a new software version
struct SoftwareVersionTable_T{NEModel model;string olderSWVersion;string newSWVersion;string versionName;};Throws
globaldefs::ProcessingFailureExceptionCompliance
CTM-defined.
3.2.28 emsMgr::EMSMgr_I::getAllSupportedMESoftwareVersions
Synopsis
void getAllSupportedMESoftwareVersions(in unsigned long how_many,out SupportedMESoftwareVersionList_T versionList,out SupportedMESoftwareVersionIterator_I versionIt)raises(globaldefs::ProcessingFailureException);Description
This API enables the OSS to add a new software version to the supported NE version table.
Parameters
struct SupportedMESoftwareVersion_T{string model;string swversion;string versionName;};typedef sequence<SupportedMESoftwareVersion_T> SupportedMESoftwareVersionList_T;interface SupportedMESoftwareVersionIterator_I{boolean next_n(in unsigned long how_many,out SupportedMESoftwareVersionList_T neVersionList)raises (globaldefs::ProcessingFailureException);unsigned long getLength()raises(globaldefs::ProcessingFailureException);void destroy()raises(globaldefs::ProcessingFailureException);};Throws
globaldefs::ProcessingFailureExceptionCompliance
CTM-defined.
3.3 emsSession::EmsSession_I
The emsSession module enables the client to query the EMS to determine the manager interfaces the EMS is supporting. The NMS retrieves an instance of the needed manager interface objects. This interface is inherited from session::Session_I.
interface EmsSession_I:session::Session_I3.3.1 emsSession::EmsSession_I::getEventChannel
Synopsis
void getEventChannel(out CosNotifyChannelAdmin::EventChannel eventChannel)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to access the event channel to receive notifications. CTM publishes the name of the notification channel through the naming service. You can use the naming service to get the corresponding object reference.
Parameters
eventChannel
CosNotifyChannelAdmin::EventChannel
Out
Event channel that the NMS uses
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - This exception indicates a non-specific internal EMS failure.Compliance
TMF-defined.
3.3.2 emsSession::EmsSession_I::getManager
Synopsis
void getManager(in string managerName,out common::Common_I managerInterface)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to access the specified manager interface.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_NOT_IMPLEMENTED - This exception indicates that the EMS does not support the manager.EXCPT_INTERNAL_ERROR - This exception indicates a non-specific internal EMS failure.Compliance
TMF-defined.
3.3.3 emsSession::EmsSession_I::getSupportedManagers
Synopsis
void getSupportedManagers(out managerNames_T supportedManagerList)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request the manager interfaces that the EMS implements.
Parameters
Throws
None.
Compliance
TMF-defined.
3.4 emsSessionFactory::EmsSessionFactory_I
A single instance of the EmsSessionFactory_I is the entry point to the EMS. The NMS uses this object reference to connect to CTM. This interface implements the version interface and returns the server IDL version. It is inherited from mtnmVersion::Version_I.
interface EmsSessionFactory_I:mtnmVersion::Version_I3.4.1 emsSessionFactory::EmsSessionFactory_I::getEmsSession
Synopsis
void getEmsSession(in string user,in string password,in nmsSession::NmsSession_I client,out emsSession::EmsSession_I emsSessionInterface)raises(globaldefs::ProcessingFailureException);Description
This operation enables the NMS to obtain the EmsSession_I object, which contains all managers of the EMS.
CTM allows 4 to 25 concurrent login sessions and as many user profiles as required for configuring the number of concurrent login sessions. See B.8 Location of Naming Service IOR File, page B-6 for configuring the number of concurrent login sessions. The username and password must contain between 1 and 53 characters.
This operation can also accept the encrypted username and password. To enable encryption on the username and password, check the Enable encryption for username and password check box in the CTM client Control Panel for the CTM Gateway/CORBA service. CTM then decrypts the username and password accordingly.
To encrypt the username and password, you must use the RSA algorithm with the public key or the public key pair provided by CTM. To obtain the CTM public key, use the emsSessionFactory::EmsSessionFactory_I::getEmsPublicKey API. To obtain the CTM public key pair, use the emsSessionFactory::EmsSessionFactory_I::getEmsPublicKeyPair API.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of a non-specific internal EMS failure.EXCPT_INVALID_INPUT - Raised when client is invalid or when the length of User name or Password passed is not within the permissible limits (1-53).EXCPT_ACCESS_DENIED - Raised in the following cases:When all the eight login sessions are used up.When the user name specified does not exist.Or in case of any other security violation.Compliance
TMF-defined.
3.4.2 emsSessionFactory::EmsSessionFactory_I::getEmsPublicKey
Synopsis
void getEmsPublicKey(out string publicKey)raises(globaldefs::ProcessingFailureException);Description
This operation enables the NMS to obtain the string representation of the RSA public key encoded in the Base64 encoding scheme. The operation encrypts the username and password from the string representation of the RSA public key.
The OSS client must use the Base64 decoders to decode the public key and get the byte[] of the public key from the decoded public key string. The byte[] corresponding to the public key represents the key in its primary encoded format; in this case, X.509 SubjectPublicKeyInfo.
You can create the RSA public key using this byte array and cryptographic libraries. Use this key to encrypt the username and password. Bouncy Castle Provider is an example of a security provider that you can use to create the RSApublic key.
The public key is then used to encrypt the username and password. Before passing the encrypted password to CTM for login, the OSS client must encode the encrypted username and password using the Base64 encoder to get the string equivalent of the encrypted data.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.Compliance
CTM-defined.
3.4.3 emsSessionFactory::EmsSessionFactory_I::getEmsPublicKeyPair
Synopsis
void getEmsPublicKeyPair(out string publicKeyModulus,out string publicKeyExponent)raises(globaldefs::ProcessingFailureException);Description
This operation enables the NMS to obtain the string representation of the RSA public key pair (in the modulus and exponent forms) from CTM for encrypting the username and password.
The OSS client must convert the string representation of the public key modulus and public key exponent into a nonnegative integer and create an RSA public key using cryptographic libraries. Crypto++ is one of the security providers available.
Before passing the encrypted password to CTM for login, the OSS client must use the Base64 encoder to encode the encrypted username and password. This provides the string equivalent of the encrypted data.
Parameters
publicKeyModulus
string
Out
The public key modulus string returned by CTM.
publicKeyExponent
string
Out
The public key exponent string returned by CTM.
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.Compliance
CTM-defined.
3.5 equipment::EquipmentInventoryMgr_I
This interface accesses operations that deal with equipment. A handle to an instance of this interface is gained through the getManager operation in emsSession. This interface is inherited from common::Common_I.
interface EquipmentInventoryMgr_I:common::Common_IThis interface implements the getCapabilities method. Operations described in the following sections are returned to the NMS when it invokes getCapabilities.
3.5.1 equipment::EquipmentInventoryMgr_I::getAllEquipment
Synopsis
void getAllEquipment(in globaldefs::NamingAttributes_T meOrHolderName,in unsigned long how_many,out EquipmentOrHolderList_T eqList,out EquipmentOrHolderIterator_I eqIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request all of the equipment and equipment holders contained in a managed element or equipment holder.
Parameters
The EqList parameter contains a sequence of the EquipmentOrHolder_T data type, which is defined as the union of Equipment_T and EquipmentHolder_T.
CTM support forEquipment_T is as follows:
•
–
•
–
•
–
•
–
•
–
•
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
•
–
•
–
•
–
•
–
CTM support for EquipmentHolder_T is as follows:
•
–
•
–
•
–
•
–
•
–
•
–
–
–
–
–
–
–
•
–
•
–
–
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
G1000_4
(Only when XC10G is installed in slot 8 or 10)
1, 2, 3, 4, 14, 15, 16, 17
OC12_4
(Only when XC10G is installed in slot 8 or 10)
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
TXP_G1000_41
1 The same physical card as was supported in the previous release, but with a different software image.
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
FCMR, OSC_CSM, OPT_BST, OPT_PRE, MUX_DMX4, AD_1B, AD_1C, AD_2C, AD_4B, AD_4C, TXPP_MR_2.5G, TXP_MR_2.5G
1, 2, 3, 4, 5, 12, 13, 14, 15, 16
MUX32_O, DMX32_O1
8, 10
OSCM
1, 2, 4, 5, 6, 12, 13, 14, 16, 17
DS3I
3, 15
DS3I, DS3IN
1 These cards occupy two slots, hence they can be provisioned only when the two subsequent slots are empty. Among the two subsequent slots, the first slot should be mentioned for provisioning these cards.
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
FCMR, OSC_CSM, OPT_BST, OPT_PRE, MUX_DMX4, AD_1B, AD_1C, AD_2C, AD_4B, AD_4C, TXPP_MR_2.5G, TXP_MR_2.5G, 2.5G SP-Datamux xx.xx, 2.5G UP-Datamux xx.xx, DS3XM_12, DS3_EC1_48, ML2_EXIGE, TXP_MR_10E, MXP_2.5G_10E, 2.5G_DM, 2.5G_DMP
1, 2, 3, 4, 5, 12, 13, 14, 15, 16
MUX32_O, DMX32_O, WSS_32, DMX32_R1
8, 10
OSCM
7, 11
TCC2P
1 These cards occupy two slots, hence they can be provisioned only when the two subsequent slots are empty. Among the two subsequent slots, the first slot should be mentioned for provisioning these cards.
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
FCMR, OSC_CSM, OPT_BST, OPT_PRE, MUX_DMX4, AD_1B, AD_1C, AD_2C, AD_4B, AD_4C, TXPP_MR_2.5G, TXP_MR_2.5G, 2.5G SP-Datamux xx.xx, 2.5G UP-Datamux xx.xx, DS3XM_12, DS3_EC1_48, ML2_EXIGE, TXP_MR_10E, MXP_2.5G_10E, 2.5G_DM, 2.5G_DMP, 2.5-10G_Muxponder, 10G_MR_Transponder, OPT_BST_E
1, 2, 3, 4, 5, 12, 13, 14, 15, 16
MUX32_O, DMX32_O, WSS_32, DMX32_R1
8, 10
OSCM
7, 11
TCC2P
1 These cards occupy two slots, hence they can be provisioned only when the two subsequent slots are empty. Among the two subsequent slots, the first slot should be mentioned for provisioning these cards.
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
FCMR, OSC_CSM, OPT_BST, OPT_PRE, MUX_DMX4, AD_1B, AD_1C, AD_2C, AD_4B, AD_4C, TXPP_MR_2.5G, TXP_MR_2.5G, 2.5G SP-Datamux xx.xx, 2.5G UP-Datamux xx.xx, DS3XM_12, DS3_EC1_48, ML2_EXIGE, TXP_MR_10E, MXP_2.5G_10E, 2.5G_DM, 2.5G_DMP, DS1_E1_56, MRC_12,OPT_BST_E, 2.5-10G_Muxponder, 10G_MR_Transponder
1, 2, 3, 4, 5, 12, 13, 14, 15, 16
MUX32_O, DMX32_O, WSS_32, DMX32_R1
8, 10
OSCM, XCVXC, XCVXC25G
7, 11
TCC2P
5, 6, 12, 13
OC192_XFP
1 These cards occupy two slots, hence they can be provisioned only when the two subsequent slots are empty. Among the two subsequent slots, the first slot should be mentioned for provisioning these cards.
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
G1000_41
1 Same physical card as supported in previous release but with different software image
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
FCMR, OSC_CSM, OPT_BST, OPT_PRE, MUX_DMX4, AD_1B, AD_1C, AD_2C, AD_4B, AD_4C, TXPP_MR_2.5G, TXP_MR_2.5G
1, 2, 3, 4, 5, 12, 13, 14, 15, 16
MUX32_O, DMX32_O1
8, 10
OSCM
1 These cards occupy two slots, hence they can be provisioned only when the two subsequent slots are empty. Amount the two subsequent slots, the first slot should be mentioned for provisioning these cards.
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
FCMR, OSC_CSM, OPT_BST, OPT_PRE, MUX_DMX4, AD_1B, AD_1C, AD_2C, AD_4B, AD_4C, TXPP_MR_2.5G, TXP_MR_2.5G, SP-Datamux xx.xx, 2.5G UP-Datamux xx.xx, TXP_MR_10E, MXP_2.5G_10E, 2.5G_DM, 2.5G_DMP
1, 2, 3, 4, 5, 12, 13, 14, 15, 16
MUX32_O, DMX32_O, WSS_32, DMX32_R1
8, 10
OSCM
1 These cards occupy two slots, hence they can be provisioned only when the two subsequent slots are empty. Amount the two subsequent slots, the first slot should be mentioned for provisioning these cards.
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
FCMR, OSC_CSM, OPT_BST, OPT_PRE, MUX_DMX4, AD_1B, AD_1C, AD_2C, AD_4B, AD_4C, TXPP_MR_2.5G, TXP_MR_2.5G, SP-Datamux xx.xx, 2.5G UP-Datamux xx.xx, TXP_MR_10E, MXP_2.5G_10E, 2.5G_DM, 2.5G_DMP, 2.5-10G_Muxponder, 10G_MR_Transponder, OPT_BST_E
1, 2, 3, 4, 5, 12, 13, 14, 15, 16
MUX32_O, DMX32_O, WSS_32, DMX32_R1
8, 10
OSCM
1 These cards occupy two slots, hence they can be provisioned only when the two subsequent slots are empty. Amount the two subsequent slots, the first slot should be mentioned for provisioning these cards.
1, 2, 3, 4, 5, 6, 12, 13, 14, 15, 16, 17
FCMR, OSC_CSM, OPT_BST, OPT_PRE, MUX_DMX4, AD_1B, AD_1C, AD_2C, AD_4B, AD_4C, TXPP_MR_2.5G, TXP_MR_2.5G, SP-Datamux xx.xx, 2.5G UP-Datamux xx.xx, TXP_MR_10E, MXP_2.5G_10E, 2.5G_DM, 2.5G_DMP, MRC_12, OPT_BST_E, 2.5-10G_Muxponder, 10G_MR_Transponder
1, 2, 3, 4, 5, 12, 13, 14, 15, 16
MUX32_O, DMX32_O, WSS_32, DMX32_R1
8, 10
OSCM, XCVXC, XCVXC25G
5, 6, 12, 13
STM64_XFP
1, 2, 3, 4, 5, 13, 14, 15, 16, 17
DS1I
18, 19, 20, 21, 22, 30, 31, 32, 33, 34
FMEC_SMZ_DS1I
1 These cards occupy two slots, hence they can be provisioned only when the two subsequent slots are empty. Amount the two subsequent slots, the first slot should be mentioned for provisioning these cards.
ONS 15327 supports the following value for all releases:
151
CMP-W, CMP-W-S, CMP-W-2E, CMP-W-2E-S
13-142
LSM-W
163
IOC-W
17
SCF-W and BAT
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
For any other supported module, see 2.2.5.6.17 ONS 15800 and ONS 15801, page 2-63
1 This constraint applies if the shelf contains a module of the specified kind. If the shelf does not contain such a module, any other supported module (see 2.2.5.6.17 ONS 15800 and ONS 15801, page 2-63) can be inserted into the slot.
2 Same as (1).
3 Same as (1).
ONS 15801 supports the following values
131
CMP-W, CMP-W-S, CMP-W-2E, CMP-W-2E-S
11-12 (see (1) below)
LSM-W
14 (see (1) below)
IOC-W
15
SCF-W and BAT
1, 2, 3, 4, 5, 6, 7, 8, 9, 10
For any other supported module, see 2.2.5.6.17 ONS 15800 and ONS 15801, page 2-63
1 This constraint applies if the shelf contains a module of the specified kind. If the shelf does not contain such a module, any other supported module (see 2.2.5.6.17 ONS 15800 and ONS 15801, page 2-63) can be inserted into the slot
ONS 15808 supports the following values
131
CMP, CMP-S
11-121
OSCM
141
AIU
15
SCU and PL
1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Any other supported module (see 2.2.5.6.18 ONS 15808, page 2-65)
1 This constraint applies if the shelf contains a module of the specified kind. If the shelf does not contain such a module, any other supported module (see 2.2.5.6.18 ONS 15808, page 2-65) can be inserted into the slot.
ONS 15302 supports the following values
ONS 15305 and ONS 15305 CTC support the following values:
1, 2, 3, 4
All equipment listed in 2.2.5.6.6 ONS 15305 and ONS 15305 CTC, page 2-54
ONS 15216 supports the following values
ONS 15600 support the following values:
5, 10
TXC
6/7, 8/9
CXC
1, 2, 3, 4, 11, 12, 13, 14
OC48_16, OC192_4
5, 10
TXC
6/7, 8/9
SSXC [new cross-connect card]
1, 2, 3, 4, 11, 12, 13, 14
OC48_16, OC192_4, OC48_32
1, 2, 3, 4, 11, 12, 13, 14
ASAP
5, 10
TXC
6/7, 8/9
CXC
1, 2, 3, 4, 11, 12, 13, 14
STM16_16, STM64_4
3, 4
CTX-2500 and CTX-FILLER
1, 2, 5, 6
DS1-84/DS3-EC1-3, DS1-28/DS3-EC1-3, and DS3-EC-6
1, 2, 5, 6
CE-100T-8, ML2-100T-8, and EXP-FILLER
Compliance
TMF-defined.
3.5.2 equipment::EquipmentInventoryMgr_I::getAllEquipmentNames
Synopsis
void getAllEquipmentNames(in globaldefs::NamingAttributes_T meOrHolderName,in unsigned long how_many,out globaldefs::NamingAttributesList_T nameList,out globaldefs::NamingAttributesIterator_I nameIt)raises(globaldefs::ProcessingFailureException);Description
This operation has exactly the same behavior as the operation described in equipment::EquipmentInventoryMgr_I::getAllEquipment, but returns the object names instead of returning the entire object.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when meOrHolderName does not reference a managed element or an equipment holder.EXCPT_ENTITY_NOT_FOUND - Raised when managedElementOrEquipmentName references object which does not exist.EXCPT_NE_COMM_LOSS - Raised when communications to managedElement is lost.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.5.3 equipment::EquipmentInventoryMgr_I::getAllSupportedPTPs
Synopsis
void getAllSupportedPTPs(in globaldefs::NamingAttributes_T equipmentName,in unsigned long how_many,out terminationPoint::TerminationPointList_T tpList,out terminationPoint::TerminationPointIterator_I tpIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request the PTPs that are directly supported by specific equipment. The PTPs that are returned are those that share their physical layer with the primary equipment (that is, they represent a port on the equipment or are connected by a fiber, wire, and so on).
If the equipment is protection equipment in a 1_FOR_N protection group, CTM reports only the AlarmReporting for the LayeredParameters of the supported PTPs.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Parameters
CTM support for TerminationPoint_T structure is as follows:
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
CTM supports the following parameters for PTP
Note
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when equipmentName does not reference an equipment object.EXCPT_ENTITY_NOT_FOUND - Raised when equipmentName references object that does not exist.EXCPT_NE_COMM_LOSS - Raised when communications to managedElement is lost.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.5.4 equipment::EquipmentInventoryMgr_I::getAllSupportedPTPNames
Synopsis
void getAllSupportedPTPNames(in globaldefs::NamingAttributes_T equipmentName,in unsigned long how_many,out globaldefs::NamingAttributesList_T nameList,out globaldefs::NamingAttributesIterator_I nameIt)raises(globaldefs::ProcessingFailureException);Description
This operation has exactly the same behavior as the operation described in equipment::EquipmentInventoryMgr_I::getAllSupportedPTPs, but returns the object names instead of returning the entire objects.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when equipmentName does not reference an equipment object.EXCPT_ENTITY_NOT_FOUND - Raised when equipmentName references object that does not exist.EXCPT_NE_COMM_LOSS - Raised when communications to managedElement is lost.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when the maximum number of iterators (128) has been reached.Compliance
TMF-defined.
3.5.5 equipment::EquipmentInventoryMgr_I::getAllSupportingEquipment
Synopsis
void getAllSupportingEquipment(in globaldefs::NamingAttributes_T ptpName,out EquipmentOrHolderList_T eqList)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request the equipment that contains this PTP.
Parameters
EquipmentOrHolderList_T is a list of EquipmentOrHolder_T, which is defined as a union of Equipment_T and EquipmentHolder_T structures. For further details on both structures, see equipment::EquipmentInventoryMgr_I::getAllEquipment.
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when ptpName does not reference a PTP object.EXCPT_ENTITY_NOT_FOUND - Raised when ptpName references a PTP object that does not exist.EXCPT_NE_COMM_LOSS - Raised when communications to managedElement is lost.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.5.6 equipment::EquipmentInventoryMgr_I::getAllSupportingEquipment
NamesSynopsis
void getAllSupportingEquipmentNames(in globaldefs::NamingAttributes_T ptpName,out globaldefs::NamingAttributesList_T nameList)raises(globaldefs::ProcessingFailureException);Description
This operation has exactly the same behavior as the operation described in equipment::EquipmentInventoryMgr_I::getAllSupportingEquipment, but returns the object names instead of returning the entire objects.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when ptpName does not reference a PTP object.EXCPT_ENTITY_NOT_FOUND - Raised when ptpName references a PTP object that does not exist.EXCPT_NE_COMM_LOSS - Raised when communication to managedElement is lost.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.5.7 equipment::EquipmentInventoryMgr_I::getContainedEquipment
Synopsis
void getContainedEquipment(in globaldefs::NamingAttributes_T equipmentHolderName,out EquipmentOrHolderList_T equipmentOrHolderList)raises(globaldefs::ProcessingFailureException);Description
This operation returns the equipment and equipment holders that a specific equipment holder contains. This operation differs from getAllEquipment in that it looks only at the next level of the containment hierarchy.
Parameters
EquipmentOrHolderList_T is a list of EquipmentOrHolder_T, which is defined as a union of Equipment_T and EquipmentHolder_T structures. For further details on both structures, see equipment::EquipmentInventoryMgr_I::getAllEquipment.
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when equipmentHolderName does not reference an equipment holder object.EXCPT_ENTITY_NOT_FOUND - Raised when equipmentHolderName references an equipment holder that does not exist.EXCPT_NE_COMM_LOSS - Raised when communications to managedElement is lost.Compliance
TMF-defined.
3.5.8 equipment::EquipmentInventoryMgr_I::getEquipment
Synopsis
void getEquipment(in globaldefs::NamingAttributes_T equipmentOrHolderName,out EquipmentOrHolder_T equip)raises(globaldefs::ProcessingFailureException);Description
This service returns the equipment or equipment holder for specific equipment or equipment holder name.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when equipmentOrHolderName does not reference an equipment or an equipment holder.EXCPT_ENTITY_NOT_FOUND - Raised when equipmentOrHolderName references an equipment or equipment holder that does not exist.EXCPT_NE_COMM_LOSS - Raised when communication to managedElement is lost.Compliance
TMF-defined.
3.5.9 equipment::EquipmentInventoryMgr_I::provisionEquipment
Synopsis
void provisionEquipment(in EQTCreateData_T equipmentCreateData,out Equipment_T createdEquipment)raises(globaldefs::ProcessingFailureException);Description
This operation enables the NMS to permanently provision a piece of equipment in an equipment holder in an ME. The result of this operation is the creation of the equipment object and all its related objects, such as TPs. The resulting object is returned.
The equipment holder that contains the equipment must exist. The equipment object can already exist, but the equipment holder must not have expected equipment already provisioned.
If the equipment is provisioned successfully, CTM generates a StateChangeEvent on the holder state change and an ObjectCreationEvent for the equipment, and pushes them to the event channel.
It is important to note that Cisco ONS 15454 SONET detects new equipment and provisions it automatically, provided that the equipment holder (slot) is empty and not preprovisioned for another module type.
The equipment must be from the acceptableEquipmentTypeList of the slots. If these slots are selected to provision any other type of card, CTM returns the EXCPT_UNABLE_TO_COMPLY exception.
PPMs and PIMs can also be provisioned using this interface.
It is not necessary to know the subtypes of the OC-n card at the time of provisioning. When equipment is actually installed, CTM reports the subtype in the name field of the equipment.
In ONS 15600 SONET and ONS 15600 SDH, each CXC or SSXC card occupies two slots (slots 6 and 7 or slots 8 and 9), and the NMS can specify any one of the slots to provision a CXC or SSXC card.
This operation is supported only for the ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15310 CL, ONS 15310 MA, ONS 15600, and ONS 15600 SDH.
Parameters
equipmentCreateData
EQTCreateData_T
In
Data that describes the equipment to create
createdEquipment
Equipment_T
Out
The resulting created equipment
CTM support for EQTCreateData_T structure is as follows:
•
–
•
–
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_OBJECT_IN_USE - Raised when the equipment holder already has an expected equipment.EXCPT_INVALID_INPUT - Raised when equipmentHolder does not reference an equipmentHolder object.EXCPT_ENTITY_NOT_FOUND - Raised when equipmentHolder references an object that does not exist.EXCPT_UNABLE_TO_COMPLY - Raised when the equipment cannot be created at the NE.EXCPT_NE_COMM_LOSS - Raised when communication to managedElement is lost.Compliance
TMF-defined.
3.5.10 equipment::EquipmentInventoryMgr_I::setAlarmReportingOff
Synopsis
void setAlarmReportingOff(in globaldefs::NamingAttributes_T equipmentOrHolderName)raises(globaldefs::ProcessingFailureException);Description
This operation disables alarm reporting on a piece of equipment. The CTM sends a warning alarm notification if successful.
This operation is supported for ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15600 SDH, ONS 15310 MA, and ONS 15310 CL.
Parameters
equipmentOrHolderName
Globaldefs::NamingAttributes_T
In
The equipment on which to deactivate alarm reporting
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when equipmentOrHolderName does not reference an equipment or holder.EXCPT_ENTITY_NOT_FOUND - Raised when equipmentOrHolderName references an object that does not exist.EXCPT_UNABLE_TO_COMPLY - Raised when alarm reporting cannot be disabled for the equipment or holder.EXCPT_NE_COMM_LOSS - Raised when communication to managedElement is lost.Compliance
TMF-defined.
3.5.11 equipment::EquipmentInventoryMgr_I::setAlarmReportingOn
Synopsis
void setAlarmReportingOn(in globaldefs::NamingAttributes_T equipmentOrHolderName)raises(globaldefs::ProcessingFailureException);Description
This operation enables alarm reporting on a piece of equipment.
The default setting for alarmReporting is "on." If the alarmReporting status is off, it indicates that a warning alarm has been raised for it. CTM generates a cleared warning alarm if successful.
This operation is supported for the ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15600 SDH, ONS 15310 MA, and ONS 15310 CL.
Parameters
equipmentOrHolderName
globaldefs::NamingAttributes_T
In
The equipment on which to activate alarm reporting
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Rraised when equipmentOrHolderName does not reference an equipment or holder.EXCPT_ENTITY_NOT_FOUND - Raised when equipmentOrHolderName references an object that does not exist.EXCPT_UNABLE_TO_COMPLY - Raised when alarm reporting cannot be disabled for the equipment or holder.EXCPT_NE_COMM_LOSS - Raised when communication to managedElement is lost.Compliance
TMF-defined.
3.5.12 equipment::EquipmentInventoryMgr_I::unprovisionEquipment
Synopsis
void unprovisionEquipment(in globaldefs::NamingAttributes_T equipmentName)raises(globaldefs::ProcessingFailureException);Description
This operation enables the NMS to permanently unprovision equipment from the managed element. The successful result of this operation is the potential deletion of the equipment object and all its related objects, such as termination points.
ONS 15454 SONET does not allow a user to unprovision a piece of equipment that is in use (SNC is created on this equipment). However, if the equipment is present in the slot and not in use, it can be unprovisioned. If the equipment is not physically removed from the slot and new equipment is not provisioned in the same slot, the NE redetects the equipment in approximately one minute. If the equipment is not physically removed from the slot and new equipment of a different type is provisioned in the same slot, the NE generates an equipment mismatch alarm.
If the equipment is unprovisioned successfully, CTM generates a StateChangeEvent on the holder state change and an ObjectDeletionEvent for the equipment, and pushes them to the event channel.
ONS 15454 reserves Slot 7 and 11 for TCC. One of these slots will have an IN SERVICE TCC card. If the NMS invokes unprovisionEquipment on this equipment, CTM throws the EXCPT_UNABLE_TO_COMPLY exception.
This operation is supported only for the ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15310 MA, ONS 15600 SDH, and ONS 15310 CL.
Parameters
equipmentName
globaldefs::NamingAttributes_T
In
The name of the equipment to be unprovisioned
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when equipmentName does not reference an equipment object.EXCPT_OBJECT_IN_USE - Deletion is rejected because equipment resources are in use.EXCPT_ENTITY_NOT_FOUND - Raised when equipmentName references an object that does not exist.EXCPT_UNABLE_TO_COMPLY - Raised when the equipment cannot be unprovisioned at the NE.EXCPT_NE_COMM_LOSS - Raised when communication to managedElement is lost.Compliance
TMF-defined.
3.5.13 equipment::EquipmentInventoryMgr_I::configureMLParameters
Synopsis
void configureMLParameters(in globaldefs::NamingAttributes_T equipmentOrHolderName,in globaldefs::NVSList_T paramListraises(globaldefs::ProcessingFailureException);Description
This operation enables provisioning of fast Ethernet and POS configuration parameters on the ML cards. The operation is performed on a best-effort basis and CTM will not validate the parameter names and the values being passed to the API.
If the operation is unsuccessful, CTM throws a ProcessingFailureException.
This operation enables the user to configure the following POS parameters:
•
•
•
Note
•
•
•
–
–
–
–
•
•
•
–
•
•
•
Note
This operation is supported only on ML cards.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failureEXCPT_INVALID_INPUT - Raised when equipmentOrHolderName does not reference a valid objectEXCPT_ENTITY_NOT_FOUND - Raised when equipmentOrHolderName references an object that does not existEXCPT_NE_COMM_LOSS - Raised when communications to the managed element is lostEXCPT_UNABLE_TO_COMPLY - Raised when CTM fails to configure the ML card parameters as requested.Compliance
CTM-defined.
3.6 maintenanceOps::MaintenanceManager_I
MaintenanceMgr_I is used as a handle to gain access to the maintenance operation. A handle to an instance of this interface is gained through the getManager operation in emsSession.
interface MaintenanceMgr_I:common::Common_IThis interface also implements the getCapabilities method. Operations described in the following subsections are returned to the NMS when it invokes getCapabilities.
3.6.1 maintenanceOps::MaintenanceMgr_I::getActiveMaintenanceOperations
Synopsis
void getActiveMaintenanceOperations(in globaldefs::NamingAttributes_T tpOrMeName,in unsigned long how_many,out CurrentMaintenanceOperationList_TcurrentMaintenanceOpeationList,out CurrentMaintenanceOperationIterator_I cmoIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables the NMS to query the EMS to determine if any persistent maintenance commands have been invoked. This query is supported for the PTP, CTP, or ME object.
This operation is supported only for ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15600 SDH, ONS 15310 MA, and ONS 15310 CL.
Parameters
CTM support for CurrentMaintenanceOperation structure is as follows:
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_NOT_IMPLEMENTED - Raised if EMS does not support this service.EXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when tpOrMeName does not reference a valid object.EXCPT_ENTITY_NOT_FOUND - Raised when tpOrMeName references an object that does not exist.EXCPT_NE_COMM_LOSS - Raised when communication to the ME is lost.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.6.2 maintenanceOps::MaintenanceMgr_I::performMaintenanceOperation
Synopsis
void performMaintenanceOperation(in CurrentMaintenanceOperation_T maintenanceOperation,in MaintenanceOperationMode_T maintenanceOperationMode)raises(globaldefs::ProcessingFailureException);Description
This operation enables the NMS to operate and release the maintenance commands that are supported by a TP.
This operation is only supported for the ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15600 SDH, ONS 15310 MA, and ONS 15310 CL.
ONS 15310 CL and ONS 15310 MA
CTM supports only terminal and facility loopback operations for electrical and OCn PTPs.
CTM does not support loopback operations for CTPs.
ONS 15327 SONET
CTM supports only terminal and facility loopback operations for DSn and OCn PTPs.
CTM does not support loopback operations for CTPs.
For NE Release 3.4 or later of the ONS 15327 SONET, the loopback state can be set only if the TP state is either Out of Service-Maintenance or Auto in Service.
ONS 15454 SDH
CTM supports only terminal and facility loopback operations for PTPs.
CTM does not support loopback operations for CTPs.
For NE Release 3.4 or later of the ONS 15454, the loopback state can be set only if the TP state is either Out of Service-Maintenance or Auto in Service.
ONS 15454 SONET
CTM supports only terminal and facility loopback operations for DSn, OCn, EC1, 10G-transponder, 10G-muxponder, and G1000_4 (NE release 4.1 and later) PTPs.
Only facility loopback is supported for DS1 CTPs on DX3XM cards.
Only terminal loopback is supported on G1000_4 for NE releases earlier than R4.1.
For NE Release 3.4 or later of the ONS 15454 SONET, the loopback state can be set only if the TP state is either Out of Service-Maintenance or Auto in Service.
ONS 15600 SDH
CTM supports only terminal and facility loopback operations for PTPs.
CTM does not support loopback operations for CTPs.
Loopback is supported only in the Out of Service-Maintenance state of the PTP.
CTM ignores the MaintenanceOperation_T value in CurrentMaintenanceOperation_T structure, if MaintenanceOperationMode_T is set to MOM_RELEASE.
ONS 15600 SONET
CTM supports only facility and payload loopback operations for PTPs.
CTM does not support loopback operations for CTPs.
Loopback is supported only in the Out of Service-Maintenance state of the PTP.
CTM ignores the MaintenanceOperation_T value in CurrentMaintenanceOperation_T structure, if MaintenanceOperationMode_T is set to MOM_RELEASE.
Parameters
CTM support for CurrentMaintenanceOperation_T structure is as follows:
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when tpName does not reference a TP.EXCPT_ENTITY_NOT_FOUND - Raised when tpName references an object that does not exist.EXCPT_UNABLE_TO_COMPLY - Raised when the operation is denied by the ME.EXCPT_NE_COMM_LOSS - Raised when communication to managedElement is lost.Compliance
TMF-defined.
3.7 managedElementManager::ManagedElementManager_I
This interface accesses operations that deal with MEs and TPs. A handle to an instance of this interface is gained through the getManager operation in emsSession.
interface ManagedElementManager_I:common::Common_IThis interface also implements the getCapabilities method. Operations described in the following sections are returned to the NMS when it invokes getCapabilities.
3.7.1 managedElementManager::ManagedElementManager_I::getAllActiveAlarms
Synopsis
void getAllActiveAlarms(in globaldefs::NamingAttributes_T meName,in notifications::ProbableCauseList_T excludeProbCauseList,in notifications::PerceivedSeverityList_T excludeSeverityList,in unsigned long how_many,out notifications::EventList_T eventList,out notifications::EventIterator_I eventIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request all active alarms for the specified ME, excluding alarms that the ME does not report to CTM. Some alarms can be filtered out (excluded) by specifying their probable causes or severities.
The result of this operation is independent of the filtering set up by the NMS for the notification service.
ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15600 SDH, and ONS 15310 CL
The ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600 and ONS 15600 SDH do not send a "clear" for TCA events. TCAs are not reported in the eventList that is returned by this method.
ONS 15540, ONS 15530, and ONS 15501
TCAs are also reported in the eventList returned by this method as ONS 15540, ONS 15530, and ONS 15501 send "clear" for the threshold crossing alarms.
ONS 15800, ONS 15801, and ONS 15808
ONS 15800, ONS 15801, and ONS 15808 alarms that are retrieved using CTM GateWay/CORBA have OT_EQUIPMENT as the object_type field.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when meName does not reference a managed element object or excludeProbCauseList contains undefined values.EXCPT_ENTITY_NOT_FOUND - Raised when meName references an ME object that does not exist.EXCPT_NE_COMM_LOSS - Raised when communications to managedElement is lost.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.7.2 managedElementManager::ManagedElementManager_I::getAllSNCs
Synopsis
void getAllSNCs(in globaldefs::NamingAttributes_T managedElementName,in transmissionParameters::LayerRateList_T connectionRateList,in unsigned long how_many,out subnetworkConnection::SubnetworkConnectionList_T sncList,out subnetworkConnection::SNCIterator_I sncIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request all SNCs that originate on, terminate on, or transit through a given ME.
•
•
•
•
This method will not report VCAT SNCs.
CTM supports this operation only for ONS 15454 SONET, ONS 15454 SDH, ONS 15327, ONS 15600, ONS 15600 SDH, and ONS 15310 NEs.
Parameters
CTM support for SubnetworkConnection_T structure is as follows:
•
–
•
–
•
–
•
–
•
–
Note
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_INVALID_INPUT - Raised when managedElementName does not reference a managed element.EXCPT_ENTITY_NOT_FOUND - Raised when meName references an ME object that does not exist.EXCPT_NE_COMM_LOSS - Raised when communications to managedElement is lost.Compliance
CTM-defined.
3.7.3 managedElementManager::ManagedElementManager_I::
getAllManagedElementsSynopsis
void getAllManagedElements(in unsigned long how_many,out managedElement::ManagedElementList_T meList,out managedElement::ManagedElementIterator_I meIt)raises(globaldefs::ProcessingFailureException);Description
This operation enables an NMS to request details about all MEs that are under the control of ManagedElementMgr_I.
Parameters
CTM support for ManagedElement_T structure is as follows:
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
•
CTM will support the following layer rates:
–
LR_T1_and_DS1_1_5M
LR_T3_and_DS3_45M
LR_VT1_5_and_TU11_VC11
LR_STS1_and_AU3_High_Order_VC3
LR_STS3c_and_AU4_VC4
LR_STS6c_and_VC4_2c
LR_STS12c_and_VC4_4c
LR_STS48c_and_VC4_16c
LR_STS192c_and_VC4_64c (Supported on ONS 15454 Release 3.1 or later)
LR_STS9c_and_VC4_3c (Supported on ONS 15454 Release 3.2 or later, and ONS 15327 Release 3.3 or later)
LR_STS24c_and_VC4_8c (Supported on ONS 15454 Release 3.2 or later, and ONS 15327 Release 3.3 or later)
–
LR_E1_2M (Supported on ONS 15454 SDH Release 4.0 or later)
LR_E3_34M (Supported on ONS 15454 SDH Release 4.0 or later)
LR_T3_and_DS3_45M (Supported on ONS 15454 SDH Release 4.0 or later)
LR_VT2_and_TU12_VC12 (Supported on ONS 15454 SDH Release 4.0 or later)
LR_Low_Order_TU3_VC3 (Supported on ONS 15454 SDH Release 4.0 or later)
LR_STS3c_and_AU4_VC4
LR_STS12c_and_VC4_4c
LR_STS48c_and_VC4_16c
LR_STS192c_and_VC4_64c
LR_STS6c_and_VC4_2c
LR_STS9c_and_VC4_3c
LR_STS24c_and_VC4_8c
LR_STS18c_and_VC4_6c (Supported on ONS 15454, 15327, and ONS 15454 SDH Release 5.0 or later)
LR_STS36c_and_VC4_12c (Supported on ONS 15454, 15327, and ONS 15454 SDH Release 5.0 or later)
–
LR_Section_OC3_STS3_and_RS_STM1
LR_Section_OC12_STS12_and_RS_STM4
LR_Section_OC48_STS48_and_RS_STM16
LR_Line_OC3_STS3_and_MS_STM1
LR_Line_OC12_STS12_and_MS_STM4
LR_Line_OC48_STS48_and_MS_STM16
LR_Optical_Channel
LR_Optical_Multiplex_Section
LR_Optical_Transmission_Section
LR_ESCON
LR_Fast_Ethernet
LR_FC_100_1063M
LR_FDDI
LR_FICON
LR_Gigabit_Ethernet
LR_SYSPLEX_ISC_COMP
LR_SYSPLEX_ISC_PEER
LR_SYSPLEX_TIMER_ETR
LR_SYSPLEX_TIMER_CLO
LR_Ten_Gigabit_Ethernet
LR_PHYSICAL_OPTICAL
–
All layer rates supported by the ONS15540
LR_PHYSICAL_ELECTRICAL
–
LR_Optical_Channel
LR_Optical_Multiplex_Section
LR_Optical_Transmission_Section
LR_PHYSICAL_OPTICAL
–
LR_PHYSICAL_OPTICAL
–
LR_STS1_and_AU3_High_Order_VC3
LR_STS3c_and_AU4_VC4
LR_STS12c_and_VC4_4c
LR_STS24c_and_VC4_8c
LR_STS48c_and_VC4_16c
LR_STS192c_and_VC4_64c
–
Not supported.
–
Not supported.
•
Supported. Two parameters is sent in this field:
–
–
PreProvisioned
False
InServiceSyncConfiguration
False
OutOfService
False
UnderMaintenance
False
InServiceIntializing
False
InService
True
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.7.4 managedElementManager::ManagedElementManager_I::
getAllManagedElementNamesSynopsis
void getAllManagedElementNames(in unsigned long how_many,out globaldefs::NamingAttributesList_T nameList,out globaldefs::NamingAttributesIterator_I nameIt)raises(globaldefs::ProcessingFailureException);Description
This operation has the same behavior as managedElementManager::ManagedElementManager_I:: getAllManagedElements, but instead of returning the entire object structures, this operation returns their names.
Parameters
Throws
globaldefs::ProcessingFailureExceptionEXCPT_INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.EXCPT_TOO_MANY_OPEN_ITERATORS - Raised when maximum number of iterators has reached 128.Compliance
TMF-defined.
3.7.5 managedElementManager::ManagedElementManager_I::getAllPTPs
Synopsis
void getAllPTPs(in globaldefs::NamingAttributes_T managedElementName,in transmissionParameters::LayerRateList_T tpLayerRateList,in transmissionParameters::LayerRateList_T connectionLayerRateList,in unsigned long how_many,out terminationPoint::TerminationPointList_T tpList,out terminationPoint::TerminationPointIterator_I tpIt)raises(globaldefs::ProcessingFailureException);Description
This operation allows an NMS to request all PTPs on a specific ME that contain one or more NMS-specified PTP layer rates, and that are capable of supporting one or more NMS-specified connection layer rates. If no PTPs match the layer constraints, an empty list is returned. A PTP is returned regardless of connectivity to other MEs or position in the subnetwork. (Both PTPs at the subnetwork edge and PTPs that are internal to the subnetwork are reported.)
For PTPs on protection equipment in a 1_FOR_N protection group, CTM reports only the AlarmReporting for the LayeredParameters of the PTPs.
This method also returns a list of front Ethernet ports on an ML-series card on the specified ManagedElement.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Parameters
For details on TerminationPoint_T structure, see equipment::EquipmentInventoryMgr_I::getAllSupportedPTPs.
CTM supports the following layer rates:
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
