Cisco ONS 15327 Procedure Guide, Release 7.0
Chapter 17, DLPs B100 to B199
Downloads: This chapterpdf (PDF - 1.25MB) The complete bookPDF (PDF - 11.08MB) | Feedback

DLPs B100 to B199

Table Of Contents

DLPs B100 to B199

DLP-B100 Roll the Source or Destination of One Optical Circuit

DLP-B101 Roll One Cross-Connect from an Optical Circuit to a Second Optical Circuit

DLP-B102 Roll Two Cross-Connects on One Optical Circuit Using Automatic Routing

DLP-B103 Roll Two Cross-Connects on One Optical Circuit Using Manual Routing

DLP-B104 Roll Two Cross-Connects from One Optical Circuit to a Second Optical Circuit

DLP-B105 Delete a Roll

DLP-B106 Cancel a Roll

DLP-B107 Adjust the Java Virtual Memory Heap Size

DLP-B110 View Alarm History

DLP-B111 Changing the Maximum Number of Session Entries for Alarm History

DLP-B112 Display Alarms and Conditions Using Time Zone

DLP-B113 Synchronize Alarms

DLP-B114 View Conditions

DLP-B115 Create a Cloned Alarm Severity Profile

DLP-B116 Apply Alarm Profiles to Ports

DLP-B117 Apply Alarm Profiles to Cards and Nodes

DLP-B118 Delete Alarm Severity Profiles

DLP-B119 Suppress Alarm Reporting

DLP-B120 Discontinue Alarm Suppression

DLP-B121 Enable Pointer Justification Count Performance Monitoring

DLP-B122 Enable Intermediate-Path Performance Monitoring

DLP-B123 View Electrical PM Parameters

DLP-B124 Refresh Electrical or Optical PM Counts at Fifteen-Minute Intervals

DLP-B126 Monitor Near-End PM Counts

DLP-B127 Monitor Far-End PM Counts

DLP-B129 Reset Current PM Counts

DLP-B130 Clear Selected PM Counts

DLP-B131 Search for Circuits

DLP-B137 Provision Path Trace on OC-N Ports

DLP-B140 Change the Node Name, Date, Time, and Contact Information

DLP-B142 Modify a Static Route

DLP-B143 Delete a Static Route

DLP-B144 Disable the Open Shortest Path First Protocol

DLP-B145 Change the Network View Background Color

DLP-B148 Create Domain Icons

DLP-B149 Manage Domain Icons

DLP-B154 Modify a 1+1 Protection Group

DLP-B155 Delete a 1+1 Protection Group

DLP-B157 Change the Node Timing Source

DLP-B158 Change User Password and Security Settings on a Single Node

DLP-B159 Delete a User on a Single Node

DLP-B160 Change User Password and Security Settings on Multiple Nodes

DLP-B161 Delete a User on Multiple Nodes

DLP-B163 Delete SNMP Trap Destinations

DLP-B165 Change Line and Threshold Settings for the DS-1 Ports

DLP-B166 Change Line and Threshold Settings for the DS-3 Ports

DLP-B170 Change Line Settings for OC-N Cards

DLP-B171 Change SONET Threshold Settings for OC-N Cards

DLP-B172 Change an Optical Port to SDH

DLP-B173 Provision OSI Routing Mode

DLP-B174 Provision or Modify TARP Operating Parameters

DLP-B175 Add a Static TID to NSAP Entry to the TARP Data Cache

DLP-B176 Remove a Static TID to NSAP Entry from the TARP Data Cache

DLP-B177 Add a TARP Manual Adjacency Table Entry

DLP-B178 Provision OSI Routers

DLP-B179 Provision Additional Manual Area Addresses

DLP-B180 Enable the OSI Subnet on the LAN Interface

DLP-B181 Create an IP-Over-CLNS Tunnel

DLP-B182 Remove a TARP Manual Adjacency Table Entry

DLP-B183 Change the OSI Routing Mode

DLP-B184 Edit the OSI Router Configuration

DLP-B185 Edit the OSI Subnetwork Point of Attachment

DLP-B186 Edit an IP-Over-CLNS Tunnel

DLP-B187 Delete an IP-Over-CLNS Tunnel

DLP-B188 View IS-IS Routing Information Base

DLP-B189 Verify That a 1+1 Working Slot Is Active

DLP-B190 View ES-IS Routing Information Base

DLP-B191 Manage the TARP Data Cache

DLP-B194 Clear a BLSR Force Ring Switch

DLP-B195 Verify Timing in a Reduced Ring

DLP-B196 Delete a BLSR from a Single Node

DLP-B197 Initiate a Path Protection Force Switch

DLP-B198 Clear a Path Protection Switch

DLP-B199 Inspect, Clean, and Replace the Reusable Air Filter


DLPs B100 to B199



Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.


DLP-B100 Roll the Source or Destination of One Optical Circuit

Purpose

This task reroutes traffic from one source or destination to another on the same circuit, thus changing the original source or destination.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 From the View menu, choose Go To Network View.

Step 2 Click the Circuits tab.

Step 3 Click the circuit that you want to roll. The circuit must have a DISCOVERED status for you to start a roll.

Step 4 From the Tools menu, choose Circuits > Roll Circuit.

Step 5 In the Roll Attributes area, complete the following (Figure 17-1):

a. From the Circuit Roll Mode drop-down list, choose Auto to create an automatic roll (required for a 1-way source roll) or Manual to create a manual roll (required for a 1-way destination roll).

b. From the Circuit Roll Type drop-down list, choose Single to indicate that you want to roll one cross-connect on the chosen circuit.

Figure 17-1 Selecting Single Roll Attributes

Step 6 Click Next.

Step 7 In the Pivot/Fixed Point 1 window, click the square in the graphic image that represents the facility that you want to keep.

This facility is the fixed location in the cross-connect involved in the roll process. The identifier appears in the text box below the graphic image. The facility that is not selected is the Roll From path. The Roll From path is deleted after the roll is completed.

Step 8 Click Next.

Step 9 In the Select New End Point area, choose the Slot, Port, and STS from the drop-down lists to select the Roll To facility (Figure 17-2).

Figure 17-2 Selecting a New Endpoint

Step 10 Click Finish. On the Circuits tab, the circuit status for the Roll From port changes from DISCOVERED to ROLL_PENDING.

Step 11 Click the Rolls tab (Figure 17-3). For the pending roll, view the Roll Valid Signal status. When one of the following conditions are met, continue with Step 12.

If the Roll Valid Signal status is true, a valid signal was found on the new port.

If the Roll Valid Signal status is false, a valid signal was not found. Wait until the signal is found before continuing with the next step. To cancel the roll, see the "DLP-B106 Cancel a Roll" task.

The roll is a one-way destination roll and the Roll Valid Signal is false. It is not possible to get a Roll Valid Signal status of true for a one-way destination roll.


Note You cannot cancel an automatic roll after a valid signal is found.


You can force a signal onto the Roll To circuit by using the Force Valid Signal button. If you choose Force Valid Signal, traffic on the circuit that is involved in the roll might drop depending on conditions at the other end of the circuit when the roll is completed. You must force a signal if the circuits do not have a signal or have a bad signal and you want to complete the roll.


Note For a one-way destination roll in manual mode, you do not need to force the valid signal.


Figure 17-3 Viewing the Rolls Tab

Step 12 If you selected Manual in Step 5, click the rolled facility on the Rolls tab and then click Complete. If you selected Auto, continue with Step 13.

Step 13 For both Manual and Auto rolls, click Finish to complete the circuit roll process. The roll clears from the Rolls tab and the rolled circuit now appears on the Circuits tab in the DISCOVERED status.

Step 14 Return to your originating procedure (NTP).


DLP-B101 Roll One Cross-Connect from an Optical Circuit to a Second Optical Circuit

Purpose

This task reroutes a cross-connect on one circuit onto another circuit resulting in a new destination.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B253 Provision Section DCC Terminations for the ports involved in the roll

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 From the View menu, choose Go To Network View.

Step 2 Click the Circuits tab.

Step 3 Press Ctrl and click the two circuits that you want to use in the roll process.

The circuits must have a DISCOVERED status; in addition, they must be the same size and direction for you to start a roll. The planned Roll To circuit must not carry traffic.The Roll To facility should be DCC connected to the source node of the Roll To circuit.

Step 4 From the Tools menu, choose Circuits > Roll Circuit.

Step 5 In the Roll Attributes area, complete the following (Figure 17-4):

a. From the Circuit Roll Mode drop-down list, choose Auto to create an automatic roll (required for a 1-way source roll) or Manual to create a manual roll (required for 1-way destination roll).

b. From the Circuit Roll Type drop-down list, choose Single to indicate that you want to roll a single connection from the Roll From circuit to the Roll To circuit.

c. In the Roll From Circuit area, click the circuit that contains the Roll From connection.

Figure 17-4 Selecting Roll Attributes for a Single Roll onto a Second Circuit

Step 6 Click Next.

Step 7 In the Pivot/Fixed Point 1 window, click the square representing the facility that you want to keep.

This facility is the fixed location in the cross-connect involved in the roll process. The identifier appears in the text box below the graphic image. The facility that is not selected is the Roll From path. The Roll From path is deleted after the roll is completed.

Step 8 Click Next.

Step 9 In the Select New End Point area, choose the Slot, Port, and STS from the drop-down lists to identify the Roll To facility on the connection being rolled.

Step 10 Click Finish.

The statuses of the Roll From and Roll To circuits change from DISCOVERED to ROLL_PENDING in the Circuits tab.

Step 11 Click the Rolls tab. For the pending roll, view the Roll Valid Signal status. When one of the following conditions are met, continue with Step 12.

If the Roll Valid Signal status is true, a valid signal was found on the new port.

If the Roll Valid Signal status is false, a valid signal was not found. Wait until the signal is found before continuing with the next step. To cancel the roll, see the "DLP-B106 Cancel a Roll" task.

The roll is a one-way destination roll and the Roll Valid Signal is false. It is not possible to get a "true" Roll Valid Signal status for a one-way destination roll.


Note You cannot cancel an automatic roll after a valid signal is found.


A roll can be forced onto the Roll To Circuit destination without a valid signal by using the Force Valid Signal button. If you choose Force Valid Signal, traffic on the circuit that is involved in the roll will be dropped once the roll is completed.

Step 12 If you selected Manual in Step 5, click the roll on the Rolls tab and click Complete to route the traffic to the new port. If you selected Auto, continue with Step 13.

Step 13 For both manual and automatic rolls, click Finish to complete the circuit roll process.

The roll is cleared from the Rolls tab and the new rolled circuit on Circuits tab returns to the DISCOVERED status.

Step 14 Return to your originating procedure (NTP).


DLP-B102 Roll Two Cross-Connects on One Optical Circuit Using Automatic Routing

Purpose

This task reroutes the network path while maintaining the same source and destination. This task allows CTC to automatically select a Roll To path.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 From the View menu, choose Go To Network View.

Step 2 Click the Circuits tab.

Step 3 Click the circuit that has the connections that you want to roll. The circuit must have a DISCOVERED status for you to start a roll.

Step 4 From the Tools menu, choose Circuits > Roll Circuit.

Step 5 In the Roll Attributes area, complete the following (Figure 17-5):

a. From the Circuit Roll Mode drop-down list, choose Auto to create an automatic roll or Manual to create a manual roll.

b. From the Circuit Type drop-down list, choose Dual to indicate that you want to roll two connections on the chosen circuit.

Figure 17-5 Selecting Dual Roll Attributes

Step 6 Click Next.

Step 7 In the Pivot/Fixed Point 1 window, click the square representing the fixed path of the first connection to be rolled.

This path is a fixed point in the cross connection involved in the roll process. The path identifier appears in the text box below the graphic image. The path that is not selected contains the Roll From path. The Roll From path is deleted after the roll is completed.

Step 8 Click Next.

Step 9 Complete one of the following:

If multiple Roll From paths exist, the Select Roll From dialog box appears. Select the path from which you want to roll traffic and click OK.

If multiple Roll From paths do not exist, continue with Step 10. The circuit status for the Roll To path changes states from DISCOVERED to ROLL_PENDING.

Step 10 In the Pivot/Fixed Point 2 window, click the square that represents the fixed path of the second connection to be rolled.

The path that is not selected is the Roll From path. The Roll From path is deleted after the roll is completed. The path identifier appears in the text box below the graphic image.

Step 11 Click Next.

Step 12 In the Circuit Routing Preferences area, check Route Automatically to allow CTC to find the route. If you check Route Automatically, the following options are available:

Using Required Nodes/Spans—If checked, you can specify nodes and spans to include or exclude in the CTC-generated circuit route in Step 15.

Review Route Before Creation—If checked, you can review and edit the circuit route before the circuit is created.

Step 13 To route the circuit over a protected path, check Fully Protected Path. (If you do not want to route the circuit on a protected path, continue with Step 14.) CTC creates a primary and alternate circuit route (virtual path protection) based on the following nodal diversity options. Select one of the following choices and follow subsequent window prompts to complete the routing:

Nodal Diversity Required—Ensures that the primary and alternate paths within path-protected mesh network (PPMN) portions of the complete circuit path are nodally diverse.

Nodal Diversity Desired—Specifies that node diversity should be attempted, but if node diversity is not possible, CTC creates link diverse paths for the PPMN portion of the complete circuit path.

Link Diversity Only—Specifies that only link-diverse primary and alternate paths for PPMN portions of the complete circuit path are needed. The paths might be node-diverse, but CTC does not check for node diversity.

Step 14 If you checked Route Automatically in Step 12:

If you checked Using Required Nodes/Spans, continue with Step 15.

If you checked only Review Route Before Creation, continue with Step 16.

If you did not check Using Required Nodes/Spans or Review Route Before Creation, continue with Step 17.

Step 15 If you checked Using Required Nodes/Spans in Step 12:

a. In the Roll Route Constraints area, click a node or span on the circuit map.

b. Click Include to include the node or span in the circuit. Click Exclude to exclude the node/span from the circuit. The order in which you select included nodes and spans sets the circuit sequence. Click spans twice to change the circuit direction.

c. Repeat Step b for each node or span you wish to include or exclude.

d. Review the circuit route. To change the circuit routing order, select a node in the Required Nodes/Lines or Excluded Nodes Links lists, then click the Up or Down buttons to change the circuit routing order. Click Remove to remove a node or span.

Step 16 If you checked Review Route Before Creation in Step 12:

a. In the Roll Route Review and Edit area, review the circuit route. To add or delete a circuit span, select a node on the circuit route. Blue arrows show the circuit route. Green arrows indicate spans that you can add. Click a span arrowhead, then click Include to include the span or Remove to remove the span.

b. If the provisioned circuit does not reflect the routing and configuration you want, click Back to verify and change circuit information.


Caution The following is only seen with DUAL roll mode when both ends of the circuit use the port mentioned in this statement. If the termination port is the XTC's DS1 port, a roll will occur even if a valid signal is not detected on the Roll To port. The absence of PDI-P downstream for LOS, LOF, and AIS line defects causes the roll to continue without a valid signal. On the XTC's DS1 port it is possible to check the Send AIS-V For Ds1 AIS check box to properly generate PDI-P downstream for the LOS and LOF AIS line defects. This check box is selected from the card view, Provisioning > Line tabs. On the XTC's DS1 port, Send AIS-V for Ds1 AIS only works for VT circuits.

Step 17 Click Finish.

In the Circuits tab, verify that a new circuit appears. This circuit is the Roll To circuit. It is designated with the Roll From circuit name appended with ROLL**.

Step 18 Click the Rolls tab. Two new rolls now appear. For each pending roll, view the Roll Valid Signal status. When one of the following requirements is met, continue with Step 19.

If the Roll Valid Signal status is true, a valid signal was found on the new port.

If the Roll Valid Signal status is false, a valid signal was not found. Wait until the signal is found before continuing with the next step. If a valid signal is not found, refer to the Cisco ONS 15327 Troubleshooting Guide. To cancel the roll, see the "DLP-B106 Cancel a Roll" task.

The roll is a one-way destination roll and the Roll Valid signal status is false. It is not possible to get a Roll Valid Signal status of true for a one-way destination roll.


Note If you have completed a roll, you cannot cancel the sibling roll. You must cancel the two rolls together.



Note You cannot cancel an automatic roll after a valid signal is found.


A roll can be forced onto the Roll To Circuit destination without a valid signal by using the Force Valid Signal button. If you choose Force Valid Signal, traffic on the circuit that is involved in the roll will be dropped once the roll is completed.

Step 19 If you selected Manual in Step 5, click both rolls on the Rolls tab and click Complete to route the traffic to the new port. If you selected Auto, continue with Step 20.


Note You cannot complete a roll if you cancelled the sibling roll. You must complete the two rolls together.


Step 20 For both manual and automatic rolls, click Finish to complete circuit roll process.

Step 21 Return to your originating procedure (NTP).


DLP-B103 Roll Two Cross-Connects on One Optical Circuit Using Manual Routing

Purpose

This task reroutes a network path of an optical circuit using manual routing.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning and higher



Step 1 From the View menu, choose Go To Network View.

Step 2 Click the Circuits tab.

Step 3 Click the circuit that you want to roll to a new path. The circuit must have a DISCOVERED status for you to start a roll.

Step 4 From the Tools menu, choose Circuits > Roll Circuit.

Step 5 In the Roll Attributes area, complete the following (Figure 17-5):

a. From the Circuit Roll Mode drop-down list, choose Auto to create an automatic roll or Manual to create a manual roll.

b. From the Circuit Type drop-down list, choose Dual to indicate that you want to roll two connections on the chosen circuit.

Step 6 Click Next.

Step 7 In the Pivot/Fixed Point 1 window, click the square representing the fixed path of the first cross-connect to be rolled.

This path is a fixed point in the cross-connect involved in the roll process. The path identifier appears in the text box below the graphic image. The path that is not selected contains the Roll From path. The Roll From path is deleted after the roll is completed.

Step 8 Click Next.

Step 9 Complete one of the following:

If multiple Roll From paths exist, the Select Roll From dialog box appears. Select the path from which you want to roll traffic and click OK, then click Next.

If multiple Roll From paths do not exist, click Next and continue with Step 10. The circuit status for the Roll From path changes from DISCOVERED to ROLL_PENDING.

Step 10 In the Pivot/Fixed Point 2 window, click the square that represents the fixed path of the second connection to be rolled.

The path that is not selected is the Roll From path. The Roll From path is deleted after the roll is complete. The path identifier appears in the text box below the graphic image.

Step 11 Click Next.

Step 12 In the Circuit Routing Preferences area, uncheck Route Automatically.

Step 13 Set the circuit path protection:

To route the circuit on a protected path, leave Fully Protected Path checked and continue with Step 14.

To create an unprotected circuit, uncheck Fully Protected Path and continue with Step 15.

Step 14 If you checked Fully Protected Path, choose one of the following:

Nodal Diversity Required—Ensures that the primary and alternate paths within the path protection portions of the complete circuit path are nodally diverse.

Nodal Diversity Desired—Specifies that node diversity is preferred, but if node diversity is not possible, CTC creates fiber-diverse paths for the path protection portion of the complete circuit path.

Link Diversity Only—Specifies that only fiber-diverse primary and alternate paths for path protection portions of the complete circuit path are needed. The paths might be node-diverse, but CTC does not check for node diversity.

Step 15 Click Next. Beneath Route Review and Edit, node icons appear for you to route the circuit manually.

The green arrows pointing from the source node to other network nodes indicate spans that are available for routing the circuit.

Step 16 Complete the "DLP-B98 Provision an OC-N Circuit Route" task.


Caution The following is only seen with DUAL roll mode when both ends of the circuit use the port mentioned in this statement. If the termination port is the XTC's DS1 port, a roll will occur even if a valid signal is not detected on the Roll To port. The absence of PDI-P downstream for LOS, LOF, and AIS line defects causes the roll to continue without a valid signal. On the XTC's DS1 port it is possible to check the Send AIS-V For Ds1 AIS check box to properly generate PDI-P downstream for the LOS and LOF AIS line defects. This check box is selected from the card view, Provisioning > Line tabs. On the XTC's DS1 port, Send AIS-V for Ds1 AIS only works for VT circuits.

Step 17 Click Finish. In the Circuits tab, verify that a new circuit appears.

This circuit is the Roll To circuit. It is designated with the Roll From circuit name appended with ROLL**.

Step 18 Click the Rolls tab. Two new rolls now appear on the Rolls tab. For each pending roll, view the Roll Valid Signal status. When one of the following conditions are met, continue with Step 19.

If the Roll Valid Signal status is true, a valid signal was found on the new port.

If the Roll Valid Signal status is false, a valid signal was not found. Wait until the signal is found before continuing with the next step. To cancel the roll, see the "DLP-B106 Cancel a Roll" task.

The roll is a one-way destination roll and the Roll Valid signal status is false. It is not possible to get a Roll Valid Signal status of true for a one-way destination roll.


Note You cannot cancel an automatic roll after a valid signal is found.


A roll can be forced onto the Roll To Circuit destination without a valid signal by using the Force Valid Signal button. If you choose Force Valid Signal, traffic on the circuit that is involved in the roll will be dropped once the roll is completed.

Step 19 If you selected Manual in Step 5, click each roll and click Complete to route the traffic to the new port. If you selected Auto, continue with Step 20.


Note You cannot complete a roll if you cancelled the sibling roll. You must complete the two rolls together.


Step 20 For both manual and automatic rolls, click Finish to complete the circuit roll process.

Step 21 Return to your originating procedure (NTP).


DLP-B104 Roll Two Cross-Connects from One Optical Circuit to a Second Optical Circuit

Purpose

This task reroutes a network path using two optical circuits by allowing CTC to select the Roll To path on the second circuit automatically.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning and higher



Step 1 From the View menu, choose Go To Network View.

Step 2 Click the Circuits tab.

Step 3 Press Ctrl and click the two circuits that you want to use in the roll process.

The Roll From path will be on one circuit and the Roll To path will be on the other circuit. The circuits must have a DISCOVERED status and must be the same size and direction for you to start a roll. The planned Roll To circuit must not carry traffic.The first Roll To path must be DCC connected to the source node of the Roll To circuit, and the second Roll To path must be DCC connected to the destination node of the Roll To circuit.

Step 4 From the Tools menu, choose Circuits > Roll Circuit.

Step 5 In the Roll Attributes area, complete the following:

a. From the Circuit Roll Mode drop-down list, choose Auto to create an automatic roll (required for a 1-way source roll) or Manual to create a manual roll (required for 1-way destination roll).

b. From the Circuit Roll Type drop-down list, choose Dual.

c. In the Roll From Circuit area, click the circuit that contains the Roll From path.

Step 6 Click Next.

Step 7 In the Pivot/Fixed Point 1 window, click the square representing the fixed path of the first cross-connect to be rolled.

This path is a fixed point in the cross-connect involved in the roll process. The path identifier appears in the text box below the graphic image. The path that is not selected contains the Roll From path. The Roll From path is deleted after the roll is completed.

Step 8 Click Next.

Step 9 Complete one of the following:

If multiple Roll From paths exist, the Select Roll From dialog box appears. Select the path from which you want to roll traffic and click OK.

If multiple Roll From paths do not exist, continue with Step 10.

The circuit status for the Roll From path changes from DISCOVERED to ROLL PENDING.

Step 10 In the Pivot/Fixed Point 2 window, click the square that represents the fixed path of the second connection to be rolled.

The path that is not selected is the Roll From path. The Roll From path is deleted after the roll is completed. The path identifier appears in the text box below the graphic image.

Step 11 Click Next.


Caution The following is only seen with DUAL roll mode when both ends of the circuit use the port mentioned in this statement. If the termination port is the XTC's DS1 port, a roll will occur even if a valid signal is not detected on the Roll To port. The absence of PDI-P downstream for LOS, LOF, and AIS line defects causes the roll to continue without a valid signal. On the XTC's DS1 port it is possible to check the Send AIS-V For Ds1 AIS check box to properly generate PDI-P downstream for the LOS and LOF AIS line defects. This check box is selected from the card view, Provisioning > Line tabs. On the XTC's DS1 port, Send AIS-V for Ds1 AIS only works for VT circuits.

Step 12 Click Finish. In the Circuits tab, the Roll From and Roll To circuits change from the DISCOVERED status to ROLL RENDING.

Step 13 Click the Rolls tab. Two new rolls now appear on the Rolls tab. For each pending roll, view the Roll Valid Signal status. When one of the following conditions are met, continue with Step 14.

If the Roll Valid Signal status is true, a valid signal was found on the new port.

If the Roll Valid Signal status is false, a valid signal was not found. Wait until the signal is found before continuing with the next step. To cancel the roll, see the "DLP-B106 Cancel a Roll" task.

The roll is a one-way destination roll and the Roll Valid signal status is false. It is not possible to get a Roll Valid Signal status of true for a one-way destination roll.


Note You cannot cancel an automatic roll after a valid signal is found.


A roll can be forced onto the Roll To Circuit destination without a valid signal by using the Force Valid Signal button. If you choose Force Valid Signal, traffic on the circuit that is involved in the roll will be dropped once the roll is completed.

Step 14 If you selected Manual in Step 5, click both rolls on the Rolls tab and click Complete to route the traffic to the new port. If you selected Auto, continue with Step 15.


Note You cannot complete a roll if you cancelled the sibling roll. You must complete the two rolls together.


Step 15 For both manual and automatic rolls, click Finish to complete the circuit roll process.

Step 16 Return to your originating procedure (NTP).


DLP-B105 Delete a Roll

Purpose

This task deletes a roll. Use caution when selecting this option, traffic may be affected. Delete a roll only if it cannot be completed or cancelled in normal ways. Circuits may have a PARTIAL status when this option is selected. See Table 19-7 for a description of circuit statuses.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B269 Bridge and Roll Traffic

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 From the View menu, choose Go To Network View.

Step 2 Click the Circuits > Rolls tabs.

Step 3 Click the rolled circuit that you want to delete.

Step 4 From the Tools menu, choose Circuits > Delete Rolls.

Step 5 In the confirmation dialog box, click Yes.

Step 6 Return to your originating procedure (NTP).


DLP-B106 Cancel a Roll

Purpose

This task cancels a roll. When the roll mode is Manual, you can only cancel a roll before you click the Complete button. When the roll mode is Auto, cancel roll is only allowed before a good signal is detected by the node or before clicking the Force Valid Signal button. A dual or single roll can be cancelled before the roll state changes to ROLL_COMPLETED.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B269 Bridge and Roll Traffic

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution If you click cancel while performing a Dual roll in Manual mode and have a valid signal detected on both rolls, you will see a dialog box stating that this can cause a traffic hit and asking if you want to continue with the cancellation. Cisco does not recommend cancelling a dual roll once a valid signal has been detected. To return the circuit to the original state, Cisco recommends completing the roll, then using bridge and roll again to roll the circuit back.


Step 1 From the Node or Network view, click the Circuits > Rolls tabs.

Step 2 Click the rolled circuit that you want to cancel.

Step 3 Click Cancel.

Step 4 Return to your originating procedure (NTP).


DLP-B107 Adjust the Java Virtual Memory Heap Size

Purpose

This task allows you to adjust the Java Virtual Memory (JVM) heap size from the default 256 MB to the maximum of 512 MB in order to improve CTC performance.

Tools/Equipment

None

Prerequisite procedures

None

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 Click Start > Settings > Control Panel. The Windows Control Panel appears.

Step 2 Double-click System. The System Properties window appears.

Step 3 Click the Advanced tab.

Step 4 Click Environmental Variables. The Environmental Variables window appears.

Step 5 In the User Variables area, click New. The New User Variable window appears.

Step 6 Type "CTC_HEAP" in the Variable Name field.

Step 7 Type "512" in the Variable Value field.

Step 8 Click OK.

Step 9 Reboot your PC.

Step 10 Return to your originating procedure (NTP).


DLP-B110 View Alarm History

Purpose

This task is used to view past cleared and uncleared ONS 15327 alarm messages at the card, node, or network level. This task is useful for troubleshooting configuration, traffic, or connectivity issues that are indicated by alarms.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve



Step 1 To view node alarm history, proceed to Step 2. To view network alarm history, proceed to Step 3. To view card alarm history, proceed to Step 4.

Step 2 To view node alarm history:

a. Click the History > Session tabs to view the alarms and conditions (events) raised during the current session.

b. Click the History > Shelf tabs to view the alarm and condition history for the node.

If you check the Alarms check box, the node's alarm history appears. If you check the Events check box, the node's Not Alarmed and transient event history appears. If you check both check boxes, you will retrieve node history for both alarms and events.

c. Click Retrieve to view all available messages for the History > Shelf tabs.


Note Alarms can be unreported when they are filtered out of the display using the Filter button in either tab. See the "DLP-B225 Enable Alarm Filtering" task for information.



Tip Double-click an alarm in the alarm table or an event (condition) message in the history table to display the view that corresponds to the alarm message. For example, double-clicking a card alarm takes you to card view. In network view, double-clicking a node alarm takes you to node view.


Step 3 To view network alarm history from node view:

a. From the View menu choose Go to Network View.

b. Click the History tab.

Alarms and conditions (events) raised during the current session appear.

Step 4 To view card alarm history from node view:

a. From the View menu choose Go to Previous View.

b. Double-click a card on the shelf graphic to display the card-level view.


Note Mechanical interface cards (MIC) do not have a card view.


c. Click the History > Session tab to view the alarm messages raised during the current session.

d. Click the History > Card tab to retrieve all available alarm messages for the card and click Retrieve.

If you check the Alarms check box, the node's alarm history appears. If you check the Events check box, the node's Not Alarmed and transient event history appears. If you check both check boxes, you will retrieve node history for both alarms and events.


Note The ONS 15327 can store up to 640 critical alarm messages, 640 major alarm messages, 640 minor alarm messages, and 640 condition messages. When any of these limits is reached, the ONS 15327 discards the oldest events in that category.


Raised and cleared alarm messages (and events, if selected) appear.

Step 5 Return to your originating procedure (NTP).


DLP-B111 Changing the Maximum Number of Session Entries for Alarm History

Purpose

This task changes the maximum number of session entries included in the alarm history. Use this task to extend the history list in order to save information for future reference or troubleshooting.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning



Step 1 From the Edit menu, choose Preferences.

The CTC Preferences Dialog box appears (Figure 17-6).

Figure 17-6 CTC Preferences Dialog Box

Step 2 Click the up or down arrow buttons next to the Maximum History Entries field to change the entry.

Step 3 Click Apply and OK.


Note Setting the Maximum History Entries value to the high end of the range uses more CTC memory and could impair CTC performance.



Note This task changes the maximum history entries recorded for CTC sessions. It does not affect the maximum number of history entries viewable for a network, node, or card.


Step 4 Return to your originating procedure (NTP).


DLP-B112 Display Alarms and Conditions Using Time Zone

Purpose

This task changes the timestamp for events to the timezone of the ONS 15327 node reporting the alarm. By default, the events timestamp is set to the timezone for the CTC workstation.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning



Step 1 From the Edit menu, choose Preferences.

The CTC Preferences Dialog box appears (Figure 17-6).

Step 2 Click the Display Events Using Each Node's Time Zone check box.

Step 3 Click Apply and OK.

Step 4 Return to your originating procedure (NTP).


DLP-B113 Synchronize Alarms

Purpose

This task is used to view ONS 15327 events at the card, node, or network level and to refresh the alarm listing so that you can check for new and cleared alarms and conditions.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve



Step 1 At the card, node, or network view, click the Alarms tab.

Step 2 Click Synchronize.

This button causes CTC to retrieve a current alarm summary for the card, node, or network. This step is optional because CTC updates the Alarms window automatically as messages arrive from the node.

Alarms that have been raised during the session will have a check mark in the Alarms window New column. When you click Synchronize, the check mark disappears.

Step 3 Return to your originating procedure (NTP).


DLP-B114 View Conditions

Purpose

This task is used to view conditions (events with a Not Reported [NR] severity) at the card, node, or network level. Conditions give you a clear record of changes or events that do not result in alarms.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve



Step 1 In the card, node, or network view, click the Conditions tab.

Step 2 Click Retrieve (Figure 17-7).

The Retrieve button requests the current set of fault conditions from the node, card, or network. The window is not updated when conditions change on the node. You must click Retrieve to see any changes.

Figure 17-7 Node View Conditions Window

Conditions include all fault conditions raised on the node, whether or not they are reported.


Note Alarms can be unreported when they are filtered out of the display. See the "DLP-B225 Enable Alarm Filtering" task for information.


Events that are reported as Major (MJ), Minor (MN), or Critical (CR) severities are alarms. Events that are reported as Not Alarmed (NA) are conditions. Conditions that are not reported at all are marked Not Reported (NR) in the Conditions window severity column.

Conditions that have a default severity of Critical (CR), Major (MJ), Minor (MN), or Not Alarmed (NA) but are not reported due to exclusion or suppression are shown as NR in the Conditions window.


Note For more information about alarm suppression, see the "DLP-B119 Suppress Alarm Reporting" task.


Current conditions are shown with the severity chosen in the alarm profile, if used. (For more information about alarm profiles, see the "NTP-B70 Create, Download, and Assign Alarm Severity Profiles" procedure.)


Note When a port is in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state, it raises an Alarms Suppressed for Maintenance (AS-MT) condition. For information about alarm and condition troubleshooting, refer to the Cisco ONS 15327  Troubleshooting Guide.



Note When a port is placed in the Out-of-Service and Autonomous, Auto In-Service (OOS-AU,AIS) service state but is not connected to a valid signal, it generates a loss of signal (LOS) alarm.


Step 3 If you want to apply exclusion rules, check the Exclude Same Root Cause check box at the node or network view, but do not check the Exclude Same Root Cause check box in card view.

An exclusion rule eliminates all lower-level alarms or conditions that originate from the same cause. For example, a fiber break might cause a LOS alarm, an alarm indication signal (AIS) condition, and a signal fail (SF) condition. If you check the Exclude Same Root Cause check box, only the LOS alarm will appear. According to Telcordia, exclusion rules apply to a query of "all conditions from a node."

Step 4 Return to your originating procedure (NTP).


DLP-B115 Create a Cloned Alarm Severity Profile

Purpose

This task creates a custom severity profile or clones and modifies the default severity profile.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 To access the alarm profile editor from network view, click the Provisioning > Alarm Profiles tabs. Figure 17-7 shows the network view.

Step 2 To access the profile editor from node or card view, click the Provisioning > Alarm Profiles > Alarm Profile Editor tabs.

Step 3 If you want to create a profile using an existing profile located on the node, click Load and From Node in the Load Profile(s) dialog box. Complete the following steps:

a. Click the node name you are logged into in the Node Names list.

b. Click the name of an existing profile in the Profile Names list, such as Default. Then go to Step 5.

Step 4 If you want to create a profile using an existing profile located in a file that is stored locally or on a network drive, click From File in the Load Profile(s) dialog box and complete the following steps:

a. Click Browse.

b. Navigate to the file location in the Open dialog box.

c. Click Open.


Note All default or user-defined severity settings that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations as defined in Telcordia GR-474.


Step 5 Click OK.

The alarm severity profile appears in the Alarm Profiles window.

Step 6 Right-click anywhere in the profile column to display the profile editing shortcut menu. (See Step 9 for further information about the Default profile.)

Step 7 Click Clone in the shortcut menu.


Tip To see the full list of profiles, including those available for loading or cloning, click Available. You must load a profile before you can clone it.


Step 8 In the New Profile or Clone Profile dialog box, enter a name in the New Profile Name field.

Profile names must be unique. If you try to import or name a profile that has the same name as another profile, CTC adds a suffix to create a new name. Long file names are supported.

Step 9 Click OK.

A new alarm profile (named in Step 8) is created. This profile duplicates the default profile severities and appears at the right of the previous profile column in the Alarm Profiles window. You can select it and drag it to a different position.


Note Up to 10 profiles, including the two reserved profiles, Inherited and Default, can be stored in CTC.


The Default profile sets severities to standard Telcordia GR-474-CORE settings. If an alarm has an Inherited profile, it inherits (copies) its severity from the same alarm's severity at the higher level. For example, if you choose the Inherited profile from the network view, the severities at the lower levels (node, card and port) will be copied from this selection. A card with an Inherited alarm profile copies the severities used by the node that contains the card. (If you are creating profiles, you can apply these separately at any level. To do this, see the "DLP-B117 Apply Alarm Profiles to Cards and Nodes" task.)

Step 10 Modify (customize) the new alarm profile by completing the following steps:

a. In the new alarm profile column, click the alarm severity you want to change in the custom profile.

b. Choose a severity from the drop-down list.

c. Repeat Steps a and b for each severity you want to customize. Refer to the following guidelines when you view the alarms or conditions after making modifications:

All Critical (CR) or Major (MJ) default or user-defined severity settings are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations as defined in Telcordia GR-474.

Default severities are used for all alarms and conditions until you create and apply a new profile.

Changing a severity to inherited (I) or unset (U) does not change the severity of the alarm.

Step 11 After you have customized the new alarm profile, right-click the profile column to highlight it.

Step 12 Click Store.

Step 13 In the Store Profile(s) dialog box, click To Node(s) and go to Step 14a or click To File and go to Step 14b (Figure 17-8).

Figure 17-8 Store Profile(s) Dialog Box

a. Choose the node(s) where you want to save the profile; then complete the following steps:

If you want to save the profile to only one node, click the node in the Node Names list.

If you want to save the profile to all nodes, click Select All.

If you do not want to save the profile to any nodes, click Select None.

If you want to update alarm profile information, click (Synchronize).

b. Save the profile by completing the following steps:

Click Browse and navigate to the profile save location.

Enter a name in the File name field.

Click Select to choose this name and location.Long file names are supported. CTC supplies a suffix of *.pfl to stored files.

Click OK to store the profile.

Step 14 As needed, perform any of the following actions:

Click the Hide Identical Rows check box to configure the Alarm Profiles window to display rows with dissimilar severities.

Click the Hide Reference Values check box to configure the Alarm Profiles window to display severities that do not match the Default profile.

Click the Only show service-affecting severities check box to configure the Alarm Profiles window not to display Minor and some Major alarms that will not affect service.

Step 15 Return to your originating procedure (NTP).


DLP-B116 Apply Alarm Profiles to Ports

Purpose

This task applies a custom or default alarm severity profile to a port or ports.

Tools/Equipment

None

Prerequisite Procedures

B115 Create a Cloned Alarm Severity Profile

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In the node view, double-click a card to display the card view.

To change alarm profiles for optical cards, proceed to Step 2. To apply alarm profiles to optical card ports, proceed to Step 3. To apply alarm profiles to electrical card ports, proceed to Step 4.


Note The card view is not available for the MIC-A or MIC-B cards.


Step 2 Click the Provisioning > Alarm Profiles > Alarm Profile Editor tabs.

An optical card view profile is shown in Figure 17-9. CTC shows Parent Card Profile: Inherited.

Figure 17-9 Optical Port Alarm Profile

Step 3 To apply profiles on a port basis:

a. In card view, click the port row in the Profile column.

b. Choose the new profile from the drop-down list.

c. Click Apply.

Step 4 To apply profiles to all ports on a card:

a. In card view, click the Force all ports to profile drop-down arrow at the bottom of the window.

b. Choose the new profile from the drop-down list.

c. Click Force (still need to "Apply").

d. Click Apply.

In node view, the Port Level Profiles column indicates port-level profiles with a notation such as "exist (1)" (Figure 17-10).

Step 5 To reapply a previous alarm profile after you have applied a new one, select the previous profile and click Apply again.

Step 6 Return to your originating procedure (NTP).


DLP-B117 Apply Alarm Profiles to Cards and Nodes

Purpose

This task applies a custom or default alarm profile to cards or nodes.

Tools/Equipment

None

Prerequisite Procedures

B115 Create a Cloned Alarm Severity Profile

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, click the Provisioning > Alarm Profiles > Alarm Profile Editor tabs (Figure 17-10).

Figure 17-10 Node View Alarm Profile

Step 2 To apply profiles to a card:

a. Click the Profile row for the card.

b. Choose the new profile from the drop-down list.

c. Click Apply.

Step 3 To apply the profile to an entire node:

a. Click the Node Profile drop-down arrow at the bottom of the window (Figure 17-10).

b. Choose the new alarm profile from the drop-down list.

c. Click Apply.

Step 4 To reapply a previous alarm profile after you have applied a new one, select the previous profile and click Apply again.

Step 5 Return to your originating procedure (NTP).


DLP-B118 Delete Alarm Severity Profiles

Purpose

This task deletes a custom or default alarm severity profile.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 From the View menu choose Go to Network View.

Step 2 To access the alarm profile editor from network view, click the Provisioning > Alarm Profiles tabs.

Step 3 To access the profile editor from node view, click the
Provisioning > Alarm Profiles > Alarm Profile Editor tabs.

Step 4 To access the profile editor from a card view, click the
Provisioning > Alarm Profiles > Alarm Profile Editor tabs.

Step 5 Click the profile you are deleting to select it.

Step 6 Click Delete.

The Select Node/Profile Combination for Delete dialog box appears (Figure 17-11).

Figure 17-11 Select Node/Profile Combination For Delete Dialog Box


Note You cannot delete the Inherited or Default alarm profiles.



Note A previously created alarm profile cannot be deleted unless it has been stored on the node. If the profile is visible on the Alarm Profiles tab but is not listed in the Select Node/Profile Combinations to Delete dialog box, continue with Step 11.


Step 7 Click the node name(s) in the Node Names list to highlight the profile location.


Tip If you hold the Shift key down, you can select consecutive node names. If you hold the Ctrl key down, you can select any combination of nodes.


Step 8 Click the profile name(s) you want to delete in the Profile Names list.

Step 9 Click OK.

Step 10 Click Yes in the Delete Alarm Profile dialog box.

If you delete a profile from a node, it still appears in the network view
Provisioning > Alarm Profile Editor window unless you remove it using the following step.

Step 11 To remove the alarm profile from the window, right-click the column of the profile you deleted and choose Remove from the shortcut menu.


Note If a node and profile combination is selected but does not exist, a warning appears: "One or more of the profile(s) selected do not exist on one or more of the node(s) selected." For example, if node A has only profile 1 stored and the user tries to delete both profile 1 and profile 2 from node A, this warning appears. However, the operation still removes profile 1 from node A.



Note The Default and Inherited special profiles cannot be deleted and do not appear in the Select Node/Profile Combination for Delete Window.


Step 12 Return to your originating procedure (NTP).


DLP-B119 Suppress Alarm Reporting

Purpose

This task suppresses the reporting of ONS 15327 alarms at the node, card, or port level.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution If multiple CTC/TL1 sessions are open, suppressing alarms in one session suppresses the alarms in all other open sessions.


Note Alarm suppression at the node level does not supersede alarm suppression at the card or port level. Suppression can exist independently for all three entities, and each entity will raise separate alarms suppressed by the user command (AS-CMD) alarm.



Step 1 If you are in node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs.

Step 2 To suppress alarms for the entire node:

a. Check the Suppress Alarms check box.

b. Click Apply.

All raised alarms for the node will change color to white in the Alarms window and their status will change to cleared. After suppressing alarms, clicking Synchronize in the Alarms window will remove cleared alarms from the window. However, an AS-CMD alarm will show in node or card view to indicate that node-level alarms were suppressed; this alarm will show System in the Object column.


Note The only way to suppress BITS, power source, or system alarms is to suppress alarms for the entire node. These cannot be suppressed separately, but the shelf backplane can be suppressed.


Step 3 To suppress alarms for individual cards:

a. Locate the card row (using the Location column for the slot number or the Eqpt Type column for the equipment name).

b. Check the Suppress Alarms column check box on that row (Figure 17-10).

Alarms that directly apply to this card will change appearance as described in Step 2. For example, if you suppressed raised alarms for an OC-48 card in Slot 4, raised alarms for this card will change in node or card view. The AS-CMD alarm will show the slot number in the Object number. For example, if you suppressed alarms for a Slot 4 OC-48 card, the AS-CMD object will be "SLOT-4."

Step 4 Click Apply.

Step 5 To suppress alarms for individual card ports double-click the card in node view.

Step 6 Click the Provisioning > Alarm Profiles > Alarm Behavior tabs.

Step 7 Check the Suppress Alarms column check box for the port row where you want to suppress alarms (Figure 17-9).

Step 8 Click Apply.

Alarms that apply directly to this port will change appearance as described in Step 2. (However, alarms raised on the entire card will remain raised.) A raised AS-CMD alarm that shows the port as its object will appear in either alarm window. For example, if you suppressed alarms for Port 1 on the Slot 16 OC-48 card, the alarm object will show "FAC-16-1."

Step 9 Return to your originating procedure (NTP).


DLP-B120 Discontinue Alarm Suppression

Purpose

This task discontinues alarm suppression and reenables alarm reporting on a port, card, or node.

Tools/Equipment

None

Prerequisite Procedures

B119 Suppress Alarm Reporting

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution If multiple CTC sessions are open, discontinuing suppression in one session will discontinue suppression in all other open sessions.


Step 1 To discontinue alarm suppression for the entire node:

a. In node view, click the Provisioning > Alarm Profiles > Alarm Behavior tab.

b. Uncheck the Suppress Alarms check box.

Suppressed alarms will reappear in the Alarms window. (They might have previously been cleared from the window using the Synchronize button.) The AS-CMD alarm with the system object will be cleared in all views.

Step 2 To discontinue alarm suppression for individual cards:

a. In the node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs.

b. Locate the card that was suppressed in the slot list.

c. Uncheck the Suppress Alarms column check box for that slot.

d. Click Apply.

Suppressed alarms will reappear in the Alarms window. (They might have previously been cleared from the window using the Synchronize button.) The AS-CMD alarm with the slot object (for example, SLOT-4) will be cleared in all views.

Step 3 Uncheck the Suppress Alarms check box for the port(s) you no longer want to suppress.

Step 4 Click Apply.

Suppressed alarms will reappear in the Alarms window. (They might have previously been cleared from the window using the Synchronize button.) The AS-CMD alarm with the port object (for example, FAC-16-1) will be cleared in all views.

Step 5 Return to your originating procedure (NTP).


DLP-B121 Enable Pointer Justification Count Performance Monitoring

Purpose

This task enables pointer justification counts, which provide a way to align the phase variations in STS and VT payloads and to monitor the clock synchronization between nodes. A consistent, large pointer justification count indicates clock synchronization problems between nodes.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, double-click the card where the line terminates (drops), called a line-terminating equipment (LTE) card. The card view appears.

Table 17-1 lists the Cisco ONS 15327 LTE cards.

Table 17-1 Traffic Cards that Terminate the Line (LTEs) 

Line Terminating Equipment

OC3 IR 1310

OC12 IR 1310

OC12 LR 1550

OC48 IR 1310

OC48 LR 1550


Step 2 Click the Provisioning > Line tabs.

Step 3 Click the PJStsMon# menu and make a selection based on the following rules:

The default value Off means pointer justification monitoring is disabled.

The values 1 to N are the number of STSs on the port. One STS per port can be enabled from the PJStsMon# card menu.

Figure 17-12 shows the PJStsMon# menu on the Provisioning window.

Figure 17-12 Line Tab for Enabling Pointer Justification Count Parameters

Step 4 In the Service State field, confirm that the port is in the In-Service and Normal (IS-NR) service state.

Step 5 If the port is IS-NR, click Apply and go to Step 7.

Step 6 If the port is in the OOS-MA,MT; OOS-AU,AINS; or Out-of-Service and Management, Disabled (OOS-MA,DSBLD) service state, choose IS from the Admin State drop-down list and click Apply.

Step 7 Click the Performance tab to view PM parameters. Figure 17-13 shows pointer justification counts. Refer to the "Performance Monitoring" chapter in the Cisco ONS 15327 Reference Manual for more PM information, details, and definitions.


Note In CTC, the count fields for PPJC and NPJC PM parameters appear white and blank unless they are enabled on the Provisioning > Line tabs.


Figure 17-13 Viewing Pointer Justification Counts

Step 8 Return to your originating procedure (NTP).


DLP-B122 Enable Intermediate-Path Performance Monitoring

Purpose

This task enables intermediate-path performance monitoring (IPPM), which allows you to monitor large amounts of STS traffic through intermediate nodes.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Note The monitored IPPM parameters are STS CV-P, STS ES-P, STS SES-P, STS UAS-P, and STS FC-P. For more information about IPPM parameters, refer to the "Performance Monitoring" chapter in the Cisco ONS 15327 Reference Manual.



Step 1 In node view, double-click the LTE card you want to monitor. The card view appears.

See Table 17-1 for a list of Cisco ONS 15327 LTE cards.

Step 2 Click the Provisioning tab.

Step 3 Click the SONET STS tab. Figure 17-14 shows the SONET STS tab in the Provisioning window.

Figure 17-14 SONET STS Tab for Enabling IPPM

Step 4 Check the check box in the Enable IPPM column for the STS you want to monitor.

Step 5 Click Apply.

Step 6 Click the Performance tab to view PM parameters. For IPPM parameter definitions, refer to the "Performance Monitoring" chapter in the Cisco ONS 15327 Reference Manual.

Step 7 Return to your originating procedure (NTP).


DLP-B123 View Electrical PM Parameters

Purpose

This task enables you to view DS-1 or DS-3 PM counts on an XTC card to detect possible performance problems.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve or higher



Step 1 In node view, double-click an XTC card. The card view appears.

Step 2 Click the Performance tab (Figure 17-15).

Figure 17-15 Viewing Electrical Performance Monitoring Information

Step 3 Click the DS1 tab or DS3 tab to view the desired PM parameters.

The PM parameter names appear on the left portion of the window in the Param column. The PM values appear on the right portion of the window in the Curr (current) and Prev-n (previous) columns. For PM parameter definitions, refer to the "Performance Monitoring" chapter in the Cisco ONS 15327 Reference Manual.

Step 4 Return to your originating procedure (NTP).


DLP-B124 Refresh Electrical or Optical PM Counts at Fifteen-Minute Intervals

Purpose

This task changes the window view to display PM counts in 15-minute intervals.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve or higher



Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.

Step 2 Click the Performance tab.

Step 3 Click the 15 min radio button.

Step 4 Click Refresh. Performance monitoring parameters appear in 15-minute intervals synchronized with the time of day.

Step 5 View the Curr column to find PM counts for the current 15-minute interval.

Each monitored performance parameter has corresponding threshold values for the current time period. If the value of the counter exceeds the threshold value for a particular 15-minute interval, a threshold crossing alert (TCA) is raised. The PM number represents the counter value for each specific performance monitoring parameter.

Step 6 View the Prev-n columns to find PM counts for the previous 15-minute intervals.


Note If a complete 15-minute interval count is not possible, the value appears with a yellow background. An incomplete or incorrect count can be caused by monitoring for less than 15 minutes after the counter started, changing node timing settings, changing the time zone settings, replacing a card, resetting a card, or changing port states. When the problem is corrected, the subsequent 15-minute interval appears with a white background.


Step 7 Return to your originating procedure (NTP).


DLP-B126 Monitor Near-End PM Counts

Purpose

This task enables you to view near-end PM counts for the selected card and port.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve or higher



Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.

Step 2 Click the Performance tab.

Step 3 Click the Near End radio button.

Step 4 Click Refresh. All PM parameters for the selected card on the incoming signal appear. For PM parameter definitions refer to the "Performance Monitoring" chapter in the Cisco ONS 15327 Reference Manual.

Step 5 View the Curr column to find PM counts for the current time interval.

Step 6 View the Prev-n columns to find PM counts for the previous time intervals.

Step 7 Return to your originating procedure (NTP).


DLP-B127 Monitor Far-End PM Counts

Purpose

Use this task to view far-end PM parameters for the selected card and port.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve or higher



Step 1 In node view, double-click an XTC card (for electrical PM counts) or an OC-N card. The card view appears.

Step 2 Click the Performance tab.

Step 3 Click the Far End radio button.


Note Only cards that allow far-end performance monitoring have this button as an option.


Step 4 Click Refresh. All PM parameters recorded by the far-end node for the selected card on the outgoing signal appear. For PM parameter definitions refer to the "Performance Monitoring" chapter in the Cisco ONS 15327 Reference Manual.

Step 5 View the Curr column to find PM counts for the current time interval.

Step 6 View the Prev-n columns to find PM counts for the previous time intervals.

Step 7 Return to your originating procedure (NTP).


DLP-B129 Reset Current PM Counts

Purpose

This task uses the Baseline button to clear the PM count displayed in the current time interval, but it does not clear the cumulative PM count. This task allows you to see how quickly PM counts rise.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve or higher



Step 1 In node view, double-click an XTC card (for electrical PM counts), Ethernet card, or an OC-N card. The card view appears.

Step 2 Click the Performance tab.

Step 3 Click Baseline.


Note The Baseline button clears the PM counts displayed in the current time interval, but does not clear the PM counts on the card. When the current time interval expires or the window view changes, the total number of PM counts on the card and in the window appear in the appropriate column. The baseline values are discarded if you change views to a different window and then return to the Performance Monitoring window.


Step 4 View the current statistics column(s) to observe changes to PM counts for the current time interval.

Step 5 Return to your originating procedure (NTP).


DLP-B130 Clear Selected PM Counts

Purpose

This task uses the Clear button to clear specified PM counts depending on the option selected.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser



Caution Pressing the Clear button can mask problems if used incorrectly. This button is commonly used for testing purposes. After pressing this button the current bin is marked invalid. Also note that the UAS state is not cleared if you were counting UAS; therefore, this count could be unreliable when UAS is no longer counting.


Step 1 In node view, double-click an Ethernet card, XTC card (for electrical PM counts), or an OC-N card. The card view appears.

Step 2 Click the Performance tab.

Step 3 Click Clear.

Step 4 From the Clear Statistics menu, choose one of three options:

Displayed statistics: Clearing displayed statistics erases from the card and the window all PM counts associated with the current combination of statistics on the selected port. This means that the selected time interval, direction, and signal type counts are erased from the card and the window.

All statistics for port x: Clearing all of the statistics for port x erases from the card and the window all PM counts associated with all combinations of the statistics on the selected port. This means that all time intervals, directions, and signal type counts are erased from the card and the window.

All statistics for card: Clearing all of the statistics for the card erases from the card and the window display all PM counts for all ports.

Step 5 From the Clear Statistics menu, click Yes to clear the selected statistics.

Step 6 View the displayed columns to verify that the selected PM counts have been cleared.

Step 7 Return to your originating procedure (NTP).


DLP-B131 Search for Circuits

Purpose

This task searches for an ONS 15327 circuit at the network, node, or card level.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve or higher



Step 1 Navigate to the appropriate CTC view:

To search the entire network, from the View menu choose Go to Network View.

To search for circuits that originate, terminate, or pass through a specific node, from the View menu choose Go to Other Node, then choose the node you want to search and click OK.

To search for circuits that originate, terminate, or pass through a specific card, double-click the card on the shelf graphic in node view to open the card in card view.

Step 2 Click the Circuits tab.

Step 3 If you are in node or card view, choose the scope for the search in the Scope drop-down list.

Step 4 Click Search.

Step 5 In the Circuit Name Search dialog box, complete the following:

Find What—Enter the text of the circuit name you want to find.

Match whole word only—Check this check box to instruct CTC to select circuits only if the entire word matches the text in the Find What field.

Match case—Check this check box to instruct CTC to select circuits only when the capitalization matches the capitalization entered in the Find What field.

Direction—Choose the direction for the search. Searches are conducted up or down from the currently selected circuit.

Step 6 Click Find Next. If a match is found, click Find Next again to find the next circuit.

Step 7 Repeat Steps 5 and 6 until you are finished, then click Cancel.

Step 8 Return to your originating procedure (NTP).


DLP-B137 Provision Path Trace on OC-N Ports

Purpose

This task monitors a path trace on OC-N ports within the circuit path.

Tools/Equipment

The OC-N ports you want to monitor must be on OC-N cards capable of receiving path trace. See Table 18-2.

Prerequisite Procedures

B264 Provision Path Trace on Circuit Source and Destination Ports

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 From the View menu, choose Go to Other Node. In the Select Node dialog box, choose the node where path trace was provisioned on the circuit source and destination ports.

Step 2 In node view, click Circuits.

Step 3 Choose the STS circuit that has path trace provisioned on the source and destination ports, then click Edit.

Step 4 In the Edit Circuit window, check the Show Detailed Map check box at the bottom of the window. A detailed circuit graphic showing source and destination ports appears.

Step 5 In the detailed circuit map, right-click the circuit OC-N port (the square on the left or right of the source node icon) and choose Edit Path Trace from the shortcut menu.


Note The OC-N port must be on a receive-only card listed in Table 18-2. If not, the Edit Path Trace menu item will not appear.


Step 6 In the Circuit Path Trace window, enable the path trace expected string by choosing Auto or Manual from the Path Trace Mode drop-down list:

Auto—Uses the first string received from the port at the other end as the baseline string. An alarm is raised when a string that differs from the baseline is received. For OC-N ports, Auto is recommended, since Manual mode requires you to trace the circuit on the Edit Circuit window to determine whether the port is the source or destination path.

Manual—Uses the Current Expected String field as the baseline string. An alarm is raised when a string that differs from the Current Expected String is received.

Step 7 If you set the Path Trace Mode field to Manual, enter the string that the OC-N port should receive in the New Expected String field. To do this, trace the circuit path on the detailed circuit window to determine whether the port is in the circuit source or destination path, then set the New Expected String field to the string transmitted by the circuit source or destination. If you set the Path Trace Mode field to Auto, skip this step.

Step 8 Click Apply, then click Close.

Step 9 Return to your originating procedure (NTP).


DLP-B140 Change the Node Name, Date, Time, and Contact Information

Purpose

This procedure changes basic information such as node name, date, time, and contact information.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Note Changing the date, time, or time zone might invalidate the node's performance monitoring counters.



Step 1 In node view, click the Provisioning > General tabs.

Step 2 Change any of the following:

General: Node Name

General: Contact

Location: Latitude

Location: Longitude

Location: Description


Note To see changes to longitude or latitude on the network map, you must go to network view and right-click the specified node, then click Reset Node Position.


Time: Use NTP/SNTP Server

Time: Date (M/D/Y)

Time: Time (H:M:S)

Time: Time Zone

Time: Use Daylight Saving Time

See the "NTP-B25 Set Up Name, Date, Time, and Contact Information" procedure for detailed field descriptions.

Step 3 Click Apply. Confirm that the changes appear; if not, repeat the task.

Step 4 Return to your originating procedure (NTP).


DLP-B142 Modify a Static Route

Purpose

This task modifies a static route on an ONS 15327.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B65 Create a Static Route

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, click the Provisioning > Network > Static Routing tabs.

Step 2 Click the static route that you want to edit.

Step 3 Click Edit.

Step 4 In the Edit Selected Static Route dialog box, enter the following:

Mask

Next Hop

Cost

See the "DLP-B65 Create a Static Route" task for detailed field descriptions.

Step 5 Click OK.

Step 6 Return to your originating procedure (NTP).


DLP-B143 Delete a Static Route

Purpose

This task deletes a static route on an ONS 15327.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B65 Create a Static Route

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, click the Provisioning > Network > Static Routing tabs.

Step 2 Click the static route you want to delete.

Step 3 Click Delete. A confirmation dialog box appears.

Step 4 Click Yes.

Step 5 Return to your originating procedure (NTP).


DLP-B144 Disable the Open Shortest Path First Protocol

Purpose

This task disables the Open Shortest Path First (OSPF) routing protocol for an ONS 15327 LAN.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B250 Set Up or Change Open Shortest Path First Protocol

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, click the Provisioning > Network > OSPF tabs. The OSPF subtab has several options.

Step 2 In the OSPF on LAN area, uncheck the OSPF active on LAN check box.

Step 3 Click Apply. Confirm that the changes appear; if not, repeat the task.


Note Disabling OSPF can cause an XTC reboot, which causes a temporary loss of connectivity to the node, but does not affect traffic.


Step 4 Return to your originating procedure (NTP).


DLP-B145 Change the Network View Background Color

Purpose

This task changes the network view background color and the domain view background color (the area shown when you open a domain).

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Retrieve or higher



Note If you modify background colors, the change is stored in your CTC user profile on the local computer. The change does not affect other CTC users on different computers.



Step 1 From the View menu, choose Go to Network View.

Step 2 Right-click the network view or domain map area and choose Set Background Color from the shortcut menu.

Step 3 In the Choose Color dialog box, click a background color.

Step 4 Click OK.

Step 5 Return to your originating procedure (NTP).


DLP-B148 Create Domain Icons

Purpose

This task creates a domain icon to group ONS 15327 icons in CTC network view for all users. By default, domain icons are visible on all CTC sessions that log into the network.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser



Note To allow users of any security level to create local domains, that is, domains that are visible on the home CTC session only, superusers can change the CTC.network.LocalDomainCreationAndViewing NE default value to TRUE. A TRUE value means any user can maintain the domain information in his or her Preferences file, meaning domain changes will not affect other CTC sessions. (The default value is FALSE, meaning domain information affects all CTC sessions and only superusers can create a domain or put a node into a domain.) See the "NTP-B270 Edit Network Element Defaults" procedure to change NE default values.



Step 1 From the View menu, choose Go to Network View.

Step 2 Right-click the network map and choose Create New Domain from the shortcut menu.

Step 3 When the domain icon appears on the map, click the map name and enter the domain name.

Step 4 Press Enter.

Step 5 Return to your originating procedure (NTP).


DLP-B149 Manage Domain Icons

Purpose

This task manages CTC network view domain icons. By default, domain icons are visible on all CTC sessions that log into the network.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B148 Create Domain Icons

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser



Note To allow users of any security level to create local domains, that is, domains that are visible on the home CTC session only, superusers can change the CTC.network.LocalDomainCreationAndViewing NE default value to TRUE. A TRUE value means any user can maintain the domain information in his or her Preferences file, meaning domain changes will not affect other CTC sessions. (The default value is FALSE, meaning domain information affects all CTC sessions and only superusers can create a domain or put a node into a domain.) See the "NTP-B270 Edit Network Element Defaults" procedure to change NE default values.



Step 1 From the View menu, choose Go to Network View.

Step 2 Locate the domain action you want in Table 17-2 and complete the appropriate steps.

Table 17-2 Managing Domains 

Domain Action
Steps

Move a domain

Drag and drop the node icon to the new location.

Rename a domain

Right-click the domain icon and choose Rename Domain from the shortcut menu. Enter the new name in the domain name field.

Add a node to a domain

Drag and drop the domain icon to the domain icon.

Move a node from a domain to the network map

Open the domain and right-click a node. Choose Move Node Back to Parent View.

Open a domain

Double-click the domain icon. Right-click the domain and choose Open Domain.

Return to network view

Right-click the domain view area and choose Go to Parent View from the shortcut menu.

Preview domain contents

Right-click the domain icon and choose Show Domain Overview. The domain icon shows a small preview of the nodes in the domain. To turn off the domain overview, right-click the overview and choose Show Domain Overview.

Remove domain

Right-click the domain icon and choose Remove Domain. Any nodes in the domain are returned to the network map.


Step 3 Return to your originating procedure (NTP).


DLP-B154 Modify a 1+1 Protection Group

Purpose

This task modifies a 1+1 protection group for any optical port (OC-3, OC-12, or OC-48).

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, click the Provisioning > Protection tabs.

Step 2 In the Protection Groups area, click the 1+1 protection group you want to modify.

Step 3 In the Selected Group area, you can modify the following as needed:

Name—Enter the changes to the protection group name. The name can have up to 32 alphanumeric characters.

Bidirectional switching—Check or uncheck.

Revertive—Check this check box if you want traffic to revert to the working card after failure conditions stay corrected for the amount of time chosen from the Reversion Time menu. Uncheck if you do not want traffic to revert.

Reversion Time—If the Revertive check box is checked, choose the reversion time from the Reversion Time drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. This is the amount of time that will elapse before the traffic reverts to the working card. Traffic can revert when conditions causing the switch are cleared.

See the "NTP-B170 Create 1+1 Protection Groups" procedure for field descriptions.

Step 4 Click Apply. Confirm that the changes appear; if not, repeat the task.

Step 5 Return to your originating procedure (NTP).


DLP-B155 Delete a 1+1 Protection Group

Purpose

This task deletes a 1+1 protection group.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In the node view, click the Provisioning > Protection tabs.

Step 2 In the Protection Groups list, click the protection group you want to delete.

Step 3 Click Delete.

Step 4 Click Yes in the Delete Protection Group dialog box to confirm deletion.

Step 5 Confirm that the changes appear; if they do not, repeat Steps 1 through 4.

Step 6 Return to your originating procedure (NTP).


DLP-B157 Change the Node Timing Source

Purpose

This task changes the SONET timing source for the ONS 15327.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution The following procedure can be service-affecting; perform during a scheduled maintenance window.


Step 1 In node view, click the Provisioning > Timing tabs.

Step 2 In the General Timing area, change any of the following information:

Timing Mode

SSM Message Set

Quality of RES

Revertive

Reversion Time


Note Because mixed timing can cause timing loops, Cisco does not recommend using the Mixed Timing option. Use this mode with care.


See the "DLP-B69 Set Up External or Line Timing" task for field descriptions.

Step 3 In the BITS Facilities area, you can change the following information:


Note The BITS Facilities section sets the parameters for your BITS1 and BITS2 timing references. Many of these settings are determined by the timing source manufacturer. If equipment is timed through BITS Out, you can set timing parameters to meet the requirements of the equipment.


In/Out State

Coding

Framing

Sync Messaging

AIS Threshold

LBO

Step 4 In the Reference Lists area, you can change the following information:


Note Reference lists define up to three timing references for the node and up to six BITS Out references. BITS Out references define the timing references used by equipment that can be attached to the node's mechanical interface cards (MICs). If you attach equipment to the MIC BITS Out pins, you normally attach it to a node with Line mode because equipment near the external timing reference can be directly wired to the reference.


NE Reference

BITS 1 Out/BITS 2 Out

Step 5 Click Apply. Confirm that the changes appear; if not, repeat the task.

Step 6 Return to your originating procedure (NTP).


DLP-B158 Change User Password and Security Settings on a Single Node

Purpose

This task changes settings for an existing user at one node.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B74 Create a New User on a Single Node

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser only



Step 1 In node view, click the Provisioning > Security > Users tabs.

Step 2 Click the user whose settings you want to modify.

Step 3 Click Change.

Step 4 In the Change User dialog box, you can:

Change a user password

Modify the user security level

Lock out or disable the user

See the "DLP-B74 Create a New User on a Single Node" task for field descriptions.

Step 5 Click OK.


Note User settings that you changed during this task will not appear until that user logs off and logs back in.


Step 6 Return to your originating procedure (NTP).


DLP-B159 Delete a User on a Single Node

Purpose

This task deletes an existing user from a single node.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser only



Note CTC will allow you to delete other Superuser IDs if one Superuser ID remains. For example, you can delete the CISCO15 user if you have created another Superuser ID. Use this option with caution.



Note Users who are logged in when you delete them will not be logged out. The delete user action will take effect after the user logs out. To log out a user who is currently logged in, complete the "DLP-B315 Log Out a User on a Single Node" task.



Step 1 In node view, click the Provisioning > Security > Users tabs.

Step 2 Choose the user you want to delete.

Step 3 In the Delete User dialog box, complete the following:

a. To log the user out before the deleting the user, check Logout before delete.

b. Click OK.

Step 4 In the User Deletion Results dialog box, click OK. Confirm that the changes appear; if not, repeat the task.

Step 5 Return to your originating procedure (NTP).


DLP-B160 Change User Password and Security Settings on Multiple Nodes

Purpose

This task changes settings for an existing user on multiple nodes.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

B75 Create a New User on Multiple Nodes

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser only



Note You must add the same user name and password to each node the user will access.



Step 1 From the View menu, choose Go to Network View. Verify that you can access all the nodes where you want to add users.

Step 2 Click the Provisioning > Security > Users tabs. Click the user's name whose settings you want to change.

Step 3 Click Change. The Change User dialog box appears.

Step 4 In the Change User dialog box, you can:

Change a user password

Modify the user security level

Lock out or disable the user

See the "DLP-B75 Create a New User on Multiple Nodes" task for field descriptions.

Step 5 Click OK. A Change Results confirmation dialog box appears.

Step 6 Click OK to acknowledge the changes.

Step 7 Return to your originating procedure (NTP).


DLP-B161 Delete a User on Multiple Nodes

Purpose

This task deletes an existing user from multiple nodes.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser only



Note CTC will allow you to delete other Superuser IDs if one Superuser ID remains. For example, you can delete the CISCO15 user if you have created another Superuser ID. Use this option with caution.



Note Users who are logged in when you delete them will not be logged out. The delete user action will take effect after the user logs out. To log out a user who is currently logged in, complete the "DLP-B316 Log Out a User on Multiple Nodes" task.



Step 1 From the View menu, choose Go to Network View.

Step 2 Click the Provisioning > Security > Users tabs. Click the name of the user you want to delete.

Step 3 Click Delete.

Step 4 In the Delete User dialog box, complete the following:

a. To log the user out before the deleting the user, check Logout before delete.

b. Click OK.

Step 5 In the User Deletion Results dialog box, click OK.

Step 6 Return to your originating procedure (NTP).


DLP-B163 Delete SNMP Trap Destinations

Purpose

This task deletes SNMP trap destinations on an ONS 15327.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, click the Provisioning > SNMP tabs.

Step 2 In the Trap Destinations list, click the trap you want to delete.

Step 3 Click Delete. A confirmation dialog box appears.

Step 4 Click Yes. Confirm that the changes appear; if not, repeat the task.

Step 5 Return to your originating procedure (NTP).


DLP-B165 Change Line and Threshold Settings for the DS-1 Ports

Purpose

This task changes the line and threshold settings for the DS-1 ports.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Note The ONS 15327 XTC cards provide 14 (XTC-14) or 28 (XTC-28-3) DS-1 ports. Each port operates at 1.544 Mbps. Default thresholds are based on recommendations in Telcordia GR-820-CORE, Section 4.0.



Note Refer to the "Network Element Defaults" appendix in the Cisco ONS 15327 Reference Manual for DS-1 port default settings.



Step 1 In node view, double-click the XTC card where you want to change the DS-1 line or threshold settings.

Step 2 Click the Provisioning > DS-1 tabs (Figure 17-16).

Figure 17-16 Provisioning Line Parameters on the DS-1 Ports

Step 3 Depending on the setting you need to modify, click the Line, Line Thresholds, Elect Path Thresholds, or SONET Thresholds subtab.

Step 4 Modify any of the settings found under these subtabs. For definitions of the line settings, see Table 17-3. For definitions of the line threshold settings, see Table 17-4. For definitions of the electrical path settings, see Table 17-5. For definitions of the SONET threshold settings, see Table 17-6.

Step 5 Click Apply.

Step 6 Click the Provisioning > Alarm Profiles > Alarm Behavior tabs to modify alarm behavior.


Note See Chapter 8 "Manage Alarms" for information about the Alarm Behavior subtab.


Step 7 Repeat Steps 4 through 6 for each subtab that has parameters you want to provision.

Table 17-3 describes the values on the Provisioning > DS1 > Line subtab for the DS-1 ports.

Table 17-3 Line Options for DS-1 Ports  

Parameter
Description
Options

Port #

Displays the port number.

1 to 14 (XTC-14)

1 to 28 (XTC-28-3)

Port

Displays the port name.

User-defined, up to 32 alphanumeric or special characters. Blank by default.

See the "DLP-B314 Assign a Name to a Port" task.

Line Type

Defines the line framing type.

D4

ESF—Extended super frame

Unframed

Line Coding

Defines the DS-1 transmission coding type.

AMI—Alternate mark inversion (default)

B8ZS—Bipolar 8 zero substitution

Line Length

Defines the distance (in feet) from backplane connection to the next termination point.

0 - 131 (default)

132 - 262

263 - 393

394 - 524

525 - 655

Admin State

Sets the port service state unless network conditions prevent the change.

IS—Puts the port in-service. The port service state changes to IS-NR.

IS,AINS—Puts the port in automatic in-service. The port service state changes to OOS-AU,AINS.

OOS,DSBLD—Removes the port from service and disables it. The port service state changes to OOS-MA,DSBLD.

OOS,MT—Removes the port from service for maintenance. The port service state changes to OOS-MA,MT.

Service State

Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State.

IS-NR—The port is fully operational and performing as provisioned.

OOS-AU,AINS—The port is out-of-service, but traffic is carried. Alarm reporting is suppressed. The ONS 15327 node monitors the ports for an error-free signal. After an error-free signal is detected, the port stays in OOS-AU,AINS state for the duration of the soak period. After the soak period ends, the port service state changes to IS-NR.

OOS-MA,DSBLD—The port is out-of-service and unable to carry traffic.

OOS-MA,MT—The port is out-of-service for maintenance. Alarm reporting is suppressed, but traffic is carried and loopbacks are allowed.

AINS Soak

Displays the automatic in-service soak time.

Duration of valid input signal in hh.mm after which the port is set in service by the software.

0 to 48 hours, 15-minute increments.


Table 17-4 describes the values on the Provisioning > DS1 > Line Thresholds subtab for the DS-1 ports.

Table 17-4 Line Thresholds Options for DS-1 Ports 

Parameter
Description
Options

Port

Port number

1 to 14 (XTC-14)

1 to 28 (XTC-28-3)

CV

Coding violations

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

ES

Errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

SES

Severely errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

LOSS

Number of one-second intervals containing one or more loss of signal (LOS) defects

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.


Table 17-5 describes the values on the Provisioning > DS1 > Elect Path Thresholds subtab for the DS-1 ports.

Table 17-5 Electrical Path Threshold Options for DS-1 Ports 

Parameter
Description
Options

Port

Port number

1 to 14 (XTC-14)

1 to 28 (XTC-28-3)

CV

Coding violations

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

ES

Errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

SES

Severely errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

SAS

Severely errored frame/alarm indication signal

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

AISS

Alarm indication signal seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

UAS

Unavailable seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.


Table 17-6 describes the values on the Provisioning > DS1 > SONET Thresholds subtab for the DS-1 ports.

Table 17-6 SONET Thresholds Options for DS-1 Ports 

Parameter
Description
Options

Port #

DS-1 ports partitioned for STS

Read-only.

Line 1, STS 1, Line 2, STS 1

Line 3, STS 1, Line 4 STS 1

CV

Coding violations

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near End, STS termination).

ES

Errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near End, STS termination).

FC

Failure count

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near End, STS termination).

SES

Severely errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near End, STS termination).

UAS

Unavailable seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near End, STS termination).



Note The threshold value appears after the circuit is created.


Step 8 Return to your originating procedure (NTP).


DLP-B166 Change Line and Threshold Settings for the DS-3 Ports

Purpose

This task changes the line and threshold settings for the DS-3 ports.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Note Refer to the "Network Element Defaults" appendix in the Cisco ONS 15327 Reference Manual for DS-3 port default settings.



Step 1 In the node view, double-click the XTC-28-3 card where you want to change the DS-3 line or threshold settings.

Step 2 Click the Provisioning tab.

Step 3 Click the DS-3 tab.

Step 4 Depending on the setting you need to modify, click the Line, Line Thresholds, or SONET Thresholds tab.

Step 5 Modify any of the settings found under these subtabs. For definitions of the Line settings, see Table 17-7. For definitions of the Line Threshold settings, see Table 17-8. For definitions of the SONET Threshold settings, see Table 17-9.

Table 17-7 describes the values on the Provisioning > DS3 > Line subtab for the DS-3 ports.

Step 6 Click Apply.

Step 7 Click the Provisioning > Alarm Profiles > Alarm Behavior tabs to modify alarm behavior.


Note See Chapter 8 "Manage Alarms" for information about the Alarm Behavior subtab.


Table 17-7 Line Options for DS-3 Ports 

Parameter
Description
Options

Port #

Displays the port number.

1 to 3

Port

Displays the port name.

User-defined, up to 32 alphanumeric or special characters. Blank by default.
See the "DLP-B314 Assign a Name to a Port" task.

Line Length

Defines the distance (in feet) from backplane connection to the next termination point.

0 - 225 (default)

226 - 450

Admin State

Sets the port service state unless network conditions prevent the change.

IS—Puts the port in-service. The port service state changes to IS-NR.

IS,AINS—Puts the port in automatic in-service. The port service state changes to OOS-AU,AINS.

OOS,DSBLD—Removes the port from service and disables it. The port service state changes to OOS-MA,DSBLD.

OOS,MT—Removes the port from service for maintenance. The port service state changes to OOS-MA,MT.

Service State

Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State.

IS-NR—The port is fully operational and performing as provisioned.

OOS-AU,AINS—The port is out-of-service, but traffic is carried. Alarm reporting is suppressed. The ONS 15327 node monitors the ports for an error-free signal. After an error-free signal is detected, the port stays in OOS-AU,AINS state for the duration of the soak period. After the soak period ends, the port service state changes to IS-NR.

OOS-MA,DSBLD—The port is out-of-service and unable to carry traffic.

OOS-MA,MT—The port is out-of-service for maintenance. Alarm reporting is suppressed, but traffic is carried and loopbacks are allowed.

AINS Soak

Displays the automatic in-service soak time.

Time of presence of valid input signal in hh.mm after which the port is set in service by the software. 0 to 48 hours, 15-minute increments.


Table 17-8 describes the values on the Provisioning > DS3 > Line Thresholds subtab for the DS-3 ports.

Table 17-8 Line Threshold Options for DS-3 Ports 

Parameter
Description
Options

Port #

Port number

1 to 3

CV

Coding violations

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

ES

Errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

SES

Severely errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.

LOSS

Loss of signal; number of one-second intervals containing one or more LOS defects

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button.


Table 17-9 describes the values on the Provisioning > DS3 > SONET Thresholds subtab for the DS-3 ports.

Table 17-9 SONET Threshold Options for DS-3 Ports 

Parameter
Description
Options

Port #

DS-3 ports partitioned for STS

Read-only.

DS-3 ports 1 to 3

Any available STS

CV

Coding violations

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near and Far End, STS termination only).

ES

Errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near and Far End, STS termination only).

FC

Failure count

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near and Far End, STS termination only).

SES

Severely errored seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near and Far End, STS termination only).

UAS

Unavailable seconds

Numeric. Can be set for 15-minute or one-day intervals. Select the bullet and click the Refresh button (Near and Far End, STS termination only).


Step 8 Repeat Steps 4 through 7 for each subtab that has parameters you want to provision.


Note The threshold value appears after the circuit is created.


Step 9 Return to your originating procedure (NTP).


DLP-B170 Change Line Settings for OC-N Cards

Purpose

This task changes the line settings for OC-N cards.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Note Refer to the "Network Element Defaults" appendix in the Cisco ONS 15327 Reference Manual for OC-N card default settings.



Step 1 Double-click the OC-N card where you want to change the line settings.

Step 2 Click the Provisioning > Line tabs.

Step 3 Modify any of the settings listed in Table 17-10.


Note The STS subtab is used to provision intermediate path performance monitoring (IPPM). To provision IPPM, circuits must be provisioned on the card.


Table 17-10 OC-N Card Line Settings 

Parameter
Description
Options

Port #

Displays the port number.

Read-only.

1 to 4 (OC-3)

1 (OC-12, OC-48)

Port Name

Provides the ability to assign the specified port a name.

User-defined, up to 32 alphanumeric or special characters. Blank by default.
See the "DLP-B314 Assign a Name to a Port" task.

SF BER

Sets the signal fail bit error rate.

1E-3

1E-4 (default)

1E-5

SD BER

Sets the signal degrade bit error rate.

1E-5

1E-6

1E-7 (default)

1E-8

1E-9

Provides Synch

If checked, the card is provisioned as a network element timing reference.

Read-only.

Yes (checked)

No (unchecked)

Admin State

Sets the port service state unless network conditions prevent the change.

IS—Puts the port in-service. The port service state changes to IS-NR.

IS,AINS—Puts the port in automatic in-service. The port service state changes to OOS-AU,AINS.

OOS,DSBLD—Removes the port from service and disables it. The port service state changes to OOS-MA,DSBLD.

OOS,MT—Removes the port from service for maintenance. The port service state changes to OOS-MA,MT.

Service State

Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State.

IS-NR—The port is fully operational and performing as provisioned.

OOS-AU,AINS—The port is out-of-service, but traffic is carried. Alarm reporting is suppressed. The ONS 15327 node monitors the ports for an error-free signal. After an error-free signal is detected, the port stays in OOS-AU,AINS state for the duration of the soak period. After the soak period ends, the port service state changes to IS-NR.

OOS-MA,DSBLD—The port is out-of-service and unable to carry traffic.

OOS-MA,MT—The port is out-of-service for maintenance. Alarm reporting is suppressed, but traffic is carried and loopbacks are allowed.

Send DoNotUse

When checked, sends a DUS (do not use) message on the S1 byte.

Yes (checked)

No (unchecked, default)

Sync MsgIn

Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source.

Yes (checked, default)

No (unchecked)

Type

Defines the port as SONET or SDH. The Enable Sync Msg field and the Send Do Not Use field must be disabled before the port can be set to SDH.

Sonet

SDH

AINS Soak

Displays the automatic in-service soak time.

Duration of valid input signal in hh.mm after which the card is set in service by the software.

0 to 48 hours, 15-minute increments

Admin SSM

Allows you to override the STU (synchronization traceability unknown) value (default setting).

PRS: Primary Reference Source (Stratum 1)

ST2: Stratum 2

TNC: Transit node clock

ST3E: Stratum 3E

ST3: Stratum 3

SMC: SONET minimum clock

ST4: Stratum 4

PJSTSMon #

Sets the STS that will be used for pointer justification. If set to 0, no STS is monitored. Only one STS can be monitored on each OC-N port.

0 - 3 (OC-3, per port)

0 - 12 (OC-12)

0 - 48 (OC-48)

Send <FF> DoNotUse

When checked, sends a special DUS (0xff) message on the S1 byte.

Yes

No


Step 4 Click Apply.

Step 5 Return to your originating procedure (NTP).


DLP-B171 Change SONET Threshold Settings for OC-N Cards

Purpose

This task changes SONET thresholds settings for OC-N cards.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, double-click the OC-N card where you want to change the SONET thresholds settings.

Step 2 Click the Provisioning > SONET Thresholds tabs.

Step 3 Modify any of the settings listed in Table 17-11.

Table 17-11 OC-N SONET Thresholds Options 

Parameter
Description
Options

Port

Port number

1 to 4 (OC-3)

1 (OC-12, OC-48)

CV

Coding violations

Numeric. Can be set for 15-minute or one-day intervals for Line, Section, or Path (Near and Far End). Select the bullet and click the Refresh button.

ES

Errored seconds

Numeric. Can be set for 15-minute or one-day intervals for Line, Section, or Path (Near and Far End). Select the bullet and click the Refresh button.

SES

Severely errored seconds

Numeric. Can be set for 15-minute or one-day intervals for Line, Section, or Path (Near and Far End). Select the bullet and click the Refresh button.

SEFS

Severely errored framing seconds

Numeric. Can be set for 15-minute or one-day intervals for Line, Section, or Path (Near and Far End). Select the bullet and click the Refresh button.

FC

Failure count

Numeric. Can be set for 15-minute or one-day intervals for Line. Select the bullet and click the Refresh button. or Path (Near and Far End)

UAS

Unavailable seconds

Numeric. Can be set for 15-minute or one-day intervals for Line or Path (Near and Far End). Select the bullet and click the Refresh button.

PPJC-PDET

Positive pointer justification count, STS path detected

Numeric. Can be set for 15-minute or one-day intervals for Line (Near and Far End). Select the bullet and click the Refresh button.

NPJC-PDET

Negative pointer justification count, STS path detected

Numeric. Can be set for 15-minute or one-day intervals for Line (Near and Far End). Select the bullet and click the Refresh button.

PPJC-PGEN

Positive pointer justification count, STS path generated

Numeric. Can be set for 15-minute or one-day intervals for Line (Near and Far End). Select the bullet and click the Refresh button.

NPJC-PGEN

Negative pointer justification count, STS path generated

Numeric. Can be set for 15-minute or one-day intervals for Line (Near and Far End). Select the bullet and click the Refresh button.

PSC

Protection switching count (Line)

Numeric. Can be set for 15-minute or one-day intervals for Line (Near and Far End). Select the bullet and click the Refresh button.

PSD

Protection switching duration (Line)

Numeric. Can be set for 15-minute or one-day intervals for Line (Near and Far End). Select the bullet and click the Refresh button.

PSC-W

Protection switching count - working line

Note Bidirectional line switch rings (BLSRs) are not supported on the OC-3 card; therefore, the PSC-W, PSC-S, and PSC-R performance monitoring parameters (PMs) do not increment.

Numeric. Can be set for 15-minute or one-day intervals for Line (Near and Far End). Select the bullet and click the Refresh button.

PSD-W

Protection switching duration - working line

Note BLSRs are not supported on the OC-3 card; therefore, the PSD-W, PSD-S, and PSD-R PMs do not increment.

Numeric. Can be set for 15-minute or one-day intervals for Line (Near and Far End). Select the bullet and click the Refresh button.


Step 4 Click Apply.

Step 5 Return to your originating procedure (NTP).


DLP-B172 Change an Optical Port to SDH

Purpose

This task provisions a port on an OC-N card for SDH.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 Double-click the OC-N card where you want to provision a port for SDH. Before you can change the port type to SDH, ensure the following:

The EnableSyncMsg and SendDoNotUse fields are unchecked.

The card is not part of a BLSR or 1+1 protection group.

The card is not part of an orderwire channel.

The card is not a SONET data communications channel (DCC) termination point.

Step 2 Click the Provisioning > Line tabs.

Step 3 In the Type field, specify the port and choose SDH.

Step 4 Click Apply.

Step 5 If the card is a multiport OC-N card, such as an OC-3, you can repeat Steps 3 and 4 for any other ports on the card.

Step 6 Return to your originating procedure (NTP).


DLP-B173 Provision OSI Routing Mode

Purpose

This task provisions the Open System Interconnection (OSI) routing mode. Complete this task when the ONS 15327 is connected to networks with third party network elements (NEs) that use the OSI protocol stack for data communications network (DCN) communication.

Tools/Equipment

None

Prerequisite Procedures

B24 Verify Card Installation

Required/As Needed

As needed

Onsite/Remote

Onsite

Security Level

Provisioning or higher



Caution Do not complete this task until you confirm the role of the node within the network. It will be either an ES, IS Level 1, or IS Level 1/Level 2. This decision must be carefully considered. For additional information about OSI provisioning, refer to the "Management Network Connectivity" chapter of the Cisco ONS 15327 Reference Manual.


Caution Link State Protocol (LSP) buffers must be the same at all NEs within the network, or loss of visibility might occur. Do not modify the LSP buffers unless you confirm that all NEs within the OSI have the same buffer size.


Caution LSP buffer sizes cannot be greater than the LAP-D maximum transmission unit (MTU) size within the OSI area.


Note The ONS 15327 primary NSAP address is also the Router 1 primary manual area address. To edit the primary NSAP, you must edit the Router 1 primary manual area address. After you enable Router 1 on the Routers subtab, the Change Primary Area Address button is available to edit the address.



Step 1 Complete the "DLP-B60 Log into CTC" task at the node where you want to provision the OSI routing mode. If you are already logged in, continue with Step 2.

Step 2 In node view, click the Provisioning > OSI tabs.

Step 3 Choose a routing mode:

End System—The ONS 15327 performs OSI end system (ES) functions and relies upon an intermediate system (IS) for communication with nodes that reside within its OSI area.


Note The End System routing mode is not available if more than one virtual router is enabled.


Intermediate System Level 1—The ONS 15327 performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area.

Step 4 If needed, change the L1 LSP Buffer Size. This adjusts the Level 1 link state PDU buffer size. The default is 512. It should not be changed.

Step 5 Return to your originating procedure (NTP).


DLP-B174 Provision or Modify TARP Operating Parameters

Purpose

This task provisions or modifies the Target Identifier Address Resolution Protocol (TARP) operating parameters including TARP protocol data unit (PDU) propagation, timers, and loop detection buffer (LDB).

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser



Step 1 In node view, click the Provisioning > OSI > TARP > Config tabs.

Step 2 Provision the following parameters, as needed:

TARP PDUs L1 Propagation—If checked (default), TARP Type 1 PDUs that are received by the node and are not excluded by the LDB are propagated to other NEs within the Level 1 OSI area. (Type 1 PDUs request a protocol address that matches a target identifier [TID] within a Level 1 routing area.) The propagation does not occur if the NE is the target of the Type 1 PDU, and PDUs are not propagated to the NE from which the PDU was received.


Note This parameter is not used when the Node Routing Area (Provisioning > OSI > Main Setup tab) is set to End System.


TARP PDUs Origination—If checked (default), the node performs all TARP origination functions including:

TID to Network Service Access Point (NSAP) resolution requests (originate TARP Type 1 and Type 2 PDUs)

NSAP to TID requests (originate Type 5 PDUs)

TARP address changes (originate Type 4 PDUs)


Note TARP Echo and NSAP to TID is not supported.


TARP Data Cache—If checked (default), the node maintains a TARP data cache (TDC). The TDC is a database of TID to NSAP pairs created from TARP Type 3 PDUs received by the node and modified by TARP Type 4 PDUs (TID to NSAP updates or corrections). TARP 3 PDUs are responses to Type 1 and Type 2 PDUs. The TDC can also be populated with static entries entered on the TARP > Static TDC tab.


Note This parameter is only used when the TARP PDUs Origination parameter is enabled.


LDB—If checked (default), enables the TARP loop detection buffer. The LDB prevents TARP PDUs from being sent more than once on the same subnet.


Note The LDP parameter is not used if the Node Routing Mode is provisioned to End System or if the TARP PDUs L1 Propagation parameter is not enabled.


LAN TARP Storm Suppression—If checked (default), enables TARP storm suppression. This function prevents redundant TARP PDUs from being unnecessarily propagated across the LAN network.

Send Type 4 PDU on Startup—If checked, a TARP Type 4 PDU is originated during the initial ONS 15454 startup. Type 4 PDUs indicate that a TID or NSAP change has occurred at the NE. (The default setting is not enabled.)

Type 4 PDU Delay—Sets the amount of time that will pass before the Type 4 PDU is generated when Send Type 4 PDU on Startup is enabled. 60 seconds is the default. The range is 0 to 255 seconds.


Note The Send Type 4 PDU on Startup and Type 4 PDU Delay parameters are not used if TARP PDUs Origination is not enabled.


LDB Entry—Sets the TARP loop detection buffer timer. The LDB buffer time is assigned to each LDB entry for which the TARP sequence number (tar-seq) is zero. The default is 5 minutes. The range is 1 to 10 minutes.

LDB Flush—Sets the frequency period for flushing the LDB. The default is 5 minutes. The range is 0 to 1440 minutes.

T1—Sets the amount of time to wait for a response to a Type 1 PDU. Type 1 PDUs seek a specific NE TID within an OSI Level 1 area. The default is 15 seconds. The range is 0 to 3600 seconds.

T2—Sets the amount of time to wait for a response to a Type 2 PDU. TARP Type 2 PDUs seek a specific NE TID value within OSI Level 1 and Level 2 areas. The default is 25 seconds. The range is 0 to 3600 seconds.

T3—Sets the amount of time to wait for an address resolution request. The default is 40 seconds. The range is 0 to 3600 seconds.

T4—Sets the amount of time to wait for an error recovery. This timer begins after the T2 timer expires without finding the requested NE TID. The default is 20 seconds. The range is 0 to 3600 seconds.


Note Timers T1, T2, and T4 are not used if TARP PDUs Origination is not enabled.


Step 3 Click Apply.

Step 4 Return to your originating procedure (NTP).


DLP-B175 Add a Static TID to NSAP Entry to the TARP Data Cache

Purpose

This task adds a static TID to NSAP entry to the TDC. The static entries are required for NEs that do not support TARP and are similar to static routes. For a specific TID, you must force a specific NSAP.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioner or higher



Step 1 In node view, click the Provisioning > OSI > TARP > Static TDC tabs.

Step 2 Click Add Static Entry.

Step 3 In the Add Static Entry dialog box, enter the following:

TID—Enter the TID of the NE. (For ONS nodes, the TID is the Node Name parameter on the node view Provisioning > General tab.)

NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.

Step 4 Click OK to close the Masked NSAP Entry dialog box, if used, and then click OK to close the Add Static Entry dialog box.

Step 5 Return to your originating procedure (NTP).


DLP-B176 Remove a Static TID to NSAP Entry from the TARP Data Cache

Purpose

This task removes a static TID to NSAP entry from the TDC.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioner or higher



Step 1 In node view, click the Provisioning > OSI > TARP > Static TDC tabs.

Step 2 Click the static entry that you want to delete.

Step 3 Click Delete Static Entry.

Step 4 In the Delete TDC Entry dialog box, click Yes.

Step 5 Return to your originating procedure (NTP).


DLP-B177 Add a TARP Manual Adjacency Table Entry

Purpose

This task adds an entry to the TARP manual adjacency table (MAT). Entries are added to the MAT when the ONS 15327 must communicate across routers or non-SONET NEs that lack TARP capability.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In the node view, click the Provisioning > OSI > TARP > MAT tabs.

Step 2 Click Add.

Step 3 In the Add TARP Manual Adjacency Table Entry dialog box, enter the following:

Level—Sets the TARP Type Code that will be sent:

Level 1—Indicates that the adjacency is within the same area as the current node. The entry generates Type 1 PDUs.

Level 2—Indicates that the adjacency is in a different area than the current node. The entry generates Type 2 PDUs.

NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.

Step 4 Click OK to close the Masked NSAP Entry dialog box, if used, and then click OK to close the Add Static Entry dialog box.

Step 5 Return to your originating procedure (NTP).


DLP-B178 Provision OSI Routers

Purpose

This task enables the OSI virtual router and edits its primary manual area address.

Tools/Equipment

None

Prerequisite Procedures

B24 Verify Card Installation

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Note The Router 1 manual area address, System ID, and Selector "00" create the node NSAP address. Changing the Router 1 manual area address changes the node's NSAP address.



Note The System ID for Router 1 is the node MAC address.



Step 1 Complete the "DLP-B60 Log into CTC" task at the node of the OSI routers that you want to provision.

Step 2 Click the Provisioning > OSI > Routers > Setup tabs.

Step 3 Chose the router you want provision and click Edit. The OSI Router Editor dialog box appears.

Step 4 In the OSI Router Editor dialog box:

a. Check Enable Router to enable the router and make its primary area address available for editing.

b. Click the manual area address, then click Edit.

c. In the Edit Manual Area Address dialog box, edit the primary area address in the Area Address field. If you prefer, click Use Mask and enter the edits in the Masked NSAP Entry dialog box. The address (hexadecimal format) can be 8 to 24 alphanumeric characters (0-9, a-f) in length.

d. Click OK successively to close the following dialog boxes: Masked NSAP Entry (if used), Edit Manual Area Address, and OSI Router Editor.

Step 5 Return to your originating procedure (NTP).


DLP-B179 Provision Additional Manual Area Addresses

Purpose

This task provisions the OSI manual area addresses. Three additional manual areas can be created for each virtual router.

Tools/Equipment

None

Prerequisite Procedures

B24 Verify Card Installation

B178 Provision OSI Routers

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 Click the Provisioning > OSI > Routers > Setup tabs.

Step 2 Chose the router where you want provision an additional manual area address and click Edit. The OSI Router Editor dialog box appears.

Step 3 In the OSI Router Editor dialog box:

a. Check Enable Router to enable the router and make its primary area address available for editing.

b. Click the manual area address, then click Add.

c. In the Add Manual Area Address dialog box, enter the primary area address in the Area Address field. If you prefer, click Use Mask and enter the address in the Masked NSAP Entry dialog box. The address (hexadecimal format) can be 2to 24 alphanumeric characters (0-9, a-f) in length.

d. Click OK successively to close the following dialog boxes: Masked NSAP Entry (if used), Add Manual Area Address, and OSI Router Editor.

Step 4 Return to your originating procedure (NTP).


DLP-B180 Enable the OSI Subnet on the LAN Interface

Purpose

This task enables the OSI subnetwork point of attachment on the LAN interface.

Tools/Equipment

None

Prerequisite Procedures

B24 Verify Card Installation

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Note OSI subnetwork points of attachment are enabled on DCCs when you create DCCs. See the "DLP-B253 Provision Section DCC Terminations" task and the "DLP-B24 Provision Line DCC Terminations" task.



Note The OSI subnetwork point of attachment cannot be enabled for the LAN interface if the OSI routing mode is set to ES (end system).



Note If Secure Mode is on, the OSI Subnet is enabled on the backplane LAN port, not the front TCC2P port.



Step 1 Complete the "DLP-B60 Log into CTC" task at the node whose OSI routers you want to provision.

Step 2 Click the Provisioning > OSI > Routers > Subnet tabs.

Step 3 Click Enable LAN Subnet.

Step 4 In the Enable LAN Subnet dialog box, complete the following fields:

ESH—Sets the End System Hello (ESH) propagation frequency. End system NEs transmit ESHs to inform other ESs and ISs about the NSAPs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

ISH—Sets the Intermediate System Hello PDU propagation frequency. Intermediate system NEs send ISHs to other ESs and ISs to inform them about the IS NETs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

IIH—Sets the Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The default is 3 seconds. The range is 1 to 600 seconds.

IS-IS Cost—Sets the cost for sending packets on the LAN subnet. The IS-IS protocol uses the cost to calculate the shortest routing path. The default IS-IS cost for LAN subnets is 20. It normally should not be changed.

DIS Priority—Sets the designated intermediate system (DIS) priority. In IS-IS networks, one router is elected to serve as the DIS (LAN subnets only). Cisco router DIS priority is 64. For the ONS 15454 LAN subnet, the default DIS priority is 63. It normally should not be changed.

Step 5 Click OK.

Step 6 Return to your originating procedure (NTP).


DLP-B181 Create an IP-Over-CLNS Tunnel

Purpose

This task creates an IP-over-CLNS tunnel to allow ONS 15327 nodes to communicate across equipment and networks that use the OSI protocol stack.

Tools/Equipment

None

Prerequisite Procedures

B24 Verify Card Installation

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution IP-over-CLNS tunnels require two end points. You will create one point on an ONS 15327. The other end point is generally provisioned on non-ONS equipment including routers and other vendor NEs. Before you begin, verify that you have the capability to create an OSI over IP tunnel on the other equipment location.


Step 1 Complete the "DLP-B60 Log into CTC" task at the node of the OSI routers that you want to provision.

Step 2 Click the Provisioning > OSI > Tunnels tabs.

Step 3 Click Create.

Step 4 In the Create IP Over OSI Tunnel dialog box, complete the following fields:

Tunnel Type—Choose a tunnel type:

Cisco—Creates the proprietary Cisco IP tunnel. Cisco IP tunnels add the CLNS header to the IP packets.

GRE—Creates a Generic Routing Encapsulation tunnel. GRE tunnels add the CLNS header and a GRE header to the IP packets.

The Cisco proprietary tunnel is slightly more efficient than the GRE tunnel because it does not add the GRE header to each IP packet. The two tunnel types are not compatible. Most Cisco routers support the Cisco IP tunnel, while only a few support both GRE and Cisco IP tunnels. You generally should create Cisco IP tunnels if you are tunneling between two Cisco routers or between a Cisco router and an ONS node.


Caution Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.

IP Address—Enter the IP address of the IP-over-CLNS tunnel destination.

IP Mask—Enter the IP address subnet mask of the IP-over-CLNS destination.

OSPF Metric—Enter the Open Shortest Path First (OSPF) metric for sending packets across the IP-over-CLNS tunnel. The OSPF metric, or cost, is used by OSPF routers to calculate the shortest path. The default is 110. Normally, it is not be changed unless you are creating multiple tunnel routes and want to prioritize routing by assigning different metrics.

NSAP Address—Enter the destination NE or OSI router NSAP address.

Step 5 Click OK.

Step 6 Provision the other tunnel end point using the documentation.

Step 7 Return to your originating procedure (NTP).


DLP-B182 Remove a TARP Manual Adjacency Table Entry

Purpose

This task removes an entry from the TARP manual adjacency table.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution If TARP manual adjacency is the only means of communication to a group of nodes, loss of visibility will occur when the adjacency table entry is removed.


Step 1 In node view, click the Provisioning > OSI > TARP > MAT tabs.

Step 2 Click the MAT entry that you want to delete.

Step 3 Click Remove.

Step 4 In the Delete TDC Entry dialog box, click OK.

Step 5 Return to your originating procedure (NTP).


DLP-B183 Change the OSI Routing Mode

Purpose

This task changes the OSI routing mode.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution Do not complete this procedure until you confirm the role of the node within the network. It will be either an ES or IS Level 1. This decision must be carefully considered. For additional information about OSI provisioning, refer to the "Management Network Connectivity" chapter of the Cisco ONS 15327 Reference Manual.


Caution LSP buffers must be the same at all NEs within the network, or loss of visibility could occur. Do not modify the LSP buffers unless you are sure that all NEs within the OSI have the same buffer size.


Caution LSP buffer sizes cannot be greater than the LAP-D MTU size within the OSI area.


Step 1 Verify that for OSI L1 to ES routing mode changes, only one L1 virtual router and no more than one subnet can be configured.

Step 2 In node view, click the Provisioning > OSI tabs.

Step 3 Choose End System. When End System is chosen, the ONS 15327 performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area.


Note Changing a routing mode should be carefully considered. Additional information about OSI ESs and ISs and the ES-IS and IS-IS protocols are provided in the "Management Network Connectivity" chapter of the Cisco ONS 15327 Reference Manual.


Step 4 Although Cisco does not recommend changing the LSP (Link State Protocol Data Unit) buffer sizes, you can change the L1 LSP Buffer Size field to change the Level 1 link state PDU buffer size.

Step 5 Return to your originating procedure (NTP).


DLP-B184 Edit the OSI Router Configuration

Purpose

This task allows you to edit the OSI router configuration, including enabling and disabling OSI routers, editing the primary area address, and creating or editing additional area addresses.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 Click the Provisioning > OSI > Routers > Setup tabs.

Step 2 Chose the router you want provision and click Edit.

Step 3 In the OSI Router Editor dialog box:

a. Check or uncheck the Enabled box to enable or disable the router.


Note Router 1 must be enabled before you can enable Routers 2 and 3.


b. For enabled routers, edit the primary area address, if needed. The address can be between 8 and 24 alphanumeric characters in length.

c. If you want to add or edit an area address to the primary area, enter the address at the bottom of the Multiple Area Addresses area. The area address can be 2 to 26 numeric characters (0-9) in length. Click Add.

d. Click OK.

Step 4 Return to your originating procedure (NTP).


DLP-B185 Edit the OSI Subnetwork Point of Attachment

Purpose

This task allows you to view and edit the OSI subnetwork point of attachment parameters. The parameters are initially provisioned when you create a Section DCC (SDCC), Line DCC (LDCC), generic communications channel (GCC), or optical service channel (OSC), or when you enable the LAN subnet.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In the node view, click the Provisioning > OSI > Routers > Subnet tabs.

Step 2 Choose the subnet you want to edit, then click Edit.

Step 3 In the Edit <subnet type> Subnet <slot/port> dialog box, edit the following fields:

ESH—The End System Hello PDU propagation frequency. An end system NE transmits ESHs to inform other ESs and ISs about the NSAPs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

ISH—The Intermediate System Hello PDU propagation frequency. An intermediate system NE sends ISHs to other ESs and ISs to inform them about the NETs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

IIH—The Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The default is 3 seconds. The range is 1 to 600 seconds.


Note The IS-IS Cost and DIS Priority parameters are provisioned when you create or enable a subnet. You cannot change the parameters after the subnet is created. To change the DIS Priority and IS-IS Cost parameters, delete the subnet and create a new one.


Step 4 Click OK.

Step 5 Return to your originating procedure (NTP).


DLP-B186 Edit an IP-Over-CLNS Tunnel

Purpose

This task allows you to edit the parameters of an IP-over-CLNS tunnel.

Tools/Equipment

None

Prerequisite procedures

B181 Create an IP-Over-CLNS Tunnel

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution Changing the IP or NSAP addresses or an IP-over-CLNS tunnel can cause loss of NE visibility or NE isolation. Do not change network addresses until you verify the changes with your network administrator.


Step 1 Click the Provisioning > OSI > Tunnels tabs.

Step 2 Click Edit.

Step 3 In the Edit IP Over OSI Tunnel dialog box, complete the following fields:

Tunnel Type—Edit the tunnel type:

Cisco—Creates the proprietary Cisco IP tunnel. Cisco IP tunnels add the CLNS header to the IP packets.

GRE—Creates a Generic Routing Encapsulation tunnel. GRE tunnels add the CLNS header and a GRE header to the IP packets.

The Cisco proprietary tunnel is slightly more efficient than the GRE tunnel because it does not add the GRE header to each IP packet. The two tunnel types are not compatible. Most Cisco routers support the Cisco IP tunnel, while only a few support both GRE and Cisco IP tunnels. You generally should create Cisco IP tunnels if you are tunneling between two Cisco routers or between a Cisco router and an ONS node.


Caution Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.

IP Address—Enter the IP address of the IP-over-CLNS tunnel destination.

IP Mask—Enter the IP address subnet mask of the IP-over-CLNS destination.

OSPF Metric—Enter the OSPF metric for sending packets across the IP-over-CLNS tunnel. The OSPF metric, or cost, is used by OSPF routers to calculate the shortest path. The default is 110. Normally, it is not be changed unless you are creating multiple tunnel routes and want to prioritize routing by assigning different metrics.

NSAP Address—Enter the destination NE or OSI router NSAP address.

Step 4 Click OK.

Step 5 Return to your originating procedure (NTP).


DLP-B187 Delete an IP-Over-CLNS Tunnel

Purpose

This task allows you to delete an IP-over-CLNS tunnel.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution Deleting an IP-over-CLNS tunnel might cause the nodes to loose visibility or cause node isolation. If node isolation occurs, onsite provisioning might be required to regain connectivity. Always confirm tunnel deletions with your network administrator.


Step 1 Click the Provisioning > OSI > Tunnels tabs.

Step 2 Choose the IP-over-CLNS tunnel that you want to delete.

Step 3 Click Delete.

Step 4 Click OK.

Step 5 Return to your originating procedure (NTP).


DLP-B188 View IS-IS Routing Information Base

Purpose

This task allows you to view the Intermediate System to Intermediate System (IS-IS) protocol routing information base (RIB). IS-IS is an OSI routing protocol that floods the network with information about NEs on the network. Each NE uses the information to build a complete and consistent picture of a network topology. The IS-IS RIB shows the network view from the perspective of the IS node.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In the node view, click the Maintenance > OSI > IS-IS RIB tabs.

Step 2 View the following RIB information for Router 1:

Subnet Type—Indicates the OSI subnetwork point of attachment type used to access the destination address. Subnet types include SDCC, LDCC, GCC, OSC, and LAN.

Location—Indicates the OSI subnetwork point of attachment. For DCC subnets, the slot and port are displayed. LAN subnets are shown as LAN.

Destination Address—The destination NSAP (network service access point) of the IS.

MAC Address—For destination NEs that are accessed by LAN subnets, the NE's Media Access Control address.

Step 3 If additional routers are enabled, you can view their RIBs by choosing the router number in the Router field and clicking Refresh.

Step 4 Return to your originating procedure (NTP).


DLP-B189 Verify That a 1+1 Working Slot Is Active

Purpose

This task verifies that a working slot in a 1+1 protection scheme is active (and that the protect slot is in standby).

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Maintenance or higher



Step 1 In node view, click the Maintenance > Protection tabs.

Step 2 In the Selected Group area, verify that the working slot/port is shown as Working/Active. If so, this task is complete.

Step 3 If the working slot says Working/Standby, perform a Manual switch on the working slot by completing the following steps:

a. In the Selected Group pane, choose the Protect/Active slot.

b. In the Switch Commands field, choose Manual.

c. Click Yes in the confirmation dialog box.

Step 4 Verify that the working slot is carrying traffic (Working/Active).


Note If the slot is not active, look for conditions or alarms that might be preventing the card from carrying working traffic. Refer to the Cisco ONS 15327 Troubleshooting Guide for procedures to resolve the alarms or conditions.


Step 5 When the working slot is carrying traffic, clear the Manual switch by completing the following steps:

a. In the Switch Commands field, choose Clear.

b. Click Yes in the confirmation dialog box.

Step 6 Verify that the working slot does not switch back to Standby, which might indicate a problem on the working span.

Step 7 Return to your originating procedure (NTP).


DLP-B190 View ES-IS Routing Information Base

Purpose

This task allows you to view the End System to Intermediate System (ES-IS) protocol RIB. ES-IS is an OSI protocol that defines how end systems (hosts) and intermediate systems (routers) learn about each other. For ESs, the ES-IS RIB shows the network view from the perspective of the ES node. For ISs, the ES-IS RIB shows the network view from the perspective of the IS node.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In the node view, click the Maintenance > OSI > ES-IS RIB tabs.

Step 2 View the following RIB information for Router 1:

Subnet Type—Indicates the OSI subnetwork point of attachment type used to access the destination address. Subnet types include SDCC, LDCC, GCC, OSC, and LAN.

Location—Indicates the subnet interface. For DCC subnets, the slot and port are displayed. LAN subnets are shown as LAN.

Destination Address—The destination IS NSAP (network service access point).

MAC Address—For destination NEs that are accessed by LAN subnets, the NE's Media Access Control address.

Step 3 If additional routers are enabled, you can view their RIBs by choosing the router number in the Router field and clicking Refresh.

Step 4 Return to your originating procedure (NTP).


DLP-B191 Manage the TARP Data Cache

Purpose

This task allows you to view and manage the TARP data cache (TDC). The TDC facilitates TARP processing by storing a list of TID to NSAP mappings.

Tools/Equipment

None

Prerequisite procedures

B60 Log into CTC

Required/As needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In the node view, click the Maintenance > OSI > TDC tabs.

Step 2 View the following TARP data cache information:

TID—The target identifier of the originating NE. For ONS 15327s, the TID is the name entered in the Node Name/TID field on the Provisioning > General tab.

NSAP/NET—The Network Service Access Point or Network Element Title of the originating NE.

Type—Indicates how the TARP data cache entry was created:

Dynamic—The entry was created through the TARP propagation process.

Static—The entry was manually created and is a static entry.

Step 3 If you want to query the network for an NSAP that matches a TID, complete the following steps. Otherwise, continue with Step 4.


Note The TID to NSAP function is not available if the TARP data cache is not enabled on the Provisioning > OSI > TARP subtab.


a. Click the TID to NSAP button.

b. In the TID to NSAP dialog box, enter the TID you want to map to an NSAP.

c. Click OK, then click OK on the information message.

d. On the TDC tab, click Refresh.

If TARP finds the TID in its TDC it returns the matching NSAP. If not, TARP sends PDUs across the network. Replies will return to the TDC later, and a check TDC later message is displayed.

Step 4 If you want to delete all the dynamically-generated TDC entries, click the Flush Dynamic Entries button. If not, continue with Step 5.

Step 5 Return to your originating procedure (NTP).


DLP-B194 Clear a BLSR Force Ring Switch

Purpose

Use this task to remove a BLSR Force ring switch.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite

Security Level

Provisioning or higher



Step 1 From the View menu, choose Go to Network View.

Step 2 Click the Provisioning > BLSR tabs.

Step 3 Click Edit.

Step 4 To clear a Force switch on the west line:

a. Right-click the BLSR west port where you want to clear the protection switch and choose Set West Protection Operation. Ports with a Force switch applied are marked with an F.

b. In the Set West Protection Operation dialog box, choose CLEAR from the drop-down list. Click OK.

c. In the Confirm BLSR Operation dialog box, click Yes.

Step 5 To clear a Force switch on the east line:

a. Right-click the BLSR east port where you want to clear the protection switch and choose Set East Protection Operation. Ports with a Force switch applied are marked with an F.

b. In the Set East Protection Operation dialog box, choose CLEAR from the drop-down list. Click OK.

c. In the Confirm BLSR Operation dialog box, click Yes.

On the BLSR network graphic, a green and a purple span line connects each node. This is the normal display for BLSR spans when a protection switch is not present.

Step 6 From the File menu, choose Close.

Step 7 Return to your originating procedure (NTP).


DLP-B195 Verify Timing in a Reduced Ring

Purpose

Use this task to verify timing in the ring where you removed a node.

Tools/Equipment

None

Prerequisite Procedures

B213 Remove a BLSR Node or

B106 Remove a Path Protection Node

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, click the Provisioning > Timing > General tabs.

Step 2 Identify the type of timing (Line, External, Mixed) in the Timing Mode field.

Step 3 Scroll down to the Reference Lists and observe the NE Reference fields to see the timing references provisioned for that node.

Step 4 If the removed node was the only BITS timing source, perform the following steps:

a. Look for another node on the ring that can be used as a BITS source and set that node's Timing Mode to External. Choose that node as the primary timing source for all other nodes in the ring. See the "DLP-B157 Change the Node Timing Source" task.

b. If no node in the reduced ring can be used as a BITS source, choose one node to be your internal timing source. Set that node's Timing Mode to External, set the BITS 1 and 2 State field to OOS, and set the NE Reference to Internal Clock. Then, choose line timing for all other nodes in the ring. This forces the first node to be their primary timing source. See the "DLP-B157 Change the Node Timing Source" task.


Note Internal timing conforms to Stratum 3 requirements and is not considered optimal.


Step 5 If the removed node was not the only BITS timing source, provision the adjacent nodes to line timing using SONET links (east and west) as timing sources, traceable to the node with external BITS timing. See the "NTP-B28 Set Up Timing" procedure.

Step 6 Return to your originating procedure (NTP).


DLP-B196 Delete a BLSR from a Single Node

Purpose

Use this task to delete a BLSR from a node after you remove the node from the BLSR.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 In node view, display the node that was removed from the BLSR by completing the appropriate step:

If the node that was removed is connected to the same LAN as your computer, from the File menu, choose Add Node, then enter the node name or IP address.

If the node that was removed is not connected to the same LAN as your computer, you must connect to the node using a direct connection. See Chapter 2 "Connect the PC and Log into the GUI," for procedures.

Step 2 Click the Provisioning > BLSR tabs.

Step 3 Highlight the ring and click Delete.

Step 4 In the Suggestion dialog box, click OK.

Step 5 In the confirmation message, confirm that this is the ring you want to delete. If so, click Yes.

Step 6 Return to your originating procedure (NTP).


DLP-B197 Initiate a Path Protection Force Switch

Purpose

Use this task to switch all circuits on a path protection span to another span.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Caution Traffic is not protected during Force path protection switches.


Step 1 From the View menu choose Go to Network View.

Step 2 Right-click the span where you want to force switch path protection traffic. Choose Circuits from the shortcut menu.

Step 3 In the Circuits on Span dialog box, choose FORCE SWITCH AWAY. Click Apply.

Step 4 In the Confirm Path Protection Switch dialog box, click Yes.

Step 5 In the Protection Switch Result dialog box, click OK.

In the Circuits on Span window, the Switch State for all circuits is FORCE. Figure 17-17 shows an example.

Figure 17-17 Circuits on Span Dialog Box with a Force Switch


Note A Force switch request on a span or card causes CTC to raise a FORCED-REQ condition. The condition clears when you clear the Force switch; it is informational only.


Step 6 Return to your originating procedure (NTP).


DLP-B198 Clear a Path Protection Switch

Purpose

Use this task to clear a path protection Force switch.

Tools/Equipment

None

Prerequisite Procedures

B60 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



Step 1 From the View menu, choose Go to Network View.

Step 2 Right-click the span where you want to clear the switch. Choose Circuits from the shortcut menu.

Step 3 In the Circuits on Span dialog box, choose CLEAR to remove the switch. Click Apply.

Step 4 In the Confirm Path Protection Switch dialog box, click Yes.

Step 5 In the Protection Switch Result dialog box, click OK.

In the Circuits on Span window, the Switch State for all path protection circuits is CLEAR.

Step 6 Return to your originating procedure (NTP).


DLP-B199 Inspect, Clean, and Replace the Reusable Air Filter

Purpose

This task ensures that the air filter is free from dirt and dust, which allows optimum air flow and prevents dirt and dust from entering the shelf.

Tools/Equipment

Vacuum or detergent

Water faucet

Spare filter

Pinned hex key tool

Prerequisite Procedures

None

Required/As Needed

As needed

Onsite/Remote

Onsite

Security Level

None



Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206

Caution Inspect the air filter every 30 days, and clean the filter every three to six months. Replace the air filter every two to three years. Avoid cleaning the air filter with harsh cleaning agents or solvents.


Step 1 Verify that you are replacing a reusable air filter. The reusable filter is made of a gray, open-cell, polyurethane foam that is specially coated to provide fire and fungi resistance. NEBS 3E and later versions of the ONS 15327 use a reusable air filter.

Step 2 Move any cables that are routed in front of the fan-tray assembly and air filter so that you can easily slide the filter out (Figure 17-18).

Step 3 Grasp the metal tab at the edge of the filter and slide the filter out of the bracket while being careful not to dislodge any dust that might have collected on the filter.

Figure 17-18 Removing the Reusable Fan-Tray Air Filter

Step 4 Visually inspect the filter material for dirt and dust.

Step 5 If the reusable air filter contains a concentration of dirt and dust, either vacuum the dirty air filter or wash it. Prior to washing the air filter, replace the dirty air filter with a spare clean air filter. Spare filters should be kept in stock.

Step 6 Wash the dirty air filter under a faucet with a light detergent. After washing the air filter, allow it to completely air dry for at least eight hours before reusing.


Note Cleaning should take place outside the operating environment to avoid releasing dirt and dust near the equipment.



Caution Do not put a damp filter back in the ONS 15327.

Step 7 Slide the clean air filter back into the shelf (Figure 17-19).

Figure 17-19 Replacing the Reusable Fan-Tray Air Filter

Step 8 Return to your originating procedure (NTP).