|
|
Table Of Contents
Interface Configuration Commands
cdl defect-indication force hop-endpoint
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 15540 ESPx.
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:
•
EV-Release
•
•
Usage Guidelines
You can configure the signal clock rate with either the cdl defect-indication force hop-endpoint 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.
Table 3-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
The following ranges are not supported by the SM transponder module hardware and the MM transponder module hardware:
•
•
For clock rate values outside of these unsupported ranges and not listed in Table 3-1, contact your SE (systems engineer) at Cisco Systems.
Caution
For information on transceiver specifications, refer to the Cisco ONS 15540 ESPx Hardware Installation Guide.
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.
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:
•
•
•
Usage Guidelines
Use this command to configure the interface as a hop endpoint for in-band message channel defect indications.
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
Disabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
This command is used to enable and disable the in-band message channel on tengigethernetphy interfaces when connected to a Cisco ONS 15530 or any other system that supports the in-band message channel. When the in-band message channel is enabled on a tengigethernetphy interface, ethernetdcc slot/subcard/1 becomes available for configuration.
Examples
The following example shows how to enable in-band message channel on an interface.
Switch# configure terminalSwitch(config)# interface tengigethernetphy 10/0Switch(config-if)# cdl enableRelated Commands
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 the performance history counters (the current counter, all 15-minute history counters, and the 24-hour counter) for all Cisco ONS 15540 ESPx 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
encapsulation
To configure the protocol encapsulation for the client signal on a transparent interface, use the encapsulation command. To disable the encapsulation for the client signal, use the no form of this command.
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
Syntax Description
Defaults
Encapsulation is disabled.
The default rate for ISC peer mode is 2g.
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
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 15540 ESPx because of the nature of the traffic type.
Note
Removing the encapsulation on a transparent interface with the no encapsulation command does not turn off the laser. To turn off the transmit laser to the client equipment, use the show performance command.
Caution
For information on transceiver specifications, refer to the Cisco ONS 15540 ESPx Hardware Installation Guide.
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.
laser control forward enable
To enable forward laser control, which automatically shuts down transponder 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
Disabled
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to enable forward laser control on both the client side and trunk side interfaces of a transponder module and on the OSC wave interfaces. If configured on a transparent interface, the client side laser of the transponder 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 shuts down when client side receiver detects a Loss of Light.
Note
Automatically shutting down the laser prevents the transmission of unreliable data. However, when the laser is shut down, fault isolation is more difficult.
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
Examples
The following example shows how to enable forward laser control on a transparent interface.
Switch# configure terminalSwitch(config)# interface transparent 3/2/0Switch(config-if)# laser control forward enableThe following example shows how to enable forward laser control on a 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 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).
Note
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, use the laser frequency command. To revert to the default value, use the no form of the command.
laser frequency value
no laser frequency
Syntax Description
Defaults
The lower frequency for the interface is the default.
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
The transparent transponders can be tuned to support one of two channel frequencies. The laser frequency command allows the user to change the laser tuning from the default lower frequency to the higher frequency, and back.
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.
Examples
The following example shows how to select the channel frequency on a transponder wave interface.
Switch(config)# interface wave 3/0Switch(config-if)# laser frequency 192300Related Commands
laser shutdown
To turn off the laser on an interface supporting the in-band message channel, 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
The laser is on.
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 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 transponder module interfaces, use the loopback command. To disable interface loopback, use the no form of this command.
loopback
no loopback
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 configure internal loopbacks on transponder module interfaces. For any given transponder module, you can configure an internal loopback on either the client side interface or the trunk side interface, but not both simultaneously.
An internal 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.
Note
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 module, 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 module. The following protocols can be monitored:
•
•
•
•
•
•
•
•
•
•
•
•
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 15540 ESPx monitors the following conditions:
•
•
•
•
For SONET errors, the Cisco ONS 15540 ESPx monitors the SONET section overhead only, not the SONET line overhead. Specifically, the Cisco ONS 15540 ESPx monitors the B1 byte and the framing bytes. The system can detect the following defect conditions:
•
•
•
•
For SONET performance, the system monitors the B1 byte, which is used to compute the four SONET section layer performance monitor parameters:
•
•
•
•
For ISC 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 transparent interface.
Displays interface information.
optical threshold power receive
To set the receive optical threshold power for alarms on wdm, thru, and wavepatch interfaces, use the optical threshold power receive command.To revert to the default values, use the no form of the command.
optical threshold power receive {low | high} {alarm | warning} value [severity {critical | major | minor | not alarmed | not reported}]
no optical threshold power receive
Syntax Description
Defaults
Alarm severity: major
Warning severity: not alarmed
Command Modes
Interface configuration
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
The default value for high alarm threshold corresponds to the receiver saturation level for the transponder module.
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 cover 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, since 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 to 10 dB below the power level measured at the interface when a signal exists or to -28 dB, whichever value is higher.
Note
Examples
The following example shows how to set the optical power low alarm threshold.
Switch(config)# interface wavepatch 8/0/0Switch(config-if)# optical threshold power receive low alarm -210Related Commands
patch
To configure the patch connections within a shelf, use the patch command. To remove the patch connection configuration, use the no form of this 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 interface1 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 mux/demux modules.
Valid patch connections between modules are:
•
wdm slot/subcard1 thru slot/subcard2
•
thru slot/subcard1 wdm slot/subcard2
•
wave slot oscfilter slot/subcard
•
oscfilter slot/subcard wave slot
•
thru slot1/subcard1 thru slot2/subcard2
•
wdm slot/subcard wdmrelay slot/subcard/port
•
wavepatch slot/subcard/port filter slot/subcard/port
•
filter slot/subcard/port wavepatch 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 interface2 in the receive direction or the transmit direction. The absence of a keyword indicates the patch connection is bidirectional.
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 patch a connection between two mux/demux modules in the same slot.
Switch#configure terminalSwitch(config)#patch wdm 1/0 thru 1/1Related 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 displays 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 None 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/0Oper. Status: upAdmin. Status: upConfigured Node Behavior: Hop TerminatingCurrent Node Behavior : Hop TerminatingDefect Indication Receive : NoneDefect Indication Transmit: NoneInterface WaveEthernetPhy4/0Oper. Status: upAdmin. Status: upConfigured Node Behavior: Hop TerminatingCurrent Node Behavior : Hop TerminatingDefect Indication Receive : NoneDefect Indication Transmit: NoneRelated 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:
•
•
12.2(18)SV
This command was first introduced.
12.2(22)S
This command was integrated in this release.
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-3 for field descriptions.)
Switch# show cdl flow defect-indicationDI = Defect IndicationInterface DI Received DI Transmittedfrom CDL network to CDL network------------ ----------------------- -----------------------Tengig8/0
Related Commands
Configures an interface as an end-of-hop.
Enables in-band message channel functionality.
Initiates debugging of defect indication on in-band message channel capable interfaces.
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
None
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 mux/demux interface.
Examples
The following example shows how to display edge connection information. (See Table 3-4 for field descriptions.)
Switch# show connect edgesclient/wave wdm channel---------- --- -----Trans3/0/0 1/0 26Trans3/1/0 1/0 27Trans3/2/0 1/0 28Trans3/3/0 1/0 29
The following example shows how to display intermediate connection information. (See Table 3-5 for field descriptions.)
Switch# show connect intermediateclient/ wave wave wdmwave client patch filter trk channel------------ ------------ ------- ------ --- -------Trans3/0/0 Wave3/0 3/0/0* 0/0/4 0/0 53/0/1Trans3/1/0 Wave3/1 3/1/0* 0/0/5 0/0 63/1/1Trans3/2/0 Wave3/2 3/2/0* 0/0/6 0/0 73/2/1Trans3/3/0 Wave3/3 3/3/0* 0/0/7 0/0 83/3/1
The following example shows how to display interface connection information. (See Table 3-6 for field descriptions.)
Switch# show connect interface transparent 2/0/0Client :Transparent2/0/0Wave :Wave2/0Wavepatch :Wavepatch2/0/0 (active) Wavepatch :Wavepatch2/1/0Filter :Filter0/0/0 Filter :Filter1/0/0Wdm :Wdm0/0 Wdm :Wdm1/0Thru :Thru0/1 Thru :Thru1/1Wdm :Wdm0/1 Wdm :Wdm1/1Thru :Thru0/2 Thru :Thru1/2Wdm (trnk):Wdm0/2 Wdm :Wdm1/2
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-7.
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-7 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-8 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-8 show controllers 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
Indicates 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 module 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
Indicates 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 wave interface. (See Table 3-8 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-8 for field descriptions.)
Switch# show controllers wave 0Controller info for OSC wave interface Wave0LRC 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]]]
Syntax Description
type
Specifies one of the interface types listed in Table 3-9.
slot
Specifies a chassis slot.
subcard
Specifies a subcard position in a motherboard.
port
Specifies a port.
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-9 shows the interface types for the show interfaces command.
Examples
The following example shows how to display transparent interface information. (See Table 3-10 for field descriptions.)
Switch# show interfaces transparent 3/1/0Transparent3/1/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 wave interface information. (See Table 3-11 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 wave interface information. (See Table 3-11 for field descriptions.)
Switch# show interfaces wave 0Wave0 is administratively up, line protocol is upChannel: 0 Frequency: 191.9 Thz Wavelength: 1562.23 nmSplitter Protected: NoLaser safety control: OffForward laser control: OffOsc physical port: YesWavelength used for inband management: NoConfigured threshold Group: NoneLoopback not setLast clearing of "show interface" counters neverHardware is OSC_phy_portMTU 1492 bytes, BW 10000000 Kbit, DLY 0 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation SNAP, loopback not setCDL receive header error count: 0Last input 00:00:02, 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/sec3447 packets input, 269630 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 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-12 for field descriptions.)
Switch# show interfaces wdm 0/0Wdm0/0 is up, line protocol is upPatched Interface: Thru0/1Wdm Hw capability: N/ANum of Wavelengths Add/Dropped: 8List of Wavelengths: 1, 2, 3, 4, 5, 6, 7, 8,Hardware is wavelength_add_drop
Related Commands
show optical filter
To display information about the channels supported by the mux/demux modules, use the show optical filter command.
show optical filter [detail]
Syntax Description
detail
Shows optical patch connections between the mux/demux modules in addition to the channels supported. This information displays only if the patch connection have been configured with the patch command.
Defaults
Displays only the channels supported by the mux/demux 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 channels supported by the mux/demux modules on the system.
Examples
The following example shows how to display optical filter information. (See Table 3-13 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/0 5 Filter0/0/4Wdm0/0 6 Filter0/0/5Wdm0/0 7 Filter0/0/6Wdm0/0 8 Filter0/0/7Wdm0/2 17 Filter0/2/0Wdm0/2 18 Filter0/2/1Wdm0/2 19 Filter0/2/2Wdm0/2 20 Filter0/2/3Wdm0/2 21 Filter0/2/4Wdm0/2 22 Filter0/2/5Wdm0/2 23 Filter0/2/6Wdm0/2 24 Filter0/2/7Wdm1/0 0 Oscfilter1/0Wdm1/0 1 Filter1/0/0Wdm1/0 2 Filter1/0/1Wdm1/0 3 Filter1/0/2Wdm1/0 4 Filter1/0/3Wdm1/0 5 Filter1/0/4Wdm1/0 6 Filter1/0/5Wdm1/0 7 Filter1/0/6Wdm1/0 8 Filter1/0/7
The following example shows how to display optical filter information on a shelf with add/drop mux/demux modules. (See Table 3-14 for field descriptions.)
Swtich# show optical filter detailaggregate filtered patched mux/demuxinterface channel(s) interface interface----------------- ----------- ----------------- -----------------Wdm0/3 0 Oscfilter0/3Wdm0/3 25 Filter0/3/0Wdm0/3 26 Filter0/3/1Wdm0/3 27 Filter0/3/2Wdm0/3 28 Filter0/3/3Wdm0/3 29 Filter0/3/4Wdm0/3 30 Filter0/3/5Wdm0/3 31 Filter0/3/6Wdm0/3 32 Filter0/3/7Wdm0/3 remaining Thru0/3 Thru1/3Wdm1/3 0 Oscfilter1/3Wdm1/3 25 Filter1/3/0Wdm1/3 26 Filter1/3/1Wdm1/3 27 Filter1/3/2Wdm1/3 28 Filter1/3/3Wdm1/3 29 Filter1/3/4Wdm1/3 30 Filter1/3/5Wdm1/3 31 Filter1/3/6Wdm1/3 32 Filter1/3/7Wdm1/3 remaining Thru1/3 Thru0/3
Related Commands
Configures patch connections for a shelf.
Displays optical connection information.
Displays optical patch connection configuration.
show optical interface brief
To display the optical characteristics of all the transponders in the system, use the show optical interface brief command.
show optical interface brief
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entries:
•
•
•
Usage Guidelines
Use this command to quickly verify the status of the optical signals on the transponder module interfaces. For more detailed information about the interface, use the show interfaces command.
Examples
The following example shows how to display optical interface signal information. (See Table 3-15 for field descriptions.)
Switch# show optical interface briefI Interface Status/Prot Laser Signal Quality Rx Power Speed/Encap----------- ----------- ----- -------------- ----------- ---------------Wave0 down/down on Loss of light n/a SNAPWave1 up/up on Good n/a SNAPWdmS0/2/0* down/down n/a Loss of light < -32.00 dBm n/aWdmS0/2/1 down/down n/a Loss of light < -32.00 dBm n/aTrans2/2/0 up/up on Good n/a GigbitEthernetWave2/2 up/up on Good -16.78 dBm n/aWavep2/2/0 admin/down n/a n/a Unknown n/aWavep2/2/1* up/up n/a n/a -16.76 dBm n/aTenGE3/1 up/up on Good n/a 10G EthernetEther3/1/1 up/up n/a Good n/a SNAPWaveE3/1 up/up on Good -12.45 dBm n/aEther3/1/0 up/up n/a Good n/a SNAPWavep3/1/0* up/up n/a n/a -12.45 dBm n/aWavep3/1/1 up/up n/a n/a Unknown n/aTrans4/0/0 down/down on Loss of light n/a 916000 KHzWave4/0 down/down on Loss of light < -33.00 dBm n/aWavep4/0/0* down/down n/a n/a < -33.00 dBm n/aTrans9/0/0 admin/down off n/a n/a SONET oc48Wave9/0 admin/down off n/a < -35.00 dBm n/aWavep9/0/0* down/down n/a n/a < -35.00 dBm n/aWavep9/0/1 down/down n/a n/a Unknown n/a
Related Commands
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 mux/demux 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 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.
Examples
The following example shows how to display patch connection information. (See Table 3-16 for field descriptions.)
Switch# show patchPatch Interface Patch Interface Type Dir Error------------------ ------------------ --------- ---- ----------------Thru0/0 Wdm0/1 USER BothThru0/1 Thru1/0 USER BothThe following example shows how to display detailed patch connection information. (See Table 3-16 for field descriptions.)
Switch# show patch detailPatch Interface Patch Interface Type Error--------------- --------------- --------- -------Wavepatch10/0/0 Filter0/3/0 AUTOMATICWavepatch10/1/0 Filter0/3/1 AUTOMATICWavepatch10/2/0 Filter0/3/2 AUTOMATICWavepatch10/3/0 Filter0/3/3 AUTOMATICWave0 Oscfilter0/0 USERWdm0/0 Thru0/1 USERWdm0/1 Thru0/2 USERWdm0/2 Thru0/3 USERThru0/0 Wdm0/3 USER
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 15540 ESPx interfaces.
Command Modes
EXEC and privileged EXEC
Command History
This table includes the following release-specific history entry:
Usage Guidelines
Use this command to view the performance history counters for the Cisco ONS 15540 ESPx interfaces.
Examples
The following example shows how to display the current counter for a transparent interface. (See Table 3-17 for field descriptions.)
Switch# show performance current transparent 2/2/0Current 15 minute performance register--------------------------------------Interface : Transparent2/2/0Interval Number : 81Elapsed Time(seconds) : 526Valid Time(seconds) : 526Code violation and running disparity error count : 0
The following example shows how to display the 15-minute history counter for a tengigethernetphy interface with CDL disabled. (See Table 3-18 for field descriptions.)
Switch# show performance history tengigEthernetPhy 10/0 2015 minute performance history register--------------------------------------Interface : TenGigEthernetPhy10/0Interval Number : 20Total Time(seconds) : 900Valid Time(seconds) : 900Code violation and running disparity error count : 0TenGige Non CDL Pkt count : 0
The following example shows how to display the 24-hour counter for a tengigethernetphy interface with CDL enabled. (See Table 3-19 for field descriptions.)
Switch# show performance 24-hour tenGigEthernetPhy 10/124 hour performance register----------------------------Interface : TenGigEthernetPhy10/1Total Time(seconds) : 86400Valid Time(seconds) : 86400Code violation and running disparity error count : 0TenGige Non CDL Pkt count : 0CDL HEC error count : 0TenGige CDL idle Pkt count : 0
Related Commands
Displays interface information.
auto-sync counters interface
Enables the automatic synchronization of the performance history counters.
Clears the performance history counters.
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 and wave interfaces, use the shutdown command to turn off the transmit lasers. To turn the transmit lasers on, use the no shutdown command.
On CDL capable interfaces, such as tengigethernetphy and waveethernetphy interfaces, use the shutdown command to stop sending data traffic. To resume sending data traffic, use the no shutdown command. On the 10-GE transponder module, use the laser shutdown command to turn the lasers off and on.
A shutdown command issued on a wave interface does not affect administrative status of the corresponding wavepatch interfaces. To administratively shut down the wavepatch interfaces, issue shutdown commands directly.
To use splitter protected line card motherboards for line card protection, you must shut down all the wavepatch interfaces connected to one of the mux/demux motherboards. (See the " Examples" section.)
The laser shutdown command does not affect the function of the shutdown command.
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 wave0/3Switch(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 line card motherboard.
Switch# configure terminalSwitch(config)# interface wavepatch 3/0/1Switch(config-if)# shutdownRelated Commands
Posted: Thu Feb 16 04:30:32 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
