Table Of Contents
DLPs B300 to B399
DLP-B301 Initiate a BLSR Manual Ring Switch
DLP-B303 Initiate a BLSR Force Ring Switch
DLP-B305 View J1 Path Trace Information on a G1000-2 Card
DLP-B306 View the Loopback Status on a G1000-2 Card
DLP-B307 View Ethernet Bandwidth Usage on a G1000-2 Card
DLP-B309 View Ethernet MAC Address Table
DLP-B310 View Ethernet Trunk Utilization
DLP-B313 Create a DCC Tunnel
DLP-B314 Assign a Name to a Port
DLP-B315 Log Out a User on a Single Node
DLP-B316 Log Out a User on Multiple Nodes
DLP-B317 View Optical OC-N PM Parameters
DLP-B318 Refresh Electrical or Optical PM Counts at One-Day Intervals
DLP-B319 Monitor PM Counts for Selected Signal Types
DLP-B320 Delete a Card
DLP-B321 Install External Alarm Cables
DLP-B322 Install Timing Cables
DLP-B323 Install the Serial Cable for TL1 Craft Interface
DLP-B324 Install DS-1 Champ Cables on a MIC
DLP-B325 Install Coaxial Cable with BNC Connectors
DLP-B326 Route Electrical Cables
DLP-B327 Install Fiber-Optic Cables on the LGX Interface
DLP-B328 Install Public-Key Security Certificate
DLP-B329 Install the Tie-Down Bar
DLP-B330 Manual or Force Switch the Node Timing Reference
DLP-B331 Clear a Manual or Force Switched Node Timing Reference
DLP-B332 View Circuit Information
DLP-B334 Create Ethernet RMON Alarm Thresholds
DLP-B335 Delete Ethernet RMON Alarm Thresholds
DLP-B336 Create a BLSR Using the BLSR Wizard
DLP-B337 Create a BLSR Manually
DLP-B338 Manually Route a Path Protection Circuit for a Topology Upgrade
DLP-B339 Automatically Route a Path Protection Circuit for a Topology Upgrade
DLP-B340 View the BLSR STS Squelch Table
DLP-B341 View the BLSR VT Squelch Table
DLPs B300 to B399
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-B301 Initiate a BLSR Manual Ring Switch
Purpose
|
This task performs a bidirectional line switched ring (BLSR) Manual ring switch. A Manual ring switch will switch traffic off a span if there is no higher priority switch (Force or lock out) and no signal degrade (SD) or signal failure (SF) conditions.
|
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 Provisioning > BLSR tabs.
Step 3 Choose the BLSR and click Edit.
Tip To move an icon to a new location, for example, to see BLSR channel (port) information more clearly, click an icon and drag and drop it in a new location.
Step 4 Right-click any BLSR node channel (port) and choose Set West Protection Operation (if you chose a west channel) or Set East Protection Operation (if you chose an east channel).
Note The squares on the node icons represent the BLSR working and protect channels. You can right-click either channel.
Step 5 In the Set West Protection Operation dialog box or the Set East Protection Operation dialog box, choose MANUAL RING from the drop-down list. Click OK.
Step 6 Click Yes in the two Confirm BLSR Operation dialog boxes.
Step 7 Verify that the channel (port) displays the letter "M" for MANUAL ring. Also verify that the span lines between the nodes where the Manual switch was invoked turn purple, and that the span lines between all other nodes turn green. This confirms the Manual switch.
Step 8 From the File menu, choose Close.
Step 9 Return to your originating procedure (NTP).
DLP-B303 Initiate a BLSR Force Ring Switch
Purpose
|
Use this task to perform a BLSR Force protection operation on a BLSR port. A Force ring switch will switch traffic off a span if there is no higher priority switch (lock out) in place.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
Provisioning or higher
|
Caution Traffic is not protected during a Force protection switch.
Note A Force switch request on a span or card causes CTC to raise a FORCED-REQ condition. It is informational only; the condition will clear when the Force switch command is cleared.
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 apply a Force switch to the west line:
a. Right-click the west BLSR port where you want to switch the BLSR traffic and choose Set West Protection Operation.
Note If node icons overlap, drag and drop the icons to a new location. Or, return to network view and change the positions of the network node icons, since BLSR node icons are based on the network view node icon positions.
b. In the Set West Protection Operation dialog box, choose FORCE RING from the drop-down list. Click OK.
c. Click Yes in the two Confirm BLSR Operation dialog boxes that appear.
On the network graphic, an F appears on the working BLSR channel where you invoked the protection switch. The span lines change color to reflect the forced traffic. Green span lines indicate the new BLSR path, and the lines between the protection switch are purple.
Performing a Force switch generates several conditions including FORCED-REQ-RING, FORCED-REQ-RING, and WKSWPR.
Step 5 To apply a Force switch to the east line:
a. Right-click the east BLSR port and choose Set East Protection Operation.
Note If node icons overlap, drag and drop the icons to a new location. Or, return to network view and change the positions of the network node icons, since BLSR node icons are based on the network view node icon positions.
Note The squares on the node icons represent the BLSR working and protect channels. You can right-click either channel.
b. In the Set East Protection Operation dialog box, choose FORCE RING from the drop-down list. Click OK.
c. Click Yes in the two Confirm BLSR Operation dialog boxes that appear.
On the network graphic, an F appears on the working BLSR channel where you invoked the protection switch. The span lines change color to reflect the forced traffic. Green span lines indicate the new BLSR path, and the lines between the protection switch are purple.
Performing a Force switch generates several conditions including FORCED-REQ-RING, FORCED-REQ-RING, and WKSWPR.
Step 6 From the File menu, choose Close.
Step 7 Return to your originating procedure (NTP).
DLP-B305 View J1 Path Trace Information on a G1000-2 Card
Purpose
|
This task displays J1 path trace information on a selected G1000-2 Ethernet card.
|
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 a G1000-2 Ethernet card. The card view appears.
Step 2 Click the Maintenance > J1 Path Trace tabs.
Step 3 Click Retrieve.
View columns to the right to the J1 Path Trace information for each port on the card.
Step 4 Return to your originating procedure (NTP).
DLP-B306 View the Loopback Status on a G1000-2 Card
Purpose
|
Use this task to view the loopback status on a selected G1000-2 Ethernet card 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 a G1000-2 Ethernet card. The card view appears.
Step 2 Click the Maintenance > Loopback tabs.
The # and Service State columns identify the port number and current operating state (In-Service and Normal [IS-NR], Out-of-Service and Autonomous, Automatic In-Service [OOS-AU,AINS], Out-of-Service and Management, Disabled [OOS-MA,DSBLD], or Out-of-Service and Management, Maintenance [OOS-MA,MT]) of each port on the card. The Loopback Type column identifies the type of loopback (None or Terminal) applied to each port on the card.
Step 3 Return to your originating procedure (NTP).
DLP-B307 View Ethernet Bandwidth Usage on a G1000-2 Card
Purpose
|
Use this task to view the Ethernet bandwidth usage on a selected G1000-2 Ethernet card.
|
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 a G1000-2 Ethernet card. The card view appears.
Step 2 Click the Maintenance > Bandwidth tabs.
The current Synchronous Transport Signal (STS) bandwidth usage information appears.
Step 3 Return to your originating procedure (NTP).
DLP-B309 View Ethernet MAC Address Table
Purpose
|
This task displays the Ethernet MAC address table for any node with one or more E10/100-4 Ethernet cards installed.
|
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, click the Maintenance > Ether Bridge > MAC Table tabs.
Step 2 Select the appropriate E10/100-4 Ethernet card in the Layer 2 Domain field.
Step 3 Click Retrieve.
The MAC address table information appears.
Step 4 Return to your originating procedure (NTP).
DLP-B310 View Ethernet Trunk Utilization
Purpose
|
This task displays the Ethernet trunk bandwidth usage on any node with one or more E10/100-4 Ethernet cards installed.
|
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, click the Maintenance > Ether Bridge > Trunk Utilization tabs.
Step 2 Select a time interval in the Interval field.
Step 3 Click Refresh.
The trunk utilization information for the current and previous time intervals appears.
Step 4 Return to your originating procedure (NTP).
DLP-B313 Create a DCC Tunnel
Purpose
|
This task creates a Data Communications Channel (DCC) tunnel to transport traffic from third-party SONET equipment across ONS 15327 networks. Tunnels can be created on the Section DCC channel (D1-D3) (if not used by the ONS 15327 as a terminated DCC), or any Line DCC channel (D4-D6, D7-D9, or D10-D12).
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B127 Verify Network Turn-Up
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Note Each ONS 15327 can have up to 32 DCC tunnel connections. Terminated Section DCCs used by the ONS 15327 cannot be used as DCC tunnel endpoints, and a Section DCC that is used as an DCC tunnel endpoint cannot be terminated. All DCC tunnel connections are bidirectional.
Step 1 In network view, click the Provisioning > Overhead Circuits tabs.
Step 2 Click Create.
Step 3 In the Overhead Circuit Creation dialog box, complete the following in the Circuit Attributes area:
•Name—Enter the tunnel name.
•Circuit Type—Choose one:
–DCC Tunnel-D1-D3—Allows you to choose either the Section DCC (D1-D3) or a Line DCC (D4-D6, D7-D9, or D10-D12) as the source or destination endpoints.
–DCC Tunnel-D4-D12—Provisions the full Line DCC as a tunnel.
Step 4 Click Next.
Step 5 In the Circuit Source area, complete the following:
•Node—Choose the source node.
•Slot—Choose the source slot.
•Port—If available, choose the source port.
•Channel—These options appear if you chose DCC Tunnel-D1-D3 as the tunnel type. Choose one of the following:
–DCC1 (D1-D3)—Section DCC
–DCC2 (D4-D6)—Line DCC 1
–DCC3 (D7-D9)—Line DCC 2
–DCC4 (D10-D12)—Line DCC 3
DCC options do not appear if they are used by the ONS 15327 (DCC1) or other tunnels.
Step 6 In the Circuit Destination area, complete the following:
•Node—Choose the destination node.
•Slot—Choose the destination slot.
•Port—If available, choose the destination port.
•Channel—These options appear if you chose DCC Tunnel-D1-D3 as the tunnel type. Choose one of the following:
–DCC1 (D1-D3)—Section DCC
–DCC2 (D4-D6)—Line DCC 1
–DCC3 (D7-D9)—Line DCC 2
–DCC4 (D10-D12)—Line DCC 3
DCC options do not appear if they are used by the ONS 15327 (DCC1) or other tunnels.
Step 7 Click Finish.
Step 8 Put the ports that are hosting the DCC tunnel in service. See the "DLP-B214 Change the Service State for a Port" task for instructions.
Step 9 Return to your originating procedure (NTP).
DLP-B314 Assign a Name to a Port
Step 1 Double-click the OC-N or XTC card that has the port you want to provision.
Step 2 Click the Provisioning tab.
Step 3 Click the Port Name column for the port number you are assigning a name to and enter the desired port name.
The port name can be up to 32 alphanumeric/special characters and is blank by default.
Step 4 Click Apply.
Step 5 Return to your originating procedure (NTP).
DLP-B315 Log Out a User on a Single Node
Purpose
|
This task logs out a 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
|
Step 1 In node view, click the Provisioning > Security > Active Logins tabs.
Step 2 Choose the user you want to log out and click Logout.
Step 3 In the Logout User dialog box, check Lockout before Logout if you want to prevent the user from logging in after logout. User lockout parameters provisioned in the Policy tab determine when the user can log back in. Either a manual unlock by a Superuser is required or the user is locked out for the amount of time specified in the Lockout Duration field. See the "DLP-B271 Change Security Policy on a Single Node" task for more information.
Step 4 Click OK.
Step 5 Click Yes to confirm the logout.
Step 6 Return to your originating procedure (NTP).
DLP-B316 Log Out a User on Multiple Nodes
Purpose
|
This task logs out a 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
|
Step 1 From the view menu, choose Go to Network View.
Step 2 Click the Provisioning > Security > Active Logins tabs.
Step 3 Choose the user you want to log out.
Step 4 Click Logout.
Step 5 In the Logout User dialog box, check the nodes where you want to log out the user.
Step 6 Check Lockout before Logout if you want to prevent the user from logging in after logout. User lockout parameters provisioned in the Policy tab determine when the user can log back in. Either a manual unlock by a Superuser is required or the user is locked out for the amount of time specified in the Lockout Duration field. See the "DLP-B271 Change Security Policy on a Single Node" task for more information.
Step 7 Click OK.
Step 8 Click Yes to confirm the logout.
Step 9 Return to your originating procedure (NTP).
DLP-B317 View Optical OC-N PM Parameters
Purpose
|
This task enables you to view PM counts on an optical (OC-N) card and port 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 OC-N card. The card view appears.
Step 2 Click the Performance tab (Figure 19-1).
Figure 19-1 Viewing Optical Performance Monitoring Information
Step 3 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-B318 Refresh Electrical or Optical PM Counts at One-Day Intervals
Purpose
|
This task changes the window to display PM parameters in 1-day 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 1 day radio button.
Step 4 Click Refresh. Performance monitoring appears in 1-day intervals synchronized with the time of day.
Step 5 View the Curr column to find PM counts for the current 1-day 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 1-day interval, a Threshold Crossing Alert (TCA) is raised. The PM number represents the counter value for each performance monitoring parameter.
Step 6 View the Prev-n columns to find PM counts for the previous 1-day intervals.
Note If a complete count over a 1-day interval is not possible, the value appears with a yellow background. An incomplete or incorrect count can be caused by monitoring for less than 24 hours 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 1-day interval appears with a white background.
Step 7 Return to your originating procedure (NTP).
DLP-B319 Monitor PM Counts for Selected Signal Types
Purpose
|
This task enables you to monitor near-end or far-end PM counts for specific signals on a 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.
Note Different port and signal-type menus appear depending on the card type and the circuit type. The appropriate types (DS1, DS3, VT path, STS path, OC-N section and OC-N line) appear based on the card. For example, the OC-48 card lists the OC-48 port and STS path PM parameters as signal-types. You can select both the OC-48 port and the STS within the specified OC-48.
Step 3 Click the Port/Line drop-down list and highlight the desired port/line. (Options vary depending on the card.)
Step 4 Click the Signal Type drop-down list and highlight the desired signal. (Options vary depending on the card.)
Step 5 Click Refresh. All PM counts recorded by the near-end or far-end node appear for the specified outgoing signal type on the selected card and port. For PM parameter definitions, refer to the "Performance Monitoring" chapter in the Cisco ONS 15327 Reference Manual.
Step 6 View the Curr column to find PM counts for the current time interval.
Step 7 View the Prev-n columns to find PM counts for the previous time intervals.
Step 8 Return to your originating procedure (NTP).
DLP-B320 Delete a Card
Purpose
|
This task deletes a card from CTC.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Both
|
Security Level
|
Provisioning or higher
|
Step 1 On the shelf graphic, right-click the card that you want to remove and choose Delete Card.
You cannot delete a card if any of the following conditions apply:
•The card is one of two installed XTC cards (a default XTC protection group was created); to replace an XTC card, refer to the Cisco ONS 15327 Troubleshooting Guide.
•The card is part of a protection group; see the "DLP-B155 Delete a 1+1 Protection Group" task.
•The card has circuits; see the "DLP-B13 Delete Circuits" task.
•The card is part of a BLSR; see the "B213 Remove a BLSR Node" procedure.
•The card is being used for timing; see the "DLP-B69 Set Up External or Line Timing" task.
Note If you do not remove a card from the shelf after you delete it in CTC, it will reboot and reappear in CTC.
Step 2 Return to your originating procedure (NTP).
DLP-B321 Install External Alarm Cables
Purpose
|
This task installs alarm cables on the Mechanical Interface Cards (MICs) so that you can provision external (environmental) alarms and controls.
|
Tools/Equipment
|
Alarm cable, CAT-5 terminated with RJ-45 for all alarm connections
|
Prerequisite Procedures
|
NTP-B216 Install the Mechanical Interface Cards, page 1-5
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
None
|
Step 1 Plug one end of the alarm cable into the ALARM port on the MIC.
Step 2 Plug the other end of the cable into the alarm-collection equipment according to local site practice.
Step 3 Repeat Steps 1 and 2 for the other MIC.
Note You can use the alarm cutoff (ACO) button to extinguish audible alarms.
Step 4 To define the six external alarm inputs and two external alarm outputs using CTC, see the "NTP-B32 Provision External Alarms and Controls on the XTC" procedure on page 8-7. Table 19-1 shows the input alarm pinouts and the corresponding alarm numbers assigned to each MIC/port. Table 19-2 shows the output alarm pinouts. Refer to these tables when connecting alarm cables to the ONS 15327.
Table 19-1 Alarm Input Pin Assignments
Alarm Number (MIC A)
|
Alarm Number (MIC B)
|
RJ-45 Pin Number
|
Function
|
2
|
1
|
5
|
Alarm 2+
|
6
|
Alarm 2-
|
4
|
3
|
3
|
Alarm 1+
|
4
|
Alarm 1-
|
6
|
5
|
1
|
Alarm 0+
|
2
|
Alarm 0-
|
Table 19-2 Alarm (External Control) Output Pin Assignments
Alarm Number (MIC A)
|
Alarm Number (MIC B)
|
RJ-45 Pin Number
|
Function
|
2
|
1
|
7
|
Contact+
|
8
|
Contact-
|
Figure 19-2 shows RJ-45 pin numbering.
Figure 19-2 Pins 1 and 8 on the RJ-45 Connector
Step 5 Return to your originating procedure (NTP).
DLP-B322 Install Timing Cables
Purpose
|
This task installs timing cables on the MICs so that you can provide BITS timing to the ONS 15327.
|
Tools/Equipment
|
#22 or #24 shielded AWG wire
|
Prerequisite Procedures
|
NTP-B216 Install the Mechanical Interface Cards, page 1-5
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
None
|
Step 1 Plug one end of the timing cable into the BITS port on the MIC.
Step 2 Plug the other end of the cable into the BITS clock according to local site practice.
Step 3 Repeat Steps 1 and 2 for the other MIC. Table 19-3 shows the BITS cable pin assignments.
Table 19-3 BITS Cable Pin Assignments
MIC A
|
MIC B
|
RJ-45 Pin Number
|
Function
|
BITS 1 In
|
BITS 2 In
|
3
|
BITS Input+
|
4
|
BITS Input-
|
BITS 1 Out
|
BITS 2 Out
|
7
|
BITS Output+
|
8
|
BITS Output-
|
Figure 19-3 shows the BITS In pins on the RJ-45 connector.
Figure 19-3 BITS In Pins on the RJ-45 Connector
Figure 19-4 shows the BITS Out pins on the RJ-45 connector.
Figure 19-4 BITS Out Pins on the RJ-45 Connector
Table 19-4 shows the external timing pin assignments for BITS timing.
Table 19-4 External Timing Pin Assignments for BITS
External Device
|
Contact
|
Tip and Ring
|
Function
|
First external device
|
A3 (BITS 1 Out)
|
Primary ring (-)
|
Output to external device
|
B3 (BITS 1 Out)
|
Primary tip (+)
|
Output to external device
|
A4 (BITS 1 In)
|
Secondary ring (-)
|
Input from external device
|
B4 (BITS 1 In)
|
Secondary tip (+)
|
Input from external device
|
Second external device
|
A1 (BITS 2 Out)
|
Primary ring (-)
|
Output to external device
|
B1 (BITS 2 Out)
|
Primary tip (+)
|
Output to external device
|
A2 (BITS 2 In)
|
Secondary ring (-)
|
Input from external device
|
B2 (BITS 2 In
|
Secondary tip (+)
|
Input from external device
|
Note For more detailed information about timing, refer to the "Timing" chapter in the Cisco ONS 15327 Reference Manual. To set up system timing, see the "NTP-B28 Set Up Timing" procedure on page 3-8.
Step 4 Return to your originating procedure (NTP).
DLP-B323 Install the Serial Cable for TL1 Craft Interface
Step 1 Plug one end of the serial cable into the front of the XTC card.
Step 2 Connect the other end to the PC you want to use to access the craft.
Note You can connect to either the active or standby XTC DB-9 plug to gain terminal access, but not both simultaneously.
Step 3 Return to your originating procedure (NTP).
DLP-B324 Install DS-1 Champ Cables on a MIC
Purpose
|
This task installs DS-1 cables.
|
Tools/Equipment
|
One of the following DS-1 cables (either right-angle or straight):
•Third-party right-angle DS-1 cable
•Cisco straight DS-1 cable
Refer to the "Shelf Assembly Hardware" chapter in the Cisco ONS 15327 Reference Manual for specific information about DS-1 cables and DS-1 connectors, including product numbers and compatibility.
|
Prerequisite Procedures
|
NTP-B8 Install Wires to Alarm, Timing, LAN, and Craft Pin Connections, page 1-13
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
None
|
Caution Always use the supplied ESD wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots.
Step 1 Prepare a 56-wire cable for each DS-1 connection you will make. See Table 19-5 for the ONS 15327 Champ connector pin assignments.
The shaded area in the table corresponds to the white/orange binder group.
Table 19-5 Pin Assignments for Champ Connector
Signal/Wire
|
Pin
|
Pin
|
Signal/Wire
|
Signal/Wire
|
Pin
|
Pin
|
Signal/Wire
|
Tx Tip 1
white/blue
|
1
|
33
|
Tx Ring 1
blue/white
|
Rx Tip 1
yellow/orange
|
17
|
49
|
Rx Ring 1
orange/yellow
|
Tx Tip 2 white/orange
|
2
|
34
|
Tx Ring 2
orange/white
|
Rx Tip 2
yellow/green
|
18
|
50
|
Rx Ring 2
green/yellow
|
Tx Tip 3
white/green
|
3
|
35
|
Tx Ring 3
green/white
|
Rx Tip 3
yellow/brown
|
19
|
51
|
Rx Ring 3
brown/yellow
|
Tx Tip 4
white/brown
|
4
|
36
|
Tx Ring 4
brown/white
|
Rx Tip 4
yellow/slate
|
20
|
52
|
Rx Ring 4
slate/yellow
|
Tx Tip 5
white/slate
|
5
|
37
|
Tx Ring 5
slate/white
|
Rx Tip 5
violet/blue
|
21
|
53
|
Rx Ring 5
blue/violet
|
Tx Tip 6
red/blue
|
6
|
38
|
Tx Ring 6
blue/red
|
Rx Tip 6
violet/orange
|
22
|
54
|
Rx Ring 6
orange/violet
|
Tx Tip 7
red/orange
|
7
|
39
|
Tx Ring 7
orange/red
|
Rx Tip 7
violet/green
|
23
|
55
|
Rx Ring 7
green/violet
|
Tx Tip 8
red/green
|
8
|
40
|
Tx Ring 8
green/red
|
Rx Tip 8
violet/brown
|
24
|
56
|
Rx Ring 8
brown/violet
|
Tx Tip 9
red/brown
|
9
|
41
|
Tx Ring 9
brown/red
|
Rx Tip 9
violet/slate
|
25
|
57
|
Rx Ring 9
slate/violet
|
Tx Tip 10
red/slate
|
10
|
42
|
Tx Ring 10
slate/red
|
Rx Tip 10
white/blue
|
26
|
58
|
Rx Ring 10
blue/white
|
Tx Tip 11
black/blue
|
11
|
43
|
Tx Ring 11
blue/black
|
Rx Tip 11
white/orange
|
27
|
59
|
Rx Ring 11
orange/white
|
Tx Tip 12
black/orange
|
12
|
44
|
Tx Ring 12
orange/black
|
Rx Tip 12
white/green
|
28
|
60
|
Rx Ring 12
green/white
|
Tx Tip 13
black/green
|
13
|
45
|
Tx Ring 13
green/black
|
Rx Tip 13
white/brown
|
29
|
61
|
Rx Ring 13
brown/white
|
Tx Tip 14
black/brown
|
14
|
46
|
Tx Ring 14
brown/black
|
Rx Tip 14
white/slate
|
30
|
62
|
Rx Ring 14
slate/white
|
Tx Spare 0+ N/A
|
15
|
47
|
Tx Spare0- N/A
|
Rx Spare0+ N/A
|
31
|
63
|
Rx Spare 0- N/A
|
Tx Spare 1+ N/A
|
16
|
48
|
Tx Spare1- N/A
|
Rx Spare1+ N/A
|
32
|
64
|
Rx Spare 1- N/A
|
Step 2 Connect the male Champ connector on the cable to the female Champ connector on the ONS 15327 MIC.
The DS-1 cable can have a straight or right-angle configuration. Figure 19-5 shows a straight DS-1 cable.
Note To install the right-angle DS-1 cable, you must have the screw-lock power connector installed.
Figure 19-5 Straight DS-1 Cable
Figure 19-6 shows a right-angle DS-1 cable.
Figure 19-6 Right-Angle DS-1 Cable
Step 3 Use the screws on the male connector to secure the connection. Figure 19-7 shows a straight DS-1 cable installation.
Figure 19-7 Installing a Straight DS-1 Cable
Step 4 Return to your originating procedure (NTP).
DLP-B325 Install Coaxial Cable with BNC Connectors
Purpose
|
This task installs the coaxial cable with BNC connectors to connect DS-3 signals to the ONS 15327.
|
Tools/Equipment
|
Shielded coaxial cable terminated with BNC connectors for DS-3 ports
|
Prerequisite Procedures
|
None
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
None
|
Caution Always use the supplied ESD wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots.
Step 1 Place a BNC cable connector over the connector on the MIC.
Figure 19-8 shows how to connect a coaxial cable to an ONS 15327 MIC.
Figure 19-8 Installing a Coaxial Cable with BNC Connectors
Step 2 Position the cable connector so that the slot in the connector is above the corresponding notch on the MIC connection point.
Step 3 Gently push the connector down until the notch on the MIC connector slides into the slot on the cable connector.
Step 4 Turn the cable connector until the notch clicks into place.
Step 5 Return to your originating procedure (NTP).
DLP-B326 Route Electrical Cables
Step 1 Route the cables to the nearest side of the shelf assembly through the side cutouts according to local site practice.
Step 2 Label all cables at each end of the connection to avoid confusion with cables that are similar in appearance.
Step 3 Return to your originating procedure (NTP).
DLP-B327 Install Fiber-Optic Cables on the LGX Interface
Step 1 Align the keyed ridge of the cable connector with the receiving SC connector on the LGX faceplate connection point. Each module supports at least one transmit and one receive connector to create an optical carrier port.
Step 2 Gently insert the cable connector into the faceplate connection point until the connector snaps into place.
Step 3 Connect the fiber optic cable to the OC-N card. See the "DLP-B42 Install Fiber-Optic Cables in a 1+1 Configuration" task.
Step 4 Return to your originating procedure (NTP).
DLP-B328 Install Public-Key Security Certificate
Purpose
|
This task installs the ITU Recommendation X.509 public-key security certificate. The public-key certificate is required to run Software Release 4.1 or later.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
This task is performed during the "DLP-B60 Log into CTC" task. You cannot perform it outside of this task.
|
Required/As Needed
|
Required
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 If the Java Plug-in Security Warning dialog box appears, choose one of the following options:
•Yes (Grant This Session)—Installs the public-key certificate to your PC only for the current session. After the session is ended, the certificate is deleted. This dialog box will appear the next time you log into the ONS 15327.
•No (Deny)—Denies permission to install certificate. If you choose this option, you cannot log into the ONS 15327.
•Always (Grant Always)—Installs the public-key certificate and does not delete it after the session is over. Cisco recommends this option.
•More Details (View Certificate)—Allows you to view the public-key security certificate.
Step 2 If the Login dialog box appears, continue with Step 4. If the Change Java Policy File dialog box appears, complete this step. The Change Java Policy File dialog box appears if CTC finds a modified Java policy file (.java.policy) on your PC. In Software Release 4.0 and earlier, the Java policy file was modified to allow CTC software files to be downloaded to your PC. The modified Java policy file is not needed in Software Release 4.1 and later, so you can remove it unless you will log into ONS 15327s running software earlier than Release 4.1. Choose one of the following options:
•Yes—Removes the modified Java policy file from your PC. Choose this option only if you will log into ONS 15327s running Software Release 4.1 software or later.
•No—Does not remove the modified Java policy file from your PC. Choose this option if you will log into ONS 15327s running Software Release 4.0 or earlier. If you choose No, this dialog box will appear every time you log into the ONS 15327. If you do not want it to appear, check the Do not show the message again check box.
Step 3 If you delete the Java policy file, you cannot log into nodes running Software Release 4.0 and earlier. If you delete the file and want to log into an ONS 15327 running an earlier release, insert the software CD for the release into your PC CD-ROM and run the CTC setup wizard to reinstall the Java policy file.
Step 4 Return to "DLP-B60 Log into CTC" task.
DLP-B329 Install the Tie-Down Bar
Purpose
|
This task installs the tie-down bar used to secure cabling on the ONS 15327. The tie-down bar can be used to provide a diverse path for redundant power feeds and cables.
|
Tools/Equipment
|
Tie-down bar
Screws (4)
|
Prerequisite Procedures
|
B5 Mount the ONS 15327 in a Rack
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite
|
Security Level
|
None
|
Step 1 Align the ends of the tie-down bar with the four screw holes located 1 RU below the ONS 15327.
Figure 19-9 shows the tie-down bar, the ONS 15327, and the rack.
Figure 19-9 Tie-Down Bar
Step 2 Install the four screws into the rack.
Step 3 Return to your originating procedure (NTP).
DLP-B330 Manual or Force Switch the Node Timing Reference
Purpose
|
This task commands the node to switch to the timing reference you have selected if the synchronization status message (SSM) quality of the reference is not less than the reference that the node is currently running.
|
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 > Timing tabs. The Timing Source window appears.
Step 2 Click the Reference drop-down list for the desired Clock, and choose the desired reference.
Step 3 Click the Operation drop-down list for the desired Clock, and choose one of the following options:
•Manual—This operation commands the NE to switch to the reference you have selected, if the SSM quality of the reference is not less the reference than the node is currently running.
•Force—This operation commands the NE to switch to the reference you have selected, regardless of the SSM quality, if the reference is valid.
Step 4 Click Apply.
Step 5 Click Yes in the confirmation dialog box.
•If the selected timing reference is invalid, a warning dialog appears. Click OK; the NE remains on the original timing reference without performing the switch.
•If the selected timing reference is an acceptable valid reference, the NE switches to the selected timing reference.
Step 6 Return to your originating procedure (NTP).
DLP-B331 Clear a Manual or Force Switched Node Timing Reference
Purpose
|
This task clears a Manual or Force switch on a node timing reference and reverts the timing reference to its provisioned reference.
|
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 > Timing tabs. The Timing Source window appears.
Step 2 Find the Clock reference that is currently set to Manual or Force in the Operation menu.
Step 3 Click the Operation drop-down list for the clock and choose Clear.
Step 4 Click Apply.
Step 5 Click Yes in the confirmation dialog box.
•If the normal timing reference is invalid or has failed, a warning dialog appears. Click OK; the NE remains on the previous timing reference without performing the switch.
•If the normal timing reference is an acceptable valid reference, the NE reverts to the normal timing reference as defined by the system configuration.
Step 6 Return to your originating procedure (NTP).
DLP-B332 View Circuit Information
Purpose
|
This task provides information about ONS 15327 circuits.
|
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 view circuits for an entire network, from the View menu, choose Go to Network View.
•To view 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 view circuits that originate, terminate, or pass through a specific card, in node view, double-click the card containing the circuits you want to view.
Step 2 Click the Circuits tab. The Circuits tab has the following information:
Note In node or card view, you can change the scope of the circuits that appear by choosing Card (in card view), Node, or Network from the Scope drop-down list in the bottom right corner of the Circuits window.
•Name—Name of the circuit. The circuit name can be manually assigned or automatically generated.
•Type—Circuit types are: STS (STS circuit), Virtual Tributary (VT) (VT circuit), VTT (VT tunnel), or VAP (VT aggregation point).
•Size—Circuit size. VT circuits are 1.5. ONS 15327 STS circuit sizes are 1, 3c, 6c, 9c, 12c, 24c, or 48c.
•Protection—The type of circuit protection. See Table 19-6 for a list of protection types.
Table 19-6 Circuit Protection Types
Protection Type
|
Description
|
1+1
|
The circuit is protected by a 1+1 protection group.
|
2F BLSR
|
The circuit is protected by a 2-fiber BLSR.
|
2F-PCA
|
The circuit is routed on a protection channel access (PCA) path on a 2-fiber BLSR. PCA circuits are unprotected.
|
DRI
|
The circuit is protected by a dual-ring interconnection (DRI).
|
N/A
|
A circuit with connections on the same node is not protected.
|
PCA
|
The circuit is routed on a PCA path on both 2-fiber and 4-fiber BLSRs. PCA circuits are unprotected.
|
Protected
|
The circuit is protected by diverse SONET topologies, for example, a BLSR and a path protection, or a path protection and 1+1.
|
Unprot (black)
|
A circuit with a source and destination on different nodes is not protected.
|
Unprot (red)
|
A circuit created as a fully protected circuit is no longer protected due to a system change, such as removal of a BLSR or 1+1 protection group.
|
Unknown
|
A circuit has a source and destination on different nodes and communication is down between the nodes. This protection type appears if not all circuit components are known.
|
Path Protection
|
The circuit is protected by a path protection.
|
•Dir—The circuit direction, either two-way or one-way.
•Status—The circuit status. Table 19-7 lists the circuit statuses that may appear.
Table 19-7 ONS 15327 Circuit Status
Status
|
Definition/Activity
|
CREATING
|
CTC is creating a circuit.
|
DISCOVERED
|
CTC created a circuit. All components are in place and a complete path exists from circuit source to destination.
|
DELETING
|
CTC is deleting a circuit.
|
PARTIAL
|
A CTC-created circuit is missing a cross-connect or network span or a complete path from source to destination(s) does not exist.
In CTC, circuits are represented using cross-connects and network spans. If a network span is missing from a circuit, the circuit status is PARTIAL. However, an PARTIAL status does not necessarily mean a circuit traffic failure has occurred, because traffic may flow on a protect path.
Network spans are in one of two states: up or down. On CTC circuit and network maps, up spans appear as green lines, and down spans appear as gray lines. If a failure occurs on a network span during a CTC session, the span remains on the network map but its color changes to gray to indicate that the span is down. If you restart your CTC session while the failure is active, the new CTC session cannot discover the span and its span line does not appear on the network map.
Subsequently, circuits routed on a network span that goes down appear as DISCOVERED during the current CTC session, but appear as PARTIAL to users who log in after the span failure.
|
DISCOVERED_TL1
|
A TL1-created circuit or a TL1-like, CTC-created circuit is complete. A complete path from source to destinations exists.
|
PARTIAL_TL1
|
A TL1-created circuit or a TL1-like, CTC-created circuit is missing a cross-connect or circuit span (network link), and a complete path from source to destination(s) does not exist.
|
CONVERSION_PENDING
|
An existing circuit in a topology upgrade is set to this state. The circuit returns to the DISCOVERED state once the topology upgrade is complete.
|
PENDING_MERGE
|
Any new circuits created to represent an alternate path in a topology upgrade are set to this state to indicate that it is a temporary circuit. These circuits can be deleted if a topology upgrade fails.
|
DROP_PENDING
|
A circuit is set to this status when a new circuit drop is being added.
|
•Source—The circuit source in the format: node/slot/port "port name"/STS/VT. (The port name will appear in quotes.) Node and slot will always appear; port "port name"/STS/VT might appear, depending on the source card, circuit type, and whether a name is assigned to the port. If the circuit size is a concatenated size (3c, 6c, 12c, etc.) STSs used in the circuit will be indicated by an ellipsis, for example, "S7..9," (STSs 7, 8, and 9) or S10..12 (STS 10, 11, and 12). If the source is located on an XTC card, port specifies DS1 or DS3; each STS on the XTC card is numbered 1.
•Destination—The circuit destination in same format (node/slot/port "port name"/STS/VT) as the circuit source.
•# of VLANS—The number of VLANS used by an Ethernet circuit with end points on E-Series Ethernet cards in single card or multicard mode.
•# of Spans—The number of internode links that constitute the circuit. Right-clicking the column shows a shortcut menu from which you can choose Span Details to show or hide circuit span detail. For each node in the span, the span detail shows the node/slot (card type)/port/STS/VT.
•State—The circuit service state, IS, OOS, or OOS-PARTIAL. The circuit service state is an aggregate of the service states of its cross-connects:
–IS—All cross-connects are in the IS-NR service state.
–OOS—All cross-connects are in the OOS-AU,AINS; OOS-MA,DSBLD; and/or OOS-MA,MT service state.
–OOS-PARTIAL—At least one cross-connect is IS-NR and others are OOS-AU,AINS; OOS-MA,DSBLD; and/or OOS-MA,MT.
Step 3 Return to your originating procedure (NTP).
DLP-B334 Create Ethernet RMON Alarm Thresholds
Purpose
|
This procedure sets up RMON to allow network management systems to monitor Ethernet ports.
|
Tools/Equipment
|
None
|
Prerequisite Procedures
|
NTP-B24 Verify Card Installation, page 3-2
B60 Log into CTC
|
Required/As Needed
|
As needed
|
Onsite/Remote
|
Onsite or remote
|
Security Level
|
Provisioning or higher
|
Step 1 Double-click the Ethernet card where you want to create the RMON alarm thresholds.
Step 2 In card view, click the Provisioning > RMON Thresholds tabs.
Step 3 Click Create.
The Create Ether Threshold dialog box appears (Figure 19-10).
Figure 19-10 Creating RMON Thresholds
Step 4 From the Slot drop-down list, choose the appropriate Ethernet card.
Step 5 From the Port drop-down list, choose the applicable port on the Ethernet card you selected.
Step 6 From the Variable drop-down list, choose the variable. See Table 19-8 for a list of the Ethernet threshold variables available in this field.
Table 19-8 Ethernet Threshold Variables (MIBs)
Variable
|
Definition
|
iflnOctets
|
Total number of octets received on the interface, including framing octets
|
iflnUcastPkts
|
Total number of unicast packets delivered to an appropriate protocol
|
ifInMulticastPkts (G-Series only)
|
Number of multicast frames received error free
|
ifInBroadcastPkts (G-Series only)
|
The number of packets, delivered by this sublayer to a higher (sub)layer, which were addressed to a broadcast address at this sublayer
|
ifInDiscards (G-Series only)
|
The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol
|
iflnErrors
|
Number of inbound packets discarded because they contain errors
|
ifOutOctets
|
Total number of transmitted octets, including framing packets
|
ifOutUcastPkts
|
Total number of unicast packets requested to transmit to a single address
|
ifInMulticastPkts (G-Series only)
|
Number of multicast frames received error free
|
ifInBroadcastPkts (G-Series only)
|
The number of packets, delivered by this sublayer to a higher (sub)layer, which were addressed to a broadcast address at this sublayer
|
ifInDiscards (G-Series only)
|
The number of inbound packets that were chosen to be discarded even though no errors had been detected that would prevent their delivery to a higher-layer protocol
|
dot3statsAlignmentErrors
|
Number of frames with an alignment error, that is, frames with a length that is not an integral number of octets and where the frame cannot pass the frame check sequence (FCS) test
|
dot3StatsFCSErrors
|
Number of frames with framecheck errors, that is, where there is an integral number of octets, but an incorrect FCS
|
dot3StatsSingleCollisionFrames (not supported by E-Series or G-Series)
|
Number of successfully transmitted frames that had exactly one collision
|
dot3StatsMutlipleCollisionFrame (not supported by E-Series or G-Series)
|
Number of successfully transmitted frames that had multiple collisions
|
dot3StatsDeferredTransmissions (not supported by E-Series or G-Series)
|
Number of times the first transmission was delayed because the medium was busy
|
dot3StatsLateCollision (not supported by E-Series or G-Series)
|
Number of times that a collision was detected later than 64 octets into the transmission (also added into collision count)
|
dot3StatsExcessiveCollision (not supported by E-Series or G-Series)
|
Number of frames where transmissions failed because of excessive collisions
|
dot3StatsCarrierSenseErrors (G-Series only)
|
The number of transmission errors on a particular interface that are not otherwise counted
|
dot3StatsSQETestErrors (G-Series only)
|
A count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface
|
etherStatsUndersizePkts
|
Number of packets received with a length less than 64 octets
|
etherStatsFragments
|
Total number of packets that are not an integral number of octets or have a bad FCS, and that are less than 64 octets long
|
etherStatsPkts64Octets
|
Total number of packets received (including error packets) that were 64 octets in length
|
etherStatsPkts65to127Octets
|
Total number of packets received (including error packets) that were 65 to 172 octets in length
|
etherStatsPkts128to255Octets
|
Total number of packets received (including error packets) that were 128 to 255 octets in length
|
etherStatsPkts256to511Octets
|
Total number of packets received (including error packets) that were 256 to 511 octets in length
|
etherStatsPkts512to1023Octets
|
Total number of packets received (including error packets) that were 512 to 1023 octets in length
|
etherStatsPkts1024to1518Octets
|
Total number of packets received (including error packets) that were 1024 to 1518 octets in length
|
etherStatsOversizePkts
|
The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed
|
etherStatsJabbers
|
Total number of packets longer than 1518 octets that were not an integral number of octets or had a bad FCS
|
etherStatsOctets
|
The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets)
|
etherStatsCollisions
|
Best estimate of the total number of collisions on this segment
|
etherStatsCollisionFrames
|
Best estimate of the total number of frame collisions on this segment
|
etherStatsCRCAlignErrors
|
Total number of packets with a length between 64 and 1518 octets, inclusive, that had a bad FCS or were not an integral number of octets in length
|
receivePauseFrames (G Series only)
|
The number of received IEEE 802.x pause frames
|
transmitPauseFrames (G Series only)
|
The number of transmitted IEEE 802.x pause frames
|
receivePktsDroppedInternal
Congestion (G Series only)
|
The number of received frames dropped due to frame buffer overflow as well as other reasons
|
transmitPktsDroppedInternal
Congestion (G Series only)
|
The number of frames dropped in the transmit direction due to frame buffer overflow as well as other reasons
|
txTotalPkts
|
Total number of transmit packets
|
rxTotalPkts
|
Total number of receive packets
|
Step 7 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, falling threshold, or both the rising and falling thresholds.
Step 8 From the Sample Type drop-down list, choose either Relative or Absolute. Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 9 Type in an appropriate number of seconds for the Sample Period.
Step 10 Type in the appropriate number of occurrences for the Rising Threshold.
Note For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a falling threshold of 400 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, this occurrence raises an alarm.
Step 11 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
Note A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 minutes subsides and creates only 799 collisions in 15 minutes, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15 minute period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Step 12 Click OK to complete the procedure.
Step 13 Return to your originating procedure (NTP).
DLP-B335 Delete Ethernet RMON Alarm Thresholds
Step 1 Double-click the Ethernet card where you want to delete the RMON alarm thresholds.
Step 2 In card view, click the Provisioning > RMON Thresholds tabs.
Step 3 Click the RMON alarm threshold that you want to delete.
Step 4 Click Delete. The Delete Threshold dialog box appears.
Step 5 Click Yes to delete that threshold.
Step 6 Return to your originating procedure (NTP).
DLP-B336 Create a BLSR Using the BLSR Wizard
Step 1 From the View menu, choose Go to Network View.
Step 2 Click the Provisioning > BLSR tabs.
Step 3 Click Create BLSR.
Step 4 In the BLSR Creation dialog box, set the BLSR properties:
•Ring Type—Choose the two-fiber BLSR ring type.
•Speed—Choose the BLSR ring speed: OC-12 or OC-48. The speed must match the OC-N speed of the BLSR trunk (span) cards.
•Ring Name—Assign a ring name. The name can be from 1 to 6 characters in length. The alphanumeric character strings that can be used are 0 to 9 and A to Z. You can combine numbers and letters and use upper or lower case letters. Do not use the character string "All" in either upper or lower case letters, this is a TL1 keyword and will be rejected. Do not choose a name that is already assigned to another BLSR.
•Reversion time—Set the amount of time that will pass before the traffic reverts to the original working path following a ring switch. The default is 5 minutes. Ring reversions can be set to Never.
Step 5 Click Next. If a network graphic appears, go to Step 7. If CTC determines that a BLSR cannot be created, for example, not enough optical cards are installed or it finds circuits with path protection selectors, a "Cannot Create BLSR" message appears. If this occurs, complete the following steps:
a. Click OK.
b. On the Create BLSR window, click Excluded Nodes. Review the information explaining why the BLSR could not be created, then click OK.
c. Depending on the problem, click Back to start over or click Cancel to cancel the operation.
d. Complete the "NTP-B40 Provision BLSR Nodes" procedure on page 4-10, making sure all steps are completed accurately, then start this procedure again.
Step 6 In the network graphic, double-click a BLSR span line. If the span line is DCC connected to other BLSR cards constituting a complete ring, the lines turn blue and the Finish button appears. If the lines do not form a complete ring, double-click span lines until a complete ring is formed. When the ring is DCC connected, go to Step 7.
Step 7 Click Finish. If the BLSR window appears with the BLSR you created, go to Step 8. If a "Cannot Create BLSR" or "Error While Creating BLSR" message appears:
a. Click OK.
b. In the Create BLSR window, click Excluded Nodes. Review the information explaining why the BLSR could not be created, then click OK.
c. Depending on the problem, click Back to start over or click Cancel to cancel the operation.
d. Complete the "NTP-B40 Provision BLSR Nodes" procedure on page 4-10, making sure all steps are completed accurately, then start this procedure again.
Note Some or all of the following alarms may briefly appear during BLSR setup: E-W MISMATCH, RING MISMATCH, APSCIMP, APSDFLTK, or BLSROSYNC.
Step 8 Verify the following:
•On the network view graphic, a green span line appears between all BLSR nodes.
•All E-W MISMATCH, RING MISMATCH, APSCIMP, DFLTK, and BLSROSYNC alarms are cleared. Refer to the Cisco ONS 15327 Troubleshooting Guide if necessary for alarm troubleshooting.
Step 9 Return to your originating procedure (NTP).
DLP-B337 Create a BLSR Manually
Step 1 In node view, click the Provisioning > Ring tabs.
Step 2 Click Create.
Step 3 In the Suggestion dialog box, click OK.
Step 4 In the Create BLSR dialog box, set the BLSR properties:
•Ring Type—Choose the two-fiber BLSR ring type.
•Ring Name—Assign a ring name. You must use the same ring name for each node in the BLSR. Any alphanumeric character string is permissible, and upper and lower case letters can be combined. Do not use the character string "All" in either upper or lower case letters, this is a TL1 keyword and will be rejected. Do not choose a name that is already assigned to another BLSR.
•Node ID—Choose a Node ID from the drop-down list (0 through 31). The Node ID identifies the node to the BLSR. Nodes in the same BLSR must have unique Node IDs.
•Reversion time—Set the amount of time that will pass before the traffic reverts to the original working path. The default is 5 minutes. All nodes in a BLSR must have the same reversion time setting.
•West Line—Assign the west BLSR port for the node from the drop-down list.
Note The east and west ports must match the fiber connections and DCC terminations set up in the "NTP-B40 Provision BLSR Nodes" procedure on page 4-10.
•East Line—Assign the east BLSR port for the node from the drop-down list.
Step 5 Click OK.
Note Some or all of the following alarms will appear until all the BLSR nodes are provisioned: E-W MISMATCH, RING MISMATCH, APSCIMP, APSDFLTK, BLSROSYNC. The alarms will clear after you configure all the nodes in the BLSR.
Step 6 From the View menu, choose Go to Other Node.
Step 7 In the Select Node dialog box, choose the next node that you want to add to the BLSR.
Step 8 Repeat Steps 1 through 7 at each node that you want to add to the BLSR. When all nodes have been added, continue with Step 9.
Step 9 From the View menu, choose Go to Network View. After 10 to 15 seconds, verify the following:
•A green span line appears between all BLSR nodes.
•All E-W MISMATCH, RING MISMATCH, APSCIMP, DFLTK, and BLSROSYNC alarms are cleared.
Step 10 Return to your originating procedure (NTP).
DLP-B338 Manually Route a Path Protection Circuit for a Topology Upgrade
Step 1 In the Circuit Routing Preferences area of the Unprotected to path protection page, uncheck Route Automatically.
Step 2 Click Next. In the Route Review and Edit area, node icons appear for you to route the circuit. The circuit source node is selected. Green arrows pointing from the source node to other network nodes indicate spans that are available for routing the circuit.
Step 3 Click Finish.
Step 4 Return to your originating procedure (NTP).
DLP-B339 Automatically Route a Path Protection Circuit for a Topology Upgrade
Step 1 In the Circuit Routing Preferences area of the Unprotected to path protection page, check Route Automatically.
Check Review Route Before Creation if you want to review and edit the circuit route before the circuit is created.
Step 2 Choose one of the following:
•Nodal Diversity Required—Ensures that the primary and alternate paths within 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 3 If you selected Review Route Before Creation, complete the following substeps. If not, continue with Step 4.
a. Click Next.
b. Review the circuit route. To add or delete a circuit span, choose 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.
c. If the provisioned circuit does not reflect the routing and configuration you want, click Back to verify and change circuit information.
Step 4 Click Finish.
Step 5 Return to your originating procedure (NTP).
DLP-B340 View the BLSR STS Squelch Table
Purpose
|
This task allows you to view the BLSR STS squelch table for an ONS 15327 BLSR node. For example, if a fiber cut occurs, the BLSR STS squelch tables show STSs that will be squelched for every isolated node. Squelching replaces traffic by inserting the appropriate alarm indication signal path (AIS-P); it prevents traffic misconnections. For an STS with a VT-access check mark, the AIS-P will be removed after 100 ms. For more information about BLSR squelching, refer to Telcordia GR-1230.
|
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 To open the squelch table in node view:
a. In node view, click the Provisioning > BLSR tabs.
b. Click the BLSR whose squelch table you want to view.
c. Click Squelch Table.
Step 2 To open the squelch table in network view:
a. In network view, click the Provisioning > BLSR tabs.
b. Click the BLSR whose squelch table you want to view.
c. Click Edit.
d. Right-click a node in the Edit window.
e. Click Squelch Table from the drop-down list.
Step 3 In the BLSR Squelch Table window you can view the following information:
•STS Number—Shows the BLSR STS numbers. For two-fiber BLSRs, the number of STSs is half the BLSR OC-N, for example, an OC-12 BLSR squelch table will show 6 STSs.
•West Source—If traffic is received by the node on its west span, the BLSR node ID of the source appears. (To view the BLSR node IDs for all nodes in the ring, click the Ring Map button.)
•West VT (from the West Source)—A check mark indicates that the STS carries incoming VT traffic. The traffic source is coming from the west side.
•West VT (from the West Destination)—A check mark indicates that the STS carries outgoing VT traffic. The traffic is dropped on the west side.
•West Dest—If traffic is sent on the node's west span, the BLSR node ID of the destination appears.
•East Source—If traffic is received by the node on its east span, the BLSR node ID of the source appears.
•East VT (from the East Source)—A check mark indicates that the STS carries incoming VT traffic. The traffic source is coming from the east side.
•East VT (from the East Destination)—A check mark indicates that the STS carries outgoing VT traffic. The traffic is dropped on the east side.
•East Dest—If traffic is sent on the node's east span, the BLSR node ID of the destination appears.
Note BLSR squelching is performed on STSs that carry STS circuits only. Squelch table entries will not appear for STSs carrying VT circuits or Ethernet circuits to or from E-Series Ethernet cards provisioned in a multicard Ethergroup.
Step 4 Return to your originating procedure (NTP).
DLP-B341 View the BLSR VT Squelch Table
Purpose
|
BLSR VT squelch tables only appear on the node dropping VTs from a BLSR and are used to perform VT-level squelching when a node is isolated. VT squelching is supported on the ONS 15327 and the ONS 15454 platforms.
The ONS 15600 platform does not support VT squelching; however, when an ONS 15454 or ONS 15327 and an ONS 15600 are in the same network, the ONS 15600 node allows the ONS 15454 or ONS 15327 node to carry VT circuits in a VT tunnel. The ONS 15600 performs 100-ms STS-level squelching for each VT-access STS at the switching node in case of a node failure. For more information about BLSR squelching, refer to Telcordia GR-1230.
|
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 To open the squelch table in node view:
a. In node view, click the Provisioning > BLSR tabs.
b. Click the BLSR whose squelch table you want to view.
c. Click Squelch Table.
Step 2 To open the squelch table in network view:
a. In network view, click the Provisioning > BLSR tabs.
b. Click the BLSR whose squelch table you want to view.
c. Click Edit.
d. Right-click a node in the Edit window.
e. Choose Squelch Table from the drop-down list.
Step 3 In the BLSR STS Squelch Table window, double-click the VT check mark. In the BLSR VT Squelch Table window you can view the following information:
Note The check mark appears on every VT-access STS; however, the VT squelch table appears only by double-clicking the check mark on the node dropping the VT. The intermediate node of the VT does not maintain the VT-squelch table.
•VT Number—Shows the BLSR VT numbers. The VT number includes VT group and channel (VT group 2 and channel 1 are displayed as 2-1.)
•West Source—If traffic is received by the node on its west span, the BLSR node ID of the source appears. (To view the BLSR node IDs for all nodes in the ring, click the Ring Map button.)
•East Source—If traffic is received by the node on its east span, the BLSR node ID of the source appears.
Step 4 Return to your originating procedure (NTP).
