User guide

2-28
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 2 NE- and CTM-Specific Details
2.2.3 Interfaces
• For the ONS 15454 SDH R3.4 and later, the AIE (if installed) is reported in AdditionalHolder 1.
• For the ONS 15600 SONET R5.0 and later, pluggable port modules (PPMs) and pluggable I/O
modules (PIMs) on ASAP cards are reported as subslots and port holders, respectively.
• For the ONS 15600 SDH R8.0, PPMs and PIMs on ASAP cards are reported as subslots and port
holders, respectively.
• For unmanaged NEs, CTM reports only ManagedElement. CTM does not report any equipment
holder or equipment.
• For storage NEs, CTM reports only ManagedElement. CTM does not report any equipment holder
or equipment.
MGX 8880/8850/8830 NEs are single-shelf NEs. However, in the future, they may be expanded to
multishelf, multibay NEs. Considering this, CTM reports the following:
• Rack = 1 and shelf = 1 for the MGX 8880/8850/8830 inventory. This implementation allows CTM
to accommodate future changes quickly.
• CTM reports MGX slots and peripheral holders as equipment holders contained by the shelf. Any
provisioned card is reported as equipment under the slot, and any provisioned peripheral is reported
as equipment under the peripheral holder.
• CTM reports MGX slots with a provisioned card as equipment holders. CTM does not report empty
slots as equipment holders.
• For M2 NEs, CTM reports the slots with a provisioned card as equipment holders; this is applicable
only to slots 1 to 3. Other equipment is not managed.
• For M6 NEs, CTM reports the slots with a provisioned card as equipment holders; this is applicable
only to slots 1 to 8. Other equipment is not managed.
2.2.3 Interfaces
Unless specified otherwise, all getXXX methods are synchronous.
CTM supports all of the ONS 15xxx-series NEs. However, methods supported for one NE type might
not be supported for another NE type. In this case, CTM returns a NOT_IMPLEMENTED
ProcessingFailureException for the unsupported method.
Note CTM supports TMF-defined and Cisco-proprietary application programming interfaces (APIs) and data
structures. The Cisco-proprietary APIs and data structures are subject to change in future releases of
CTM to accommodate the introduction of new features or to maintain TMF compliance. This is
especially true if the TMF were to define the same method with a different behavior.
In such cases, the affected API name is changed without changing the behavior. The renamed API retains
the signature and behavior of the original API.
A standard deprecation period of one CTM release is allowed on the obsolete APIs and data structure.
However, Cisco is willing to consider exceptions that minimize the business impact to customers.