|
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 Optical Power Thresholds
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. This chapter includes the following sections:
• Configuring Protocol Encapsulation or Clock Rate
• Configuring Protocol Monitoring
• Configuring Alarm Thresholds
• Configuring Optical Power Thresholds
• Configuring Patch Connections
To configure transparent interfaces on the Cisco ONS 15540, 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, 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, perform the following steps:
Step 1 Configure the patch connections between the mux/demux modules (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}
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 (2 Gbps). OFC is enabled for compatibility mode and disabled for peer mode.
Specifies FICON 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 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.
Sysplex CLO and Sysplex ETR are supported outside the nominal range of the clock rates for the Cisco ONS 15540 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 on Cisco ONS 15540 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 2.5-Gbps 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.
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 5, "Configuring Splitter Protection and Line Card Protection with 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 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 (InterSystem Channel) links compatibility mode
•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 15540 monitors the code violation and running disparity error count.
For SONET errors, the Cisco ONS 15540 monitors the SONET section overhead only, not the SONET line overhead. Specifically, the Cisco ONS 15540 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)
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:
Example
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.
Example
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 2.5-Gbps 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.
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 or SDH STM-1 SONET OC-12 or SDH STM-4 SONET OC-48 or SDH STM-16 Gigabit Ethernet ESCON FICON Fibre Channel1 ISC23
31,7533
32,0003
32,0003
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
1 One Gbps rate only.
2 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 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:
Example
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 supports mechanisms to automatically shut down 2.5-Gbps transponder module 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 2.5-Gbps transponder module 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 4-1). The receive signal loss of light can result from a failure in the client equipment, a receiver failure in the 2.5-Gbps transponder module, 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 4-1 Forward Laser Control Overview
About OFC
The Cisco ONS 15540 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 2.5-Gbps 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 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 allows you to enable laser safety control on the trunk side interfaces of the 2.5-Gbps transponder modules. Much like OFC, the laser safety control protocol shuts down the 2.5-Gbps 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 2.5-Gbps transponder module interfaces.
Note To function correctly, configure forward laser control on both the transparent and wave interfaces on a 2.5-Gbps transponder module. For y-cable protection, configure forward laser control on both the transparent and wave interfaces on both 2.5-Gbps transponder modules.
Configuring Forward Laser Control
To configure forward laser control on a 2.5-Gbps 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 2.5-Gbps 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
The following example shows how to configure forward laser control for an OSC wave interface:
Switch(config)# interface wave 0
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 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 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 module, perform the following steps, beginning in global configuration mode:
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/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 optical power threshold 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 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, 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.
For more information on patch connection rules, refer to the
Cisco ONS 15540 ESP Planning and Design Guide.Configuring Patch Connections
To configure patch connections between mux/demux modules within the same shelf, use the following global configuration commands:
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 9-3.
Example
The following example shows how configure the patch connections between OSC interfaces and between mux/demux modules:
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
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 2.5-Gbps 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 interface optical cross connections through the Cisco ONS 15540. Figure 4-4 shows an example of cross connections. Knowing the path of a signal through the shelf helps with system management and troubleshooting.
Figure 4-4 Optical Cross Connection Example
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
Posted: Thu Jul 15 11:15:13 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.