|
Table Of Contents
Configuring 2.5-Gbps Transponder Module Interfaces and Patch Connections
Configuring Protocol Encapsulation or Clock Rate
Displaying Protocol Encapsulation or Clock Rate Configuration
Configuring Protocol Monitoring
Displaying Protocol Monitoring Configuration
Displaying Alarm Threshold Configuration
Configuring Forward Laser Control
Configuring Laser Safety Control
Configuring Transponder Channel Frequency
Displaying Transponder Channel Frequency
Configuring Optical Power Thresholds
Displaying Optical Power Threshold Configuration
About Performance History Counters
Displaying Performance History Counters
Configuring 2.5-Gbps 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:
• Configuring Protocol Encapsulation or Clock Rate
• Configuring Protocol Monitoring
• Configuring Alarm Thresholds
• Configuring Transponder Channel Frequency
• Configuring Optical Power Thresholds
• Configuring Patch Connections
• About Performance History Counters
• Displaying Performance History Counters
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 xviii. Also refer to the "Hardware Supported" section and "Feature Set" section of the latest release notes for the Cisco ONS 15540 ESPx.
To configure transparent interfaces on the Cisco ONS 15540 ESPx, 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 Enable protocol monitoring (optional).
Step 3 Create alarm threshold lists and apply them to the interfaces (optional).
Step 4 Enable forward laser control (optional).
To configure wave interfaces on the Cisco ONS 15540 ESPx, 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 15540 ESPx, perform the following steps:
Step 1 Configure the patch connections (required).
Step 2 Configure the patch connections between the OSC (optical supervisory channel) interface on the mux/demux motherboards and the mux/demux modules (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 PurposeStep 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}
orSwitch(config-if)# encapsulation sysplex clo
orSwitch(config-if)# encapsulation sysplex etr
orSwitch(config-if)# encapsulation sysplex isc {compatibility | peer [1g | 2g]}
orSwitch(config-if)# encapsulation ficon {1g | 2g}
orSwitch(config-if)# encapsulation sonet {oc3 | oc12 | oc48}
orSwitch(config-if)# encapsulation sdh {stm-1 | stm-4 | stm-16}
orSwitch(config-if)# encapsulation fibrechannel {1g | 2g} [ofc {enable | disable}]
orSwitch(config-if)# clock rate value
Specifies Fast Ethernet, FDDI, Gigabit Ethernet, or ESCON. OFC1 is disabled.
Specifies Sysplex CLO2 . OFC is disabled. Forward laser control is enabled on both the transparent and wave interfaces. OFC is disabled.
Specifies Sysplex ETR3 . OFC is disabled.
Specifies ISC4 compatibility mode (1 Gbps) or peer mode (1 Gbps or 2 Gbps). OFC is enabled for compatibility mode and disabled for peer mode.
Specifies FICON as the signal protocol and 1 Gbps or 2 Gbps as the transmission 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.
1 For information about OFC, see the "About Laser Shutdown" section.
2 CLO = control link oscillator
3 ETR = external timer reference
4 ISC = Intersystem Channel Links
Note Disable autonegotiation 2-Gbps Fibre Channel client equipment connected to Cisco ONS 15540 ESPx 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.
Caution Do not configure y-cable protection with Sysplex CLO, Sysplex ETR, or ISC compatibility protocol encapsulation, or with the OFC safety protocol.
Note Sysplex CLO and Sysplex ETR are supported outside the nominal range of the clock rates for the Cisco ONS 15540 ESPx because of the nature of the traffic type.
Table 4-1 lists the clock rates for well-known protocols supported by the 2.5-Gbps transponder module:
1 DV = digital video
2 ADI = Asynchronous Digital Interface
Note Data coding, as well as clock rate, determines whether a particular traffic type is supported onCisco ONS 15540 ESPx transponder modules. 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.
The following ranges are not supported by the SM transponder module hardware and the MM transponder module hardware:
•851,000 kbps to 999,999 kbps
•1,601,000 kbps to 1,999,999 kbps
For clock rate values outside of these unsupported ranges and not listed in Table 4-1, contact your SE (systems engineer) at Cisco Systems.
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.
Caution The SFP optics supported by the extended range transponder modules yield optimal performance at the data rates for which the SFP optics are explicitly designed. Configuring a protocol encapsulation or clock rate outside of the clock rate specifications for the SFP optics could result in suboptimal performance, depending on the SFP optics characteristics (such as receiver sensitivity and output power).
For information on SFP optics specifications, refer to the Cisco ONS 15540 ESPx Hardware Installation Guide.
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 7, "Configuring APS."
Examples
The following example shows how to configure GE (Gigabit Ethernet) encapsulation on a transparent interface:
Switch(config)# interface transparent 8/0/0
Switch(config-if)# encapsulation gigabitethernet
The following example shows how to configure a clock rate on a transparent interface:
Switch(config)# interface transparent 10/1/0
Switch(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 Purposeshow 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/0
Transparent11/3/0 is up, line protocol is up
Encapsulation: GigabitEthernet
Signal monitoring: off
Time of last "monitor" state change never
Time of last "encapsulation" change 00:00:03
Forward laser control: Off
Configured threshold Group: None
Loopback not set
Last clearing of "show interface" counters 00:00:03
Hardware is transparent
The following example shows how to display the clock rate configuration of a transparent interface:
Switch# show interfaces transparent 10/1/0
Transparent11/3/0 is up, line protocol is up
Encapsulation: Unknown
Clock rate: 1000000 KHz
Signal monitoring: off
Time of last "monitor" state change never
Time of last "encapsulation" change never
Forward laser control: Off
Configured threshold Group: None
Loopback not set
Last clearing of "show interface" counters never
Hardware is transparent
About Protocol Monitoring
Transparent interfaces on the Cisco ONS 15540 ESPx 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 and 2 Gbps)
•FICON (Fiber Connection) (1 Gbps and 2 Gbps)
•Gigabit Ethernet
•ISC (InterSystem Channel) links compatibility mode
•ISC links peer mode(1-Gbps and 2-Gbps)
•SDH (Synchronous Digital Hierarchy) (STM-1, STM-4, STM-16)
•SONET (OC-3, OC-12, OC-48)
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.
Note To monitor 2-Gbps FC, FICON, and ISC links peer mode, you must upgrade the transponder module functional image to release 1.A3. For information on upgrading functional images, refer to the Cisco ONS 15540 ESPx Software Upgrade Guide.
For GE, FC, and FICON traffic, the Cisco ONS 15540 ESPx monitors the following conditions:
•CVRD (code violation running disparity) error counts
•Loss of Sync
•Loss of Lock
•Loss of Light
For SONET errors, the Cisco ONS 15540 ESPx monitors the SONET section overhead only, not the SONET line overhead. Specifically, the Cisco ONS 15540 ESPx 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:
•SEFS-S (second severely errored framing seconds)
•CV-S (section code violations)
•ES-S (section errored seconds)
•SES-S (section severely errored seconds)
For ISC traffic, the system monitors the following conditions:
•CVRD error counts
•Loss of CDR (clock data recovery) Lock
•Loss of Light
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:
Examples
The following example shows how to enable protocol monitoring on a transparent interface:
Switch(config)# interface transparent 10/0/0
Switch(config-if)# monitor enable
The following example shows how to disable protocol monitoring on a transparent interface:
Switch(config)# interface transparent 10/0/0
Switch(config-if)# no monitor enable
Displaying Protocol Monitoring Configuration
To display the protocol monitoring configuration of a transparent interface, use the following EXEC command:
Command Purposeshow 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/0
Transparent10/0/0 is up, line protocol is up
Signal quality: Signal degrade threshold exceeded
Encapsulation: Sonet Rate: oc3
Signal monitoring: on
Forward laser control: Off
Configured 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: 384
Loopback not set
Last clearing of "show interface" counters never
Hardware is transparent
The following example shows how to display the protocol monitoring configuration of a wave interface:
Switch# show interfaces wave 10/0
Wave10/0 is up, line protocol is up
Channel: 25 Frequency: 195.1 Thz Wavelength: 1536.61 nm
Splitter Protected: No
Receiver power level: -7.0 dBm
Laser safety control: Off
Forward laser control: Off
Osc physical port: No
Wavelength used for inband management: No
Configured threshold Group: None
Section code violation error count(bip1): 929326
Number of errored seconds(es): 30
Number of severely errored seconds(ses): 30
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: 0
Loopback not set
Last clearing of "show interface" counters never
Hardware 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 module 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. Signal degrade and signal failure are indicators of signal quality based on the signal data stream. Signal degrade is reported when the number of errors reported per second is more than the signal degrade threshold. Signal failure is reported when the number of errors per second is more than the signal failure threshold.
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 PurposeStep 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.
Note For y-cable protected transparent and wave interfaces, disable monitoring on the interface with the no monitor command before removing an alarm threshold. Use the show aps command to determine the protection configuration for the interface.
Table 4-2 lists the threshold error rates in errors per second for each of the protocol encapsulations.
Table 4-2 Thresholds for Monitored Protocols (Errors Per Second)
Rate SONET OC-3 / SDH STM-1 SONET OC-12 / SDH STM-4 SONET OC-48 / SDH STM-16 GE CVRD ESCON CVRD FC/ FICON 1G CVRD FC/ FICON 2G CVRD ISC CVRD13
31,753
32,000
32,000
125000
199,102
110000
220000
1,057,731
4
12,318
27,421
31,987
12500
19,991
11000
22000
106,202
5
1518
5654
17,296
1250
2000
1100
2200
10,625
6
155
616
2394
125
200
110
220
1062
7
15.5
62
248
13
20
11
22
106
8
1.55
6.2
24.8
1.3
2
1.1
2.2
10.6
9
0.155
0.62
2.48
0.13
0.2
0.11
0.22
1.06
1 Compatibility mode only.
Examples
The following example shows how to create an alarm threshold list and configure that list on a transparent interface:
Switch# configure terminal
Switch(config)# threshold-list sonet-counters
Switch(config-t-list)# threshold name sonet-sdh section cv degrade
Switch(config-threshold)# value rate 9
Switch(config-threshold)# exit
Switch(config-t-list)# threshold name sonet-sdh section cv failure
Switch(config-threshold)# value rate 7
Switch(config-threshold)# exit
Switch(config-t-list)# exit
Switch(config)# interface transparent 10/0/0
Switch(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-alarms
Switch(config-t-list)# threshold name sonet-sdh section cv 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 sonet-channel
Switch(config-red-aps)# aps working transparent 3/0/0
Switch(config-red-aps)# aps protection transparent 3/0/0
Switch(config-red-aps)# aps y-cable
Switch(config-red-aps)# aps revertive
Switch(config-red-aps)# enable
Switch(config-red-aps)# exit
Switch(config-red)# exit
Switch(config)# interface transparent 3/0/0
Switch(config-if)# encap sonet oc3
Switch(config-if)# monitor enable
Switch(config-if)# threshold-group sonet-alarms
Switch(config-if)# exit
Switch(config)# interface transparent 5/0/0
Switch(config-if)# encap sonet oc3
Switch(config-if)# monitor enable
Switch(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:
Examples
The following example shows how to display the configuration of a threshold group:
Switch# show threshold-list sonet-counters
Threshold List Name: sonet-counters
Notification throttle timer : 5 (in secs)
Threshold name : sonet-sdh section cv Severity : Degrade
Value : 10e-9
APS Trigger : Not set
Description : SONET BIP1 counter
Threshold name : sonet-sdh section cv Severity : Failure
Value : 10e-6
APS Trigger : Set
Description : SONET BIP1 counter
The following example shows how to display the threshold group information for an interface:
Switch# show interfaces transparent 3/1/0
Transparent3/1/0 is up, line protocol is up
Encapsulation: Sonet Rate: oc3
Signal monitoring: on
Forward 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: 378
Loopback not set
Last clearing of "show interface" counters never
Hardware is transparent
About Laser Shutdown
To avoid operator injury or transmission of unreliable data, or to provide quick path switchover, the Cisco ONS 15540 ESPx supports mechanisms to automatically shut down transponder module lasers. The three types of laser shutdown mechanisms are:
•Forward laser control (FLC)
•Open Fibre Control (OFC) safety protocol
•Laser safety control
About Forward Laser Control
When loss of light occurs on a receive interface (client, trunk, or intermediate) in a DWDM network, the corresponding transmitting laser on the far end of the network continues to function and may send unreliable information to the client. FLC provides a means to quickly shut down a transmitting laser when a receive signal failure occurs and pass the fault to the client devices ( Figure 4-1). Loss of light can result from a failure in upstream optics or in the client equipment, a laser shutdown on an upstream node in the network, or a receiver failure in the module.
Figure 4-1 Forward Laser Control Overview
FLC works by optical shutdown or in-band signaling.
•In optical shutdown, all intermediate transmitters (lasers) are shut down when loss of light is detected. As a hop shuts down, the loss of light is passed to the next hop causing that hop to shut down. When a hop receives light causing its laser to restart, the signal is passed to the next hop, causing its laser to restart. Optical shutdown is used primarily by transparent transponders.
Optical shutdown is independent of service protocol. A disadvantage to optical shutdown is the delay caused by the shutdown and restart on the intermediate lasers. Services and clients that include shut/unshut of their transmitters in their link initialization protocol and that expect peer responses within the loop propagation delay may not be able to initialize their links through the DWDM with FLC enabled.
•In-band signaling occurs when a link break is detected by the edge DWDM device on the far end, but shutdown of the intermediate optics on the trunk is not done. This method is also referred to as end-to-end FLC or E2EFLC. The advantage of in-band signaling is that it provides faster loop response for fault propagation and restoration than regular FLC. Unlike optical shutdown, in-band signaling is protocol dependent and cannot be applied to generic or unknown traffic types. This method of FLC is used by specific protocol types on the transparent transponders and by aggregation cards on the Cisco ONS 15530.
FLC cannot be configured with OFC or ISC (Compatibility Mode). For the following services, the IOS software enables FLC in both directions during encapsulation configuration. In these cases, a user should not modify FLC:
•Sysplex ETR
•Sysplex CLO
•Sysplex ISC peer mode
•All Y-cable automatic protection switching configurations
FLC is recommended for Gigabit Ethernet and FICON. For Gigabit Ethernet and FICON without FLC enabled, network fault propagation and recovery are dependent on the client device. Client fault propagation and detection may not work properly without FLC.
About Open Fibre Control
The Cisco ONS 15540 ESPx 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 ports or when the fiber is cut (see Figure 4-2).
Figure 4-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 15540 ESPx 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 Protocol Encapsulation or Clock Rate" section to configure OFC on a transparent interface.
About Laser Safety Control
The Cisco ONS 15540 ESPx allows you to enable laser safety control on the trunk side interfaces of the transponder modules. Much like OFC, the laser safety control protocol shuts down the transponder module laser transmitting to the trunk when a fiber cut occurs or when the trunk fiber is detached from the shelf (see Figure 4-3).
Figure 4-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 15540 ESPx transponder module interfaces.
Note To function correctly, configure forward laser control on both the transparent and wave interfaces on a transponder module.
Configuring Forward Laser Control
To configure forward laser control on a transponder module transparent and wave interfaces, perform the following steps, beginning in global configuration mode:
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 module:
Switch(config)# interface transparent 5/1/0
Switch(config-if)# laser control forward enable
Switch(config-if)# exit
Switch(config)# interface wave 5/1
Switch(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 Purposeshow 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/0
Transparent10/0/0 is up, line protocol is up
Encapsulation: Sonet Rate: oc3
Signal monitoring: off
Time of last "monitor" state change never
Time of last "encapsulation" change 10:18:20
Forward laser control: On
Configured threshold Group: None
Loopback not set
Last clearing of "show interface" counters 10:18:20
Hardware is transparent
Configuring Laser Safety Control
To configure laser safety control on a wave interface, perform the following steps, beginning in global configuration mode:
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/0
Switch(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:
Example
The following example shows how to display the laser safety control configuration for an interface:
Switch# show interfaces wave 3/1
launch2#show interfaces wave 10/0
Wave10/0 is up, line protocol is up
Channel: 25 Frequency: 195.1 Thz Wavelength: 1536.61 nm
Splitter Protected: Yes
Receiver power level: -10.0 dBm
Laser safety control: On
Forward laser control: Off
Osc physical port: No
Wavelength used for inband management: No
Configured threshold Group: None
Loopback not set
Last clearing of "show interface" counters never
Hardware is data_only_port
Configuring Transponder Channel Frequency
The transponders supported by the Cisco ONS 15540 ESPx transmits at one of two channel frequencies. You can select the channel frequency using the CLI (command-line interface). To change the channel frequency transmitted by the transponder module laser, perform the following steps, beginning in global configuration mode:
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 channel frequency:
Switch(config)# interface wave 10/0
Switch(config-if)# laser frequency 192300
Displaying Transponder Channel Frequency
To display the channel frequency configuration, use the following EXEC command:
Example
The following example shows how to verify the transponder channel frequency:
Switch# show interface wave 10/0
Wave10/0 is down, line protocol is down
Channel: 30 Frequency: 195.7 Thz Wavelength: 1531.90 nm
Active Wavepatch : Wavepatch10/0/0
Splitter Protected: No
Signal quality: Loss of light
Receiver power level:
Forward laser control: Off
Laser safety control: Off
Osc physical port: No
Wavelength used for inband management: No
Configured threshold Group: None
Loopback not set
Last clearing of "show interface" counters never
Hardware 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 a wavepatch interface on a transponder module, perform the following steps, beginning in global configuration mode:
Examples
The following example shows how to configure optical power thresholds for a wavepatch interface on a transponder module:
Switch(config)# interface wavepatch 5/0/0
Switch(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:
Example
The following example shows how to display the forward laser control configuration for an interface:
Switch# show interfaces wavepatch 4/0/0
Wavepatch4/0/0 is up, line protocol is up
Receiver power level: -23.91 dBm
Optical threshold monitored for : Receive Power (in dBm)
Low alarm value = -28.0 (default)
Low Alarm Severity = major
Low warning value = -24.0 (default)
Low Warning Severity = not alarmed
High alarm value = -8.0 (default)
High Alarm Severity = major
High warning value = -10.0 (default)
High Warning Severity = not alarmed
Hardware is passive_port
About 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 connection configuration using the CLI.
Note If you correctly patched your mux/demux modules, mux/demux motherboards, and line card motherboards, no CLI configuration is necessary for the signal to pass from the client to the trunk fiber.
Table 4-3 describes the types of patch connections on the Cisco ONS 15540 ESPx.
For more information on patch connection rules, refer to the Cisco ONS 15540 ESPx Planning Guide.
Configuring Patch Connections
To configure patch connections between mux/demux modules within the same shelf, use the following global configuration commands:
Command Purposepatch thru slot/subcard1 wdm slot/subcard2
or
patch wdm slot/subcard1 thru slot/subcard2
Configures the patch connection between two add/drop mux/demux modules in the same chassis slot.
patch thru slot1/subcard1 thru slot2/subcard2
Configures the patch connection between two add/drop mux/demux modules in different chassis slots.
patch filterband slot1/subcard1/port1 filtergroup slot2/subcard2/port2
or
patch filtergroup slot1/subcard1/port1 filterband slot2/subcard2/port2
Configures the patch connection between a terminal mux/demux module supporting channels 1 through 16 and a terminal mux/demux module supporting channels 17 through 32 in the same chassis slot or in different chassis slots.
patch wave slot oscfilter slot/subcard
or
patch oscfilter slot/subcard wave slot
Configures the patch connection between an OSC wave interface on a mux/demux motherboard and an OSC oscfilter interface on a mux/demux module in the same chassis slot.
Note Correct patch command configuration for the oscfilter and OSC wave interfaces is required for bidirectional APS to function over the OSCP (see the "About Path Switching" section on page 7-17).
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 wavepatch interface on the line card motherboard and a filter interface on a mux/demux module or a mux/demux motherboard (Cisco ONS 15540 ESPx only).
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.
Figure 4-4 shows an example of a shelf configured with splitter protection for 12 channels.
Figure 4-4 Example Splitter Protected Shelf Configuration
The line card motherboards directly connect to the optical filter connectors on the mux/demux modules.
Example
The following example shows how to configure the patch connections between OSC interfaces, between mux/demux modules, and between the line card motherboards and the mux/demux modules in Figure 4-4:
Switch#
configure terminal
Switch(config)#
patch thru 0/0 wdm 0/1
Switch(config)#
patch thru 0/1 wdm 0/2
Switch(config)#
patch thru 0/2 thru 1/0
Switch(config)#
patch thru 1/1 wdm 1/0
Switch(config)#
patch thru 1/2 wdm 1/1
Switch(config)#
patch wave 0 oscfilter 0/0
Switch(config)#
patch wave 1 oscfilter 1/2
Switch(config)#
patch wavepatch 2/0/0 filter 0/0/0
Switch(config)#
patch wavepatch 2/1/0 filter 0/0/1
Switch(config)#
patch wavepatch 2/2/0 filter 0/0/2
Switch(config)#
patch wavepatch 2/3/0 filter 0/0/3
Switch(config)#
patch wavepatch 2/0/1 filter 1/0/0
Switch(config)#
patch wavepatch 2/1/1 filter 1/0/1
Switch(config)#
patch wavepatch 2/2/1 filter 1/0/2
Switch(config)#
patch wavepatch 2/3/1 filter 1/0/3
Switch(config)#
patch wavepatch 5/0/0 filter 0/1/0
Switch(config)#
patch wavepatch 5/1/0 filter 0/1/1
Switch(config)#
patch wavepatch 5/2/0 filter 0/1/2Switch(config)# patch wavepatch 5/3/0 filter 0/1/3
Switch(config)#
patch wavepatch 5/0/1 filter 1/1/0
Switch(config)#
patch wavepatch 5/1/1 filter 1/1/1
Switch(config)#
patch wavepatch 5/2/1 filter 1/1/2
Switch(config)#
patch wavepatch 5/3/1 filter 1/1/3
Switch(config)#
patch wavepatch 8/0/0 filter 0/2/0
Switch(config)#
patch wavepatch 8/1/0 filter 0/2/1
Switch(config)#
patch wavepatch 8/2/0 filter 0/2/2
Switch(config)#
patch wavepatch 8/3/0 filter 0/2/3
Switch(config)#
patch wavepatch 8/0/1 filter 1/2/0
Switch(config)#
patch wavepatch 8/1/1 filter 1/2/1
Switch(config)#
patch wavepatch 8/2/1 filter 1/2/2
Switch(config)#
patch wavepatch 8/3/1 filter 1/2/3
Displaying Patch Connections
To display the patch connections, use the following privileged EXEC command:
Note The error field in the show patch command output helps troubleshoot shelf misconfigurations. When there is a channel mismatch between a 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 Error
--------------- --------------- ---- -----
Thru0/0 Wdm0/1 USER
Thru0/1 Wdm0/2 USER
Thru0/2 Thru1/0 USER
Thru1/1 Wdm1/0 USER
Thru1/2 Wdm1/1 USER
Wave0 Oscfilter0/0 USER
Wave1 Oscfilter1/2 USER
About Cross Connections
The client signal follows a path of optical cross connections through the Cisco ONS 15540 ESPx. Figure 4-5 shows an example of cross connections. Knowing the path of a signal through the shelf helps with system management and troubleshooting.
Figure 4-5 Optical Cross Connection Example on the Cisco ONS 15540 ESPx
Displaying Cross Connections
To display the signal path cross connections, use the following privileged EXEC command:
Command Purposeshow 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 intermediate
client/ wave wave wdm
wave client patch filter trk channel
------------ ------------ ------- ------ --- -------
Trans2/0/0 Wave2/0 2/0/0* 0/0/0 0/0 1
2/0/1 1/0/0 1/0 1
Trans2/2/0 Wave2/2 2/2/0* 0/0/2 0/0 3
2/2/1 1/0/2 1/0 3
Trans2/3/0 Wave2/3 2/3/0* 0/0/3 0/0 4
2/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 intermediate
client/ wave wave wdm
wave client patch filter trk channel
------------ ------------ ------- ------ --- -------
Trans10/0/0 Wave10/0 10/0/0* 0/3/0 0/2 25
10/0/1
Trans10/1/0 Wave10/1 10/1/0* 0/3/1 0/2 26
10/1/1
Trans10/2/0 Wave10/2 10/2/0* 0/3/2 0/2 27
10/2/1
Trans10/3/0 Wave10/3 10/3/0* 0/3/3 0/2 28
10/3/1
About Performance History Counters
Cisco ONS 15540 ESPx supports 15 minute based performance history counters. You can use the performance history counters to track the performance of the Cisco ONS 15540 ESPx interfaces.
There are three types of performance history counters: current, 15-minute history, and 24-hour. Cisco ONS 15540 ESPx uses these counters to store the performance data for the following time periods:
•The current 15 minutes (using the current counter).
•The last 24 hours (using ninety six 15-minute history counters).
•The previous 1 day (using the 24-hour counter).
When the Cisco ONS 15540 ESPx system boots up, a continuously incrementing current counter is started. At the end of 15 minutes, this current counter is converted to a static 15-minute history counter with an interval number 1, and a new current counter is started with an interval number 2.
This process continues for 24 hours, by the end of which, ninety six 15-minute history counters are created. After the creation of the ninety sixth 15-minute history counter, a new 24-hour counter is created along with a current counter that has an interval number 1. The 24-hour counter has the aggregated data of all the ninety six 15-minute history counters.
The 15-minute history counters that are created thereafter overwrite the existing set of ninety six 15-minute history counters, in the order they were created. Again, after the creation of the ninety sixth 15-minute history counter, the contents of the existing 24-hour counter are overwritten with new values. This entire process continues in a cyclic fashion.
Note The performance history counters are reset if you reboot the Cisco ONS 15540 ESPx system, insert or remove the line card or SFP online, or change the encapsulation.
The performance history counters synchronize periodically from the primary CPU switch module to the standby CPU switch module enabling the system to preserve the performance data across a CPU switch module switchover.
Note To enable or disable the syncing of the performance history counters to the standby CPU switch module, execute the auto-sync counter interfaces command.
Displaying Performance History Counters
To display the performance history counters, use the following EXEC commands:
Command Purposeshow performance current [interface]
Displays the current counter for the specified interface1 .
show performance history [interface] [interval number]
Displays the 15-minute history counter for the specified interface and interval number1.
show performance 24-hour [interface]
Displays the 24-hour counter for the specified interface1.
1 If you do not specify the interface or interval number, the performance history counters for all interfaces or interval numbers are displayed.
To clear and reset all performance history counters, use the following EXEC command:
Command Purposeclear performance history [interface]
Clears the performance history counters for the specified interface.
Performance history counters are supported only for the ESCON, FC, FICON, Gigabit Ethernet, and Sysplex ISC encapsulations on the transparent interface. The wave interface counters are not supported.
Examples
The following example shows how to display the current counter for a transparent interface:
Switch# show performance current transparent 2/0/0
Current 15 minute performance register
--------------------------------------
Interface : Transparent2/0/0
Interval Number : 32
Elapsed Time(seconds) : 715
Valid Time(seconds) : 715
Code violation and running disparity error count : 0
The following example shows how to display the 15-minute history counter for a transparent interface:
Switch# show performance history transparent 2/0/0 10
15 minute performance history register
--------------------------------------
Interface : Transparent2/2/0
Interval Number : 10
Total Time(seconds) : 900
Valid Time(seconds) : 900
Code violation and running disparity error count : 0
The following example shows how to display the 24-hour counter for a transparent interface:
Switch# show performance 24-hour transparent 2/0/0
24 hour performance register
----------------------------
Interface : Transparent2/0/0
Total Time(seconds) : 86400
Valid Time(seconds) : 86400
Code violation and running disparity error count : 0
Posted: Wed Apr 26 03:10:58 PDT 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.