Cisco Cisco Prime Optical 10.3 Developer's Guide
Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide
43
A standard deprecation period of one Prime Optical release is allowed on the obsolete APIs and
data structure. However, Cisco is willing to consider exceptions that minimize the business
impact to customers.
data structure. However, Cisco is willing to consider exceptions that minimize the business
impact to customers.
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 Prime Optical client:
• In the Domain Explorer window, choose File > Add Network Element(s). Choose <SELF>
cases. There are two ways to create a new subnetwork through the Prime Optical 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. Prime Optical creates a new
subnetwork and assigns a name to the new subnetwork object. The naming convention is
Subnetwork-ID, where ID = 00000001, 00000002, n.
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 Prime Optical 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.
Add New Subnetwork. Enter the subnetwork name.
There are four ways to add NEs to subnetworks:
• Use the Prime Optical client to specify a subnetwork for the new NE. If the new NE is a
• Use the Prime Optical 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.
as described in the first bullet above.
• If the new NE is not a GNE, choose an existing subnetwork as the subnetwork ID. Prime
Optical adds this NE to the subnetwork.
• If the new NE is connected to an existing NE on the network, Prime Optical discovers the NE
and automatically adds it to the existing NE’s subnetwork. No user action is required.
• Use the Prime Optical 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.
Prime Optical 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
Prime Optical merges the two subnetworks, the result is reflected in GateWay/CORBA. The two
subnetworks are merged automatically when the Automatically Group NEs in Subnetworks
feature is enabled in Prime Optical.
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.
Prime Optical 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
Prime Optical merges the two subnetworks, the result is reflected in GateWay/CORBA. The two
subnetworks are merged automatically when the Automatically Group NEs in Subnetworks
feature is enabled in Prime Optical.
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 NCS2K SDH, ONS NCS2K SONET,
ONS 15600 SONET, and ONS 15600 SDH NEs. Prime Optical does not support SNC in
pending state. However, Prime Optical SNC has a proprietary deleting state.
ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS NCS2K SDH, ONS NCS2K SONET,
ONS 15600 SONET, and ONS 15600 SDH NEs. Prime Optical does not support SNC in
pending state. However, Prime Optical SNC has a proprietary deleting state.
2.2.4.3 AVC Events
In certain situations, Prime Optical cannot provide the list of changed object attributes. In this
case, Prime Optical generates an AVC event with an empty attribute list. The NMS makes a get
call to retrieve the object details.
case, Prime Optical generates an AVC event with an empty attribute list. The NMS makes a get
call to retrieve the object details.