Complete the "DLP-D60 Log into CTC" task at the node where you want to view the cross-connect card resource usage. If you are already logged in, continue with Step 2.

Click the Maintenance > Cross-Connect > Resource Usage tabs.

In the Summary area of the Resource Usage tab, view the following information:

VC4 Matrix-Provides the percent of VC4 paths and VC4s dropped to lower order paths that are in use. 384 VC4s are available with XC-VXL-10G and XC-VXC-10G cross-connect cards; 192 VC4s are available with XC-VXL-2.5G cards.

TUG3 Matrix Ports-Provides the percent of cross-connect card TUG3 matrix ports that are in use. TUG3 matrix ports are the number of VC4s that are dropped to lower order paths (using TUG3s to hold VC3s and TUG2s) shown in VC4 size. 384 TUG3 matrix ports are available.

TUG3 Matrix-Provides the percent of TUG3 matrix resources that are in use. 384 TUG3 paths are available.

VC12 Matrix Ports-Provides the percent of VC12 matrix ports that are in use. VC12 matrix ports are the number of TUG3s used to support TUG2s (that is, VC11s and VC12s). 96 VC12 matrix ports are available.

VC12 Matrix-Provides the percent of VC12 matrix resources that are in use. 2016 VC12 paths are available.

VC11 Matrix Ports-(XC-VXC-10G card only) Provides the percent of VC11 matrix ports that are in use. VC11 matrix ports are the number of TUG3s used to support TUG2s (that is, VC11s and VC12s). 96 VC11 matrix ports are available.

VC11 Matrix-(XC-VXC-10G card only) Provides the percent of VC11 matrix resources that are in use. 2688 VC11 paths are available.

Tunnel Name-If the port is used by a tunnel, the tunnel name appears here.

% Used-Shows the percent of the matrix port that is used.

Usage-Shows the port usage.

As needed, you can perform the following actions:

Click Refresh to update the view. For example, if other users create circuits while you view the Resource Usage tab, click Refresh to see the effect that those circuits have on matrix usage.

Click Delete to delete VC12s, VC11s, or VC3s that use matrix resources but no longer carry circuits. This occasionally occurs when many circuits are added and deleted over a period of time. Stranded VC12s, VC11s, or VC3s appear with 0 percent usage in the TUG3 Matrix Port Detail area. If stranded VC12s, VC11s, or VC3s appear, click the VC, then click Delete to free matrix capacity.

Note: The Delete button requires a Superuser security level.

Stop. You have completed this procedure.

NTP-D287 Modify and Delete Circuits

Purpose

This procedure edits or changes the properties of ONS 15454 SDH circuits and deletes circuits.

Note: For unidirectional circuits, create a drop to the port where the test equipment is attached.

Complete the "DLP-D60 Log into CTC" task at a node on the network where you will create the monitor circuit. If you are already logged in, continue with Step 2.

From the View menu, choose Go to Network View.

Click the Circuits tab.

Choose the bidirectional (two-way) circuit that you want to monitor and double-click it (or click Edit).

Verify that the circuit name is no longer than 44 characters. Monitor circuits append a "_MON" to the circuit name. If the name is longer than 44 characters, edit the name in the Name field, then click Apply.

In the Edit Circuit window, click the Monitors tab.

The Monitors tab provides ports that you can use to monitor the circuit. The Monitor tab is only available when the circuit has a DISCOVERED status.

In the Monitors tab, choose the monitor source port. The monitor circuit will show traffic coming into the node at the port you choose.

Click Create Monitor Circuit.

In the Circuit Destination section of the Circuit Creation wizard, choose the destination node, slot, port, and if applicable, VC for the monitored circuit.

Note: In Figure 7-1, the monitor circuit destination is Port 2 on the STM-1 card.

From the File menu in the Edit Circuit window, click Close. The new monitor circuit appears on the Circuits tab.

Figure 7-1 shows an example of a monitor circuit. At Node 1, a VC4 is dropped from Port 1 of an STM-1 card. To monitor the VC4 traffic, test equipment is plugged into Port 2 of the STM-1 card and a monitor circuit to Port 2 is provisioned in Cisco Transport Controller (CTC). Circuit monitors are one-way. The monitor circuit in Figure 7-1 is used to monitor VC4 traffic received by Port 1 of the STM-1 card.

Figure 7-1: VC4 Monitor Circuit Received at an STM-1 Port

Stop. You have completed this procedure.

NTP-D329 Create a J0 Section Trace

Purpose

This procedure creates a repeated, fixed-length string of characters used to monitor interruptions or changes to traffic between nodes.

Tools/Equipment

At least one card of the following cards must be installed: MRC-2.5G-12, MRC-12 or STM64-XFP.

Prerequisite Procedures

None

Required/As Needed

As needed (optional if path trace is set)

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Complete the "DLP-D60 Log into CTC" task at a node on the network where you will create the section trace. If you are already logged in, continue with Step 2.

Auto-The first string received from the source port is automatically provisioned as the current expected string. An alarm is raised when a string that differs from the baseline is received.

Manual-The string entered in the Current Expected String field is the baseline. An alarm is raised when a string that differs from the Current Expected String is received.

In the Section Trace String Size area, click 1 byte, 16 byte, or 64 byte. In the New Transmit String field, enter the string that you want to transmit. Enter a string that makes the destination port easy to identify, such as the node IP address, node name, or another string. If the New Transmit String field is left blank, the J0 transmits a string of null characters.

If you set the Section Trace Mode field to Manual, enter the string that the destination port should receive from the source port in the New Expected String field. If you set Section Trace Mode to Auto, skip this step.

Click the Disable AIS and RDI if TIM-P is detected check box if you want to suppress the alarm indication signal (AIS) and remote defect indication (RDI) when the STS Section Trace Identifier Mismatch Path (TIM-P) alarm appears. Refer to the Cisco ONS 15454 SDH Troubleshooting Guide for descriptions of alarms and conditions.

Click Apply.

After you set up the section trace, the received string appears in the Received field. The following options are available:

Click Hex Mode to display section trace in hexadecimal format. The button name changes to ASCII Mode. Click it to return the section trace to ASCII format.

Click the Reset button to reread values from the port.

Click Default to return to the section trace default settings (Section Trace Mode is set to Off and the New Transmit and New Expected Strings are null).

Caution! Clicking Default will generate alarms if the port on the other end is provisioned with a different string.

The expect and receive strings are updated every few seconds if the Section Trace Mode field is set to Auto or Manual.

Stop. You have completed this procedure.

NTP-D79 Create a J1 or J2 Path Trace

Purpose

This procedure creates a repeated, fixed-length string of characters used to monitor changes to circuit traffic.

Tools/Equipment

ONS 15454 SDH cards capable of transmitting and/or receiving path trace must be installed. See Table 19-5 for a list of J1 path trace cards. See Table 20-26 for a list of J2 path trace cards.

Note: There are two types of J1 bytes, high-order (HO-J1) and low-order (LO-J1). The electrical cards support LO-J1 (VC3). The optical cards support HO-J1 (VC4) and cannot monitor the LO-J1 byte. In addition, the E1-42 card supports HO-J1 when the card is provisioned as an HO circuit endpoint.

Note: J1 path trace is available for VC3 and VC4 circuits. In ONS 15454 SDH Software R3.4 and earlier, you can set the VC3 J1 transmit string on E3 and DS3i-N-12 cards, but VC3 is not monitored by STM-N cards. J2 path trace is available for VC12 circuits.

Complete the "DLP-D60 Log into CTC" task at a node on the network where you will create the path trace. If you are already logged in, continue with Step 2.

NTP-D332 Bridge and Roll Traffic

Purpose

This procedure reroutes live traffic without interrupting service. You can use the Bridge and Roll wizard for maintenance functions such as card replacement or load balancing. A circuit consists of a source facility, one or more destination facilities, and intermediate facilities (path).

Use the NTP-D199 Locate and View Circuits to verify that the planned Roll To paths are in service. Verify that the planned Roll To and Roll From paths are not in the Roll Pending status, used in test access, or used in a loopback. Refer to the Cisco ONS 15454 SDH Troubleshooting Guide to clear any alarms.

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Note: Using the bridge and roll feature, you can upgrade an unprotected circuit to a fully protected circuit or downgrade a fully protected circuit to an unprotected circuit.

Caution! Performing bridge and roll on an STM64C might cause a traffic hit of 50 ms.

Complete the "DLP-D60 Log into CTC" task at the ONS 15454 SDH circuit source node. If you are already logged in, continue with Step 2.

As needed, complete the "DLP-D239 Delete a Roll" task. Use caution when selecting this option. Delete a roll only if it cannot be completed or canceled. Circuits might have a PARTIAL status when this option is selected.

Stop. You have completed this procedure.

NTP-D309 Reconfigure Circuits

Purpose

This procedure rebuilds circuits, which might be necessary when a large number of circuits are in the PARTIAL status.

NTP-D310 Merge Circuits

Purpose

This procedure merges two circuits that create a single, contiguous path but are separate circuits because of different circuit IDs or conflicting parameters. A merge combines a single master circuit with one or more circuits.