|
|
Table Of Contents
Interface Configuration Commands
cdl defect-indication force hop-endpoint
optical attenuation automatic desired-power
optical threshold power receive
show cdl flow defect-indication
Interface Configuration Commands
Use the following commands to configure and monitor the interfaces on the Cisco ONS 15530.
cdl defect-indication force hop-endpoint
To configure an interface as an end-of-hop, use the cdl defect-indication force hop-endpoint command. To disable end-of-hop configuration on an interface, use the no form of this command.
cdl defect-indication force hop-endpoint
no cdl defect-indication force hop-endpoint
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
EV-Release
•
•
Usage Guidelines
Use this command to configure the interface as a hop endpoint for in-band message channel defect indications.
A node acting as an end-of-hop terminates hop-by-hop defect indications for the in-band message channel. If you use the cdl defect-indication force hop-endpoint command, it is only in effect when APS is not configured on the interface. When APS is configured, the node always acts as end-of-hop. If APS is not configured, we recommend forcing end-of-hop at administrative boundaries. This ensures that FDI-H (forward defect indication hop) and BDI-H (backward defect indication hop) between two administrative domains reflect only errors that occur between the domains.
Examples
The following example shows how to enable hop endpoint on an interface.
Switch# configure terminalSwitch(config)# interface waveethernetphy 8/0Switch(config-if)# cdl defect-indication force hop-endpointRelated Commands
cdl enable
To enable in-band message channel functionality on an interface, use the cdl enable command. To disable in-band message channel functionality, use the no form of this command.
cdl enable
no cdl enable
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Enable the in-band message channel on both interfaces supporting the signal.
Examples
The following example shows how to enable in-band message channel on an interface.
Switch# configure terminalSwitch(config)# interface esconphy 10/0/0Switch(config-if)# cdl enableRelated Commands
cdl flow identifier
To configure the in-band message channel flow identifier on an esconphy, gigabitphy, or twogigabitphy interface, use the cdl flow identifier command.
To remove the flow identifier, use the no form of this command.
cdl flow identifier number
no cdl flow identifier
Syntax Description
Defaults
255
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Configure the same in-band message channel flow identifier on both interfaces supporting the signal.
Note
Examples
The following example shows how to configure the flow identifier on an interface.
Switch# configure terminalSwitch(config)# interface esconphy 10/0/0Switch(config-if)# cdl flow identifier 100Related Commands
Specifies the in-band message channel flow identifier values for all esconphy interfaces on an ESCON aggregation card.
Displays interface information.
cdl flow identifier reserve
To configure the in-band message channel flow identifiers on all esconphy interfaces on an ESCON aggregation card, use the cdl flow identifier reserve command. To remove the flow identifiers, use the no form of this command.
cdl flow identifier reserve group-name
no cdl flow identifier reserve
Syntax Description
Defaults
255
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command when the traffic from an ESCON aggregation card is mixed with GE traffic on a 10-Gbps ITU trunk card. This command ensures that all ten interfaces have flow identifiers, even when the card is not fully populated with SFPs. The command is supported on the portgroup interface.
Configure the same in-band message channel flow identifiers on both interfaces supporting the signal.
If the cdl flow identifier command is used to configure a flow identifier on an esconphy interface, that flow identifier takes precedence over a reserved flow identifier.
Note
Examples
The following example shows how to configure the flow identifiers for all esconphy interfaces on an ESCON aggregation card.
Switch# configure terminalSwitch(config)# interface portgroup 10/0/0Switch(config-if)# cdl flow identifier reserve group-1Related Commands
Specifies the in-band message channel flow identifier value.
Displays interface information.
clear performance history
To clear and reset the performance history counters, use the clear performance history command.
clear performance history [interface]
Syntax Description
Defaults
Clears all performance history counters (the current counter, all 15-minute history counters, and the 24-hour counter) for all Cisco ONS 15530 interfaces.
Command Modes
EXEC and privileged EXEC.
Command History
This table includes the following release-specific history entries:
Usage Guidelines
Use this command to clear and reset the performance history counters.
Examples
The following example shows how to clear the performance history counters for a transparent interface.
Switch# clear performance history transparent 8/0/0Reset performance history on interface?[confirm]ySwitch#Related Commands
clock rate
To configure the signal clock rate without an associated protocol on a transparent interface, use the clock rate command. To disable the clock rate, use the no form of this command.
clock rate value
no clock rate
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
You can configure either the signal clock rate with either the encapsulation command or the clock rate command, but not both. Protocol monitoring cannot be enabled on the interface when the clock rate command is configured because no protocol is specified.
Note
Table 3-1 lists the clock rates for well-known protocols supported by the transponder line card:
1 DV = digital video
2 ADI = Asynchronous Digital Interface
Note
Examples
The following example shows how to configure the signal clock rate on an interface.
Switch# configure terminalSwitch(config)# interface transparent 10/0/0Switch(config-if)# clock rate 125000Related Commands
Specifies the protocol encapsulation for a transparent interface.
Displays interface information.
connect
To configure the signal cross connections through the switch fabric, use the connect command. To remove the cross connection configuration, use the no form of the command.
connect interface1 interface2 [override]
no connect interface1 interface2
Syntax Description
interface1 interface2
Specifies the interfaces to be cross connected. See the " Usage Guidelines" section for valid interface types.
override
Changes the cross connect state from protection to provisioned.
Defaults
None
Command Modes
Global configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to configure cross connections through the switch fabric.
To change the cross-connect state from protection to provisioned, use the override option with the connect command. When one of the interfaces specified in the connect command is APS protected, only one of the interfaces is specified in the connect command, but both are automatically included in the cross-connect installed in the switch fabric.
This option is useful for migration scenarios, when moving the APS protection to different interfaces without taking a data hit.
Valid cross connections between modules are:
•
portgroup slot1/subcard1/port waveethernetphy slot2/subcard2•
portgroup slot1/subcard1/port waveethernetphy slot2/subcard2.subinterface
•
portgroup slot1/subcard1/port tengigethernetphy slot2/subcard2.subinterface
You cannot preconfigure a cross connection. The interfaces must exist on the shelf before configuring them.
The order of the interfaces in the command does not affect the cross connect configuration. For example, configuring a cross connect with the command connect portgroup 1/0/0 waveethernetphy 2/0.1 is equivalent to configuring a cross connect with connect waveethernetphy 2/0.1 portgroup 1/0/0.
Examples
The following example shows how to cross connect an ESCON aggregation card and a 10-Gbps ITU trunk card.
Switch# configure terminalSwitch(config)# connect portgroup 1/0/0 waveethernetphy 3/0.0 overrideRelated Commands
encapsulation
To configure the protocol encapsulation for the client signal on a transparent, twogigabitphy, gigabitphy, or multirate interface, use the encapsulation command. To disable the encapsulation for the client signal, use the no form of this command.
Transparent Interfaces
encapsulation {fastethernet | fddi | gigabitethernet | escon |
sysplex {clo | etr | isc {compatibility | peer [1g | 2g]}} |
ficon {1g | 2g} |
sonet {oc3 | oc12 | oc48} |
sdh {stm-1 | stm-4 | stm-16} |
fibrechannel {1g | 2g} [ofc {enable | disable}]}no encapsulation
Twogigabitphy Interfaces
encapsulation {fibrechannel {1g | 2g| auto} [ofc {enable | disable}] |
ficon {1g | 2g| auto} [ofc {enable | disable}] |
sysplex isc {compatibility | peer {1g | 2g}}}no encapsulation
Gigabitphy Interfaces
encapsulation {fibrechannel [ofc {enable | disable}] |
ficon [ofc {enable | disable}] |
gigabitethernet |
sysplex isc {compatibility | peer}}no encapsulation
Multirate Interfaces
encapsulation {t1 | e1 | dvb | sdi | its | escon |
fibrechannel |
ficon |
gigabitethernet {optical | copper} |
fastethernet {optical | copper} |
sdh stm-1 | sonet oc3}Syntax Description
fastethernet
Specifies Fast Ethernet encapsulation. The OFC1 safety protocol is disabled.
fddi
Specifies FDDI encapsulation. OFC is disabled.
gigabitethernet
Specifies Gigabit Ethernet encapsulation. OFC is disabled.
escon
Specifies ESCON encapsulation. OFC is disabled.
sysplex
Specifies Sysplex encapsulation.
Note
clo
Specifies CLO2 timing. OFC is disabled. Forward laser control is enabled on both the transparent and wave interfaces.
etr
Specifies ETR3 timing. OFC is disabled.
isc
Specifies ISC4 encapsulation.
compatibility
Specifies ISC links compatibility mode (ISC-1) with rate of 1.0625 Gbps. OFC is enabled on all interface types except multirate interfaces where OFC is not supported.
peer
Specifies ISC links peer mode (ISC-3). OFC is disabled.
1g
Specifies 1 Gbps for the protocol rate.
2g
Specifies 2 Gbps for the protocol rate.
auto
Enables automatic end-to-end speed negotiation on twogigabitphy interfaces encapsulated for FC or FICON traffic.
ficon
Specifies FICON encapsulation. OFC is disabled.
sonet
Specifies SONET encapsulation. OFC is disabled.
oc3
Specifies SONET rate of OC-3.
oc12
Specifies SONET rate of OC-12.
oc48
Specifies SONET rate of OC-48.
sdh
Specifies SDH encapsulation. OFC is disabled.
stm-1
Specifies SDH rate of STM-1.
stm-4
Specifies SDH rate of STM-4.
stm-16
Specifies SDH rate of STM-16.
fibrechannel
Specifies Fibre Channel encapsulation.
ofc {enable | disable}
Enables or disables OFC. The default OFC state is disabled. (Optional)
t1
Specifies T1 encapsulation.
e1
Specifies E1 encapsulation.
dvb
Specifies DVB-ASI5 encapsulation.
sdi
Specifies SDI6 encapsulation.
its
Specifies ITS7 encapsulation.
{optical | copper}
Specifies the type of SFP.
1 OFC = open fiber control
2 CLO = Control Link Oscillator
3 ETR = external time reference
4 ISC = InterSystem Channel
5 DVB-ASI = Digital Video Broadcasting Asynchronous Serial Interface
6 SDI = Serial Digital Interface
7 ITS = Integrated Trading System
Defaults
The default rate on twogigabitphy interfaces fibrechannel 1g.
Encapsulation disabled is on all other interfaces.
The default rate for Sysplex ISC peer mode on transparent interfaces is 2-Gbps.
See the "Syntax Description" section for the default OFC state.
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Transponder Line Card
Use this command to provide clocking for the client signal for specific protocols. The protocol encapsulation must be configured for the transparent interface to allow signal monitoring to be enabled with the monitor enable command. The following protocol encapsulation types are supported in 3R mode plus protocol monitoring:
•
•
•
•
•
•
•
•
•
•
•
•
The following protocol encapsulation types are supported in 3R mode without protocol monitoring:
•
•
•
•
To specify the signal clock rate without specifying a protocol, use the clock rate command.
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.
Note
Removing the encapsulation on an interface with the no encapsulation command does not turn off the laser. To turn off the transmit laser to the client equipment, use the shutdown command.
Gigabitphy Interfaces
Removing the encapsulation on an interface with the no encapsulation command does not turn off the laser. To turn off the transmit laser to the client equipment, use the shutdown command.
Twogigabitphy Interfaces
Removing the encapsulation on an interface with the no encapsulation command does not turn off the laser. To turn off the transmit laser to the client equipment, use the shutdown command.
Note
Multirate Interfaces
The 8-port multi-service muxponder does not support FICON bridge.
You must disable a multirate interface with the shutdown command before removing or changing the protocol encapsulation. You can then reenable the interface with the no shutdown command.
Note
Note
Note
Examples
The following example shows how to configure SONET encapsulation at a rate of OC-3 on a transparent interface.
Switch#configure terminalSwitch(config)#interface transparent 2/0/0Switch(config-if)#encapsulation sonet oc3Related Commands
Configures a clock rate on a transparent interface.
Enables signal monitoring for certain protocol encapsulations.
Displays interface information.
Disables an interface.
flow control
To adjust the flow of data and enable buffer credits for FC and FICON on 4-port 1-Gbps/2-Gbps FC aggregation cards and on 8-port FC/GE aggregation cards, use the flow control command. To revert to the default value, use the no form of this command.
flow control [asymmetric | symmetric]
no flow control
Syntax Description
asymmetric
Specifies asymmetric mode for twogigabitphy interfaces.
symmetric
Specifies symmetric mode for twogigabitphy interfaces.
Defaults
Disabled
When enabled, the default mode is symmetric on twogigabitphy interfaces.
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
Usage Guidelines
This command is only available on gigabitphy interfaces and twogigabitphy interfaces encapsulated for Fibre Channel or FICON traffic.
You can use symmetric mode in most configurations. However, use asymmetric mode if the following conditions occur when using symmetric mode:
1.
2.
3.
–
–
Examples
The following example shows how to enable flow control.
Switch(config)#configure terminalSwitch(config-if)#interface gigabitphy 3/0/0Switch(config-if)#encapsulation fibrechannelSwitch(config-if)#flow controlThe following example shows how to disable flow control.
Switch(config)#configure terminalSwitch(config-if)#interface gigabitphy 3/0/0Switch(config-if)#no flow controlRelated Commands
Configures the encapsulation of the client signal on the interface.
Displays interface information.
Configures the size of the transmit latency buffer.
laser control forward enable
To enable forward laser control, which automatically shuts down line card lasers when a Loss of Light failure occurs, use the laser control forward enable command. To disable this feature, use the no form of this command.
laser control forward enable
no laser control forward
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled on esconphy interfaces
Enabled on multirate interfaces when encapsulated for ESCON traffic
Disabled on all other interfaces
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Automatically shutting down the laser prevents the transmission of unreliable data. However, when the laser is shut down, fault isolation is more difficult.
Forward laser control is supported on transparent and wave interfaces on transponder line cards, esconphy interfaces on ESCON aggregation cards, twogigabitphy interfaces on 4-port 1-Gbps/2-Gbps FC aggregation cards, gigabitphy interfaces on 8-port FE/GE aggregation cards, and multirate interfaces on 8-port multi-service muxponders:
•
Use this command to enable forward laser control on both the transparent and wave interfaces of a transponder line card. If configured on a transparent interface, the client side laser of a transponder line card shuts down when the trunk side receiver detects a Loss of Light. If configured on the wave interface, the trunk side laser of the transponder line card shuts down when the client side receiver detects a Loss of Light.
Note
This feature is convenient for configurations, such as Sysplex, where signal protection is performed in the client hardware and quick laser shutdown causes quick path switchover.
Caution
•
When forward laser control is enabled on an esconphy interface and a Loss of Light is detected on the port, the transmitter laser on the corresponding port on the remote node is turned off, regardless of the forward laser control configuration on the remote esconphy interface.
•
When forward laser control is enabled on a twogigabitphy interface and a Loss of Light is detected on the port, the transmitter laser on the corresponding port on the remote node is turned off only if forward laser control is configured on the remote twogigabitphy interface.
•
When forward laser control is enabled on a twogigabitphy interface and a Loss of Light is detected on the port, the transmitter laser on the corresponding port on the remote node is turned off only if forward laser control is configured on the remote twogigabitphy interface.
•
When forward laser control is enabled on a multirate interface and a Loss of Light, Loss of Sync, or Loss of Lock is detected on the port, the transmitter laser on the corresponding port on the remote node is turned off only if forward laser control is configured on the remote multirate interface.
Note
Examples
The following example shows how to enable forward laser control on a transparent interface.
Switch# configure terminalSwitch(config)# interface transparent 3/0/0Switch(config-if)# laser control forward enableThe following example shows how to enable forward laser control on a transponder line card wave interface.
Switch# configure terminalSwitch(config)# interface wave 2/0Switch(config-if)# laser control forward enableRelated Commands
laser control safety enable
To enable laser safety control on a wave, waveethernetphy, wavesonetphy, or tengigethernetphy interface, use the laser control safety enable command. To disable laser safety control, use the no form of this command.
laser control safety enable
no laser control safety
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to automatically shut down the lasers transmitting to the trunk fiber when a Loss of Light failure occurs, such as a trunk fiber cut. Enable laser safety control on all wave interfaces in the shelf, including the OSC wave interface.
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 durations timers compliant with the ALS (automatic laser shutdown) standard (ITU-T G.664).
Caution
Caution
Examples
The following example shows how to enable laser safety control on a wave interface.
Switch#configure terminalSwitch(config)#interface wave 2/0Switch(config-if)#laser control safety enableRelated Commands
laser frequency
To select the desired channel frequency on a transparent transponder line card, 10-Gbps ITU trunk card, 10-Gbps ITU tunable trunk card, 2.5-Gbps ITU trunk card, or 8-port multi service muxponders, use the laser frequency command.
To revert to the default value, use the no form of the command.
laser frequency number
no laser frequency
Syntax Description
number
One of the two channel frequencies supported by the transponder line card, or one of the four channel frequencies supported by a 10-Gbps ITU trunk card.
Defaults
The lower frequency for the transponder laser
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
The transponder line card can be tuned to support one of two channel frequencies and the 10-Gbps ITU tunable trunk card can be tuned to support one of four channel frequencies.
The change from one frequency to another takes about 10 seconds. Do not expect traffic to transit the system until the frequency selection completes. Also, successive laser frequency commands are ignored until after the new channel frequency stabilizes.
Note
Examples
The following example shows how to select the channel frequency on a transponder line card wave interface:
Switch(config)# interface wave 9/0Switch(config-if)# laser frequency 194100The following example shows how to select the channel frequency on a 2.5-Gbps ITU trunk card and 10-Gbps ITU tunable trunk card waveethernetphy interface:
Switch(config)# interface waveethernetphy 9/0Switch(config-if)# laser frequency 194100Related Commands
laser shutdown
To turn off the laser on a module supporting the in-band message channel or DCC, use the laser shutdown command. To turn the laser on, use the no form of this command.
laser shutdown
no laser shutdown
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to explicitly shut down the laser. The interface shutdown command disables data traffic; however the control traffic carried over in-band message channel or DCC continues to flow. Use this command to turn off the laser and stop all traffic.
Note
Note
Note
Examples
The following example shows how to turn off the laser on a waveethernetphy interface.
Switch(config)# interface waveethernetphy 4/0Switch(config-if)# laser shutdownRelated Commands
loopback
To configure a signal loopback on an interface, use the loopback command. To disable interface loopback, use the no form of this command.
loopback [facility | terminal]
no loopback [facility | terminal]
Syntax Description
Defaults
Disabled
When neither facility or terminal is specified in the command, the default is facility.
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to configure facility loopbacks on transparent, wave, esconphy, or multirate interfaces, and facility and terminal loopbacks on waveethernetphy, wavesonetphy, or tengigethernetphy interfaces. On a transponder line card, you can configure a loopback on either the wave interface or the transparent interface, but not both simultaneously.
A configured loopback differs from an external loopback where you simply run a cable from the output of a given interface to its input. Using the loopback command, you can set loopbacks without the need to change the cabling. This is useful for remote testing, configuration, and troubleshooting.
Caution
Note
The facility and terminal options are available only on waveethernetphy and tengigethernetphy interfaces. If neither the facility or terminal keywords are used, the default is a terminal loopback.
Examples
The following example shows how to enable loopback on a transparent interface.
Switch#configure terminalSwitch(config)#interface transparent 2/0/0Switch(config-if)#loopbackThe following example shows how to enable loopback on a wave interface.
Switch#configure terminalSwitch(config)#interface wave 10/0Switch(config-if)#loopbackRelated Commands
monitor enable
To monitor signal quality and protocol error statistics in the transponder line card, use the monitor enable command. To disable monitoring, use the no form of this command.
monitor enable
no monitor
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to collect error statistics on signal quality in the transponder line card. The following protocols can be monitored:
•
•
•
•
•
•
•
•
•
•
•
•
Note
When monitoring is enabled on the transparent interface, it is automatically enabled on the corresponding wave interface.
For GE, FC, and FICON traffic, the Cisco ONS 15530 monitors the following conditions:
•
•
•
•
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:
•
•
•
•
For SONET performance, the system monitors the B1 byte, which is used to compute the four SONET section layer performance monitor parameters:
•
•
•
•
For ISC link compatibility and peer mode traffic, the system monitors the following conditions:
•
•
•
Note
Monitoring signal error statistics is useful for isolating system and network faults.
Examples
The following example shows how to monitor error counters on a transparent interface.
Switch#configure terminalSwitch(config)#interface transparent 2/0/0Switch(config-if)#monitor enableRelated Commands
Configures the encapsulation of the client signal on the interface.
Displays interface information.
negotiation auto
To enable autonegotiation for Gigabit Ethernet on 8-port FC/GE aggregation cards, use the negotiation auto command. To revert to the default value, use the no form of this command.
negotiation auto
no negotiation auto
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
12.2(18)SV
This command was introduced.
12.2(22)S
Usage Guidelines
This command is available on gigabitphy interfaces encapsulated for Gigabit Ethernet traffic and on multirate interfaces encapsulate for copper Fast Ethernet or copper Gigabit Ethernet.
Examples
The following example shows how to enable autonegotiation on a gigabitphy interface.
Switch(config)#configure terminalSwitch(config-if)#interface gigabitphy 3/0/0Switch(config-if)#encapsulation gigabitethernetSwitch(config-if)#negotiation autoThe following example shows how to disable autonegotiation on a multirate interface.
Switch(config)#configure terminalSwitch(config-if)#interface multirate 8/0/3Switch(config-if)#encapsulation gigabitethernet copperSwitch(config-if)#no negotiation autoRelated Commands
Configures the encapsulation of the client signal on the interface.
Displays interface information.
optical attenuation automatic desired-power
To configure automatic attenuation on a voain interface, use the optical attenuation automatic desired-power command. To revert to manual attenuation at the previously configured automatic desired power value, use the no form of the command.
optical attenuation automatic desired-power value
no optical attenuation automatic desired-power
Syntax Description
Defaults
None
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to automatically set the optical attenuation on a WB-VOA module interface. Once you set a desired signal power and the system checks every second until the signal power comes into attenuable range. Then the system sets the attenuation so that the signal transmits at the desired power value. The system waits 60 seconds before checking the signal power again and adjusting the attenuation if necessary. The system automatically adjusts the attenuation only if it is at least 0.5 dBm out of range.
To determine the desired power setting, use the show interfaces command with the attenuation desired-power keywords.
Note
Examples
The following example shows how to set the optical attenuation on a WB-VOA module interface.
Switch# configure terminalSwitch(config)# interface voain 7/0/0Switch(config-if)# optical attenuation automatic desired-power 100Related Commands
Manually sets the attenuation value for the input interfaces on VOA modules.
Displays interface information.
optical attenuation manual
To manually set the attenuation level on a VOA module interface, use the optical attenuation manual command. To revert to the default value, use the no form of the command.
optical attenuation manual value
no optical attenuation manual
Syntax Description
Defaults
For single and double WB-VOA (wide-band variable optical attenuator) modules the default is 1.7 dB.
For single band PB-OE (per-band optical equalizer) modules the default is 3.4 dB.
For dual band PB-OE modules the default is 3.7 dB.
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to manually set the optical attenuation on a VOA module interface.
To determine the power setting, use the show interfaces command with the attenuation desired-power keywords.
Note
Examples
The following example shows how to set the optical attenuation on a WB-VOA module interface.
Switch# configure terminalSwitch(config)# interface voain 7/0/0Switch(config-if)# optical attenuation manual 100The following example shows how to set the optical attenuation on a PB-OE module interface.
Switch# configure terminalSwitch(config)# interface voafilterin 7/0/0.1Switch(config-subif)# optical attenuation manual 100Related Commands
Configures automatic attenuation on a WB-VOA module interface.
Displays interface information.
optical threshold power receive
To set the optical threshold power for alarms on a transponder line card, VOA module, 2.5-Gbps ITU trunk card, 10-Gbps ITU tunable and non tunable trunk card, or 8-port multi-service muxponder use the optical threshold power receive command. To revert to the default values, use the no form of the command.
optical threshold power receive [after-attenuation] {low | high} {alarm | warning} value [severity {critical | major | minor | not alarmed | not reported}]
no optical threshold power receive [after-attenuation] {low | high} {alarm | warning}
Syntax Description
Defaults
Alarm severity: major
Warning severity: not alarmed
Command Modes
Interface configuration for WB-VOA modules, transponder line cards, 2.5-Gbps ITU trunk cards, and 10-Gbps ITU tunable and non tunable trunk cards
Subinterface configuration for PB-OE modules
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to set the optical power thresholds for alarms and warning on VOA module interfaces, transponder line card interfaces, 2.5-Gbps ITU trunk card interfaces, 10-Gbps ITU tunable and non tunable trunk card interfaces, or 8-port multi-service muxponder interfaces.
The default value for high alarm threshold corresponds to the receiver saturation level for the transponder line card.
The default value for low alarm threshold corresponds to the Loss Of Light condition. Exceeding the low alarm threshold on the active wavepatch interface causes a protection switchover to the standby wavepatch interface, provided that the standby interface is up and operating normally prior to the protection switchover.
The default values apply to most network configurations. However, when optical amplifiers are used in the network in the receive direction as preamplifiers, the low alarm threshold value should be reconfigured, because the amplified noise level might be higher than the sensitivity of the receiver and the protection switchover might not be triggered. In such cases, we recommend setting the low alarm threshold either to 10 dB below the power level measured at the interface when a signal exists or to -28 dB for transponder line cards, 8-port multi-service muxponders, and 2.5-Gbps ITU trunk cards, or to -22 dB for 10-Gbps ITU tunable and non tunable trunk cards, whichever value is higher.
Note
Examples
The following example shows how to set the optical power low alarm threshold on a PB-OE module.
Switch(config)# interface voafilterin 9/0/0.1Switch(config-subif)# optical threshold power receive after-attenuation low alarm -210The following example shows how to set the optical power high alarm threshold on a WB-VOA module.
Switch(config)# interface voain 8/0/0Switch(config-if)# optical threshold power receive after-attenuation high alarm -200The following example shows how to set the optical power low warning threshold on a wavepatch interface.
Switch(config)# interface wavepatch 4/0/0Switch(config-if)# optical threshold power receive low warning -200Related Commands
over-subscription
To oversubscribe 4-port 1-Gbps/2-Gbps FC aggregation cards, use the over-subscription command. To disable oversubscription, use the no form of this command.
over-subscription
no over-subscription
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled.
Command Modes
Interface configuration.
Command History
This table includes the following release-specific history entries:
•
Usage Guidelines
Oversubscription is supported only in the FC/FICON mode and not in the ISC mode. To maximize throughput, Cisco recommends that you configure oversubscription along with flow control.
You can oversubscribe a 4-port 1-Gbps/2-Gbps FC aggregation card only if the following conditions are met:
–
–
–
–
Examples
The following example shows how to enable oversubscription on a 4-port 1-Gbps/2-Gbps FC aggregation card:
Switch(config)#configure terminalSwitch(config-if)#interface portgroup 3/0/0Switch(config-if)#over-subscriptionSwitch(config-if)# exitThe following example shows how to disable oversubscription on a 4-port 1-Gbps/2-Gbps FC aggregation card:
Switch(config)#configure terminalSwitch(config-if)#interface portgroup 3/0/0Switch(config-if)#no over-subscriptionSwitch(config-if)# exitRelated Commands
Configures the subrate for the twogigabitphy interfaces that are part of an oversubscribed portgroup or a superportgroup.
Displays interface information.
patch
To configure the patch connections within a shelf, use the patch command. To remove the patch connection configuration, use the no form of the command.
patch interface1 [transmit | receive] interface2
no patch interface1 [transmit | receive] interface2
Syntax Description
interface1
Specifies the first patched interface. See the " Usage Guidelines" section for valid interface types.
transmit
Indicates that interface1 is patched to interface2 in the transmit direction.
receive
Indicates that ainterface1 is patched to interface2 in the receive direction.
interface2
Specifies the second patched interface. See the " Usage Guidelines" section for valid interface types.
Defaults
Both directions
Command Modes
Global configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to describe the patch connections between the OADM modules.
Valid patch connections between modules are:
•
thru slot1/subcard1 thru slot/subcard2
•
wave slot/subcard oscfilter slot/subcard
•
wave slot/subcard voain slot/subcard/port
•
oscfilter slot/subcard voaout slot/subcard/port
•
wavepatch slot/subcard/port filter slot/subcard/port
•
wavepatch slot/subcard/port wdmrelay slot/subcard/port
•
wdm slot/subcard wdmrelay slot/subcard/port
•
wdm slot/subcard voain slot/subcard/port
•
wdm slot/subcard voaout slot/subcard/port
•
wdm slot/subcard voafilterin slot/subcard/port
•
wdm slot/subcard voafilterout slot/subcard/port
•
voabypassout slot/subcard/port voain slot/subcard/port
•
voaout slot/subcard/port voabypassin slot/subcard/port
•
voabypassout slot/subcard/port voafilterin slot/subcard/port
•
voafilterout slot/subcard/port voabypassin slot/subcard/port
You cannot preconfigure a patch connection. The interfaces must exist on the shelf before configuring them.
The order of the interfaces in the command does not affect the patch connect configuration. For example, configuring patch wdm 0/1 thru 0/0 is equivalent to configuring patch thru 0/0 wdm 0/1.
In case of an optical interface where the transmitted and received signals travel on two different strands of fiber, it is possible that each fiber is patched to a different interface. The direction keywords receive and transmit indicate whether interface1 is patched to the interface2 in the receive direction or the transmit direction. The absence of the keyword indicates that interface1 is patched to interface2 in both directions.
When one interface in a patch connection is physically removed from the shelf, the patch connection configuration persists but does not appear in the show running-config output. A subsequent patch command that includes the remaining interface overwrites the previous patch connection configuration.
Note
Examples
The following example shows how to describe the patch connection between two OADM modules in the same slot.
Switch#configure terminalSwitch(config)#patch wdm 0/0 wave 1/1The following example shows how to describe the patch connection in the transmit direction between an OADM module and a PB-OE module.
Switch#configure terminalSwitch(config)#patch wdm 1/0 transmit voafilterin 1/1/0Related Commands
portgroup
To map a twogigabitphy interface to a portgroup interface, use the portgroup command. To remove the interface mapping configuration, use the no form of the command.
portgroup interface-number
no portgroup
To map portgroups to a superportgroup on a 4-port 1-Gbps/2-Gbps FC aggregation card, use the portgroup command. To remove the interface mapping configuration, use the no form of the command.
portgroup interface-number {identifier trunk flow identifier}
no portgroup interface-number
Syntax Description
Defaults
None
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
12.2(29)SV
Added support for oversubscription configurations.
12.2(23)SV
This command was introduced.
Usage Guidelines
If the portgroup is not oversubscribed, you can map two twogigabitphy interfaces carrying 1-Gbps traffic to a single portgroup interface. If the twogigabitphy interface carries 2-Gbps traffic, it is the only interface you can map to the portgroup interface. If oversubscription is enabled on the portgroup, any number of twogigabitphy interfaces can be mapped to the portgroup. The total subrates of all the clients in a portgroup must not exceed the portgroup bandwidth (250 MBps).
When a portgroup is associated to the superportgroup, oversubscription is automatically enabled on that portgroup. If you disassociate a portgroup from the superportgroup, oversubscription is automatically disabled on that portgroup. Moreover, while superportgroup is configured, oversubscription cannot be enabled on any other portgroup (in the same 4-port 1-Gbps/2-Gbps FC aggregation card) that is not part of the superportgroup. A portgroup that is associated to a superportgroup cannot be connected to any twogigabitphy interfaces.
In a superportgroup, client-to-client mappings are fixed. For instance, port-0 of the 4-port 1-Gbps/2-Gbps FC aggregation card at one end will communicate only with port-0 of the 4-port 1-Gbps/2-Gbps FC aggregation card at the other end.
Examples
The following example shows how to configure the mapping between a twogigabitphy interface and a portgroup interface.
Switch(config)# interface twogigabitphy 4/0/0Switch(config-if)# portgroup 2The following example shows how to configure the mapping between a portgroup interface and the superportgroup interface.
Switch# configure terminalSwitch(config)# interface superportgroup 7/0/0Switch(config-if)# portgroup 0 identifier 16Related Commands
show cdl defect-indication
To display the defect indication information on in-band message channel capable interfaces use the show cdl defect-indication command.
show cdl defect-indication [interface interface | detail]
Syntax Description
detail
Displays the defect indication information for in-band message channel capable interfaces.
interface interface
Displays the defect indication information for a specific interface.
Defaults
Displays a defect indication summary
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command is used to display the defect indication information on in-band message channel capable interfaces.
Examples
The following example shows how to display in-band message channel defect indication information. (See Table 3-2 for field descriptions.)
Switch# show cdl defect-indicationCDL Defect-Indication Status SummaryInterface Interface DI Defect-Indication Defect-IndicationName Status Status Receive Transmit------------ ---------- ------ ----------------------- -----------------------WaveE3/0 up up BDI-H NoneWaveE4/0 up up None NoneWaveE9/0 up up None NoneWaveE10/0 up up None None
The following example shows how to display the defect indication information for in-band message channel capable interfaces.
Switch# show cdl defect-indication detailInterface WaveEthernetPhy3/0Operational Status : upAdministrative Status : upCDL Status : EnabledDefect Indication state : upConfigured Node Behavior : NoneCurrent Node Behavior : Path TerminatingDefect Indication Receive : BDI-HDefect Indication Transmit: NoneRelated Commands
show cdl flow
To display in-band message channel flow identifier and defect indication information on a per-flow basis, use the show cdl flow command.
show cdl flow [interface interface]
Syntax Description
interface interface
Displays flow identifier and defect indication information for a specific interface.
Defaults
Shows all flow identifiers and defect indications on the system
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command is used to display the flow identifier and defect indication information on in-band message channel capable interfaces.
Examples
The following example shows how to display in-band message channel flow identifier information. (See Table 3-3 for field descriptions.)
Switch# show cdl flowDI = Defect IndicationInterface Flow DI Received DI TransmittedIdentifier from CDL network to CDL network------------ ---------- ----------------------- -----------------------Esco9/0/0 50Esco9/0/1 255Esco9/0/2 255Esco9/0/3 255Esco9/0/4 255Esco9/0/5 255Esco9/0/6 255Esco9/0/7 255Esco9/0/8 255Esco9/0/9 255Esco10/0/0 255Esco10/0/1 255Esco10/0/2 255Esco10/0/3 255Esco10/0/4 255Esco10/0/5 255Esco10/0/6 255Esco10/0/7 255Esco10/0/8 255Esco10/0/9 255
Related Commands
show cdl flow defect-indication
To display in-band message channel defect indication information on a per-flow basis, use the show cdl flow defect-indication command.
show cdl flow defect-indication [interface interface]
Syntax Description
Defaults
Shows defect indications for all flows on the system
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command is used to display the defect indication information on in-band message channel capable interfaces.
Examples
The following example shows how to display in-band message channel flow identifier information. (See Table 3-4 for field descriptions.)
Switch# show cdl flow defect-indicationDI = Defect IndicationInterface DI Received DI Transmittedfrom CDL network to CDL network------------ ----------------------- -----------------------Esco10/0/0Esco10/0/1Esco10/0/2Esco10/0/3Esco10/0/4Esco10/0/5Esco10/0/6Esco10/0/7Esco10/0/8Esco10/0/9
Related Commands
show cdl flow identifier
To display in-band message channel flow identifier information, use the show cdl flow identifier command.
show cdl flow identifier [interface interface]
Syntax Description
Defaults
Shows all flow identifiers on the system
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command is used to display the flow identifier information for in-band message channel capable interfaces.
Examples
The following example shows how to display in-band message channel flow identifier information. (See Table 3-5 for field descriptions.)
Switch# show cdl flow identifierInterface FlowIdentifier------------ ----------Esco8/0/0 80Esco8/0/1 81Esco8/0/2 82Esco8/0/3 83Esco8/0/4 84Esco8/0/5 85Esco8/0/6 86Esco8/0/7 87Esco8/0/8 88Esco8/0/9 89Esco10/0/0 100Esco10/0/1 255Esco10/0/2 255Esco10/0/3 255Esco10/0/4 255Esco10/0/5 255Esco10/0/6 255Esco10/0/7 255Esco10/0/8 255Esco10/0/9 255
Related Commands
show connect
To display the connection relationships between the interfaces in the shelf, use the show connect command.
show connect [edges | intermediate [sort-channel | interface interface]]
Syntax Description
Defaults
Summary of configured cross connections
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command shows the relationships between the interfaces in the shelf. Use this command to trace a single channel from the client side interface to the trunk side OADM interface.
Examples
The following example shows how to display configured cross connection information. (See Table 3-6 for field descriptions.)
Switch# show connectIndex Client Intf Trunk Intf Kind C2TStatus T2CliStatus----- --------------- --------------- ----------- ---------- ---------15 Port3/0/0 WaveE8/0.1 Provisioned Up Up15 Port3/0/0 WaveE10/0.1 Protection Up Dormant
The following example shows how to display edge connection information. (See Table 3-7 for field descriptions.)
Switch# show connect edgesclient/wave wdm channel---------- --- -----Tran4/0/0 0/1 4
The following example shows how to display intermediate connection information. (See Table 3-8 for field descriptions.)
Switch# show connect intermediateclient/ wave wave wdmclient/ wave wave wdmwave client patch filter trk channel------------ ------------ ------- ------ ----- -------Esco3/0/0 WaveE8/0 8/0/0*8/0/1Esco3/0/1 WaveE8/0 8/0/0*8/0/1Esco3/0/2 WaveE8/0 8/0/0*8/0/1Esco3/0/3 WaveE8/0 8/0/0*8/0/1Esco3/0/4 WaveE8/0 8/0/0*8/0/1Esco3/0/5 WaveE8/0 8/0/0*8/0/1Esco3/0/6 WaveE8/0 8/0/0*8/0/1Esco3/0/7 WaveE8/0 8/0/0*8/0/1Esco3/0/8 WaveE8/0 8/0/0*8/0/1Esco3/0/9 WaveE8/0 8/0/0*8/0/1client/ wave wave wdmwave client patch filter trk channel------------ ------------ ------- ------ ----- -------Tran4/0/0 Wave4/0 4/0/0* 0/1/3 0/1 44/0/1Tran7/0/0 Wave7/0 7/0/07/0/1* 0/0/2 0/0 3
The following example shows how to display interface connection information. (See Table 3-9 for field descriptions.)
Switch# show connect interface transparent 2/0/0client/ wave wave wdmwave client patch filter trk channel------------ ------------ ------- ------ ----- -------Esco3/0/0 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/1 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/2 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/3 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/4 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/5 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/6 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/7 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/8 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2Esco3/0/9 WaveE8/0.1 8/0/0* 0/0/1 0/0 28/0/1 0/1/1 0/1 2client/ wave wave wdmwave client patch filter trk channel------------ ------------ ------- ------ ----- -------Tran4/0/0 Wave4/0 4/0/0* 0/1/3 0/1 44/0/1Tran7/0/0 Wave7/0 7/0/07/0/1* 0/0/2 0/0 3
Related Commands
show controllers
To display hardware register information for an interface, use the show controllers command.
show controllers [type slot[/subcard[/port]]]
Syntax Description
type
Specifies one of the interface types listed in Table 3-10.
slot
Specifies a chassis slot.
subcard
Specifies a subcard position in a motherboard.
port
Specifies a port.
Defaults
Displays controller information for all interfaces on the system.
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
The show controllers command displays the contents of hardware registers for the interfaces. This information is useful for troubleshooting system problems.
Table 3-10 shows the interface types for the show controller command.
Examples
The following example shows how to display hardware register information about a transparent interface. (See Table 3-11 for field descriptions.)
Switch# show controllers transparent 3/0/0Controller info for Transparent interface Transparent3/0/0LRC start addr = 0x200000hardware port = 1RCI0 monitor................:enabledport 1 intr SRC/CPU.........:enabledCPU0 MSB MAC................:0x0CPU0 LSB MAC................:0x0CPU1 MSB MAC................:0x0CPU1 LSB MAC................:0x0port error register.........:0x10000port ctrl msg intf mask.....:0x0port APS port fail mask.....:0x0HuJr start addr = 0x240000Optics control and status:LSC indication..............:oktrunk laser failure alarm...:clearLSC indication enable.......:disabledtrunk laser alarm enable....:disabledline transceiver mode.......:non pluggableloss of light...............:yestrunk laser deviation alarm.:clearLSC.........................:disabledquick shutdown (FLC)........:disabledwavelength select...........:n-1 [lo wlen]CDR control and status:loss of lock................:yesloss of lock enable.........:disabledSerDes control and status:diags loop back.............:disabledline loop back..............:disabledGE handler control and status:loss of sync................:noloss of sync enable.........:disabledFC/ESCON handler control and status:loss of sync................:noloss of sync enable.........:disabledSONET handler control and status:loss of frame...............:yesseverely errored frame......:yesLOF enable..................:disabledSEF enable..................:disabled
Table 3-11 show controllers Command Field Descriptions for Transparent Interfaces
Optics control and status:
Shows control and status information for the optical components in the interface.
LSC indication
Shows laser safety control status (valid only on wave interfaces).
trunk laser failure alarm
Shows the status of the trunk laser alarm. The values are:
•
•
LSC indication enable
Indicates whether laser safety control has been enabled (valid only on wave interfaces).
trunk laser alarm enable
Shows the status of the trunk laser alarm. If enabled, the system will signal when laser failure occurs.
loss of light
Indicate whether there is a Loss of Light condition.
trunk laser deviation alarm
Shows the status of the wavelength deviation alarm. If enabled, the system will signal when there is a deviation in the functioning of the laser.
LSC
Indicates whether laser safety control is enabled from the CLI (valid only on wave interfaces).
quick shutdown (FLC)
Indicates whether forward laser control is enabled on the interface (valid only on wave interfaces).
wavelength select
Indicates whether a transponder line card is transmitting the lower wavelength (lo wlen) or the higher wavelength (hi wlen).
CDR control and status:
Shows the CDR (clock and data recovery) control and status information.
loss of lock
Indicated whether there is a Loss of Lock condition.
loss of lock enable
Indicates whether Loss of Lock monitoring is enabled on the interface via the monitor enable command.
SerDes control and status:
Shows the SerDes (serializer/deserializer) information.
GE handler control and status:
Shows Gigabit Ethernet control and status information.
loss of sync
Indicates whether there is a Loss of Synchronization for the signal. This field is only valid if protocol encapsulation is Gigabit Ethernet, and monitoring is enabled.
loss of sync enable
Indicates whether Loss of Synchronization monitoring is enabled via the monitor enable command.
FC/ESCON handler control and status:
Shows Fibre Channel and ESCON control and status information.
loss of sync
Indicates whether there is a Loss of Synchronization for the signal. This field is only valid if protocol encapsulation is Fibre Channel or ESCON, and monitoring is enabled.
loss of sync enable
Indicates whether Loss of Synchronization monitoring is enabled via the monitor enable command.
SONET handler control and status:
Shows SONET control and status information.
loss of frame
Indicates whether there is a Loss of Frame for the signal. This field is only valid if protocol encapsulation is SONET, and monitoring is enabled.
severely errored frame
Indicates whether there is a severely errored frame in the signal. This field is only valid if protocol encapsulation is SONET, and monitoring is enabled.
LOF enable
Indicates whether Loss of Frame monitoring is enabled via the monitor enable command.
SEF enable
Indicates whether severely errored frame monitoring is enabled via the monitor enable command.
The following example shows how to display hardware register information about a transponder line card wave interface. (See Table 3-11 for field descriptions.)
Switch# show controllers wave 3/1Controller info for Wave interface Wave3/1LRC start addr = 0x200000hardware port = 2RCI1 monitor................:enabledport 2 intr SRC/CPU.........:enabledCPU0 MSB MAC................:0x0CPU0 LSB MAC................:0x0CPU1 MSB MAC................:0x0CPU1 LSB MAC................:0x0port error register.........:0x10000port ctrl msg intf mask.....:0xF00FC00Aport APS port fail mask.....:0x0HuJr start addr = 0x250000Optics control and status:auto fail-over indication...:normaloptical switch alarm........:clearline laser degrade alarm....:clearoptical switch position.....:Mux 1loss of light...............:noBLC and LAS.................:disabledLSC.........................:disabledquick shutdown (FLC)........:disabledCDR control and status:loss of lock................:yesloss of lock enable.........:enabledSerDes control and status:diags loop back.............:disabledline loop back..............:disabledGE handler control and status:loss of sync................:noloss of sync enable.........:disabledFC/ESCON handler control and status:loss of sync................:noloss of sync enable.........:disabledSONET handler control and status:loss of frame...............:yesseverely errored frame......:yesLOF enable..................:disabledSEF enable..................:disabledThe following example shows how to display hardware register information about an OSC wave interface. (See Table 3-11 for field descriptions.)
Switch# show controllers wave 3/0Controller info for OSC wave interface Wave3/0LRC start addr = 0x900000hardware port = 0RCI0 monitor................:enabledport 0 intr SRC/CPU.........:enabledCPU0 MSB MAC................:0x0CPU0 LSB MAC................:0x1060000CPU1 MSB MAC................:0x0CPU1 LSB MAC................:0x1070000port error register.........:0x8002port ctrl msg intf mask.....:0x0port APS port fail mask.....:0x0HuJr start addr = 0x940000CDL add/drop control and status:FIFO overflow indication....:clearHEC error threshold exceeded:indicateFIFO overflow enable........:disabledHEC error threshold enable..:disabledCDL alarm status............:true alarmCDL add enable..............:enabledCDL drop enable.............:enabledOptics control and status:LSC indication..............:oktrunk laser failure alarm...:indicatedLSC indication enable.......:disabledtrunk laser alarm enable....:disabledloss of light...............:yeswavelength deviation alarm..:clearLSC.........................:disabledwavelength select...........:n [hi wlen]CDR control and status:loss of lock................:yesloss of lock enable.........:disabledSerDes control and status:diags loop back.............:disablednetwork loop back...........:disabledGE handler control and status:loss of sync................:yesloss of sync enable.........:disabledRelated Commands
show interfaces
To display interface information, use the show interfaces command.
show interfaces [type slot[/subcard[/port]]] [attenuation desired-power value]
Syntax Description
type
Specifies one of the interface types listed in Table 3-12.
slot
Specifies a chassis slot.
subcard
Specifies a subcard position in a motherboard.
port
Specifies a port.
attenuation desired-power value
Specifies the desired attenuation power for voain interfaces.
Defaults
Displays information for all interfaces on the system.
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Table 3-12 shows the interface types for the show interfaces command.
Examples
The following example shows how to display the configuration of a waveethernetphy interface:
Switch# show interfaces waveethernetphy 10/0WaveEthernetPhy10/0 is down, line protocol is downChannel:30 Frequency:195.7 Thz Wavelength:1531.90 nmActive Wavepatch :Wavepatch10/0/1Splitter Protected :NoSignal quality :Loss of lockReceive power level :-35.0 dBmLaser Bias Current :91 mALaser Temperature :31.0 degree CLaser shut down :NoOsc physical port :NoWavelength used for inband management:NoLoopback not setConfigured threshold Group:NoneCDL HEC error count:0Number of times SF threshold exceeded:0Number of times SD threshold exceeded:0CRC error count:0Number of times SF threshold exceeded:0Number of times SD threshold exceeded:0Code violation and running disparity error count( 64b66b cvrd):0Number of times SF threshold exceeded:0Number of times SD threshold exceeded:0Defect Indication Status :upConfigured Node Behavior :NoneCurrent Node Behavior :Path TerminatingDefect Indication Receive : NoneDefect Indication Transmit :BDI-HTotal Tx Frames Sent to N/W: 0Tx Gen CDL Idle Frame: 1843017892Rx Frames rcvd from N/W: 0Rx CRC Errors: 0Rx HEC Errors: 0Rx XGMII Errors: 0Rx IPG drpd pkts: 0Rx Idle Packets : 0Rx Oversize Frames : 0Rx Undersize Frames : 0Rx SII mismatch drpd data Frames : 0Rx SII mismatch drpd idle Frames : 0Last clearing of "show interface" counters neverHardware is data_enabled_portThe following example shows how to display transparent interface information. (See Table 3-13 for field descriptions.)
Switch# show interfaces transparent 3/0/0Transparent3/0/0 is administratively up, line protocol is upSignal quality: Loss of lockEncapsulation: Sonet Rate: oc3Signal monitoring: onForward laser control: OffConfigured threshold Group: NoneThreshold monitored for: BIP1 errorSet threshold SF:10e-5 SD:10e-7Section code violation error count(bip1): 61286Number of errored seconds(es): 2Number of severely errored seconds(ses): 2Number of severely errored framing seconds(sefs): 273Number of times SEF alarm raised: 0Number of times SF threshold exceeded: 0Number of times SD threshold exceeded: 2Loopback not setLast clearing of "show interface" counters neverHardware is transparent
The following example shows how to display information on a wavepatch interface. (See Table 3-14 for field descriptions.)
Switch# show interfaces wavepatch 1/0/0Wavepatch1/0/0 is down, line protocol is downReceiver power level: < -23.00 dBmOptical threshold monitored for : Receive Power (in dBm)Threshold exceeded for : Low Warning and Low AlarmLow alarm value = -22.0 dBm (default)Low Alarm Severity = majorLow warning value = -20.0 dBm (default)Low Warning Severity = not alarmedHigh alarm value = -6.0 dBm (default)High Alarm Severity = majorHigh warning value = -8.0 dBm (default)High Warning Severity = not alarmedHardware is passive_portThe following example shows how to display wave interface information. (See Table 3-14 for field descriptions.)
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: -37.30 dBmLaser safety control: OffForward laser control: OffOsc physical port: NoWavelength used for inband management: NoConfigured threshold Group: NoneSection code violation error count(bip1): 0Number of errored seconds(es): 29Number of severely errored seconds(ses): 29Number of severely errored framing seconds(sefs): 0Number of times SEF alarm raised: 0Number of times SF threshold exceeded: 0Number of times SD threshold exceeded: 0Loopback not setLast clearing of "show interface" counters 4d03hHardware is data_only_port
The following example shows how to display OSC wave interface information. (See Table 3-14 for field descriptions.)
Switch# show interfaces wave 2/0Wave2/0 is up, line protocol is upChannel: 0 Frequency: 191.9 Thz Wavelength: 1562.23 nmLaser safety control: OffOsc physical port: YesWavelength used for inband management: NoConfigured threshold Group: NoneLast clearing of "show interface" counters neverHardware is OSC_phy_portInternet address is 1.0.0.3/16MTU 1492 bytes, BW 10000000 Kbit, DLY 0 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation SNAP, loopback not setLast input 00:00:00, output never, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 05 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort14719 packets output, 971930 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outThe following example shows how to display wdm interface information. (See Table 3-15 for field descriptions.)
Switch# show interfaces wdm 0/0Wdm0/0 is up, line protocol is upWdm Hw capability: N/ANum of Wavelengths Add/Dropped: 5List of Wavelengths: 0, 25, 26, 27, 28Hardware is wavelength_add_drop
The following example shows how to display wdm interface information. (See Table 3-16 for field descriptions.)
Switch# show interfaces voain 1/0/0 attenuation desired-power 0Current Output Power: 10.0dBmDesired Output Power: 0.0dBmMinimum settable Attenuation: 3.4dBMaximum settable Attenuation: 30.0dBCurrent set Attenuation: 3.4dB (default)Attenuation needed to achieve Desired Output Power:13.4dB
Related Commands
show optical filter
To display information about the channels supported by the OADM modules, use the show optical filter command.
show optical filter [detail]
Syntax Description
detail
Shows optical patch connections between the OADM modules in addition to the channels supported. This information displays only if the patch connection has been configured with the patch command.
Defaults
Displays only the channels supported by the OADM modules.
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to verify the system configuration.
Examples
The following example shows how to display optical filter information. (See Table 3-17 for field descriptions.)
Switch# show optical filteraggregate filteredinterface channel(s) interface----------------- ----------- ------------Wdm0/0 0 Oscfilter0/0Wdm0/0 1 Filter0/0/0Wdm0/0 2 Filter0/0/1Wdm0/0 3 Filter0/0/2Wdm0/0 4 Filter0/0/3Wdm0/1 0 Oscfilter0/1Wdm0/1 1 Filter0/1/0Wdm0/1 2 Filter0/1/1Wdm0/1 3 Filter0/1/2Wdm0/1 4 Filter0/1/3
The following example shows how to display optical filter information on a shelf with OADM modules. (See Table 3-18 for field descriptions.)
Swtich# show optical filter detailaggregate filtered patched mux/demuxinterface channel(s) interface interface----------------- ----------- ----------------- -----------------Wdm0/0 0 Oscfilter0/0Wdm0/0 1 Filter0/0/0Wdm0/0 2 Filter0/0/1Wdm0/0 3 Filter0/0/2Wdm0/0 4 Filter0/0/3Wdm0/0 remaining Thru0/0Wdm0/1 0 Oscfilter0/1Wdm0/1 1 Filter0/1/0Wdm0/1 2 Filter0/1/1Wdm0/1 3 Filter0/1/2Wdm0/1 4 Filter0/1/3Wdm0/1 remaining Thru0/1
Related Commands
Configures patch connections for a shelf.
Displays optical connection information.
Displays optical patch connection configuration.
show patch
To display the patch connections, use the show patch command.
show patch [detail]
Syntax Description
Defaults
Displays summary patch connection information.
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to display the patch connections on the OADM modules configured with the patch command.
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 an 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.
Examples
The following example shows how to display patch connection information. (See Table 3-19 for field descriptions.)
Switch# show patchPatch Interface Patch Interface Type Dir Error------------------ ------------------ --------- ---- ----------------Oscfilter0/1 Wave2/1 USER BothOscfilter0/0 Wave2/0 USER BothFilter0/1/2 Wavepatch10/0/0 USER BothFilter0/0/1 Wavepatch8/0/0 USER BothFilter0/1/1 Wavepatch8/0/1 USER BothFilter0/1/3 Wavepatch4/0/0 USER BothFilter0/0/2 Wavepatch7/0/1 USER BothThe following example shows how to display detailed patch connection information. (See Table 3-19 for field descriptions.)
Switch# show patch detailPatch Interface Patch Interface Type Dir Error------------------ ------------------ --------- ---- ----------------Oscfilter0/1 Wave2/1 USER BothOscfilter0/0 Wave2/0 USER BothFilter0/0/2 Wavepatch7/0/1 USER BothFilter0/0/1 Wavepatch8/0/0 USER BothFilter0/1/2 Wavepatch10/0/0 USER BothFilter0/1/1 Wavepatch8/0/1 USER BothFilter0/1/3 Wavepatch4/0/0 USER BothSwitch# show patch detailPatch Interface Patch Interface Type Error----------------- ----------------- --------- ----------------Filter0/0/0 Wavepatch7/0/0 AUTOMATIC Channel Mismatch
Related Commands
Enables debugging of optical port activity.
Configures patch connections within a shelf.
show performance
To display the performance history counters, use the show performance command.
show performance {current | history | 24-hour} [interface] [interval number]
Syntax Description
Defaults
Displays all performance history counters (the current counter, all 15-minute history counters, and the 24-hour counter) for all Cisco ONS 15530 interfaces.
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
Usage Guidelines
Use this command to view the performance history counters for the Cisco ONS 15530 interfaces.
Examples
The following example shows how to display the current counter for an esconphy interface. (See Table 3-20 for field descriptions.)
Switch# show performance current esconphy 9/0/0Current 15 minute performance register--------------------------------------Interface : EsconPhy9/0/0Interval Number : 23Elapsed Time(seconds) : 454Valid Time(seconds) : 454Received Frames : 121203104Transmit Frames : 121203101CRC Error count : 659Code violation and running disparity error count : 9Egress Packet Sequence error count : 0Egress Packet Indicated error count : 10
The following example shows how to display the 15-minute history counter for a gigabitphy interface. (See Table 3-21 for field descriptions.)
Switch# show performance history gigabitphy 2/0/0 5315 minute performance history register--------------------------------------Interface : GigabitPhy2/0/0Interval Number : 53Total Time(seconds) : 900Valid Time(seconds) : 900Received Frames : 17328419Received Bytes : 25992628500Transmit Frames : 17328419Transmit Bytes : 25992630000RX CRC Errors : 0TX CRC Errors : 0Code violation and running disparity error count : 0Giant Packets : 0Runt Packets : 0
The following example shows how to display the 24-hour counter for a portgroup interface. (See Table 3-22 for field descriptions.)
Switch# show performance 24-hour portgroup 4/0/024 hour performance register----------------------------Interface : Portgroup4/0/0Total Time(seconds) : 86400Valid Time(seconds) : 86400Transmit Frames : 57373022290Received Frames : 57372085236Oversized Frames : 0Undersized Frames : 21Code violation and running disparity error count : 4294967295Secondary fabric CVRD count : 0CRC error count : 0CDL HEC error count : 23SII Mismatch error count : 24
Related Commands
show tsi
To display the TSI (Time Slot Interchange) information on the 8-port multi-service muxponders, use the show tsi command.
show tsi [slot-number]
Syntax Description
Defaults
Displays TSI information for all slots.
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
Usage Guidelines
The 8-port multi-service muxponder assigns variable bandwidth using correctly sized STS-n streams for each client protocol and then aggregates the STS-n streams to form a 2.5-Gbps ITS signal. The aggregated signal is demultiplexing in the receive direction. This is achieved using a time slot interchange (TSI) mapping scheme.
Each supported client protocol uses a fixed number of STS-1 streams. Table 3-23 shows the bandwidth allocation.
The trunk signal rate is 2.5-Gbps, which translates to 48 STS-1 streams. The STS-1 stream allocation algorithm is a simple top-down search using the first available required number of STS-1 streams.
Based on the order in which client protocols are configured and removed across the various client ports, the resulting TSI mapping in the client-to-trunk transmit direction can vary. The TSI protocol sends the transmit TSI mapping to the remote muxponder where it is used to program the trunk receive TSI maps.
Note
Examples
The following example shows how to display TSI information. (See Table 3-24 for field descriptions.)
Switch# show tsi 1Port Local Peer Error Trunk STS MapEncap Encap Transmit ReceiveCard: 1, TSI Ver: 1, DCC: SDCC1/0/0, TSI-Protocol: Enabled0. CFE CFE - 00 00 00 00 00 07 00 00 00 00 00 071. CFE CFE - 00 00 00 00 00 38 00 00 00 00 00 382. CFE CFE - 00 00 00 00 01 C0 00 00 00 00 01 C03. None None -4. None None -5. None None -6. None None -7. None None -Available STS= 39------------------------------Card: 9, TSI Ver: 1, DCC: SDCC9/0/0, TSI-Protocol: Enabled0. T1 T1 - 00 00 00 00 00 01 00 00 00 00 00 011. FC1 FC1 - 00 FF FE 00 00 0E 00 00 00 07 FF FE2. T1 T1 - 00 00 00 00 00 01 00 00 00 00 00 013. CFE CFE - 07 00 00 00 00 00 00 00 00 38 00 004. E1 E1 - 00 00 00 00 00 01 00 00 00 00 00 015. CGE CGE - 00 00 01 FF FF F0 07 FF FF C0 00 006. T1 ESCON M 00 00 00 00 00 01 78 00 00 00 00 007. None None -Available STS= 47------------------------------The following concepts are shown by the muxponder in slot 9:
•
The Trunk STS Receive field shows that the STS-1 streams 2 to 19 on the incoming STS-48 signal carry client data from the remote node for this port. A similar explanation can be extended to port 3 (multirate 9/0/3) and port 5 (multirate 9/0/5).
•
•
Related Commands
shutdown
To disable an interface, use the shutdown command. To restart a disabled interface, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Usage Guidelines
This command disables all functions on the specified interface.
This command also marks the interface as unavailable. To check whether an interface is disabled, use the show interfaces command. An interface that has been shut down is shown as administratively down in the show interfaces output.
On transparent, esconphy, gigabitphy, twogigabitphy, and multirate interfaces, use the shutdown command to turn off the transmit lasers. To turn the transmit lasers on, use the no shutdown command.
On wave, waveethernetphy, or tengigethernetphy interfaces, a shutdown command issued does not affect administrative status of the corresponding wavepatch interfaces. To administratively shut down the wavepatch interfaces, issue shutdown commands directly. Also, the shutdown command does not shut down the laser on these interfaces or stop CDL message traffic. To shut down the laser, user the laser shutdown command.
On wavesonetphy interfaces, the shutdown command does not affect data or DCC traffic or the status of the wavepatch interfaces. To administratively shut down the wavepatch interfaces, issue shutdown commands directly. To shut down the laser, user the laser shutdown command.
To use splitter line cards for line card protection, you must shut down the standby wavepatch interfaces. (See the " Examples" section.)
Examples
The following example shows how to shut down a wave interface, which also turns off the laser that transmits to the trunk fiber.
Switch# configure terminalSwitch(config)# interface wave 3/0Switch(config-if)# shutdownThe following example shows how to reenable a transparent interface and turn on the laser transmitting to the client equipment.
Switch# configure terminalSwitch(config)# interface transparent 8/0/0Switch(config-if)# no shutdownThe following example shows how to disable the east (slot 1) side of the wavepatch interface pair on a splitter protected card or muxponder.
Switch# configure terminalSwitch(config)# interface wavepatch 3/0/1Switch(config-if)# shutdownRelated Commands
tsi-protocol
To enable the TSI protocol on a wavesonetphy interface, use the tsi-protocol command. To disable this feature, use the no form of the command.
tsi-protocol
no tsi-protocol
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
Usage Guidelines
Use the show tsi command to verify the status of the STS maps on both nodes.
If the TSI Protocol is disabled, then the user must ensure that the local trunk transmit STS maps match with the remote trunk receive STS map using the show tsi command.
Note
Note
You can ensure that the maps are the same by provisioning the interfaces on each node in the same order.
Examples
The following example shows how to disable the TSI protocol on a wavesonetphy interface.
Switch# configure terminalSwitch(config)# interface wavesonetphy 4/0Switch(config-if)# no tsi-protcolRelated Commands
tx-buffer size
To set the transmit buffer size for ESCON aggregation cards, 4-port 1-Gbps/2-Gbps FC aggregation cards, and 8-port Fibre Channel/Gigabit Ethernet aggregation cards, use the tx-buffer size command. To revert to the default value, use the no form of the command.
tx-buffer size bytes
no tx-buffer size
Syntax Description
bytes
Specifies the transmit buffer size. The range is 16 to 232 on esconphy interfaces and 256 to 13,824 on gigabitphy interfaces.
Defaults
16 bytes for esconphy interfaces on an ESCON aggregation card.
256 bytes for gigabitphy interfaces on an 8-port FC/GE aggregation card.
256 bytes for twogigabitphy interfaces on a 4-port 1-Gbps/2-Gbps FC aggregation card carrying 1-Gbps traffic.
512 bytes for twogigabitphy interfaces on a 4-port 1-Gbps/2-Gbps FC aggregation card carrying 2-Gbps traffic.
Command Modes
Interface configuration
Command History
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
The ESCON aggregation card and 8-port FC/GE aggregation card add latency to the traffic transmission depending on the services configured on the transmitting node. Use the values listed in Table 3-25 to configure the transmission buffer on the esconphy interface on the ESCON aggregation card on the receiving node.
Note
Use the values listed in Table 3-26 and Table 3-27 to configure the transmission buffer on the twogigabitphy interfaces on the 4-port 1-Gbps/2-Gbps FC aggregation card on the receiving node.
Note
Use the values listed in Table 3-28 to configure the transmission buffer on the gigabitphy interfaces on the 8-port FC/GE aggregation card on the receiving node.
Note
Table 3-28 FC, FICON, and ISC Transmit Buffer Settings for Gigabitphy Interfaces
FC/FICON/ISC only on the port pair1 carried over a 2.5-Gbps ITU trunk card
256 (default)
FC/FICON/ISC only on the port pair carried over a 10-Gbps ITU trunk card
256 (default)
FC/FICON/ISC only on the port pair mixed with GE on the same 10-Gbps ITU trunk card
384
640
1280
FC/FICON/ISC and GE on the same port pair carried over a 2.5-Gbps ITU trunk card
768
1792
3712
FC/FICON/ISC and GE on the same port pair carried over a 10-Gbps ITU trunk card
1280
3584
7296
1 A port pair on an 8-port FC/GE aggregation card consists of ports 0-1, 2-3, 4-5, or 6-7.
Caution
Examples
The following example shows how to set the transmit buffer size for a gigabitphy interface on the receiving node.
Switch# configure terminalSwitch(config)# interface gigabitphy 2/0/0Switch(config-if)# shutdownSwitch(config-if)# tx-buffer size 250Switch(config-if)# no shutdownRelated Commands
Displays interface information.
Enables buffer credits for FC and FICON traffic on 8-port FC/GE aggregation cards.
sub-rate
To configure subrates for twogigabitphy interfaces that part of an oversubscribed portgroup or a superportgroup on a 4-port 1-Gbps/2-Gbps FC aggregation card, use the sub-rate command. To remove the subrate configuration, use the no form of the command.
sub-rate rate {lock| }
no sub-rate
Syntax Description
Defaults
The default subrate is 1 MBps.
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
Usage Guidelines
When you oversubscribe a portgroup, you need to configure subrates for every client interface. Subrate is specified in megabytes per second (MBps). For example, to permit full-rate 1-Gbps or 2-Gbps FC traffic over an oversubscribed portgroup, you must specify 106 MBps or 212 MBps as the subrate for that client interface. By default, for each client interface, subrate is set to 1 MBps.
Subrates can be configured only for those client interfaces that are already connected to an oversubscribed portgroup or superportgroup. Incorrect subrate configuration can lead to under utilization of the portgroup bandwidth.
Examples
The following example shows how to configure the subrate for a twogigabitphy interface that is part of an oversubscribed portgroup.
Switch# configure terminalSwitch(config)# interface twogigabitphy 4/0/0Switch(config-if)# sub-rate 50Related Commands
superportgroup
To associate twogigabitphy interfaces encapsulated for FC or FICON traffic to a superportgroup, use the superportgroup command. To remove the superportgroup configuration, use the no form of the command.
superportgroup
no superportgroup
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled.
Command Modes
Interface configuration.
Command History
This table includes the following release-specific history entries:
Usage Guidelines
To configure superportgroup, the following system requirements must be met:
•
•
•
•
Examples
The following example shows how to associate a superportgroup to a twogigabitphy interface:
Switch(config)#configure terminalSwitch(config-if)#interface twogigabitphy 3/0/0Switch(config-if)#superportgroupRelated Commands
Posted: Mon Feb 27 03:20:47 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
