Cisco MDS 9000 Family Command Reference, Release 1.2(2a) - Debug Commands [Cisco MDS 9000 NX-OS and SAN-OS Software]

Table Of Contents

Debug Commands

debug all

debug bootvar

debug callhome

debug cdp

debug core

debug ethport

debug exceptionlog

debug fc2

debug fcc

debug fcdomain

debug fcfwd

debug fcns

debug fcs

debug flogi

debug fspf

debug hardware

debug idehsd

debug ipconf

debug ipfc

debug ips

debug logfile

debug mcast

debug mip

debug module

debug ntp

debug platform

debug port

debug port-channel

debug qos

debug rd-reg

debug rdl

debug rib

debug rscn

debug scsi-target

debug security

debug sensor

debug snmp

debug span

debug system

debug tcap

debug tlport

debug ttyd

debug vni

debug vrrp

debug vsan

debug wr-reg

debug wwn

debug xbar

debug xbc

debug zone

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 all

•debug bootvar

•debug callhome

•debug cdp

•debug core

•debug ethport

•debug exceptionlog

•debug fc2

•debug fcc

•debug fcdomain

•debug fcfwd

•debug fcns

•debug fcs

•debug flogi

•debug fspf

•debug hardware

•debug idehsd

•debug ipconf

•debug ipfc

•debug ips

•debug logfile

•debug mcast

•debug mip

•debug module

•debug ntp

•debug platform

•debug port

•debug port-channel

•debug qos

•debug rd-reg

•debug rdl

•debug rib

•debug rscn

•debug scsi-target

•debug security

•debug sensor

•debug snmp

•debug span

•debug system

•debug tcap

•debug tlport

•debug ttyd

•debug vni

•debug vrrp

•debug vsan

•debug wr-reg

•debug wwn

•debug xbar

•debug xbc

•debug zone

debug 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

None.

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 all
debug 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
Syntax Description

all

Enables all boot variable debug options.

errors

Enables debugging for boot variable errors.

events

Enables debugging for boot variable events.

info

Enables debugging for boot variable information.

pss

Enables debugging for boot variable PSS operations.

Defaults

None.

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 all
debug 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
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

None.

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 callhome events command is issued:
switch# debug callhome events
Apr  8 13:09:37 callhome: Src: 0x00000501/4065  Dst: 0x00000501/66  ID: 0x0004FA
05  Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0004FA05  HA_SEQNO:
0x00000000  TS: 0x8657D581CAE  REJ:0
Apr  8 13:09:37 callhome: 00 00 00 00 64 00 00 00 00 00 00 00 00 00 00 00
Apr  8 13:09:37 callhome: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr  8 13:09:37 callhome: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
...
The following example displays the system output when the debug callhome mts command is issued:
switch# debug callhome mts
Apr  8 13:09:42 callhome: Src: 0x00000501/4067  Dst: 0x00000501/66  ID: 0x0004FA
0D  Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0004FA0D  HA_SEQNO:
0x00000000  TS: 0x86708AFE37B  REJ:0
Apr  8 13:09:42 callhome: 00 00 00 00 06 00 00 00 00 00 00 00 00 00 00 00
Apr  8 13:09:42 callhome: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr  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: 0x0004FA
10  Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0004FA10  HA_SEQNO:
0x00000000  TS: 0x86708D6A974  REJ:0
Apr  8 13:09:42 callhome: 00 00 00 00 05 00 00 00 00 00 00 00 00 00 00 00
Apr  8 13:09:42 callhome: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr  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 ) ]
Syntax Description

all

Enables debugging for all CDP features.

errors

Enables debugging for CDP error conditions.

events

Enables debugging for CDP events.

mts

Enables debugging for CDP tx/rx MTS packets.

packets

Enables debugging for CDP tx/rx CDP packets.

pss

Enables debugging for all PSS related CDP events.

interface

Specifies debugging for the specified interface.

gigbitethernet slot-port

Specifies the Gigabit Ethernet interface slot and port.

mgmt 0

Specifies the management interface.

Defaults

None.

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 packets
Apr  8 21:22:34 cdp: Sent CDP packet, interface 0x2380000
Apr  8 21:22:34 cdp: Sent CDP packet, interface 0x2381000
Apr  8 21:22:35 cdp: Sent CDP packet, interface 0x2382000
Apr  8 21:22:35 cdp: Sent CDP packet, interface 0x2383000
Apr  8 21:22:51 cdp: Received CDP packet, interface 0x5000000
Apr  8 21:23:01 cdp: Sent CDP packet, interface 0x5000000
Apr  8 21:23:34 cdp: Sent CDP packet, interface 0x2380000
Apr  8 21:23:34 cdp: Sent CDP packet, interface 0x2381000
Apr  8 21:23:35 cdp: Sent CDP packet, interface 0x2382000
...
debug core

To enable core demon 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
Syntax Description

errors

Enables debugging for core demon error conditions.

flow

Enables debugging for the core demon flow.

Defaults

None.

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 flow 
debug 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) ]
Syntax Description

all

Enables debugging for all Ethernet port features.

error

Enables debugging for Ethernet port error conditions.

event

Enables debugging for Ethernet port events.

ha

Enables debugging for port high availability.

trace

Enables debugging for Ethernet port traces.

interface gigibetethernet slot-port

Specifies the slot and port of the Gigabit Ethernet interface.

module slot

Specifies the slot number of the module being debugged.

Defaults

None.

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 ehtport all 
debug 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
Syntax Description

demux

Enables debugging for the exception logger demux functions.

deque

Enables debugging for the exception logger deque function.

error

Enables debugging for exception logger errors.

flow

Enables debugging for the exception logger flow.

info

Enables debugging for exception logger information.

Defaults

None.

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 exceptionlog 
7), credit(3), empty
debug 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 type number | vsan vsan-id ) ] |
[ flag ] |
[ flow ( fcid fcid ) | (interface fc type number | vsan vsan-id ) ] |
[ frame ] |
[ loopback ] |
[ pkt (both | tx | rx) ( fcid fcid ) | (interface fc type number | vsan vsan-id ) ] |
[ pkthdr (both | tx | rx) ( fcid fcid ) | (interface fc type number | vsan vsan-id ) ] |
[ rdl ] |
[ rxhdrhistory (both | tx | rx) ( fcid fcid ) | (interface fc type number | vsan vsan-id ) ] |
[ txhdrhistory (both | tx | rx) ( fcid fcid ) | (interface fc type number | vsan vsan-id ) ]
Syntax Description

credit

Enables FC2 credit debugging.

error

Enables FC2 error debugging.

flag

Enables FC2 flags debugging.

flow

Enables FC2 flow debugging.

frame

Enables FC2 frame debugging.

loopback

Enables FC2 loopback debugging.

pkt

Enables FC packet debugging.

pkthdr

Enables FC header debugging.

rdl

Enables FC2 RDL debugging.

rxhdrhistory

Enables FC2 received header history debugging.

txhdrhistory

Enables FC2 transmitted header history debugging.

both

Enables debugging in both the transmit and receive directions.

tx

Enables debugging in the transmit direction,

rx

Enables debugging in the receive direction.

fcid fcid

Restricts debugging to the specified FCID.

interface fc type number

Restricts debugging to the specified interface.

vsan vsan-id

Restricts debugging to the specified VSAN.

Defaults

None.

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 1
debug 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 ] |
[ errors ( module slot ) ] |
[ events ( module slot ) ] |
[ mts { pkt both | tx | rx ( node range | opcode range | sap range ) } | { ( pkthdr both | tx | rx ( numpkt range ) } ]
[ trace ( module slot ) ]]
Syntax Description

all

Enables debugging for all FCC features.

errors

Enables debugging for FCC error conditions.

events

Enables debugging for FCC events.

mts

Enables debugging for FCC tx/rx MTS packets.

trace

Enables debugging for FCC traces.

module slot

Specifies the slot number of the module being debugged.

pkt

Enables debugging for FCC tx/rx FCC packets.

pkthdr

Enables debugging for FCC tx/rx FCC headers.

numpkt

Specifies the number of required packets

both

Specifies debugging in both the transmit and receive directions.

tx

Specifies debugging in the transmit direction,

rx

Specifies debugging in the receive direction.

node

Specifies the node for the packets in the receive direction.

opcode

Specifies the opcode for the packets in the receive direction.

sap

Specifies the sap for the packets in the receive direction.

range

Specifies the integer range from 1 to 4095.

Defaults

None.

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 all 
debug 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 | tx | rx) (interface type number | vsan vsan-id) ] |
[ipc (pkt | pkthdr) (both | tx | rx) (interface type number | vsan vsan-id) ] |
[memory] |
[notify] |
[phase]
Syntax Description

all

Enables debugging of all fcdomain parameters.

critical

Enables debugging of critical operations.

error

Enables debugging of error operation.

fc

Enables debugging of Fibre Channel Packets and Headers.

ipc

Enables debugging of IPC Packets and Headers.

pkt

Enables debugging of packets.

pkthdr

Enables debugging of headers.

both

Enables debugging in both the transmit and receive directions.

tx

Enables debugging in the transmit direction,

rx

Enables debugging in the receive direction.

interface type number

Specifies the interface to be debugged.

vsan vsan-id

Restricts debugging to the specified VSAN.

memory

Enables debugging of memory operations.

notify

Enables debugging of notifications

phase

Enables debugging of global phases

Defaults

None.

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 critical
Jan 27 07:04:31 fcdomain: Src: 0x00000501/6243  Dst: 0x00000501/14  ID: 0x0005BF
41  Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0005BF41  HA_SEQNO:
0x00000000  TS: 0x183C4D027F4A3
Jan 27 07:04:31 fcdomain: 00 00 00 00 68 00 00 00 00 00 00 00 00 00 00 00
Jan 27 07:04:31 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 27 07:04:31 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
Jan 27 07:04:31 fcdomain: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00
Jan 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 error
Jan 27 07:05:29 fcdomain: Src: 0x00000501/6245  Dst: 0x00000501/14  ID: 0x0005BF
7E  Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x0005BF7E  HA_SEQNO:
0x00000000  TS: 0x183D5E63C081A
Jan 27 07:05:29 fcdomain: 00 00 00 00 64 00 00 00 00 00 00 00 00 00 00 00
Jan 27 07:05:29 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 27 07:05:29 fcdomain: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
Jan 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 both
Apr  8 20:44:38 fcdomain: Src: 0x00000501/3883  Dst: 0x00000501/14  ID: 0x00038E
1D  Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x00038E1D  HA_SEQNO:
0x00000000  TS: 0x5DD9B14EA3AA  REJ:0
Apr  8 20:44:38 fcdomain: 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00
Apr  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: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
Apr  8 20:44:38 fcdomain: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00
Apr  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: 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: 0x00038E
20  Size: 252 [REQ] Opc: 182 (MTS_OPC_DEBUG_WRAP_MSG) RR: 0x00038E20  HA_SEQNO:
0x00000000  TS: 0x5DD9B186CCEB  REJ:0
Apr  8 20:44:38 fcdomain: 00 00 00 00 07 00 00 00 00 00 00 00 00 00 00 00
Apr  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: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
Apr  8 20:44:38 fcdomain: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00
Apr  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: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
...
Related Commands

Command

Description

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 error ( module slot | vsan vsan-id) | event ( module slot | vsan vsan-id) | trace ( module slot | vsan vsan-id) ] |
[ idxmap error ( module slot | vsan vsan-id) | event ( module slot | vsan vsan-id) | trace ( module slot | vsan vsan-id) ] |
[ pcmap error ( module slot | vsan vsan-id) | event ( module slot | vsan vsan-id) | trace ( module slot | vsan vsan-id) ] |
[ sfib error ( module slot | vsan vsan-id) | event ( module slot | vsan vsan-id) | trace ( module slot | vsan vsan-id) ] |
[ spanmap error ( module slot | vsan vsan-id) | event ( module slot | vsan vsan-id) | trace ( module slot | vsan vsan-id) ]
Syntax Description

flogimap

Enables flogimap debugging.

idxmap

Enables idxmap debugging.

pcmap

Enables pcmap debugging.

sfib

Enables sfib debugging.

spanmap

Enables spanmap debugging.

error

Enables debugging for FCC error conditions.

event

Enables debugging for FCC events.

trace

Enables debugging for FCC traces.

module slot

Specifies the slot number of the module being debugged.

vsan vsan-id

Restricts debugging to the specified VSAN.

Defaults

None.

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 error
debug 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 (vsan vsan-id ) ] |
[ errors (vsan vsan-id ) ] |
[ events mts (vsan vsan-id ) | query (vsan vsan-id ) | register (vsan vsan-id ) ]
Syntax Description

all

Enables debugging for all name server features.

errors

Enables debugging for name server error conditions.

events

Enables debugging for name server events.

mts

Enables debugging for name server tx/rx MTS packets.

query

Enables debugging for name server tx/rx CDP packets.

register

Enables debugging for name server PSS related events.

vsan vsan-id

Restricts debugging to the specified VSAN.

Defaults

None.

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 99
Feb 17 04:42:54 fcns: vsan 99: Got Entry for port-id 27800
Feb 17 04:42:54 fcns: vsan 99: Registered port-name 36a4078be0000021 for port-id 780200
Feb 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 (vsan vsan-id ) ] |
[ discovery events ] |
[ errors (vsan vsan-id ) ] |
[ mts events (brief | detail) ] |
[ pss events] |
[ queries events (vsan vsan-id )] |
[ registration events (vsan vsan-id ) ] |
[ rscn events (vsan vsan-id ) ] |
[ snmp events ]
Syntax Description

all

Enables debugging for all FCS features.

discovery events

Enables debugging for FCS discovery events.

errors

Enables debugging for FCS error conditions.

mts events

Enables debugging for FCS tx/rx MTS events.

brief

Provides brief information for each event.

detail

Provides detailed information for each event.

queries events

Enables debugging for FCS tx/rx events.

registration events

Enables debugging for FCS PSS related events.

rscn events

Enables debugging for FCS RSCN events.

snmp events

Enables debugging for FCS SNMP events.

vsan vsan-id

Restricts debugging to the specified VSAN.

Defaults

None.

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 all
debug 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 ] |
[ 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

action

Enables all FLOGI debug features.

all

Enables all FLOGI debug options.

demux

Enables FLOGI demux

error

Enables debugging for FLOGI error conditions.

event

Enables debugging for FLOGI FSMs and events.

ha

Enables debugging for FLOGI high availability.

init

Enables debugging of FLOGI addition, deletion, and initialization.

timer

Enables debugging for FLOGI message timers

trace

Enables debugging for FLOGI traces.

warning

Enables debugging for FLOGI warnings.

interface type number

Restricts debugging to the specified interface.

vsan vsan-id

Restricts debugging to the specified VSAN.

Defaults

None.

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 all
Apr  9 22:44:08 flogi: fs_demux: msg consumed by sdwrap_process msg
Apr  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_list
Apr  9 22:44:08 flogi: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 67690) dropped
The following example displays the system output when the debug flogi event command is issued:
switch# debug flogi event
Apr 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_list
Apr 10 00:07:16 flogi: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 71314) dropped
The following example displays the system output when the debug flogi trace command is issued:
switch# debug flogi trace
Apr 10 00:42:36 flogi: fs_genport_vsan_hash_fn: key: 0x1 index: 0x1
Apr 10 00:42:36 flogi: fs_mts_hdlr_fs_flogo: FLOGI HOLD(0x8122144) refcnt:3
Apr 10 00:42:36 flogi: fs_clear_all_outstanding_responses_for_flogi: FLOGI FREE(
a07e00300500252b) refcnt:3
debug 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 ] |
[ error (interface type number | vsan vsan-id ) ] |
[ 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 | pkthdr) (both | tx | rx) (interface type number | vsan vsan-id) ] |
[ retrans (interface type number | vsan vsan-id) ] |
[ route ] |
[ timer ]
Syntax Description

all

Enables debugging for all FSPF features.

database

Enables debugging for the FSPF database.

error

Enables debugging for FSPF error conditions.

events

Enables debugging for FSPF events.

fc

Enables debugging of Fibre Channel Packets and Headers.

ipc

Enables debugging of IPC Packets and Headers.

pkt

Enables debugging of packets.

pkthdr

Enables debugging of headers.

both

Enables debugging in both the transmit and receive directions.

tx

Enables debugging in the transmit direction,

rx

Enables debugging in the receive direction.

flood

Enables debugging for FSPF flooding events.

ha

Enables debugging for FSPF high availability.

mts

Enables debugging for FSPF tx/rx MTS events.

retrans

Enables debugging for FSPF retransmits.

route

Enables debugging for FSPF route computation.

timer

Enables debugging for FSPF timers.

interface type number

Restricts debugging to the specified interface.

vsan vsan-id

Restricts debugging to the specified VSAN.

Defaults

None.

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 all
Apr 5 11:50:01 fspf: Wrong hello interval for packet on interface 100f000 in VSAN 1
Apr 5 11:50:04 fspf: Error in processing hello packet , error code = 4
debug hardware

To configures debugging for the hardware kernel module parameters, use the debug hardware 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 ] |
[ sso flow | init | interrupt ]
Syntax Description

arbiter

Enables debugging for the hardware arbiter driver.

sso

Enables debugging for the SSO driver.

errors

Enables debugging for hardware kernel errors.

flow

Enables debugging for hardware flow errors

init

Enables debugging for hardware initialization.

interrupt

Enables debugging for hardware interrupts.

Defaults

None.

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 1
debug 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 ]
Syntax Description

cmd

Enables debugging for the IDE hot swap handler.

dbglevel debug-level

Specifies the debug level (0 to 8).

error

Enables debugging for IDE hot swap handler error conditions.

flow

Enables debugging for IDE hot swap handler flow.

Defaults

None.

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 5 
set debug level to 5 succeeded
debug 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
Syntax Description

all

Enables debugging for all IP configuration features.

errors

Enables debugging for IP configuration error conditions.

events

Enables debugging for IP configuration tx/rx MTS events.

info

Enables debugging for IP configuration information.

pss

Enables debugging for IP configuration PSS operations.

Defaults

None.

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 all
debug 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

all

Enables debugging for all IPFC features.

errors

Enables debugging for IPFC error conditions.

events

Enables debugging for IPFC tx/rx MTS events.

info

Enables debugging for IPFC n information.

kernel

Enables debugging for IPFC PSS operations.

errors

Enables debugging for IPFC kernel error conditions.

events

Enables debugging for IPFC kernel events.

Defaults

None.

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 errors
debug 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
[ all ] |
[ demux ]
[ error ] |
[ flow ( ethernet | fcip | iscsi | iscsi_detail ) ] |
[ fsm ] |
[ ha ] |
[ init ] |
[ show_all ] |
[ timers ]
[ warning ]
Syntax Description

all

Enables all IPS debug options.

demux

Enables IPS demux

error

Enables debugging for IPS error conditions.

flow

Enables debugging for the IPS flow.

ethernet

Restricts debugging to the Ethernet flow

fcip

Restricts debugging to the FCIP flow

iscsi

Restricts debugging to the iSCSI flow

iscsi_detail

Restricts debugging to a detailed iSCSI flow

fsm

Enables debugging for IPS FSM and events.

ha

Enables debugging for IPS high availability.

init

Enables debugging of IPS addition, deletion, and initialization.

show_all

Enables all debugging IPS manager flags.

timers

Enables debugging for FLOGI message timers

warning

Enables debugging for FLOGI warnings.

Defaults

None.

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_all
IPS Manager: 
iSCSI Trace Detail debugging is on
debug 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 size )
Syntax Description

filename

Assigns the name of the log file.

size size

Specifies the logfile size in bytes (4096-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.

Examples

The following example redirects the output of the debug commands to the file named sample.
switch# debug logfile sample 
The following example assigns the log file size for the file named sample.
switch# debug logfile sample size 410000
debug 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 | tx | rx) ( node range | opcode range | sap range ) } | { ( pkthdr both | tx | rx ( numpkt range ) ] } |
[ trace (vsan vsan-id ) (interface fc slot-port ) ]
Syntax Description

all

Enables debugging for all multicast definitions.

error

Enables debugging for multicast errors.

event

Enables debugging for multicast events.

mts

Enables debugging for multicast tx/rx MTS events.

trace

Enables debugging for multicast traces.

vsan vsan-id

Restricts debugging to the specified VSAN.

interface fc slot-port

Restricts debugging to the specified interface.

pkt

Specifies debugging of packets.

pkthdr

Specifies debugging of headers.

numpkt

Specifies the number of required packets

both

Specifies debugging in both the transmit and receive directions.

tx

Specifies debugging in the transmit direction,

rx

Specifies debugging in the receive direction.

node

Specifies the node for the packets in the receive direction.

opcode

Specifies the opcode for the packets in the receive direction.

sap

Specifies the sap for the packets in the receive direction.

range

Specifies the integer range from 1 to 4095.

Defaults

None.

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 all
debug 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
Syntax Description

errors

Enables debugging for MIP error conditions.

events

Enables debugging for MIP events.

Defaults

None.

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 errors
debug 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 ) ]
Syntax Description

all

Enables debugging for all module features.

error

Enables debugging for module error conditions.

event

Enables debugging for module events.

ha

Enables debugging for a module's high availability features.

no-powerdown

Disables the power cycle feature for the module.

trace

Enables debugging for a module's trace flows.

module slot

Restricts debugging to the specified module.

Defaults

None.

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 all
Apr 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, 0x3300000000000
004> to the pss runtime service add data list
Apr 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
Syntax Description

errors

Enables debugging for NTP error conditions.

info

Enables debugging for NTP information and events.

Defaults

None.

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 errors
debug 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) (both | tx | rx) ]
Syntax Description

all

Enables debugging for all platform features.

error

Enables debugging for platform-related error conditions.

flow

Enables debugging for platform-related flows.

fsm

Enables debugging for platform-related FSMs.

ha

Enables debugging for platform-related high availability.

hitless

Enables the platform loading feature while the switch is in hitless mode.

mts

Enables debugging for platform-related tx/rx MTS events.

fcid f c-id

Restricts debugging to the specified FC ID module number (from 0 to 2147483647).

pkt

Enables debugging of packets.

pkthdr

Enables debugging of headers.

both

Enables debugging in both the transmit and receive directions.

tx

Enables debugging in the transmit direction,

rx

Enables debugging in the receive direction.

Defaults

None.

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 all
debug 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 ] |
[ error ] |
[ event (interface type number | vsan vsan-id ) ] |
[ ha (interface type number | vsan vsan-id) ] |
[ trace (interface type number | vsan vsan-id)]
Syntax Description

action

Enables all port debug features.

all

Enables all port debug options.

error

Enables debugging for port error conditions.

event

Enables debugging for port FSMs and events.

ha

Enables debugging for port high availability.

trace

Enables debugging for port traces.

interface type number

Restricts debugging to the specified interface.

vsan vsan-id

Restricts debugging to the specified VSAN.

Defaults

None.

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 all
Apr 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_list
Apr 10 00:49:38 port: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 40239) dropped
The following example displays the system output when the debug port event command is issued:
switch# debug port event
Apr 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_list
Apr 10 15:30:35 port: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 7002)
 dropped
switch# 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 call
Apr 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), empty
Apr 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 (interface port-channel number) ] |
[ error ] |
[ event (interface port-channel number ) ] |
[ ha (interface port-channel number) ] |
[ mts (pkt | pkthdr) (both | tx | rx) (interface port-channel number) ]
[ query ]
[ trace (interface port-channel number) ]
Syntax Description

all

Enables all PortChannel debug options.

error

Enables debugging for PortChannel error conditions.

event

Enables debugging for PortChannel FSMs and events.

ha

Enables debugging for PortChannel high availability.

pkt

Enables debugging of packets.

pkthdr

Enables debugging of headers.

both

Enables debugging in both the transmit and receive directions.

tx

Enables debugging in the transmit direction,

rx

Enables debugging in the receive direction.

trace

Enables debugging for PortChannel traces.

interface port-channel number

Restricts debugging to the specified PortChannel.

vsan vsan-id

Restricts debugging to the specified VSAN.

Defaults

None.

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 all
debug 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 | detail | errors | flow | trace
Syntax Description

all

Enables all QoS debug options.

detail

Enables all QoS debug output.

error

Enables debugging for QoS error conditions.

flow

Enables flow-level QoS debug options.

trace

Enables debugging for QoS traces.

Defaults

None.

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 all
debug 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

None.

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 abc 
debug rdl

To enable debugging for the list of devices using the read-register feature, use the debug rdl 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

errors

Enables debugging for RDL errors.

Defaults

None.

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 errors 
debug 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

all

Enables debugging for all RIB features.

error

Enables debugging for RIB errors.

event

Enables debugging for RIB events.

trace

Enables debugging for trace events.

Defaults

None.

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 error 
debug 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 (vsan vsan-id ) ] |
[ errors (vsan vsan-id ) ] |
[ events (vsan vsan-id ) ] |
[ mts-errors (vsan vsan-id ) ] |
[ mts-events (vsan vsan-id ) ]
Syntax Description

all

Enables debugging for all RSCN features.

error

Enables debugging for RSCN errors.

event

Enables debugging for RSCN events.

mts-errors

Enables debugging for RSCN MTS errors.

mts-events

Enables debugging for RSCN MTS events.

Defaults

None.

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 error command is issued:
switch# debug rscn error 
debug 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
Syntax Description

error

Enables debugging for SCSI target daemon errors.

flow

Enables debugging for the SCSI target flow.

Defaults

None.

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 flow
Apr 28 21:11:52 vhbad: vhba_mts_handler: sdwrap_dispatch: retval:0
Apr 28 21:11:54 vhbad: vhbad_handle_timeout: timer:1 context:(nil)
Apr 28 21:12:06 vhbad: vhba_mts_handler: sysmgr_dispatch: retval:-1
debug 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
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

None.

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 radius 
Mar  5 00:51:13 securityd: RADIUS is enabled, hence it will be tried first for CHAP 
authentication
Mar  5 00:51:13 securityd: reading RADIUS configuration
Mar  5 00:51:13 securityd: opening radius configuration for group:default
Mar  5 00:51:13 securityd: opened the configuration successfully
Mar  5 00:51:13 securityd: GET request for RADIUS global config
Mar  5 00:51:13 securityd: got back the return value of global radius configuration 
operation:success
Mar  5 00:51:13 securityd: closing RADIUS pss configuration
Mar  5 00:51:13 securityd: opening radius configuration for group:default
debug 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
Syntax Description

demux

Enables debugging for sensor demux functions.

deque

Enables debugging for sensor deque events.

error

Enables debugging for sensor errors.

info

Enables debugging for sensor information.

init

Enables debugging for sensor initialization.

Defaults

None.

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 info 
Related Commands

Command

Description

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 | tx | rx ( node range | opcode range | sap range ) | { pkthdr both | tx | rx ( numpkt range ) } ] |
[ pkt-dump ] |
[ trace ( trace-entryexit | trace-stub ) ]
Syntax Description

all

Enables debugging for all SNMP output.

errors

Enables debugging for SNMP error output.

mts

Enables debugging for SNMP packets and headers.

pkt-dump

Enables a packet dump of debug output.

trace

Enables trace level debug output.

pkt

Specifies debugging of packets.

pkthdr

Specifies debugging of headers.

both

Specifies debugging in both the transmit and receive directions.

tx

Specifies debugging in the transmit direction.

rx

Specifies debugging in the receive direction.

node

Specifies the node for the packets in the receive direction.

opcode

Specifies the opcode for the packets in the receive direction.

sap

Specifies the sap for the packets in the receive direction.

numpkt

Specifies the number of required packets

range

Specifies the integer range from 1 to 4095.

trace-entryexit

Specifies trace-level entry or exit debug output.

trace-stub

Specifies trace-level stub debug output.

Defaults

None.

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 trace
Apr 29 16:03:34 snmpd[1177]: SDWRAP message Successfully processed
debug 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 | error | event | trace | warning
Syntax Description

all

Enables debugging for all SPAN features.

error

Enables debugging for SPAN errors.

event

Enables debugging for SPAN events.

trace

Enables debugging for SPAN traces.

warning

Enables debugging for SPAN warning messages.

Defaults

None.

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 all
Apr 29 16:06:44 span: span_demux: msg consumed by sdwrap_process msg
Apr 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_list
Apr 29 16:06:44 span: fu_fsm_engine: mts msg MTS_OPC_DEBUG_WRAP_MSG(msg_id 2548887) 
dropped
Apr 29 16:06:48 span: fu_priority_select:  - setting fd[3] for select call
Apr 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), empty
Apr 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_MSG
debug system

To enable system debugging, use the debug system 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 [ all | error | ha | health ( all | error | event | ha | trace ) ]
Syntax Description

all

Enables all PortChannel debug options.

error

Enables debugging for PortChannel error conditions.

ha

Enables debugging for PortChannel high availability.

health

Enables online health monitoring debugging.

all

Specifies debugging of all health monitoring flags.

error

Specifies debugging of health monitoring error flags.

event

Specifies debugging of health monitoring event flags.

ha

Specifies debugging of health monitoring HA flags.

trace

Specifies debugging of health monitoring trace flags.

Defaults

None.

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 command is issued:
switch# debug system all
debug 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
Syntax Description

demux

Enables debugging for terminal capture demux functions.

deque

Enables debugging for terminal capture deque events.

error

Enables debugging for terminal capture errors.

info

Enables debugging for terminal capture information.

init

Enables debugging for terminal capture initialization.

Defaults

None.

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 demux command is issued:
switch# debug demux 
debug 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 (interface fc slot ) ] |
[ errors (interface fc slot) ] |
[ events fc2 terminal (interface fc slot) | fc2 transit (interface fc slot) | mts (interface fc slot) | pss (interface fc slot) ]
Syntax Description

all

Enables debugging for all TL port features.

errors

Enables debugging for TL port error conditions.

events

Enables debugging for TL port monitoring events.

fc2

Enables debugging for TL port monitoring FC 2 events.

terminal

Specifies TL port monitoring FC 2 terminating events.

transit

Specifies TL port monitoring FC 2 transit events.

mts

Enables debugging for TL port monitoring MTS packets.

pss

Enables debugging for TL port monitoring PSS packets.

interface fc slot

Restricts debugging to the specified interface.

Defaults

None.

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 pss
debug 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
Syntax Description

all

Enables debugging for all TTYD features.

errors

Enables debugging for TTYD error conditions.

events

Enables debugging for TTYD events.

Defaults

None.

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 events
debug 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
Syntax Description

all

Enables debugging for all VNI features.

errors

Enables debugging for VNI error conditions.

events

Enables debugging for VNI events.

info

Enables debugging for VNI events.

pss

Enables debugging for VNI PSS packets.

Defaults

None.

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 all
Apr 29 17:00:59 vni: Received MTS message
Apr 29 17:00:59 vni: message not processed by system mgr library , so process it normal 
way
debug 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 all | error | event | info ] |
[ engine all | error | event | info ]
Syntax Description

configuration

Enables VRRP configuration debugging.

engine

Enables VRRP engine debugging.

all

Enables debugging for all VRRP features.

error

Enables debugging for VRRP error conditions.

event

Enables debugging for VRRP events.

info

Enables debugging for VRRP events.

Defaults

None.

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 all
Apr 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 call
Apr 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), empty
Apr 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 sent
Apr 29 17:35:58 vrrp_eng: message not processed by system mgr library , so process it 
normal way
debug 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 ]
Syntax Description

all

Enables all debugging flags for the VSAN feature.

global

Enables debugging of events for the VSAN global parameter database

ha

Enables debugging of VSAN's HA-related events.

info

Enables debugging of events for VSAN information database.

membership

Enables debugging of events for VSAN membership database.

mts

Enables Tx/Rx packets of MTS.

Defaults

None.

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-channel all
debug 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 )
Syntax Description

device-name

Specifies the device name for the required device.

register address

Specifies the register address for the required device.

Defaults

None.

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-reg 
debug 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
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

None.

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 wwn all
Apr 29 19:24:17 wwn: 53601-wwnm_sdwrap_dispatch:77|SDWRAP massage Successfully processed
Apr 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:0
Apr 29 19:24:17 wwn: 01 00 00 00 E7 03 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
Apr 29 19:24:17 wwn: 2F 64 65 76 2F 70 74 73 2F 30 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Apr 29 19:24:17 wwn: 00 00 00 00 00 00 00 00 2E 00 00 00
Apr 29 19:24:17 wwn: 53601-wwnm_unmask_sigalrm:1261|TRACE: 
FILE=_manager/wwnm/wwnm_utilities.c
debug 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

all

Enables all XBAR debug options.

demux

Enables debugging for XBAR demux functions.

deque

Enables debugging for XBAR deque events.

error

Enables debugging for XBAR errors.

fsm

Enables debugging for XBAR FSMs.

ha

Enables debugging for XBAR high availability information.

init

Enables debugging for XBAR initialization.

main

Enables XBAR debugging for main functions.

module slot

Specifies the slot number of the module being debugged.

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 all
Apr 29 19:48:34 xbar:  its a sdwrap msg, fsm utils dropping the mts msg
Apr 29 19:48:34 xbar: fu_fsm_engine: (Error) SYSERR_FU_xx: 0x10, err_num (16) in demux
Apr 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 ]
Syntax Description

demux

Enables debugging for crossbar demux functions.

deque

Enables debugging for crossbar deque events.

init

Enables debugging for crossbar initialization.

main

Enables debugging for crossbar main functions.

Defaults

None.

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 init
debug 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 (vsan vsan-id) | events (vsan vsan-id) | packets (vsan vsan-id) ] |
[ database errors (vsan vsan-id) | events (vsan vsan-id) ] |
[ gs errors (vsan vsan-id) | events (vsan vsan-id) | packets (vsan vsan-id) ] |
[ merge errors (vsan vsan-id) | events (vsan vsan-id) | packets (vsan vsan-id) ] |
[ mts notifications (vsan vsan-id) ] |
[ pss errors (vsan vsan-id) | events (vsan vsan-id) ] |
[ tcam errors (vsan vsan-id) | events (vsan vsan-id) | packets (vsan vsan-id) ] |
Syntax Description

all

Enables all zone server debug options.

change

Enables change protocol message debugging.

errors

Enables debugging for zone errors.

events

Enables debugging for zone events.

packets

Enables debugging l for zone packets.

vsan vsan-id

Restricts debugging to the specified VSAN.

database

Specifies database message debugging.

gs

Specifies GS protocol message debugging.

merge

Specifies merge protocol message debugging.

mts notification

Specifies MTS notification message debugging.

tcam

Specifies TCAM message debugging.

Defaults

None.

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