-
Cisco MDS 9000 Family Command Reference, Release 1.3 (from Release 1.3(1) through Release 1.3(6))
-
New and Changed Information
-
Preface
-
CLI Overview
-
A Commands
-
C Commands
-
D Commands
-
Debug Commands
-
E Commands
-
F Commands
-
G Commands
-
H Commands
-
I Commands
-
K Commands
-
L Commands
-
M Commands
-
N Commands
-
O Commands
-
P Commands
-
Q Commands
-
R Commands
-
S Commands
-
Show Commands
-
T Commands
-
U Commands
-
V Commands
-
W Commands
-
Z Commands
-
Advanced Services Module Commands
-
Caching Services Module (CSM) Commands
-
FeedbackTable Of Contents
Debug Commands
The commands in this chapter apply to the Cisco MDS 9000 Family of multilayer directors and fabric switches. All debug commands are issued in EXEC mode and are shown here in alphabetical order. For more information, refer to the Cisco MDS 9000 Family Troubleshooting Guide and the Cisco MDS 9000 Family System Messages Guide.
Using the CLI, you can enable debugging modes for each switch feature and view a real-time updated activity log of the control protocol exchanges. Each log entry is time-stamped and listed in chronological order. Access to the debug feature can be limited through the CLI roles mechanism and can be partitioned on a per-role basis.
debug aaa
To enable debugging for boot variables, use the debug aaa command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug aaa {all | conf-events | errors | events | mts}
no debug aaa {all | conf-events | errors | events | mts}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(1).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug aaa conf-events command is issued:
switch# debug aaa conf-eventsNov 20 06:29:52 aaa: aaa_cleanup_sessionNov 20 06:29:52 aaa: mts_drop of request msgNov 20 06:29:52 aaa: Configured method local SucceededNov 20 06:29:58 aaa: Src: 0x00000101/10886 Dst: 0x00000101/0 ID: 0x003ize: 197 [REQ] Opc: 8402 (MTS_OPC_AAA_REQ) RR: 0x003A48F7 HA_SEQNO: 0x0TS: 0x9FC1C1234E7C REJ:0 SYNC:0Nov 20 06:29:58 aaa: 01 01 0C 00 00 00 00 00 00 00 00 00 00 00 02 01Nov 20 06:29:58 aaa: 00 00 00 00 00 00 00 06 08 00 03 05 00 00 00 00Nov 20 06:29:58 aaa: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Nov 20 06:29:58 aaa: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Nov 20 06:29:58 aaa: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Nov 20 06:29:58 aaa: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Nov 20 06:29:58 aaa: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Nov 20 06:29:58 aaa: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Nov 20 06:29:58 aaa: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Nov 20 06:29:58 aaa: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00debug all
To enable debugging for all features on the switch, use the debug all command in EXEC mode. You can disable this command and turn off all debugging by using the no form of this command.
debug all
no debug all
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug all command is issued:
switch# debug alldebug bootvar
To enable debugging for boot variables, use the debug bootvar command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug bootvar {all | errors | events | info | pss}
no debug bootvar {all | errors | events | info | pss}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug bootvar all command is issued:
switch# debug bootvar alldebug callhome
To enable debugging for the Call Home function, use the debug callhome command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug callhome {all | events | mts}
no debug callhome {all | events | mts}
Syntax Description
all
Enables debugging for all Call Home features.
events
Enables debugging for all Call Home events.
mts
Enables debugging for all Call Home tx/rx packets of MTS
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
The debug callhome command, when used with the all parameter, displays the troubleshooting information for both Call Home event traces and a dump of the messaging and transaction service (MTS) messages that the Call Home function receives.
Note
The debug Call Home function displays event traces for both successful and unsuccessful Call Home e-mail transmissions.
Examples
The following example displays the system output when the debug callhome events command is issued:
switch# debug callhome events2005-03-09T05:37:21 2005 Mar 9 05:37:21 callhome: filling in name field with Test2005 Mar 9 05:37:21 callhome: filling in the header list2005 Mar 9 05:37:21 callhome: filling up the chassis list2005 Mar 9 05:37:21 callhome: filling up the main body list2005 Mar 9 05:37:21 callhome: filling up the fru list 2005 Mar 9 05:37:21 callhome: Entering function do_event_correlation2005 Mar 9 05:37:21 callhome: getting dest profiles for alert group test2005 Mar 9 05:37:21 callhome: getting dest profiles for alert group cisco-tac2005 Mar 9 05:37:21 callhome: Applying the event rule for destination profile full_txt2005 Mar 9 05:37:21 callhome: Applying the event rule for destination profile short_txt2005 Mar 9 05:37:21 callhome: Applying the event rule for destination profile xml 2005 Mar 9 05:37:21 callhome: Applying the event rule for destination profile basu2005 Mar 9 05:37:21 callhome: Exiting function do_event_correlation2005 Mar 9 05:37:21 callhome: running cli commands for alert name : Test, message id : 15403834262005 Mar 9 05:37:21 callhome: process scheduled for running cli commands for alert Test, message id 1540383426, destination profile basu2005 Mar 9 05:37:21 callhome: process scheduled for running cli commands for alert Test, message id 1540383426, destination profile xml2005 Mar 9 05:37:21 callhome: process scheduled for running cli commands for alert Test, message id 1540383426, destination profile short_txt..The following example displays the system output when the debug callhome mts command is issued:
switch# debug callhome mtsApr 8 13:09:42 callhome: Src: 0x00000501/4067 Dst: 0x00000501/66 ID: 0x0004FA0D Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0004FA0D HA_SEQNO:0x00000000 TS: 0x86708AFE37B REJ:0Apr 8 13:09:42 callhome: 00 00 00 00 06 00 00 00 00 00 00 00 00 00 00 00Apr 8 13:09:42 callhome: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 8 13:09:42 callhome: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF...Apr 8 13:09:42 callhome: Src: 0x00000501/4067 Dst: 0x00000501/66 ID: 0x0004FA10 Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0004FA10 HA_SEQNO:0x00000000 TS: 0x86708D6A974 REJ:0Apr 8 13:09:42 callhome: 00 00 00 00 05 00 00 00 00 00 00 00 00 00 00 00Apr 8 13:09:42 callhome: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 8 13:09:42 callhome: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF...debug cdp
To enable debugging for the CDP function, use the debug cdp command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug cdp {all | errors | events {mts | packets | pss}}
[interface {gigabitethernet slot/port | mgmt 0}]no debug cdp {all | errors | events {mts | packets | pss}}
[interface {gigabitethernet slot/port | mgmt 0}]Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug cdp events packets command is issued:
switch# debug cdp events packetsApr 8 21:22:34 cdp: Sent CDP packet, interface 0x2380000Apr 8 21:22:34 cdp: Sent CDP packet, interface 0x2381000Apr 8 21:22:35 cdp: Sent CDP packet, interface 0x2382000Apr 8 21:22:35 cdp: Sent CDP packet, interface 0x2383000Apr 8 21:22:51 cdp: Received CDP packet, interface 0x5000000Apr 8 21:23:01 cdp: Sent CDP packet, interface 0x5000000Apr 8 21:23:34 cdp: Sent CDP packet, interface 0x2380000Apr 8 21:23:34 cdp: Sent CDP packet, interface 0x2381000Apr 8 21:23:35 cdp: Sent CDP packet, interface 0x2382000...debug cimserver
To enable debugging for the Common Information Model (CIM) management applications function, use the debug cimserver command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug cimserver {all | errors | events | mts | trace}
no debug cimserver {all | errors | events | mts | trace}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(1).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug cimserver all command is issued:
switch# debug cimserver all2004 Mar 29 20:05:22 cimsrvprov: cim_mts_dispatch(): Opcode is 182debug core
To enable core daemon debugging, use the debug core command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug core {error | flow}
no debug core {error | flow}
Syntax Description
error
Enables debugging for core demon error conditions.
flow
Enables debugging for the core demon flow.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug core flow command is issued:
switch# debug core flowdebug dstats
To enable delta statistics debugging, use the debug dstats command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug dstats {error | flow}
no debug dstats {error | flow}
Syntax Description
error
Enables debugging for delta statistics error conditions.
flow
Enables debugging for the delta statistics flow.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug dstats flow command is issued:
switch# debug dstats flowdebug ethport
To enable Ethernet port debugging, use the debug ethport command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ethport {all | error |
event [interface gigabitethernet slot/port | module slot] |
ha [interface gigibetethernet slot/port | module slot] |
trace [interface gigibetethernet slot/port | module slot]}no debug ethport {all | error |
event [interface gigabitethernet slot/port | module slot] |
ha [interface gigibetethernet slot/port | module slot] |
trace [interface gigibetethernet slot/port | module slot]}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug ethport all command is issued:
switch# debug ethport all1981 May 5 07:28:59 ethport: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)1981 May 5 07:28:59 ethport: fu_fsm_execute_all: null fsm_event_list1981 May 5 07:28:59 ethport: fu_fsm_engine_post_event_processing: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 52343) droppeddebug exceptionlog
To enable the exception log debugging feature, use the debug exceptionlog command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug exceptionlog {demux | deque | error | flow | info}
no debug exceptionlog {demux | deque | error | flow | info}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug exceptionlog command is issued:
switch# debug exceptionlog7), credit(3), emptydebug fabric-binding
To enable debugging for the fabric binding feature, use the debug fabric-binding command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fabric-binding {all | efmd {db-events | errors | merge {errors | events | packets}} | mts-events | pss-events} | errors [vsan vsan-id] | events [vsan vsan-id] | mts-events | pss-events | snmp-events | trace [vsan vsan-id]}
no debug fabric-binding {all | efmd {db-events | errors | merge {errors | events | packets}} | mts-events | pss-events} | errors [vsan vsan-id] | events [vsan vsan-id] | mts-events | pss-events | snmp-events | trace [vsan vsan-id]}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fabric-binding all command is issued:
switch# debug fabric-binding alldebug fc-tunnel
To enable debugging for the Fibre Channel tunnel feature, use the debug fc-tunnel command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fc-tunnel {all | errors | external-events | ha | label-update | mts {pkt | pkthdr} {both | rx | tx} | pss | route-update [vsan vsan-id] | rsvp-messages [tunnel tunnel-id | vsan vsan-id] | state-machine}
no debug fc-tunnel {all | errors | external-events | ha | label-update | mts {pkt | pkthdr} {both | rx | tx} | pss | route-update [vsan vsan-id] | rsvp-messages [tunnel tunnel-id | vsan vsan-id] | state-machine}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fc-tunnel all command is issued:
switch# debug fc-tunnel alldebug fc2
To enable debugging for the FC2 feature, use the debug fc2 command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fc2 {credit |
error [fcid fcid [interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]]
flag |
flow [fcid fcid [interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | (interface fc type number | vsan vsan-id) |
frame |
loopback |
pkt {both | tx | rx} [bytes bytes | fcid fcid [bytes bytes | interface {fc slot/port | fcip port} [bytes bytes | pkts pkts [bytes bytes]] | pkts pkts [bytes bytes] | vsan vsan-id [bytes bytes | interface {fc slot/port | fcip port} [bytes bytes | pkts pkts [bytes bytes]]] |
pkthdr {both | tx | rx} [bytes bytes | fcid fcid [bytes bytes | interface {fc slot/port | fcip port} [bytes bytes | pkts pkts [bytes bytes]] | pkts pkts [bytes bytes] | vsan vsan-id [bytes bytes | interface {fc slot/port | fcip port} [bytes bytes | pkts pkts [bytes bytes]]] |
rdl |
rxhdrhistory [fcid fcid [interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]]
txhdrhistory [fcid fcid [interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]]}no debug fc2 {credit |
error [fcid fcid [interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]]
flag |
flow [fcid fcid [interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | (interface fc type number | vsan vsan-id) |
frame |
loopback |
pkt {both | tx | rx} [bytes bytes | fcid fcid [bytes bytes | interface {fc slot/port | fcip port} [bytes bytes | pkts pkts [bytes bytes]] | pkts pkts [bytes bytes] | vsan vsan-id [bytes bytes | interface {fc slot/port | fcip port} [bytes bytes | pkts pkts [bytes bytes]]] |
pkthdr {both | tx | rx} [bytes bytes | fcid fcid [bytes bytes | interface {fc slot/port | fcip port} [bytes bytes | pkts pkts [bytes bytes]] | pkts pkts [bytes bytes] | vsan vsan-id [bytes bytes | interface {fc slot/port | fcip port} [bytes bytes | pkts pkts [bytes bytes]]] |
rdl |
rxhdrhistory [fcid fcid [interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]]
txhdrhistory [fcid fcid [interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]] | interface {fc slot/port | fcip port} | vsan vsan-id [interface {fc slot/port | fcip port}]]}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
If FSPF receives a bad FC2 packet analyze the output of the debug fc2 pkt command.
Examples
The following example displays the system output when the debug fc2 error vsan 1 command is issued:
switch1# debug fc2 error vsan 1debug fc2d
To enable debugging for the FC2 feature, use the debug fc2 command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fc2 {all | bypass ficon_mgr | demux [vsan vsan-id] | deque | error | event [vsan vsan-id] | ha [vsan vsan-id] | trace [detail] [vsan vsan-id] | warning [vsan vsan-id]}
no debug fc2 {all | bypass ficon_mgr | demux [vsan vsan-id] | deque | error | event [vsan vsan-id] | ha [vsan vsan-id] | trace [detail] [vsan vsan-id] | warning [vsan vsan-id]}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(4).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fc2d all command is issued:
switch1# debug fc2d all2004 Mar 29 22:57:25 fc2d: fu_fsm_execute_all: match_msg_id(0), log_already_open (0)2004 Mar 29 22:57:25 fc2d: fu_fsm_execute_all: null fsm_event_list2004 Mar 29 22:57:25 fc2d: fu_fsm_engine_post_event_processing: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 6894921) droppeddebug fcc
To enable debugging for the Fibre Channel Congestion (FCC) function, use the debug fcc command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fcc {all | error [module slot] | event [module slot] |
mts [pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | tx | rx [numpkt range]}] | trace [module slot]}no debug fcc {all | error [module slot] | event [module slot] |
mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | tx | rx [numpkt range]}} | trace [module slot]}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fcc all command is issued:
switch# debug fcc alldebug fcdomain
To enable debugging for the fcdomain feature, use the debug fcdomain command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fcdomain {all | critical | error |
fc {pkt | pkthdr} {both | rx | tx} [interface type number [vsan vsan-id] | vsan vsan-id] |
ipc {pkt | pkthdr} {both | rx [node range | opcode range | sap range] | tx} |
memory | notify | phase}no debug fcdomain {all | critical | error |
fc {pkt | pkthdr} {both | rx | tx} [interface type number [vsan vsan-id] | vsan vsan-id] |
ipc {pkt | pkthdr} {both | rx [node range | opcode range | sap range] | tx} |
memory | notify | phase}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fcdomain critical command is issued:
switch# debug fcdomain criticalJan 27 07:04:31 fcdomain: Src: 0x00000501/6243 Dst: 0x00000501/14 ID: 0x0005BF41 Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0005BF41 HA_SEQNO:0x00000000 TS: 0x183C4D027F4A3Jan 27 07:04:31 fcdomain: 00 00 00 00 68 00 00 00 00 00 00 00 00 00 00 00Jan 27 07:04:31 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Jan 27 07:04:31 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FFJan 27 07:04:31 fcdomain: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00Jan 27 07:04:31 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...The following example displays the system output when the debug fcdomain error command is issued:
switch# debug fcdomain errorJan 27 07:05:29 fcdomain: Src: 0x00000501/6245 Dst: 0x00000501/14 ID: 0x0005BF7E Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0005BF7E HA_SEQNO:0x00000000 TS: 0x183D5E63C081AJan 27 07:05:29 fcdomain: 00 00 00 00 64 00 00 00 00 00 00 00 00 00 00 00Jan 27 07:05:29 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Jan 27 07:05:29 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FFJan 27 07:05:29 fcdomain: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00...The following example displays the system output when the debug fcdomain ipc pkthdr both command is issued:
vegas2# debug fcdomain ipc pkthdr bothApr 8 20:44:38 fcdomain: Src: 0x00000501/3883 Dst: 0x00000501/14 ID: 0x00038E1D Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x00038E1D HA_SEQNO:0x00000000 TS: 0x5DD9B14EA3AA REJ:0Apr 8 20:44:38 fcdomain: 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00Apr 8 20:44:38 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 8 20:44:38 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FFApr 8 20:44:38 fcdomain: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00Apr 8 20:44:38 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 8 20:44:38 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...Apr 8 20:44:38 fcdomain: Src: 0x00000501/3883 Dst: 0x00000501/14 ID: 0x00038E20 Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x00038E20 HA_SEQNO:0x00000000 TS: 0x5DD9B186CCEB REJ:0Apr 8 20:44:38 fcdomain: 00 00 00 00 07 00 00 00 00 00 00 00 00 00 00 00Apr 8 20:44:38 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 8 20:44:38 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FFApr 8 20:44:38 fcdomain: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00Apr 8 20:44:38 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 8 20:44:38 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00...Related Commands
show fcdomain domain-list
Displays current domains in the fabric.
fcdomain
Enables fcdomain features.
debug fcfwd
To enable debugging for the Fibre Channel forwarding feature, use the debug fcfwd command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fcfwd {flogimap | idxmap | pcmap | sfib | spanmap} {error | event | trace} [module slot | vsan vsan-id [module slot]]
no debug fcfwd {flogimap | idxmap | pcmap | sfib | spanmap} {error | event | trace} [module slot | vsan vsan-id [module slot]]
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fcfwd error command is issued:
switch# debug fcfwd errordebug fcns
To enable debugging for name server registration, use the debug fcns command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fcns {all | errors | events {mts | query | register}} [vsan vsan-id]
no debug fcns {all | errors | events {mts | query | register}} [vsan vsan-id]
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fcns events register vsan 99 command is issued:
switch# debug fcns events register vsan 99Feb 17 04:42:54 fcns: vsan 99: Got Entry for port-id 27800Feb 17 04:42:54 fcns: vsan 99: Registered port-name 36a4078be0000021 for port-id 780200Feb 17 04:42:54 fcns: vsan 99: Registered node-name 36a4078be0000020 for port-id 780200...debug fcs
To enable debugging for the fabric configuration server, use the debug fcs command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fcs {all | discovery events | errors [vsan vsan-id] | ess-events [vsan vsan-id] |
mts events {brief | detail} | pss events | queries events [vsan vsan-id] |
registrations events [vsan vsan-id] | rscn events [vsan vsan-id] | snmp events}no debug fcs {all | discovery events | errors [vsan vsan-id] | ess-events [vsan vsan-id] |
mts events {brief | detail} | pss events | queries events [vsan vsan-id] |
registrations events [vsan vsan-id] | rscn events [vsan vsan-id] | snmp events}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fcs all command is issued:
switch# debug fcs alldebug fcsp-mgr
To enable debugging for the Fibre Channel Security Protocol (FC-SP) manager, use the debug fcsp-mgr command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fcsp-mgr {all | critical | datastructure | dhchap | error | event-gen | fc2 | fsm | general | ha | init | level1 | level2 | level3 | level4 | level5 | message | mts | notify | trace}
no debug fcsp-mgr {all | critical | datastructure | dhchap | error | event-gen | fc2 | fsm | general | ha | init | level1 | level2 | level3 | level4 | level5 | message | mts | notify | trace}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fcs all command is issued:
switch# debug fcsp-mgr all2004 Mar 29 23:33:56 fcsp-mgr: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)2004 Mar 29 23:33:56 fcsp-mgr: fu_fsm_execute_all: null fsm_event_list2004 Mar 29 23:33:56 fcsp-mgr: fu_fsm_engine_post_event_processing: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 7061762) droppeddebug fdmi
To enable debugging for the Fabric-Device Management Interface (FDMI) feature, use the debug fdmi command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fdmi {all | errors | fdmi-messages [vsan vsan-id] | ha | mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | tx | rx [numpkt range]}} | pss | trace}
no debug fdmi {all | errors | fdmi-messages [vsan vsan-id] | ha | mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | tx | rx [numpkt range]}} | pss | trace}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fdmi all command is issued:
switch# debug fdmi alldebug ficon
To enable debugging for the FI-bre CON-nection (FICON) interface capabilities, use the debug ficon command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ficon {all | bypass {acl | esa | file | pm | postcheck | precheck} |
control-device {all | bypass ficon_mgr | demux [vsan vsan-id] | deque | error | event [vsan vsan-id] | ficon_mgr | ha [vsan vsan-id] | demux [vsan vsan-id] | sb3 {error | flow} trace [detail] [vsan vsan-id] | warning [vsan vsan-id]} |
error | event | file-trace | ha | max-port-number ports | pss-trace |
stat {all | demux [vsan vsan-id] | deque | error | event [vsan vsan-id] | ha [vsan vsan-id] | trace [detail] [vsan vsan-id] | warning [vsan vsan-id]} |
timer | trace}no debug ficon {all | bypass {acl | esa | file | pm | postcheck | precheck} |
control-device {all | bypass ficon_mgr | demux [vsan vsan-id] | deque | error | event [vsan vsan-id] | ficon_mgr | ha [vsan vsan-id] | demux [vsan vsan-id] | sb3 {error | flow} trace [detail] [vsan vsan-id] | warning [vsan vsan-id]} |
error | event | file-trace | ha | max-port-number port | pss-trace |
stat {all | demux [vsan vsan-id] | deque | error | event [vsan vsan-id] | ha [vsan vsan-id] | trace [detail] [vsan vsan-id] | warning [vsan vsan-id]} |
timer | trace}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(2).
Usage Guidelines
FICON must be enabled on the switch to use this command.
Examples
The following example displays the system output when the debug ficon all command is issued:
switch# debug ficon alldebug flogi
To enable debugging for the fabric login (FLOGI) feature, use the debug flogi command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug flogi {action [interface type number | vsan vsan-id] |
all |
bypass {acl | dm | dpvm | fcsp | lcp | npiv | ns | pl | pm | pmvc | rib| vsan_mgr | zs} |
demux [interface type number | vsan vsan-id] |
error |
event [interface type number | vsan vsan-id] |
ha [interface type number | vsan vsan-id] |
init [interface type number | vsan vsan-id] |
timers [interface type number | vsan vsan-id] |
trace [interface type number | vsan vsan-id] |
warning}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug flogi all command is issued:
switch# debug flogi allApr 9 22:44:08 flogi: fs_demux: msg consumed by sdwrap_process msgApr 9 22:44:08 flogi: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)Apr 9 22:44:08 flogi: fu_fsm_execute_all: null fsm_event_listApr 9 22:44:08 flogi: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 67690) droppedThe following example displays the system output when the debug flogi event command is issued:
switch# debug flogi eventApr 10 00:07:16 flogi: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)Apr 10 00:07:16 flogi: fu_fsm_execute_all: null fsm_event_listApr 10 00:07:16 flogi: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 71314) droppedThe following example displays the system output when the debug flogi trace command is issued:
switch# debug flogi traceApr 10 00:42:36 flogi: fs_genport_vsan_hash_fn: key: 0x1 index: 0x1Apr 10 00:42:36 flogi: fs_mts_hdlr_fs_flogo: FLOGI HOLD(0x8122144) refcnt:3Apr 10 00:42:36 flogi: fs_clear_all_outstanding_responses_for_flogi: FLOGI FREE(a07e00300500252b) refcnt:3debug fm
To enable feature manager debugging, use the debug fm command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fm {error | flow}
no debug fm {error | flow}
Syntax Description
error
Enables debugging for feature manager error conditions.
flow
Enables debugging for the feature manager flow.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fm flow command is issued:
switch# debug fm flowdebug fspf
To enable debugging for the FSPF feature, use the debug fspf command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug fspf {all [interface type number] [vsan vsan-id] |
database [interface type number] [vsan vsan-id |
error |
event [interface type number] [vsan vsan-id] |
fc {pkt | pkthdr} {both | tx | rx} [interface type number] [vsan vsan-id] |
flood [interface type number] [vsan vsan-id] |
ha [interface type number] [vsan vsan-id] |
mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | rx [numpkt range] | tx}} |
retrans [interface type number] [vsan vsan-id] |
route |
timer}no debug fspf {all [interface type number] [vsan vsan-id] |
database [interface type number] [vsan vsan-id |
error |
event [interface type number] [vsan vsan-id] |
fc {pkt | pkthdr} {both | tx | rx} [interface type number] [vsan vsan-id] |
flood [interface type number] [vsan vsan-id] |
ha [interface type number] [vsan vsan-id] |
mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | rx [numpkt range] | tx}} |
retrans [interface type number] [vsan vsan-id] |
route |
timer}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
If you receive bad packets on an interface, use the debug fc pkt command.
If you receive an error in processing a packet on an interface in VSAN, turn on debug fspf error to get more information. Make sure there is no misconfiguration of FSPF parameters on the two ends of the interface. Also issue the debug fspf fc pkt command for the specific interface.
If you receive an error in flooding the local LSR in a VSAN issue the debug fspf flood and debug fspf error commands. If error is reported in transmitting packet check if interface is up and turn on debug fc2 error.
If you receive an error in processing a timer event for the interface in a VSAN, issue the debug fspf error command.
If you receive an error in processing due to a wrong MTS message, use the debug fspf mts pkt and debug fspf error commands.
If you receive an error when interacting with RIB, use the debug fspf route command along with the RIB debug traces.
If you receive an error in computing routes for VSANs, issue the debug fspf error and the debug fspf route commands.
If you receive an error due to the interface being stuck in a state other than FULL, use the debug fspf event and debug fspf fc pkt commands on the interfaces involved.
Examples
The following example displays the system output when the debug fspf all command is issued:
switch1# debug fspf allApr 5 11:50:01 fspf: Wrong hello interval for packet on interface 100f000 in VSAN 1Apr 5 11:50:04 fspf: Error in processing hello packet , error code = 4debug hardware arbiter
To configures debugging for the hardware arbiter driver, use the debug hardware arbiter command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug hardware arbiter {error | flow} [group number]}
no debug hardware arbiter {error | flow} [group number]}
Syntax Description
error
Enables debugging for hardware arbiter kernel errors.
flow
Enables debugging for hardware arbiter kernel flow.
group number
Restricts debugging to the specified group. The range is 0 to 17.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug hardware arbiter error group command is issued:
switch# debug hardware arbiter error group 1debug idehsd
To enable IDE hot swap handler debugging, use the debug idehsd command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug idehsd {cmd dbglevel [debug-level] | error | flow}
no debug idehsd {cmd dbglevel [debug-level] | error | flow}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug idehsd cmd dbglevel command is issued:
switch# debug idehsd cmd dbglevel 5set debug level to 5 succeededdebug ilc_helper
To enable ILC helper debugging, use the debug ilc_helper command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ilc_helper {all | errors | events | info}
no debug ilc_helper {all | errors | events | info}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug ilc_helper all command is issued:
switch# debug ilc_helper alldebug ipacl
To enable IP ACL debugging, use the debug ipacl command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ipacl {all | error | event | trace}
no debug ipacl {all | error | event | trace}
Syntax Description
all
Enables debugging for all IP ACL features.
error
Enables debugging for IP ACL error conditions.
event
Enables debugging for the IP ACL events.
trace
Enables debugging for IP ACL trace.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug ipacl all command is issued:
switch# debug ipacl alldebug ipconf
To enable IP configuration debugging, use the debug ipconf command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ipconf {all | errors | events | info | pss}
no debug ipconf {all | errors | events | info | pss}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug ipconf all command is issued:
switch# debug ipconf alldebug ipfc
To enable IPFC debugging, use the debug ipfc command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ipfc {all | errors | events | info | kernel {errors | events}}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug ipfc kernel errors command is issued:
switch# debug ipfc kernel errorsdebug ips
To enable debugging for the IP storage (IPS) manager, use the debug ips command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ips {acl {flow | flow-detail} | all | demux | error | flow {ethernet | fcip} | fsm | ha | init | iscsi {config | config-detail | flow | flow-detail | msgs} | isns {config | config-detail | error | flow | flow-detail | msgs | packet} | show_all | upgrade}
no debug ips {acl {flow | flow-detail} | all | demux | error | flow {ethernet | fcip} | fsm | ha | init | iscsi {config | config-detail | flow | flow-detail | msgs} | isns {config | config-detail | error | flow | flow-detail | msgs | packet} | show_all | upgrade}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug ips show_all command is issued:
switch# debug ips show_allIPS Manager: iSCSI Trace Detail debugging is ondebug klm
To enable kernel loadable module parameter debugging, use the debug klm command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug klm {fc2 {cpuhog seconds | flag flags} | scsi-target {driver | error [vsan vsan-id] [fcid fc-id] | flag flags | flow [vsan vsan-id] [fcid fc-id] | snmp | syscall} | sdip {all | error | flow | warning}}
no debug klm {fc2 {cpuhog seconds | flag flags} | scsi-target {driver | error [vsan vsan-id] [fcid fc-id] | flag flags | flow [vsan vsan-id] [fcid fc-id] | snmp | syscall} | sdip {all | error | flow | warning}}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug klm scsi-target driver command is issued:
switch# debug klm scsi-target driverdebug license
To enable licensing debugging, use the debug license command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug license {all | errors | event s | mts}
no debug license {all | errors | events | mts}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug license all command is issued:
switch# debug license alldebug logfile
To direct the output of the debug commands to a specified file, use the debug logfile command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug logfile filename [size bytes]
Syntax Description
filename
Assigns the name of the log file. Maximum length is 80 characters.
size bytes
Specifies the logfile size in bytes. The range is 4096 to 4194304.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
Use this command to log debug messages to a special log file. This file is more secure and easier to process than sending the debug output to the console.
When you use the debug logfile command to create a log file, the file is automatically created in the log: directory on the supervisor module unless you specify a different path.
For example, using the debug logfile command to created a log file named captureDebug, you must enter the dir log://sup-local/? command to find the log file you created. Following example shows you how to find the log file created.
switch# debug logfile captureDebugswitch# dir log://sup-local/?log: Enter URL "log:[//<module-number>]/<filename>"log://sup-local/dmesglog://sup-local/messageslog://sup-local/captureDebugswitch# dir log://sup-local/Examples
The following example redirects the output of the debug commands to the file named sample.
switch# debug logfile sampleThe following example assigns the log file size for the file named sample.
switch# debug logfile sample size 410000debug mcast
To enable debugging for multicast definitions, use the debug mcast command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug mcast {all | error [vsan vsan-id] [interface fc slot/port] | event [vsan vsan-id] [interface fc slot/port] | mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | rx [numpkt range] | tx}} | trace [vsan vsan-id] [interface fc slot/port]]
no debug mcast {all | error [vsan vsan-id] [interface fc slot/port] | event [vsan vsan-id] [interface fc slot/port] | mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | rx [numpkt range] | tx}} | trace [vsan vsan-id] [interface fc slot/port]]
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug mcast all command is issued:
switch# debug mcast alldebug mip
To enable debugging for multiple IP (MIP) kernel drivers, use the debug mip command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug mip {errors | events}
no debug mip {errors | events}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug mip errors command is issued:
switch# debug mip errorsdebug module
To enable debugging for switching or service modules, use the debug module command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug module {all | error [module slot] | event | ha | no-powerdown | trace [module slot]}
no debug module {all | error [module slot] | event | ha | no-powerdown | trace [module slot]}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug fcs all command is issued:
switch# debug fcs allApr 28 19:23:20 module: fu_fsm_execute: (ID(5): Slot 4, node 0x0402)Apr 28 19:23:20 module: current state [LCM_ST_LC_ONLINE]Apr 28 19:23:20 module: current event [LCM_EV_LCM_HEARTBEAT_TIMEOUT]Apr 28 19:23:20 module: next state [LCM_ST_LC_ONLINE]Apr 28 19:23:20 module: fu_add_pss_data: adding data for key <8, 0x3300000000000004> to the pss runtime service add data listApr 28 19:23:20 module: fu_add_pss_data: added key <8, 0x3300000000000004> data...debug ntp
To enable debugging for the NTP module, use the debug ntp command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ntp {errors | info}
no debug ntp {errors | info}
Syntax Description
errors
Enables debugging for NTP error conditions.
info
Enables debugging for NTP information and events.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug ntp errors command is issued:
switch# debug ntp errorsdebug platform
To enable debugging for the platform manager, use the debug platform command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug platform {all [fc_id fc-id] | error [module slot] | flow [module slot] | fsm | ha | hitless |
mts {pkt | pkthdr} {tx | rx} | nopowerdown | supervisor-reset}no debug platform {all [fc_id fc-id] | error [module slot] | flow [module slot] | fsm | ha | hitless |
mts {pkt | pkthdr} {tx | rx} | nopowerdown | supervisor-reset}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug platform all command is issued:
switch# debug platform alldebug port
To enable debugging for ports, use the debug port command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug port {all | bypass {acl_manager | domain_manager | fcsp | ficon | fport_server | lcp | loopback_diag | port_channel_mgr | port_lock | qos_mgr | span | switch_wwn | vsan_mgr | wwn_mgr | xbar_mgr | zone_server} | error | event [interface type number | module slot] | ha [interface type number | module slot] | trace [interface type number | module slot]}
no debug port {all | bypass {acl_manager | domain_manager | fcsp | ficon | fport_server | lcp | loopback_diag | port_channel_mgr | port_lock | qos_mgr | span | switch_wwn | vsan_mgr | wwn_mgr | xbar_mgr | zone_server} | error | event [interface type number | module slot] | ha [interface type number | module slot] | trace [interface type number | module slot]}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug port all command is issued:
switch# debug port allApr 10 00:49:38 port: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)Apr 10 00:49:38 port: fu_fsm_execute_all: null fsm_event_listApr 10 00:49:38 port: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 40239) droppedThe following example displays the system output when the debug port event command is issued:
switch# debug port eventApr 10 15:30:35 port: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)Apr 10 15:30:35 port: fu_fsm_execute_all: null fsm_event_listApr 10 15:30:35 port: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 7002)droppedswitch# Apr 10 15:30:35 port: fu_priority_select: - setting fd[3] for select call - setting fd[5] for select call - setting fd[6] for select callApr 10 15:30:35 port: fu_priority_select_select_queue: round credit(16)Apr 10 15:30:35 port: curr_q - FU_PSEL_Q_CAT_FD, usr_q_info(32), fd(5), priority(3), credit(2), emptyApr 10 15:30:35 port: fu_priority_select: returning FU_PSEL_Q_CAT_MTS queue, fd(3), usr_q_info(8)debug port-channel
To enable debugging for PortChannels, use the debug port-channel command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug port-channel {all | error | event | ha | trace | warning}
no debug port-channel {all | error | event | ha | trace | warning}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug port-channel all command is issued:
switch# debug port-channel alldebug qos
To enable debugging for quality of Service (QoS), use the debug qos command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug qos {all [interface fc slot/port] | detail | errors supervisor | flow | trace}
no debug qos {all [interface fc slot/port] | detail | errors supervisor | flow | trace}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug qos all command is issued:
switch# debug qos alldebug radius
To enable debugging for boot variables, use the debug radius command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug radius {aaa-request | aaa-request-lowlevel | all | config | config-lowlevel}
no debug radius {aaa-request | aaa-request-lowlevel | all | config | config-lowlevel}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(1).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug radius config-lowlevel command is issued:
switch# debug radius config-lowlevelNov 20 06:36:42 radius: radius_new_debug_conf_open: entering...Nov 20 06:36:42 radius: radius_new_conf_close: entering...Nov 20 06:36:42 radius: radius_new_conf_close: returning 0Nov 20 06:36:42 radius: radius_new_enable_info_config: entering for Radius Daemon debugNov 20 06:36:42 radius: radius_new_debug_conf_open: entering...Nov 20 06:36:42 radius: radius_new_debug_conf_open: exitingNov 20 06:36:42 radius: radius_new_enable_info_config: SET_REQ for Radius Daemon debug with 1Nov 20 06:36:42 radius: radius_new_enable_info_config: SET_REQ done for Radius Daemon debug with 1Nov 20 06:36:42 radius: radius_new_enable_info_config: got back the return value of configuration operation:successNov 20 06:36:42 radius: radius_new_debug_conf_close: entering...Nov 20 06:36:42 radius: radius_new_debug_conf_close: returning 0Nov 20 06:36:42 radius: radius_new_enable_info_config: exiting for Radius Daemon debugdebug rd-reg
To enable debugging for the list of devices using the read-register feature, use the debug rd-reg command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug rd-reg [device-name | register address]
Syntax Description
device-name
Specifies the device name for the required device.
register address
Specifies the register address for the required device.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug rd-reg abc command is issued:
switch# debug rd-reg abcdebug rdl errors
To enable debugging for RDL errors, use the debug rdl errors command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug rdl errors
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug rdl errors command is issued:
switch# debug rdl errorsdebug rib
To enable debugging for the routing information base (RIB) feature, use the debug rib command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug rib {all | error | event | trace}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
If a RIB operation is ignored or not supported, then issue the debug rib all command to find out more details.
Examples
The following example displays the system output when the debug rib error command is issued:
switch# debug rib errordebug rlir
To enable RLIR debugging, use the debug rlir command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug rlir {all | errors | events | mts-errors | mts-events}
no debug rlir {all | errors | events | mts-errors | mts-events}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug rlir all command is issued:
switch# debug rlir alldebug rscn
To enable debugging for the registered state change notification (RSCN) feature, use the debug rscn command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug rscn {all | errors | events | mts-errors | mts-events} [vsan vsan-id]
no debug rscn {all | errors | events | mts-errors | mts-events} [vsan vsan-id]
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug rscn errors command is issued:
switch# debug rscn errorsdebug scsi-target
To enable debugging for SCSI targets, use the debug scsi-target command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug scsi-target {error | flow}
no debug scsi-target {error | flow}
Syntax Description
error
Enables debugging for SCSI target daemon error conditions.
flow
Enables debugging for the SCSI target flow.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug scsi-target flow command is issued:
switch# debug scsi-target flowApr 28 21:11:52 vhbad: vhba_mts_handler: sdwrap_dispatch: retval:0Apr 28 21:11:54 vhbad: vhbad_handle_timeout: timer:1 context:(nil)Apr 28 21:12:06 vhbad: vhba_mts_handler: sysmgr_dispatch: retval:-1debug security
To enable debugging for the security and accounting features, use the debug security command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug security {all | events | mts | radius}
no debug security {all | events | mts | radius}
Syntax Description
all
Enables debugging for all security features.
events
Enables debugging for security events.
mts
Enables debugging for security MTS packets.
radius
Enables debugging for RADIUS events.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug security radius command is issued:
switch# debug security radiusMar 5 00:51:13 securityd: RADIUS is enabled, hence it will be tried first for CHAP authenticationMar 5 00:51:13 securityd: reading RADIUS configurationMar 5 00:51:13 securityd: opening radius configuration for group:defaultMar 5 00:51:13 securityd: opened the configuration successfullyMar 5 00:51:13 securityd: GET request for RADIUS global configMar 5 00:51:13 securityd: got back the return value of global radius configuration operation:successMar 5 00:51:13 securityd: closing RADIUS pss configurationMar 5 00:51:13 securityd: opening radius configuration for group:defaultdebug sensor
To enable debugging for the sensor manager, use the debug sensor command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug sensor {demux | deque | error | info | init}
no debug sensor {demux | deque | error | info | init}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
Use this command to debug sensor manager events and information.
Examples
The following example displays the system output when the debug sensor info command is issued:
switch# debug sensor infoRelated Commands
show environment temperature
Displays current temperature threshold settings and state.
debug snmp
To enable debugging for the SNMP manager, use the debug snmp command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug snmp
{all |
errors |
mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | rx [numpkt range] | tx}}
| pkt-dump |
trace {trace-entryexit | trace-stub}}no debug snmp
{all |
errors |
mts {pkt {both | rx [node range | opcode range | sap range] | tx} | pkthdr {both | rx [numpkt range] | tx}}
| pkt-dump |
trace [trace-entryexit | trace-stub]}Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug snmp trace command is issued:
switch# debug snmp traceApr 29 16:03:34 snmpd[1177]: SDWRAP message Successfully processeddebug span
To enable SPAN debugging, use the debug span command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug span {all | buffer-size bytes | error | event | trace | warning}
no debug span {all | error | event | trace | warning}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug span all command is issued:
switch# debug span allApr 29 16:06:44 span: span_demux: msg consumed by sdwrap_process msgApr 29 16:06:44 span: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)Apr 29 16:06:44 span: fu_fsm_execute_all: null fsm_event_listApr 29 16:06:44 span: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 2548887) droppedApr 29 16:06:48 span: fu_priority_select: - setting fd[3] for select callApr 29 16:06:48 span: fu_priority_select_select_queue: round credit(12)Apr 29 16:06:48 span: curr_q - FU_PSEL_Q_CAT_CQ, usr_q_info(4), priority(7), credit(6), emptyApr 29 16:06:48 span: fu_priority_select: returning FU_PSEL_Q_CAT_MTS queue, fd(3), usr_q_info(2)Apr 29 16:06:48 span: span_get_data_from_mts_q dequeued mts msg (26e525), MTS_OPC_DEBUG_WRAP_MSGdebug system health
To enable system health monitoring debugging, use the debug system health command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug system health {all | asic-counters | battery-charger | cache-disk | eobc | error | event | external-loopback | failure-analysis | fc2 | ha | inband | loopback | mgmt | misc | mts | pss | serdes | special | trace | xipc}
no debug system health {all | asic-counters | battery-charger | cache-disk | eobc | error | event | external-loopback | failure-analysis | fc2 | ha | inband | loopback | mgmt | misc | mts | pss | serdes | special | trace | xipc}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug system health command is issued:
switch# debug system health alldebug tacacs+
To enable debugging for boot variables, use the debug tacacs+ command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug tacacs+ {aaa-request | aaa-request-lowlevel | all | config | config-lowlevel}
no debug tacacs+ {aaa-request | aaa-request-lowlevel | all | config | config-lowlevel}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.3(1).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug tacacs+ config-lowlevel command is issued:
switch# debug tacacs+ config-lowlevelNov 20 06:39:44 tacacs: tacacs_debug_conf_open: entering...172.22.94.252# Nov 20 06:39:44 tacacs: tacacs_debug_conf_open: exitingNov 20 06:39:44 tacacs: tacacs_conf_close: entering...Nov 20 06:39:44 tacacs: tacacs_conf_close: returning 0Nov 20 06:39:44 tacacs: tacacs_enable_info_config: entering for TACACS+ Daemon debugNov 20 06:39:44 tacacs: tacacs_debug_conf_open: entering...Nov 20 06:39:44 tacacs: tacacs_debug_conf_open: exitingNov 20 06:39:44 tacacs: tacacs_enable_info_config: SET_REQ for TACACS+ Daemon debug with 1Nov 20 06:39:44 tacacs: tacacs_enable_info_config: SET_REQ done for TACACS+ Daemon debug with 1Nov 20 06:39:44 tacacs: tacacs_enable_info_config: got back the return value of configuration operation:successNov 20 06:39:44 tacacs: tacacs_debug_conf_close: entering...Nov 20 06:39:44 tacacs: tacacs_debug_conf_close: returning 0Nov 20 06:39:44 tacacs: tacacs_enable_info_config: exiting for TACACS+ Daemon debugdebug tcap
To enable debugging the exception logger, use the debug tcap command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug tcap {demux | deque | error | info | init}
no debug tcap {demux | deque | error | info | init}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
Use this command to debug terminal capture utility events and information.
Examples
The following example displays the system output when the debug tcap demux command is issued:
switch# debug tcap demuxdebug tlport
To enable debugging for TL port interfaces, use the debug tlport command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug tlport {all | errors | events {fc2 {terminal | transit} | mts | pss}} [interface fc slot/port]
no debug tlport {all | errors | events {fc2 {terminal | transit} | mts | pss}} [interface fc slot/port]
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug tlport events pss command is issued:
switch# debug tlport events pssdebug ttyd
To enable TTYD debugging, use the debug ttyd command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug ttyd {all | errors | events}
no debug ttyd {all | errors | events}
Syntax Description
all
Enables debugging for all TTYD features.
errors
Enables debugging for TTYD error conditions.
events
Enables debugging for TTYD events.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug ttyd events command is issued:
switch# debug ttyd eventsdebug vni
To enable debugging for a virtual network interface (VNI), use the debug vni command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug vni {all | errors | events | info | pss}
no debug vni {all | errors | events | info | pss}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug vni all command is issued:
switch# debug vni allApr 29 17:00:59 vni: Received MTS messageApr 29 17:00:59 vni: message not processed by system mgr library , so process it normal waydebug vrrp
To enable debugging for a Virtual Router Redundancy Protocol (VRRP), use the debug vrrp command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug vrrp {configuration | engine} {all | error | event | info}
no debug vrrp {configuration | engine} {all | error | event | info}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug vrrp engine all command is issued:
switch# debug vrrp engine allApr 29 17:35:58 vrrp_eng: fu_priority_select: - setting fd[7] for select call - setting fd[11] for select call - setting fd[12] for select call - setting fd [13] for select call - setting fd[15] for select callApr 29 17:35:58 vrrp_eng: fu_priority_select_select_queue: round credit(6)Apr 29 17:35:58 vrrp_eng: curr_q - FU_PSEL_Q_CAT_FD, usr_q_info(6), fd(15), priority(2), credit(1), emptyApr 29 17:35:58 vrrp_eng: fu_priority_select: returning FU_PSEL_Q_CAT_FD queue, fd(7), usr_q_info(3)Apr 29 17:35:58 vrrp_eng: heartbeat sentApr 29 17:35:58 vrrp_eng: message not processed by system mgr library , so process it normal waydebug vsan
To enable debugging for VSANs, use the debug vsan command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug vsan {all | global | ha | info | membership | mts}
no debug vsan {all | global | ha | info | membership | mts}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug vsan all command is issued:
switch# debug vsan alldebug wr-reg
To enable debugging for the list of devices using the write-register feature, use the debug wr-reg command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug wr-reg [device-name | register-address]
no debug wr-reg [device-name | register-address]
Syntax Description
device-name
Specifies the device name for the required device.
register-address
Specifies the register address for the required device.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug wr-reg command is issued:
switch# debug wr-regdebug wwn
To enable debugging for the world wide name (WWN) manager, use the debug wwn command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug wwn {all | detail | errors | flow | trace}
no debug wwn {all | detail | errors | flow | trace}
Syntax Description
all
Enables all WWN debug options.
detail
Enables all WWN output
error
Enables debugging for WWN error conditions.
flow
Enables flow-level WWN debug options.
trace
Enables debugging for WWN traces.
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug wwn all command is issued:
switch# debug wwn allApr 29 19:24:17 wwn: 53601-wwnm_sdwrap_dispatch:77|SDWRAP massage Successfully processedApr 29 19:24:17 wwn: Src: 0x00000601/5206 Dst: 0x00000601/46 ID: 0x002C7DE4 Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x002C7DE4 HA_SEQNO: 0x00000000 TS: 0x55D49A130243 REJ:0Apr 29 19:24:17 wwn: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 2E 00 00 00Apr 29 19:24:17 wwn: 53601-wwnm_unmask_sigalrm:1261|TRACE: FILE=_manager/wwnm/wwnm_utilities.cdebug xbar
To enable crossbar debugging (XBAR), use the debug xbar command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug xbar {all | demux | deque | error [module slot] | fsm [module slot] | ha [module slot] |
init | main}Syntax Description
Defaults
Enabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug xbar all command is issued:
switch# debug xbar allApr 29 19:48:34 xbar: its a sdwrap msg, fsm utils dropping the mts msgApr 29 19:48:34 xbar: fu_fsm_engine: (Error) SYSERR_FU_xx: 0x10, err_num (16) in demuxApr 29 19:48:34 xbar: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)Apr 29 19:48:34 xbar: fu_fsm_execute_all: null fsm_event_list...debug xbc
To enable crossbar client debugging (XBC), use the debug xbc command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug xbc {demux | deque | init | main}
no debug xbc {demux | deque | init | main}
Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
Use this command to debug crossbar client events and information.
Examples
The following example displays the system output when the debug xbc init command is issued:
switch# debug xbc initdebug zone
To enable debugging for zones, use the debug zone command in EXEC mode. When you finish using a debug command, remember to disable it with its specific no command (or use the no debug all command to turn off all debugging).
debug zone {all |
change {errors | events | packets} |
database {detail | errors | events} |
gs errors {errors | events | packets} |
lun-zoning {errors | events | packets} |
merge {errors | events | packets} |
mts notifications |
pss {errors | events} ||
read-only-zoning {errors | events | packets} |
tcam errors {errors | events | packets} |
transit {errors | events}} [vsan vsan-id]no debug zone {all |
change {errors | events | packets} |
database {detail | errors | events} |
gs errors {errors | events | packets} |
lun-zoning {errors | events | packets} |
merge {errors | events | packets} |
mts notifications |
pss {errors | events} ||
read-only-zoning {errors | events | packets} |
tcam errors {errors | events | packets} |
transit {errors | events}} [vsan vsan-id]Syntax Description
Defaults
Disabled.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example displays the system output when the debug zone all command is issued:
switch# debug zone all
