-
Cisco Transport Manager GateWay/CORBA User's Guide and Programmer Manual, 9.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 Use Cases and Client Development
-
Appendix D: Equipment List for NEs
-
Table Of Contents
2.1.3 ONS 15305 and ONS 15305 CTC
2.1.15 ONS 15800 and ONS 15801
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.
The following sections include NE- and CTM-specific details:
Note
In this document, the terms network element (NE) and managed element (ME) are interchangeable. Also, card and equipment strings are used interchangeably to refer to equipment.
2.1 NE-Specific Details
2.1.1 ONS 15216
Some NEs in the ONS 15216 family do not provide a management interface. These NEs are considered passive because the user enters all data from the CTM client. After the data has been entered, CTM reports these NEs. Other ONS 15216 NEs provide a management interface; these NEs are considered active.
See the Release Notes for Cisco Transport Manager Release 9.0 for the passive and active ONS 15216 software releases that CTM R9.0 supports.
Note
2.1.1.1 PTPs
CTM reports PTPs for ONS 15216 NEs only if a topological link originates from or terminates on the ONS 15216 NE.
2.1.1.2 Topological Links
Topological links are unidirectional for ONS 15216 NEs. Inter-NE links are available between all NEs in the ONS 15216 family. CTM supports links between an ONS 15216 and the following NEs at compatible layer rates:
•
•
•
•
•
2.1.2 ONS 15302
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15302 software releases that CTM R9.0 supports.
2.1.2.1 Slots
The ONS 15302 is a single-shelf NE with four slots. Slot 4 is the only slot that contains a removable card. Cards in slots 1, 2, and 3 cannot be removed.
2.1.2.2 PTPs
The ONS 15302 supports PTPs associated to WAN, SDH, and PDH ports.
2.1.3 ONS 15305 and ONS 15305 CTC
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15305 software releases that CTM R9.0 supports.
Note
2.1.3.1 Slots
The ONS 15305 and ONS 15305 CTC are single-shelf NEs with four slots.
2.1.3.2 PTPs
The ONS 15305 and ONS 15305 CTC support PTPs associated to WAN, SDH, and PDH ports.
2.1.4 ONS 15310 CL
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15310 CL software releases that CTM R9.0 supports.
2.1.4.1 Slots
The ONS 15310 CL is a single-shelf NE with two slots. Slot 1 is the expansion slot and contains the provisionable data card. Slot 2 is a nonreplicable unit and contains the Control Timing and Cross-Connect (CTX)-CL controller.
2.1.4.2 Equipment
All cards for the ONS 15310 CL R5.0 and later display administration and service states. For earlier software releases, these states are not applicable and CTM displays them as N/A. The following tables show the attribute values for these two states.
2.1.4.2.1 Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. Table 2-1 lists the attribute values for the administration state. Table 2-2 and Table 2-3 list the attribute values for the service state.
2.1.4.2.2 Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. The attribute value for the service state is the same as that shown in CTM.
2.1.4.3 Topological Links
All topological links are unidirectional or bidirectional for ONS 15310 CL NEs.
2.1.4.4 CTX Cards
The CTX card is an electrical card that consists of 21 digital signal level 1 (DS1) ports and three DS3/EC1 ports. Two optical interfaces are supported using SFP technology. OC-3/STM-1 and OC-12/STM-4 ports are available.
2.1.4.5 PTPs
All PTPs are bidirectional for the 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.4.6 CTPs
All CTPs are in channelized mode for the ONS 15310 CL.
2.1.4.7 SNCs
CTX cards perform synchronous transport signal (STS) and VT1.5 switching. The subnetwork connection (SNC) name cannot exceed 48 characters. The NE enforces the SNC name character limit.
2.1.4.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 must 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 listens to the AVC event for the managed element name and invokes managedElementManager::ManagedElementManager_I:: getManagedElement.
2.1.5 ONS 15310 MA SDH
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15310 MA SDH software releases that CTM R9.0 supports.
2.1.5.1 Slots
The ONS 15310 MA SDH consists of two CTX slots and four Expansion (EXP) I/O slots.
2.1.5.2 Topological Links
All topological links are unidirectional or bidirectional for ONS 15310 MASDH NEs.
2.1.5.3 Cards
The ONS 15310 MA SDH supports the following cards:
•
–
–
•
•
2.1.5.4 PTPs
All PTPs are bidirectional for the ONS 15310 MA SDH. The ports are always in channelized mode. PTPs support In Service and Out of Service-Maintenance values for the service state attribute.
SNC provisioning on E1_21_DS3_3 and E1_63_E3_3 cards uses the following DS3/E3 ports:
•
•
2.1.5.5 Auto Discovery
The ONS 15310 MA 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. However, CTM must 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 AVC event is generated for the managed element name. The NMS listens to the AVC event for the managed element name and invokes managedElementManager::ManagedElementManager_I:: getManagedElement.
2.1.6 ONS 15310 MA SONET
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15310 MA SONET software releases that CTM R9.0 supports.
2.1.6.1 Slots
The ONS 15310 MA SONET consists of two CTX slots and four EXP I/O slots.
2.1.6.2 Topological Links
All topological links are unidirectional or bidirectional for ONS 15310 MA SONET NEs.
2.1.6.3 CTX Cards
The CTX card is an electrical card that consists of 21 DS1 ports and three DS3/EC-1 ports. Two optical interfaces are supported using SFP technology. OC-3/STM-1 and OC-12/STM-4 ports are available.
•
•
2.1.6.4 PTPs
All PTPs are bidirectional for the ONS 15310 MA SONET. The ports are always in channelized mode. PTPs support In Service and Out of Service-Maintenance values for the service state attribute.
SNC provisioning on DS1_28_DS3_3 and DS1_84_DS3_3 cards uses the following DS3/EC1 ports:
•
•
2.1.6.5 CTPs
All CTPs are in channelized mode for the ONS 15310 MA SONET.
2.1.6.6 SNCs
CTX cards perform STS and VT1.5 switching. The SNC name cannot exceed 48 characters. The NE enforces the SNC name character limit.
2.1.6.7 Auto Discovery
The ONS 15310 MA 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 must 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 AVC event is generated for the managed element name. The NMS listens to the AVC event for the managed element name and invokes managedElementManager::ManagedElementManager_I:: getManagedElement.
2.1.7 ONS 15327
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15327 software releases that CTM R9.0 supports.
2.1.7.1 Slots
The ONS 15327 is a single-shelf NE with eight slots. The Mechanical Interface Card (MIC) A card must occupy slot 8; the MIC B card must occupy slot 7. If an integrated Cross-Connect, Timing, and Control (XTC) card is required, it must occupy slot 5 or slot 6.
2.1.7.2 Equipment
All of the cards in the ONS 15327 R5.0 and later display administration and service states. For earlier software releases, these states are not applicable and CTM displays them as N/A.
2.1.7.2.1 Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. Table 2-4 lists the attribute values for the administration state. Table 2-5 and Table 2-6 list the attribute values for the service state.
2.1.7.2.2 Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. The attribute value for the service state is the same as that shown in CTM.
2.1.7.3 Topological Links
All topological links are unidirectional or bidirectional for ONS 15327 NEs.
2.1.7.4 XTC Cards
The XTC-14 card has 14 DS1 ports numbered 1 through 14. Only VT1.5 SNCs can be created on these ports. The XTC-28-3 card has 28 DS1 ports numbered 1 through 28 and 3 DS3 ports numbered 29 through 31. VT1.5 SNCs can be created on DS1 ports, and STS-1 SNCs can be created on DS3 ports.
2.1.7.5 PTPs
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.7.6 CTPs
All CTPs are in channelized mode for the ONS 15327. Alarm monitoring cannot be turned on or off for CTPs.
2.1.7.7 SNCs
XTC cards perform STS and VT1.5 switching. The XTC cards support the total rearrangement of 192 bidirectional STSs from the four high-speed slots (1 to 4), plus 12 bidirectional STSs for XTC module low-speed electrical interfaces. The XTC VT1.5 matrix supports the grooming of 336 bidirectional VT1.5 circuits.
The SNC name cannot exceed 48 characters.
2.1.7.8 Autodiscovery
ONS 15327 autodiscovery is identical to ONS 15454 SONET autodiscovery, described in Autodiscovery.
2.1.8 ONS 15454 SDH
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15454 SDH software releases that CTM R9.0 supports.
2.1.8.1 Shelves
All supported ONS 15454 SDH NEs have exactly one shelf each, with the exception of the ONS 15454 SDH multiservice transport platform (MSTP) R7.0, which can have up to eight shelves per NE.
2.1.8.2 Slots
The ONS 15454 SDH 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. The Timing Communications and Control-International (TCC-I) module 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.8.3 Equipment
All cards in the ONS 15454 SDH R5.0 and later display administration and service states. For earlier software releases, these states are not applicable and CTM displays them as N/A.
2.1.8.3.1 Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. Table 2-7 lists the attribute values for the administration state. Table 2-8 and Table 2-9 list the attribute values for the service state.
2.1.8.3.2 Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. The attribute value for the service state is the same as that shown in CTM.
2.1.8.4 Topological Links
Topological links are unidirectional or bidirectional for ONS 15454 SDH NEs.
2.1.8.5 PTPs
All PTPs are bidirectional for the ONS 15454 SDH, except for PTPs on DWDM cards (optical amplifiers, optical multiplexers, optical demultiplexers, and optical add/drop multiplexers). 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.8.6 CTPs
All CTPs are in channelized mode for the ONS 15454 SDH. Alarm monitoring cannot be turned on or off for CTPs.
2.1.8.7 SNCs
One node supports a maximum of 192 bidirectional VC4 SNCs. The SNC name cannot exceed 48 characters. The NE enforces the SNC name character limit.
2.1.8.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. 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.8.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.8.10 Autodiscovery
ONS 15454 SDH autodiscovery is identical to ONS 15454 SONET autodiscovery, described in Autodiscovery.
2.1.9 ONS 15454 SONET
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15454 SONET software releases that CTM R9.0 supports.
2.1.9.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.9.2 Slots
Each ONS 15454 SONET shelf has 17 slots. The Timing Communications and Control Plus (TCC+) card must occupy slot 7 or slot 11. For more information, refer to the Cisco ONS 15454 SONET user documentation.
2.1.9.3 Equipment
All the cards in the ONS 15454 SONET R5.0 and later display administration and service states. For earlier software releases, these states are not applicable and CTM displays them as N/A. The following tables show the attribute values for these two states.
2.1.9.3.1 Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. Table 2-10 lists the attribute values for the administration state. Table 2-11 and Table 2-12 list the attribute values for the service state.
2.1.9.3.2 Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. The attribute value for the service state is the same as that shown in CTM.
2.1.9.4 Topological Links
Topological links are unidirectional or bidirectional for ONS 15454 SONET NEs.
2.1.9.5 PTPs
All PTPs are bidirectional for the ONS 15454 SONET, except for PTPs on DWDM cards (optical amplifiers, optical multiplexers, optical demultiplexers, and optical add/drop multiplexers). 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.9.6 CTPs
All CTPs are in channelized mode for the ONS 15454 SONET. Alarm monitoring cannot be turned on or off for CTPs.
2.1.9.7 SNCs
One node supports a maximum of 144 bidirectional STS SNCs with an XC or Cross-Connect Virtual Tributary (XCVT) card installed or 576 bidirectional STS SNCs with a 10 Gigabit Cross-Connect (XC10G) card installed. If an XCVT or XC10G card is present, you can create a maximum of 336 bidirectional VT1.5 SNCs.
The SNC name cannot exceed 48 characters. The NE enforces the SNC name character limit.
2.1.9.8 Equipment Protection
1:N equipment protection is supported for DS1, DS3, 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. Installing DS1N or DS3N cards in slot 3 or slot 15 does not automatically protect other DS1 or DS3 cards. 1:N equipment protection is always revertive.
1:1 equipment protection is supported for DS1, DS3, 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.
2.1.9.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.9.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 must 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 AVC event is generated for the managed element name. The NMS listens to the AVC event for the managed element name and invokes managedElementManager::ManagedElementManager_I:: getManagedElement.
2.1.10 ONS 15501
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15501 software releases that CTM R9.0 supports.
2.1.10.1 Slots
The ONS 15501 is a single-shelf system with no slots.
2.1.10.2 PTPs
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.10.3 CTPs
CTM GateWay/CORBA does not support CTPs for the ONS 15501.
2.1.10.4 SNCs
CTM GateWay/CORBA does not support SNCs for the ONS 15501.
2.1.10.5 Equipment
The ONS 15501 has no removable equipment. The chassis is reported as equipment under the shelf equipment holder.
2.1.10.6 Topological Links
Topological links are unidirectional for ONS 15501 NEs.
2.1.11 ONS 15530
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15530 software releases that CTM R9.0 supports.
2.1.11.1 Slots
The ONS 15530 is a single-shelf NE with 13 slots. It has a dual-CPU system with integrated switch fabric. The processor cards occupy slot 6 and slot 7. Slot 1 contains the multiplexer/demultiplexer motherboards, which are populated with optical multiplexer/demultiplexer modules. The remaining slots can contain:
•
•
•
•
•
2.1.11.2 PTPs
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.11.3 CTPs
CTM GateWay/CORBA does not support CTPs for the ONS 15530.
2.1.11.4 SNCs
CTM GateWay/CORBA does not support SNCs for the ONS 15530.
2.1.11.5 Equipment Protection
1:1 equipment protection is supported for the CPU card.
2.1.11.6 Equipment
The ONS 15530 reports all field-replaceable units (FRUs) as equipment. The chassis is also reported as equipment under the shelf equipment holder.
2.1.11.7 Topological Links
Topological links are unidirectional or bidirectional for ONS 15530 NEs. CTM reports both inter-NE and intra-NE links for the ONS 15530.
2.1.11.8 PTP Layer Rates
The ONS 15530 supports the following additional PTP layer rates:
•
•
•
•
•
2.1.12 ONS 15540
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15540 ESP and ESPx software releases that CTM R9.0 supports.
2.1.12.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 slot 7 and slot 8. Slot 1 and slot 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.12.2 PTPs
All PTPs are bidirectional for the ONS 15540. PTPs do not support the service state attribute.
Wavepatch interfaces on transponder cards and filter interfaces on multiplexer/demultiplexer cards are reported as PTPs, even though the cards are not visible externally from the fixed optical backplane. Wave interfaces on 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.12.3 CTPs
CTM GateWay/CORBA does not support CTPs for the ONS 15540.
2.1.12.4 SNCs
CTM GateWay/CORBA does not support SNCs for the ONS 15540.
2.1.12.5 Equipment Protection
1:1 equipment protection is supported for CPU cards.
2.1.12.6 Equipment
The ONS 15540 reports all FRUs as equipment. The chassis is also reported as equipment under the shelf equipment holder.
2.1.12.7 Topological Links
Topological links are unidirectional or bidirectional for ONS 15540 NEs. CTM reports both inter-NE and intra-NE links for the ONS 15540.
2.1.12.8 PTP Layer Rates
The ONS 15540 supports the following additional PTP layer rates:
•
•
•
•
•
2.1.13 ONS 15600 SONET
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15600 SONET software releases that CTM R9.0 supports.
2.1.13.1 Slots
The ONS 15600 SONET 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. Single Shelf Cross-Connect (SSXC) cards replace CXC cards from release 5.0 of the NE. However, due to a known caveat (CSCse87505), CTM and CTC display SSXC cards as CXC. For more information, refer to the Cisco ONS 15600 SONET user documentation.
2.1.13.2 Equipment
All cards in the ONS 15600 SONET R5.0 and later display administration and service states. For earlier software releases, these states are not applicable and CTM displays them as N/A.
2.1.13.2.1 Equipment Administration State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. Table 2-13 lists the attribute values for the administration state. Table 2-14 and Table 2-15 list the attribute values for the service state.
2.1.13.2.2 Equipment Service State
The attribute name is ACTUAL_EQUIPMENT_SERVICE_STATE and is displayed in getAdditionalInfo for the equipment. The attribute value for the service state is the same as that shown in CTM.
2.1.13.3 Topological Links
Topological links are unidirectional or bidirectional for ONS 15600 SONET NEs.
2.1.13.4 PTPs
All PTPs are bidirectional for the ONS 15600 SONET. These ports are always in channelized mode. PTPs support In Service and Out of Service-Maintenance values for the service state attribute.
2.1.13.5 CTPs
All CTPs are in channelized mode for the ONS 15600 SONET. Alarm monitoring cannot be turned on or off for CTPs.
2.1.13.6 SNCs
One ONS 15600 SONET NE supports a maximum of 1536 STS SNCs.
2.1.13.7 Protection
The ONS 15600 SONET 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 only by port 1 on another OC-48 card.
2.1.13.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. However, CTM must 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 AVC event is generated for the managed element name. The NMS listens to the AVC event for the managed element name and invokes managedElementManager::ManagedElementManager_I:: getManagedElement.
2.1.14 ONS 15600 SDH
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15600 SDH software releases that CTM R9.0 supports.
2.1.14.1 Slots
The ONS 15600 SDH is a single-shelf NE with 14 slots. The TSC card must occupy slot 5 or slot 10. The 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. SSXC cards replace CXC cards from release 5.0 of the NE. For more information, refer to the Cisco ONS 15600 SDH user documentation.
2.1.14.2 Topological Links
Topological links are unidirectional or bidirectional for ONS 15600 SDH NEs.
2.1.14.3 PTPs
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 the service state attribute.
2.1.14.4 CTPs
All CTPs are in channelized mode for the ONS 15600 SDH. Alarm monitoring cannot be turned on or off for CTPs.
2.1.14.5 SNCs
One ONS 15600 SDH NE supports a maximum of 1536 VC4 SNCs.
2.1.14.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 only by port 1 on another STM-16 card.
2.1.14.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. However, CTM must 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 AVC event is generated for the managed element name. The NMS listens to the AVC event for the managed element name and invokes managedElementManager::ManagedElementManager_I:: getManagedElement.
2.1.15 ONS 15800 and ONS 15801
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15800 and ONS 15801 software releases that CTM R9.0 supports.
2.1.15.1 Racks
Each ONS 15800 or ONS 15801 can have from one to ten racks.
2.1.15.2 Shelves
Each ONS 15800 or ONS 15801 has three shelves per rack.
2.1.15.3 Slots
Each ONS 15800 has 17 slots per shelf. Each ONS 15801 has 15 slots per shelf.
2.1.15.4 Topological Links
All topological links are unidirectional for ONS 15800 and ONS 15801 NEs.
2.1.15.5 PTPs
All PTPs are unidirectional for ONS 15800 and ONS 15801 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).
Links can be established between PTPs supported by the following boards:
•
•
Each board can delimit only a link.
2.1.16 ONS 15808
See the Release Notes for Cisco Transport Manager Release 9.0 for the ONS 15808 software releases that CTM R9.0 supports.
2.1.16.1 Racks
Each ONS 15808 can have from one to ten racks.
2.1.16.2 Shelves
Each ONS 15808 has three shelves per rack.
2.1.16.3 Slots
Each ONS 15808 has 15 slots per shelf.
2.1.16.4 Topological Links
All topological links are unidirectional for the ONS 15808 NEs.
2.1.16.5 PTPs
All PTPs are unidirectional for ONS 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 with 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, with opposite directions.
2.1.17 MGX 8880/8850/8830
See the Release Notes for Cisco Transport Manager Release 9.0 for the MGX software releases that CTM R9.0 supports.
2.1.17.1 Racks
The MGX 8880/8850/8830 is a single-rack NE.
2.1.17.2 Shelves
Each MGX 8880/8850/8830 NE has one shelf per rack.
2.1.17.3 Slots
The MGX 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.
The MGX 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.17.4 Subslots
The MGX 8880/8850/8830 slot is divided into subslots or bays. The full-height cards (AXSM, VXSM, PXM, RPM, and PXM1E) have two subslots; the half-height cards (VISM, MPSM, and SRME) have one subslot. The subslots contain the back card for the corresponding front card.
2.1.17.5 PTPs
All PTPs are bidirectional for MGX 8880/8850/8830 NEs. PTPs do not support the service state attribute but do support the layer rate attribute.
2.1.18 MDS 9000
The MDS 9000 is a passive storage NE that does not contain any equipment. CTM reports PTPs for the MDS 9000 only if a topological link originates from or terminates on the MDS 9000. There are no alarms reported for the MDS 9000.
2.1.19 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 a topological link originates from or terminates on the unmanaged NE. There are no alarms reported for unmanaged NEs.
2.2 CTM-Specific Details
2.2.1 Layer Rate
Note
CTM R9.0 supports the following layer rates:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
2.2.2 Inventory
The ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15501, ONS 15530, ONS 15540, ONS 15600 SONET, and ONS 15600 SDH are single-shelf NEs. However, in future they may be expanded to multishelf, multibay NEs. Considering this, CTM reports the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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:
•
•
•
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
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.
In addition to implementing TMF-defined interfaces, CTM defines the following new proprietary 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:
•
•
There are four ways to add NEs to subnetworks:
•
•
•
•
SNC creation is limited within a multilayer subnetwork scope. For example, assume Subnetwork-1 contains two NEs, A and B, that are connected to each other with an autodiscovered link. Subnetwork-2 contains two NEs, C and D, that are connected to each other with an autodiscovered link. There is also a manually routable link between NEs B and C. To create an SNC between NEs A and D, you must move NEs C and D into Subnetwork-1, or move NEs A and B into Subnetwork-2.
CTM includes a 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 merges the two subnetworks, the result is reflected in CTM GateWay/CORBA. The two subnetworks are merged automatically when the Automatically Group NEs in Subnetworks feature is enabled in CTM.
2.2.4.2 SNCs
SNCs are supported only for ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15600 SONET, and ONS 15600 SDH NEs. CTM does not support SNC in 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 makes a get call to retrieve the object details.
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
The following table lists the MultiLayerSubnetwork_T attributes and where they are reported.
Table 2-16 MultiLayerSubnetwork_T
name
cache
nativeEMSName
cache
subnetworkType
cache
2.2.4.5.2 EMS_T
The following table lists the EMS_T attributes and where they are reported.
Table 2-17 EMS_T
name
cache
nativeEMSName
cache
emsVersion
constant value
type
constant value
2.2.4.5.3 Equipment_T
The following table lists the Equipment_T attributes and where they are reported.
Note
Table 2-18 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
The following table lists the EquipmentHolder_T attributes and where they are reported.
Note
Table 2-19 EquipmentHolder_T
name
cache
nativeEMSName
cache
holderType
cache
expectedOrInstalledEquipment
cache
acceptableEquipmentTypeList
cache
holderState
cache
2.2.4.5.5 TerminationPoint_T
The following table lists the TerminationPoint_T attributes and where they are reported.
Note
2.2.4.5.6 SubnetworkConnection_T
The following table lists the SubnetworkConnection_T attributes and where they are reported.
Note
2.2.4.5.7 ManagedElement_T
The following table lists the ManagedElement_T attributes and where they are reported.
Note
2.2.4.5.8 TopologicalLink_T
The following table lists the TopologicalLink_T attributes and where they are reported.
Note
Table 2-23 TopologicalLink_T
name
cache
nativeEMSName
cache
direction
cache
rate
cache
aEndTP
cache
zEndTP
cache
2.2.4.5.9 ProtectionGroup_T
The following table lists the ProtectionGroup_T attributes and where they are reported.
Note
Table 2-24 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
The following table lists the ServerTrailLink_T attributes and where they are reported.
2.2.5 Naming Conventions
The following sections describe naming conventions for objects that CTM reports.
2.2.5.1 Multilayer Subnetwork
You define the name in the CTM client. If you do not specify a name, CTM assigns a default name.
2.2.5.2 Managed Element
The ME reports the name.
2.2.5.3 Physical Termination Point
The PTP name represents the position of the PTP with respect to the equipment. For example, port number 4 on equipment in slot 15 is reported as /rack=1/shelf=1/slot=15/port=4.
For multishelf NEs, the rack and shelf number must be included in the PTP name. ONS 15454 MSTP NEs support up to eight shelves per NE. The shelf ID identifies a specific shelf on the NE. The rack ID remains 1 for all shelves.
This PTP naming convention is used to represent the front Ethernet ports for the ONS 15454 SONET and ONS 15454 SDH ML-series cards. The back Ethernet ports are reported as floating termination points (FTPs).
For class of service (CoS) data on data cards, the PTP name specifies the interface (POS, Fast Ethernet, Gigabit Ethernet), direction (input/output), and CoS level (0 to 7).
For example, CoS data with a POS interface, input direction, and CoS level 3 for slot 1, port 1 is reported as rack=1/shelf=1/slot=1/port=1:POS/Input/3.
Similarly, CoS data with a Fast Ethernet interface, output direction, and CoS level 5 for slot 1, port 1 is reported as /rack=1/shelf=1/slot=1/port=1:FastEthernet/Output/5.
For the ONS 15600 SONET, the ASAP card on slot 3, port 1 on PPM 3 and PIM 2 is reported as /rack=1/shelf=1/slot=3/sub_slot=2/ppm_holder=3/port=1.
For the ONS 15310 CL, ONS 15310 MA SONET, and ONS 15310 MA SDH, a port on PPM number 2 is reported as /rack=1/shelf=1/slot=2/ppm_holder=2/port=1.
For the ONS 15454 SONET and ONS 15454 SDH, a port on PPM number 2 is reported as /rack=1/shelf=1/slot=2/ppm_holder=2/port=1.
For the ONS 15501, ONS 15530, and ONS 15540, the PTP name represents the position of the PTP with respect to the equipment. It also specifies the CLI name, since there can be more than one interface type with 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 translates PTP names.
For example, the wavepatch0/0/0 port (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.
The transparent0/0/0 port (which is 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. Because the subslot does not apply to this port, it is skipped.
The In-Port on the ONS 15501 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:0.
Subslot and port are not significant for ONS 158xx equipment. The direction can have the following values:
•
•
•
•
PTPs of three port GE line cards in slot 3 is reported as /rack=1/shelf=1/slot=3/sub_slot=0/port=0, /rack=1/shelf=1/slot=3/sub_slot=0/port=1, and /rack=1/shelf=1/slot=3/sub_slot=0/port=2.
For unmanaged NEs, the PTP native name is a free-format string.
For the MGX 8880/8850/8830, the PTP name represents the position of the PTP with respect to the equipment. For example, port number 4 on equipment in slot 10 and bay 1 is reported as /rack=1/shelf=1/slot=10/subslot=1/port=4.
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 the ONS 15327 R3.3 or later, ONS 15454 SONET R3.2.1 or later, and ONS 15454 SDH R3.3 or later, CTM supports STS6c, STS9c, and STS24c layer rates. On the ONS 15327 R5.0 or later, ONS 15454 SONET R5.0 or later, and ONS 15454 SDH R5.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.
The following table shows the CTM CTPs for STS6c, STS9c, STS24c, STS18c, and STS36c layer rates. The number after `-r' is the difference between the STS/VC4 number and the previous edge STS/VC4 number.
In addition, the following CTP name support has been added:
For CTPs used for WDM SNCs (optical channel network connection [OCHNC], optical channel client connection [OCHCC], and OCH trail tunnels), 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 is "/direction=src or sink/frequency=nnn.mm" for WDM SNC CTPs.
Because the CTM client uses wavelengths 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:
•
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).
•
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:
•
1529.55 nm, 1530.33 nm, 1531.12 nm, 1531.90 nm, 1532.68 nm, 1533.47 nm, 1534.25 nm, 1535.04 nm, 1535.82 nm, 1536.61 nm, 1537.40 nm, 1538.19 nm, 1538.98 nm, 1539.77 nm, 1540.56 nm, 1541.35 nm, 1542.14 nm, 1542.94 nm, 1543.73 nm, 1544.53 nm, 1545.32 nm, 1546.12 nm, 1546.92 nm, 1547.72 nm, 1548.51 nm, 1549.32 nm, 1550.12 nm, 1550.92 nm, 1551.72 nm, 1552.52 nm, 1553.33 nm, 1554.13 nm, 1554.94 nm, 1555.75 nm, 1556.55 nm, 1557.36 nm, 1558.17 nm, 1558.98 nm, 1559.79 nm, 1560.61 nm, 1561.42 nm.
•
1529.94 nm, 1530.73 nm, 1531.51 nm, 1532.29 nm, 1533.07 nm, 1533.86 nm, 1534.64 nm, 1535.43 nm, 1536.22 nm, 1537.00 nm, 1537.79 nm, 1538.58 nm, 1539.37 nm, 1540.16 nm, 1540.95 nm, 1541.75 nm, 1542.54 nm, 1543.33 nm, 1544.13 nm, 1544.92 nm, 1545.72 nm, 1546.52 nm, 1547.32 nm, 1548.12 nm, 1548.92 nm, 1549.71 nm, 1550.52 nm, 1551.32 nm, 1552.12 nm, 1552.93 nm, 1553.73 nm, 1554.54 nm, 1555.34 nm, 1556.15 nm, 1556.96 nm, 1557.77 nm, 1558.58 nm, 1559.39 nm, 1560.20 nm, 1561.01 nm, 1561.83 nm.
•
1570.83 nm, 1571.65 nm, 1572.48 nm, 1573.30 nm, 1574.13 nm, 1574.95 nm, 1575.78 nm, 1576.61 nm, 1577.44 nm, 1578.27 nm, 1579.10 nm, 1579.93 nm, 1580.77 nm, 1581.60 nm, 1582.44 nm, 1583.27 nm, 1584.11 nm, 1584.95 nm, 1585.78 nm, 1586.62 nm, 1587.46 nm, 1588.30 nm, 1589.15 nm, 1589.99 nm, 1590.83 nm, 1591.68 nm, 1592.52 nm, 1593.37 nm, 1594.22 nm, 1595.06 nm, 1595.91 nm, 1596.76 nm, 1597.62 nm, 1598.47 nm, 1599.32 nm, 1600.17 nm, 1601.03 nm, 1601.88 nm, 1602.74 nm, 1603.60 nm.
•
1571.24 nm, 1572.06 nm, 1572.89 nm, 1573.71 nm, 1574.54 nm, 1575.37 nm, 1576.20 nm, 1577.03 nm, 1577.86 nm, 1578.69 nm, 1579.52 nm, 1580.35 nm, 1581.18 nm, 1582.02 nm, 1582.85 nm, 1583.69 nm, 1584.53 nm, 1585.36 nm, 1586.20 nm, 1587.04 nm, 1587.88 nm, 1588.73 nm, 1589.57 nm, 1590.41 nm, 1591.26 nm, 1592.10 nm, 1592.95 nm, 1593.79 nm, 1594.64 nm, 1595.49 nm, 1596.34 nm, 1597.19 nm, 1598.04 nm, 1598.89 nm, 1599.75 nm, 1600.60 nm, 1601.46 nm, 1602.31 nm, 1603.17 nm, 1604.03 nm.
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 FTP name is a free-format string. However, CTM GateWay/CORBA follows the convention for PTP and CTP, if applicable.
All Ethernet termination points (TPs) for circuit provisioning on E-series, G-series, ML-series, CE-100T-8, and FCMR cards are modeled as FTPs. The convention for the FTP values for Ethernet TPs is as follows:
•
•
•
•
•
•
•
•
•
2.2.5.6 Equipment
For a list of equipment that CTM GateWay/CORBA reports for each NE type, see Appendix D, "Equipment List for NEs."
2.2.5.7 Equipment Holder
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 translates 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 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 a piece of 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, a PIM present in slot 3 is named /rack=1/shelf=1/slot=3/sub_slot=1. A PPM present in PIM 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 apply only to ONS 15454 SONET and SDH NEs when AIE or AEP cards are installed.
For the MGX 8880/8850/8830, there is a new equipment holder called peripheral_holder. Because the TMF determines whether or not a piece of 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 in 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 Topological Link
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 topological link name has the following format, where the port number is optional:
<ME NameA:InterfaceType/slot number/subslot number [/port number]-ME NameB:InterfaceType/slot number/subslot number[/port number ]>
For example:
•
•
CTM reports two topological links for a Y-cable link. Both topological links have the same nativeEMSName, but different values in the second tuple of the topological link name. The names "<nativeEMSName>:::1" and "<nativeEMSName>:::2" identify the two legs of the Y-cable link.
2.2.5.9 Protection Group
The protection group name reported by the NE is used as the PGP native name for 1_FOR_1, 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. "<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
An 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 ML VLANs.
2.2.5.11 ML VLAN
Each ML VLAN is associated with an L2 topology and is unique for a given L2 topology. The fully qualified ML VLAN 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 ML VLAN (which is the VLAN ID). A maximum of 255 ML VLANs can be created per L2 topology, ranging from 1 to 4095.
2.2.5.12 QoS Template
The QoS template is defined in the scope of an EMS domain. The fully qualified QoS template name is identified by two tuples. The first tuple represents the EMS name and the second tuple represents the QoS template 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.
By default, CTM cleans up all 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.5 and jacORB 2.1.3.7 on Sun Solaris 10 and is compliant with the CORBA 2.3 specification. The OSS can use Java or the C++ IDL compiler to compile IDL files.
Note
The thread_pool_max property indicates the maximum number of concurrent threads that CTM can handle. By default, the thread_pool_max property is set to 200 in the /<CTM_installation_directory>/bin/jcorbagw.sh file. If the value is exceeded, the following exception is returned:
org.omg.CORBA.TRANSIENT: Server-side Exception: resource limit reached2.2.6.4 Exception Handling
All interfaces that CTM GateWay/CORBA implements 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 naming attribute 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 that the NMS supplied an object name as a parameter and the EMS cannot find an object with that name. 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 the server cannot respond to the request.
2.2.6.4.6 EXCPT_NE_COMM_LOSS
This exception is used as a generic value when the 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 perform 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 large volumes of data. 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. The OSS uses this exception to issue the upgrade request with a LOOSE MERGE operation type.
2.2.7 Provisioning Subnetwork Connections
SNC provisioning must be within a multilayer subnetwork scope, which means the aEnd and the zEnd of an SNC must be in the same multilayer subnetwork.
CTM defines the method multiLayerSubnetwork::MultiLayerSubnetworkMgr_I:: createAndActivateSNCFromUserLabel for SNC provisioning.
2.2.7.1 SNC Provisioning on OC-n or Electrical Equipment
CTM supports SNC provisioning on OC-n or electrical cards for ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, and ONS 15600 SONET NEs.
CTPs are used as the endpoints to create the SNC.
2.2.7.2 SNC Provisioning on Ethernet Equipment
ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH managed elements support Ethernet equipment. SNCs 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.
Provisioning SNCs on E-series, G-series, and ML-series equipment supported by the ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH is different from creating SNCs on SONET or PDH equipment. For SNCs on Ethernet equipment, CTM uses FTP to model the endpoint. See Floating Termination Point for naming conventions.
The three modes supported for SNC provisioning on Ethernet equipment are:
•
•
•
To obtain 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. A single-card EtherSwitch group can exist only if a node has at least one Ethernet card.
•
•
The following table shows the maximum bandwidth allowed for single- 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 OC-n 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:
•
•
CTM supports the following layer rate for CE-100T-8 and ML-100T-8 cards:
•
2.2.7.2.4 SNC Provisioning for ONS 15454 CE-MR-10 Cards
The ONS 15454 CE-MR-10 card implements two different working modes:
•
•
Automatic mode is similar to the provisioning of existing ML-series cards, where FTPs must be used for CCAT and VCAT circuit provisioning, and the FTP name is the number of the virtual back-end port.
Manual mode requires PTPs/CTPs to be specified for the aEnd and zEnd on CCAT circuits, and for aEnd(s) and zEnd(s) on VCAT member circuits. For VCAT circuit endpoints, FTPs must be used.
Use one of the following APIs to retrieve available CTPs:
Use the API getAllSrc<PTP/CTP/FTP>ForCircuitProvisioning to retrieve the possible endpoints, taking into account the current card mode.
Note
To determine whether a CE-MR-10 card is configured for Manual or Automatic mode, use the getEquipment API, which returns the CardMode parameter.
The following layer rates are supported for CCAT circuits:
•
•
•
•
•
•
•
The following layer rates are supported for VCAT member circuits:
•
•
•
2.2.7.3 Tunnel SNC Provisioning
CTM supports tunnel SNC provisioning on ONS 15310, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH NEs. The tunnel SNC 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 VC tunnel, and the layer rate must be 15 (LR_STS3c_and_AU4_VC4). See Naming Conventions for naming conventions.
Only one aEnd and zEnd are specified for the VT/VC tunnel SNC provisioning.
CTM supports only fully automatically routed VT/VC tunnel SNCs. CTM does not support manually routed and constraint-based automatically routed VT/VC tunnel SNCs.
CTM supports VC tunnel for VC3 port grouping and SNC provisioning on ONS 15454 SDH. For VC tunnel for VC3 port grouping and SNC provisioning, if the source or destination end is an STM-n card, it is modeled as CTP; if the source or destination end is on an E3, DS3I, or DS3IN card, it is modeled as FTP.
The following table shows the combinations of cards that can be selected for creating the VC4 tunnel for VC3 port grouping circuits.
Table 2-28 Tunnel SNC Provisioning
DS3I or DS3IN
DS3I, DS3IN, or STM-n
E3
E3 or STM-n
STM-n
DS3I, DS3IN, or E3
When VC tunnel for VC3 port grouping and 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 OCHCC circuit provisioning on transponders, muxponders, and ITU-T line cards for ONS 15454 SONET and ONS 15454 SDH NEs.
The OCHCC SNC is created between client ports on transponder or muxponder cards, or on trunk ports on ITU-T line cards.
OCHCC is an extension of OCHNC. OCHCC is a part of the OCHCC SNC. OCHCC can have only one source and one destination.
CTP naming is identical to OCHNC SNCs: CTM GateWay/CORBA determines whether to create an OCHNC or OCHCC, depending on the layer. See Connection Termination Point for the CTP details.
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 created only on protected transponder or muxponder cards where there is a protected trunk port.
Note
OSPF-detected links between GCC terminations on transponder or muxponder cards are indicated at the Optical_Transport_OTUk layer.When an OCHCC circuit is created, unless transponder cards are directly connected by a trunk-to-trunk patchcord link, an additional OCH trail tunnel circuit is created automatically.
The following method is defined for protected OCHCC circuits when it is necessary to specify constraints for both working and protected routes: multiLayerSubnetwork::MultiLayerSubnetworkMgr_I:: createAndActivateProtectedOchccFromUserLabel
2.2.7.4.2 OCHNC Circuit Provisioning
CTM supports OCHNC circuit provisioning on the following WDM cards for ONS 15454 SONET and ONS 15454 SDH NEs:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
This type of circuit is referred to 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. WDM SNCs are unidirectional or bidirectional. CTM GateWay/CORBA supports the creation of bidirectional OCHNC circuits on R5.0 and later NEs. You can also create two unidirectional OCHNC circuits on the same frequency, in opposite directions.
The CTPs used in WDM SNCs 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." You can specify four possible directions:
•
•
•
•
The preceding values are added to the globaldefs::ConnectionDirection_T structure.
For OCHNC on ONS 15454 SONET and ONS 15454 SDH R7.0 and later, you do not have to specify the east-to-west or west-to-east direction; instead, UniDir and BiDir must be used. For R8.0 NEs you can specify route constraints (NE include/exclude constraints) in the SNCCreateData_T parameter.
When creating OCHNC bidirectional circuits on R5.x or R6.x NEs, you must specify all four circuit endpoints: source, destination, secondary source (the source in the opposite direction), and secondary destination (the destination in the opposite direction). For R7.x or R8.x NEs you must specify only the source and destination in one direction, because the endpoints for the opposite direction are calculated automatically.
In CTM R9.0, the ONS 15454 SONET and ONS 15454 SDH OCHNC circuits support protected optical paths, which allows you to specify the following property within the creation data structure: staticProtectionLevel=StaticProtectionLevel_T.FULLY_PROTECTED.
The availability of protected paths and the possibility of provisioning protected OCHNC circuits depend on the presence of the Protection Switch Module (PSM). When configured correctly, the PSM provides one of the available protection schemas.
CTM GateWay/CORBA distinguishes the mode that the NE version uses.
2.2.7.5 Specifying Route Constraints for OCHxx Circuit Provisioning
For OCHCC, OCHNC, and OCH trail tunnel circuits, you can specify route constraints (NE include/exclude constraints) in the SNCCreateData_T parameter.
For protected OCHCC circuits, constraints for the working path are specified in the SNCCreateData_T parameter; constraints for the protected path are specified in a separate parameter. See details in the createAndActivateProtectedOchccFromUserLabel API description.
2.2.7.6 Low-Order Circuit Provisioning Using VAP/LAP
CTM supports low-order circuit provisioning using VAP circuits on ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, and ONS 15454 SONET NEs, and low-order aggregation point (LAP) circuits on ONS 15454 SDH NEs. The VAP/LAP circuits must be bidirectional.
When provisioning VAP/LAP circuits, the source is treated as the STS grooming end; the destination is treated as the VT grooming end and is used later to connect VT circuits.
The source is a CTP and the destination is an FTP. See Naming Conventions for naming conventions.
