User guide

2-29
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 2 NE- and CTM-Specific Details
2.2.4 Object Details
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:
• In the Domain Explorer window, choose File > Add Network Element(s). Choose <SELF> as the
GNE ID and <System Default> as the subnetwork ID. CTM creates a new subnetwork and assigns
a name to the new subnetwork object. The naming convention is Subnetwork-ID, where
ID = 00000001, 00000002, n.
• Create a subnetwork object from the CTM client by choosing File > Subnetwork Explorer. In the
Subnetwork Explorer window, select a network partition and choose File > Add New Subnetwork.
Enter the subnetwork name.
There are four ways to add NEs to subnetworks:
• Use the CTM client to specify a subnetwork for the new NE. If the new NE is a GNE and you choose
<System Default> as the subnetwork ID, the new subnetwork is created as described in the first
bullet above.
• If the new NE is not a GNE, choose an existing subnetwork as the subnetwork ID. CTM adds this
NE to the subnetwork.
• If the new NE is connected to an existing NE on the network, CTM discovers the NE and
automatically adds it to the existing NE’s subnetwork. No user action is required.
• Use the CTM client to move the NE from one subnetwork to another subnetwork.
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.