User guide

2-21

Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual

OL-20937-01

Chapter 2 NE- and CTM-Specific Details

2.1.12 ONS 15600 SDH

See the Release Notes for Cisco Transport Manager Release 9.2 for the ONS 15600 SDH software

releases that CTM R9.2 supports.

2.1.12.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.12.2 Topological Links

Topological links are unidirectional or bidirectional for ONS 15600 SDH NEs.

2.1.12.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.12.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.12.5 SNCs

One ONS 15600 SDH NE supports a maximum of 1536 VC4 SNCs.

2.1.12.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.12.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.