-
Cisco Transport Manager GateWay/CORBA User's Guide and Programmer Manual, 7.0
-
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
2.2.7 Provisioning Subnetwork Connections
NE- and CTM-Specific Details
This chapter provides specific details about each of the NEs that CTM supports. It also provides details specific to CTM.
Note
In this document, the terms network element (NE) and managed element (ME) are interchangeable.
The following subsections include NE- and CTM-specific details:
2.1 NE-Specific Details
2.1.1 Cisco 7600
The EMS provides the management support for Cisco 7600 Edge Router running the following IOS release: 12.2 (18) SXE and 12.2 (18) SXF.
2.1.2 CRS-1
CTM R7.0 supports Cisco Carrier Routing System 1 (CRS-1) software releases 3.0 and 3.2.
CRS-1 model type includes CRS-1/8, CRS-1/16, and Multichassis.
2.1.3 Cisco XR 12000
CTM R7.0 supports XR 12000 software release 3.2.
CTM R7.0 supports following types of XR 12000 chassis:
•
•
•
•
•
•
•
•
•
2.1.3.1 Rack
The XR 12000 is a single-rack NE.
2.1.3.2 Shelf
Each XR 12000 has one shelf per rack.
2.1.3.3 Slots
Number of slots in the XR 12000 rack can be determined by the type of XR 12000 chassis.
2.1.3.4 Subslots
XR 12000 release 3.2 has the Shared Port Adaptor (SPA) support. A container for a slot will contain all the SPAs; a slot might have multiple SPAs. The container is modeled as subslot in an XR 12000.
2.1.3.5 Topological Links
The topological links are not supported for XR 12000 at the northbound GateWay/CORBA interface in CTM R7.0.
2.1.3.6 Autodiscovery
The automatic discovery (autodiscovery) of XR 12000 is not supported at the northbound GateWay/CORBA interface in CTM R7.0.
2.1.3.7 PTP
XR 12000 supports the PTPs associated to ports (POS, POS/SDH, GE) of line cards. The XR 12000 PTP structure will contain the follow name/value pairs as additional information.
Table 2-1 lists the additional information in the XR 12000 PTP structure.
2.1.4 MGX 8880/8850/8830
CTM R7.0 supports the following MGX 8880/8850/8830 software releases:
•
•
•
2.1.4.1 Rack
MGX 8880/8850/8830 is a single-rack NE.
2.1.4.2 Shelf
Each MGX 8880/8850/8830 NE has one shelf per rack.
2.1.4.3 Slots
MGM 8880/8850 is a single-shelf NE with 32 slots. Slots 7 and 8 are reserved for the controller (PXM45 or PXM1E) front card. Slots 15/31 and 16/32 are reserved for the short reach (SR) ME front cards.
MGM 8830 is a single-shelf NE with 14 slots. Slots 1 and 2 are reserved for the controller (PXM1E) front card. Slots 13/14 are reserved for SRME front cards.
2.1.4.4 Subslot
The MGX 8880/8850/8830 slot is also divided into subslots or bays. The full-height cards (AXSM, VXSM, PXM, RPM, and PXM1E) have two subslots and the half-height cards (VISM, MPSM, and SRME) have one subslot. The subslots contain the back card for the corresponding front card.
2.1.4.5 PTP
For the MGX 8880/8850/8830 NEs, all PTPs are bidirectional. PTPs do not support the service state attribute. PTPs supports the layer rate attribute.
2.1.5 ONS 15216
Some NEs in the ONS 15216 family do not provide any management interface. These NEs are considered passive and all data is entered by a user from the CTM client. After data has been entered, CTM reports these NEs. Other NEs provide a management interface. These NEs are considered active.
CTM R7.0 supports the following NEs in the ONS 15216 family:
•
•
•
•
•
•
•
•
•
•
•
Note
2.1.5.1 PTP
CTM reports PTPs for the ONS 15216 NEs only if there exists a topological link originating or terminating on an ONS 15216 NE.
2.1.5.2 Topological Links
All topological links for the ONS 15216 FlexLayer are unidirectional. Inter-NE links are available between all NEs in the ONS 15216 family. CTM also supports bidirectional links between an ONS 15216 and the following NEs at compatible layer rates:
•
•
•
•
•
2.1.6 ONS 15302
CTM R7.0 supports ONS 15302 R2.0.1 and R2.0.2.
Support for (AXX155E R1.0) and R2.0 has been dropped.
2.1.6.1 Slots
ONS 15302 is a single-shelf NE with four slots. Slot 4 is the only one containing a removable card. Cards in slot 1, 2, and 3 cannot be removed.
2.1.6.2 PTP
ONS 15302 supports PTPs associated to WAN, SDH, and PDH ports.
2.1.7 ONS 15305
CTM R7.0 supports the following ONS 15305 software releases:
•
•
Support for Release 2.0 has been dropped.
2.1.7.1 Slots
ONS 15305 is a single-shelf NE with 4 slots.
2.1.7.2 PTP
ONS 15305 supports PTPs associated to WAN, SDH, and PDH ports.
2.1.8 ONS 15310 CL
CTM R7.0 supports the following ONS 15310 CL software releases:
•
•
•
•
Support for 5.0 version has been dropped.
2.1.8.1 Slots
ONS 15310 CL is a single-shelf NE with two slots. Slot 1 is the expansion slot and can contain the provisionable data card. Slot 2 is a nonreplicable unit and contains the ctx-cl controller.
2.1.8.2 Equipment
All the cards for ONS 15310 CL will display the Administration and Service states. For the previous software release these two states are not applicable (N/A). The following tables show the attribute values for these two states.
Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute values for the Administration state are listed in Table 2-2. The attribute values for the Service state are listed in Table 2-3 and Table 2-4.
Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute value for the service state is the same as CTM's.
2.1.8.3 Topological Links
All topological links are unidirectional or bidirectional for ONS 15310 CL NEs.
2.1.8.4 CTX Card
CTX card is an electrical card and consists of 21 DS1 ports and 3 DS3/EC1 ports. Two optical interfaces are supported using SFP technology. OC3 & OC12 are available.
2.1.8.5 PTP
All PTPs are bidirectional for ONS 15310 CL. The ports are always in channelized mode. PTPs support IN_SERVICE and OUT_OF_SERVICE_MAINTENANCE values for the service state attribute.
2.1.8.6 CTP
All CTPs are in channelized mode for the 15310 CL.
2.1.8.7 SNC
CTX cards perform synchronous transport signal (STS) and VT1.5 switching. The subnetwork connection (SNC) name cannot exceed 48 characters.
2.1.8.8 Autodiscovery
The ONS 15310 CL supports automatic discovery of connected elements. CTM can connect to one node and retrieve information about all connected nodes. The first time CTM connects to a node, it retrieves only the IP address of the connected node; CTM does not retrieve the node name. However, CTM has to report this element to the users. Because the IP address is unique, CTM initializes the name of the newly discovered element with the IP address. An Object Creation Event is generated for this managed element with the IP address as the name. Later, CTM connects to this element and retrieves all information, including the actual name, and an Attribute Value Change (AVC) event is generated for the managed element name. The network management system (NMS) should listen to AVC event for the managed element name and invoke managedElementManager::ManagedElementManager_I::getManagedElement.
2.1.9 ONS 15310 MA
CTM R7.0 supports the ONS 15310 MA R7.0.
2.1.9.1 Slots
ONS 15310 MA consist of two Control Timing and Cross-Connect (CTX) slots, and four Expansion (EXP) I/O slots.
2.1.10 ONS 15327
CTM R7.0 supports the following ONS 15327 software releases:
•
•
•
•
•
•
•
Support has been dropped for 4.1.5, 4.1.6, 5.0, 4.6.2, 5.0, and 5.0.4 software releases.
2.1.10.1 Slots
ONS 15327 is a single-shelf NE with eight slots. The Mechanical Interface Card (MIC) A card must reside in slot 8 and the MIC B card must reside in slot 7. If an integrated Cross-Connect, Timing, and Control (XTC) card is required, it must reside in slot 5 or slot 6.
2.1.10.2 Equipment
All the cards in ONS 15327 R7.0 display the Administration and Service states. For earlier software releases, these states are not applicable and CTM will display them as "N/A."
Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute values for the Administration state are listed in Table 2-5. The attribute values for the Service state are listed in Table 2-6 and Table 2-7.
Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute value for the service state shown is the same as that displayed in CTM.
2.1.10.3 Topological Links
All topological links are unidirectional or bidirectional for the ONS 15327 NEs.
2.1.10.4 XTC Card
The XTC-14 card has 14 digital signal level 1 (DS-1) ports numbered 1 through 14. Only VT1.5 subnetwork connections (SNCs) can be created on these ports. The XTC-28-3 card has 28 DS-1 ports numbered 1 through 28 and three DS-3 ports numbered 29 through 31. VT1.5 SNCs can be created on DS-1 ports, and STS-1 SNCs can be created on DS-3 ports
2.1.10.5 PTP
All PTPs are bidirectional for the ONS 15327. The ports are always in channelized mode. PTPs support IN_SERVICE, OUT_OF_SERVICE, OUT_OF_SERVICE_MAINTENANCE, and AUTO_IN_SERVICE values for the service state attribute
2.1.10.6 CTP
All CTPs are in channelized mode for the ONS 15327. Alarm monitoring cannot be turned on or off for CTPs
2.1.10.7 SNC
•
•
Note
2.1.11 ONS 15454 SDH
CTM R7.0 supports the following ONS 15454 SDH software releases:
•
•
•
•
•
•
•
•
•
•
•
•
Support has been dropped for 5.0, 5.0.1, 5.0.2, and 5.0.7 software release(s).
2.1.11.1 Shelves
All supported ONS 15454 SDH NEs have exactly one shelf each, with the exception of ONS 15454 SDH MSTP R7.0, which an have up to eight shelves per NE.
2.1.11.2 Slots
The ONS 15454 SDH NE has one shelf view supplemented with the top subrack Electrical Facility Connection Assembly (EFCA) shelf and bottom subrack chassis. The main shelf has 17 slots numbered 1 to 17 and contains cards that carry traffic. The EFCA shelf has 12 additional slots numbered 18 to 29 and contains Front Mount Electrical Connection (FMEC) modules, the ALM/PWR/MIC (A/P/M) module, and the CRFT/TMG/MIC (C/T/M) module. Slots 18 to 29 are optional, are not available for equipment provisioning, and are reported only for inventory management. The Timing Communications and Control (TCC) modules must be in slot 7 or slot 11, the A/P/M module must be in slot 23, and the C/T/M module must be in slot 24
2.1.11.3 Equipment
All cards in ONS 15454 SDH software release 7.0 display the Administration and Service states. For earlier software releases, these states are not applicable and CTM will display them as "N/A."
Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute values for the Administration state are listed in Table 2-8. The attribute values for the Service state are listed in Table 2-9 and Table 2-10.
Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment.
2.1.11.4 Topological Links
Topological links are either unidirectional or bidirectional for ONS 15454 SDH NEs
2.1.11.5 PTP
All PTPs are bidirectional for the ONS 15454 SDH. Additionally, these ports are always in channelized mode. PTPs support IN_SERVICE, OUT_OF_SERVICE, OUT_OF_SERVICE_MAINTENANCE, and AUTO_IN_SERVICE values for the service state attribute
2.1.11.6 CTP
All CTPs are in channelized mode for the ONS 15454 SDH. Alarm monitoring cannot be turned on or off for CTPs.
2.1.11.7 SNC
One node supports a maximum of 192 VC4 SNCs. The SNC name cannot exceed 48 characters
Note
2.1.11.8 Equipment Protection
1:N equipment protection is supported for E1, E1-42, and DS3i cards. You must install protect cards (E1-N, E1-42, DS3i-N) in slot 3 or slot 15 on the same side of the shelf as the protected cards. Protect cards must match the cards they protect. For example, an E1-N card protects only E1 or E1-N cards. You must create the protection group explicitly. Installing E1-N, E1-42, or DS3i-N cards in slot 3 or slot 15 does not automatically protect other E1, E1-42, or DS3i cards. 1:N equipment protection is always revertive.
1:1 equipment protection is supported for E1, E1-42, E3, STM-1E-12, and DS3i cards. Install the protect card in an odd-numbered slot and install the working card in an adjacent even-numbered slot. For example, install the protect card in slot 1 and install the working card in slot 2.
2.1.11.9 Facility Protection
Facility protection is available for STM-n PTPs. Protect ports must match the working ports. For example, port 1 of an STM-1 (OC-3) card is protected only by port 1 on another STM-1 (OC-3) card.
2.1.11.10 Autodiscovery
The ONS 15454 SDH supports automatic discovery of connected elements such as the ONS 15454 SONET autodiscovery described in ONS 15454 SONET
2.1.12 ONS 15454 SONET
CTM R7.0 supports the following ONS 15454 SONET software releases:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Support has been dropped for 4.1.1, 4.1.5, 4.1.7, 5.0, 5.0.2, and 5.0.3 software release(s).
2.1.12.1 Shelves
All supported ONS 15454 SONET NEs have exactly one shelf each, with the exception of the ONS 15454 SONET MSTP R7.0, which can have up to eight shelves per NE.
2.1.12.2 Slot
The ONS 15454 SONET is a single-shelf NE with 17 slots. The Timing Communications and Control (TCC) card must reside in slot 7 or slot 11. For more information, refer to the Cisco ONS 15454 user documentation.
Each ONS 15454 shelf has 17 slots. The Timing Communications and Control (TCC) card must reside in slot 7 or slot 11.
2.1.12.3 Equipment
All the cards for ONS 15454 will display the Administration and Service state. For the previous release these two states are not applicable, so CTM will display them as "N/A."
All the cards in the ONS 15454 display the Administration and Service states. For earlier software releases, these states are not applicable and CTM will display them as "N/A." The following tables show the attribute values for these two states.
Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute values for the Administration state are listed in Table 2-11. The attribute values for the Service state are listed in Table 2-12 and Table 2-13.
Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute value for the service state is the same as that displayed in CTM.
2.1.12.4 Topological Links
Topological links are either unidirectional or bidirectional for ONS 15454 SONET NEs.
2.1.12.5 PTP
All PTPs are bidirectional for the ONS 15454. The ports are always in channelized mode. PTPs support IN_SERVICE, OUT_OF_SERVICE, OUT_OF_SERVICE_MAINTENANCE, and AUTO_IN_SERVICE values for the service state attribute
2.1.12.6 CTP
All CTPs are in channelized mode for the ONS 15454 SONET. Alarm monitoring cannot be turned on or off for CTPs
2.1.12.7 SNC
One node supports a maximum of 144 bidirectional STS SNCs with an XC or Cross-Connect Virtual Tributary (XCVT) card installed. If an XCVT card is present, you can create a maximum of 336 VT1.5 SNCs. You can create a maximum of 576 bidirectional STS SNCs with an XC10G card installed.
In release 3.0.3, the name of the SNC cannot exceed 32 characters. For release 3.2.1 or later, the name cannot exceed 48 characters.
Note
2.1.12.8 Equipment Protection
1:N equipment protection is supported for DS-1, DS-3, DS3I, and DS3E cards. You must install protect cards (DS1N, DS3N, DS3IN, and DS3NE) in slot 3 or slot 15 on the same side of the shelf as the protected cards. Protect cards must match the cards they protect. For example, a DS1N protects only DS1 or DS1N cards. You must create the protection group explicitly. Installing DS1N or DS3N cards in slot 3 or slot 15 does not automatically protect other DS-1 or DS-3 cards. 1:N equipment protection is always revertive.
1:1 equipment protection is supported for DS-1, DS-3, DS3I, DS3E, EC-1, and DS3XM cards. Install the protect card in an odd-numbered slot and install the working card in an adjacent even-numbered slot. For example, install the protect card in slot 1 and install the working card in slot 2.
Note
2.1.12.9 Facility protection
Facility protection is available for OC-n PTPs. Protect ports must match the working ports. For example, port 1 on an OC-3 card is protected only by port 1 on another OC-3 card.
2.1.12.10 Autodiscovery
The ONS 15454 SONET supports automatic discovery of connected elements. CTM can connect to one node and retrieve information about all connected nodes. The first time CTM connects to a node, it retrieves only the IP address of the connected node; CTM does not retrieve the node name. However, CTM has to report this element to the users. Because the IP address is unique, CTM initializes the name of the newly discovered element with the IP address. An Object Creation Event is generated for this managed element with the IP address as the name. Later, CTM connects to this element and retrieves all information, including the actual name, and an attribute value change (AVC) event is generated for the managed element name. The NMS should listen to AVC event for the managed element name and invoke managedElementManager::ManagedElementManager_I::getManagedElement.
2.1.13 ONS 15501
CTM R7.0 supports the following ONS 15501 releases:
–
–
–
–
2.1.13.1 Slot
ONS 15501 is a single-shelf system with no slots.
2.1.13.2 PTP
All PTPs are unidirectional for ONS 15501 NEs. PTPs do not support the service state attribute. Only the In-Port and Out-Port interfaces are reported as PTPs
2.1.13.3 CTP
CTPs for the ONS 15501 are not supported in this release of GateWay/CORBA
2.1.13.4 SNC
SNCs for the ONS 15501 are not supported in this release of GateWay/CORBA
2.1.13.5 Equipment
The ONS 15501 has no removable equipment. The chassis is reported as equipment present under the shelf equipment holder
2.1.13.6 Topological Links
All topological links are unidirectional for ONS 15501 NEs
2.1.14 ONS 15530
CTM R7.0 supports the following releases of the Cisco IOS image on the ONS 15530:
•
•
•
Support has been dropped for 12.2(26)SV and 12.2(25)SV.
2.1.14.1 Slots
The ONS 15530 is a single-shelf NE with 13 slots. The ONS 15530 is a dual-CPU system with integrated switch fabric. The processor cards must occupy slots 6 and 7. Slot 1 contains the multiplexer/demultiplexer (mux/demux) motherboards, which are populated with optical multiplexer/demultiplexer modules. The remaining slots can contain:
•
•
•
•
•
2.1.14.2 PTP
PTPs are both unidirectional and bidirectional for the ONS 15530. PTPs do not support the service state attribute.
The following interfaces are reported as PTPs:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
2.1.14.3 CTP
CTPs for the ONS 15530 are not supported in this release of GateWay/CORBA
2.1.14.4 SNC
SNCs for the ONS 15530 are not supported in this release of GateWay/CORBA
2.1.14.5 Equipment Protection
1:1 equipment protection is supported for the CPU card
2.1.14.6 Equipment
The ONS 15530 reports all the field-replaceable units (FRUs) as equipment. In addition, the chassis is reported as equipment present under the shelf equipment holder
2.1.14.7 Topological Links
Topological links can be either unidirectional or bidirectional for ONS 15530 NEs. CTM reports both inter-NE and intra-NE links for ONS 15530
2.1.14.8 PTP Layer Rates
ONS 15530 supports these additional PTP layer rates:
•
•
•
•
•
2.1.15 ONS 15540
CTM R7.0 supports the following Cisco IOS releases on the ONS 15540 ESP and ONS 15540 ESPx:
•
•
•
Support has been dropped for 12.2(26)SV and 12.2(25)SV.
2.1.15.1 Slots
The ONS 15540 is a single-shelf NE with 13 slots. The ONS 15540 is a dual-CPU system where the processor cards occupy slots 7 and 8. Slots 1 and 2 contain the multiplexer/demultiplexer motherboards, which are populated with optical multiplexer/demultiplexer modules. The remaining slots contain the line card motherboards, which are populated with transponder modules
2.1.15.2 PTP
All PTPs are bidirectional for the ONS 15540. PTPs do not support the service state attribute.
Wavepatch interfaces on the transponder card and filter interfaces on multiplexer/demultiplexer cards are reported as PTPs even though the cards are not externally visible from the fixed optical backplane. Wave interfaces on the transponder cards are reported as PTPs even though they are internal interfaces, because alarms are generated on these interfaces and CTPs are not supported.
The following interfaces are reported as PTPs:
•
•
•
•
•
•
•
•
•
•
•
•
2.1.15.3 CTP
CTPs for the ONS 15540 are not supported in this release of GateWay/CORBA.
2.1.15.4 SNC
SNCs for the ONS 15540 are not supported in this release of GateWay/CORBA.
The NMS should listen to AVC event for the managed element name and invoke managedElementManager::ManagedElementManager_I::getManagedElement
2.1.15.5 Equipment Protection
1:1 equipment protection is supported for CPU card.
2.1.15.6 Equipment
The ONS 15540 reports all the FRUs as equipment. The chassis is also reported as equipment present under the shelf equipment holder.
2.1.15.7 Topological Links
Topological links can be unidirectional or bidirectional for ONS 15540 NEs. CTM reports both inter-NE and intra-NE links for the ONS 15540
2.1.15.8 PTP Layer Rates
The ONS 15540 supports these additional layer rates:
•
•
•
•
•
2.1.16 ONS 15600 SONET
CTM R7.0 supports the following ONS 15600 SONET software releases:
•
•
•
•
•
•
•
•
•
2.1.16.1 Slots
The ONS 15600 is a single-shelf NE with 14 slots. The Timing and Shelf Control (TSC) card must occupy slot 5 or slot 10. The Core Cross-Connect (CXC) cards are always 1+1 redundant in slots 6/7 and 8/9. Each CXC card occupies two slots. Slots 1 to 4 and 11 to 14 are reserved for optical I/O cards. The CXC card will be replaced with the Single Shelf Cross-Connect (SSXC) card in the ONS 15600 R5.0.
2.1.16.2 Equipment
All the cards in the ONS 15600 display the Administration and Service states. For earlier software releases, these states are not applicable and CTM will display them as "N/A." Following tables show the attribute values for these two states.
Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute values for the Administration state are listed in Table 2-14. The attribute values for the Service state are listed in Table 2-15 and Table 2-16.
Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and will be displayed in getAdditionalInfo for the equipment. The attribute value for the service state is the same as that displayed in CTM.
2.1.16.3 Topological Links
Topological links are either unidirectional or bidirectional for the ONS 15600 NEs
2.1.16.4 PTP
All PTPs are bidirectional for the ONS 15600. These ports are always in channelized mode. PTPs support IN_SERVICE and OUT_OF_SERVICE_MAINTENANCE values for service state attribute.
2.1.16.5 CTP
All CTPs are in channelized mode for the ONS 15600. Alarm monitoring cannot be turned on or off for CTPs.
2.1.16.6 SNC
The ONS 15600 supports a maximum of 1536 STS SNCs
2.1.16.7 Protection
The ONS 15600 supports 1+1 protection to create redundancy for optical ports. Protect ports must match the working ports. For example, port 1 on an OC-48 card can be protected by port 1 on another OC-48 card or another port on the same card.
2.1.16.8 Autodiscovery
The ONS 15600 SONET supports automatic discovery of connected elements. CTM can connect to one node and retrieve information about all connected nodes. The first time CTM connects to a node, it retrieves only the IP address of the connected node; CTM does not retrieve the node name, even though CTM has to report this element to the user. Because the IP address is unique, CTM uses the NE IP address as the name of the newly discovered element. An Object Creation Event is generated for this managed element with the IP address as the name. Later, CTM connects to this element and retrieves all information, including the actual name, and an AVC event is generated for the managed element name.
Note
2.1.17 ONS 15600 SDH
CTM R7.0 supports the ONS 15600 SDH R1.4.
2.1.17.1 Slots
The ONS 15600 SDH is a single-shelf NE with 14 card slots numbered sequentially from left to right. Slots 1 to 4 and 11 to 14 are reserved for optical (STM-N) traffic cards. These slots can host any of the ONS 15600 SDH optical cards. Slots 6/7 and 8/9 are dedicated to CXC cards, which are always 1+1 redundant, and slots 5 and 10 house the TSC cards. Each card is keyed to fit only in an appropriate slot for that card. Unused card slots should be occupied by a filler card (blank faceplate). For more information, refer to the Cisco ONS 15600 SDH user documentation.
2.1.17.2 Topological Links
Topological links are either unidirectional or bidirectional for ONS 15600 SDH NEs
2.1.17.3 PTP
All PTPs are bidirectional for the ONS 15600 SDH. These ports are always in channelized mode. PTPs support IN_SERVICE and OUT_OF_SERVICE_MAINTENANCE values for service state attribute
2.1.17.4 CTP
All CTPs are in channelized mode for the ONS 15600 SDH. Alarm monitoring cannot be turned on or off for CTPs
2.1.17.5 SNC
The ONS 15600 SDH supports a maximum of 1536 VC4 SNCs
2.1.17.6 Protection
The ONS 15600 SDH supports 1+1 protection to create redundancy for optical ports. Protect ports must match the working ports. For example, port 1 on an STM-16 card can be protected by port 1 on another STM-16 card or another port on the same card
2.1.17.7 Autodiscovery
The ONS 15600 SDH supports automatic discovery of connected elements. CTM can connect to one node and retrieve information about all connected nodes. The first time CTM connects to a node, it retrieves only the IP address of the connected node; CTM does not retrieve the node name, even though CTM has to report this element to the user. Because the IP address is unique, CTM uses the NE IP address as the name of the newly discovered element. An Object Creation Event is generated for this managed element with the IP address as the name. Later, CTM connects to this element and retrieves all information, including the actual name, and an AVC event is generated for the managed element name.
Note
2.1.18 ONS 15800, ONS 15801
CTM R7.0 supports the following ONS 15800 releases:
•
•
2.1.18.1 Racks
Each ONS 15800 or ONS 15801 can have from one to ten racks.
2.1.18.2 Shelf
Each ONS 15800 or ONS 15801 has three shelves per rack
2.1.18.3 Slots
Each ONS 15800 has 17 slots per shelf. Each ONS 15801 has 15 slots per shelf
2.1.18.4 Topological Links
All topological links are unidirectional for ONS 15800/15801 NEs.
2.1.18.5 PTP
All PTPs are unidirectional for ONS 15800 and ONS 15801equipment. There are four types of PTPs:
•
•
•
•
A topological link starts in a source PTP and ends in a sink PTP. PTPs bordering the same link have the same direction (east-to-west or west-to-east).
Links can be established between PTPs supported by following boards:
•
•
Each board can delimit only a link.
2.1.19 ONS 15808
CTM R7.0 supports the following ONS 15808 releases:
•
•
•
2.1.19.1 Racks
Each ONS 15808 can have from one to ten racks.
2.1.19.2 Shelf
Each ONS 15808 has three shelves per rack.
2.1.19.3 Slots
Each ONS 15808 has 15 slots per shelf.
2.1.19.4 Topological Links
All topological links are unidirectional for the ONS 15808 NEs.
2.1.19.5 PTP
All PTPs are unidirectional for the 15808 equipment. There are four types of PTPs:
•
•
•
•
A topological link starts in a source PTP and ends in a sink PTP. PTPs bordering the same link have the same direction (east-to-west or west-to-east).
Each terminal site supports up to two links having opposite directions; all other sites support up to four links—two `East to West' and two `West to east'. Links can be established between PTPs supported by the following boards:
•
•
Each board can delimit two links through a source PTP and a sink PTP, having opposite directions.
2.1.20 MSD 9000
The MSD 9000 is a passive storage NE that does not contain any equipment. CTM reports PTPs for the MSD 9000 if there is a topological link originating from or terminating on the MSD 9000. There are no alarms reported for the MSD 9000
2.1.21 Unmanaged NEs
Unmanaged NEs are other vendor MEs in CTM. There is no equipment for these NEs. CTM reports PTPs for unmanaged NEs only if there is a topological link originating or terminating on the unmanaged NE. There are no reported alarms on unmanaged NEs.unmanaged
2.2 CTM-Specific Details
2.2.1 Layer Rate
CTM R7.0 supports the following layer rates:
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
2.2.2 Inventory
The ONS 15327, ONS 15310, ONS 15600, ONS 15600 SDH, ONS 15540, ONS 15530, and ONS 15501 are single-shelf NEs. However in future they may be expanded to multishelf, multibay NEs. Considering this, CTM will always report Rack = 1 and Shelf =1 for 15310, 15327, ONS 15600, 15540, 15530, and 15501 inventory. This implementation will allow CTM to accommodate future changes quickly.
Starting from CTM R7.0, ONS 15454 MSTP NEs supports up to eight shelves per NE. The shelf ID will identify a specific shelf on the NE. The rack id will remain 1 for all the shelves.
•
•
•
•
•
•
•
•
•
•
•
–
–
–
•
•
•
Note
•
•
2.2.3 Interfaces
Note
Note
Note
In such cases, the affected API name will be changed without changing the behavior. The renamed API will retain the signature and behavior of the original API.
A standard deprecation period of one CTM release will be allowed on the obsolete APIs and data structure. However, Cisco is willing to consider exceptions that minimize the business impact to the customers.
Note
In addition to implementing TeleManagement Forum (TMF)-defined interfaces, CTM defines the following new methods on different interfaces:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
2.2.4 Object Details
2.2.4.1 Multilayer Subnetwork
A subnetwork is a collection of managed elements that reflects network connectivity, in most cases. There are two ways to create a new subnetwork through the CTM client:
1.
2.
There are four ways to add NEs to subnetworks:
1.
2.
3.
4.
SNC creation is limited within a MultiLayerSubnetwork scope. For example, assume Subnetwork-00000001 contains two NEs, A and B, that are connected to each other with an autodiscovered link. Subnetwork-00000002 contains two NEs, C and D, that are connected to each other with an autodiscovered link. There is also a manual link between NEs B and C, and the use-for-routing attribute for the link is set to true by CTM. To create an SNC between NEs A and D, you must move NEs C and D into Subnetwork-00000001, or move NEs A and B into Subnetwork-00000002.
CTM R7.0 includes a new feature to automatically group NEs in subnetworks. This feature is enabled by default. If a routable link is created between two NEs in different subnetworks and CTM decides to merge the two subnetworks, the result is reflected in CTM GateWay/CORBA. In this instance the two subnetworks are automatically merged when this feature is enabled in CTM.
2.2.4.2 SNC
SNC is supported only for ONS 15310, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15600, and ONS 15600 SDH NEs. CTM does not support SNC in a pending state. However, CTM SNC has a proprietary deleting state.
2.2.4.3 AVC Events
In certain situations, CTM cannot provide the list of changed object attributes. In this case, CTM generates an AVC event with an empty attribute list. The NMS must retrieve the object details by making an explicit get call.
2.2.4.4 Managed Element and Object Creation Event
You can use the CTM client to add new managed elements. If the name of the new element is incorrect, an Object Creation event is generated with the incorrect name. Later, when CTM connects to the actual NE, it retrieves the correct name. CTM generates an AVC event to notify the NMS.
2.2.4.5 Source of Object Attributes Reported by CTM
This section lists the attributes of objects that CTM GateWay/CORBA reports. Each attribute is a constant value or is retrieved from the cache or from the NE. The term cache refers to "in-memory" and includes the CTM database repository and configuration files. CTM relies on notifications from the NE to update the value of these attributes.
2.2.4.5.1 MultiLayerSubnetwork_T
Table 2-17 lists the MultiLayerSubnetwork_T attributes and where they are reported from.
Table 2-17 MultiLayerSubnetwork_T
name
cache
nativeEMSName
cache
subnetworkType
cache
2.2.4.5.2 EMS_T
Table 2-18 lists the EMS_T attributes and where they are reported from.
Table 2-18 EMS_T
name
cache
nativeEMSName
cache
emsVersion
constant value
type
constant value
2.2.4.5.3 Equipment_T
Table 2-19 lists the Equipment_T attributes and where they are reported from.
Note
Table 2-19 Equipment_T
name
cache
nativeEMSName
cache
expectedEquipmentObjectType
cache
installedEquipmentObjectType
cache
installedPartNumber
cache
installedVersion
cache
installedSerialNumber
cache
additionalInfo (only CLEI1 code is reported)
cache
1 CLEI = Common Language Equipment Identifier
2.2.4.5.4 EquipmentHolder_T
Table 2-20 lists the Equipment_T attributes and where they are reported from.
Note
Table 2-20 EquipmentHolder_T
name
cache
nativeEMSName
cache
holderType
cache
expectedOrInstalledEquipment
cache
acceptableEquipmentTypeList
cache
holderState
cache
2.2.4.5.5 TerminationPoint_T
Table 2-21 lists the TerminationPoint_T attributes and where they are reported from.
Note
2.2.4.5.6 SubnetworkConnection_T
Table 2-22 lists the TerminationPoint_T attributes and where they are reported from.
Note
Table 2-22 SubnetworkConnection_T
name
cache
nativeEMSName
cache
sncState
cache
direction
cache
rate
cache
staticProtectionLevel
Note
cache
aEnd, zEnd
tpName
cache
transmissionParams
See Section TerminationPoint_T
2.2.4.5.7 ManagedElement_T
Table 2-23 lists the ManagedElement_T attributes and where they are reported from.
For NE-specific details, see the 3.7.3 managedElementManager::ManagedElementManager_I:: getAllManagedElements, page 3-78.
2.2.4.5.8 TopologicalLink_T
Table 2-24 lists the TopologicalLink_T attributes and where they are reported from.
For NE-specific details, see the 3.2.5 emsMgr::EMSMgr_I::getAllTopLevelTopologicalLinks, page 3-7.
Table 2-24 TopologicalLink_T
name
cache
nativeEMSName
cache
direction
constant value
rate
cache
aEndTP
cache
zEndTP
cache
2.2.4.5.9 ProtectionGroup_T
Table 2-25 lists the ProtectionGroup_T attributes and where they are reported from.
For NE-specific details, see the 3.11.2 protection::ProtectionMgr_I::getAllProtectionGroups, page 3-291.
Table 2-25 ProtectionGroup_T
name
cache
nativeEMSName
cache
protectionGroupType
cache
protectionSchemeState
constant value
reversionMode
cache
rate
cache
pgTPList
cache
pgpParameters1
cache
additionalInfo2
cache
1 CTM supports only wtrTime
2 CTM supports only "BIDIRECTIONAL" for 1_PLUS_1 PGP
2.2.4.5.10 ServerTrailLink_T
Table 2-26 lists the ServerTrailLink_T attributes and where they are reported from.
2.2.5 Naming Conventions
The following sections describe naming conventions for objects that CTM reports.
2.2.5.1 MultiLayerSubnetwork
Name is defined by the user in the CTM client. If the user does not specify a name, CTM assigns a default name.
2.2.5.2 ManagedElement
Name is reported by ManagedElement.
2.2.5.3 Physical Termination Point
The PTP name will be representative of the position of the PTP with respect to the equipment. For example, port number 4 on equipment in slot 15 will be reported as "/rack=1/shelf=1/slot=15/port=4". This PTP naming convention will be used to represent the front Ethernet ports for the ONS 15454 SONET and ONS 15454 SDH ML-series cards. The back Ethernet ports will be reported as FTPs.
For class of service (CoS) data on data cards, the PTP name will also specify the interface (POS/FastEthernet/GigabitEthernet), direction (input/output), and CoS level (0-7).
For example, CoS data with POS interface, Input direction, and CoS level 3, for slot 1, port 1 in the NE will be reported as /rack=1/shelf=1/slot=1/port=1:POS/Input/3.
Similarly, CoS data with Fast Ethernet interface, Output direction, and CoS level 5 for slot 1, port 1 in the NE will be reported as /rack=1/shelf=1/slot=1/port=1:FastEthernet/Output/5.
For the ONS 15600, ASAP card on slot 3, port 1 on PPM 3 and PIM 2 will be reported as /rack=1/shelf=1/slot=3/sub_slot=2/ppm_holder=3/port=1.
Similarly, for the ONS 15310, a port on PPM 2 will be reported as /rack=1/shelf=1/slot=2/ppm_holder=2/port=4.
Similar for ONS 15310, a port on PPM number 2 would be referred as /rack=1/shelf=1/slot=2/ppm_holder=2/port=1.
For the ONS 15501, ONS 15530, and ONS 15540 NEs, the PTP name represents the position of the PTP with respect to the equipment. It also specifies the cliName, because more than one interface type could have the same physical position. Numbering for equipmentHolders and ports starts from 0 in the NE. However, the TMF convention is to start numbering from 1 for equipmentHolders and ports. Therefore, CTM does translation when reporting PTP names.
For example, wavepatch0/0/0 (which is present in slot 0, subslot 0 in the NE) is reported as /rack=1/shelf=1/slot=1/subslot=1/port=1:wavepatch0/0/0.
Transparent0/0/0 port (which is also present in slot 0, subslot 0 in the NE) is reported as /rack=1/shelf=1/slot=1/subslot=1/port=1:transparent0/0/0.
Some PTPs, such as wdm0/0, do not have an associated port number. In these cases, the port number is set to 1.
Wdm0/0, which is present in slot 0 and subslot 0 in the NE, is reported as /rack=1/shelf=1/slot=1/subslot=1/port=1:wdm0/0.
Wave0 interface (which is present in slot 0 in the NE) is reported as /rack=1/shelf=1/slot=1/port=1:wave0 (since the subslot does not apply to this port, it is skipped).
In-Port present on the chassis is reported as rack=1/shelf=1/port=1:In-Port.
For the ONS 15800, ONS 15801, and ONS 15808, the PTP name represents the position of the PTP with respect to the equipment, where the physical location is composed of rack/shelf/slot. It also specifies the direction, since there can be more than one PTP with the same physical position:
/rack=1/shelf=1/slot=13:0Subslot and port are not significant for ONS 158xx equipment. The direction can assume the following values:
•
•
•
•
For the CRS-1 and XR 12000, the PTP name represents the position of the PTP with respect to the equipment. For example, PTPs of 3-port GE line cards in slot 3 are reported as:
/rack=1/shelf=1/slot=3/sub_slot=0/port=0/rack=1/shelf=1/slot=3/sub_slot=0/port=1/rack=1/shelf=1/slot=3/sub_slot=0/port=2
Note
Note
2.2.5.4 Connection Termination Point
Naming conventions for SONET, SDH, and plesiochronous digital hierarchy (PDH) CTP are defined by TMF 814 in a document named objectNaming.html. CTM follows these rules.
For OC-n or STM-n cards on ONS 15454 SONET release 3.2.1 or later, ONS 15327 release 3.3 or later, and ONS 15454 SDH release 3.3 or later, CTM supports STS6c, STS9c, and STS24c layer rates. On ONS 15327 release 5.0 or later, ONS 15454 SONET release 5.0 or later, and ONS 15454 SDH 5.0 or later, CTM supports STS18c and STS36c layer rates. These are not conventional SONET/SDH rates; therefore, the TMF document does not cover their naming. Table 2-27 shows the CTM connection terminal points for STS6c, STS9c, STS24c, STS18c, and STS36c layer rates.
Note
In addition, the following CTP name support has been added:
For CTPs used for WDM SNCs, use the naming conventions defined in TMF: /frequency=nnn.mm, where nnn.mm is a decimal representing the frequency in terahertz (THz)
For unidirectional CTP, the naming convention is to add "/direction=src or sink" in front of the name. Because the CTPs in WDM SNC are all unidirectional, the name will be "/direction=src or sink/frequency=nnn.mm" for WDM SNC CTPs.
Since the CTM client uses wavelength to represent an optical channel, enter the corresponding wavelength value in the nativeEMSName field for the CTP.
The formula for converting wavelength to frequency is:
frequency (THz) = 299792458 / wavelength (nm) / 1000.
The formula for converting frequency back to wavelength is:
wavelength (nm) = 299792458 / frequency (THz) / 1000.
The possible values of the frequency nnn.mm (in THz) in the CTP and the corresponding wavelength values are:
For OCHNC:
C Band
195.90 (1530.33), 195.80 (1531.12), 195.70 (1531.90), 195.60 (1532.68), 195.40 (1534.25), 195.30 (1535.04), 195.20 (1535.82), 195.10 (1536.61), 194.90 (1538.19), 194.80 (1538.98), 194.70 (1539.77), 194.60 (1540.56), 194.40 (1542.14), 194.30 (1542.94), 194.20 (1543.73), 194.10 (1544.53), 193.90 (1546.12), 193.80 (1546.92), 193.70 (1547.72), 193.60 (1548.51), 193.40 (1550.12), 193.30 (1550.92), 193.20 (1551.72), 193.10 (1552.52), 192.90 (1554.13), 192.80 (1554.94), 192.70 (1555.75), 192.60 (1556.55), 192.40 (1558.17), 192.30 (1558.98), 192.20 (1559.79), 192.10 (1560.61).
L-Band
1577.86, 1578.69, 1579.52, 1580.35, 1581.18, 1582.02, 1582.85, 1583.69, 1584.53, 1585.36, 1586.20, 1587.04, 1587.88, 1588.73, 1589.57, 1590.41, 1591.26, 1592.10, 1592.95, 1593.79, 1594.64, 1595.49, 1596.34, 1597.19, 1598.04, 1598.89, 1599.75, 1600.60, 1601.46, 1602.31, 1603.17, 1604.03.
For OCHCC:
C Band ODD
1529.55nm, 1530.33nm, 1531.12nm, 1531.90nm, 1532.68nm, 1533.47nm, 1534.25nm, 1535.04nm, 1535.82nm, 1536.61nm, 1537.40nm, 1538.19nm, 1538.98nm, 1539.77nm, 1540.56nm, 1541.35nm, 1542.14nm, 1542.94nm, 1543.73nm, 1544.53nm, 1545.32nm, 1546.12nm, 1546.92nm, 1547.72nm, 1548.51nm, 1549.32nm, 1550.12nm, 1550.92nm, 1551.72nm, 1552.52nm, 1553.33nm, 1554.13nm, 1554.94nm, 1555.75nm, 1556.55nm, 1557.36nm, 1558.17nm, 1558.98nm, 1559.79nm, 1560.61nm, 1561.42nm.
C Band EVEN
1529.94nm, 1530.73nm, 1531.51nm, 1532.29nm, 1533.07nm, 1533.86nm, 1534.64nm, 1535.43nm, 1536.22nm; 1537.00nm; 1537.79nm; 1538.58nm; 1539.37nm; 1540.16nm; 1540.95nm; 1541.75nm; 1542.54nm; 1543.33nm; 1544.13nm; 1544.92nm; 1545.72nm; 1546.52nm; 1547.32nm; 1548.12nm; 1548.92nm; 1549.71nm; 1550.52nm; 1551.32nm; 1552.12nm; 1552.93nm; 1553.73nm; 1554.54nm; 1555.34nm; 1556.15nm; 1556.96nm; 1557.77nm; 1558.58nm; 1559.39nm; 1560.20nm; 1561.01nm; 1561.83nm.
L BAND ODD
1570.83nm, 1571.65nm, 1572.48nm, 1573.30nm, 1574.13nm, 1574.95nm, 1575.78nm, 1576.61nm, 1577.44nm, 1578.27nm, 1579.10nm, 1579.93nm, 1580.77nm, 1581.60nm, 1582.44nm, 1583.27nm, 1584.11nm, 1584.95nm, 1585.78nm, 1586.62nm, 1587.46nm, 1588.30nm, 1589.15nm, 1589.99nm, 1590.83nm, 1591.68nm, 1592.52nm, 1593.37nm, 1594.22nm, 1595.06nm, 1595.91nm, 1596.76nm, 1597.62nm, 1598.47nm, 1599.32nm, 1600.17nm, 1601.03nm, 1601.88nm, 1602.74nm, 1603.60nm.
L Band EVEN
1571.24nm; 1572.06nm; 1572.89nm; 1573.71nm; 1574.54nm; 1575.37nm; 1576.20nm; 1577.03nm; 1577.86nm; 1578.69nm; 1579.52nm; 1580.35nm; 1581.18nm; 1582.02nm; 1582.85nm; 1583.69nm; 1584.53nm; 1585.36nm; 1586.20nm; 1587.04nm; 1587.88nm; 1588.73nm; 1589.57nm; 1590.41nm; 1591.26nm; 1592.10nm; 1592.95nm; 1593.79nm; 1594.64nm; 1595.49nm; 1596.34nm; 1597.19nm; 1598.04nm; 1598.89nm; 1599.75nm; 1600.60nm; 1601.46nm; 1602.31nm; 1603.17nm; 1604.03nm.
2.2.5.5 Floating Termination Point
The FTP naming contains three tuples. The first tuple is the EMS name, the second tuple is the ME name, and the third tuple is the FTP name. The value of the name field in the third tuple is "FTP." The native name of FTP is a free-formatted string. However, CTM GateWay/CORBA follows the convention for PTP and CTP, if applicable.
In CTM R7.0, all Ethernet TPs for circuit provisioning on E-Series, G-Series, and ML-Series, FCMR cards are modeled as FTPs. The convention for the FTP values for Ethernet TPs is as follows:
•
•
•
•
•
•
•
•
•
2.2.5.6 Equipment
2.2.5.6.1 CRS-1
Table 2-28 lists the CRS-1 equipment that CTM R7.0 supports.
2.2.5.6.2 XR 12000
Table 2-29 lists the XR 12000 equipment that CTM R7.0 supports.
2.2.5.6.3 MGX 8880/8850/8830
Table 2-30 lists the MGX 8880/8850/8830 equipment that CTM R7.0 supports.
2.2.5.6.4 ONS 15216
The equipment is the ManagedElement itself for the following ONS 15216 NEs; ONS 15216 Terminal Filters, ONS 15216 OADMs, ONS 15216 EDFA, and ONS 15216 OSC.
Table 2-31 lists the ONS 15216 equipment that CTM R7.0 supports.
Table 2-32 lists the ONS 15216 FlexLayer equipment that CTM R7.0 supports.
2.2.5.6.5 ONS 15302
Table 2-33 lists the ONS 15302 equipment that CTM R7.0 supports.
2.2.5.6.6 ONS 15305
Table 2-34 lists the ONS 15305 equipment that CTM R7.0 supports.
Table 2-34 CTM-Supported ONS 15305 Equipment
E100-8
E1-21
E1-63
E1-8
E3T3-6
GE-1-LC
GE-2-LC
S1.1-2-LC
S1.1-8-LC
S16.1-1-LC
S4.1-2-LC
S4.1-4-LC
2.2.5.6.7 ONS 15310 CL
The equipment name is reported by the actual ManagedElement. The following table gives the list of supported equipment names. For the most current list, refer to the Cisco ONS 15310 CL user documentation for actual equipment names used by the NE.
Table 2-35 lists the ONS 15310 CL equipment that CTM R7.0 supports.
2.2.5.6.8 ONS 15310 MA
Table 2-36 lists the ONS 15310 MA equipment that CTM R7.0 supports.
Table 2-36 CTM-Supported ONS 15310 MA Equipment
CE-100T-8
CTX-2500
CTX-FILLER
DS1-28/DS3-EC1-6
DS1-84/DS3-EC1-3
EXP-FILLER
ML2-100T-8
PPM_1_PORT
2.2.5.6.9 ONS 15327
The equipment name is reported by the actual ManagedElement. The following table gives the list of supported equipment names. For the most current list, refer to the Cisco ONS 15327 user documentation for actual equipment names used by the NE.
Table 2-37 lists the ONS 15327 equipment that CTM R7.0 supports.
2.2.5.6.10 ONS 15454 SDH
The equipment name is reported by the actual ManagedElement. The following table gives the list of supported equipment names. For the most current list, refer to the Cisco ONS 15454 SDH user documentation for actual equipment names used by the NE.
Table 2-38 lists the ONS 15454 SDH equipment that CTM R7.0 supports.
2.2.5.6.11 ONS 15454 SONET
The equipment name is reported by the actual ManagedElement. The following table gives the list of supported equipment names. For the most current list, refer to the Cisco ONS 15454 SONET user documentation for actual equipment names used by the NE.
Note
Table 2-39 lists the ONS 15454 SONET equipment that CTM R7.0 supports.
2.2.5.6.12 ONS 15501
The equipment name is reported by the actual ManagedElement. Section D.1 Equipment List for ONS15501, page D-1 describes the list of equipment supported for the ONS 15501.
2.2.5.6.13 ONS 15530
The equipment name is reported by the actual ManagedElement. Section D.2 Equipment List for ONS15530, page D-1 describes the list of equipment supported for the ONS 15530.
2.2.5.6.14 ONS 15540
Appendix D.3 Equipment List for ONS15540 ESP, page D-14 and appendix D.4 Equipment List for ONS 15540 ESPx, page D-20 list the ONS 15540ESP and ONS 15540ESPx equipment that CTM supports.
2.2.5.6.15 ONS 15600
The equipment name is reported by the actual ManagedElement. The following table gives the list of supported equipment names. For the most current list, refer to the Cisco ONS 15600 user documentation for actual equipment names used by the NE.
Table 2-40 lists the ONS 15600 equipment that CTM R7.0 supports.
Table 2-40 CTM-Supported ONS 15600 Equipment
ASAP_4
OC12_PORT
OC192_4
OC3_PORT
OC48_16
OC48_32
OC48_PORT
PIM_4_PPM
PPM_1_PORT
SSXC
TSC
2.2.5.6.16 ONS 15600 SDH
The equipment name is reported by the actual ManagedElement. The following table gives the list of supported equipment names. For the most current list, refer to the Cisco ONS 15600 SDH user documentation for actual equipment names used by the NE.
Table 2-41 lists the ONS 15600 SDH equipment that CTM R7.0 supports.
2.2.5.6.17 ONS 15800 and ONS 15801
Table 2-42 lists the ONS 15800 and ONS 15801 equipment that CTM R7.0 supports.
Table 2-42 CTM-Supported ONS 15800 and ONS 15801 Equipment
24WD-LLR
—
24WD-R
—
24WD-RX
—
32WD-IR
—
8WD-B
—
ADA
—
BAT
—
BBA
—
BBA-10G
—
CMP-W
—
CMP-W-2E
—
CMP-W-2E-S
—
CMP-W-S
—
EMPTY-SLOT
—
EOI-W
—
IOC-W
—
IRBA
—
IRBA-10G
—
LEM10GFxx
xx = 1 ... 64
LEM10GMxx
xx = 1 ... 64
LEM10GNxx
xx = 1 ... 64
LEM10HMxx
xx = 1 ... 64
LEM622Nxx
xx = 1 ... 32
LEM-EMFxx
xx = 1 ... 64
LEM-EM-Mxx
xx = 1 ... 64
LEM-EM-Nxx
xx = 1 ... 32
LSM-W
—
OADM-P4-B1
—
OADM-P4-B2
—
OADM-P4-R1
—
OADM-P4-R2
—
OADM-P4-R3
—
OSU-W
—
PRE-L
—
PRE-L-IR
—
RBA
—
RBA-10G
—
RBA-10G-E
—
RBU-W
—
RXT10GF
—
RXT10GFxx
xx = 1 ... 64
RXT10GN
—
RXT10GNxx
xx = 1 ... 64
RXT10HM
—
RXT10HMxx
xx = 1 ... 64
RXT622N
—
RXT622Nxx
xx = 1 ... 32
RXT-DMF
—
RXT-DMFxx
xx = 1 ... 64
RXTDMLHM
RXTDMLHMxx
xx = 1 ... 32
RXT-DM-M
—
RXT-DM-Mxx
xx = 1 ... 64
RXT-DM-N
—
RXT-DM-Nxx
xx = 1 ... 32
SCF-W
—
TPA-B
—
TPA-IR
—
TPA-R
—
WCM10GFxx
xx = 1 ... 64
WCM10GMxx
xx = 1 ... 64
WCM10GNxx
xx = 1 ... 64
WCM10HMxx
xx = 1 ... 64
WCM622Nxx
xx = 1 ... 32
WCM-EMFxx
xx = 1 ... 64
WCM-EM-Mxx
xx = 1 ... 64
WCM-EM-Nxx
xx = 1 ... 32
1 xx represents the specific lambda wavelength as configured on the line card.
2.2.5.6.18 ONS 15808
Table 2-43 lists the ONS 15808 equipment that CTM R7.0 supports.
Table 2-43 CTM-Supported ONS 15808 Equipment
20MD-LE--D
—
20MD-LE--M
—
20MD-LO--D
—
20MD-LO--M
—
40MD-CE--D
—
40MD-CE--M
—
40MD-CO--D
—
40MD-CO--M
—
8MD-C
—
AIU
—
BCS-ELH
—
BCS-LH
—
BT10E-LCxx
xx = 1 ... 80
BT10G-LLxx
xx = 1 ... 40
CISCO-808-NE
—
CMP
—
CMP-S
—
EMPTY-SLOT
—
LT-10G-Cxx
xx = 1 ... 80
LT10G-SCxx
xx = 1 ... 80
LT10G-SLxx
xx = 1 ... 80
LT-25G-Cxx
xx = 1 ... 80
OAD-8-C
—
OA-ELH--L
—
OA-ELH--OA
—
OA-ELH--OD
—
OA-ELH--OR
—
OA-ELH--OT
—
OA-ELH--RC
—
OA-ELH--RE
—
OA-ELH--RO
—
OA-ELH--TX
—
OBA-C--ADL
—
OBA-C--ATX
—
OBA-C--DRX
—
OBA-C—L
—
OBA-C--RXE
—
OBA-C--RXO
—
OCP
—
OECP-C
—
OECP-C--P
—
OECP-L
—
OECP-L--P
—
OEP-C--ADL
—
OEP-C—L
—
OEP-C--RXE
—
OEP-C--RXO
—
OPA-C--ADL
—
OPA-C--ATX
—
OPA-C--DRX
—
OPA-C--LRX
—
OPA-C--LTX
—
OP-ELH--L
—
OP-ELH--OA
—
OP-ELH--OD
—
OP-ELH--OR
—
OP-ELH--OT
—
OP-ELH--RC
—
OP-ELH--RE
—
OP-ELH--RO
—
OP-ELH--TX
—
ORP-ELHxx
xx = 1 ... 2
OSCM
—
PLF
—
RT10G13C
—
RT10G13Cxx
xx = 1 ... 80
RT10G13L
—
RT10G13Lxx
xx = 1 ... 80
RT-10G-C
—
RT-10G-Cxx
xx = 1 ... 80
RT10G-SC
—
RT10G-SCxx
xx = 1 ... 80
RT10G-SL
—
RT10G-SLxx
xx = 1 ... 80
RT-25G-C
—
RT-25G-Cxx
xx = 1 ... 80
SCU
—
SNH
—
SNS
—
TT-10G-Cxx
xx = 1 ... 80
TT10G-SCxx
xx = 1 ... 80
TT10G-SLxx
xx = 1 ... 80
TT-25G-Cxx
xx = 1 ... 80
UDC
—
1 xx represents the specific lambda wavelength as configured on the line card.
2.2.5.6.19 MDS 9000
MDS 9000 NEs do not report any equipment.
2.2.5.6.20 Unmanaged NE
Unmanaged NEs do not report any equipment.
2.2.5.7 EquipmentHolder
The TMF defines the EquipmentHolder naming convention. Numbering is done from left to right and from top to bottom. For example, slot 15 is named /rack=1/shelf=1/slot=15.
For ONS 15xxx NEs, the numbering for EquipmentHolders starts from 0 in the NE. The TMF convention is to start numbering from 1 for EquipmentHolders. CTM does translation when reporting EquipmentHolder names.
For example, subslot 1 in slot 0 in the NE is named /rack=1/shelf=1/slot=1/sub_slot=2.
For the ONS 15454 multishelf termination point (MSTP) NEs, shelves are numbered using their unique shelf id, and not their physical location attributes, such as rack number and shelf position.
For example, slot 1 on an MSTP shelf with an id of 7 that is physically located in rack #1, shelf #2 is named /rack=1/shelf=7/slot=1.
For the ONS 155xx family, there is a new equipment holder called a port_holder. Because the TMF determines whether or not an equipment has to be in an EquipmentHolder, the port_holder is created to hold the transceiver modules that contain the PTPs. A port_holder that is present in subslot 1, slot 0 in an NE is named /rack=1/shelf=1/slot=1/sub_slot=2/port_holder=1.
A port holder present in slot 1 in an NE is named /rack=1/shelf=1/slot=2/port_holder=1.
For the ONS 15600 NE and ASAP cards, the PIM present in slot 3 is named /rack=1/shelf=1/slot=3/sub_slot=1 and the PPM present in PIM number 3 in slot 2 is named /rack=1/shelf=1/slot=2/sub_slot-3/ppm_holder=1.
For AdditionalHolder, the naming convention is defined as /additionalHolder=1; there is no subholder for additionalHolder. AdditionalHolders are applicable only to ONS 15454 SONET and SDH ManagedElements when AIE or AEP cards are installed.
For CRS-1 and XR 12000 slots that contain more than one card, each card will be modeled under a subslot. For example, if a PLIM is present under slot 1, the hierarchy will be:
/rack=1/shelf=1/slot=1/sub_slot=1/card=1
When a CRS-1 or XR 12000 slot, for example slot 1, contains an SPA jacket card, the hierarchy will be:
/rack=1/shelf=1/slot=1/sub_slot=1/spa_holder=1/card=1
For the MGX 8880/8850/8830, there is a new equipment holder called peripheral_holder. Because the TMF determines whether or not an equipment has to be in an EquipmentHolder, the peripheral_holder is created to hold the peripherals.
A peripheral_holder present on a shelf is named /rack=1/shelf=1/ /peripheral_holder=17236110, where the number 17236110 is the unique peripheral id.
A peripheral_holder present on a slot 1 is named /rack=1/shelf=1/slot=1/peripheral_holder=17236111, where the number 17236111 is the unique peripheral ID.
2.2.5.8 TopologicalLink
CTM discovers topological links and assigns a name with the following default format:
<MEName A:slot number/port number-ME Name B: slot number/port number >Integer values are used for slot and port number. You can use the CTM client to change the link name
For the ONS 15501, ONS 15530 and ONS 15540, the TopologicalLink name has the following format:
<ME NameA:InterfaceType/slot number/subslot number [/port number]-ME NameB:InterfaceType/slot number/subslot number[/port number ]>The port number is optional.
For example:
NE540A:Wdm0/0--NE540B:Wdm1/0NE540A:Wavepatch10/1/0--NE540A:Filter0/3/1CTM reports two TopologicalLinks for a Y-cable link. Both TopologicalLinks have the same nativeEMSName, but different values in the second tuple of the TopologicalLink name. The names "<nativeEMSName>:::1" and "<nativeEMSName>:::2" identify the two legs of the Y-cable link
2.2.5.9 ProtectionGroup
The protection group name reported by the NE is used as the PGP native name for 1_FOR_N and 1_PLUS_1 protection groups. The Ring ID is used as the PGP native name for 2_FIBER_BLSR and 4_FIBER_BLSR protection groups. The Ring Name is used instead of the Ring ID in this release. "<Ring Id>-EAST" and "<Ring Id>-WEST" are used as the native names for the two component groups of 4_FIBER_BLSR PGP
2.2.5.10 L2 Topology
L2 topology represents a point-to-point, hub-and-spoke, or Resilient Packet Ring (RPR) Layer 2 network topology. These topologies exist over the underlying Layer 1 topology, which is formed by physical topological links. Each L2 topology name is identified in the context of an EMS and has two tuples. The first tuple represents the EMS name, and the second tuple represents the nativeEMSName of the L2 topology. The L2 topology name is unique within an EMS. Each L2 topology can be associated with multiple MLVlans.
2.2.5.11 MLVlan
Each MLVlan is associated with an L2 topology and is unique for a given L2 topology. The fully qualified MLVlan name is identified by three tuples. The first tuple represents the EMS name, the second tuple represents the L2 topology name, and the last tuple represents the nativeEMSName of the MLVlan (which is the VLAN ID). A maximum of 255 MLVlans can be created per L2 topology, ranging from 1 to 4095.
2.2.5.12 QoSTemplate
QoSTemplate is defined in the scope of an EMS domain. The fully qualified QoSTemplate name is identified by two tuples. The first tuple represents the EMS name and the second tuple represents the QoSTemplate name.
2.2.5.13 VCAT
The fully qualified VCAT name is identified by two tuples. The first tuple represents the EMS name and the second tuple represents the VCAT name, which is the same as the nativeEMSName of the VCAT.
2.2.6 Programming Details
2.2.6.1 Boolean Mapping
The following Boolean parameters apply:
•
•
2.2.6.2 Resource Cleanup
Many TMF interfaces that CTM implements return iterator objects for large volumes of data. These iterators are allocated CTM resources. CTM supports a maximum of 128 iterators. If the iterator limit is reached, the NMS receives an EXCPT_TOO_MANY_OPEN_ITERATORS exception.
CTM, by default, cleans up all the iterator objects if they are not accessed in a time interval of six hours.
2.2.6.3 Development Environment
CTM GateWay/CORBA has been developed with Java Development Kit (JDK) 1.4.2 and JacORB object request broker (ORB) 2.x on Sun Solaris 2.9. JacORB 1.4 is portable object adapter (POA)-based and ORB-compliant with the CORBA 2.3 specification. You can use Java or the C++ IDL compiler to compile IDL files.
Note
2.2.6.4 Exception Handling
All interfaces implemented by CTM GateWay/CORBA raise the exception globaldefs::ProcessingFailureException. The following sections discuss each exception type in detail.
2.2.6.4.1 EXCPT_NOT_IMPLEMENTED
This exception indicates whether some IDL operations are optional or are not implemented in this release. If the operation itself is not supported, the errorReason is an empty string
2.2.6.4.2 EXCPT_INTERNAL_ERROR
This exception indicates an internal EMS error and applies to all methods.
2.2.6.4.3 EXCPT_INVALID_INPUT
This exception indicates an incorrect parameter format, such as a three-level namingAttribute termination point (TP) name that is passed as a single-level name. If a parameter is out of range, this exception is also used. The reason field contains the incorrect parameter.
2.2.6.4.4 EXCPT_ENTITY_NOT_FOUND
This exception indicates an incorrect parameter format, such as a three-level namingAttribute TP name that is passed as a single-level name. If a parameter is out of range, this exception is also used. The reason field contains the name that was passed as a parameter.
2.2.6.4.5 EXCPT_UNABLE_TO_COMPLY
This exception is used as a generic value when a server cannot respond to the request
2.2.6.4.6 EXCPT_NE_COMM_LOSS
This exception is used as a generic value when a server cannot communicate with the NE, preventing the successful completion of the operation. All operations that involve communication with the NE might return this exception type
2.2.6.4.7 EXCPT_ACCESS_DENIED
This exception indicates that an operation has resulted in a security violation. Verify that you have the required access to invoke the operation
2.2.6.4.8 EXCPT_TOO_MANY_OPEN_ITERATORS
This exception indicates that the EMS has exceeded the number of iterators it can support. CTM supports 128 iterators. If you receive this exception, it is possible that other sessions are retrieving data in large volume. Wait several minutes; then, retry. Alternately, close other sessions. To avoid this exception, the NMS must invoke the destroy method on iterators.
2.2.6.4.9 EXCPT_USERLABEL_IN_USE
This exception indicates that the userLabel uniqueness constraint cannot be met
2.2.6.4.10 EXCPT_STRICT_MERGE_FAILED
This exception is raised when an OSS issues an upgrade request to merge circuits with a STRICT MERGE operation type. This exception can be used by the OSS to issue the upgrade request with a LOOSE MERGE operation type.
2.2.7 Provisioning Subnetwork Connections
SNC provisioning must be within a MultiLayerSubnetwork scope, which means the aEnd and the zEnd of an SNC must be in the same MultiLayerSubnetwork.
CTM defines the method multiLayerSubnetwork::MultiLayerSubnetworkMgr_I::createAndActivateSNCFromUserLabel for SNC provisioning.
See the "Naming Conventions" section for naming conventions.
2.2.7.1 SNC Provisioning on OCn or Electrical Equipment
CTM supports SNC Provisioning on OCn or electrical cards for ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15600, and ONS 15310 NEs.
CTPs are used as the end points to create the SNC. See section Connection Termination Point for naming conventions.
2.2.7.2 SNC Provisioning on Ethernet Equipment
The ONS 15454 SONET, ONS 15454 SDH, ONS 15327, and ONS 15310 managed elements support Ethernet equipment. SNC can be created on this equipment to carry Ethernet traffic. The TMF standard supports only SONET, SDH, DWDM, and ATM; it does not support Ethernet at this time.
Creating SNC provisioning on E-series, G-series, and ML-series equipment supported by the ONS 15310, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH is different from creating SNC on SONET or PDH equipment. For SNCs on Ethernet equipment, CTM uses FTP to model the end point. For SNCs on Ethernet equipment, CTM uses FTP to model the end point. See section Floating Termination Point for naming conventions.
The three modes supported for SNC provisioning on Ethernet equipment are:
•
•
•
To get available source and destination FTPs for SNC provisioning, use the following methods:
•
•
2.2.7.2.1 Single-Card Mode and Multicard Mode
By default, all E-series cards are in the multicard mode EtherSwitch group. Each node has only one multicard mode EtherSwitch group; the group exists even if the node has no Ethernet cards. To create SNC in multicard mode, both aEnd and zEnd must be in the multicard EtherSwitch group.
A single-card EtherSwitch group can exist only if a node has at least one Ethernet card. To create SNC in single-card mode, one end can be OCn CTP. You must create bidirectional SNC
Table 2-44 shows the maximum bandwidth allowed for single-card EtherSwitches and multicard EtherSwitches:
2.2.7.2.2 Linear-Card Mode
You can apply linear-card mode SNC provisioning to all types of Ethernet cards. One end of the SNC must be an FTP; the other end can be a CTP on any OCn port, or an FTP. The FTPs must use linear-mode naming conventions.
Only single source and single destination are supported for the SNC creation, and the SNC must be bidirectional.
For E-series and G-series cards, the port number in the FTP name is the number of the front Ethernet port. For ML-series cards, the port number is the number of the virtual back-end port.
2.2.7.2.3 Layer Rates
CTM supports the following layer rates for E-Series cards:
–
–
–
–
CTM supports the following layer rates for G-Series cards:
–
–
–
–
–
–
–
CTM supports the following layer rates for ML-Series cards:
–
–
–
–
–
–
CTM supports the following layer rates for FCMR cards:
–
–
2.2.7.3 Tunnel SNC Provisioning
CTM supports tunnel SNC provisioning on ONS 15327, ONS 15454 SONET, ONS 15454 SDH, and ONS 15310 NEs. The tunnel circuit must be bidirectional.
The tunnel SNC for the ONS 15310, ONS 15327, and ONS 15454 SONET is called VT tunnel, and the layer rate must be 14 (LR_STS1_and_AU3_High_Order_VC3). The tunnel SNC for the ONS 15454 SDH is called VCTunnel, and the layer rate must be 15 (LR_STS3c_and_AU4_VC4). See section Naming Conventions for naming conventions.
Only one aEnd and zEnd are specified for the VT/VC tunnel SNC provisioning.
CTM only supports fully automatically routed VT/VC tunnel SNCs. CTM does not support manually routed and constraint-based automatically routed VT/VC tunnel SNCs.
CTM supports VCTunnel for VC3 port grouping SNC provisioning on ONS 15454 SDH. For VC tunnelVC tunnelVC tunnel for VC3 port grouping SNC provisioning, if the source or destination end is an STM-N card, it is modeled as CTP, and if the source or destination end is on an E3, DS3I, or DS3IN card, it is modeled as FTP.
Table 2-45 shows the combinations of cards that can be selected for creating the VC4 Tunnel for VC3 port grouping circuits.
Table 2-45 Tunnel SNC Provisioning
DS3I or DS3IN
DS3I, DS3IN or STMn
E3
E3 or STMn
STMn
DS3I, DS3IN or E3
When VCTunnel for VC3 port grouping SNC provisioning is complete:
•
•
Deleting one PGC SNC results in the deletion of all four SNCs. You cannot delete a PGT SNC if any PGC SNCs exist. See Naming Conventions for the naming conventions.
2.2.7.4 SNC Provisioning on WDM Equipment
2.2.7.4.1 OCHCC Circuit Provisioning
CTM supports optical channel client connection (OCHCC) circuit provisioning on transponders, muxponders, and International Telecommunication Union (ITU-T) line cards for ONS 15454 SONET and ONS 15454 SDH NEs.
We will refer to them as OCHCC SNC. The OCHCC SNC is created between client ports on transponders, muxponders cards, or trunk ports on ITU-T line cards.
OCHCC is an extension of the optical channel network connection (OCHNC). OCHCC is a part of the OCHCC SNC. OCHCC can just have one source and one destination.
CTP naming is identical to OCHNC SNCs. See Section Connection Termination Point for the CTP details.
CTPs used in WDM SNCs do not use the same naming as CTPs used in SONET or SDH SNCs. The layer rate for the CTPs and WDM SNC is always LR_Optical_Channel. For information about the CTP naming conventions used in WDM SNCs, see the "Connection Termination Point" section.
OCHCC must be bidirectional.
CTM supports different sizes corresponding to possible payload types of transponder and muxponder client ports. A specific layer must be defined for each payload type.
OCHCC is either unprotected or protected. Protected is only created on protected transponders or muxponders cards where there is a protected trunk port.
Note
2.2.7.4.2 OCHNC Circuit Provisioning
CTM supports OCHNC circuit provisioning on some of the WDM cards for ONS 15454 SONET and ONS 15454 SDH NEs. We will refer to them as WDM SNC. The WDM SNC is created on a particular wavelength channel with a direction of either east-to-west or west-to-east. The WDM SNCs are basically unidirectional. CTM GateWay/CORBA supports the creation of bidirectional OCHNC circuits on NE releases 5.0 and later. You can also create two unidirectional OCHNC circuits on the same frequency, one west-to-east and one east-to-west.
The CTPs used in the WDM SNC are different from the CTPs used in SONET/SDH SNCs in terms of naming and nature. See Connection Termination Point for the CTP naming conventions. The layer rate for the CTPs and WDM SNC must be LR_Optical_Channel.
The OCHNC size is "Equipped not specific."
For NE releases 6.0 and earlier, to create a bidirectional OCHNC you must specify all four CTPs (which are source, destination, secondary source, and secondary destination in the API). The secondary source/destination must be the CTPs in the opposite direction: If the circuit is from node A to B, the secondary source is on node B, and the secondary destination is on node A. You can specify four possible directions:
•
•
•
•
For NE releases 7.0 and later, you must specify only the primary source and destination CTPs; the remaining CTPs are identified automatically. You can specify the following directions:
•
•
2.2.7.5 Low-Order Circuit Provisioning Using VAP/LAP
CTM supports low-order circuit provisioning using VT aggregation point (VAP) circuits on ONS 15310, ONS 15327, and ONS 15454 SONET NEs, and low-order aggregation point (LAP) circuits on ONS 15454 SDH NEs. The VAP/LAP circuits have to be bidirectional.
When provisioning VAP/LAP circuits, the source is treated as STS grooming end, and the destination is treated as VT grooming end and will later be used to hook up VT circuits.
The source is a CTP and the destination is an FTP. See Section Naming Conventions for naming conventions.
