cc/td/doc/product/mels/15540x/12_2_s
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Configuring 10-GE Transponder Module Interfaces and Patch Connections

Enabling Tengigethernetphy Interfaces

Displaying Tengigethernetphy Interface Information

Enabling the In-Band Message Channel on Tengigethernetphy Interfaces

Displaying the In-Band Message Channel Configuration

Enabling Waveethernetphy Interfaces and Turning on ITU Lasers

Displaying Waveethernetphy Interface Information

Configuring Loopbacks

Displaying Loopback Configuration

About Alarm Thresholds

Configuring Alarm Thresholds

Displaying Alarm Threshold Configuration

Configuring Forward Laser Control

Displaying Forward Laser Control Configuration

Configuring Patch Connections

Displaying Patch Connections

Configuring Optical Power Thresholds

Displaying Optical Power Threshold Configuration

Turning Lasers On and Off

Displaying Laser Status

About Cross Connections

Displaying Cross Connections


Configuring 10-GE Transponder Module Interfaces and Patch Connections

This chapter describes how to configure interfaces and patch connections on the Cisco ONS 15540 ESPx. This chapter includes the following sections:

• Enabling Tengigethernetphy Interfaces

• Enabling the In-Band Message Channel on Tengigethernetphy Interfaces

• Enabling Waveethernetphy Interfaces and Turning on ITU Lasers

• Configuring Loopbacks

• About Alarm Thresholds

• Configuring Alarm Thresholds

• Configuring Forward Laser Control

• Configuring Patch Connections

• Configuring Optical Power Thresholds

• Turning Lasers On and Off

• About Cross Connections

Note To ensure the installed Cisco IOS software supports your hardware and provides the software features you wish to use, see the "New and Changed Information" section on page xxi. Also refer to the "Hardware Supported" section and "Feature Set" section of the latest release notes for the Cisco ONS 15540 ESPx.

To configure tengigethernetphy interfaces on the Cisco ONS 15540 ESPx, perform the following steps:

Step 1 Enable the interface (required).

Step 2 Enable the in-band message channel (optional).

Step 3 Configure loopback (optional).

Step 4 Create alarm threshold lists and apply them to the interfaces (optional).

Step 5 Enable forward laser control (optional).

To configure waveethernetphy interfaces on the Cisco ONS 15540 ESPx, perform the following steps:

Step 1 Enable the interface and turn on the ITU laser (required).

Step 2 Enable forward laser control (optional).

Step 3 Configure loopback (optional).

Step 4 Create alarm threshold lists and apply them to the interfaces (optional).

To configure wavepatch interfaces on the Cisco ONS 15540 ESPx, perform the following steps:

Step 1 Configure the patch connections (required).

Step 2 Configure the optical power receive threshold (optional).

Enabling Tengigethernetphy Interfaces

To enable the 10-GE transponder module tengigethernetphy interfaces, perform the following tasks, starting in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface tengigethernetphy slot/subcard

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# no shutdown

Enables the interface.

Step 3 

Switch(config-if)# no laser shutdown

Turns on the client-side laser.

Example

The following example shows how to enable a tengigethernetphy interface:

Switch(config)# interface tengigethernetphy 10/0
Switch(config-if)# no shutdown

Displaying Tengigethernetphy Interface Information

The following example shows how to display tengigethernetphy interface information.

Switch# show interface tengigethernetphy 10/0
TenGigEthernetPhy10/0 is up, line protocol is up
Signal quality : Loss of lock
Laser shut down : No
Forward laser control : Off
CDL Enabled : Yes

Configured threshold Group: thresh
Threshold monitored for: 64b66b cvrd
SF set value: 10e-4 (1249438 in 1 secs)
SD set value: 10e-5 (124994 in 1 secs)
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
TenGige Non CDL Pkt count: 0
CDL HEC error count: 0
TenGige CDL idle Pkt count: 0
Defect Indication Status : up
Configured Node Behavior : Hop Terminating
Current Node Behavior : Hop Terminating
Defect Indication Receive : None
Defect Indication Transmit : FDI-E BDI-H
Loopback set
Last clearing of "show interface" counters never
Hardware is data_enabled_port

Enabling the In-Band Message Channel on Tengigethernetphy Interfaces

The tengigethernetphy interface will support in-band message channel traffic when a system connected to the 10-GE transponder module also supports the in-band message channel. When the in-band message channel is enabled on a tengigethernetphy interface, an ethernetdcc interface becomes available for configuration. The identifier for this interface is ethernetdcc slot/subcard/1.

To enable the in-band message channel on tengigethernetphy interfaces, perform the following tasks, starting in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface tengigethernetphy slot/subcard

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# cdl enable

Enables the in-band message channel on a tengigethernetphy interface. The default is disabled.

To configure the ethernetdcc slot/subcard/1 interface, refer to the "Configuring IP on Ethernetdcc Interfaces for the In-Band Message Channel" section on page 11-11.

Note The in-band message channel must be enabled on both systems to function correctly.

Example

The following example shows how to enable the in-band message channel on a tengigethernetphy interface:

Switch(config)# interface tengigethernetphy 10/0
Switch(config-if)# no shutdown

Displaying the In-Band Message Channel Configuration

The following example shows how to display the in-band message channel configuration on a tengigethernetphy interface.

Switch# show interface tengigethernetphy 10/0
TenGigEthernetPhy10/0 is up, line protocol is up
Signal quality : Loss of lock
Laser shut down : No
Forward laser control : Off
   CDL Enabled : Yes

Configured threshold Group: thresh
Threshold monitored for: 64b66b cvrd
SF set value: 10e-4 (1249438 in 1 secs)
SD set value: 10e-5 (124994 in 1 secs)
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
TenGige Non CDL Pkt count: 0
CDL HEC error count: 0
TenGige CDL idle Pkt count: 0

Defect Indication Status : up
Configured Node Behavior : Hop Terminating
Current Node Behavior : Hop Terminating
Defect Indication Receive : None
Defect Indication Transmit : FDI-E BDI-H
Loopback set
Last clearing of "show interface" counters never
Hardware is data_enabled_port

Enabling Waveethernetphy Interfaces and Turning on ITU Lasers

The waveethernetphy interface is the trunk side interface for the 10-GE transponder module that corresponds to the ITU laser. It supports the in-band message channel and is associated with the ethernetdcc slot/subcard/0 interface.

To enable the 10-GE transponder module waveethernetphy interface and turn on the ITU laser, perform the following tasks, starting in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface waveethernetphy slot/subcard

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# no shutdown

Enables the interface.

Step 3 

Switch(config-if)# no laser shutdown

Turns on the ITU laser.

To configure the ethernetdcc slot/subcard/0 interface, refer to the "Configuring IP on Ethernetdcc Interfaces for the In-Band Message Channel" section on page 11-11.

Example

The following example shows how to enable a waveethernetphy interface:

Switch(config)# interface waveethernetphy 10/0
Switch(config-if)# no shutdown

Displaying Waveethernetphy Interface Information

The following example shows how to display waveethernetphy interface information.

Switch# show interface waveethernetphy 10/0
WaveEthernetPhy10/0 is up, line protocol is up
Channel: 26 Frequency: 195.2 Thz Wavelength: 1535.82 nm
Active Wavepatch : Wavepatch4/1/0
Splitter Protected : No
Signal quality : Loss of lock
Receive power level : -30.0 dBm
Transmit condition : Good
Laser shut down : No
Forward laser control : Off
Osc physical port : No
Wavelength used for inband management: No
Loopback not set

Configured threshold Group: thresh
Threshold monitored for: 64b66b cvrd
SF set value: 10e-4 (1249438 in 1 secs)
SD set value: 10e-5 (124994 in 1 secs)
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
TenGige Non CDL Pkt count: 0
CDL HEC error count: 0
TenGige CDL idle Pkt count: 0

Defect Indication Status : up
Configured Node Behavior : Hop Terminating
Current Node Behavior : Hop Terminating
Defect Indication Receive : None
Defect Indication Transmit : FDI-E BDI-H

Last clearing of "show interface" counters never
Hardware is data_and_cdl_enabled_port

Configuring Loopbacks

The Cisco ONS 15540 ESPx software allows you to configure interface loopback using the CLI. You can use this feature to test and troubleshoot interfaces without physically looping them back.

To configure a loopback on 10-GE transponder module interfaces, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface {waveethernetphy slot/subcard | tengigethernetphy slot/subcard}

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# loopback

Configures a software loopback on the interface.

Note Loop back either the waveethernetphy interface or the tengigethernetphy interface on a given module, but not both at the same time.

Displaying Loopback Configuration

To display the loopback configuration for a tengigethernetphy or waveethernetphy interface, use the following EXEC command:

Command
Purpose

show interfaces {tengigethernetphy slot/subcard | waveethernetphy slot/subcard}

Displays the tengigethernetphy or waveethernetphy interface configuration.


Example

The following example shows how to display the loopback configuration for a tengigethernetphy interface:

Switch# show interfaces tengigethernetphy 10/0
TenGigEthernetPhy10/0 is up, line protocol is up
Signal quality : Loss of lock
Laser shut down : No
Forward laser control : Off
CDL Enabled : Yes

Configured threshold Group: tengig-counters
Threshold monitored for: 64b66b cvrd
SF set value: 10e-4 (1249438 in 1 secs)
SD set value: 10e-5 (124994 in 1 secs)
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
TenGige Non CDL Pkt count: 0
CDL HEC error count: 0
TenGige CDL idle Pkt count: 0

Defect Indication Status : up
Configured Node Behavior : Hop Terminating
Current Node Behavior : Hop Terminating
Defect Indication Receive : None
Defect Indication Transmit : FDI-E BDI-H
   Loopback set
Last clearing of "show interface" counters never
Hardware is data_enabled_port

The following example shows how to display the loopback configuration on a waveethernetphy interface.

Switch# show interface waveethernetphy 10/0
WaveEthernetPhy10/0 is up, line protocol is up
Channel: 26 Frequency: 195.2 Thz Wavelength: 1535.82 nm
Active Wavepatch : Wavepatch4/1/0
Splitter Protected : No
Signal quality : Loss of lock
Receive power level : -30.0 dBm
Transmit condition : Good
Laser shut down : No
Forward laser control : Off
Osc physical port : No
Wavelength used for inband management: No
  Defect Indication Transmit : FDI-E BDI-H
   Loopback not set

Configured threshold Group: thresh
Threshold monitored for: 64b66b cvrd
SF set value: 10e-4 (1249438 in 1 secs)
SD set value: 10e-5 (124994 in 1 secs)
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
TenGige Non CDL Pkt count: 0
CDL HEC error count: 0
TenGige CDL idle Pkt count: 0

< Information deleted >

About Alarm Thresholds

You can configure thresholds on tengigethernetphy and waveethernetphy interfaces that issue alarm messages to the system if the thresholds are exceeded. Every second, the monitoring facility updates the counters that correspond to the alarm thresholds. When the signal degrades, or fails entirely, the system issues alarms to the console. These alarms can help isolate failures in the system and in the network.

You can configure more than one threshold list on an interface. The threshold lists cannot have overlapping counters so that only one counter is set for the interface. Also, the threshold list name cannot begin with the text string "default" because the it is reserved for use by the system.

Configuring Alarm Thresholds

To configure alarm thresholds on tengigethernetphy and waveethernetphy interfaces, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# threshold-list name

Switch(config-t-list)#

Creates or selects the threshold list to configure and enters threshold list configuration mode.

Note You cannot modify an existing threshold list if it is associated with an interface.

Step 2 

Switch(config-t-list)# notification-throttle timer seconds

Configures the SNMP notification timer. The default value is 5 seconds. (Optional)

Step 3 

Switch(config-t-list)# threshold name {cvrd | cdl hec | crc | sonet-sdh section cv | tx-crc} {failure | degrade} [index value]

Switch(config-threshold)#

Specifies a threshold type to modify and enters threshold configuration mode.

Step 4 

Switch(config-threshold)# value rate value

Specifies the threshold rate value. This value is the negative power of 10 (10-n).

Step 5 

Switch(config-threshold)# description text

Specifies a description of the threshold. The default value is the null string. (Optional)

Step 6 

Switch(config-threshold)# aps trigger

Enables APS switchover when this threshold is crossed. (Optional)

Note This command only triggers switchovers for y-cable protection, not for splitter protection.

Step 7 

Switch(config-threshold)# exit

Switch(config-t-list)#

Returns to threshold list configuration mode.

Repeat Step 3 through Step 7 to configure more thresholds in the threshold list.

Step 8 

Switch(config-t-list)# exit

Switch(config)#

Returns to global configuration mode.

Step 9 

Switch(config)# interface {tengigethernetphy slot/subcard | waveethernetphy slot/subcard}

Switch(config-if)#

Selects the tengigethernetphy or waveethernetphy interface to configure and enters interface configuration mode.

Step 10 

Switch(config-if)# threshold-group name

Configures the threshold list on the interface.

Note If a threshold type does not apply to the 10-GE protocol, that threshold type is ignored.

Table 5-1 lists the threshold error rates in errors per second.

Table 5-1 Thresholds for Monitored Protocols (Errors Per Second)

Rate
10-Gigabit Ethernet CVRD
10-Gigabit Ethernet CDL HEC

3

12,443,900

6512

4

1,249,438

665

5

124,944

67

6

10,312

7

7

1031

0.7

8

103

0.07

9

10

0.007


Examples

The following example shows how to create an alarm threshold list and configure that list on a tengigethernetphy interface:

Switch# configure terminal
Switch(config)# threshold-list tengig-counters
Switch(config-t-list)# threshold name cvrd degrade
Switch(config-threshold)# value rate 5
Switch(config-threshold)# exit
Switch(config-t-list)# threshold name cvrd failure
Switch(config-threshold)# value rate 4
Switch(config-threshold)# exit
Switch(config-t-list)# exit
Switch(config)# interface tengigethernetphy 10/0
Switch(config-if)# threshold-group tengig-counters

The following example shows how to create an alarm threshold list with the APS switchover trigger and configure that list on a pair of associated tengigethernetphy interfaces:

Switch(config)# threshold-list tengig-alarms
Switch(config-t-list)# threshold name cvrd failure
Switch(config-threshold)# value rate 6
Switch(config-threshold)# aps trigger
Switch(config-threshold)# exit
Switch(config-t-list)# exit
Switch(config)# redundancy
Switch(config-red)# associate group tengig-channel
Switch(config-red-aps)# aps working tengigethernetphy 3/0
Switch(config-red-aps)# aps protection tengigethernetphy 5/0
Switch(config-red-aps)# aps y-cable
Switch(config-red-aps)# aps enable
Switch(config-red-aps)# exit
Switch(config-red)# exit
Switch(config)# interface tengigethernetphy 3/0
Switch(config-if)# no shutdown
Switch(config-if)# threshold-group tengig-alarms
Switch(config-if)# exit
Switch(config)# interface tengigethernetphy 5/0
Switch(config-if)# no shutdown
Switch(config-if)# threshold-group tengig-alarms

Displaying Alarm Threshold Configuration

To display the configuration of a threshold list and the threshold group for a tengigethernetphy or waveethernetphy interface, use the following EXEC commands:

Command
Purpose

show threshold-list [name]

Displays the threshold group configuration.

show interfaces {tengigethernetphy slot/subcard | waveethernetphy slot/subcard}

Displays the tengigethernetphy or waveethernetphy interface configuration.


Example

The following example shows how to display the configuration of a threshold group:

Switch# show threshold-list tengig-counters

Threshold List Name: tengig-counters
Notification throttle timer : 5 (in secs)
Threshold name : cvrd Severity : Degrade
Value : 10e-5
APS Trigger : Not set
Threshold name : cvrd Severity : Failure
Value : 10e-4
APS Trigger : Not set

The following example shows how to display the threshold group information for a tengigethernetphy interface:

Switch# show interfaces tengigethernetphy 10/0
TenGigEthernetPhy10/0 is up, line protocol is up
Signal quality : Loss of lock
Laser shut down : No
Forward laser control : Off
CDL Enabled : Yes

Configured threshold Group: tengig-counters
Threshold monitored for: 64b66b cvrd
SF set value: 10e-4 (1249438 in 1 secs)
SD set value: 10e-5 (124994 in 1 secs)
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
TenGige Non CDL Pkt count: 0
CDL HEC error count: 0
TenGige CDL idle Pkt count: 0

Defect Indication Status : up
Configured Node Behavior : Hop Terminating
Current Node Behavior : Hop Terminating
Defect Indication Receive : None
Defect Indication Transmit : FDI-E BDI-H
Loopback set
Last clearing of "show interface" counters never
Hardware is data_enabled_port

Configuring Forward Laser Control

To configure forward laser control on a 10-GE transponder module tengigethernetphy and waveethernetphy interfaces, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface tengigethernetphy slot/subcard

Switch(config-if)#

Selects the tengigethernetphy interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# [no] laser control forward enable

Configures forward laser control on the interface. The default state is disabled.

Configuring FLC on the tengigethernetphy interface shuts down the waveethernetphy interface laser when loss of light occurs on the client (tengigethernetphy) side.

For more information, see the "About Forward Laser Control" section on page 4-13.

Step 3 

Switch(config-if)# exit

Returns to global configuration mode.

Step 4 

Switch(config)# interface waveethernetphy slot/subcard

Switch(config-if)#

Selects the waveethernetphy interface to configure and enters interface configuration mode.

Step 5 

Switch(config-if)# [no] laser control forward enable

Configures forward laser control on the interface. The default state is disabled.

Configuring FLC on the waveethernetphy interface shuts down the tengigethernetphy interface laser when loss of light occurs on the trunk (waveethernetphy) side.

For more information, see the "About Forward Laser Control" section on page 4-13.

Examples

The following example shows how to configure forward laser control for the tengigethernetphy and waveethernetphy interfaces on a 10-GE transponder module:

Switch(config)# interface tengigethernetphy 5/1
Switch(config-if)# laser control forward enable
Switch(config-if)# exit
Switch(config)# interface waveethernetphy 5/1
Switch(config-if)# laser control forward enable

Displaying Forward Laser Control Configuration

To display the forward laser control configuration of a tengigethernetphy or waveethernetphy interface, use the following EXEC command:

Command
Purpose

show interfaces {tengigethernetphy slot/subcard | waveethernetphy slot/subcard}

Displays interface information.


Example

The following example shows how to display the forward laser control configuration for an interface:

Switch# show interfaces waveethernetphy 10/0
TenGigEthernetPhy10/0 is up, line protocol is up
Signal quality  : Loss of lock
Laser shut down : No
   Forward laser control : On
CDL Enabled : Yes

Configured threshold Group: thresh
Threshold monitored for: 64b66b cvrd
SF set value: 10e-4 (1249438 in 1 secs)
SD set value: 10e-5 (124994 in 1 secs)
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
TenGige Non CDL Pkt count: 0
CDL HEC error count: 0
TenGige CDL idle Pkt count: 0

Defect Indication Status : up
Configured Node Behavior : Hop Terminating
Current Node Behavior : Hop Terminating
Defect Indication Receive : None
Defect Indication Transmit : FDI-E BDI-H
Loopback set
Last clearing of "show interface" counters never
Hardware is data_enabled_port

Configuring Patch Connections

Because the mux/demux modules are passive devices, the Cisco ONS 15540 ESPx does not detect its optical patch connection configuration. For system management purposes, you must also configure the patch connections using the CLI.

Note If you correctly patched your modules, no CLI configuration is necessary for the signal to pass from the client to the trunk fiber.

To configure patch connections, use the following global configuration commands:

Command
Purpose

patch wavepatch slot/subcard/port filter slot/subcard/port

or

patch filter slot/subcard/port wavepatch slot/subcard/port

Configures the patch connection between the wavepatch interface on a 10-Gbps line card motherboard and the filter interface on a mux/demux module.


Note If you correctly patch your mux/demux modules, patch command configuration is not necessary for the signal to pass from the client to the trunk fiber. However, without correct patch command configuration, CDP is unable to locate the wdm interfaces that connect to the trunk fiber and discover the topology neighbors. For more information on network monitoring, see the "Configuring CDP" section on page 11-3.

Example

The following example shows how configure the patch connection between a 10-Gbps line card motherboard and a mux/demux module:

Switch# configure terminal
Switch(config)# patch wavepatch 10/0/0 filter 0/0/1

Displaying Patch Connections

To display the patch connections, use the following privileged EXEC command:

Command
Purpose

show patch [detail]

Displays the patch connections.


Note The error field in the show patch command output helps troubleshoot shelf misconfigurations. When there is a channel mismatch between a 10-GE transponder module and a mux/demux module, "Channel Mismatch" appears for the patch connection. When more than one mux/demux module drops the same channels, "Channel Mismatch" appears for all patch connections.

Example

The following example shows the patch connections:

Switch# show patch
Patch Interface Patch Interface Type Dir Error
------------------ ------------------ --------- ---- ----------------
Filter0/0/1         Wavepatch10/0/0 USER Both
Oscfilter0/0 Wave0 USER Both
Wdm0/0 Thru0/1 USER Both

Configuring Optical Power Thresholds

Optical power thresholds provide a means of monitoring the signal power from the ITU laser. Four types of thresholds are provided:

•Low alarm

•Low warning

•High warning

•High alarm

When a threshold is crossed, the system sends a message to the console.

Note The default values for the optical power receive thresholds are sufficient for most network configurations.

To configure optical power thresholds for wavepatch interfaces on a 10-GE transponder module, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface wavepatch slot/subcard/port

Switch(config-if)#

Selects the transparent interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# optical threshold power receive {low | high} {alarm | warning} value [severity {critical | major | minor | not alarmed | not reported}]

Specifies the optical power threshold value in units of 0.1 dBm. The default values are as follows:

Low alarm: -22 dBm

Low warning: -20 dBm

High warning: -10 dBm

High alarm: -8 dBm

Alarm severity: major

Warning severity: not alarmed

Examples

The following example shows how to configure optical power thresholds for wavepatch interfaces on a 10-GE transponder module:

Switch(config)# interface wavepatch 5/0/0
Switch(config-if)# optical threshold power receive low alarm -210

Displaying Optical Power Threshold Configuration

To display the optical power thresholds for a wavepatch interface, use the following EXEC command:

Command
Purpose

show interfaces wavepatch slot/subcard/port

Displays interface information.


Example

The following example shows how to display the forward laser control configuration for an interface:

Switch# show interfaces wavepatch 10/0/0
Wavepatch10/0/0 is up, line protocol is up
Receiver power level: -35.0 dBm

Optical threshold monitored for : Receive Power (in dBm)
Threshold exceeded for : Low Warning and Low Alarm
Low alarm value = -21.0
Low Alarm Severity = critical
Low warning value = -20.0 (default)
Low Warning Severity = not alarmed
High alarm value = -6.1
High Alarm Severity = critical
High warning value = -8.0 (default)
High Warning Severity = not alarmed
Hardware is passive_port

Turning Lasers On and Off

When in-band message channel capable interfaces are administratively shut down using the shutdown command, data traffic is interrupted. To stop all traffic, you must turn off the laser.

To turn the lasers on and off on a 10-GE transponder module, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface {tengigethernetphy slot/subcard | waveethernetphy slot/subcard}

Switch(config-if)#

Selects the transparent interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# laser shutdown

Shuts down the laser.

Step 3 

Switch(config-if)# no laser shutdown

Turns the laser on.

Note The 10-GE laser must warm up for 2 minutes before carrying traffic when a no laser shutdown command is used on a tengigethernetphy interface.

Examples

The following example shows how to configure optical power thresholds for wavepatch interfaces on a 10-GE transponder module:

Switch(config)# interface waveethernetphy 10/0
Switch(config-if)# laser shutdown

Displaying Laser Status

To display the laser status, use the following EXEC command:

Command
Purpose

show interfaces {tengigethernetphy slot/subcard | waveethernetphy slot/subcard}

Displays interface information.


Example

The following example shows how to display the forward laser control configuration for an interface:

Switch# show interfaces waveethernetphy 10/0
WaveEthernetPhy10/0 is up, line protocol is up
Channel: 26 Frequency: 195.2 Thz Wavelength: 1535.82 nm
Active Wavepatch : Wavepatch4/1/0
Splitter Protected : No
Signal quality : Loss of lock
Receive power level : -35.0 dBm
Transmit condition : Good
   Laser shut down : No
Forward laser control : Off
Osc physical port : No
Wavelength used for inband management: No
Loopback not set

Configured threshold Group: thresh
Threshold monitored for: 64b66b cvrd
SF set value: 10e-4 (1249438 in 1 secs)
SD set value: 10e-5 (124994 in 1 secs)
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
TenGige Non CDL Pkt count: 0
CDL HEC error count: 0
TenGige CDL idle Pkt count: 458745

Defect Indication Status : up
Configured Node Behavior : Hop Terminating
Current Node Behavior : Hop Terminating
Defect Indication Receive : None
Defect Indication Transmit : FDI-E

Last clearing of "show interface" counters never
Hardware is data_and_cdl_enabled_port

About Cross Connections

The client signal follows a path of interface optical cross connections through the Cisco ONS 15540 ESPx. Knowing the path of a signal through the shelf helps with system management and troubleshooting.

Displaying Cross Connections

To display the signal path cross connections, use the following privileged EXEC command:

Command
Purpose

show connect [edge | intermediate [sort-channel | interface {tengigethernetphy slot/subcard | waveethernetphy slot/subcard}]]

Displays the optical connections.


Examples

The following example shows the cross connections within a system configured for splitter protection:

Switch# show connect intermediate
client/ wave wave wdm
wave client patch filter trk channel
------------ ------------ ------- ------ ----- -------
TenGE3/0 WaveE3/0 3/0/0*
Tran9/0/0 Wave9/0 9/0/0*
9/0/1
Tran9/1/0 Wave9/1 9/1/0*
9/1/1
Tran9/2/0 Wave9/2 9/2/0*
9/2/1
Tran9/3/0 Wave9/3 9/3/0*
9/3/1
Tran10/1/0 Wave10/1 10/1/0*
10/1/1
Tran10/3/0 Wave10/3 10/3/0*
10/3/1
TenGE11/0 WaveE11/0 11/0/0* 0/0/25 0/0 26
11/0/1 1/3/1 1/3 26

The following example shows the cross connections within a system configured for line card protection using splitter protected 10-Gbps line card motherboards:

Switch# show connect intermediate
client/ wave wave wdm
wave client patch filter trk channel
------------ ------------ ------- ------ --- -------
TenGE10/0/0 WaveE10/0 10/0/0* 0/3/0 0/2 25
 10/0/1
TenGE10/1/0 WaveE10/1 10/1/0* 0/3/1 0/2 26
 10/1/1
TenGE10/2/0 WaveE10/2 10/2/0* 0/3/2 0/2 27
 10/2/1
TenGE10/3/0 WaveE10/3 10/3/0* 0/3/3 0/2 28
 10/3/1

hometocprevnextglossaryfeedbacksearchhelp

Posted: Tue Apr 5 08:17:07 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.