|
Table Of Contents
debug driver ten-gigabit trunk
debug driver transponder events
debug driver two-five-gigabit trunk
Debug Commands
Use the following commands to debug the Cisco ONS 15530. For information on other debug commands refer to the Cisco IOS Debug Command Reference document.
debug aps
To debug APS operation, use the debug aps command. To disable APS debugging, use the no form of this command.
debug aps
no debug aps
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled.
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to enable debugging of APS operations.
Switch# debug aps
Related Commands
Command DescriptionCreates or specifies an APS interface group and enters APS configuration mode.
Associates wavepatch interfaces for APS splitter protection.
Disables all debugging.
debug cdl defect-indication
To enable debugging for the in-band message channel defect indications, use the debug cdl defect-indication command. To disable debugging for in-band message channel defect indications, use the no form of this command.
debug cdl defect-indication {error | events | periodic}
no debug cdl defect-indication {error | events | periodic}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to enable debugging for the message channel.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to enable debugging for the in-band message channel.
Switch# debug cdl defect-indication errors
Related Commands
Command DescriptionEnables online diagnostics for the system.
Enables online diagnostics for a specified slot number.
Disables all debugging.
debug cm
To enable debugging for the connection manager, use the debug cm command. To disable debugging for the connection manager, use the no form of this command.
debug cm {errors | events | sync {errors | events}}
no debug cm {errors | events | sync {errors | events}}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to enable debugging for the connection manager.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to enable debugging of the connection manager.
Switch# debug cm events
Related Commands
debug cpu
To debug IPC (interprocess communication) initialization and switchover events, use the debug cpu command. To disable debugging IPC initialization and switchover events, use the no form of this command.
debug cpu {ipc | redundancy | ehsa | sub-ipc}
no debug cpu {ipc | redundancy | ehsa | sub-ipc}
Syntax Description
Defaults
Disabled.
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to enable debugging of IPC initialization and switchover events. To debug redundancy software operations, use the debug redundancy command.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to enable redundancy state debugging.
Switch# debug cpu redundancy
Related Commands
debug diag online
To enable debugging for online diagnostics, use the debug diag online command. To disable debugging for online diagnostics, use the no form of this command.
debug diag online [online-insertion-removal | background | redundancy]
no debug diag online [online-insertion-removal | background | redundancy]
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to enable debugging for online diagnostics.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to enable debugging of background tests for online diagnostics.
Switch# debug diag online background
Related Commands
debug driver 2gfc
To enable 4-port 1-Gbps/2-Gbps FC aggregation card driver debugging, use the debug driver 2gfc command. To disable 4-port 1-Gbps/2-Gbps FC aggregation card driver debugging operations, use the no form of this command.
debug driver 2gfc {errors | events | fpga | periodic}
no debug driver 2gfc {errors | events | fpga | periodic}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•SV-Release
Usage Guidelines
Use this command to enable 4-port 1-Gbps/2-Gbps FC aggregation card driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate 4-port 1-Gbps/2-Gbps FC aggregation card driver debugging.
Switch# debug driver 2gfc errors
Related Commands
debug driver control ethernet
To enable backplane Ethernet driver debugging, use the debug driver control ethernet command. To disable backplane ethernet driver debugging operations, use the no form of this command.
debug driver control ethernet {errors | events | packets}
no debug driver control ethernet {errors | events | packets}
Syntax Description
errors
Enables debugging for SRC driver error conditions.
events
Enables debugging for internal software error conditions.
packets
Enables debugging of the backplane Ethernet driver packets.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate backplane Ethernet driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate backplane Ethernet driver error debugging.
Switch# debug driver control ethernet errors
Related Commands
debug driver escon
To enable ESCON aggregation card driver debugging, use the debug driver escon command. To disable ESCON aggregation card driver debugging operations, use the no form of this command.
debug driver escon {errors | events | fpga}
no debug driver escon {errors | events | fpga}
Syntax Description
errors
Enables debugging for ESCON aggregation card driver error conditions.
events
Enables debugging for internal software events.
fpga
Enables debugging FPGA operations.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to enable ESCON aggregation card driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate ESCON aggregation card driver debugging.
Switch# debug driver escon errors
Related Commands
debug driver gefc
To enable 8-port FC/GE aggregation card driver debugging, use the debug driver gefc command. To disable 8-port FC/GE aggregation card driver debugging operations, use the no form of this command.
debug driver gefc {errors | events | fpga | periodic}
no debug driver gefc {errors | events | fpga | periodic}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to enable 8-port FC/GE aggregation card driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate 8-port FC/GE aggregation card driver debugging.
Switch# debug driver gefc errors
Related Commands
debug driver multirate
To enable 8-port multi-service muxponder driver debugging, use the debug driver multirate command. To disable 8-port multi-service muxponder driver debugging operations, use the no form of this command.
debug driver multirate {errors | events | fpga | periodic | stop | tle1 | tsi {errors | events | messages} | xcrv}
no debug driver multirate {errors | events | fpga | periodic | stop | tle1 | tsi {errors | events | messages} | xcrv}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•SV-Release
Usage Guidelines
Use this command to enable 8-port multi-service muxponder driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate 8-port multi-service muxponder driver debugging.
Switch# debug driver multirate errors
Related Commands
debug driver nvram
To enable NVRAM file system debugging, use the debug driver nvram command. To disable NVRAM file system debugging operations, use the no form of this command.
debug driver nvram {errors | events}
no debug driver nvram {errors | events}
Syntax Description
errors
Enables debugging for NVRAM driver error conditions.
events
Enables debugging for internal software events.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to enable NVRAM file system platform specific debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate NVRAM file system platform specific debugging.
Switch# debug driver nvram errors
Related Commands
debug driver osc
To enable the OSC driver debugging, use the debug driver osc command. To disable the OSC driver debugging, use the no form of this command.
debug driver osc {events | fpga}
no debug driver osc {events | fpga}
Syntax Description
events
Enables debugging for internal software error conditions.
fpga
Enables debugging of the FPGA.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate the OSC driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate the OSC driver error debugging.
Switch# debug driver osc errors
Related Commands
debug driver psm
To enable the PSM driver debugging, use the debug driver psm command. To disable PSM driver debugging, use the no form of this command.
debug driver psm {errors | events}
no debug driver psm {errors | events}
Syntax Description
errors
Enables debugging for PSM driver error conditions.
events
Enables debugging for internal software events.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate the PSM driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate the PSM driver error debugging.
Switch# debug driver psm errors
Related Commands
Command DescriptionEnables debugging of APS and APS Channel Protocol activity.
Enables debugging of optical port activity.
Disables all debugging.
debug driver src
To enable SRC driver debugging, use the debug driver src command. To disable SRC driver debugging operations, use the no form of this command.
debug driver src {errors | events | poll-errors | portfail | defect-indication {errors | events | periodic}}
no debug driver src {error | events | poll-errors | portfail | defect-indication {errors | events | periodic}}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate SRC driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate SRC driver debugging.
Switch# debug driver src
Related Commands
debug driver ten-gigabit trunk
To enable 10-Gbps ITU tunable and non tunable trunk card driver debugging, use the debug driver ten-gigabit trunk command. To disable 10-Gbps ITU tunable and non tunable trunk card driver debugging operations, use the no form of this command.
debug driver ten-gigabit trunk {errors | events}
no debug driver ten-gigabit trunk {error | events}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate 10-Gbps ITU tunable and non tunable trunk card driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate 10-Gbps ITU tunable and non tunable trunk card driver debugging.
Switch# debug driver ten-gigabit trunk events
Related Commands
debug driver transponder events
To enable transponder line card driver events debugging, use the debug driver transponder command. To disable transponder line card driver events debugging operations, use the no form of this command.
debug driver transponder events
no debug driver transponder events
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate transponder line card driver events debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate transponder line card events driver debugging.
Switch# debug driver transponder events
Related Commands
debug driver two-five-gigabit trunk
To enable 2.5-Gbps ITU trunk card driver debugging, use the debug driver two-five-gigabit trunk command. To disable 2.5-Gbps ITU trunk card driver debugging operations, use the no form of this command.
debug driver two-five-gigabit trunk {errors | events}
no debug driver two-five-gigabit trunk {error | events}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate 2.5-Gbps ITU trunk card driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate 2.5-Gbps ITU trunk card driver debugging.
Switch# debug driver two-five-gigabit trunk events
Related Commands
debug driver voa
To enable VOA (variable optical attenuator) module driver debugging, use the debug driver voa command. To disable VOA module driver debugging operations, use the no form of this command.
debug driver voa
no debug driver voa
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate VOA module driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to activate VOA module driver debugging.
Switch# debug driver voa
Related Commands
debug oscp
To debug OSCP operations, use the debug oscp command. To disable debugging for OSCP operations, use the no form of this command.
debug oscp {events | hello-packet | transport} [wave slot/subcard]
no debug oscp {events | hello-packet | transport} [wave slot/subcard]
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to enable debugging for OSCP activity.
To disable all debugging, use the undebug all command.
Caution This command can generate a significant amount of output and may interfere with other activity on the system once the command is invoked.
Examples
The following example shows how to enable debugging for OSCP events.
Switch# debug oscp events
01:53:59:Control interface Wave1 is going up
01:54:00:OSCP:Adding neighbor on wave Wave1
The following example shows how to display information contained in the OSCP Hello packets.
Switch# debug oscp hello-packet wave 0
01:53:08:OSCP:Hello at Wave1 Tx, state 2way
01:53:08: NodeId:0202.0304.0506 Port:10000
01:53:08: Remote:NodeId:0202.0304.0506 Port:10000
01:53:08:OSCP:Hello at Wave1 Rx, state 2way
01:53:08: NodeId:0202.0304.0506 Port:10000
01:53:08: Remote:NodeId:0202.0304.0506 Port:10000
01:53:08:OSCP:Hello event 2wayd
Related Commands
Command DescriptionDisplays OSCP configuration information.
Displays OSCP neighbor information.
Displays OSCP activity statistics.
Displays OSCP message traffic information.
Disables all debugging.
debug ports
To debug port operations, use the debug ports command. To disable debugging for port operations, use the no form of this command.
debug ports {errors [type slot[/subcard[/port]]] | events [type slot[/subcard[/port]]] | patch}
no debug ports {errors [type slot[/subcard[/port]]] | events [type slot[/subcard[/port]]] | patch}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to debug common software errors and events, patch connection activity, and cross connection activity. If the interface option is not specified, debugging is enabled for all interfaces.
To disable all debugging, use the undebug all command.
Examples
The following example shows how to enable error debugging for transparent interface 2/0/0.
Switch# debug ports errors transparent 2/0/0
Related Commands
debug redundancy
To debug redundancy operations, use the debug redundancy command. To disable debugging for redundancy operations, use the no form of this command.
debug redundancy {ehsa | errors | fsm | kpa | msg | progression | status | timer}
no debug redundancy {ehsa | errors | fsm | kpa | msg | progression | status | timer}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to debug redundancy software operations. Use the debug cpu command to debug CPU switch module redundancy.
To disable all debugging, use the undebug all command.
Caution This command can generate a significant amount of output and may interfere with other activity on the system once the command is invoked.
Examples
The following example shows how to debug finite state machine transition events.
Switch# debug redundancy fsm
Related Commands
Command DescriptionEnables debugging of CPU switch module redundancy.
Displays CPU switch module redundancy status and configuration information.
Disables all debugging.
debug switch
To enable switch driver debugging, use the debug switch command. To disable debugging switch driver operations, use the no form of this command.
debug switch {errors | events | sync}
no debug switch {errors | events | sync}
Syntax Description
errors
Enables debugging for switch driver error conditions.
events
Enables debugging for switch driver event conditions.
sync
Enables debugging for switch driver connections.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate switch driver debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to enable switch fabric error debugging.
Switch# debug switch errors
Related Commands
debug topology
To enable topology neighbor debugging, use the debug topology command.
To disable debugging for redundancy operations, use the no form of this command.
debug topology {ehsa | errors | fsm | kpa | msg | progression | status | timer}
no debug topology {ehsa | errors | fsm | kpa | msg | progression | status | timer}
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to activate topology neighbor debugging.
To turn off all debugging, use the undebug all command.
Examples
The following example shows how to enable topology debugging.
Switch# debug topology errors
Related Commands
undebug all
To disable all debugging, use the undebug all command.
undebug all
Syntax Description
This command has no other arguments or keywords.
Defaults
None
Command Modes
Privileged EXEC
Command History
This table includes the following release-specific history entries:
•EV-Release
•SV-Release
•S-Release
Usage Guidelines
Use this command to turn off all debugging.
Examples
The following example shows how to turn off all debugging.
Switch# undebug all
Related Commands
Posted: Mon Feb 27 03:19:56 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.