Configuring Transponder Line Card Interfaces

Table Of Contents

Configuring Transponder Line Card Interfaces

Configuring Protocol Encapsulation or Clock Rate

Displaying Protocol Encapsulation or Clock Rate Configuration

About Transponder Line Card Channel Frequencies

Configuring Transponder Line Card Channel Frequency

Displaying Transponder Line Card Channel Frequency

About Protocol Monitoring

Configuring Protocol Monitoring

Displaying Protocol Monitoring Configuration

About Alarm Thresholds

Configuring Alarm Thresholds

Displaying Alarm Threshold Configuration

About Laser Shutdown

About Forward Laser Control

About OFC

About Laser Safety Control

Configuring Laser Shutdown

Configuring Forward Laser Control

Configuring Laser Safety Control

Configuring Optical Power Thresholds

Displaying Optical Power Threshold Configuration

About Patch Connections

Configuring Patch Connections

Displaying Patch Connections

About Cross Connections

Displaying Cross Connections

Configuring Transponder Line Card Interfaces

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

• Configuring Protocol Encapsulation or Clock Rate

• About Transponder Line Card Channel Frequencies

• Configuring Transponder Line Card Channel Frequency

• About Protocol Monitoring

• Configuring Protocol Monitoring

• About Alarm Thresholds

• Configuring Alarm Thresholds

• About Laser Shutdown

• Configuring Laser Shutdown

• Configuring Optical Power Thresholds

• About Patch Connections

• Configuring Patch Connections

• About Cross Connections

To configure transparent interfaces on the Cisco ONS 15530, perform the following steps:

Step 1 Specify the protocol encapsulation and, if required, the transmission rate and OFC (open fiber control), or specify the signal clock rate (required).

Step 2 Specify the laser frequency (optional).

Step 3 Enable protocol monitoring (optional).

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

Step 5 Enable forward laser control (optional).

To configure wave interfaces on the Cisco ONS 15530, perform the following steps:

Step 1 Enable forward laser control (optional).

Step 2 Enable laser safety protocol (optional).

To configure patch connections on the Cisco ONS 15530, perform the following steps:

Step 1 Configure the patch connections between the OADM modules and the wavepatch interface of the transponder line card (required).

Step 2 Configure the patch connections between the OSC (optical supervisory channel) interface on the OADM modules and the wavepatch interface of the OSC (required if the OSC is present).

Configuring Protocol Encapsulation or Clock Rate

A transparent interface does not terminate the protocol of the signal it receives, but it does convert it from an optical signal to an electrical signal and back to an optical signal. Therefore, you must configure the signal transmission rate by specifying either the protocol encapsulation or the clock rate.

To configure the protocol encapsulation or the clock rate for a transparent interface, perform the following steps, beginning in global configuration mode:

Command

Purpose

Step 1

Switch(config)# interface transparent slot/subcard/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 2

Switch(config-if)# encapsulation {fastethernet | fddi | gigabitethernet | escon}
or

Switch(config-if)# encapsulation sysplex clo

or

Switch(config-if)# encapsulation sysplex etr
or

Switch(config-if)# encapsulation sysplex isc {compatibility | peer}

or

Switch(config-if)# encapsulation ficon {1g | 2g}
or

Switch(config-if)# encapsulation sonet {oc3 | oc12 | oc48}

or

Switch(config-if)# encapsulation sdh {stm-1 | stm-4 | stm-16}

or

Switch(config-if)# encapsulation fibrechannel {1g | 2g} [ofc {enable | disable}]

or

Switch(config-if)# clock rate value

Specifies Fast Ethernet, FDDI, Gigabit Ethernet, or ESCON. OFC¹ is disabled.

Specifies Sysplex CLO². OFC is disabled. Forward laser control is enabled on both the transparent and wave interfaces. OFC is disabled.

Specifies Sysplex ETR³. OFC is disabled.

Specifies ISC⁴ compatibility mode (1 Gbps) or peer mode (2 Gbps). OFC is enabled for compatibility mode and disabled for peer mode.

Specifies FICON encapsulation and rate. OFC is disabled.

Specifies SONET as the signal protocol and OC-3, OC-12, or OC-48 as the transmission rate. OFC is disabled.

Specifies SDH as the signal protocol and STM-1, STM-4, or STM-16 as the transmission rate. OFC is disabled.

Specifies Fibre Channel as the signal protocol and 1 Gbps or 2 Gbps as the transmission rate. Enables or disables OFC. OFC is disabled by default.

Specifies the signal transmission clock rate without an associated protocol. OFC is disabled.

Note Protocol monitoring cannot be enabled on the interface when the clock rate command is configured.

¹For information about OFC, see the "About Laser Shutdown" section.

²CLO = control link oscillator

³ETR = external timer reference

⁴ISC = Intersystem Channel Links

Note Disable autonegotiation 2-Gbps Fibre Channel client equipment connected to Cisco ONS 15530 and set the speed to match the clock rate or protocol encapsulation set on the transparent interfaces. The transponder modules only recognize the configured clock rate or protocol encapsulation and do not support autonegotiation.

Note Use the encapsulation command for clock rates supported by protocol monitoring rather than the clock rate command. For more information protocol monitoring, see the "About Protocol Monitoring" section.

Note When you must use Sysplex CLO encapsulation or Sysplex ETR encapsulation, you must configure APS bidirectional path switching. For more information on APS and bidirectional path switching, see Chapter 10, "Configuring APS."

Caution Do not configure y-cable protection with Sysplex CLO, Sysplex ETR, or ISC compatibility protocol encapsulation, or with the OFC safety protocol.

Sysplex CLO and Sysplex ETR are supported outside the nominal range of the clock rates for the Cisco ONS 15530 because of the nature of the traffic type.

Table 6-1 lists the clock rates for well-known protocols supported by the transponder line card:

Table 6-1 Supported Clock Rates for Well-Known Protocols

Well-Known Protocol

Clock Rate (in kbps)

DS3

44,736

DV1¹ in ADI² mode

270,000

E3

34,368

ESCON

200,000

Fibre Channel (1 Gbps)

1,062,500

Fibre Channel (2 Gbps)

2,125,000

FICON (1 Gbps)

1,062,500

FICON (2 Gbps)

2,125,000

Gigabit Ethernet

1,250,000

ISC Compatibility Mode (ISC-1)

1,062,500

ISC Peer Mode (ISC-3)

2,125,000

SONET OC-1

51,840

SONET OC-3/SDH STM-1

155,520

SONET OC-12/SDH STM-4

622,080

SONET OC-24

1,244,160

SONET OC-48/SDH STM-16

2,488,320

¹DV = digital video

²ADI = Asynchronous Digital Interface

Note Data coding, as well as clock rate, determines whether a particular traffic type is supported onCisco ONS 15530 transponder line cards. For information on supported traffic types, contact your SE (systems engineer) at Cisco Systems.

Note Error-free transmission of some D1 video signals (defined by the SMPTE 259M standard) and test patterns (such as Matrix SDI) cannot be guaranteed by the Cisco ONS 15500 Series because of the pathological pattern in D1 video. This well-known limitation is usually overcome by the D1 video equipment vendor, who uses a proprietary, second level of scrambling. No standards exist at this time for the second level of scrambling.

Examples

The following example shows how to configure GE (Gigabit Ethernet) encapsulation on a transparent interface:
Switch(config)# interface transparent 8/0/0Switch(config-if)# encapsulation gigabitethernet

The following example shows how to configure a clock rate on a transparent interface:
Switch(config)# interface transparent 10/1/0Switch(config-if)# clock rate 1065

Note Removing the protocol encapsulation or the clock rate does not shut down the transmit lasers. To shut down the lasers, use the shutdown command.

Displaying Protocol Encapsulation or Clock Rate Configuration

To display the protocol encapsulation configuration of a transparent interface, use the following EXEC command:

Command

Purpose

show interfaces transparent slot/subcard/0

Displays the transparent interface configuration.

Examples

The following example shows how to display the protocol encapsulation configuration of a transparent interface:
Switch# show interfaces transparent 8/0/0Transparent11/3/0 is administratively up, line protocol is up   Encapsulation: GigabitEthernetSignal monitoring: offTime of last "monitor" state change neverTime of last "encapsulation" change 00:00:03Forward laser control: OffConfigured threshold Group: NoneLoopback not setLast clearing of "show interface" counters 00:00:03Hardware is transparent

The following example shows how to display the clock rate configuration of a transparent interface:
Switch# show interfaces transparent 10/0/0Transparent10/0/0 is administratively up, line protocol is upEncapsulation: Unknown   Clock rate: 1000000 KHzSignal monitoring: offTime of last "monitor" state change neverTime of last "encapsulation" change neverForward laser control: OffConfigured threshold Group: NoneLoopback not setLast clearing of "show interface" counters neverHardware is transparent
About Transponder Line Card Channel Frequencies

The transponder line card supported by the Cisco ONS 15530 is tunable to one of two frequencies. These frequencies are adjacent on the ITU grid. For example, a transponder line card can support the frequencies for channel 5 and channel 6, but not for channel 5 and channel 8. By default, the transponder line card operates at the laser frequency for the lower channel number. However, you can configure the transponder line card to operate at the laser frequency for the higher channel number using the CLI.

Configuring Transponder Line Card Channel Frequency

To select the desired channel frequency for the transponder line cards supported by the Cisco ONS 15530, perform the following steps, beginning in global configuration mode:

Command

Purpose

Step 1

Switch(config)# interface wave slot/subcard

Switch(config-if)#

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

Step 2

Switch(config-if)# laser frequency number

Selects one of the two frequencies in GHz supported by the laser. The default is the lower frequency for the transponder module.

Note The laser requires approximately 10 seconds to change to the new frequency and stabilize. Any laser frequency commands entered during this time are ignored.

Example

The following example shows how to change the transponder line card channel frequency:
Switch(config)# interface wave 10/0Switch(config-if)# laser frequency 195700
Displaying Transponder Line Card Channel Frequency

To display the channel frequency configuration, use the following EXEC command:

Command

Purpose

show interfaces wave slot/subcard

Displays the wave interface configuration.

Example

The following example shows how to display the transponder line card channel frequency:
Switch# show interface wave 10/0Wave10/0 is down, line protocol is down Channel: 30 Frequency: 195.7 Thz Wavelength: 1531.90 nmActive Wavepatch : Wavepatch10/0/0Splitter Protected: NoSignal quality: Loss of lightReceiver power level:Forward laser control: OffLaser safety control: OffOsc physical port: NoWavelength used for inband management: NoConfigured threshold Group: NoneLoopback not setLast clearing of "show interface" counters neverHardware is data_only_port
About Protocol Monitoring

Transparent interfaces on the Cisco ONS 15530 can be configured to monitor protocol and signal performance. When monitoring is enabled, the system maintains statistics that are used to determine the quality of the signal.

The following protocols can be monitored:

•ESCON (Enterprise Systems Connection)

•Fibre Channel (1 Gbps only)

•FICON (Fiber Connection) (1 Gbps only)

•Gigabit Ethernet

•SDH (Synchronous Digital Hierarchy) (STM-1, STM-4, STM-16)

•SONET (OC-3, OC-12, OC-48)

•ISC (compatibility mode only)

Note Enabling monitoring on a transparent interface also enables monitoring on the corresponding wave interface. For example, if you enable monitoring on transparent interface 3/0/0, monitoring is also enabled on wave interface 3/0.

For Gigabit Ethernet, Fibre Channel, and FICON, the Cisco ONS 15530 monitors the code violation and running disparity error count.

For SONET errors, the Cisco ONS 15530 monitors the SONET section overhead only, not the SONET line overhead. Specifically, the Cisco ONS 15530 monitors the B1 byte and the framing bytes. The system can detect the following defect conditions:

•Loss of light

•Loss of lock (when the clock cannot be recovered from the received data stream)

•Severely errored frame

•Loss of frame

For SONET performance, the system monitors the B1 byte, which is used to compute the four SONET section layer performance monitor parameters:

The definitions for these acronyms come from the Telcordia SONET standard spec page 6-110.

•SEFS-S (second severely errored framing seconds)

•CV-S (section code violations)

•ES-S (section errored seconds)

•SES-S (section severely errored seconds)

Configuring Protocol Monitoring

To configure protocol monitoring on a transparent interface, and its corresponding wave interface, perform the following steps, beginning in global configuration mode:

Command

Purpose

Step 1

Switch(config)# interface transparent slot/subcard/0

Switch(config-if)#

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

Step 2

Switch(config-if)# monitor enable

Enables signal monitoring.

Note Protocol encapsulation must be configured on the transparent interface before enabling monitoring.

Examples

The following example shows how to enable protocol monitoring on a transparent interface:
Switch(config)# interface transparent 10/0/0Switch(config-if)# monitor enable

The following example shows how to disable protocol monitoring on a transparent interface:
Switch(config)# interface transparent 10/0/0Switch(config-if)# no monitor
Displaying Protocol Monitoring Configuration

To display the protocol monitoring configuration of a transparent interface, use the following EXEC command:

Command

Purpose

show interfaces {transparent slot/subcard/0 | wave slot/subcard}

Displays the transparent interface configuration.

Examples

The following example shows how to display the protocol monitoring configuration of a transparent interface:
Switch# show interfaces transparent 10/0/0Transparent10/0/0 is administratively up, line protocol is up  Encapsulation: Sonet Rate: oc3 Signal monitoring: onForward laser control: OffConfigured threshold Group: None Section code violation error count(bip1): 3714369135 Number of errored seconds(es): 57209 Number of severely errored seconds(ses): 57209 Number of severely errored framing seconds(sefs): 0 Number of times SEF alarm raised: 0 Number of times SF threshold exceeded: 0 Number of times SD threshold exceeded: 384Loopback not setLast clearing of "show interface" counters neverHardware is transparent

The following example shows how to display the protocol monitoring configuration of a wave interface:
Switch# show interfaces wave 7/0Wave7/0 is up, line protocol is upChannel: 31 Frequency: 195.8 Thz Wavelength: 1531.12 nmActive Wavepatch : Wavepatch7/0/0Splitter Protected: NoSignal quality: GoodReceiver power level: -14.71 dBmForward laser control: OffLaser safety control: OffOsc physical port: NoWavelength used for inband management: NoConfigured threshold Group: NoneLoopback not setLast clearing of "show interface" counters 09:20:01Hardware is data_only_port
About Alarm Thresholds

You can configure thresholds on transparent and wave interfaces that issue alarm messages to the system if the thresholds are exceeded. The threshold values are applied to both transparent and wave interfaces on a transponder line card when protocol monitoring is enabled on the transparent interface.

The rate is based on the protocol encapsulation or the clock rate for the interface. 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 transparent 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 {transparent slot/subcard/0 | wave slot/subcard}

Switch(config-if)#

Selects the transparent or wave 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 encapsulation type for the interface, that threshold type is ignored.

Table 6-2 lists the threshold error rates in errors per second for each of the protocol encapsulations.

Table 6-2 Thresholds for Monitored Protocols (Errors Per Second)

Rate

SONET OC-3 or SDH STM-1

SONET OC-12 or SDH STM-4

SONET OC-48 or SDH STM-16

Gigabit Ethernet

ESCON

FICON¹

Fibre Channel²

ISC³

3

31,753

32,000

32,000

1,244,390

199,102

1,057,731

1,057,731

1,057,731

4

12,318

27,421

31,987

124,944

19,991

106,202

106,202

106,202

5

1518

5654

17,296

12,499

2000

10,625

10,625

10,625

6

155

616

2394

1250

200

1062

1062

1062

7

15.5

62

248

125

20

106

106

106

8

1.55

6.2

24.8

12.5

2

10.6

10.6

10.6

9

0.155

0.62

2.48

1.25

0.2

1.06

1.06

1.06

¹One Gbps rate only.

²One Gbps rate only.

³Compatibility mode only.

³ 3. Rate is limited by the hardware.

Examples

The following example shows how to create an alarm threshold list and configure that list on a transparent interface:
Switch# configure terminalSwitch(config)# threshold-list sonet-countersSwitch(config-t-list)# threshold name sonet-sdh section cv degradeSwitch(config-threshold)# value rate 9Switch(config-threshold)# exitSwitch(config-t-list)# threshold name sonet-sdh section cv failureSwitch(config-threshold)# value rate 7Switch(config-threshold)# exitSwitch(config-t-list)# exitSwitch(config)# interface transparent 10/0/0Switch(config-if)# threshold-group sonet-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 transparent interfaces:
Switch(config)# threshold-list sonet-alarmsSwitch(config-t-list)# threshold name sonet-sdh section cv failureSwitch(config-threshold)# value rate 6Switch(config-threshold)# aps triggerSwitch(config-threshold)# exitSwitch(config-t-list)# exitSwitch(config)# redundancySwitch(config-red)# associate group sonet-channelSwitch(config-red-aps)# aps working transparent 3/0/0Switch(config-red-aps)# aps protection transparent 5/0/0Switch(config-red-aps)# aps y-cableSwitch(config-red-aps)# aps revertiveSwitch(config-red-aps)# enableSwitch(config-red-aps)# exitSwitch(config-red)# exitSwitch(config)# interface transparent 3/0/0Switch(config-if)# encapsulation sonet oc3Switch(config-if)# monitor enableSwitch(config-if)# threshold-group sonet-alarmsSwitch(config-if)# exitSwitch(config)# interface transparent 5/0/0Switch(config-if)# encapsulation sonet oc3Switch(config-if)# monitor enableSwitch(config-if)# threshold-group sonet-alarms
Displaying Alarm Threshold Configuration

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

Command

Purpose

show threshold-list [name]

Displays the threshold group configuration.

show interfaces {transparent slot/subcard/0 | wave slot[/subcard]}

Displays the transparent or wave interface configuration.

Examples

The following example shows how to display the configuration of a threshold group:
Switch# show threshold-list sonet-counters
Threshold List Name: sonet-countersNotification throttle timer : 5 (in secs)Threshold name : sonet-sdh section cv Severity : DegradeValue : 10e-9APS Trigger : Not setDescription : SONET BIP1 counterThreshold name : sonet-sdh section cv Severity : FailureValue : 10e-6APS Trigger : SetDescription : SONET BIP1 counter

The following example shows how to display the threshold group information for an interface:
Switch# show interfaces transparent 3/0/0Transparent3/0/0 is administratively up, line protocol is upEncapsulation: Sonet Rate: oc3Signal monitoring: onForward laser control: Off Configured threshold Group: sonet-counters Threshold monitored for: sonet-sdh section cv SF set value: 10e-8 (155 in 100 secs) SD set value: 10e-9 (155 in 1000 secs) Section code violation error count(bip1): 3713975925 Number of errored seconds(es): 57203 Number of severely errored seconds(ses): 57203 Number of severely errored framing seconds(sefs): 0 Number of times SEF alarm raised: 0 Number of times SF threshold exceeded: 0 Number of times SD threshold exceeded: 378Loopback not setLast clearing of "show interface" counters neverHardware is transparent
About Laser Shutdown

To avoid operator injury or transmission of unreliable data, or to provide quick path switchover, the Cisco ONS 15530 supports mechanisms to automatically shut down transponder line card lasers. The three types of laser shutdown mechanisms are:

•Forward laser control

•OFC safety protocol

•Laser safety control

About Forward Laser Control

When loss of light occurs on the receive signal of a transparent or wave interface, the corresponding transmitting laser on the other side of the transponder line card continues to function and might send unreliable information to the client. Forward laser control provides a means to quickly shut down a transmitting laser when such a receive signal failure occurs (see Figure 6-1). The receive signal loss of light can result from a failure in the client equipment, a receiver failure in the transponder line card, or a laser shutdown on another node in the network.

This feature is convenient for configurations, such as Sysplex, where signal protection is performed in the client hardware and a quick laser shutdown causes a quick path switchover.

Figure 6-1 Forward Laser Control Overview

About OFC

The Cisco ONS 15530 allows you to enable the OFC safety protocol on the client side interfaces. When the system detects an "open fiber," the laser that transmits to the client equipment shuts down. An open fiber condition occurs when the connectors to the client equipment are detached from the transponder line card ports or when the fiber is cut (see Figure 6-2).

Figure 6-2 OFC Overview

The OFC safety protocol conforms to the Fibre Channel standard. It applies only to the Fibre Channel and ISC compatibility mode encapsulations. The Cisco ONS 15530 interoperates with OFC-standard-compliant client equipment.

Caution Do not configure OFC with either forward laser control or laser safety control. Combining these features interferes with the OFC protocol.

Use the encapsulation command, described in the "Configuring Transponder Line Card Channel Frequency" section to configure OFC on a transparent interface.

About Laser Safety Control

The Cisco ONS 15530 allows you to enable laser safety control on the trunk side interfaces of the transponder line cards and the 2.5-Gbps ITU trunk cards. Much like OFC, the laser safety control protocol shuts down the transponder line card laser transmitting to the trunk when a fiber cut occurs or when the trunk fiber is detached from the shelf (see Figure 6-3).

Figure 6-3 Laser Safety Control Overview

Laser safety control uses the same protocol state machine as OFC, but not the same timing. Laser safety control uses the pulse interval and pulse duration timers compliant with the ALS (automatic laser shutdown) standard (ITU-T G.664).

Use laser safety control with line card protected and unprotected configurations only. Enable laser safety control on all wave interfaces, including the OSC.

Caution Laser safety control can interrupt signal transmission with splitter protected configurations. If you configure the system with splitter protection and enable laser safety control, the transmit laser to the client shuts down when an open fiber occurs on one transport fiber and signal transmission to the client is interrupted.

Configuring Laser Shutdown

This sections describes how to configure forward laser control and laser safety control on the Cisco ONS 15530 transponder line card interfaces.

Note To function correctly, configure forward laser control on both the transparent and wave interfaces on a transponder line card. For y-cable protection, forward laser control on both the transparent and wave interfaces on both transponder line cards will be configured automatically.

Configuring Forward Laser Control

To configure forward laser control for transparent and wave interfaces on a transponder line card, perform the following steps, beginning in global configuration mode:

Command

Purpose

Step 1

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

Switch(config-if)#

Selects the transparent 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.

Step 3

Switch(config-if)# exit

Returns to global configuration mode.

Step 4

Switch(config)# interface wave slot/subcard

Switch(config-if)#

Selects the wave 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.

Caution Do not configure forward laser control when OFC is enabled. Combining these features interferes with the OFC protocol.

Examples

The following example shows how to configure forward laser control for the transparent and wave interfaces on a transponder line card:
Switch(config)# interface transparent 5/0/0Switch(config-if)# laser control forward enableSwitch(config-if)# exitSwitch(config)# interface wave 5/0Switch(config-if)# laser control forward enable

Displaying Forward Laser Control Configuration

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

Command

Purpose

show interfaces {transparent slot/subcard/port | wave slot/subcard}

Displays interface information.

Example

The following example shows how to display the forward laser control configuration for an interface:
Switch# show interfaces transparent 10/0/0Transparent10/0/0 is administratively up, line protocol is upEncapsulation: Sonet Rate: oc3Signal monitoring: offTime of last "monitor" state change neverTime of last "encapsulation" change 10:18:20 Forward laser control: OnConfigured threshold Group: NoneLoopback not setLast clearing of "show interface" counters 10:18:20Hardware is transparent
Configuring Laser Safety Control

To configure laser safety control on a wave interface, perform the following steps, beginning in global configuration mode:

Command

Purpose

Step 1

Switch(config)# interface wave slot/subcard}

Switch(config-if)#

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

Step 2

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

Enables or disables laser safety control.

Note Use laser safety control only with line card protected and unprotected configurations. Enable laser safety control on all the wave interfaces in the shelf, including the OSC.

Caution Do not configure laser safety control when OFC is enabled. Combining these features interferes with the OFC safety protocol.

Example

The following example shows how to configure laser safety control on a wave interface:
Switch(config)# interface wave 8/0Switch(config-if)# laser control safety enable
Displaying Laser Safety Control Configuration

To display the laser safety control configuration of a wave interface, use the following EXEC command:

Command

Purpose

show interfaces wave slot/subcard

Displays interface information.

Example

The following example shows how to display the laser safety control configuration for an interface:
Switch# show interfaces wave 10/0Wave10/0 is administratively up, line protocol is upChannel: 25 Frequency: 195.1 Thz Wavelength: 1536.61 nmSplitter Protected: YesReceiver power level: -10.0 dBm Laser safety control: OnForward laser control: OffOsc physical port: NoWavelength used for inband management: NoConfigured threshold Group: NoneLoopback not setLast clearing of "show interface" counters neverHardware is data_only_port
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 transponder line card, 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 for the active wavepatch interfaces are as follows:

Low alarm: -28 dBm

Low warning: -24 dBm

High warning: -10 dBm

High alarm: -8 dBm

Alarm severity: major

Warning severity: not alarmed

The default values for the standby wavepatch interfaces are as follows:

Low alarm: -28 dBm

Low warning: -24 dBm

High warning: -15 dBm

High alarm: -13 dBm

Alarm severity: major

Warning severity: not alarmed

Examples

The following example shows how to configure optical power thresholds for wavepatch interfaces on a transponder line card:
Switch(config)# interface wavepatch 5/0/0Switch(config-if)# optical threshold power receive high alarm -70

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 4/0/0Wavepatch4/0/0 is up, line protocol is upReceiver power level: -23.91 dBmOptical threshold monitored for : Receive Power (in dBm)Low alarm value = -28.0 (default)Low Alarm Severity = majorLow warning value = -24.0 (default)Low Warning Severity = not alarmedHigh alarm value = -8.0 (default)High Alarm Severity = majorHigh warning value = -10.0 (default)High Warning Severity = not alarmedHardware is passive_port
About Patch Connections

Because the OADM modules are passive devices, the Cisco ONS 15530 does not detect its optical patch connection configuration. For system management purposes, you must also configure the patch connection configuration using the CLI.

Table 6-3 describes the types of patch connections on the Cisco ONS 15530.

Table 6-3 Patch Connection Types

Patch Connection

Description

Thru interface to thru interface

Connection between two OADM modules in different chassis slots.

Wavepatch interface to filter interface or
filter interface to wavepatch interface

Connection between the wavepatch on a transponder line card and the filter interface on an OADM module.

OSC wave interface to oscfilter interface or
oscfilter interface to OSC wave interface

Connection between the OSC wave interface and the oscfilter interface on the OADM module in the same chassis slot.

For more information on patch connection rules, refer to the
Cisco ONS 15530 Planning and Design Guide.

Configuring Patch Connections

To configure patch connections between OADM modules within the same shelf, use the following global configuration commands:

Command

Purpose

patch thru slot1/subcard1 thru slot2/subcard2

Configures the patch connection between two add/drop OADM modules in different chassis slots.

patch wavepatch slot1/subcard1/port1 filter slot2/subcard2/port2

or

patch filter slot1/subcard1/port1 wavepatch slot2/subcard2/port2

Configures the patch connection between a transponder line card and a OADM module.

patch wave slot/subcard oscfilter slot/subcard

or

patch oscfilter slot/subcard wave slot/subcard

Connection between the OSC wave interface and the oscfilter interface on the OADM module in the same chassis slot.

Note If you correctly patch your OADM 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 12-3.

Example

The following example shows how to configure the patch connections:
Switch# configure terminalSwitch(config)# patch thru 0/0 thru 0/1Switch(config)# patch wave 0 oscfilter 0/0Switch(config)# patch wave 1 oscfilter 0/1Switch(config)# patch wavepatch 4/0/0 filter 0/0/1Switch(config)# patch wavepatch 4/0/1 filter 0/1/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 transponder line card and a OADM module, "Channel Mismatch" appears for the patch connection. When more than one OADM 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 Error--------------- --------------- ---- -----Thru0/0 Wdm0/1 USERThru0/1 Wdm0/2 USERThru0/2 Thru1/0 USERThru1/1 Wdm1/0 USERThru1/2 Wdm1/1 USERWave0 Oscfilter0/0 USERWave1 Oscfilter1/2 USER
About Cross Connections

The client signal follows a path of interface optical cross connections through the Cisco ONS 15530. 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 {transparent slot/subcard/port | wave slot/subcard}]]

Displays the optical connections.

Examples

The following example shows the cross connections within a system configured for splitter protection:
Switch# show connect intermediateclient/ wave wave wdmwave client patch filter trk channel------------ ------------ ------- ------ --- -------Trans2/0/0 Wave2/0 2/0/0* 0/0/0 0/0 12/0/1 1/0/0 1/0 1Trans2/2/0 Wave2/2 2/2/0* 0/0/2 0/0 32/2/1 1/0/2 1/0 3Trans2/3/0 Wave2/3 2/3/0* 0/0/3 0/0 42/3/1 1/0/3 1/0 4

The following example shows the cross connections within a system configured for line card protection using splitter protected line card motherboards:
Switch# show connect intermediateclient/ wave wave wdmwave client patch filter trk channel------------ ------------ ------- ------ --- -------Trans10/0/0 Wave10/0 10/0/0* 0/3/0 0/2 2510/0/1Trans10/1/0 Wave10/1 10/1/0* 0/3/1 0/2 2610/1/1Trans10/2/0 Wave10/2 10/2/0* 0/3/2 0/2 2710/2/1Trans10/3/0 Wave10/3 10/3/0* 0/3/3 0/2 2810/3/1

	Command	Purpose
Step 1	Switch(config)# interface transparent slot/subcard/0 Switch(config-if)#	Selects the interface to configure and enters interface configuration mode.
Step 2	Switch(config-if)# encapsulation {fastethernet \| fddi \| gigabitethernet \| escon} or Switch(config-if)# encapsulation sysplex clo or Switch(config-if)# encapsulation sysplex etr or Switch(config-if)# encapsulation sysplex isc {compatibility \| peer} or Switch(config-if)# encapsulation ficon {1g \| 2g} or Switch(config-if)# encapsulation sonet {oc3 \| oc12 \| oc48} or Switch(config-if)# encapsulation sdh {stm-1 \| stm-4 \| stm-16} or Switch(config-if)# encapsulation fibrechannel {1g \| 2g} [ofc {enable \| disable}] or Switch(config-if)# clock rate value	Specifies Fast Ethernet, FDDI, Gigabit Ethernet, or ESCON. OFC¹ is disabled. Specifies Sysplex CLO². OFC is disabled. Forward laser control is enabled on both the transparent and wave interfaces. OFC is disabled. Specifies Sysplex ETR³. OFC is disabled. Specifies ISC⁴ compatibility mode (1 Gbps) or peer mode (2 Gbps). OFC is enabled for compatibility mode and disabled for peer mode. Specifies FICON encapsulation and rate. OFC is disabled. Specifies SONET as the signal protocol and OC-3, OC-12, or OC-48 as the transmission rate. OFC is disabled. Specifies SDH as the signal protocol and STM-1, STM-4, or STM-16 as the transmission rate. OFC is disabled. Specifies Fibre Channel as the signal protocol and 1 Gbps or 2 Gbps as the transmission rate. Enables or disables OFC. OFC is disabled by default. Specifies the signal transmission clock rate without an associated protocol. OFC is disabled. Note Protocol monitoring cannot be enabled on the interface when the clock rate command is configured.

Well-Known Protocol	Clock Rate (in kbps)
DS3	44,736
DV1¹ in ADI² mode	270,000
E3	34,368
ESCON	200,000
Fibre Channel (1 Gbps)	1,062,500
Fibre Channel (2 Gbps)	2,125,000
FICON (1 Gbps)	1,062,500
FICON (2 Gbps)	2,125,000
Gigabit Ethernet	1,250,000
ISC Compatibility Mode (ISC-1)	1,062,500
ISC Peer Mode (ISC-3)	2,125,000
SONET OC-1	51,840
SONET OC-3/SDH STM-1	155,520
SONET OC-12/SDH STM-4	622,080
SONET OC-24	1,244,160
SONET OC-48/SDH STM-16	2,488,320

	Command	Purpose
Step 1	Switch(config)# interface wave slot/subcard Switch(config-if)#	Selects the wave interface to configure and enters interface configuration mode.
Step 2	Switch(config-if)# laser frequency number	Selects one of the two frequencies in GHz supported by the laser. The default is the lower frequency for the transponder module.

	Command	Purpose
Step 1	Switch(config)# interface transparent slot/subcard/0 Switch(config-if)#	Selects the transparent interface to configure and enters interface configuration mode.
Step 2	Switch(config-if)# monitor enable	Enables signal monitoring. Note Protocol encapsulation must be configured on the transparent interface before enabling monitoring.

	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 {transparent slot/subcard/0 \| wave slot/subcard} Switch(config-if)#	Selects the transparent or wave interface to configure and enters interface configuration mode.
Step 10	Switch(config-if)# threshold-group name	Configures the threshold list on the interface.

Rate	SONET OC-3 or SDH STM-1	SONET OC-12 or SDH STM-4	SONET OC-48 or SDH STM-16	Gigabit Ethernet	ESCON	FICON¹	Fibre Channel²	ISC³
3	31,753	32,000	32,000	1,244,390	199,102	1,057,731	1,057,731	1,057,731
4	12,318	27,421	31,987	124,944	19,991	106,202	106,202	106,202
5	1518	5654	17,296	12,499	2000	10,625	10,625	10,625
6	155	616	2394	1250	200	1062	1062	1062
7	15.5	62	248	125	20	106	106	106
8	1.55	6.2	24.8	12.5	2	10.6	10.6	10.6
9	0.155	0.62	2.48	1.25	0.2	1.06	1.06	1.06

Command	Purpose
show threshold-list [name]	Displays the threshold group configuration.
show interfaces {transparent slot/subcard/0 \| wave slot[/subcard]}	Displays the transparent or wave interface configuration.

	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 for the active wavepatch interfaces are as follows: Low alarm: -28 dBm Low warning: -24 dBm High warning: -10 dBm High alarm: -8 dBm Alarm severity: major Warning severity: not alarmed The default values for the standby wavepatch interfaces are as follows: Low alarm: -28 dBm Low warning: -24 dBm High warning: -15 dBm High alarm: -13 dBm Alarm severity: major Warning severity: not alarmed

Patch Connection	Description
Thru interface to thru interface	Connection between two OADM modules in different chassis slots.
Wavepatch interface to filter interface or filter interface to wavepatch interface	Connection between the wavepatch on a transponder line card and the filter interface on an OADM module.
OSC wave interface to oscfilter interface or oscfilter interface to OSC wave interface	Connection between the OSC wave interface and the oscfilter interface on the OADM module in the same chassis slot.

Command	Purpose
patch thru slot1/subcard1 thru slot2/subcard2	Configures the patch connection between two add/drop OADM modules in different chassis slots.
patch wavepatch slot1/subcard1/port1 filter slot2/subcard2/port2 or patch filter slot1/subcard1/port1 wavepatch slot2/subcard2/port2	Configures the patch connection between a transponder line card and a OADM module.
patch wave slot/subcard oscfilter slot/subcard or patch oscfilter slot/subcard wave slot/subcard	Connection between the OSC wave interface and the oscfilter interface on the OADM module in the same chassis slot.