Cisco Prime Optical User Guide, 10.7

Adding Groups

Step 1 Select a node or group in the Domain Explorer tree.

Note You cannot add a new group to the Discovered Network Elements or Deleted Network Elements groups.

Step 2 Choose File > New Group (or click the Add a New Group tool). The New Group dialog box opens.

Step 3 Enter the following information in the New Group dialog box.

Step 4 Click OK . The new group appears in the Domain Explorer tree.

Copying Groups

You can easily create domains for multiple users in Prime Optical. Just copy the same groups in different domains, so that users who work different shifts can use the same group.

Step 1 In the Domain Explorer tree, select the group to be copied.

Step 2 Choose Edit > Copy (or click the Copy tool).

Step 3 Select the group where the group will be pasted and choose Edit > Paste (or click the Paste tool). This pastes the group under the selected group.

Note You cannot paste a group into the Discovered Network Elements or Deleted Network Elements groups.

Tip The drag-and-drop feature can also be used to copy groups. Use the mouse to drag and drop the group to a new location.

Since they cannot see the entire domain, users with the Assign NEs property (Provisioner, Operator, and some custom user profiles) are not allowed to modify the topology using copy, cut, paste, or drag and drop. See Managing Security for information about the Assign NEs property.

Moving Groups

Prime Optical provides drag-and-drop capabilities to easily move groups in the Domain Explorer tree.

Step 1 In the Domain Explorer tree, select the group to be moved.

Step 2 Use the mouse to drag and drop the selected group to a new location.

Note You cannot move groups into the Discovered Network Elements or Deleted Network Elements groups.

Deleting Groups

Prime Optical allows you to delete a single group or multiple groups.

Deleting a Single Group

Step 1 In the Domain Explorer tree, select the group to be deleted.

Step 2 You can delete either the selected instance of the group or all instances of the group:

• To remove the selected instance of the group, choose Edit > Delete ; then, click Yes in the confirmation dialog box.
• To remove all instances of the selected group, choose Edit > Delete All ; then, click Yes in the confirmation dialog box.

Note Before deleting the last instance of a group, the group must be empty. Move all of the NEs and groups that the group contains to a different group.

Deleting Multiple Groups

Step 1 In the Domain Explorer tree, select the group to be deleted. Select multiple groups by pressing the Ctrl key, and then click each group that will be deleted.

Step 2 You can delete either the selected instance of the groups or all instances of the groups:

• To remove the selected instance of the groups, choose Edit > Delete ; then, click Yes in the confirmation dialog box.
• To remove all instances of the selected groups, choose Edit > Delete All ; then, click Yes in the confirmation dialog box.

Note Before deleting the last instance of a group, the group must be empty. Move all of the NEs and groups that the group contains to a different group.

Adding Network Partitions

Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer .

Step 2 In the Subnetwork Explorer window, choose File > Add New Network Partition (or click the Add a New Network Partition tool). The Add New Network Partition dialog box opens.

Step 3 Enter the following information.

Step 4 Click OK . The new network partition appears in the Subnetwork Explorer tree.

Modifying Network Partitions

Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer . The Subnetwork Explorer opens.

Step 2 In the Subnetwork Explorer tree, select a network partition to modify.

Step 3 In the Network Partition Properties pane, click the Identification tab.

Step 4 Modify the following information as needed.

Step 5 Click Save .

Step 6 In the confirmation dialog box, click Yes . The modifications are visible in the Subnetwork Explorer tree and Network Partition Properties pane.

Deleting Network Partitions

Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer . The Subnetwork Explorer opens.

Step 2 In the Subnetwork Explorer tree, select the network partition that you want to delete; then, choose Edit > Delete .

Note A network partition cannot be deleted if it is associated with any subnetwork in the domain, or if it is the last network partition in the domain. When the network partition is deleted, any running instances of the NE Service that were associated with the partition stop running.

Step 3 In the confirmation dialog box, click Yes . The network partition is removed from the Subnetwork Explorer tree.

Adding Subnetworks

Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer .

Note To open the Subnetwork Explorer, the domain must contain at least one NE. If the domain does not contain any NEs, the Subnetwork Explorer menu option is unavailable.

Step 2 In the Subnetwork Explorer tree, select the network partition where you will add the subnetwork and choose File > Add New Subnetwork (or click the Add a New Subnetwork tool). The Add New Subnetwork dialog box opens.

Step 3 Enter the following information in the Add New Subnetwork dialog box.

Step 4 Click OK . The new subnetwork appears in the Subnetwork Explorer tree.

Note The Add New Subnetwork feature is not available for users with the Assign NEs property (Provisioner, Operator, and custom user profiles) because they cannot see the entire domain.

Moving Subnetworks

A subnetwork can be moved from one network partition to another if there are no routable links among the NEs that belong to that subnetwork and if automatic subnetwork grouping is disabled. (For information about automatic subnetwork grouping, see Automatically Grouping NEs in Subnetworks.)

Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer .

Step 2 In the Subnetwork Explorer tree, select the subnetwork to be moved.

Step 3 Use the mouse to drag and drop the selected subnetwork to a new network partition.

Deleting Subnetworks

Step 1 In the Domain Explorer window, choose File > Subnetwork Explorer .

Step 2 In the Subnetwork Explorer tree, click the subnetwork that will be deleted.

Note Only an empty subnetwork can be deleted. An empty subnetwork is one that does not contain any NEs or deleted NEs. Trying to delete a subnetwork that contains deleted NEs will generate the error message: “Selected subnetwork has some deleted NEs. Prune those NEs to delete the subnetwork.” Before deleting the subnetwork, remove the deleted NEs from the Prime Optical database. For more information, see Removing a Deleted NE.

Step 3 Choose Edit > Delete .

Step 4 In the confirmation dialog box, click Yes to remove the subnetwork from the tree.

Prerequisites for Adding NEs

Before adding a new NE, enable the NE service for that NE. (You can, however, add the NE even if the NE service is disabled.) The NE service is enabled by default, but the service is not started as a process unless you activate an NE for that particular service. You must also meet certain other specific prerequisites depending on the type of NE you are adding.

Note There are no prerequisites for adding ONS 15327, ONS 15600 SONET, or ONS 15600 SDH NEs.

Prerequisites for Adding ONS 15216 EDFA2 and EDFA3 NEs

Before adding ONS 15216 EDFA2 and EDFA3 NEs to Prime Optical, you must do the following:

• Configure the Prime Optical SNMP community string with read-write access on the ONS 15216 EDFA2 or EDFA3. Refer to the NE documentation for more information.
• Ensure that the Prime Optical SNMP community string value and the CommTrapEntry community string value on the ONS 15216 EDFA2 or EDFA3 match. To ensure that these values match, enter the value from the CommTrapEntry in the ONS 15216 EDFA2 or EDFA3 into the SNMP Community String field in the Domain Explorer .
• (For the ONS 15216 EDFA3 only) Start the FTP service. To verify that the FTP service has started, enter the ftp 0 command and enter the username and password specified during installation.
• (For the ONS 15216 EDFA2 only) Configure the TFTP service on the Prime Optical server to publish the TFTP directory and start the TFTP service. The directory to be published as a TFTP directory should have read-write access.

To configure the default tftpboot directory:

Step 1 Start the TFTP service on the Prime Optical server by uncommenting the TFTP service entry from the /etc/inetd.conf file, and update the name of the directory to be published as a TFTP directory. For example:

Step 2 Stop and restart the inetd process.

The name of the ONS 15216 EDFA3 NE must be unique and cannot be a null value. To set the name of the ONS 15216 EDFA3 NE:

Step 1 Log in to TL1 for that particular NE. For example, enter:

Step 2 Enter the username and password. For example, enter:

Step 3 Enter the following command to set the new name on the ONS 15216 EDFA3 NE:

Step 4 Enter the following command to verify that the name is correct:

Step 5 Enter the following command to log out:

Note For passive ONS 15216 NEs, there is no communication between Prime Optical and the NE itself, and all the information is user-defined. For example, you can add inventory information in the Domain Explorer and add specific information (such as a serial number) in the NE Explorer. For passive ONS 15216 NEs with multiple slots, you can use the NE Explorer to specify the content of each slot. The information you define is maintained in the database and propagated to an external OSS by using Prime Optical GateWay/CORBA.

Prerequisites for Adding ONS 15305 NEs

Before adding ONS 15305 NEs to Prime Optical, be sure that a valid SNMP community string is set up on the ONS 15305 to allow performance monitoring and fault management data collection from the NE.

Note To enable you to add an ONS 15305 NE to Prime Optical, its SNMP Users table must contain the row 0.0.0.0 public true, where public is the community string. In addition, to obtain trap events from the NE, the Prime Optical server IP address must be added to the NE. See the Cisco Edge Craft user documentation for more information.

Important Note About Upgrading from ONS 15305 R2.0.2, R2.0.3, or R2.0.4 to ONS 15305 R3.0

When upgrading from ONS 15305 R2.0.2, R2.0.3, or R2.04 to ONS 15305 R3.0, note the following constraints:

• After you upgrade the NE to ONS 15305 R3.0, you must delete the R2.0 NE (with NE model “ONS 15305”) from Prime Optical and add it again with the correct NE model attribute (“ONS 15305 CTC”).
• All PM data that was collected before the upgrade will be lost.

These constraints exist because the NE service that manages the ONS 15305 R2.0.2, R2.0.3, and R2.0.4 is different from the NE service that manages the ONS 15305 R3.0.

Prerequisites for Adding ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15454 SONET, and ONS 15454 SDH NEs

Before adding ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15454 SONET, and ONS 15454 SDH NEs with ML-series cards to Prime Optical, be sure the NEs are set up as follows:

• Because Prime Optical does not support duplicate IP addresses, be sure that your ONS network does not contain duplicate IP addresses before adding ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15454 SONET, and ONS 15454 SDH NEs.
• A valid SNMP community string must be given when adding an NE with ML-series cards to resynchronize Syslog and Configuration events. Audit Log messages will be added in case of a resynchronization failure.

Note For SNMPv3 node configuration, see Managing SNMPv3—CTC-Based Release 9.6 NEs.

• A trap destination with IP address equal to the Prime Optical server IP address, UDP port 162, SNMP version as SNMPv2c, maximum traps per second set to 0, and SNMP community string must be created and must allow SNMP sets to receive traps from ML-series cards.
• The Cisco IOS startup-config file must have the snmp-server enable traps command to receive traps from ML-series cards.
• Whenever the user changes the trap destination for NE IP address and port=162/391 in either CTC or Prime Optical, NEs must be out of service to resynchronize the ML-series card events and be registered for traps. Change the operational state of the NE to In Service after making the changes.
• CTC SuperUser credentials (NE username and password) are required to exploit full Prime Optical functionalities.
• If your network contains ML cards, SNMPv1/SNMPv2c uses the following configurations on GNEs and ENEs for traps:

– GNE trap destination: Prime Optical server IP address

– GNE trap port: 162

– GNE community string: public

– GNE version: v1 or v2c

– ENE trap destination: GNE IP address

– ENE trap port: 391

– ENE community string: Same as on GNE

– ENE version: v1 or v2c

Note Keep the SNMP version consistent across all the GNEs/ENEs in the ring.

Adding a DWDM Node to an Existing Multi-Service Transport Platform (MSTP) Network

Step 1 Mark the two NEs of the DWDM span (where you want to insert the new node) as Out of Service.

Step 2 Delete all invalid DWDM links between the two NEs from Prime Optical.

Step 3 Complete the steps in the NTP-G129 Add a DWDM Node section, described in the Cisco ONS 15454 DWDM Procedure Guide .

Step 4 Mark the two NEs as In Service. The newly added NE will be automatically discovered when the new links are running.

Prerequisites for Adding CPT 200 and CPT 600 NEs

If a CPT 200 or CPT 600 NE is connected to an ONS 15454 NE, the CPT NE model must match the ONS 15454 NE model. For example, if the ONS 15454 NE is added as a SONET NE, the CPT 200 or CPT 600 NE must be added as a SONET NE.

If the CPT 200 or CPT 600 NE is a standalone NE, the NE model is irrelevant.

Adding NEs

From the Domain Explorer or Subnetwork Explorer tree, you can use the Add New NE wizard to add a single NE or multiple NEs.

Note Prime Optical does not support duplicate IP addresses. Before adding NEs, be sure that your network does not contain duplicate IP addresses.

Adding a Single NE

Step 1 Select a node in the Domain Explorer or Subnetwork Explorer tree; choose File > Add Network Element(s) (or click the Add Network Element(s) tool).

The Add New NE wizard opens. Table 3-5 provides descriptions for the Add New NE Wizard.

Note You cannot add a new NE to Discovered Network Elements or Deleted Network Elements groups.

Step 2 Enter the following information:

• NE model
• NE type

Step 3 Click one of the following radio buttons in the NE Addition area:

• Single NE Addition —To add only one NE.
• Single NE Addition (Use TL1 Tunnel) —To add only one tunnel NE (TNE). Prime Optical can connect to a TNE that belongs to an OSI network behind a non-Cisco GNE.

Step 4 Complete the following substeps if you are adding a single NE:

a. Click one of the following radio buttons in the IP Address area:

– IP

– Hostname

b. Enter the IP address or hostname; then, click Add .

Note You can enter an IP address in IPv4 or IPv6 format.

To enable you to add an NE using its hostname, the hostname must be resolved inside the Domain Name Service (DNS).

Step 5 Complete the following substeps if you are adding a single TNE:

a. Enter the gateway NE.

b. Click one of the following radio buttons:

– Use Default TL1 Port

– Use Other TL1 Port—If selected, enter the TL1 port number.

c. Choose a TL1 encoding mode from the drop-down list.

d. Check the GNE Login Required check box if GNE login is required.

e. Enter the GNE TID (available if the GNE Login Required check box is checked).

Step 6 Click Next .

Note If you click Finish in this window, Cisco default values are assigned to the remaining fields. In addition, the NE is placed in a preprovisioned state, and discovery does not start automatically. If you want to add the NE in a nonpreprovisioned state, click Next and proceed to the next window; then, in the Operational State field, select a state other than Preprovisioned.

Step 7 Enter the following information. Fields shown depend on the NE type.

a. NE ID

Note • Do not use “Prime Optical” as an NE ID, because the Alarm Browser might contain Prime Optical alarms with the source ID “Prime Optical.” It will be difficult to distinguish between NE alarms and Prime Optical alarms, if they both have the same source ID. For the same reason, do not cause Prime Optical to automatically populate an NE whose NE ID is “Prime Optical.”

• If you are using Prime Optical with Prime Central, do not use “None” or “All” as the NE ID, because those names have internal meaning to Prime Central.
• If the NE ID field is left blank, it will default to the IP address. After communication is established, Prime Optical discovers the NE ID from the NE.

b. Alias

c. Operational state

d. Description

e. Location name

f. Subnetwork ID

Note This field is dimmed when the Automatically Group NEs in Subnetworks check box is checked in the UI Properties pane of the Control Panel.

g. Network partition ID.

Step 8 Click the icon to view the parameters.

Step 9 Click OK to change the discovery mode of the network partition.

Note You can also create new network partitions by clicking the ellipsis (...) icon. Specify a name and description for the new network partition.

Step 10 To view the threshold of the new network partition, the number of NEs (which will be 0), and the option to change the discovery mode, choose either Manual or Automatic (the default) from the drop-down list.

If you choose Automatic, Prime Optical automatically discovers all NEs and adds them to the network partition. If you choose Manual, the NE is added and remains in the Undiscovered Network Elements folder ( Administration > Control Panel ).

Note If you have no NEs in a network partition but are still unable to change the discovery mode, check if the Allow Provisioning (Administration > Control Panel > UI Properties) check box is unchecked. Also, verify the value in the Discovery Mode drop-down list.

Step 11 Click Next if you are adding an ONS 15305, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, or ONS 15600 SONET NE.

Note If you click Finish in this window, Cisco default values will be assigned to the remaining fields.

Step 12 Click Finish if you are adding an ONS 15216, ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15600 SDH, or Not Managed/Other Vendor NE.

Step 13 Select the grouping option for the NE.

Step 14 Click Finish to add the new NE to the domain.

Wait 2 to 5 minutes while the Prime Optical server completes the node discovery. (Not applicable if the operational state is Preprovisioned.)

Step 15 Check to see if the communication state is correct. If Prime Optical cannot connect to the NE, the NE displays an unavailable communication state icon in the tree.

Step 16 Verify that the NE software version is listed in the Supported NE table ( Domain Explorer > Administration > Supported NE table). If it is not listed, see Adding a New NE Software Version to the Prime Optical Domain.

Adding Multiple NEs

Step 1 Select a node in the Domain Explorer or Subnetwork Explorer tree; then, choose File > Add Network Element(s) (or click the Add Network Element(s) tool). The Add New NE wizard opens. Table 3-5 provides descriptions.

Note You cannot add a new NE to the Discovered Network Elements or Deleted Network Elements group.

Step 2 Enter the following information:

• NE model.
• NE type.
• NE addition—Click the Bulk NE Addition radio button.

Note Bulk NE addition does not apply to passive ONS 15216 NEs or Not Managed/Other Vendor NEs.

• IP address range—Enter the IP addresses in the From and To fields; then, click Add .

Note The IP addresses must be from the same subnetwork.

You can enter IP addresses in IPv4 or IPv6 format. You can only enter IPv6 addresses if all of the selected NE models support IPv6. Prime Optical provides IPv6 support for the following NE releases: ONS 15310 MA SDH R9.3, ONS 15310 MA SONET R9.3, ONS 15454 SDH R9.3, and ONS 15454 SONET R9.3.

• IP address selection—Add or remove IP addresses using the Add or Remove button.

Step 3 Click Next .

Note If you click Finish in this window, Cisco default values are assigned to the remaining fields.

Step 4 Enter the following information. Fields shown depend on the NE type.

a. NE ID— Display only.

b. Alias— Display only .

c. Operational state.

d. Description.

e. Location name.

f. Subnetwork ID.

Note This field is dimmed when the Automatically Group NEs in Subnetworks check box is checked in the UI Properties pane of the Control Panel.

g. Network partition ID.

Step 5 Click the icon to view the parameters.

Step 6 Click OK to change the discovery mode of the network partition.

Note You can also create new network partitions by clicking the ellipsis (...) icon. Specify a name and description for the new network partition.

Step 7 To view the threshold of the new network partition, the number of NEs (which will be 0), and the option to change the discovery mode, choose either Manual or Automatic (the default) from the drop-down list.

If you choose Automatic , Prime Optical automatically discovers all NEs and adds them to the network partition. If you choose Manual , the NE is added and remains in the Undiscovered Network Elements folder ( Administration > Control Panel ).

Note If you have no NEs in a network partition but are still unable to change the discovery mode, check if the Allow Provisioning (Administration > Control Panel > UI Properties) check box is unchecked. Also, verify the value in the Discovery Mode drop-down list.

Step 8 Click Next if you are adding an ONS 15305, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, or ONS 15600 SONET NE.

Note If you click Finish in this window, Cisco default values are assigned to the remaining fields.

Step 9 Click Finish if you are adding an ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, or ONS 15600 SDH NE.

Step 10 Select the grouping option for the NE.

Step 11 Click Finish to add the NEs to the domain.

Wait 2 to 5 minutes while the Prime Optical server completes the node discovery. (Not applicable if the operational state is Preprovisioned.)

Step 12 Check to see if the communication state is correct. If Prime Optical cannot connect to the NE, the NE displays an unavailable communication state icon in the tree.

Step 13 Verify that the NE software version is listed in the Supported NE table ( Domain Explorer > Administration > Supported NE table). If it is not listed, see Adding a New NE Software Version to the Prime Optical Domain.

Table 3-5 Field Descriptions for the Add New NE Wizard

Field	Description
NE Addition Panel
NE Model	Select the NE model (Carrier Packet Transport 200, Carrier Packet Transport 200 SDH, Carrier Packet Transport 600, Carrier Packet Transport 600 SDH, Cisco ONS 15216 [all types], Cisco ONS 15305, Cisco ONS 15305 CTC, Cisco ONS 15310 CL, Cisco ONS 15310 MA SONET, Cisco ONS 15310 MA SDH, Cisco ONS 15327, Cisco ONS 15454 SONET, Cisco ONS 15454 SDH, Cisco ONS 15600 SONET, Cisco ONS 15600 SDH, or Not Managed/Other Vendor).
NE Type	Select the type of NE. Available types depend on the selected NE model.
NE Addition	Click one of the following radio buttons. The available fields change, depending on which option you select: Single NE Addition —To add only one NE. Bulk NE Addition —To add several NEs simultaneously. Single NE Addition (Use TL1 Tunnel) —To add only one TNE.
IP Address	Click one of the following radio buttons: IP—To enter an IP address in IPv4 or IPv6 format. Hostname—To enter a hostname.
IP/Hostname ( for single NE additions )	Enter a unique IP address or hostname for the NE. You can enter an IP address in IPv4 or IPv6 format. The IPv4 address must be in the form ddd.ddd.ddd.ddd , where ddd is a decimal octet expressed as an integer between 0 and 255. The first octet cannot be a zero. The IPv6 address is a 128-bit address (hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh:hhhh) that is divided into 16-bit blocks, where each block is converted to a 4-digit hexadecimal number and separated by a colon (:). An IPv6 address is valid only if the NE model that you selected supports IPv6 addresses. Note Prior to the NE ID discovery, Prime Optical uses the NE IP address as a temporary NE ID. To enable you to add an NE using its hostname, the hostname must be resolved inside the DNS. The IP/Hostname field is unavailable when adding passive NEs and Not Managed/Other Vendor NEs.
From IP Address ( for bulk NE additions )	Enter the beginning IP address for the range of NEs you want to add. Note You can enter an IP address in IPv4 or IPv6 format.
To IP Address ( for bulk NE additions )	(Optional) Enter the ending IP address for the range of NEs you want to add. Click Add to add the range to the Selected IP field.
IP Address Selection ( for bulk NE additions )	Select one or more IP addresses in the Deleted IP field and click Add to add them to the Selected IP field. Select one or more IP addresses in the Selected IP field and click Remove to remove them. Only the IP addresses in the Selected IP field are affected by clicking Next . Note You can add IPv6 addresses only if the selected NE model supports IPv6. Prime Optical provides IPv6 support for the following NE releases: ONS 15310 MA SDH R9.3, ONS 15310 MA SONET R9.3, ONS 15454 SDH R9.3, and ONS 15454 SONET R9.3.
Gateway NE ( for single TNE additions )	If you selected Single NE Addition (Use TL1 Tunnel) in the NE Addition area, the Gateway NE area becomes visible. Fill in the following fields to add a TNE to the Prime Optical domain. The following NE models support TL1 tunnels: ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH. GNE IP Address —IP address of the non-Cisco GNE that supports the TL1 tunnel. This field is mandatory. Use Default TL1 Port —If selected, the default value for the TL1 port is used. Use Other TL1 Port —If selected, specify the TL1 port number in the text field. TL1 Encoding Mode —Specify the TL1 encoding mode: – LV + Base64 Payload: (Default) If selected, and if Use Default TL1 Port is selected, TL1 port 3081 is used. – LV + Binary Payload: If selected, and if Use Default TL1 Port is selected, TL1 port 3081 is used. – Raw: If selected, and if Use Default TL1 Port is selected, TL1 port 3082 is used. GNE Login Required —If checked, a login is required on the non-Cisco GNE. The GNE login uses the following settings: – GNE TID: The value specified in the GNE TID field. – Username and password: The values specified in the Control Panel > Security Properties pane > CTC-Based SDH or CTC-Based SONET tab > Server - GNE Connection (TL1 Tunnel) area.
NE Properties Panel
NE ID	Enter a unique name for the NE in the form of an ASCII text string. Apostrophes (’) and quotation marks (“) are not accepted. The NE ID you enter should be the same as the NE ID that is configured on the NE itself. If it is not the same, this field will be updated with the NE hostname. Note Do not use “Prime Optical” as an NE ID because the Alarm Browser might contain Prime Optical alarms with the source ID “Prime Optical.” It will be difficult to distinguish between NE alarms and Prime Optical alarms if they both have the same source ID. For the same reason, do not cause Prime Optical to automatically populate an NE whose NE ID is “Prime Optical.” Note If the NE ID field is blank, it will default to the IP address. After communication is established, Prime Optical autodiscovers the NE ID from the NE.
Alias	Enter a unique alias name for the NE. The alias name can contain alphanumeric characters. It can also contain characters from international character sets.
Operational State	Specify the operational state of the NE. There are four states: Preprovisioned—The NE has been added to the database for provisioning but is not yet in service. Under Maintenance—The NE is temporarily under maintenance but requires monitoring. In Service—The NE is currently deployed and requires monitoring. Out of Service—The NE has been marked Out of Service and does not require monitoring.
SNMP Community String	Enter the SNMP community string for the NE. The Cisco default is public . Note The SNMP community string applies only to the ONS 15216 EDFA2, ONS 15216 EDFA3, ONS 15305, ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH NEs.
Description	Enter a description of the NE.
Location Name	Enter the NE geographic location.
Subnetwork ID ( not selectable if automatic subnetwork grouping is enabled )	Select the subnetwork ID associated with the NE.
Network Partition ID	Select the network partition associated with the NE. To add a CTC-based NE that was discovered manually, do the following: To view the NE partition details, click the icon next to the NE partition ID . Click OK to change the discovery mode. The discovery mode can be changed only if the network partition is empty. You can also create new network partitions by clicking the ellipsis (...) icon. Specify a name and description for the network partition. Note When you are adding manually discovered NEs to a network partition, only the partitions that are compatible with the selected NE model are listed.
Group Properties Panel
Grouping Option for Discovered NEs	Select one of the following grouping options for the discovered NEs: Group discovered NEs in the Discovered Network Elements group Group NEs with the NE that discovered them (Cisco default) Group NEs by subnet Note If you are adding manually discovered NEs, the first option is preselected, and the other options are dimmed. To move an NE, cut and paste it into the desired group.

Note • For Prime Optical to communicate with certain NE types, you must set the username and password that the Prime Optical server uses to establish a session with the NE. To enter user information, choose Administration > Control Panel > Security Properties tab; then, enter the username and password on the ONS 15216 EDFA2, ONS 15216 EDFA3, ONS 15216 OADM, ONS 15305 CTC, ONS 15327, ONS 15454, ONS 15454 SDH, ONS 15600 SDH, or ONS 15600 tab.

• Regardless of the actual length of the password, the Password and Confirm Password fields display only a fixed-length string of 15 asterisks (*).
• For more information, see Configuring Prime Optical Security Parameters. For NEs that do not use SNMP, you can set the username and password in the NE Authentication tab of the Domain Explorer . For more information, see Setting NE Authentication.
• When adding more than one data communications channel (DCC)-connected, CTC-based NE, add one NE to a subnetwork and allow the other NEs to be automatically discovered and placed in the same subnetwork. When moving NEs from one subnetwork to another, move all DCC-connected NEs to the same subnetwork. Move the entire subnetwork instead of splitting DCC-connected NEs between subnetworks.
• Errors encountered while adding NEs are listed in the Error Log .

Copying an NE from One Group to Another

Groups for multiple users can easily be created in Prime Optical. Just copy the same NE into different groups.

Step 1 In the Domain Explorer tree, select the NE to be copied.

Step 2 Choose Edit > Copy (or click the Copy tool).

Step 3 Select the group or management domain node where the NE will be pasted and choose Edit > Paste (or click the Paste tool). This pastes the NE under the selected node.

Note You cannot paste an NE in the Discovered Network Elements or Deleted Network Elements groups. Also, you cannot paste an NE in a group where the same instance of the NE already exists.

Tip The drag-and-drop feature can also be used to copy NEs. Use the mouse to drag and drop the NE to a new location.

Note Since they cannot see the entire domain, users with the Assign NEs property (Provisioner, Operator, and some custom user profiles) are not allowed to modify the topology using copy, cut, paste, or drag and drop.

Moving an NE from One Group to Another

Prime Optical provides drag-and-drop capabilities to allow you to easily move NEs from one group to another.

Step 1 In the Domain Explorer tree, select the NE to be moved.

Step 2 Choose Edit > Cut , and then choose Edit > Paste . You can also use the mouse to drag and drop the selected NE to a new location.

Note You cannot copy or move NEs into the Discovered Network Elements group.

Note Since they cannot see the entire domain, users with the Assign NEs property (Provisioner, Operator, and some custom user profiles) are not allowed to modify the topology using copy, cut, paste, or drag and drop.

Moving an NE from One Network Partition to Another

Note Do not add SONET and SDH NEs in the same network partition.

Step 1 In the Domain Explorer tree, select File > Subnetwork Explorer . The Subnetwork Explorer opens.

Step 2 Identify the network partition ID:

a. In the Subnetwork Explorer tree, click the new network partition where you will move the NE.

b. In the Network Partition Properties pane, click the Identification tab.

Step 3 Identify the subnetwork(s) assigned to the new network partition.

Note A subnetwork can only be assigned to one network partition.

Step 4 In the Domain Explorer , click the NE to be moved. In the Network Element Properties pane, click the Address tab.

Step 5 Change the subnetwork ID to a subnetwork ID assigned to the new network partition. Choose from the list of subnetwork IDs; then, click OK .

Step 6 Click Save .

Automatically Grouping NEs in Subnetworks

Note An NE can be assigned to only one subnetwork.

Prime Optical allows you to automatically group NEs in a subnetwork. When this feature is enabled, Prime Optical automatically creates the subnetwork, which consists of NEs that are connected by topological links; you cannot change the subnetwork of the NE. This means that:

• When adding a new NE, the option to select the Subnetwork ID is disabled. The Subnetwork ID field displays System Default .
• In the Address tab of the Domain Explorer > Network Element Properties pane, you cannot change the subnetwork ID.
• You cannot drag and drop NEs in the Subnetwork Explorer tree.

Complete the following steps to automatically group NEs in a subnetwork:

Step 1 In the Domain Explorer window, choose Administration > Control Panel and click UI Properties .

Step 2 In the Subnetwork Grouping area, check the Automatically Group NEs in Subnetworks check box.

Step 3 Click Save .

Note If a topological link is deleted while NEs are automatically grouped in subnetworks, Prime Optical deletes isolated NEs, creates a new subnetwork, and moves the deleted NEs to the new subnetwork.

If a topological link is discovered or added manually, it will result in a network that contains disjointed subnetworks. Prime Optical deletes the NEs from the disjointed subnetwork that contains fewer NEs, deletes the disjointed subnetwork, and adds the deleted NEs to the subnetwork where the topological link was added manually.

Deleting NEs

From the Domain Explorer tree, you can delete a single NE, multiple NEs, or out-of-service NEs.

Note • All links from the NE are deleted automatically from the database during the purge phase of NE deletion. The purge process does not start if there are valid links on the NEs scheduled for permanent deletion. You must wait until all links on the NE become invalid and then try again.

• If the NE is linked with OMS, then the NE cannot be deleted. Delete the OMS link from that particular NE and OTS link to delete the NE from the DE.

Deleting a Single NE

Only out-of-service or preprovisioned NEs can be placed in the Deleted Network Elements group.

If a CTC-based NE is deleted and then DCC connectivity to the deleted NE is removed, Prime Optical rediscovers the deleted NE. If DCC connectivity is removed before deleting the NE, Prime Optical does not rediscover the NE. Therefore, remove DCC connectivity to the NE before deleting the NE from Prime Optical.

Step 1 In the Domain Explorer tree, select the NE that will be deleted.

Step 2 In the Status tab of the Network Element Properties pane, set the Operational State field to Out of Service ; then, click Save . Click Yes in the confirmation dialog box.

Note If there is more than one instance of an NE (that is, if the NE was copied so two versions exist), you do not need to move the NE to Out of Service before deleting it.

Step 3 You can delete either a selected instance of the NE or all instances of the NE:

• Deleting the selected instance of the NE—Only the specific NE that you selected in the Domain Explorer tree is deleted. To delete the selected instance of the NE, choose Edit > Delete ; then, click Yes . If this is the last instance of the NE, the NE is placed in the Deleted Network Elements group.

Note A GNE that has associated subtending NEs cannot be deleted. A subtending NE can be disassociated from the GNE by removing the NE from the Prime Optical domain or by assigning it to a different GNE.

• Deleting all instances of the NE—All NEs in the user domain that have the same NE ID are deleted. To delete all instances of the selected NE, choose Edit > Delete All ; then, click Yes in the confirmation dialog box. The NE is placed in the Deleted Network Elements group.

Note Check the Audit Log to confirm that the selected NE has been successfully deleted from the database. The deletion is not complete until the following message is displayed in the Audit Log: AUD-5015 NE ID has been successfully purged. See Viewing the Audit Log for information on how to view the Audit Log.

No client views for an NE can be opened in the Deleted Network Elements group. Also, no properties of a deleted NE can be modified. The deleted NE and its associated data are removed from all client views except the Domain Explorer .

Step 4 To purge the NEs in the Deleted Network Elements group, see Removing a Deleted NE.

Deleting Multiple NEs

Step 1 For each NE that will be deleted:

a. In the Domain Explorer tree, select the NE that will be deleted.

b. In the Status tab of the Network Element Properties pane, set the Operational State field to Out of Service ; then, click Save .

Step 2 In the Domain Explorer tree, select again all the NEs that will be deleted. To select multiple NEs, press and hold down the Ctrl button; then, click each NE that will be deleted.

Step 3 You can delete the selected instance of the NEs or all instances of the NEs:

• Deleting the selected instance of the NE—Only the specific NEs that you selected in the Domain Explorer tree will be deleted. To delete the selected instance of the NEs, choose Edit > Delete ; then, click Yes in the confirmation dialog box. If the selected NEs are the last instance of the NE, the NEs are placed in the Deleted Network Elements group.

Note A GNE that has associated subtending NEs cannot be deleted. A subtending NE can be disassociated from the GNE by removing the NE from the Prime Optical domain or by assigning it to a different GNE.

• Deleting all instances of the NEs—All NEs in the user domain that have the same NE ID as the NE being deleted will be deleted. To delete all instances of the selected NEs, choose Edit > Delete All ; then, click Yes in the confirmation dialog box. The NEs are placed in the Deleted Network Elements group.

Note Both the Delete and Delete All menu options are enabled if at least one of the selected NEs can be deleted. The confirmation dialog box lists the NEs that can and cannot be deleted.

Note Check the Audit Log to confirm that the selected nodes have been successfully deleted from the database. The deletion is not complete until the following message is displayed in the Audit Log: AUD-5015 NE ID has been successfully purged. See Viewing the Audit Log for information on how to view the Audit Log.

Note You can use the mouse to drag and drop the selected NEs to the Deleted Network Elements group only if all the selected NEs can be deleted.

Step 4 To purge the NEs in the Deleted Network Elements group, see Removing a Deleted NE.

Using the prune_ne.sh Script to Remove an Out-of-Service NE from the Database

Note It is recommended that you delete an out-of-service NE from the Prime Optical client (see Deleting a Single NE or Deleting Multiple NEs), because doing so does not involve stopping and starting the Prime Optical server.

Aside from using the Domain Explorer to remove an out-of-service NE from the database, you can also use the prune_ne.sh script.

Note Shut down the Prime Optical server and all Prime Optical clients before running the prune_ne.sh script.

Step 1 In the Domain Explorer tree, select the NE that will be removed.

Step 2 In the Status tab of the Network Element Properties pane, set the Operational State field to Out of Service ; then, click Save .

Step 3 Close the Prime Optical client.

Step 4 Log in to the Prime Optical server as the root user and enter the following command to stop the server:

Step 5 Enter the following command to verify that all Prime Optical processes have stopped:

a. If any processes are still running, enter the following command:

b. Re-enter the following command to verify that the processes have stopped:

Step 6 Change the directory to /opt/CiscoTransportManagerServer/bin and enter the following command:

Step 7 Enter the following command to start the Prime Optical server:

Removing a Deleted NE

Complete the following steps to remove an NE from the client view and delete all records associated with the NE from the database:

Step 1 In the Domain Explorer tree, click the Deleted Network Elements group.

Step 2 Click the NE that will be removed from the Prime Optical domain.

Step 3 Choose Edit > Delete ; then, click Yes .

One of the following happens:

• The NE purge begins for NEs without any valid links.
• If the NEs that are scheduled for permanent deletion contain any valid links, the purge process does not start. You must wait until all links become invalid before trying.

While the purge is in progress, the following icon is displayed in the Domain Explorer tree.

Figure 3-1 Domain Explorer Icon—NE Purge In Progress

If the NE purge fails, the following icon is displayed in the Domain Explorer tree. The Audit Log reports the purge failure. You can repeat the purge and view the progress.

Figure 3-2 Domain Explorer Icon—NE Purge Failed

Step 4 When the NE purge completes successfully, the NE is removed from the Deleted Network Elements group.

The following figure shows the different purge states, where:

• 15454-ansi-65-102—NE has been deleted but not yet purged.
• 15454-ETSI-65-142—Purge is in progress.
• 15454-ETSI-65-140—Purge failed.

Figure 3-3 Sample Purge States: Deleted, In Progress, Failed

Note • Wait until all records associated with the NE are deleted from the database before adding the NE back again.

• The amount of time it takes to prune NEs depends on the amount of data that needs to be removed, the amount of data in the database, the system performance, and so on. The Deleted Network Elements group is visible to users who have the add_delete_NE_group permission. You can purge or undelete an NE that is in the Deleted Network Elements group only if that NE was assigned to you.

Restoring a Deleted NE

Step 1 In the Domain Explorer tree, click the Deleted Network Elements group.

Step 2 Click the NE to restore.

Step 3 Choose Edit > Undelete .

Prime Optical restores the selected NE under the management domain node.

Searching for an NE

Prime Optical allows you to search for a specific NE in the network. See Finding Data in the Domain Explorer.

Overview of Supported Links

Links can be created at different layer rates depending on the card type. See Table 3-6 for the links supported between NEs at compatible layer rates. See Table 3-7 for the supported links per layer rate.

Note Links can be created for a Not Managed/Other Vendor NE only if the NE is in service or under maintenance. Links created for CTC-based NEs are for circuit routing purposes only. Links created for Not Managed/Other Vendor NEs are not used for circuit routing.

Note Physical nonroutable links can be created between NEs that are in the same or a different network partition(s).

Links between TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, TXP_MR_10G, 2.5G_DM, 2.5G_DMP, TXP_MR_10E, or MXP_MR_10E cards are automatically discovered and cannot be manually created. They can exist if:

• The layer rate is Optical Physical Section (OPS).
• Both cards support the same wavelength.
• The links are bidirectional.

Links between TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, TXP_MR_10G, 2.5G_DM, 2.5G_DMP, TXP_MR_10E, MXP_MR_10E cards or DWDM cards are manually created and cannot be automatically discovered. They can be created if:

• The layer rate is Physical.
• The link is unidirectional.
• The link rate is 10G ITU if a MXP_2.5G_10G, TXP_MR_10G, TXP_MR_10E or MXP_MR_10E card is used at one end of the link, or 2.5 G ITU if a TXP_MR_2.5G, TXPP_MR_2.5G, 2.5G_DM or 2.5G_DMP card is used at one end of the link.
• The link is unprotected.
• The link is created between TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, TXP_MR_10G, 2.5G_DM, 2.5G_DMP, TXP_MR_10E, or MXP_MR_10E trunk ports and DWDM channel ports.
• DWDM channel ports are unidirectional and can only be used as the link source if they are transmit ports and as the link destination if they are receive ports.
• The working wavelength of TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, TXP_MR_10G, 2.5G_DM, 2.5G_DMP, TXP_MR_10E, and MXP_MR_10E cards is equal to the expected wavelength set on the DWDM channel port on the other end of the link.

Prime Optical discovers links that are created in CTC as L2 trunk-to-trunk links and displays them with a layer rate of L2. Only 10GE_XP and GE_XP cards in L2 mode support L2 trunk-to-trunk links.

When a DWDM transponder card (including a DWDM line card) is used as the destination of a manual link with a channel port, the wavelength is not calculated, because the physical connection works correctly. Therefore, verify that you want to create a manual link between a given channel (for example, a demux card) and a TXP card whose trunk port is set to a different wavelength.

Viewing the Link Report

The Link Report shows information about each link attribute. Use the Link Report to view, modify, and delete links. You can open the Link Report for the Prime Optical domain, network partition, subnetwork, group, or NE. You can launch the Link Table from the Link Report . For more details on Link table, see Viewing the Link Table.

If you select the Prime Optical domain, network partition, subnetwork, or group, the Link Table shows all links that terminate on any of the NEs contained in the Prime Optical domain, subnetwork, or group.

If you select an NE, the Link Table shows all links that terminate on that particular NE.

Use one of the following methods to open the Link table:

• From the Network Map—In the Domain Explorer or Subnetwork Explorer , choose File > Network Map. In the Network Map , select a network partition, subnetwork, group, or NE; then, choose Configuration > Link Report.
• From the Network Map—Right-click a link or server trail and choose Link Report from the shortcut menu.
• From the Domain Explorer—Select the Prime Optical domain, group, or NE; then choose Configuration > Link Report.
• From the Subnetwork Explorer—Select the Prime Optical domain, network partition, subnetwork, or NE; then, choose Configuration > Link Report.

Note Modify Link is Enabled for OTS and OPS Link with patchcord Provision Type. User is allowed to modify and update Alias and Description of selected link. The modified Alias and Description for a link will also be retained under the following conditions:

• OOS/IS operation of nodes.
• If the same link is deleted and recreated from CTC.

Table 3-8 Field Description for the Link Report

Field	Description
Source NE ID	Displays the ID of the NE selected as the source node.
Source PTP	PTP of the link source.
Destination NE ID	Displays the ID of the NE selected as the destination node.
Destination PTP	PTP of the link destination. Because a link can have up to two destinations on the same NE, a “DST1” or “DST2” label is affixed to the destination to indicate the destination number.
Layer	Layer rate, defined as per ITU-T standard G.872 for multilayered optical networks. Values are Physical, Transmission Section, Optical Multiplex Section (OMS), OTS, OPS, SONET/SDH, Layer 2, Composite, and OTU.
Details	Bandwidth of the link as per the layer rate: For SONET links, the link rate is OC-3, OC-12, OC-48, OC-192, or Layer 2, depending on the NE configuration. For SDH links, the link rate is STM1, STM-4, STM-16, STM-64, or Layer 2. For DWDM links, the link rate is 40G ITU, 10G ITU, 2.5G ITU, or OTS. For OCH links, the link rate is 10G ITU or 2.5G ITU. For patchcord links on Layer 2, the link rate is 10G ITU, 1G ITU, or Fast Ethernet. For links between Not Managed/Other Vendor NEs, the link rate is Not Applicable. For links between Not Managed/Other Vendor NEs and a CTC-based NE, the rate is that of the CTC-based NE. Links between a SONET/SDH link and a Not Managed/Other Vendor NE depend on the link source. If the link source is the Not Managed/Other Vendor NE, the layer rate is Not Applicable. If the link source is the SONET/SDH link, the layer rate is that of the SONET/SDH link. For server trails, this field displays the server trail type and the number of server trails.
Alias	Enter a unique alias name for the NE. The alias name can be alphanumeric. It can also contain characters from international character sets.
Description	Enter a description of the NE.
Service State	Select the state of the termination: IS-NR—In Service–Normal OOS-AU—Out of Service–Autonomous OOS-MA—Out of Service–Management OOS-AUMA—Out of Service–Autonomous and Management
Provision Type	Specify the type of link provisioning. Values are: Manual—The link is manually provisioned. Patchcord (Applicable only to links involving transponders and DWDM modules)— The link is an internode or intranode termination provisioned between homogeneous ports. A patchcord link represents the connection between a line card and a transponder, or the connection between a transponder and a DWDM card. Patchcord links can be provisioned by Prime Optical or CTC users and are maintained by the NEs. Note Protection groups are not recognized when creating patchcord or manual links.
Is Routable	Defines if it is possible to route a service over the link as described by the row in the link report.
Is Valid	Reports if the link is present in management system and in the managed network.
Connection Type	Filters out inter-NE or intra-NE links. By default, all links are displayed. You can also filter using server trails.
Cost	Specify a numeric cost associated with the SONET or SDH layer link. The cost range is 0 to 999999. This field applies only to links in the SONET or SDH layer between CTC-based NEs. For all other links, the Cisco default value is 1024. All autodiscovered links have the Cisco default cost 1024.
SRLG	(SONET/SDH layer rates only) Enter a free-format string that represents the SRLG, or a group of links that share a common risk. For example, links that originate at a node share the node as the common risk. The Shared Risk Link Groups field supports up to 5 comma-separated values, with 32 characters per value.
Utilization	Link utilization information for Layer 3, SONET/SDH, and OTS links. For non-Layer 3, non-SONET/SDH, non-OTS links, this field shows Not Applicable. For detailed information about link utilization, see Viewing Link Utilization.
Alarm	Reports the number of active alarms for each alarm severity (critical, major, minor, or warning).
Name	Name of the selected link. Note The names of bidirectional links are prone to change when they are rediscovered as a result of a system restart. Prime Optical assigns names to the links, combining their source and destination points. Because the links are bidirectional, the order of the source and destination points could change when the links are rediscovered.
Description	User-entered description of the selected link. If you do not modify the System Default string in the Create Link wizard, the description is a string built from the endpoint information.
Protection Type	Displays the circuit protection type.

Viewing the Link Table

The Link Table shows information about each link attribute. Use the Link Table to view, modify, and delete links. You can open the Link Table from Configuration > Link Report > Link Table.

Note • A link is visible in the Link Table even if the source or destination NE has been deleted, but this same link is not visible in the Network Map. If the NE is deleted from the Deleted Network Elements group, the references to that NE are removed from the Link table.

• When launching the Link Table in a large or high-end network setup and on a larger scope (for example, for the Domain Explorer ), a database timeout can occur due to the large volume of data that needs to be retrieved. As a workaround, launch the Link Table on a smaller scope.

Note the following constraints for OPS unidirectional and bidirectional patchcord links, Optical Transmission Section (OTS) links, Y-cable patchcord links, server trail links, and autodiscovered links:

• An invalid patchcord link is a link that has been deleted from the Network Control Protocol (NCP) layer but is still present in the Prime Optical database. The resources allocated for the patchcord link are freed up and made available for a new link.
• Invalid links are shown in strikethrough font.
• An invalid patchcord link is removed from the Prime Optical database and disappears from the Link table only if a Prime Optical user deletes that link. All logical and physical resources are released from the deleted link.
• If the Link Table contains an invalid patchcord link and you create a new patchcord link using the same termination points and attributes as the invalid link, the invalid patchcord link becomes valid and is shown in the Link table as a valid link.
• When an invalid patchcord link becomes valid, the link name changes. Prime Optical uses link identification numbers to create the patchcord link name. The NCP layer associates identification numbers to both terminations during the link creation phase. These numbers are used to identify the patchcord link inside the NCP layer and are required to delete the patchcord link. To change the patchcord link name:

1. Use the Create Link wizard to create a new patchcord link.

2. Force the patchcord link validity to change to INVALID (for example, by marking the NE as Out of Service or deleting the patchcord link).

3. Create a new patchcord link that uses the same termination points and attributes as the invalid link.

4. View the patchcord link name in the Link Table . The link name has changed.

Table 3-9 describes the fields in the Link table.

Filtering the Link Table

Step 1 In the Link Table , choose File > Filter . The Filter dialog box opens.

Step 2 Specify the filter parameters described in Table 3-10 .

Step 3 Click OK to run the filter.

Creating Links

Step 1 Open the Create Link wizard by using one of the following methods:

• From the Network Map—Select the source NE and choose Configuration > Create Link (or right-click the NE and choose Create Link ). Connect the line to the destination NE or click the map. The Create Link wizard opens. The Link Destination panel displays a list of NEs that support compatible layer rates with the source NE.
• From the Domain Explorer or Subnetwork Explorer—Select the source NE and choose Configuration > Create Link (or right-click the NE and choose Create Link ). The pointer changes to a plus sign; select the destination NE or group. The Create Link wizard opens.

Note If you press the Esc key while the plus sign is enabled, the operation is canceled and the plus sign returns to a pointer.

Note Table 3-11 describes the fields in the Create Link wizard. Fields shown depend on the NE selected.

Step 2 Create the link, as follows:

a. Enter the following information in the Link Attributes panel:

• Name
• Link alias
• Description
• Provision type
• Layer
• Layer detail

Note Links from a Not Managed/Other Vendor NE to a CTC-based or Not Managed/Other Vendor NE will have a link rate of Not Applicable. Links from a CTC-based NE to a Not Managed/Other Vendor NE will have the link rate allowed for the CTC-based NE.

Note The layer details displayed in the Create Link wizard are based on the NE selected as the link source. For example, when you attempt to create a link from NE A to NE B, the link sizes displayed are based on the supported sizes and inventory of NE A. If the link is attempted in the reverse direction, from NE B to NE A, the link sizes displayed are based on the inventory and sizes for NE B. As a result, the link sizes displayed could differ when the operation is attempted differently. An error message is displayed in the Link Destination panel when the size displayed is not applicable for the destination NE.

• Wavelength ( available only if the layer is Optical Channel , the provisioning type is Patchcord , and the direction is Unidirectional)
• Protection
• Direction

Note Prime Optical allows creation of bidirectional SONET/SDH links as well as unidirectional and bidirectional physical links.

If the layer rate is SONET/SDH or Layer 2, only bidirectional links are available. For other layer rates, both unidirectional and bidirectional links are available.

• Cost
• Shared risk link groups

b. Click Next .

c. Enter the following information in the Link Source panel:

• Node
• PTP slot
• PTP port
• PTP value
• Name

d. Click Next .

e. Enter the following information in the Link Destination panel:

• Node
• PTP slot
• PTP port
• PTP value
• Name

Note A PTP can be associated with only one bidirectional link or two unidirectional links at a particular layer rate for all NEs except Not Managed/Other Vendor NEs. For Not Managed/Other Vendor NEs, a PTP can terminate in only one link.

Note If you are creating a SONET/SDH-layer manual link between two CTC-based NEs, verify that no DCC exists on the endpoints that are selected for the link termination.

Note You can create a provisional patch cord (PPC), a virtual link, between 15600 and 15454 NEs destination points.

f. Click Next .

Step 3 The Link Summary panel summarizes the attributes of the new link. To change the link summary information, click Back and change the selections as needed.

Step 4 Click Finish .

Table 3-11 Field Descriptions for the Create Link Wizard

Field	Description
Link Attributes Panel
Name	Enter a unique name for the new link. The link name is a free-format string, up to 256 characters.
Link Alias	Enter a unique alias name for the new link. The alias name can contain alphanumeric characters. It also supports international character sets.
Description	Enter a description of the new link. The link description is a free-format string, up to 256 characters.
Provision Type	Specify the type of link provisioning. Values are: Manual—The link is manually provisioned. Patchcord—( Applicable only to links involving transponders and DWDM modules ) The link is an internode or intranode termination provisioned between homogeneous ports. A patchcord link represents the connection between a line card and a transponder, or the connection between a transponder and a DWDM card. Patchcord links can be provisioned by Prime Optical or CTC users and are maintained by the NEs. Note Protection groups are not recognized when creating patchcord or manual links.
Layer	Choose the link layer rate, defined as per ITU-T standard G.872 for multilayered optical networks. Values are: Physical OTS (Optical Transmission Section) OMS Note Only links with manual provision type support Multiplex section layer. OPS SONET/SDH Layer 2 Note Patchcord links on Layer 2 can be created between NNI ports on GE-XP or 10GE-XP cards if the card modes are set to L2 over DWDM.
Layer Detail	Choose the bandwidth of the link as per the layer rate. For SONET links, the link rate is OC-3, OC-12, OC-48, OC-192, or Layer 2, depending on the NE configuration. For SDH links, the link rate is STM1, STM-4, STM-16, STM-64, or Layer 2. For DWDM links, the link rate is 100G ITU, 40G ITU, 10G ITU, 2.5G ITU, or OTS. For OCH links, the link rate is 10G ITU or 2.5G ITU. For patchcord links on Layer 2, the link rate is 10G ITU,1G ITU, or Fast Ethernet. For links between Not Managed/Other Vendor NEs, the link rate is Not Applicable. For links between Not Managed/Other Vendor NEs and CTC-based NEs, the rate is that of the CTC-based NE. Links between a SONET/SDH link and a Not Managed/Other Vendor NE depend on the link source. If the link source is the Not Managed/Other Vendor NE, the layer rate is Not Applicable. If the link source is the SONET/SDH link, the layer rate is that of the SONET/SDH link.
Wavelength	Filter the wavelength in the first drop-down list. In the second drop-down list, choose the appropriate wavelength value according to the selected filter. The Wavelength drop-down lists are available only if the layer is Optical Channel , the provisioning type is Patchcord , and the direction is Unidirectional . Note When the layer is Optical Channel, the provisioning type is Patchcord, and the direction is Bidirectional, the Wavelength drop-down lists are disabled, but Prime Optical executes an automatic wavelength check on the endpoints before creating the link. If the link endpoints do not have the same wavelength value, the link is not created and a wavelength error is generated.
Protection	Specify the link protection: Unprotected, 1+1, Y-Cable (meaning 1+1 with Y-cable protection), 2-Fiber BLSR/MS-SPRing, 4-Fiber BLSR/MS-SPRing, or Not Applicable. For CTC-based NEs, select Unprotected, 1+1, or Y-Cable. For links between Not Managed/Other Vendor NEs, the link protection is Not Applicable. For links between Not Managed/Other Vendor NEs and CTC-based NEs, the link protection is that of the CTC-based NE.
Direction	Specify whether the link is unidirectional or bidirectional.
Cost	Specify a numeric cost associated with the SONET or SDH layer link. The cost range is 0 to 999999. This field applies only to links in the SONET or SDH layer between CTC-based NEs. For all other links, the Cisco default value is 1024. All autodiscovered links have the Cisco default cost 1024.
Shared Risk Link Groups	(SONET/SDH layer rates only) Enter a free-format string that represents the SRLG, or a group of links that share a common risk. For example, links that originate at a node share the node as the common risk. The Shared Risk Link Groups field supports up to 5 comma-separated values, with 32 characters per value.
Link Source Panel
Node	Identify which NE serves as the source of the link.
Physical Termination Point	Identify the physical side, shelf, slot, subslot (if applicable), and port in the source NE. For the ONS 15216, identify the name of the PTP. Note The card type is shown adjacent to the slot number; for example, “1 (OC3_8)” represents the OC3_8 card in slot 1. Note If the port name is available, it is shown adjacent to the port number. Note OTS links can be created for FLD_OSC cards.
PTP Value	(Not Managed/Other Vendor NEs only) Specify the PTP value. The maximum length is 30 characters; the minimum length is 1 character.
Link Destination Panel
Node	This is a display-only field if you selected an NE as the destination of the link. If you selected a group as the destination of the link, choose from the drop-down list a specific NE that will be the destination of the link.
Physical Termination Point	Identify the physical side, shelf, slot, subslot (if applicable), and port in the destination NE. For the ONS 15216, identify the name of the PTP. Note The card type is shown adjacent to the slot number; for example, “1 (OC3_8)” represents the OC3_8 card in slot 1. Note If the port name is available, it is shown adjacent to the port number. Note OTS links can be created for FLD_OSC cards.
PTP Value	(Not Managed/Other Vendor NEs only) Specify the PTP value. The maximum length is 30 characters; the minimum length is 1 character.
Name	Enter a unique name for the new link.
Link Summary Panel
Link Summary	Summarizes the selections you made. To change the Link Summary, click Back and change your selection(s).

Note • After the links are created, each link has a different color notation depending on the alarm status of the PTP on which the link is created. Links between Not Managed/Other Vendor NEs are always black. The color of the link between a Not Managed/Other Vendor NE and a CTC-based NE is the color of the TP of the CTC-based NE. The colors are green for no alarm, yellow for minor alarms, orange for major alarms, and red for critical alarms. Invalid links (as reflected in the Is Link Valid field) are gray. An autodiscovered link can become invalid if (1) the DCC is disabled on either PTP; (2) either PTP is marked as Out of Service (OOS); (3) there is a fiber cut or transmitter/receiver failure; or (4) either NE is marked as OOS. Manual links are colored to match the highest alarm severity on either PTP. L2 links are always gray.

• Links that are supported in different layer rates can be created only if the link endpoints are compatible with the specified layer rate.
• If Prime Optical discovers a link, it automatically assigns layer rates based on its endpoint.

Table 3-12 summarizes link color as it relates to link type and the involved NEs.

Modifying Links

Use the Modify Link wizard to modify the Name , Alias , Description , Cost , or SRLG (if applicable) of links displayed in the Link Table . You can modify a link in the Link Table or in the Network Map .

Note You cannot modify patchcord links.

Step 1 Open the Modify Link wizard (see Table 3-13 ) by using one of the following methods:

• In the Link table , select a link and choose Edit > Modify Link (or click the Modify Selected Link tool).
• In the Network Map , select a link and choose Configuration > Modify Link (or click the Modify Selected Link tool).

Step 2 In the Link Attributes panel, modify the following information, as needed:

• Name
• Link alias
• Description
• Direction
• Cost
• Shared risk link groups

Note If you modify the SRLG value, you receive the warning popup “There might be circuits routed with diverse SRLG constraints on this link. Changing risk link groups might affect the diversity constraint.” Click OK; then, verify the SRLG value that you entered.

Step 3 Click Next until you reach the Finish panel.

Step 4 Verify the link summary and click Finish .

Note After certain topology reconfigurations that involve removing fiber, the Network Map might not report the correct links. This problem occurs because the Prime Optical server is not synchronized with the new network topology and cannot retrieve network or link updates. This problem applies only to CTC-based NEs. The workaround is to remove the links completely by deleting the SDCC termination on the ports, rather than by simply unplugging the fiber cable.

Deleting Links

You can delete one or multiple links from the Link Table . You can delete a single link from the Network Map .

Note OTS Link cannot be deleted directly from link report, if it is associated with OMS Link. Delete OMS link, then the OTS links can be directly deleted from the Link Report.

Step 1 In the Link Table , select one or multiple links and choose Edit > Delete Link (or click the Delete Selected Link tool). In the Network Map , select a single link and choose Configuration > Delete Link .

Step 2 Click OK in the confirmation dialog box.

Step 3 For multiple link deletion, complete the following substeps:

a. The Deleting Links dialog box tracks the progress of the deletion. If you selected links that cannot be deleted, you receive the message: “Some of the links can’t be deleted, proceed anyway?” Review the links that you selected for deletion; then, click OK .

b. The Multiple Link Deletion Summary dialog box opens, summarizing the results of the deletion. Click the Details button to see which links were deleted, and which links could not be deleted.

The following rules apply to single and multiple link deletion:

• User-created links or invalid autodiscovered links can be deleted.
• Valid autodiscovered links cannot be deleted.
• An autodiscovered link is marked Invalid when Prime Optical can no longer verify the link from either of the NEs at the ends of the link.
• To remove a valid autodiscovered link from Prime Optical, you must remove the topology neighbors from both NEs at the end of the link.
• Prime Optical can delete physical links even if there is an autodiscovered SONET/SDH link.
• If you use Prime Optical to delete invalid autodiscovered links, verify that the DCCs are deleted on both ends of the link. If you delete a partial link with a DCC up on one end, it might cause problems later with the creation of phantom links.
• When you delete an OSC termination, any autodiscovered links become invalid. If you then delete the invalid links and recreate the OSC termination, an update event is generated. But because Prime Optical cannot find a link to update, it discards the event and does not discover the link. This is normal Prime Optical behavior in response to the deletion of invalid links. The workaround is to mark the NE(s) as Out of Service and then In Service.

Create or Edit OMS Link

The OMS Links are created from the Network Map . To create or edit OMS Links , follow these steps:

Step 1 In the Domain Explorer , choose Network Map.

Step 2 Select a node for which to create or edit a circuit, right-click and choose Create OMS Link.

The Create OMS Link window opens.

Step 3 In the Name field, enter the link name. The link name can be manually assigned or automatically generated.

Step 4 In the Type field, choose OMS . The link type determines the provisioning options that are displayed.

The following attributes are not available when the OMS type is chosen:

• WSON Attributes pane
• Wavelength pane
• Path Constraints pane
• Bidirectional check box (OCHNC only)
• Protection drop-down (OCHCC and OCHNC only)
• Apply Trunk Ports check box (OCHTRAIL only)

Step 5 Expand the Details field to configure all custom related fields. In the Details area, enter the following:

• Alias—Enter a unique alias name for the new circuit. The alias name can be alphanumeric. International character sets are also supported.

The alias name of the links OTS contains the name of the corresponding OMS link (if the OMS link is created by the user).

• Description—Enter a circuit description of up to 256 characters.

Step 6 In the Source Termination area, enter the following:

• Managed Element—Specifies a node in the network. Press CTRL+SPACE to display the available filters.
• Termination Point—Allows you to change the managed element and to specify the termination point by pressing CTRL+SPACE or by clicking the search icon.

A new dialog box is opened and the user can filter results by typing the appropriate fields in the Enter Search Query text box. Press CTRL+SPACE to display the available filters.

• Local Drop—This field is displayed only when the OCH-NC circuit is selected.

Step 7 In the Destination Termination area, enter the following:

• Managed Element—Specifies a node in the network.
• Termination Point—Allows you to change the managed element and to specify the termination point by pressing CTRL+SPACE or by clicking the search icon.

A new dialogue box is opened and the user can filter results by typing the appropriate fields in the Enter Search Query text box. Press CTRL+SPACE to display the available filters. When user selects an OCH-NC circuit, the selection of local drop and local source is available.

• Local Source—This field is displayed only when the OCH-NC circuit is selected.

Viewing the Link Maintenance Report

The following new functionality is supported on the OCHCC, OCHNC and OCH Trail circuits:

• Protection groups related to the circuits sharing a selection of OTS links.
• Perform bulk protection operations on those circuits

The information is available in the Link Maintenance Report .

You can launch the Link Maintenance Report only from the network map when you right-click the multiple links selection.

Performing Switch Operations

You can perform protection operations on single and multiple circuits only if the following conditions are met:

• A protection group is present.
• Current protection operations on sources and destinations are the same.

From the Link Maintenance Report , click the Perform Protection Switch Operations button. An Operations dialog box containing the protection operations available for Y-Cable and Splitter protection groups is displayed.

Once the operation is completed, a protection operation report with the result is displayed.

Viewing Link Utilization

The Link Utilization Table displays utilization information for the selected links. Link utilization, shown as a percentage, displays the overall consumption of bandwidth. All bandwidths are in megabits per second (Mb/s).

% Link utilization = ([Bandwidth consumed] / [Total bandwidth of link]) x 100

Example: In SONET, for an OC12 link, the total bandwidth is (12 x 51.84) Mb/s, where STS-1/OC12 = 51.84 Mb/s.

Depending on the number of provisioned circuits, the consumed bandwidth is totaled. Circuits such as VAP/LAP and virtual tributary (VT) tunnel are preprovisioned and are not included in the calculation. This is applicable to SONET and SDH.

Example: In SDH, for an STM4 link, the total bandwidth is (4 x 155) Mb/s, where STM-1 = 155 Mb/s.

Note • Link utilization does not apply to server trails. An error message is displayed if you attempt to launch the Link Utilization table from a server trail.

• The customize table view function is not available for the Link Utilization table.

Use one of the following methods to view the Link Utilization table:

• From the Domain Explorer—Select the Prime Optical domain, group, or NE; then choose Configuration > Link Report . The Link Report opens.
• From the Link Report —Select a link, right-click and choose Link Utilization Table .

Table 3-16 provides descriptions.

Note You can launch the Circuit Trace window from a selected circuit in the Link Utilization table. Select a circuit in the Link Utilization table and then choose View > Circuit Trace. See Tracing Circuits.

Table 3-16 Field Descriptions for the Link Utilization Table

Column	Description
STS ID (SONET only)	Displays the STS ID.
VT1.5 ID (SONET only)	Displays the VT 1.5 ID.
VT2 ID (SONET only)	Displays the VT2 ID.
VC4 ID (SDH only)	Displays the VC4 ID.
VC3/TUG3 ID (SDH only)	Displays the VC3/TUG3 ID.
TUG2 ID (SDH only)	Displays the TUG2 ID.
VC12 ID (SDH only)	Displays the VC12 ID.
VC11 ID (SDH only)	Displays the VC11 ID.
Circuit Name	Displays the name of any circuits passing through the link. When Unused appears in the Circuit Name field there is unused bandwidth available, and the Circuit Type, Circuit Protection Type, Customer ID, and Service ID fields are blank.
Circuit Alias	Displays a unique alias name for the new circuit. The alias name can contain alphanumeric characters. It also supports international character sets.
Circuit Type	Displays the circuit type.
Circuit Protection Type	Displays the circuit protection type.
Switch State	Displays the switch state for UPSR protected circuits only. Values are: CLEAR—Removes a previously set switch command. MANUAL—A manual switch is active on the span. FORCE—A force switch is active on the span. LOCKOUT_OF_PROTECTION—A protection lockout is active on the span; traffic cannot be switched to the span. Note A force switch always overrides a manual switch. A protection lockout always overrides both a force switch and a manual switch. To configure the span switch state, see Configuring the Span Switch State on a UPSR Protected Circuit. Note N/A is displayed for non-UPSR-protected circuits.
Customer ID	Displays the user-defined customer ID.
Service ID	Displays the user-defined service ID number.

Launching the Link Utilization Table for SONET/SDH or OTS Links from the Network Map

Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).

Step 2 Right-click a SONET/SDH or OTS link in the Network Map and choose Link Utilization from the right-click menu.

Configuring the Span Switch State on a UPSR Protected Circuit

Note The span switch is applicable to all UPSR circuits in the Link Utilization table. The selection context has no impact on the switching. When you perform protection switching after selecting an unprotected circuit, the protection switch applies to only UPSR-protected circuits.

Step 1 In the Domain Explorer window, choose Configuration > Link Report . The Link report opens.

Step 2 In the Link Report , choose Link > Link Utilization table .

Step 3 In the Link Utilization table, choose Configuration > Span Switch > CLEAR, MANUAL, FORCE , or LOCKOUT_OF_PROTECTION .

Note Switch states that cannot be applied are dimmed.

The possible switch state that can be applied to the circuits in the Link Utilization table is decided by switch priority. The switch priority order is:

1. MANUAL

2. FORCE

3. LOCKOUT_OF_PROTECTION

4. CLEAR

Note The CLEAR switch state overrides all other switch states.

Example 3-1 Unprotected OC-48 Link

Example 3-2 2-Fiber BLSR OC-48 Link

Filtering the Link Utilization Table

Step 1 In the Link Utilization table, choose File > Filter (or click the Filter Data tool). The Filter dialog box opens.

Step 2 Specify the filter parameters described in Table 3-17 .

Step 3 Click OK to run the filter.

Setting OTS Link Capacity

You can set the maximum number of wavelengths on one or more OTS links.

Step 1 In the Link Table , select a single OTS link or multiple OTS links, and choose Configuration > Set OTS Link Capacity (or click the OTS Link Capacity window icon) or from the domain explorer, select the Prime Optical domain, group, or NE; then choose Configuration > Link Report > Link > Set OTS Link Capacity.

Step 2 Enter the maximum number of wavelengths for the selected OTS links.

Step 3 Click Apply. A Link Capacity Set Result window appears and summarizes the number of links that were configured or have failed.

Note A warning message appears when you select links of different layers.

Step 4 Click on the OTS success link to launch the report. The results can be printed in a text report.

Viewing OTS Link Utilization and Circuits

The OTS Link Utilization Report displays utilization information for the selected OTS links. OTS link utilization, shown as a percentage, displays the resources used. You can also view associated circuit names, types and wavelengths.

Use one of the following options for viewing OTS Link Capacity window:

• From the Domain Explorer —Select the Prime Optical domain, group, or NE; then choose Configuration > Link Report > Link > OTS Link Utilization Report.
• From the Link Table—Select a link from the Link Report, and choose Configuration > OTS Link Utilization Report.

To view the Link Utilization and Circuit Reports :

Step 1 In the Domain Explorer window, choose Configuration > Link Report . The Link report opens.

Step 2 Select the OTS links that you want to view utilization for.

Step 3 From the Link Report window, choose > Link > Link Table.

Step 4 In the Link Table , choose Configuration > OTS Link Utilization Report (or click the Open Link Utilization Report icon).

Step 5 From the OTS Link Utilization Report , select the link that you want to view associated circuit names, types, and wavelengths for.

Step 6 Click the Open Circuit Report icon.

If the Auto-Refresh check box is checked in the OTS Link Utilization Report window, the respective rows are automatically highlighted when a circuit undergoes a change. When the Auto-Refresh check box is not unchecked, a notification bar appears at the top of the window, stating that the reported data has changed. To refresh the report, click the Refresh tool.

If the report consists of more than one page, the Previous Page and Next Page arrows at the top-right corner of the Circuit Report window are enabled. The Pagination Settings tool allows you to select the number of records per page to display.

The status bar at the bottom of the OTS Link Utilization Report window displays:

• Current page number
• Total number of pages in the report
• Number of records displayed
• Number of records selected

To move to a specific page, enter the page number in the Page text box and press Enter.

Exporting the OTS Link Utilization Report

To export the OTS Link Utilization Report , complete the following steps:

Step 1 In the OTS Link Utilization Report window, choose File > Export to CSV (or click the Export to CSV tool). The Export to CSV dialog box appears.

Step 2 Specify the filter parameters described in Table 3-18 .

Step 3 Click OK to export.

Table 3-18 Field Descriptions for the Export to CSV Dialog Box

Field	Description
Separator Character	Allows you to select a separator character. Values are Comma, Tab, and Other. Note If you choose Other, enter a value in the text box next to the Separator Character drop-down list.
Data to Export	Allows you to define the rows to be exported. Values are: All {0} Selected Records All Records at Page {0} Entire Table Note The first option is available only if at least one record is selected. The second option is available only if there is more than one page.
Export File	Click Browse to select the location to which you want to export the file.

OMS Link Table

The Optical Multiplex Section (OMS) Link Table is a specialized Link Table that shows only OMS layer links. It can be launched from Link Table . OMS links are unidirectional.

Open OMS Link Table from an OTS Link

From the Link Table , you can open the OMS Link Table , which contains the OMS links. The OMS links are displayed only when it is launched from an Optical Transmission Section (OTS) link only. If you open the OMS Link Table , the OMS links used by the OTS links are displayed.

Open Underlying OTS Link Table

The Open Underlying OTS Link Table displays underlying information for the selected OMS link. The Open Underlying OTS Link Table menu can be launched from the Configuration menu only. The action is enabled only when an OTS link is selected. You cannot select multiple OTS links. This action results in a new Link Table which contains the OMS links that use the selected OTS link.

To view the Open Underlying OTS Link table, follow these steps:

Step 1 In the Domain Explorer window, choose Configuration > Link Report. The Link report opens.

Step 2 Select the OTS links for which you want to view the utilization.

Step 3 From the Link Report window, choose Link > Link Table.

Step 4 In the Link Table , choose Configuration > Open underlying OTS Link Table.

A new Link Table is opened, but the details displayed are the OTS links that build the OMS.

Open OMS Link Table

The Open OMS (Optical Multiplex Section) Link table displays optical multiplex section information for the selected OTS links. The Open Underlying OTS Link table menu can be launched from the Configuration menu only. It is possible to create Manual OMS links using the Link Wizard. OMS links are unidirectional.

You must use the Link Wizard to create manual links. Follow these steps:

1. Choose OMS layer links. It can be launched from Circuit Report or from Link Table.

The Link Wizard shows the available ports.

2. Open Link Table ( Underlying OTS Link Table) with the OTS links used by the OMS links .

The OMS Link Table can be launched from:

– The Link Table , an OTS link containing the OMS links that use the OTS links.

– A circuit in the circuit report that contains the OMS links traversed by the circuit (for OCHXX circuits only).

To view the Open OMS Link Table , follow these steps:

Step 1 In the Domain Explorer window, choose Configuration > Link Report. The Link report opens.

Step 2 Select the OMS links for which you want to view the utilization.

Step 3 From the Link Report window, choose Link > Link Table.

Step 4 In the Link Table, choose Configuration > Open OMS Link Table.

A new Link Table is opened, but the details displayed are the OTS links that build the OMS.

Creating Server Trails

Step 1 Select the source NE in the Domain Explorer or Subnetwork Explorer and choose Configuration > Create Server Trail (or right-click the NE and choose Create Server Trail ). The pointer changes to a plus (+) symbol; select the destination NE. The Create Server Trail wizard opens.

Step 2 In the Server Trail Attributes pane, specify the following:

• Type—Select the type of server trail to create.
• Size—Select the size of the server trail. The options displayed depend on the type selected.
• Protection—Select the server trail protection type.
• Number of Trails—Enter the number of trails.
• Shared Risk Link Groups—Enter a free-format string that represents the shared risk link group or a group of links that share a common risk.
• Cost—Specify the numeric cost associated with the server trail.

Step 3 Click Next.

Step 4 In the Source pane, set the server trail source. The options displayed depend on the server trail type selected in the Server Trail Attributes pane.

Step 5 Click Next .

Step 6 In the Destination pane, set the server trail destination. The options displayed depend on the server trail type selected in the Server Trail Attributes pane.

Step 7 Click Finish. The server trail is listed in the Link Table . You can also view the server trail in the Network Map .

Note Server trails that were created in Prime Optical or CTC are listed in the Link table. Open the Link Table Viewing the Link Table for more information.

Modifying Server Trails

Step 1 Open the Modify Link wizard using one of the following methods:

• In the Link Table , select a server trail and choose Edit > Modify Link (or click the Modify Selected Link tool).
• In the Network Map , select a server trail and choose Configuration > Modify Link (or click the Modify Selected Link tool).

Step 2 In the Link Attributes panel, modify the following information, as needed:

• Name
• Alias
• Description
• Cost
• Shared risk link groups

Note If you modify the SRLG value, you receive the warning popup “There might be circuits routed with diverse SRLG constraints on this link. Changing risk link groups might affect the diversity constraint.” Click OK; then, verify the SRLG value that you entered.

Step 3 Click Next .

Step 4 Verify the link summary and click Finish .

Deleting Server Trails

Step 1 In the Link Table , select a server trail and choose Edit > Delete Link (or click the Delete Selected Link tool). In the Network Map , select a server trail and choose Configuration > Delete Link .

Step 2 Click OK in the confirmation dialog box.

Customizing a Network Map

Use the Edit menu and toolbar buttons to customize your network map.

Step 1 In the Domain Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).

Note There is no Network Map for the Discovered Network Elements or Deleted Network Elements groups.

Step 2 Use the Edit menu in the Network Map window to customize the Network Map . Edit menu options include:

• Filter—Filters the network map by NEs, groups, or links.
• Set Background—Allows you to set the map background.
• Zoom Magnify—Magnifies the area on the map where the pointer is placed when the left mouse button is held down.
• Zoom In—Zooms in on an object in the map view.
• Zoom Out—Zooms out on the map view.
• Zoom to Fit—Adjusts the view of the map to fit the window.
• Zoom Area—Lets you pan and zoom the view to a different region of the map.
• Zoom Magnify—Magnifies the area under the lens.
• Expand/Collapse Group—Shows or hides NEs contained in a group selected on the map.

Note A group on the map can be expanded if all of its nodes have a coordinate set at the given level. When a group is expanded, all nodes and subgroups are displayed around the expanded group.

• Collapse All Groups—Hides NEs contained in all groups on the map.
• Expand All Links—Shows links contained in an aggregate link.
• Collapse All Links—Hides links contained in an aggregate link.
• Grid Layout—Arranges nodes in a grid pattern.
• Explorer Mesh Layout—Arranges nodes in planar or nonplanar cyclic patterns.
• Uniform Length Edges Layout—Arranges nodes in patterns with edges of uniform length.
• User Preferences—Opens the User Preferences dialog box to set user preferences for options such as event notification and time.

Note Users with SuperUser privileges can configure labels for various nodes and device icons.

Viewing a Node on the Network Map

Icons on the Network Map are displayed based on the nodes you select in the Domain Explorer . Nodes on the Network Map do not have a default position unless one has been configured in a Network Partition Map or a SuperUser has configured one in the current map.

Launching the Network Map from the following nodes displays varying results:

• From the Prime Optical domain in the Domain Explorer—Displays all the groups and individual nodes in the Prime Optical domain.
• From a specific group in the Domain Explorer—Displays all NEs that belong to that group.
• From a specific NE in the Domain Explorer—Displays the parent group that the selected NE belongs to.
• From a specific network partition in the Subnetwork Explorer—Displays all the NEs in that network partition.

Adjusting the Zoom Level or Pan Position

When the Network Map is launched from the Prime Optical domain, it displays a world map with the individual groups, network partitions, and NE icons. To view a particular region or icon, you adjust the zoom level or pan position.

Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool). The Network Map opens with the node preselected.

Step 2 Do any of the following:

• To adjust the zoom level, do either of the following:

– On the Network Map , choose Edit > Zoom In , Zoom Out , Zoom to Fit, or Zoom Area .

– Click the Zoom In , Zoom Out , Zoom to Fit, or Zoom Area tool.

• To adjust the pan position, use the mouse to pan across the desired region on the map.
• View or hide the links contained in each link bundle (aggregate link):

– To view links, click a link bundle and choose Edit > Expand All Links (or double-click a link bundle to show all the links)

– To hide links from view in the Network Map , click a link bundle and choose Edit > Collapse All Links .

Table 3-19 describes how the zoom tools at the right of the Network Map work.

Table 3-19 Field Description for Zoom Level

Note When the network map is zoomed in to show the entire node icon, the related device icons and labels are displayed. When the zoom level is low, only the Alarm Severity icon for each node is displayed. When zoom magnify is applied to the Alarm Severity icon, the entire node icon is visible, along with the related device icons and labels.

Configuring the Icon Size of Nodes

The Network Maps enables you to set the background and icon size separately and allows them to stick on to each other. The Node Icons are displayed from normal to high level representation along with the Alarm Severity icon. Using the slider, you can zoom in or zoom out the icon size of your choice.

To zoom in the background and increase the icon size, do the following:

Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map. The Network Map opens with the node preselected.

Step 2 Click Gear in the zoom toolbar.

The Icon Size Configuration dialog box is displayed.

Step 3 Move the slider on the left or right to adjust the zoom level to increase the icon size. See Table 3-19 for more information.

The zoom level and icon size percentage are displayed above the slider.Click Apply.

Step 4 Choose File > Save Map Coordinates to save the icon size configuration.

Modifying a Map Background Image

Network map backgrounds are provided by default as part of Prime Optical, and are used to display a geographical layout of the network. The icons in the Network Map can be customized. See Icons and Menus Displayed in Prime Optical for details of all the icons displayed in the Network Map window.

Prime Optical supports nonanimated GIF, JPG/JPEG, PNG, and shapefile format icons and maps. Shapefile is a universal standard for data files and allows users to zoom in and zoom out without losing details.

To modify a map background:

Step 1 In the Domain Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).

Step 2 In the Network Map window, choose Edit > Select Background . The Select Background dialog box opens.

Step 3 Select a background image from the list of existing background images. The selected image appears in the Preview area.

Note If you want to add a new background image to the list, click the Add tool at the top of the list, browse, and select the file to be added. In the Data area on the right, you can provide the name, description, and additional files if any, for the newly added background image. Clicking the Save tool in the Data area will save the attributes you entered for the background image.

Step 4 After choosing a map background, click Apply . The new map background appears in the network map.

Step 5 Select the No Background check box if you do not want a background image displayed for the network map.

Step 6 Choose File > Save Map Settings to save your settings.

Note You can edit the name and description, and change or upload new files for an existing background image, by selecting the row and editing the fields in the Data area. You can delete files for a selected background image by clicking the Remove tool in the Data area.

You can also delete an existing background image by selecting it from the list and clicking the Remove tool at the top of the list.

Configuring the Network Map View

Prime Optical allows you to configure the appearance of the graphical components on the network map. You can set how nodes, groups, and links appear.

To configure the network map view:

Step 1 In the Network Map window, choose Edit > Global Network Map Configuration.

Step 2 On the Node tab:

• In the Badges area, from the list of badges, drag and drop the badges to be displayed on the nodes in the map. The badges available are:

– Multishelf

– WSON State

– Node Role

– Admin State

– Alarm

– Discovery State

– Connection State

• From the Labels area, drag and drop the labels to be displayed for each node. The labels to choose from include:

– Alias

– Model Type

– IP Address

– Software Version

• If you want the alarm to be highlighted on the map, check the Highlight on Alarm check box.

Step 3 On the Group tab, check one or both check boxes (Alarm or Connection State) to display the Alarm or Connection State badge for the group on the network map.

Step 4 On the Link tab:

• Enter the desired values for the following:

– Width of the link

– Distance between links

– Width of the links for a bundle

– Minimum number of links for a bundle

• If you want to hide all links in a bundle on the network map, select the Bundle Collapsed by Default check box.
• If you want the DWDM side for the links displayed on the map, select the Show DWDM Side check box in the Link Attributes section.
• Specify how frequently you want the links refreshed on the map, by selecting the Refresh Interval in the Link Refresh Interval section.

Note The default value for the Refresh Interval is 15 minutes.

Step 5 Click OK.

Saving Changes to the Network Map

Step 1 In the Domain Explorer or Subnetwork Explorer tree, click a node and choose File > Network Map (or click the Open Network Map tool).