Brocade Communications Systems FastIron SX 800 User manual

53-1002965-01
30 September 2013
®
Brocade FastIron, FCX, ICX,
and TurboIron
Diagnostic Reference
Supporting FastIron Software Release 08.0.01

Copyright © 2013 Brocade Communications Systems, Inc. All Rights Reserved.
ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and
Vyatta are registered trademarks, and HyperEdge, The Effortless Network, and The On-Demand Data Center are trademarks of
Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names
mentioned may be trademarks of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning
any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to
this document at any time, without notice, and assumes no responsibility for its use. This informational document describes
features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.
Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other
open source license agreements. To find out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Document History
Corporate and Latin American Headquarters
Brocade Communications Systems, Inc.
130 Holger Way
San Jose, CA 95134
Tel: [phone]
Fax: [phone]
E-mail: inf[email protected]
Asia-Pacific Headquarters
Brocade Communications Systems China HK, Ltd.
No. 1 Guanghua Road
Chao Yang District
Units 2718 and 2818
Beijing 100020, China
Tel: [phone]
Fax: [phone]
E-mail: [email protected]
European Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour B - 4ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: [phone]
Fax: [phone]
E-mail: emea-i[email protected]
Asia-Pacific Headquarters
Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Citic Plaza
No. 233 Tian He Road North
Unit 1308 – 13th Floor
Guangzhou, China
Tel: [phone]
Fax: [phone]
E-mail: [email protected]
Title Publication number Summary of changes Date
Brocade FastIron, FCX, ICX, and
TurboIron Diagnostic Reference
53-1002645-01 Release 07.4.00 document
updated with
enhancements in Release
08.0.00.
April 2013
Brocade FastIron, FCX, ICX, and
TurboIron Diagnostic Reference
53-1002645-02 Release 08.0.00 document
updated for Release
08.0.00a.
June 2013
Brocade FastIron, FCX, ICX, and
TurboIron Diagnostic Reference
53-1002965-01 Release 08.0.00a
document updated for
Release 08.0.01.
September 2013

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference iii
53-1002965-01
Contents
About This Guide
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Supported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Unsupported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
What’s new in this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Notes and caution notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Getting technical help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Chapter 1 Using Diagnostic Commands
Using debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Brief and detail debug options . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Generic debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Disabling debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2 System Level and Layer 1 Diagnostics
Layer 1 debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Hardware backplane debug command . . . . . . . . . . . . . . . . . . . . 5
Loop detect debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Port debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
System debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Software licensing debug command . . . . . . . . . . . . . . . . . . . . . . . . .12
Chapter 3 Layer 2 Diagnostics
STP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
RSTP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
MSTP debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
DHCP debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
GVRP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

iv Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01
MAC address debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
MCT debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
MCT show commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Packet-capture debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Link aggregation debug commands . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 4 IP Diagnostics
ARP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
BGP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
DHCP snooping debug commands . . . . . . . . . . . . . . . . . . . . . . . . . .56
GRE debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
ICMP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
OSPF debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
RIP debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
NTP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Source Guard debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
SSH debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Synchronization debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . 77
TCP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
UDP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
VRRP and VRRP-E debug commands . . . . . . . . . . . . . . . . . . . . . . . . 81
Web debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Chapter 5 IPv6 Diagnostics
General IPv6 debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
IPv6 MLD debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
IPv6 OSPF debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
DHCPv6 debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
DHCPv6 show commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
IPv6 PIM debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
IPv6 RIP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Chapter 6 Multicast Diagnostics
MSDP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
IGMP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
IGMP snooping debug commands. . . . . . . . . . . . . . . . . . . . . . . . . .150
PIM debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
PIM-SM snooping debug commands. . . . . . . . . . . . . . . . . . . . . . . .164

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference v
53-1002965-01
MLD snooping debug commands . . . . . . . . . . . . . . . . . . . . . . . . . .167
Chapter 7 Security Diagnostics
ACL debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
802.1x debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
MAC authentication debug commands . . . . . . . . . . . . . . . . . . . . . .172
sFlow debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
IP security debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Web events debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Web authentication debug commands . . . . . . . . . . . . . . . . . . . . . . 176
RA guard debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
Chapter 8 supportsave Diagnostics
supportsave overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
supportsave commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
Limitations and pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . .179
Recovery during continuous reload . . . . . . . . . . . . . . . . . . . . .183
Chapter 9 Technical Support Diagnostics
show tech-support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Diagnostic Command Index

vi Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference vii
53-1002965-01
About This Guide
This chapter contains the following sections:
•Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
•Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
•Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
•What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
•Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Introduction
This guide describes many common diagnostic processes for the Brocade FastIron devices. Each
chapter contains diagnostic information about a specific segment of your network configuration.
Supported Hardware
•FastIron X Series devices (chassis models):
•Brocade FastIron SX 800
•FastIron SX 1600
•Brocade FCX Series (Brocade FCX) Stackable Switch
•Brocade ICX 6610 (ICX 6610) Stackable Switch
•Brocade ICX 6430 Series (ICX 6430)
•Brocade ICX 6450 Series (ICX 6450)
•Brocade ICX 6650 Series (ICX 6650)
•Brocade TurboIron 24X Series
For information about the specific models and modules supported in a product family, refer to the
hardware installation guide for that product family. “Related publications” on page x lists the
hardware installation guides and software configuration guides.
NOTE
The Brocade ICX 6430-C switch supports the same feature set as the Brocade ICX 6430 switch
unless otherwise noted.

viii Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01
NOTE
The Brocade ICX 6450-C12-PD switch supports the same feature set as the Brocade ICX 6450
switch unless otherwise noted.
NOTE
Some debug commands report information about internal hardware settings and registers that is
relevant primarily to the Brocade engineering staff. Consequently, this information is not described
in this document.
Unsupported features
Features that are not documented in “Related publications” on page x are not supported.
Audience
This document is designed for network engineers with a working knowledge of Layer 2 and Layer 3
switching and routing.
If you are using a Brocade Layer 3 switch, you should be familiar with the following protocols if
applicable to your network – IP, RIP, OSPF, BGP, ISIS, IGMP, PIM, DVMRP, and VRRP.
Disclaimer
This manual is provided without any warranty of any kind, expressed or implied. When using this
manual to troubleshoot Brocade products, you assume all risk as to the quality and performance of
the debug procedures. Brocade assumes no liability for any damages, including general, special,
incidental, or consequential damages arising from the use of the procedures in this manual
(including, but not limited to any loss of profit or savings, loss of data, or failure to successfully
troubleshoot network problems).
Debug information may be changed or updated without notice. You are responsible for obtaining
newer versions of this manual when they are made available. The procedures in this document are
not intended as a substitute for the expertise of qualified technicians.
Enabling debug commands can seriously degrade system performance. Debug commands are
generally intended for use when troubleshooting specific problems while working with qualified
service technicians, or in conjunction with calls to Brocade Technical Support. Whenever possible,
troubleshoot your system during periods of low network traffic and user activity to preserve system
performance.
If you have any questions regarding this disclaimer please contact us at
http://www.brocade.com/products/all/routers/index.page.
What’s new in this document
There are no enhancements for FastIron release 08.0.01.

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference ix
53-1002965-01
Document conventions
This section describes text formatting conventions and important notice formats used in this
document.
Text formatting
The narrative-text formatting conventions that are used are as follows:
For readability, command names in the narrative portions of this guide are presented in mixed
lettercase: for example, switchShow. In actual examples, command lettercase is all lowercase.
Command syntax conventions
Command syntax in this manual follows these conventions:
Notes and caution notices
The following notices and statements are used in this manual. They are listed below in order of
increasing severity of potential hazards.
NOTE
A note provides a tip, guidance, or advice, emphasizes important information, or provides a
reference to related information.
ATTENTION
An Attention statement indicates potential damage to hardware or data.
bold text Identifies command names
Identifies the names of user-manipulated GUI elements
Identifies keywords
Identifies text to enter at the GUI or CLI
italic text Provides emphasis
Identifies variables
Identifies document titles
code text Identifies CLI output
command and
parameters
Commands and parameters are printed in bold.
[ ] Optional parameter.
variable Variables are printed in italics.
... Repeat the previous element, for example “member[;member...]”
| Choose from one of the parameters.

xBrocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.
Related publications
The following Brocade documents supplement the information in this guide and can be located at
http://www.brocade.com/ethernetproducts.
•FastIron Ethernet Switch Administration Guide, 08.0.01
•FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide, 08.0.01
•FastIron Ethernet Switch Layer 3 Routing Configuration Guide, 08.0.01
•FastIron Ethernet Switch IP Multicast Configuration Guide, 08.0.01
•FastIron Ethernet Switch Security Configuration Guide, 08.0.01
•FastIron Ethernet Switch Software Upgrade Guide, 08.0.01
•FastIron Switch Stacking Configuration Guide, 08.0.01
•FastIron Ethernet Switch Traffic Management Guide, 08.0.01
•FastIron Ethernet Switch Software Licensing Guide, 08.0.01
•FastIron Feature Support Matrix, 08.0.01
•Brocade TurboIron 24X Series Configuration Guide, 08.0.01
•Brocade ICX 6430-C Switch Installation Guide, 08.0.01
•Brocade ICX 6430 and ICX 6450 Stackable Switches Hardware Installation Guide, 08.0.01
•Brocade FCX Series Hardware Installation Guide, 08.0.01
•Brocade FastIron ICX 6610 Stackable Switch Hardware Installation Guide, 08.0.01
•Brocade ICX 6650 Ethernet Switch Installation Guide, 08.0.01
•Brocade FastIron SX Series Chassis Hardware Installation Guide, 08.0.01
•Brocade TurboIron 24X Series Hardware Installation Guide, 08.0.01
•Brocade ICX 6450-C12-PD Switch Installation Guide, 08.0.01
•Unified IP MIB Reference, 08.0.01
Getting technical help
To contact Technical Support, go to http://www.brocade.com/services-support/index.page for the
latest e-mail and telephone contact information.

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference xi
53-1002965-01
Document feedback
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a
topic needs further development, we want to hear from you. Forward your feedback to:
[e-mail]
Provide the title and version number of the document and as much detail as possible about your
comment, including the topic heading and page number and your suggestions for improvement.

xii Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference 1
53-1002965-01
Chapter
1
Using Diagnostic Commands
This chapter contains the following sections:
•Using debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
•Generic debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Using debug commands
This section describes how to use debug commands to monitor and troubleshoot Brocade FCX,
Brocade ICX, and Brocade TurboIron switch configurations. The debug commands are accessible
from the Privileged EXEC mode in the IronWare command line interface (CLI). Most of the debug
commands can be configured to send output to a specified destination.
When enabled, the debug commands can noticeably affect system performance. Many debug
commands are specifically designed to be used in conjunction with calls to Brocade technical
support. If you report a problem, the support engineer may ask you to execute one or more of the
debug commands described in this guide.
ATTENTION
Some debug commands report information about internal hardware settings and registers, which is
relevant primarily to the Brocade engineering staff. These commands are not described in this
document.
Brief and detail debug options
When enabled, many debug commands can significantly impact system performance. Many debug
commands provide options for brief or detailed reporting. Generating detailed output places an
additional burden on system performance, and in many cases the results may be more difficult to
interpret than output generated using the brief option. To conserve performance and prevent
system disruption, use the brief option whenever possible.
Generic debug commands
The following generic debug commands perform functions related to all debugging actions:
•debug ?—Generates a list of debug options.
•[no]debug all—Enables or disables all debug functions.
•show debug—Shows all enabled debug settings.
•debug destination—Allows you to select an output destination; Telnet, SSH, console, or logging
(default).

2Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01
Generic debug commands
1
debug ?
Syntax: debug ?
This command generates a list of available debug variables.
ATTENTION
Many first-level variables have their own variable subsets. When you enter a debug command, the
system indicates that there are additional variables available and you have entered an incomplete
command. Add a space and a question mark to your original command to view the additional
variables.
debug all
Syntax: [no]debug all
This command enables all the debug functions, and should be used only during a troubleshooting
session with a Brocade technician.
Brocade# debug all
Warning! This may severely impact network performance!
All possible debuggings have been turned on
Enter the no command to cancel the setting.
Brocade#no debug all
Debug message destination: default (console)
All possible debuggings have been turned off
tracking is off and all results are cleared
Disabling ACL log
Don't monitor port
CAUTION
The debug all command generates extensive output and can significantly slow device operation.
Use this command with caution. Never use this command during periods of peak network activity.
Enter no debug all to stop the output.
debug destination
Syntax: [no]debug destination [ console |logging |telnet num | ssh num ]
Brocade# debug ip
Incomplete command
Brocade#debug ip ?
arp ARP messages
dhcp_snooping DHCP snooping
icmp ICMP transactions
igmp IGMP protocol activity
pim PIM/dvmrp protocol activity
source_guard Source Guard
ssh SSH information
tcp TCP information
udp UDP based transactionstp
web WEB HTTP/HTTPS information

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference 3
53-1002965-01
Generic debug commands 1
•console—Directs output to the system console.
•logging—Directs output to the syslog buffer and to the syslog server (default).
•telnet num—Directs output to a specified Telnet session (ranges from 1 through 5).
•ssh num—Directs output to a specified Secure Shell (SSH) session (ranges from 1 through 5).
This command allows you to specify a destination for debugging output. The default destination is
the system console, but you can redirect output to a syslog buffer, Telnet session, or SSH session.
To send debug output to a Telnet session, first determine your session number using the show who
command.
This example indicates that you are connected through active Telnet session 1. To redirect the
debug output to your Telnet session, enter the following command.
Brocade#debug destination telnet 1
show debug
Syntax: show debug
This command displays all the enabled debug functions. The output resembles the following
example, which shows that ACL log and IPv6 debugging are enabled, with the console as the output
destination.
Brocade# show who
Console connections (by unit number):
1 established
4 minutes 29 seconds in idle
Telnet connections (inbound):
1 established, client ip address 172.31.0.1
you are connecting to this session
2 seconds in idle
2 closed
3 closed
4 closed
5 closed
Telnet connection (outbound):
6 closed
SSH connections:
1 closed
2 closed
3 closed
4 closed
Brocade# show debug
Debug message destination: Console
Enabling ACL log
IPv6 Routing:
ipv6: icmp debugging is on

4Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01
Generic debug commands
1
Disabling debug commands
When activated, most debug commands instruct the system to collect specific information about
router configurations and activity. In all cases, adding no in front of the command disables the
debug function.

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference 5
53-1002965-01
Chapter
2
System Level and Layer 1 Diagnostics
This chapter contains the following sections:
•Layer 1 debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
•System debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
•Software licensing debug command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Layer 1 debug commands
The following commands deal with the Layer 1 debugging for the Brocade FastIron platforms. In
general, Layer 1 issues are related to hardware, the most common being physical connectivity
problems.
Hardware backplane debug command
The following command enables the hardware backplane debugging feature in a device.
debug hw
Syntax: [no]debug hw
This command enables the hardware backplane debugging feature. To disable this feature, enter
the no form of the command.
Brocade# debug hw
HW BP: backplane debugging is on
Loop detect debug commands
Brocade Port Loop Detection (PLD) protocol allows the Brocade devices to detect loops and disable
a port that is on the receiving end of a loop. The loop is detected by sending Bridge Packet Data
Unit (BPDU) test packets.
debug loop-detect
Syntax: [no]debug loop-detect
This command initiates debugging the loop detection.
NOTE
Execute the command prior to configuring the modes.
Execute the following command to configure loop detection of a single port in strict mode.
Brocade# debug loop-detect
Configure loop-detection strict mode on port 1/1/25 :

6Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01
Layer 1 debug commands
2
Brocade(config-if-e1000-1/1/25)# loop-detection
When there is loop detection activity in the switch, the debug information regarding loop detection
is displayed on the console. The following example shows the output for the debug loop-detect
command when the port goes into a disabled state because of loop detection (strict mode).
insert_disable primary 1/1/25, vlan=4096
Loop-detection: port 1/1/25 (vlan=1), put into errdisable state
Execute the following command to configure loop detection in a VLAN in loose mode.
Configure loop-detection loose mode on port vlan 2 :
Brocade(config-vlan-2)# loop-detection
Brocade(config-vlan-2)# insert_disable primary 1/1/31, vlan=2
The following output is displayed after the configuration.
Loop-detection: port 1/1/31 (vlan=2), put into errdisable state
insert_disable primary 1/1/32, vlan=2
Loop-detection: port 1/1/32 (vlan=2), put into errdisable state
debug loop-detect level
Syntax: [no]debug loop-detect level <decimal>
This command debugs loop detection in a particular level.
Brocade# debug loop-detect level 1
STRICT MODE:
Topology: port 1/1/25 is single port.
Brocade# debug loop-detect level 3
Configure loop-detection on port 1/1/25 :
Brocade(config-if-e1000-1/1/25)# loop-detection
Brocade(config-if-e1000-1/1/25)# Loop-detection: port 1/1/25 (vlan=1), put into
errdisable state
LOOSE MODE:
Topology: port 1/1/31 is connected to 1/1/32 in same vlan.
Configure loop-detection on port vlan 2 :
Brocade(config-vlan-2)# loop-detection
Brocade(config-vlan-2)# Loop-detection: port 1/1/31 (vlan=2), put into errdisable
state
Loop-detection: port 1/1/32 (vlan=2), put into errdisable state
Port debug commands
The following commands deal with the debugging of port activity.
debug port hw-state
Syntax: [no]debug port hw-state
This command monitors the hardware status of a port. This helps to enable or disable port
debugging in the hardware state.
Brocade# debug port hw-state
Topology: Port 1/1/31 is connected to port 1/1/32.

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference 7
53-1002965-01
Layer 1 debug commands 2
If port 1/1/31 is disabled, an output similar to the following is displayed.
Brocade(config)# interface ethernet 1/1/31
Brocade(config-if-e1000-1/1/31)# disable ( when port is disabled)
Change port 1/1/31 hw_state from PORT_READY(7) to DISABLED(0)
stack: 4040 2050A970 2050AA44 2060D498 20608BF8 2060B5A4 20576A90 20576C74
2057707C 202A50A8 20491E9C 20492DC0 204906D8 2050BF48 204A03C8 204A0418 2011BBC8
20047698 2011CF7C 5008
Brocade(config-if-e1000-1/1/31)# change port 1/1/32 hw_state from PORT_READY(7)
to SEEQ_INIT(1)
stack: 4040 2050A970 2050AA44 2060D498 20608E18 20609344 20609AFC 2055FA50
2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524
If port 1/1/31 is enabled, an output similar to the following is displayed.
Brocade(config-if-e1000-1/1/32)# interface ethernet 1/1/31
Brocade(config-if-e1000-1/1/31)# enable
Change port 1/1/31 hw_state from DISABLED(0) to SEEQ_INIT(1)
stack: 4040 2050A970 2050AA44 2060D498 20608A34 2060B598 20576BC4 20576C74
2057707C 202A4F84 20491E9C 20492DC0 204906D8 2050BF48 204A03C8 204A0418 2011BBC8
20047698 2011CF7C 5008
Brocade(config-if-e1000-1/1/31)# change port 1/1/31 hw_state from SEEQ_INIT(1) to
PORT_READY(7)
stack: 4040 2050A970 2050AA44 2060D498 206093D0 20609AFC 2055FA50 2050A214
200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524
Change port 1/1/32 hw_state from SEEQ_INIT(1) to PORT_READY(7)
stack: 4040 2050A970 2050AA44 2060D498 206093D0 20609AFC 2055FA50 2050A214
200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524
debug port port
Syntax: [no]debug port port stackid/slot/port
This command monitors a specific physical port and is used with the debug port up-down or debug
port hw-state commands. The stackid/slot/port variable refers to the stack ID, slot number, and
port number.
.
Brocade# debug port port 1/1/2
Topology: Port 1/1/31 is connected to port 1/1/2.
When the debug port hw-state command is enabled after the debug port port command, the
output similar to the following example is displayed.
Brocade# debug port port 1/1/2
monitor port 1/1/2
Brocade# debug port hw-state
If port 1/1/2 is disabled, an output similar to the following is displayed.
Brocade(config-if-e1000-1/1/2)# disable
port_disable_cmd: for port 0x1 1/1/2
U1, hal_pp_link_port_enable(1/1/2, 0), is_stby=0, to_shadow=0, parsed = 3,
stack=1
stack: 0116c83c 000de8f0 00accc3c 00acd6ac 00ad21f4 0136c614 0136c850 0136cf00
012b842c 0084b3b0 0084e0a0 00847608 00966c0c 0086c110 0086c154 00243f98 000f0524
00246f54 0159f920 017713c4
pp_link_port_en_dis(port=1/1/2, 0), return 0
stack: 0116ca20 000de8f0 00accc3c 00acd6ac 00ad21f4 0136c614 0136c850 0136cf00
012b842c 0084b3b0 0084e0a0 00847608 00966c0c 0086c110 0086c154 00243f98 000f0524
00246f54 0159f920 017713c4
Change 1/1/2 state from Forward to Disable

8Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference
53-1002965-01
Layer 1 debug commands
2
stack: 00acb98c 00ad1e14 00aebd74 0071dddc 0071ebbc 00af0e8c 00af18e8 00ad0e20
00acccf4 00acd6ac 00ad21f4 0136c614 0136c850 0136cf00 012b842c 0084b3b0 0084e0a0
00847608 00966c0c 0086c110 0086c154 00243f98 000f0524 00246f54 0159f920 017713c4
Change port 1/1/2 hw_state from PORT_READY(7) to DISABLED(0)
stack: 00ad5d4c 00accd2c 00acd6ac 00ad21f4 0136c614 0136c850 0136cf00 012b842c
0084b3b0 0084e0a0 00847608 00966c0c 0086c110 0086c154 00243f98 000f0524 00246f54
0159f920 017713c4
Change 1/1/2 state from Disable to Blocked
stack: 00acb98c 00acba3c 00acbce4 00accd38 00acd6ac 00ad21f4 0136c614 0136c850
0136cf00 012b842c 0084b3b0 0084e0a0 00847608 00966c0c 0086c110 0086c154 00243f98
000f0524 00246f54 0159f920 017713c4
Change 1/1/2 state from Blocked to Disable
stack: 00acb98c 00acba3c 00accd48 00acd6ac 00ad21f4 0136c614 0136c850 0136cf00
012b842c 0084b3b0 0084e0a0 00847608 00966c0c 0086c110 0086c154 00243f98 000f0524
00246f54 0159f920 017713c4
If port 1/1/2 is enabled, an output similar to the following is displayed.
Brocade(config-if-e1000-1/1/2)# enable
Brocade(config-if-e1000-1/1/2)# change port 1/1/2 hw_state from SEEQ_INIT(1) to
PORT_READY(7)
stack: 4040 2050A970 2050AA44 2060D498 206093D0 20609AFC 2055FA50 2050A214
200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524
Change 1/1/2 state from Disable to Blocked
stack: 4040 2050A970 2050AA44 206082E0 2060B354 206215F8 203F9F10 203FB4D8
203FA2B4 2062268C 20623404 2060A624 20609520 20609AFC 2055FA50 2050A214 200478DC
2011BBCC 20047698 2011CF7C
Change 1/1/2 state from Blocked to Listen
stack: 4040 2050A970 2050AA44 206082E0 2060B354 20621734 203F9F10 203FD490
203FD1C4 203FA2BC 2062268C 20623404 2060A624 20609520 20609AFC 2055FA50 2050A214
200478DC 2011BBCC 20047698
Change 1/1/2 state from Listen to Learn
stack: 4040 2050A970 2050AA44 206082E0 2060B354 2062178C 203F9F10 20400F38
20400C84 20400A1C 203F9980 2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8
18524
Change 1/1/2 state from Learn to Blocked
stack: 4040 2050A970 2050AA44 206082E0 2060B354 206215F8 203F9F10 203FD70C
203FD248 203FDFD8 204F3C8C 20616AB8 20612D30 200DC33C 200DC600 200DC6C0 200DC780
200444C4 2011BC28 20047698
The debug port up-down disables or enables a port to get output information of the specified port.
When the debug port up-down command is enabled after the debug port port command, the
output similar to the following example is displayed.
Brocade# debug port port 1/1/32
monitor port 1/1/32
Brocade# debug port up-down
If port 1/1/32 is disabled, an output similar to the following is displayed.
Brocade(config-if-e1000-1/1/32)# disable
port_down_indication. port=1/1/32, UNTAG, vlan-idx=1
stack: 4040 2050A970 2050AA44 2060A8FC 20608BEC 2060B5A4 20576A90 20576C74
2057707C 202A50A8 20491E9C 20492DC0 204906D8 2050BF48 204A03C8 204A0418 2011BBC8
20047698 2011CF7C 5008
Change 1/1/32 state from Blocked to Disable
stack: 4040 2050A970 2050AA44 206082E0 2060B354 206214F0 203F9F10 203FA3A0
20622F60 20623404 2060AA38 20608BEC 2060B5A4 20576A90 20576C74 2057707C 202A50A8
20491E9C 20492DC0 204906D8
Change 1/1/32 state from Disable to Blocked