Brocade FastIron SX, FCX, ICX Diagnostic Reference

Download

Page 1

53-1003076-02

30 July 2014

Brocade FastIron SX, FCX, and ICX

Diagnostic Reference

Supporting FastIron Software Release 08.0.10d

Page 2

Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be trademarks of others.

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. assume no liability or responsibility to any person or entity with respect to the accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein 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

Corporate and Latin American Headquarters Brocade Communications Systems, Inc. 130 Holger Way San Jose, CA 95134 Tel: 1-408-333-8000 Fax: 1-408-333-8101 E-mail: info@brocade.com

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: +41 22 799 5640 Fax: +41 22 799 5641 E-mail: emea-info@brocade.com

Asia-Pacific Headquarters Brocade Communications Systems China HK, Ltd. No. 1 Guanghua Road Chao Yang District Units 2718 and 2818 Beijing 100020, China Tel: +8610 6588 8888 Fax: +8610 6588 9999 E-mail: china-info@brocade.com

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: +8620 3891 2000 Fax: +8620 3891 2111 E-mail: china-info@brocade.com

Document History

Title Publication number Summary of changes Date

Brocade FastIron, FCX, ICX, and TurboIron Diagnostic Reference

Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1002645-01 Release 07.4.00 document

updated with enhancements in Release

08.0.00.

53-1002645-02 Release 08.0.00 document

updated for Release

08.0.00a.

53-1002965-01 Release 08.0.00a

document updated for Release 08.0.01.

53-1003076-01 Release 08.0.01 document

updated for Release

08.0.10.

53-1003076-02 Release 08.0.10 document

updated for Release

08.0.10d.

April 2013

June 2013

September 2013

January 2014

July 2014

Page 3

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

MAC address debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Brocade FastIron SX, FCX, and ICX Diagnostic Reference iii 53-1003076-02

Page 4

MCT debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

MCT show commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Packet-capture debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . .45

VXLAN debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Link aggregation debug commands . . . . . . . . . . . . . . . . . . . . . . . . .50

Chapter 4 IP Diagnostics

ARP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

BGP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

DHCP snooping debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . 60

GRE debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

ICMP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

OSPF debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

RIP debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

NTP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Source Guard debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

SSH debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Synchronization debug commands . . . . . . . . . . . . . . . . . . . . . . . . . .80

TCP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

UDP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

VRRP and VRRP-E debug commands . . . . . . . . . . . . . . . . . . . . . . . .84

Web debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Chapter 5 IPv6 Diagnostics

General IPv6 debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

IPv6 MLD debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

IPv6 OSPF debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

DHCPv6 debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

DHCPv6 show commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

IPv6 PIM debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

IPv6 RIP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Chapter 6 Multicast Diagnostics

MSDP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

IGMP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

IGMP snooping debug commands. . . . . . . . . . . . . . . . . . . . . . . . . .152

PIM debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

PIM-SM snooping debug commands. . . . . . . . . . . . . . . . . . . . . . . .166

iv Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 5

MLD snooping debug commands . . . . . . . . . . . . . . . . . . . . . . . . . .168

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Diagnostic Command Index

Brocade FastIron SX, FCX, and ICX Diagnostic Reference v 53-1003076-02

Page 6

vi Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 7

About This Guide

NOTE

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

•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 ICX 7750 Series (ICX 7750)

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.

The Brocade ICX 6430-C switch supports the same feature set as the Brocade ICX 6430 switch unless otherwise noted.

The Brocade ICX 6450-C12-PD switch supports the same feature set as the Brocade ICX 6450 switch unless otherwise noted.

Brocade FastIron SX, FCX, and ICX Diagnostic Reference vii 53-1003076-02

Page 8

NOTE

Audience

Disclaimer

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.

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.

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

This document includes the information from IronWare software release 08.0.10d. Table 1 lists the enhancements for FastIron release 08.0.10d.

viii Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 9

TABLE 1 Summary of Enhancements in FastIron release 08.0.10d

Feature Description Described in

DHCPv6 Relay Agent Prefix Delegation (PD) notification

VXLAN debug commands

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:

bold text Identifies command names

The debug ipv6 dhcp command has been modified to support DHCPv6 PD debugging.

Added new debug commands for debugging the VXLAN Layer 2 tunnel configurations.

“DHCPv6 debug commands”

“VXLAN debug commands”

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

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:

command and parameters

[ ] Optional parameter.

variable Variables are printed in italics.

... Repeat the previous element, for example “member[;member...]”

| Choose from one of the parameters.

Commands and parameters are printed in bold.

Brocade FastIron SX, FCX, and ICX Diagnostic Reference ix 53-1003076-02

Page 10

Notes and caution notices

NOTE

ATTENTION

CAUTION

The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.

A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.

An Attention statement indicates potential damage to hardware or data.

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.10d

• FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide, 08.0.10d

• FastIron Ethernet Switch Layer 3 Routing Configuration Guide, 08.0.10d

• FastIron Ethernet Switch IP Multicast Configuration Guide, 08.0.10a

• FastIron Ethernet Switch Security Configuration Guide, 08.0.10d

• FastIron Ethernet Switch Software Upgrade Guide, 08.0.10a

• FastIron Switch Stacking Configuration Guide, 08.0.10a

• FastIron Ethernet Switch Traffic Management Guide, 08.0.10b

• FastIron Ethernet Switch Software Licensing Guide, 08.0.10

• FastIron Feature Support Matrix, 08.0.10d

• Brocade ICX 6430-C Compact Switch Hardware Installation Guide, 08.0.10

• Brocade ICX 6430 and ICX 6450 Stackable Switches Hardware Installation Guide, 08.0.10

• Brocade FCX Series Hardware Installation Guide, 08.0.10

• Brocade FastIron ICX 6610 Stackable Switch Hardware Installation Guide, 08.0.10

• Brocade ICX 6650 Ethernet Switch Installation Guide, 08.0.10

• Brocade ICX 7750 Switch Hardware Installation Guide, 08.0.10

• Brocade FastIron SX Series Chassis Hardware Installation Guide, 08.0.10

• Brocade ICX 6450-C Compact Switch Hardware Installation Guide, 08.0.10

• Unified IP MIB Reference, 08.0.10

x Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 11

To contact Technical Support, go to http://www.brocade.com/services-support/index.page for the latest e-mail and telephone contact information.

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:

documentation@brocade.com

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.

Brocade FastIron SX, FCX, and ICX Diagnostic Reference xi 53-1003076-02

Page 12

xii Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 13

Chapter

ATTENTION

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 FastIron, Brocade FCX, and Brocade ICX 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.

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).

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 1 53-1003076-02

Page 14

Generic debug commands

ATTENTION

CAUTION

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

debug ?

Syntax: debug ?

This command generates a list of available debug variables.

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

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.

2 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

debug destination

Syntax: [no] debug destination [ console | logging | telnet num | ssh num ]

53-1003076-02

Page 15

Generic debug commands

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

• 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

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 3 53-1003076-02

destination.

Page 16

Generic debug commands

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.

4 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 17

Chapter

NOTE

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.

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 :

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 5 53-1003076-02

Page 18

Layer 1 debug commands

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.

6 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 19

Layer 1 debug commands

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

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 7 53-1003076-02

Page 20

Layer 1 debug commands

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

8 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 21

Layer 1 debug commands

stack: 4040 2050A970 2050AA44 206082E0 20608330 206084C4 20608C00 2060B5A4 20576A90 20576C74 2057707C 202A50A8 20491E9C 20492DC0 204906D8 2050BF48 204A03C8 204A0418 2011BBC8 20047698 Change 1/1/32 state from Blocked to Disable stack: 4040 2050A970 2050AA44 206082E0 20608330 20608C0C 2060B5A4 20576A90 20576C74 2057707C 202A50A8 20491E9C 20492DC0 204906D8 2050BF48 204A03C8 204A0418 2011BBC8 20047698 2011CF7C

If port 1/1/32 is enabled, an output similar to the following is displayed.

Brocade(config-if-e1000-1/1/32)# enable Change 1/1/32 state from Disable to Blocked stack: 4040 2050A970 2050AA44 206082E0 206089A0 2060B598 20576BC4 20576C74 2057707C 202A4F84 20491E9C 20492DC0 204906D8 2050BF48 204A03C8 204A0418 2011BBC8 20047698 2011CF7C 5008 Brocade(config-if-e1000-1/1/32)# pp_link_change_final. port=1/1/32, up=1 port_up_indication. port=1/1/32, UNTAG, vlan-idx=1 stack: 4040 2050A970 2050AA44 2060A2C8 20609520 20609AFC 2055FA50 2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524 Change 1/1/32 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/32 state from Listen to Blocked stack: 4040 2050A970 2050AA44 206082E0 2060B354 206215F8 203F9F10 203FD70C 203FD248 203FDFD8 204F3C8C 20616AB8 20612D30 200DC33C 200DC600 200DC6C0 200DC780 200444C4 2011BC28 20047698

debug port ten-gig

Syntax: [no] debug port ten-gig

This command monitors all 10 Gigabit ports in the Brocade FastIron devices and is used in conjunction with the debug port hw-state command.

Brocade# debug port ten-gig Topology: Port 2/3/1 is the 10 gig port which is Up and forwarding on stack.

Brocade# debug port ten-gig Brocade# debug port hw-state hw-state monitor hw_state change Brocade# debug port hw-state

If port 1/1/32 is disabled, an output similar to the following is displayed.

Brocade(config-if-e10000-2/3/1)# disable Change port 2/3/1 hw_state from PORT_READY(7) to DISABLED(0) stack: 4040 2050A970 2050AA44 2060D498 20608BF8 2060B5A4 20576A90 20576C74 2057707C 202A50A8 20491E9C 20492DC0 204906D8 2050BF48 2027FD8C 20280888 202809F0 2015FCDC 2015FF44 20160B80

If port 1/1/32 is enabled, an output similar to the following is displayed.

Brocade(config-if-e10000-2/3/1)# enable Change port 2/3/1 hw_state from DISABLED(0) to SEEQ_INIT(1) stack: 4040 2050A970 2050AA44 2060D498 20608A34 2060B598 20576BC4 20576C74 2057707C 202A4F84 20491E9C 20492DC0 204906D8 2050BF48 2027FD8C 20280888 202809F0 2015FCDC 2015FF44 20160B80 Brocade(config-if-e10000-2/3/1)# change port 2/3/1 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

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 9 53-1003076-02

Page 22

Layer 1 debug commands

debug port up-down

Syntax: [no] debug port up-down decimal

This command monitors the status of the ports. The port status up, down, and up/down are indicated by 1, 2, and 3 respectively. The decimal variable refers to the status of the port.

Brocade# debug port up-down 1 Monitor port up Topology: Port 1/1/31 is connected to port 1/1/32.

The debug port up-down command disables or enables a port to get output information of the specified port.

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 port_down_indication. port=1/1/31, 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 Brocade(config-if-e1000-1/1/31)# port_down_indication. port=1/1/32, UNTAG, vlan-idx=3 stack: 4040 2050A970 2050AA44 2060A8FC 20608DA0 20609344 20609AFC 2055FA50 2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524 pp_link_change_final. port=1/1/32, up=0

If port 1/1/31 is enabled, an output similar to the following is displayed.

Brocade(config-if-e1000-1/1/31)# enable Brocade(config-if-e1000-1/1/31)# pp_link_change_final. port=1/1/31, up=1 port_up_indication. port=1/1/31, UNTAG, vlan-idx=1 stack: 4040 2050A970 2050AA44 2060A2C8 20609520 20609AFC 2055FA50 2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524 pp_link_change_final. port=1/1/32, up=1 port_up_indication. port=1/1/32, UNTAG, vlan-idx=3 stack: 4040 2050A970 2050AA44 2060A2C8 20609520 20609AFC 2055FA50 2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524

debug port vlan

Syntax: [no] debug port vlan decimal

This command monitors a specific VLAN and is used with the debug port up-down and debug port commands. The decimal variable refers to the number of the VLAN.

Brocade# debug port vlan 1 monitor vlan 1

Topology: Port 1/1/31 is connected to port 1/1/32.

Brocade# debug port vlan 2 monitor vlan 2 Brocade# debug port up-down up-down monitor port up/down event. 1: up, 2: down, 3: up/down

Brocade# debug port up-down 3 Monitor both port up and down

10 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 23

System debug commands

If port 1/1/31 is disabled, an output similar to the following is displayed.

Brocade(config-if-e1000-1/1/31)# disable port_down_indication. port=1/1/31, TAG, vlan-idx=4096 stack: 4040 2050A970 2050AA44 2060A8FC 20608BEC 2060B5A4 20576A90 20576C74 2057707C 202A50A8 20491E9C 20492DC0 204906D8 2050BF48 204A03C8 204A0418 2011BBC8 20047698 2011CF7C 5008 Brocade(config-if-e1000-1/1/31)# port_down_indication. port=1/1/32, TAG, vlan-idx=4096 stack: 4040 2050A970 2050AA44 2060A8FC 20608DA0 20609344 20609AFC 2055FA50 2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524 pp_link_change_final. port=1/1/32, up=0

If port 1/1/31 is enabled, an output similar to the following is displayed.

Brocade(config-if-e1000-1/1/31)# enable Brocade(config-if-e1000-1/1/31)# pp_link_change_final. port=1/1/31, up=1 port_up_indication. port=1/1/31, TAG, vlan-idx=4096 stack: 4040 2050A970 2050AA44 2060A2C8 20609520 20609AFC 2055FA50 2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524 pp_link_change_final. port=1/1/32, up=1 port_up_indication. port=1/1/32, TAG, vlan-idx=4096 stack: 4040 2050A970 2050AA44 2060A2C8 20609520 20609AFC 2055FA50 2050A214 200478DC 2011BBCC 20047698 2011CF7C 5008 135C8 18524

System debug commands

The following system debug commands enable debugging of the system services and device drivers.

debug system campram

Syntax: [no] debug system campram

This command traces Content Addressable Memory (CAM) or Parallel Random Access Machine (PRAM) operations.

Brocade# debug system campram cam/pram: Trace debugging is on

debug system optics

Syntax: [no] debug system optics

This command activates optical monitor debugging.

Brocade# debug system optics optics: Trace debugging is on

debug system poll

Syntax: [no] debug system poll

This command is used for backplane polling.

Brocade# debug system poll backplane-poll: Trace debugging is on

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 11 53-1003076-02

Page 24

Software licensing debug command

This section describes the debug command that generates software licensing information.

debug license

Syntax: [no] debug license

This command is used to display the package information on which the license has been loaded. The license information is encoded as Hexa decimal values and can be displayed only when the show license command is used with the license index; for example, show license unit 1 index 1.

Before enabling debugging::

Brocade# show license unit 1 index 1 License information for unit 1 license <1>: +license name: FCX-ADV-LIC-SW +lid: deyHHGLhGvz +license type: trial +status: active +license period: 30 days Trial license information: +days used: 0 +hours used: 0 +days left: 30 +hours left: 0

After enabling debugging::

Brocade# debug license License all debugging ON Brocade(config)# show license unit 1 index 1 License information for unit 1 license <1>: +license name: FCX-ADV-LIC-SW +lid: deyHHGLhGvz +license type: trial +status: active +license period: 30 days Trial license information: +license precedence: 1 +days used: 0 +hours used: 0 +days left: 30 +hours left: 0 Brocade license information: +pkg info: 0X200

12 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 25

Chapter

Layer 2 Diagnostics

This chapter contains the following sections:

•STP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

•RSTP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

•MSTP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

•DHCP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

•GVRP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

•MAC address debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

•MCT debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

•Packet-capture debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

•VXLAN debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

•Link aggregation debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

STP debug commands

The Spanning Tree Protocol (STP) eliminates Layer 2 loops in networks, by selectively blocking some ports and allowing other ports to forward traffic, based on the global (bridge) and local (port) parameters.

STP-related features, such as Rapid Spanning Tree Protocol (RSTP) and Per VLAN Spanning Tree (PVST), extend the operation of standard STP, enabling you to fine-tune standard STP and avoid some of its limitations.

You can enable or disable STP on a global basis (for the entire device), a port-based Virtual Local Area Network (VLAN) basis (for the individual Layer 2 broadcast domain), or an individual port basis. For more information on configuring STP, refer to the FastIron Configuration Guide.

A control protocol, such as STP, can block one or more ports in a protocol-based VLAN that uses a virtual routing interface to route to other VLANs. For IP VLANs and IP subnet VLANs, even though some of the physical ports of the virtual routing interface are blocked, the virtual routing interface can still route as long as at least one port in the protocol-based VLAN is not blocked by STP.

The following are the commands used to enable the STP debugging.

debug span all_802_1d_events

Syntax: [no] debug span all_802_1d_events vlan decimal

This command monitors information about all the events, timers, and packets on a specific VLAN. The decimal variable refers to the number of the VLAN.

The output from this command resembles the following example.

Brocade# debug span all_802_1d_events vlan 2 STP Enabling All events Debugging for VLAN 2

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 13 53-1003076-02

Page 26

STP debug commands

Brocade# STP: Transmitting Config BPDU - VLAN 2 - Port 1/1/5 0000 00 00 00 80000012f2dbfd80 00000004 8000002438154580 08 05 0100 1400 0200 0f00 STP: Transmitting Config BPDU - VLAN 2 - Port 1/1/6 0000 00 00 00 80000012f2dbfd80 00000004 8000002438154580 08 06 0100 1400 0200 0f00 STP: Transmitting Config BPDU - VLAN 2 - Port 1/1/5 0000 00 00 00 80000012f2dbfd80 00000004 8000002438154580 08 05 0100 1400 0200 0f00 STP: Transmitting Config BPDU - VLAN 2 - Port 1/1/6 0000 00 00 00 80000012f2dbfd80 00000004 8000002438154580 08 06 0100 1400 0200 0f00 STP: Transmitting Config BPDU - VLAN 2 - Port 1/1/5 0000 00 00 00 80000012f2dbfd80 00000004 8000002438154580 08 05 0100 1400 0200 0f00 STP: Transmitting Config BPDU - VLAN 2 - Port 1/1/6 0000 00 00 00 80000012f2dbfd80 00000004 8000002438154580 08 06 0100 1400 0200 0f00 STP: Transmitting Config BPDU - VLAN 2 - Port 1/1/5 0000 00 00 00 80000012f2dbfd80 00000004 8000002438154580 08 05 0100 1400 0200 0f00 STP: Transmitting Config BPDU - VLAN 2 - Port 1/1/6 0000 00 00 00 80000012f2dbfd80 00000004 8000002438154580 08 06 0100 1400 0200 0f00

Disabling the debug span all_802_1d_events on FCX: Brocade# no debug span all_802_1d_events vlan 2 STP : Disabling All 802.1w Debugging for VLAN 2

debug span config

Syntax: [no] debug span config vlan decimal

This command monitors information about STP Bridge Protocol Data Unit (BPDU) configuration on a specific VLAN. The decimal variable refers to the number of the VLAN.

If the configuration of VLAN 2 on the Brocade FCX is enabled, the output similar to the following is displayed.

Brocade# debug span config vlan 2 STP Enabling packets Debugging for VLAN 2

14 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 27

RSTP debug commands

NOTE

If the configuration of VLAN 2 on the Brocade FCX is disabled, the output similar to the following is displayed.

Brocade# no debug span config vlan 2 STP : Disabling Packets Debugging for VLAN 2

debug span timers

Syntax: [no] debug span timers vlan decimal

This command displays information about the specific STP timer events. The decimal variable refers to the number of the VLAN.

If the STP timer event on VLAN 2 of the Brocade FastIron device is enabled, the output similar to the following is displayed.

Brocade# debug span timers vlan 2 STP Enabling Timer Debugging for VLAN 2

Sample output: STP: Timer Alert - Forward Delay Timer expired On port 1/1/6(5) , VLAN 2 STP: Timer Alert - Forward Delay Timer expired On port 1/1/1(0) , VLAN 2 STP: Timer Alert - Forward Delay Timer expired On port 1/1/6(5) , VLAN 2 STP: Timer Alert - Message Age Timer expired On port 1/1/1(0) , VLAN 2 STP: Timer Alert - Message Age Timer expired On port 1/1/2(1) , VLAN 2 STP: Timer Alert - Forward Delay Timer expired On port 1/1/2(1) , VLAN 2 STP: Timer Alert - Forward Delay Timer expired On port 1/1/2(1) , VLAN 2

If the STP timer event on VLAN 2 of the Brocade FastIron device is disabled, the output similar to the following is displayed.

Brocade# no debug span timers vlan 2 STP Disabling Timer Debugging for VLAN 2

RSTP debug commands

RSTP provides rapid traffic reconvergence for point-to-point links within a few milliseconds (less than 500 milliseconds) following the failure of a bridge or bridge port. This reconvergence occurs more rapidly than that provided by STP because convergence in RSTP bridges is based on the explicit handshakes between designated ports and their connected root ports rather than on timer values. The debug 802.1w command displays some information about RSTP.

For RSTP debug commands, enter 4094 if STP is enabled. Enter the VLAN ID for Multiple Spanning Tree Protocol (MSTP). The CLI alerts the user if the VLAN ID does not exist.

debug 802.1w all_802_1w_events

Syntax: [no] debug 802.1w all_802_1w_events vlan decimal

This command debugs all the RSTP transactions, timers, and packets on a specific VLAN. The decimal variable refers to the number of the VLAN.

If the events are enabled, the output similar to the following is displayed.

Brocade# debug 802.1w all_802_1w_events vlan 2 RSTP Enabling All events Debugging for VLAN 2

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 15 53-1003076-02

Page 28

RSTP debug commands

Brocade# RSTP[daa69]: Timer Alert - helloWhen timer_expired On port 1/1/2(1) , VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/2(1) VLAN 2 RSTP: PTX =>ROLE is ALTERNATE or BACKUP , port 1/1/2(1), VLAN 2 RSTP[daa69]: Timer Alert - helloWhen timer_expired On port 1/1/9(8) , VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/9(8) VLAN 2 RSTP[daa69]: Tx RST Config BPDU Port 1/1/9(8) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00004e20 8000002438154580 08 09 0100 1400 0200 0f00 RSTP: Rcvd RST Config BPDU: Port 1/1/1(0) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 01 0000 0000 0000 0000 RSTP: PRT =>no valid transition found ,no error, port 1/1/1(0) VLAN 2 RSTP: Rcvd RST Config BPDU: Port 1/1/2(1) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 02 0000 0000 0000 0000 RSTP[daa7d]: Timer Alert - helloWhen timer_expired On port 1/1/2(1) , VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/2(1) VLAN 2 RSTP: PTX =>ROLE is ALTERNATE or BACKUP , port 1/1/2(1), VLAN 2 RSTP[daa7d]: Timer Alert - helloWhen timer_expired On port 1/1/9(8) , VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/9(8) VLAN 2 RSTP[daa7d]: Tx RST Config BPDU Port 1/1/9(8) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00004e20 8000002438154580 08 09 0100 1400 0200 0f00 RSTP: Rcvd RST Config BPDU: Port 1/1/1(0) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 01 0000 0000 0000 0000 RSTP: PRT =>no valid transition found ,no error, port 1/1/1(0) VLAN 2 RSTP: Rcvd RST Config BPDU: Port 1/1/2(1) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 02 0000 0000 0000 0000 RSTP[daa91]: Timer Alert - helloWhen timer_expired On port 1/1/2(1) , VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/2(1) VLAN 2 RSTP: PTX =>ROLE is ALTERNATE or BACKUP , port 1/1/2(1), VLAN 2 RSTP[daa91]: Timer Alert - helloWhen timer_expired On port 1/1/9(8) , VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/9(8) VLAN 2 RSTP[daa91]: Tx RST Config BPDU Port 1/1/9(8) VLAN 2

If the events are disabled, the output similar to the following is displayed.

Brocade# no debug 802.1w all_802_1w_events vlan 2 RSTP Disabling All 802.1w Debugging for VLAN 2

debug 802.1w messages

Syntax: [no] debug 802.1w messages vlan decimal

This command displays BPDU information on a VLAN. The decimal variable refers to the number of the VLAN.

If the 802.1w messages are enabled, an output similar to the following is displayed.

Brocade# debug 802.1w messages vlan 2 RSTP Enabling packets Debugging for VLAN 2

Brocade# RSTP: Rcvd RST Config BPDU: Port 1/1/1(0) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 01 0000 0000 0000 0000 RSTP: Rcvd RST Config BPDU: Port 1/1/2(1) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000

16 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 29

RSTP debug commands

80000012f2dbfd80 08 02 0000 0000 0000 0000 RSTP[db06d]: Tx RST Config BPDU Port 1/1/9(8) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00004e20 8000002438154580 08 09 0100 1400 0200 0f00 RSTP: Rcvd RST Config BPDU: Port 1/1/1(0) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 01 0000 0000 0000 0000 RSTP: Rcvd RST Config BPDU: Port 1/1/2(1) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 02 0000 0000 0000 0000 RSTP[db081]: Tx RST Config BPDU Port 1/1/9(8) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00004e20 8000002438154580 08 09 0100 1400 0200 0f00 RSTP: Rcvd RST Config BPDU: Port 1/1/1(0) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 01 0000 0000 0000 0000 RSTP: Rcvd RST Config BPDU: Port 1/1/2(1) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00000000 80000012f2dbfd80 08 02 0000 0000 0000 0000 RSTP[db095]: Tx RST Config BPDU Port 1/1/9(8) VLAN 2 0000 02 02 7e 80000012f2dbfd80 00004e20 8000002438154580 08 09 0100 1400 0200 0f00

If the 802.1w messages are disabled, the output similar to the following is displayed.

Brocade# no debug 802.1w messages valn 2 RSTP Disabling Packets Debugging for VLAN 2

debug 802.1w timer

Syntax: [no] debug 802.1w timer vlan decimal

This command debugs the RSTP (802.1w) timer expiration. The decimal variable refers to the number of the VLAN.

If the timer is enabled, an output similar to the following is displayed.

Brocade# debug 802.1w timer vlan 2

Brocade# RSTP[db6fd]: Timer Alert - helloWhen timer_expired On port 1/1/2(1) , VLAN 2 RSTP[db6fd]: Timer Alert - helloWhen timer_expired On port 1/1/9(8) , VLAN 2 RSTP[db711]: Timer Alert - helloWhen timer_expired On port 1/1/2(1) , VLAN 2 RSTP[db711]: Timer Alert - helloWhen timer_expired On port 1/1/9(8) , VLAN 2 RSTP[db725]: Timer Alert - helloWhen timer_expired On port 1/1/2(1) , VLAN 2 RSTP[db725]: Timer Alert - helloWhen timer_expired On port 1/1/9(8) , VLAN 2 RSTP[db739]: Timer Alert - helloWhen timer_expired On port 1/1/2(1) , VLAN 2

If the timer is disabled, the output similar to the following is displayed.

Brocade# no debug 802.1w timer vlan 2 RSTP Disabling Timer Debugging for VLAN 2

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 17 53-1003076-02

Page 30

MSTP debug commands

debug 802.1w transitions

Syntax: [no] debug 802.1w transitions vlan decimal

This command debugs the RSTP state machine transitions. The decimal variable refers to the number of the VLAN.

If the 802.1w transtitions are enabled, an output similar to the following is displayed.

Brocade# debug 802.1w transitions vlan 2 RSTP Enabling Events Debugging for VLAN 2

Brocade# RSTP: PRT =>no valid transition found ,no error, port 1/1/1(0) VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/2(1) VLAN 2 RSTP: PTX =>ROLE is ALTERNATE or BACKUP , port 1/1/2(1), VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/9(8) VLAN 2 RSTP: PRT =>no valid transition found ,no error, port 1/1/1(0) VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/2(1) VLAN 2 RSTP: PTX =>ROLE is ALTERNATE or BACKUP , port 1/1/2(1), VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/9(8) VLAN 2 RSTP: PRT =>no valid transition found ,no error, port 1/1/1(0) VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/2(1) VLAN 2 RSTP: PTX =>ROLE is ALTERNATE or BACKUP , port 1/1/2(1), VLAN 2 RSTP: PTX entering the Periodic state , port 1/1/9(8) VLAN 2

If the 802.1w transtitions are disabled, the output similar to the following is displayed.

Brocade# no debug 802.1w transitions vlan 2 RSTP Disabling Events Debugging for VLAN 2

MSTP debug commands

With Multiple Spanning Tree Protocol (MSTP), the entire network runs a common instance of RSTP. Within the common instance, one or more VLANs can be individually configured into distinct regions. The entire network runs the Common Spanning Tree (CST) instance and the regions run a local instance, or Internal Spanning Tree (IST). Because the CST treats each IST as a single bridge, ports are blocked to prevent loops that might occur within an IST and also throughout the CST. In addition, MSTP can coexist with individual devices running STP or RSTP in the Common and Internal Spanning Tree instance (CIST). With the exception of the provisions for multiple instances, MSTP operates exactly like RSTP.

The following MSTP debug commands are used for debugging information.

debug mstp bpdu

Syntax: [no] debug mstp bpdu

This command records and displays information in conjunction with the debug mstp enable and debug mstp events commands. When the debug mstp bpdu command is enabled, it monitors MSTP BPDUs.

If this command is enabled, an output similar to the following is displayed.

Brocade# debug mstp bpdu MSTP Bpdu debugging ON

Brocade# debug mstp enable

Brocade# MSTP[0xeb217]: PRX RECEIVE->RECEIVE - Port 1/1/1

18 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 31

MSTP debug commands

MST 0, Port 1/1/1 - received BPDU

(802.1s) 0000 03 02 7c 80000012f2dbfd80 00000000 80000012f2dbfd80 00000000 8001 0000 0014 0002 000f 80000012f2dbfd80 14 {0xac36177f50283cd4b83821d8ab26de62} MSTP[0xeb217]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/1 MSTP[0xeb217]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/1, rcvdInfoWhile 5->7 MSTP[0xeb217]: PRX RECEIVE->RECEIVE - Port 1/1/2 MST 0, Port 1/1/2 - received BPDU [0xeb217] (802.1s) 0000 03 02 3c 80000012f2dbfd80 00000000 80000012f2dbfd80 00000000 8002 0000 0014 0002 000f 80000012f2dbfd80 14 {0xac36177f50283cd4b83821d8ab26de62} MSTP[0xeb217]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/2 MSTP[0xeb217]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/2, rcvdInfoWhile 5->7 MSTP[0xeb21b]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/1 MSTP[0xeb21b]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/2 MSTP[0xeb22b]: PRX RECEIVE->RECEIVE - Port 1/1/1 MST 0, Port 1/1/1 - received BPDU [0xeb22b] (802.1s) 0000 03 02 7c 80000012f2dbfd80 00000000 80000012f2dbfd80 00000000 8001 0000 0014 0002 000f 80000012f2dbfd80 14 {0xac36177f50283cd4b83821d8ab26de62} MSTP[0xeb22b]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/1 MSTP[0xeb22b]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/1, rcvdInfoWhile 5->7 MSTP[0xeb22b]: PRX RECEIVE->RECEIVE - Port 1/1/2 MST 0, Port 1/1/2 - received BPDU [0xeb22b] (802.1s) 0000 03 02 3c 80000012f2dbfd80 00000000 80000012f2dbfd80 00000000 8002 0000 0014 0002 000f 80000012f2dbfd80 14 {0xac36177f50283cd4b83821d8ab26de62} MSTP[0xeb22b]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/2 MSTP[0xeb22b]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/2, rcvdInfoWhile 5->7 MSTP[0xeb22f]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/1 MSTP[0xeb22f]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/2 MSTP[0xeb23f]: PRX RECEIVE->RECEIVE - Port 1/1/1 MST 0, Port 1/1/1 - received BPDU [0xeb23f] (802.1s) 0000 03 02 7c 80000012f2dbfd80 00000000 80000012f2dbfd80 00000000 8001 0000 0014 0002 000f 80000012f2dbfd80 14 {0xac36177f50283cd4b83821d8ab26de62} MSTP[0xeb23f]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/1 MSTP[0xeb23f]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/1, rcvdInfoWhile 5->7 MSTP[0xeb23f]: PRX RECEIVE->RECEIVE - Port 1/1/2 MST 0, Port 1/1/2 - received BPDU [0xeb23f] (802.1s) 0000 03 02 3c 80000012f2dbfd80 00000000 80000012f2dbfd80 00000000 8002 0000 0014 0002 000f 80000012f2dbfd80 14 {0xac36177f50283cd4b83821d8ab26de62} MSTP[0xeb23f]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/2 MSTP[0xeb23f]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/2, rcvdInfoWhile 5->7 MSTP[0xeb243]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/1 MSTP[0xeb243]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/2 MSTP[0xeb253]: PRX RECEIVE->RECEIVE - Port 1/1/1 MST 0, Port 1/1/1 - received BPDU [0xeb253] (802.1s) 0000 03 02 7c 80000012f2dbfd80 00000000 80000012f2dbfd80 00000000 8001 0000 0014 0002 000f 80000012f2dbfd80 14 {0xac36177f50283cd4b83821d8ab26de62}

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 19 53-1003076-02

Page 32

MSTP debug commands

debug mstp events

Syntax: [no] debug mstp events

This command displays MSTP state machine events. It monitors any MSTP events that take place.

Brocade# debug mstp events MSTP Event debugging ON

If MSTP events are enabled, an output similar to the following is displayed.

Brocade# debug mstp enable Brocade# MSTP[0xeda7f]: PRX RECEIVE->RECEIVE - Port 1/1/1 MSTP[0xeda7f]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/1 MSTP[0xeda7f]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/1, rcvdInfoWhile 5->7 MSTP[0xeda7f]: PRX RECEIVE->RECEIVE - Port 1/1/2 MSTP[0xeda7f]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/2 MSTP[0xeda7f]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/2, rcvdInfoWhile 5->7 MSTP[0xeda89]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/1 MSTP[0xeda89]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/2 MSTP[0xeda93]: PRX RECEIVE->RECEIVE - Port 1/1/1 MSTP[0xeda93]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/1 MSTP[0xeda93]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/1

If MSTP events are disabled, an output similar to the following is displayed.

Brocade# no debug mstp events MSTP Event debugging OFF

debug mstp level

Syntax: [no] debug mstp level decimal

This command monitors MSTP. Level 3 gives more information than level 2, and level 0 gives no information. The decimal variable refers to the level of MSTP.

Brocade# debug mstp level 2 Configuration :

Brocade# [ebd95] MSTP_RX[pid=#0] *** [ebd95] MSTP_RX[pid=#0] done (region) *** [ebd95] MSTP_RX[pid=#1] *** [ebd95] MSTP_RX[pid=#1] done (region) *** [ebda9] MSTP_RX[pid=#0] *** [ebda9] MSTP_RX[pid=#0] done (region) *** [ebda9] MSTP_RX[pid=#1] *** [ebda9] MSTP_RX[pid=#1] done (region) *** [ebdbd] MSTP_RX[pid=#0] *** [ebdbd] MSTP_RX[pid=#0] done (region) *** [ebdbd] MSTP_RX[pid=#1] *** [ebdbd] MSTP_RX[pid=#1] done (region) *** [ebdd1] MSTP_RX[pid=#0] *** [ebdd1] MSTP_RX[pid=#0] done (region) *** [ebdd1] MSTP_RX[pid=#1] *** [ebdd1] MSTP_RX[pid=#1] done (region) *** [ebde5] MSTP_RX[pid=#0] *** [ebde5] MSTP_RX[pid=#0] done (region) *** [ebde5] MSTP_RX[pid=#1] ***

20 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 33

MSTP debug commands

If the MSTP level 3 is enabled, an output similar to the following is displayed.

Brocade# debug mstp level 3

Brocade# [ebf4d] MSTP_RX[pid=#0] *** cist_Rx[ebf4d] CIST, Port(#0) [ebf4d] MSTP_RX[pid=#0] done (region) *** [ebf4d] MSTP_RX[pid=#1] *** cist_Rx[ebf4d] CIST, Port(#1) [ebf4d] MSTP_RX[pid=#1] done (region) *** [ebf61] MSTP_RX[pid=#0] *** cist_Rx[ebf61] CIST, Port(#0) [ebf61] MSTP_RX[pid=#0] done (region) *** [ebf61] MSTP_RX[pid=#1] *** cist_Rx[ebf61] CIST, Port(#1) [ebf61] MSTP_RX[pid=#1] done (region) *** n[ebf75] MSTP_RX[pid=#0] *** cist_Rx[ebf75] CIST, Port(#0) [ebf75] MSTP_RX[pid=#0] done (region) *** [ebf75] MSTP_RX[pid=#1] *** cist_Rx[ebf75] CIST, Port(#1) [ebf75] MSTP_RX[pid=#1] done (region) ***

debug mstp msti

Syntax: [no] debug mstp msti decimal

This command displays information for a specific MSTP instance. The decimal variable specifies the value 0 for CIST and from 1 through 4094 for the Multiple Spanning Tree Instance (MSTI).

Brocade# debug mstp msti 0 MSTP debugging turned on for instances 0

If this command is enabled, an output similar to the following is displayed.

Brocade# debug mstp msti 2 MSTP debugging turned on for instances 2 ,0

Brocade# debug mstp enable Brocade# debug mstp events MSTP Event debugging ON

Brocade# MSTP[0x175f15]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/1 MSTP[0x175f15]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/2 MSTP[0x175f21]: PRX RECEIVE->RECEIVE - Port 1/1/1 MSTP[0x175f21]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/1 MSTP[0x175f21]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/1, rcvdInfoWhile 5->7 MSTP[0x175f21]: PIM CURRENT->RECEIVE - MST 2, Port 1/1/1 MSTP[0x175f21]: PIM RECEIVE->REPEATED_DESIGNATED - MST 2, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileMsti mst=2, Port 1/1/1, rcvdInfoWhile 4->7 MSTP[0x175f21]: PRX RECEIVE->RECEIVE - Port 1/1/2 MSTP[0x175f21]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/2 MSTP[0x175f21]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/2, rcvdInfoWhile 5->7 MSTP[0x175f21]: PIM CURRENT->RECEIVE - MST 2, Port 1/1/2 MSTP[0x175f21]: PIM RECEIVE->REPEATED_DESIGNATED - MST 2, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileMsti mst=2, Port 1/1/2, rcvdInfoWhile 4->7 MSTP[0x175f29]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/1 MSTP[0x175f29]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/2 noMSTP[0x175f35]: PRX RECEIVE->RECEIVE - Port 1/1/1 MSTP[0x175f35]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/1

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 21 53-1003076-02

Page 34

MSTP debug commands

MSTP[0x175f35]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/1, rcvdInfoWhile 5->7 MSTP[0x175f35]: PIM CURRENT->RECEIVE - MST 2, Port 1/1/1 MSTP[0x175f35]: PIM RECEIVE->REPEATED_DESIGNATED - MST 2, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileMsti mst=2, Port 1/1/1, rcvdInfoWhile 4->7 MSTP[0x175f35]: PRX RECEIVE->RECEIVE - Port 1/1/2 MSTP[0x175f35]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/2 MSTP[0x175f35]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/2, rcvdInfoWhile 5->7 MSTP[0x175f35]: PIM CURRENT->RECEIVE - MST 2, Port 1/1/2 MSTP[0x175f35]: PIM RECEIVE->REPEATED_DESIGNATED - MST 2, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileMsti mst=2, Port 1/1/2, rcvdInfoWhile 4->7 deMSTP[0x175f3d]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/1 MSTP[0x175f3d]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/2 bug msMSTP[0x175f49]: PRX RECEIVE->RECEIVE - Port 1/1/1 MSTP[0x175f49]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/1 MSTP[0x175f49]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/1, rcvdInfoWhile 5->7 MSTP[0x175f49]: PIM CURRENT->RECEIVE - MST 2, Port 1/1/1 MSTP[0x175f49]: PIM RECEIVE->REPEATED_DESIGNATED - MST 2, Port 1/1/1 MSTP: mstp_updtRcvdInfoWhileMsti mst=2, Port 1/1/1, rcvdInfoWhile 4->7 MSTP[0x175f49]: PRX RECEIVE->RECEIVE - Port 1/1/2 MSTP[0x175f49]: PIM CURRENT->RECEIVE - MST 0, Port 1/1/2 MSTP[0x175f49]: PIM RECEIVE->REPEATED_DESIGNATED - MST 0, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileCist mst=0, Port 1/1/2, rcvdInfoWhile 5->7 MSTP[0x175f49]: PIM CURRENT->RECEIVE - MST 2, Port 1/1/2 MSTP[0x175f49]: PIM RECEIVE->REPEATED_DESIGNATED - MST 2, Port 1/1/2 MSTP: mstp_updtRcvdInfoWhileMsti mst=2, Port 1/1/2, rcvdInfoWhile 4->7 tpMSTP[0x175f51]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/1 MSTP[0x175f51]: PTX IDLE->TRANSMIT_PERIODIC - Port 1/1/2 eventMSTP[0x175f5d]: PRX RECEIVE->RECEIVE - Port 1/1/1

debug mstp port-level

Syntax: [no] debug mstp port-level decimal

This command displays the information about the hardware level of the port on which the MSTP is running. The port level determines the level of the information. The decimal variable refers to the level of the port.

Brocade# debug mstp port-level 1

Configuration for port-level 1 : Brocade# debug mstp port-level DECIMAL 0 -- print nothing Brocade# debug mstp port-level 1 Brocade# configure terminal Brocade(config)# interface ethernet 1/1/1 Brocade(config-if-e1000-1/1/1)# disable Brocade(config-if-e1000-1/1/1)# enable Brocade(config-if-e1000-1/1/1)# ^Z

debug mstp state

Syntax: [no] debug mstp state

This command displays information about the MSTP port state events.

Brocade# debug mstp state MSTP Port State debugging ON

22 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 35

DHCP debug commands

debug mstp verbose

Syntax: [no] debug mstp verbose

This command displays the MSTP debug information in the verbose mode.

Brocade# debug mstp verbose MSTP debugging set to VERBOSE mode

debug mstp show

Syntax: debug mstp show

This command displays the current MSTP debug parameters that are enabled.

Brocade# debug mstp show mstp debug is on because of enabled, level or port-level level 4 parameters: Brief, StateMachineEvents BpduEvents are being tracked Ports: All MSTP instances: 0

If this command is enabled, an output similar to the following is displayed.

Brocade#debug mstp show mstp debug is off because enabled=0, level=0 & port-level=0 parameters: Brief, No events being tracked Ports: ethe 1/1/1 MSTP instances: All

DHCP debug commands

These commands are used to debug the various Dynamic Host Configuration Protocol (DHCP) client features.

debug dhcp-client alarms

Syntax: [no] debug dhcp-client alarms

This command displays the debugging of the DHCP client on a particular port ID.

Brocade#debug dhcp-client alarms "DHCPC: failed to initialize port; dhcpc unable to continue” "DHCPC: failed to initialize protocol timer" "DHCPC: no tftp server address or name found. unable to download configuration file” "DHCPC: unable to construct dns request” "DHCPC: dns failed to resolve tftp server name” “DHCPC: dns aborted” “DHCPC: No DHCP Servers found on any ports” "DHCPC: No DHCP Servers found on any ports" "DHCPC: setting 0 seconds lease time" "DHCPC: setting 0 seconds lease time on port port-id" "DHCPC: No DHCP Servers found on any ports" "DHCPC: failed to allocate a dhcpc packet on port port-id" "DHCPC: failed to send message on port port-id" "DHCPC: failed to allocate a dhcpc packet on port port-id" "DHCPC: failed to send message on port port-id " "DHCPC: get_an_ip_send_packet () failed on port port-id"

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 23 53-1003076-02

Page 36

DHCP debug commands

debug dhcp-client events

Syntax: [no] debug dhcp-client events

This command displays information about DHCP client events related to configuration.

Brocade# debug dhcp-client events "DHCPC: failed to delete static ip-address to ip-address" "DHCPC: failed to set the port ip-address to ip-address; subnet mask ip-address" "DHCPC: changing port port-id state from REQUEST to BOUND" "DHCPC: exceeds maximum some-number DNS servers" "DHCPC: added ip-address dns-server address" "DHCPC: failed to set the port ip-address to ip-address; subnet mask ip-address" "DHCPC: TFTP timeout error for bootfile name %s" "DHCPC: TFTP client busy" "DHCPC: TFTP error wrong file type" "DHCPC: TFTP long file name error" "DHCPC: TFTP vlan-id invalid" "DHCPC: TFTP flash write errors" "DHCPC: TFTP error out of buffer space" "DHCPC: TFTP flash read error" "DHCPC: TFTP flash preparation for read failed" "DHCPC: TFTP flash preparation for write failed" "DHCPC: %s failed to save running-configuration" "DHCPC: changing protocol from running to stopped" "DHCPC: changing protocol from stopped to running" "DHCPC: Auto update in progress, cannot change DHCP client state on port port-id " "DHCPC: invalid parameter for " "DHCPC: dhcp_get_next_port() bad port number port-id" "DHCPC: sent DHCP-REQUEST message on port port-id \” "DHCPC: sent DHCP-RENEWING message on port port-id” "DHCPC: sent DHCP-REBINDING message on port port-id " "DHCPC: sent DHCP-RELEASE message on port port-id " "DHCPC: received packet port port-id" "DHCPC: received bad packet port port-id, no DHCP END OPT found" "DHCPC: received offer message on port port-id" "DHCPC: recieved non matching 'xid' (0x%X) in offer message" "DHCPC: changing port port-id state from INIT-SELECTING to INIT-SELECTING" "DHCPC: changing port port-id state from INIT-SELECTING to REQUEST" "DHCPC: received DHCPCACK message on port port-id" "DHCPC: recieved non matching 'xid'(0x%X) in DHCPCACK message" "DHCPC: changing timer-event to SEEKING_CONFIGURATION_AND_WAITING_FOR_OFFERS" "DHCPC: recieved non matching 'xid'(0x%X) in DHCPNAK message" "DHCPC: deleting existing ip address configuration on port port-id" "DHCPC: received DHCPNAK packet on port port-id” “DHCPC: changing port port-id state from REQUEST to INIT-SELECTING” “DHCPC: received DHCPCOFFER packet on port port-id> while in bound state” "DHCPC: received DHCPCREQUEST packet on port port-id while in bound state" "DHCPC: received DHCPCDECLINE packet on port port-id while in bound state" "DHCPC: received DHCPCACK packet on port port-id while in bound state" "DHCPC: received DHCPCNAK packet on port port-id while in bound state" "DHCPC: received DHCPCRELEASE packet on port port-id while in bound state" "DHCPC: received DHCPCINFORM packet on port port-id while in bound state" "DHCPC: received DHCPCINFORM packet on port port-id while in bound state" "DHCPC: received unknown packet on port port-id while in bound state" "DHCPC: received DHCPACK packet in renewal-state on port port-id" "DHCPC: received non matching 'xid'(0x%X) in RENEWAL message" "DHCPC: TFTP flash read error" "DHCPC: changing port port-id state from RENEWING to BOUND" "DHCPC: received non matching 'xid'(0x%X) in DHCPNAK message"

24 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 37

GVRP debug commands

"DHCPC: received DHCPNAK packet in renewal-state on port port-id" "DHCPC: changing port port-id state from RENEWING to INIT-SELECTING" "DHCPC: received DHCPACK packet in rebind-state on port port-id" "DHCPC: received non matching 'xid'(0x%X) in REBIND message" "DHCPC: changing port port-id state from REBINDING to BOUND" "DHCPC: received non matching 'xid'(0x%X) in DHCPNAK message" "DHCPC: received DHCPNAK packet in renewal-state on port port-id" "DHCPC: changing port port-id state from REBIND to INIT-SELECTING" "DHCPC: sending packet port port-id" "DHCPC: send completion called on port: port-id" "DHCPC: Freeing packet" "DHCPC: unable to get some-number option from dhcp message from port port-id" "DHCPC: received server id address opton: ip-address from port port-id" "DHCPC: received lease-time option: some-number from port port-id" "DHCPC: received domain-name option: %s from port port-id" "DHCPC: received dns-server address option: ip-address from port port-id" "DHCPC: received default-router address option: ip-address from port port-id" "DHCPC: received TFTP server name option: %s from port port-id" "DHCPC: received TFTP server address opton: ip-address from port port-id" "DHCPC: received Bootfile name option: %s from port port-id" "DHCPC: received 'hostname' option: %s from port port-id" "DHCPC: received maximum message size option: some-number from port port-id" "DHCPC: lease timer events called with invalid port" "DHCPC: changing port port-id state from BOUND to REBINDING" "DHCPC: changing port port-id state from BOUND to RENEWING" "DHCPC: deleting existing ip address configuration on port port-id" "DHCPC: changing port port-id state from REQUESTING to INIT-SELECTING" "DHCPC: failed to renew ip address with dhcp server; continuing with lease period" "DHCPC: changing port port-id state from REBINDING to INIT_SELECTING" "DHCPC: changing port port-id state from REBINDING to REQUESTING"

GVRP debug commands

The GARP VLAN Registration Protocol (GVRP) debugging can be enabled by using the debug gvrp command.

debug gvrp packets

Syntax: [no] debug gvrp packets

This command enables the debugging of GVRP packets.

Brocade# debug gvrp packets GVRP: Packets debugging is on GVRP: 0x2095ced4: 01 80 c2 00 00 21 00 e0 52 ab 87 40 00 3a 42 42 GVRP: 0x2095cee4: 03 00 01 01 02 00 04 05 00 02 04 05 00 07 04 05 GVRP: 0x2095cef4: 00 09 04 05 00 0b 04 02 03 e9 04 01 03 eb 04 01 GVRP: 0x2095cf04: 03 ec 04 01 03 ef 04 01 03 f1 04 01 05 dd 04 01 GVRP: 0x2095cf14: 09 cb 04 01 0f a1 00 00 GVRP: Port 2/1 RCV GVRP: 0x2095ced4: 01 80 c2 00 00 21 00 e0 52 ab 87 40 00 28 42 42 GVRP: 0x2095cee4: 03 00 01 01 04 02 03 e9 04 01 03 eb 04 01 03 ec GVRP: 0x2095cef4: 04 01 03 ef 04 01 03 f1 04 01 05 dd 04 01 09 cb GVRP: 0x2095cf04: 04 01 0f a1 00 00 GVRP: Port 2/1 TX GVRP: 0x207651b8: 01 80 c2 00 00 21 00 04 80 2c 0e 20 00 3a 42 42 GVRP: 0x207651c8: 03 00 01 01 02 00 04 05 03 e9 04 05 03 eb 04 05 GVRP: 0x207651d8: 03 ec 04 05 03 ef 04 05 03 f1 04 05 05 dd 04 05

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 25 53-1003076-02

Page 38

MAC address debug commands

GVRP: 0x207651e8: 09 cb 04 05 0f a1 04 02 00 02 04 01 00 07 04 01 GVRP: 0x207651f8: 00 09 04 01 00 0b 00 00 GVRP: Port 2/1 TX GVRP: 0x207651b8: 01 80 c2 00 00 21 00 04 80 2c 0e 20 00 18 42 42 GVRP: 0x207651c8: 03 00 01 01 04 02 00 02 04 01 00 07 04 01 00 09 GVRP: 0x207651d8: 04 01 00 0b 00 00

MAC address debug commands

debug mac

Syntax: [no] debug mac

This command enables the Media Access Control (MAC) address debugging action.

Brocade# debug mac MAC DB: Action debugging is on mac_action_request: done->

MA - Normal, ALL_SYST, FLUSH Ports: All Ports Vlans: All Vlans stack: 20B89ED4 2028D708 2028D8A0 201AB040 20C2D58C 20C2EA48 20C2D6DC 20C2EDA4 20C2B2B8 20B8B3A8 2076C3EC 2076C448 20590734 205146FC 20592568 5010 15B4C 1AAD8 Brocade# aging_timer. call mac_action_handler()

MA - Normal, ALL_SYST, FLUSH Ports: All Ports Vlans: All Vlans stack: 20B89ED4 2028D708 20C6FAB0 20B894BC 20514924 20590738 205146FC 20592568 5010 15B4C 1AAD8 mac_clear_request(). NO_ACTION, SPECIFIC stack: 20B89ED4 2028CD28 2028D1F0 20C6FAB4 20B894BC 20514924 20590738 205146FC 20592568 5010 15B4C 1AAD8

MCT debug commands

Multi-Chassis Trunking (MCT) provides link-level redundancy and load sharing in addition to increased capacity. If any one of the MCT cluster device fails, the data path remains operational through the other MCT cluster device without any disruption.

This section describes the debug commands that display MCT information.

debug cluster all

Syntax: [no] debug cluster all

This command enables or disables the MCT debugging information log.

If the debug cluster all command is enabled, the output similar to the following is displayed.

Brocade# debug cluster all MCT:: Enabling all debugs CLUSTER ALL debugging is now ON

Brocade# rstp_txRSTP(T=25364)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior

26 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 39

MCT debug commands

rstp_txRSTP(T=25364)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25365, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25384)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25384)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25385, VLAN=20,port=1/7) port-stp-state=FORWARDING CCP_PKT(T=25394): Receiving Packet from peer 10.1.1.2 CCP_PKT(T=25394): Packet Info:0100000c000000080003000400000056 CCP_PKT(T=25394): Receiving Packet from peer 10.1.1.2, appId=0 (CCP_APPLICATION_CCP=0;CCP_APPLICATION_CLUSTER_MGR=1) CCP_PKT(T=25394): Packet Info:0100000c000000080003000400000056 CCP_PKT(T=25394):Processing ccp packet CCP_PKT(T=25394): Packet Info:0003000400000056 CCP_PKT(T=25394): Handling received keep alive message CCP_PKT(T=25394): Packet Info:0003000400000056 CLUSTER CCP_FSM(T=25394): Fsm7 got keepalive from 10.1.1.2 CLUSTER CCP:free data buf allocated packet count 1 buffer 2291f5be CLUSTER CCP:internal free data buf allocated packet count 0 bufer 2291f5be CLUSTER CCP:internal alloc data buf allocated packet count 1 buffer 2291f5be CLUSTER CCP:alloc data buf allocated packet count 1 buffer 2291f5be rstp_txRSTP(T=25404)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25404)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25405, VLAN=20,port=1/7) port-stp-state=FORWARDING CLUSTER CCP_FSM(T=25413): Fsm12 10.1.1.2 sending keepalive CLUSTER CCP PEER(T=25413): Make keep alive message -> CCP_PKT(T=25413): Sending Keep Alive message to peer CCP_PKT(T=25413): Packet Info:0100000c000000080003000400000056 CLUSTER CCP_FSM(T=25413): Fsm11 KeepAlive check for peer 10.1.1.2 rstp_txRSTP(T=25424)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25424)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25425, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25444)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25444)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25445, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25464)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25464)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25465, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25484)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25484)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25485, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25504)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25504)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25505, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25524)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 27 53-1003076-02

Page 40

MCT debug commands

rstp_txRSTP(T=25524)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25525, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25544)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25544)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25545, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25564)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25564)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25565, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25584)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25584)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25585, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25604)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25604)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25605, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25624)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25624)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25625, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25644)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25644)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25645, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25664)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25664)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25665, VLAN=20,port=1/7) port-stp-state=FORWARDING rstp_txRSTP(T=25684)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25684)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& rstputil_mct_handle_incoming_BPDU(T=25685, VLAN=20,port=1/7) port-stp-state=FORWARDING

Brocade# CCP_PKT(T=25694): Receiving Packet from peer 10.1.1.2 CCP_PKT(T=25694): Packet Info:0100000c000000080003000400000057 CCP_PKT(T=25694): Receiving Packet from peer 10.1.1.2, appId=0 (CCP_APPLICATION_CCP=0;CCP_APPLICATION_CLUSTER_MGR=1) CCP_PKT(T=25694): Packet Info:0100000c000000080003000400000057 CCP_PKT(T=25694):Processing ccp packet CCP_PKT(T=25694): Packet Info:0003000400000057 CCP_PKT(T=25694): Handling received keep alive message CCP_PKT(T=25694): Packet Info:0003000400000057 CLUSTER CCP_FSM(T=25694): Fsm7 got keepalive from 10.1.1.2 CLUSTER CCP:free data buf allocated packet count 1 buffer 2291f5be CLUSTER CCP:internal free data buf allocated packet count 0 bufer 2291f5be CLUSTER CCP:internal alloc data buf allocated packet count 1 buffer 2291f5be CLUSTER CCP:alloc data buf allocated packet count 1 buffer 2291f5be

28 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 41

MCT debug commands

Brocade# rstp_txRSTP(T=25704)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25704)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom&

Brocade# rstputil_mct_handle_incoming_BPDU(T=25705, VLAN=20,port=1/7) port-stp-state=FORWARDING no CLUSTER CCP_FSM(T=25713): Fsm12 10.1.1.2 sending keepalive CLUSTER CCP PEER(T=25713): Make keep alive message -> CCP_PKT(T=25713): Sending Keep Alive message to peer CCP_PKT(T=25713): Packet Info:0100000c000000080003000400000057 debug crstp_txRSTP(T=25724)(vlan=20,port=1/15) Tx on CCEP, MCT peer is superior rstp_txRSTP(T=25724)(vlan=20,port=1/15) Tx on CCEP while MCT peer is superior and UP, abandom& lurstputil_mct_handle_incoming_BPDU(T=25725, VLAN=20,port=1/7) port-stp-state=FORWARDING

If the debug cluster all command is disabled, the output similar to the following is displayed.

Brocade# no debug cluster all MCT:: disabling all debugs CLUSTER ALL debugging is now OFF

debug cluster ccp

• fsm - Enables CCP FSM debugging for a given peer IP or all peers.

• tcp - Enables CCP TCP debugging for a given peer IP or all peers.

• packets - Enables CCP packet debugging for a given peer IP or all peers.

• itc - Enables CCP ITC debugging .

• client - Enables CCP client related registration debugging.

• events - Enables CCP events debugging.

• memory - Enables CCP memory debugging.

This command enables debugging of all CCP FSM messages, CCP client registrations, CCP packet exchanges from clients, Keepalive messages and notifications, data buffer usage, and specific peer-related message exchanges. Command output resembles the following example.

Brocade# debug cluster ccp CLUSTER CCP debugging is on for all

============= Packet Receive ======================= SX_4#CCP_PKT(T=104981): Receiving Packet from peer 10.10.10.2 CCP_PKT(T=104981): Packet Info:0100001c000400180009001400010065012c0300000000008000002438 CCP_PKT(T=104981): Receiving Packet from peer 10.10.10.2, appId=4 (CCP_APPLICATION_CCP=0;CCP_APPLICATION_CLUSTER_MGR=1) CCP_PKT(T=104981): Packet Info:0100001c000400180009001400010065012c0300000000008000002438 CCP_PKT(T=104981): Passing packet to app 4 (cluster=1,mac=2,stp=4) CCP_PKT(T=104981): Packet Info:000400180009001400010065012c0300000000008000002438221b1a ================= Packet passed to specific client ====================== ccp_pass_pkt_to_client()(T=104981): cluster id 1, peer ip=168430082, STP msg CLUSTER CCP: free data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:internal free data buf allocated packet count 0 bufer 21a215e8 CLUSTER CCP:internal alloc data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:alloc data buf allocated packet count 1 buffer 21a215e8

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 29 53-1003076-02

Page 42

MCT debug commands

CCP_PKT(T=105001): Receiving Packet from peer 10.10.10.2 CCP_PKT(T=105001): Packet Info:0100001c000400180009001400010065012c0300000000008000002438 CCP_PKT(T=105001): Receiving Packet from peer 10.10.10.2, appId=4 (CCP_APPLICATION_CCP=0;CCP_APPLICATION_CLUSTER_MGR=1) CCP_PKT(T=105001): Packet Info:0100001c000400180009001400010065012c0300000000008000002438 CCP_PKT(T=105001): Passing packet to app 4 (cluster=1,mac=2,stp=4) CCP_PKT(T=105001): Packet Info:000400180009001400010065012c0300000000008000002438221b1a ccp_pass_pkt_to_client()(T=105001): cluster id 1, peer ip=168430082, STP msg CLUSTER CCP: free data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:internal free data buf allocated packet count 0 bufer 21a215e8 CLUSTER CCP:internal alloc data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:alloc data buf allocated packet count 1 buffer 21a215e8 CCP_PKT(T=105021): Receiving Packet from peer 10.10.10.2 CCP_PKT(T=105021): Packet Info:0100001c000400180009001400010065012c0300000000008000002438 CCP_PKT(T=105021): Receiving Packet from peer 10.10.10.2, appId=4 (CCP_APPLICATION_CCP=0;CCP_APPLICATION_CLUSTER_MGR=1) CCP_PKT(T=105021): Packet Info:0100001c000400180009001400010065012c0300000000008000002438 CCP_PKT(T=105021): Passing packet to app 4 (cluster=1,mac=2,stp=4) CCP_PKT(T=105021): Packet Info:000400180009001400010065012c0300000000008000002438221b1a ccp_pass_pkt_to_client()(T=105021): cluster id 1, peer ip=168430082, STP msg CLUSTER CCP: free data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:internal free data buf allocated packet count 0 bufer 21a215e8 CLUSTER CCP:internal alloc data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:alloc data buf allocated packet count 1 buffer 21a215e8 CCP_PKT(T=105041): Receiving Packet from peer 10.10.10.2 CCP_PKT(T=105041): Packet Info:0100001c000400180009001400010065012c0300000000008000002438 CCP_PKT(T=105041): Receiving Packet from peer 10.10.10.2, appId=4 (CCP_APPLICATION_CCP=0;CCP_APPLICATION_CLUSTER_MGR=1) CCP_PKT(T=105041): Packet Info:0100001c000400180009001400010065012c0300000000008000002438 CCP_PKT(T=105041): Passing packet to app 4 (cluster=1,mac=2,stp=4) CCP_PKT(T=105041): Packet Info:000400180009001400010065012c0300000000008000002438221b1a ccp_pass_pkt_to_client()(T=105041): cluster id 1, peer ip=168430082, STP msg CLUSTER CCP: free data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:internal free data buf allocated packet count 0 bufer 21a215e8 CLUSTER CCP:internal alloc data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:alloc data buf allocated packet count 1 buffer 21a215e8

SX_4#CCP_PKT(T=105059): Receiving Packet from peer 10.10.10.2 CCP_PKT(T=105059): Packet Info:0100000c00000008000300040000015f CCP_PKT(T=105059): Receiving Packet from peer 10.10.10.2, appId=0 (CCP_APPLICATION_CCP=0;CCP_APPLICATION_CLUSTER_MGR=1) CCP_PKT(T=105059): Packet Info:0100000c00000008000300040000015f CCP_PKT(T=105059):Processing ccp packet CCP_PKT(T=105059): Packet Info:000300040000015f CCP_PKT(T=105059): Not handling keepalive as keepalive_timeout is set. CCP_PKT(T=105059): Packet Info:000300040000015f ================= Data buffer usage ============================ CLUSTER CCP:free data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:internal free data buf allocated packet count 0 bufer 21a215e8 ================= Error notifications ============== CLUSTER CCP PEER(T=105059): Sending Error Notification 49

30 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 43

MCT debug commands

CCP_PKT(T=105059): Sending Notify message to peer CCP_PKT(T=105059): Packet Info:01000016000000120001000e0000015f00000031000000000000 CLUSTER CCP:internal alloc data buf allocated packet count 1 buffer 21a215e8 CLUSTER CCP:alloc data buf allocated packet count 1 buffer 21a215e8 =============== CCP State machine ============== CLUSTER CCP_FSM(T=105060): Fsm12 10.10.10.2 sending keepalive CLUSTER CCP PEER(T=105060): Make keep alive message -> =================== Send Keepalive ======================= CCP_PKT(T=105060): Sending Keep Alive message to peer CCP_PKT(T=105060): Packet Info:0100000c000000080003000400000160

If the debug cluster ccp command is disabled, the output similar to the following is displayed.

Brocade# no debug cluster ccp CCP debugging is off for all

debug cluster client-auto-detect

Syntax: [no] debug cluster client-auto-detect

This command displays debugging information related to cluster client auto detect functionality, as shown in the following example.

Brocade# debug cluster client-auto-detect CLUSTER AUTOCONFIG INFO - New Client: A-satya-000000147d80 with rbridge id: 3318 discovered on LACP port 4/17 CLUSTER AUTOCONFIG INFO - New Client: A-satya-000000c74d40 with rbridge id: 2668 discovered on Static port 3/13 CLUSTER AUTOCONFIG INFO - Port 3/14 added as Static interface to Client:A-satya-000000c74d40 LAG MCT-CCAC-LAG_1 deployed successfully! Spanning tree is disabled on CCEP port 4/17 of MCT Client: A-satya-000000147d80. CLUSTER AUTOCONFIG INFO - Port 4/17 is successfully programmed as client interface. Removing from autoconfig port list.

debug clLAG MCT-CCAC-LAG_2 deployed successfully! Spanning tree is disabled on CCEP port 3/13 of MCT Client: A-satya-000000c74d40. CLUSTER AUTOCONFIG INFO - Port 3/13 is successfully programmed as client interface. Removing from autoconfig port list. CLUSTER AUTOCONFIG INFO - Port 3/14 is successfully programmed as client interface. Removing from autoconfig port list. CLUSTER AUTOCONFIG INFO - Cluster 1 client auto-config process stopped

debug cluster config

Syntax: [no] debug cluster config

This command enables debugging for any addition or deletion of the clusters, addition or deletion of the clients, or exchange of cluster finite state machine (FSM) messages between the peer and the client isolation mode.

If the debug cluster config command is enabled, the output similar to the following is displayed.

Brocade# debug cluster config CLUSTER Config debugging is now ON Brocade# config terminal Brocade# cluster ABC 1 Brocade(config-cluster-ABC)# rbridge-id 200 Brocade(config-cluster-ABC)# session-vlan 100 Brocade(config-cluster-ABC)# icl icl1 ethernet 4/3

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 31 53-1003076-02

Page 44

MCT debug commands

Brocade(config-cluster-ABC)# peer 10.10.10.1 rbridge-id 100 icl icl1 Brocade(config-cluster-ABC)# deploy

============= cluster create =============== CLUSTER CCP:ccp_internal_create_cluster::Cluster 1 Configured. Brocade(config-cluster-ABC)# client c1uster Brocade(config-cluster-ABC-client-c1)# rbridge-id 300 Brocade(config-cluster-ABC-client-c1)# client-interface ethernet 4/13

=========== Client add ====================== clustercu_add_client_interface(cluseter=1,client_name=c1,client_port=4/13) clustermgr_add_cluster_client_port(cluseter=1,client_name=c1,client_port=4/13,add ) Brocade(config-cluster-ABC-client-c1)# deploy

===================== FSM Message ==================== clustermgr_send_loading_info_to_peer(cluster=1)(T=121842) >>>> clustermgr_send_vlanmask_to_peer && clustermgr_send_intf_mac_to_peer clustermgr_send_loading_info_to_peer(cluster=1)(T=121842) >>>> DONE

================ Client isolation mode config ============== Brocade(config-cluster-ABC)# client-isolation strict clustermgr_client_isolation_mode(cluster_id=1,mode=1)

If the debug cluster config command is disabled, the output similar to the following is displayed.

Brocade# no debug cluster config CLUSTER Config debugging is now OFF?

debug cluster fsm

Syntax: [no] debug cluster fsm client client_id

This command enables debugging of the MCT cluster FSM for a particular client. Any events that occur in the client such as CCEP Up/Down, remote CCEP Up/Down, or CCP Up/Down, are tracked. The client_id variable refers to the port number of the client.

Brocade# debug cluster fsm client 300 CLUSTER fsm debugging is now ON for client rbridge 300 =================== Local CCEP Down ===================

Brocade(config-if-e1000-4/13)# disable CLUSTER FSM: cluster id 1, client id 300, old state: Up, event: Local Down CLUSTER FSM: new state: Remote Up, master: FALSE Brocade(config-if-e1000-4/13)# CLUSTER FSM: Received CCRR message from peer when CCP is up

Brocade(config-if-e1000-4/13)# enable =================== Local CCEP UP ===================

Brocade(config-if-e1000-4/13)# CLUSTER FSM: cluster id 1, client id 300, old state: Remote Up, event: Local Up CLUSTER FSM: new state: Preforwarding Remote Up, master: FALSE =================== Remote CCEP Down =================== CLUSTER FSM: Received CCRR message from peer when CCP is up CLUSTER FSM: cluster id 1, client id 300, old state: Preforwarding Remote Up, event: CCRR Ack Rcvd CLUSTER FSM: new state: Up, master: FALSE CLUSTER FSM: Received CCRR message from peer when CCP is up CLUSTER FSM: cluster id 1, client id 300, old state: Up, event: Remote Down CLUSTER FSM: Cluster ABC (Id: 1), client c1 (RBridge Id: 300) - Remote client CCEP down CLUSTER FSM: new state: Local Up, master: FALSE

32 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 45

MCT debug commands

=================== Remote CCEP UP =================== CLUSTER FSM: Received CCRR message from peer when CCP is up CLUSTER FSM: cluster id 1, client id 300, old state: Local Up, event: Remote Up CLUSTER FSM: Cluster ABC (Id: 1), client c1 (RBridge Id: 300) - Remote client CCEP up CLUSTER FSM: new state: Up, master: FALSE ===================== CCP Down ============================ CLUSTER FSM: cluster id 1, peer rbridge id 100, old state: CCP Down, event: CCP Down CLUSTER FSM: cluster id 1, peer rbridge id 100, old state: CCP Down, event: CCP Down CLUSTER FSM: cluster id 1, peer rbridge id 100, old state: CCP Down, event: CCP Down CLUSTER FSM: cluster id 1, peer rbridge id 100, old state: CCP Down, event: CCP Down

======================== CCP getting established ========================== CLUSTER FSM: new state: Loading CLUSTER FSM: cluster id 1, peer rbridge id 100, old state: Loading, event: CCP Up CLUSTER FSM: cluster id 1, peer rbridge id 100, old state: Loading, event: CCP Up CLUSTER FSM: cluster id 1, peer rbridge id 100, old state: Loading, event: CCP Up CLUSTER FSM: Received Loading-Done message from peer CLUSTER FSM: cluster id 1, peer rbridge id 100, old state: Loading, event: Loading Done CLUSTER FSM: getting EVENT_ID_MCT_CCP_UP event CLUSTER FSM(T=121842)main: cluster id 1, client id 300, old state: Init, event: CCP Up CLUSTER FSM(T=121842)main: new state: Local Deploy, master: FALSE CLUSTER FSM: new state: CCP Up CLUSTER FSM: Received CCRR message from peer when CCP is up CLUSTER FSM: cluster id 1, client id 300, old state: Local Deploy, event: Remote Deploy CLUSTER FSM: Cluster ABC (Id: 1), client c1 (RBridge Id: 300) - Remote client deployed CLUSTER FSM: new state: Admin Up, master: FALSE CLUSTER FSM: Received CCRR message from peer when CCP is up

If the debug cluster fsm client command is disabled, the output similar to the following is displayed.

Brocade# no debug cluster fsm client 300 CLUSTER fsm debugging is now OFF for client rbridge 300

debug cluster intf-mac

Syntax: [no] debug cluster intf-mac

This command displays interface MAC debug information for the cluster as shown in the following example.

Brocade# debug cluster intf-mac CLUSTER ROUTER MAC(T=1791244): sent to peer rbridge id 2, base mac address

0000.0021.a500, number of mac addresses 1 CLUSTER ROUTER MAC(T=1791244): received from peer rbridge id 2, router mac address

0000.0083.3200, number of mac addresses 1

debug cluster mdup

Syntax: [no] debug cluster mdup

This command displays MDUP debug information for the cluster as shown in the following example.

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 33 53-1003076-02

Page 46

MCT debug commands

Brocade# debug cluster mdup CLUSTER MDUP: Send Vlan mask message to peer CLUSTER MDUP: Received vlan mask from peer for cluster 1 mdupmgr_proc_port_oper_status_change(port_id=3/13, oper_status=up, vlan=100 ) -> mdupmgr_proc_port_oper_status_change(port_id=3/13, oper_status=up, vlan=100 ), port is CCEP mdupmgr_proc_port_oper_status_change(port_id=3/13, oper_status=up, vlan=100 ), port is CCEP -> macmgr_move_mct_mac_from_icl_to_ccep CLUSTER MDUP: Moving MACs from ICL port to CCEP port 3/13 for client 2668 in VLAN 100 mdupmgr_proc_port_oper_status_change(port_id=3/13, oper_status=up, vlan=100 ) DONE mdupmgr_proc_port_oper_status_change(port_id=4/17, oper_status=up, vlan=100 ) -> mdupmgr_proc_port_oper_status_change(port_id=4/17, oper_status=up, vlan=100 ), port is CCEP mdupmgr_proc_port_oper_status_change(port_id=4/17, oper_status=up, vlan=100 ), port is CCEP -> macmgr_move_mct_mac_from_icl_to_ccep CLUSTER MDUP: Moving MACs from ICL port to CCEP port 4/17 for client 3318 in VLAN 100 mdupmgr_proc_port_oper_status_change(port_id=4/17, oper_status=up, vlan=100 ) DONE <<<<< mdupmgr_sync_static_mac_table >>> mdupmgr_sync_static_mac_table done, sync 0 entries mdupmgr_sync_mac_table(restart=yes,ccp_up_restart=yes)(T=95629) mac_mdup_sync_in_progress=0, start_mac_index=0, previous_loop_start_mac_index=0, g_mac_mdup_sync_delay=0 mdupmgr_sync_mac_table(restart=yes,ccp_up_restart=yes)(T=95629) DELAY SYNC (mac_mdup_sync_in_progress=1, start_mac_index=0, previous_loop_start_mac_index=0, g_mac_mdup_sync_delay=2)& CLUSTER MDUP: Convert CCR to CCL for cluster_id: 1, client rbridge id = 2668 macmgr_convert_ccr_to_ccl(cluster_id=1, port_id=3/13)(T=95629) client A-satya-000000c74d40 (hw_timer_gone=1 msec)& CLUSTER MDUP: Convert CCR to CCL for cluster_id: 1, client rbridge id = 3318 macmgr_convert_ccr_to_ccl(cluster_id=1, port_id=4/17)(T=95629) client A-satya-000000147d80 (hw_timer_gone=1 msec)& mdupmgr_sync_mac_table(restart=no,ccp_up_restart=no)(T=95630) mac_mdup_sync_in_progress=1, start_mac_index=0, previous_loop_start_mac_index=0, g_mac_mdup_sync_delay=2 mdupmgr_sync_mac_table(restart=no,ccp_up_restart=no)(T=95630) DELAY SYNC (mac_mdup_sync_in_progress=1, start_mac_index=0, previous_loop_start_mac_index=0, g_mac_mdup_sync_delay=3)& mdupmgr_sync_mac_table(restart=no,ccp_up_restart=no)(T=95631) mac_mdup_sync_in_progress=1, start_mac_index=0, previous_loop_start_mac_index=0, g_mac_mdup_sync_delay=3 mdupmgr_sync_mac_table(restart=no,ccp_up_restart=no)(T=95631) DELAY SYNC (mac_mdup_sync_in_progress=1, start_mac_index=0, previous_loop_start_mac_index=0, g_mac_mdup_sync_delay=4)&

debug cluster show

Syntax: [no] debug cluster show

This command displays debug flags for the cluster as shown in the following example.

Brocade# debug cluster show CLUSTER debugging is :ENABLED

CLUSTER ALL debugging is :OFF

CLUSTER IPC debugging is :OFF CLUSTER Hardware debugging is :OFF

34 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 47

MCT debug commands

CLUSTER Config debugging is :OFF CLUSTER FSM debugging is :OFF CLUSTER MDUP debugging is :ON CLUSTER interface mac debugging is :OFF CLUSTER Forwarding debugging is :OFF CLUSTER STP debugging is :OFF CLUSTER BPDU forwarding debugging is :OFF

CLUSTER CCP debugging is :OFF

debug cluster stp

Syntax: [no] debug cluster stp

This command enables debugging of STP and RSTP modules. The output details how the STP registers the ICL or CCEP ports. Changes occur while supporting MCT on STP, such as ICL guard, CCEP state sync, STP and CCP messages, and topology change messages are tracked. Command output resembles the following example.

Brocade# debug cluster stp CLUSTER STP debugging is now ON

Brocade(config-vlan-101)# spanning-tree 802-1w

STP -> INIT STP for bridge, vlan 10. Port mask 194 201 204 1168 1170 1173 to 1174 2000 2147 to 2149 2154 2157 2185 2187 to 2188 2192 to 2193 2195 to 2196 2201 2205 2368 to 2369 2371 to 2372 2377 2381 2387 to 2389 2394 2397 2425 2427 to 2428

Startup:: In initialize_bridge_spanning_tree::MCT enabled on this VLAN 101

Startup:: In initialize_bridge_spanning_tree:: MCT enabled Clearing ICL port

Searching for ICL and CCEP for this VLAN/STP

stputil_discover_mct:: ICL port is 4/3

Initialize Port 4/3. vlan 101 initialize_port(T=173641): icl-port guard timer cleared on port 4/3, VLAN 101

initialize_port:: Set ICL to FORWARDING. Vlan 101 port 4/3

Searching for ICL and CCEP for this VLAN/STP

Initialize Port 4/10. vlan 101 initialize_port(T=173641): icl-port guard timer cleared on port 4/10, VLAN 101

initialize_port:: Port is neither ICL/ CCEP of Root Bridge. Set to BLOCKING. Vlan 101 port 4/10

Searching for ICL and CCEP for this VLAN/STP

stputil_discover_mct::This is CCEP port 4/13

Initialize Port 4/13. vlan 101 initialize_port(T=173641): icl-port guard timer cleared on port 4/13, VLAN 101

initialize_port:: Set CCEP or root bridge to FORWARDING. Vlan 101 port 4/13 stputil_mct_send_ccep_state_to_peer(T=173641,vlan=101,port=204,state=FORWARDING) stputil_mct_send_ccep_state_to_peer(T=173641,vlan=101,port=204,state=FORWARDING) primary_port 4/13 --> stputil_mct_send_ccep_state_to_peer(T=173641,vlan=101,port=204,state=FORWARDING) primary_port 4/13 done

rstp_setup_this_bridge_values:: mct_enable = TRUE

rstputil_mct_enable_port.vlan 101 port 4/3

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 35 53-1003076-02

Page 48

MCT debug commands

rstputil_mct_enable_port:: port is trunk

rstputil_mct_enable_port. Per VLAN STP. VLAN 101 Port 4/3 mct_icl_port = TRUE

rstp_enable_port:: VLAN 101 port 4/3. skip_Initialize_RSTP_state_machines = 0.

rstp_enable_port:: PIM state 0. PRT state 0. PTX state 0. TCM state 0. PPM state

0. PST state 0

rstp_enable_port::rstp_role 0 rstp_selectedRole 0 state 5 rstp_infols 0 rstp_initialize_port(T=173641) VLAN101, port 4/3. Port is trunk. primary = 4/3 active stp port = 4/3 rstp_RoleSelection_State_Machine. set_flag 1 for vlan 101

New root:: vlan 101 INVALID rstp_RoleSelection_State_Machine. set_flag 2 for vlan 101

New root:: vlan 101 INVALID

Vlan 101 port 4/3. rstp_selectedRole = RSTP_DESIGNATED_PORT as rstp_infols == RSTP_PORT_INFO_STATE_AGED. rstp_RoleSelection_State_Machine. set_flag 2 for vlan 101

New root:: vlan 101 INVALID

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/3 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

rstp_port_Role_Transition_State_Machine:: port 4/3 vlan 101 role = 0 selected role = 3. old PRT state 529 new state 529. Designated_Port_transitions. rstp_enable_forwarding(T=173641) VLAN101, port 4/3

rstp_Port_State_Transition_State_Machine_Action: VLAN 101 Port 4/3. ICL port set to FWD.

rstputil_mct_enable_port.vlan 101 port 4/10 rstp_enable_port:: VLAN 101 port 4/10. skip_Initialize_RSTP_state_machines = 0.

rstp_enable_port:: PIM state 0. PRT state 0. PTX state 0. TCM state 0. PPM state

0. PST state 0

rstp_enable_port::rstp_role 0 rstp_selectedRole 0 state 2 rstp_infols 0 rstp_initialize_port(T=173641) VLAN101, port 4/10. Port is not trunk. rstp_RoleSelection_State_Machine. set_flag 2 for vlan 101

New root:: vlan 101 INVALID

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/3 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE rstp_RoleSelection_State_Machine. set_flag 2 for vlan 101

New root:: vlan 101 INVALID

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/3 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

Vlan 101 port 4/10. rstp_selectedRole = RSTP_DESIGNATED_PORT as rstp_infols == RSTP_PORT_INFO_STATE_AGED. rstp_RoleSelection_State_Machine. set_flag 2 for vlan 101

New root:: vlan 101 INVALID

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/3 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

36 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 49

MCT debug commands

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/10 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

rstp_port_Role_Transition_State_Machine:: port 4/10 vlan 101 role = 0 selected role = 3. old PRT state 529 new state 529. Designated_Port_transitions. rstp_disable_learning(T=173641) VLAN101, port 4/10 BLOCKING

rstp_Port_State_Transition_State_Machine_Action: VLAN 101 Port 4/10 set to BLOCKING. rstp_disable_forwarding(T=173641) VLAN101, port 4/10 BLOCKING

rstputil_mct_enable_port.vlan 101 port 4/13

rstputil_mct_enable_port:: port is trunk

rstputil_mct_enable_port. Per VLAN STP. VLAN 101 Port 4/13 CCEP = TRUE

rstputil_mct_enable_port.rstputil_mct_send_rstp_state_reset_to_peer. VLAN 101 Port 4/13 CCEP = TRUE rstputil_mct_send_stp_state_RESET_to_peer(vlan=173641,port=101) primary_port 4/13

--> rstputil_mct_send_stp_state_RESET_to_peer(T=173641,vlan=101,port=204) primary_port 4/13 done

rstp_enable_port:: VLAN 101 port 4/13. skip_Initialize_RSTP_state_machines = 0.

rstp_enable_port:: PIM state 0. PRT state 0. PTX state 0. TCM state 0. PPM state

0. PST state 0

rstp_enable_port::rstp_role 0 rstp_selectedRole 0 state 5 rstp_infols 0 rstp_initialize_port(T=173641) VLAN101, port 4/13. Port is trunk. primary = 4/13 active stp port = 4/13 rstp_RoleSelection_State_Machine. set_flag 2 for vlan 101

New root:: vlan 101 INVALID

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/3 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/10 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE rstp_RoleSelection_State_Machine. set_flag 2 for vlan 101

New root:: vlan 101 INVALID

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/3 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/10 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

Vlan 101 port 4/13. rstp_selectedRole = RSTP_DESIGNATED_PORT as rstp_infols == RSTP_PORT_INFO_STATE_AGED. rstp_RoleSelection_State_Machine. set_flag 2 for vlan 101

New root:: vlan 101 INVALID

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/3 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/10 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

rstp_compute_port_role_infols_Mine:: vlan 101 port 4/13 rstp_selectedRole = RSTP_DESIGNATED_PORT.rstp_updtInfo = FALSE

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 37 53-1003076-02

Page 50

MCT show commands

rstp_port_Role_Transition_State_Machine:: port 4/13 vlan 101 role = 0 selected role = 3. old PRT state 529 new state 529. Designated_Port_transitions.

rstputil_mct_handle_port_role_transition:: old state = 529, new = 3 (RSTP_DESIGNATED_PORT/RSTP_ROOT_PORT). Send ccep_state_to_peer. VLAN 101 port 4/13 rstputil_mct_send_ccep_state_to_peer(T=173641,vlan=101,port=4/13,role=3) primary_port 4/13 --> rstputil_mct_send_ccep_state_to_peer(T=173641,vlan=101,port=4/13,role=3) primary_port 4/13 done rstp_disable_learning(T=173641) VLAN101, port 4/13 BLOCKING

rstp_Port_State_Transition_State_Machine_Action: VLAN 101 Port 4/13 set to BLOCKING. rstp_disable_forwarding(T=173641) VLAN101, port 4/13 BLOCKING rstp_txRSTP(T=173641)(vlan=101,port=4/13) Tx on CCEP, MCT peer is inferior -> Tx BPDU -> Brocade(config-vlan-101)# rstputil_mct_handle_incoming_BPDU(T=173641, VLAN=101,port=4/10) port-stp-state=DISCARDING rstputil_mct_handle_incoming_BPDU(T=173641, VLAN=101,port=4/10) port-stp-state=DISCARDING

MCT show commands

This section describes the show commands that display MCT information.

show cluster

Syntax: show cluster

This command displays the complete cluster state information about the ICL, peer, and client, as shown in the following example.

Brocade# show cluster Cluster abc 1 ============= Rbridge Id: 1, Session Vlan: 3999, Keep-Alive Vlan: 4001 Cluster State: Deploy Client Isolation Mode: Loose Member Vlan Range: 100

ICL Info:

-------- Name Port Trunk icl1 4/9 11

Peer Info:

--------- Peer IP: 10.1.1.2, Peer Rbridge Id: 2, ICL: icl1 KeepAlive Interval: 10 , Hold Time: 90, Fast Failover Active Vlan Range: 100 Last Reason for CCP Down: Not Down Peer State: CCP Up (Up Time: 0 days: 0 hr: 0 min:41 sec)

Client Info:

----------- Number of Clients configured: 2

38 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 51

MCT show commands

Name Rbridge-id Config Port Trunk FSM-State A-satya-000000147d80 3318 Deployed 4/17 3 Admin Up A-satya-000000c74d40 2668 Deployed 3/13 2 Up

show cluster ccp client

Syntax: show cluster cluster_name | cluster_id ccp client client_ID

• cluster_name—Specifies the cluster name.

• cluster_id—Specifies the cluster port number.

• client_ID—Specifies the client port ID.

This command displays the registered CCP clients such as cluster manager, MDUP, or STP.

The following output is displayed when the show cluster command is configured with the cluster ID.

Brocade# show cluster 3000 ccp client Client Node Info:

---------------- Name: cluster_mgr ID: 1 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: 10.1.1.2 Registered Events: All Events Client Node Info:

---------------- Name: mdup ID: 2 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: All Peers Registered Events: PACKET_RECEIVED Client Node Info:

---------------- Name: stp ID: 4 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: All Peers Registered Events: All Events Client Node Info:

---------------- Name: mcast ID: 8 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: All Peers Registered Events: All Events Client Node Info:

---------------- Name: vrrp ID: 16 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: All Peers Registered Events: All Events

The following output is displayed when the show cluster command is configured with the cluster name.

Brocade# show cluster SX ccp client Client Node Info:

---------------- Name: cluster_mgr ID: 1 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: 10.1.1.2 Registered Events: All Events Client Node Info:

---------------- Name: mdup ID: 2 Cluster ID: 3000 Number of Peers: 1 Peer Node Info:

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 39 53-1003076-02

Page 52

MCT show commands

Peer IP: All Peers Registered Events: PACKET_RECEIVED Client Node Info:

---------------- Name: stp ID: 4 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: All Peers Registered Events: All Events Client Node Info:

---------------- Name: mcast ID: 8 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: All Peers Registered Events: All Events Client Node Info:

---------------- Name: vrrp ID: 16 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: All Peers Registered Events: All Events

The following output is displayed when the show cluster command is configured with the cluster name and the CCP client ID.

Brocade# show cluster SX ccp client 1 Client Node Info:

---------------- Name: cluster_mgr ID: 1 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: 10.1.1.2 Registered Events: All Events

The following output is displayed when the show cluster command is configured with the cluster ID and the CCP client ID.

Brocade# show cluster 3000 ccp client 1 Client Node Info:

---------------- Name: cluster_mgr ID: 1 Cluster ID: 3000 Number of Peers: 1 Peer Node Info: Peer IP: 10.1.1.2 Registered Events: All Events

show cluster ccp peer

Syntax: show cluster ccp peer

This command displays the cluster peer-state configuration information as shown in the following example.

Brocade# show cluster ccp peer Cluster Name : abc Cluster ID: 1 PEER IP ADDRESS STATE UP TIME

--------------- ------------- --------------

10.1.1.1 OPERATIONAL 1 days: 4 hr: 0 min:42 sec

show cluster ccp peer detail

Syntax: show cluster ccp peer detail

This command displays the cluster peer session and the TCP connection configuration information as shown in the following example.

40 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 53

MCT show commands

Brocade# show cluster ccp peer detail **************Peer Session Details********************* IP address of the peer 10.1.1.1 Rbridge ID of the peer 100 Session state of the peer OPERATIONAL Next message ID to be send 3369 Keep Alive interval in seconds 30 Hold Time Out in seconds 90 Fast Failover is enable for the session UP Time 1 days: 4 hr: 3 min:55 sec Number of tcp packet allocations failed 0 Message Init Keepalive Notify Application Badmessages Send 9 3932 0 102 0 Receive 9 3932 0 100 0 TCP connection is up TCP connection is initiated by 10.1.1.2 TCP connection tcbHandle not pending TCP connection packets received

**************TCP Connection Details********************* TCP Connection state: ESTABLISHED Maximum segment size: 1436 Local host: 10.1.1.2, Local Port: 12071 Remote host: 10.1.1.1, Remote Port: 4175 ISentSeq: 160671712 SendNext: 160726330 TotUnAck: 0 TotSent: 54618 ReTrans: 1 UnAckSeq: 160726330 IRcvSeq: 751804 RcvNext: 806410 SendWnd: 16384 TotalRcv: 54606 DupliRcv: 0 RcvWnd: 16384 SendQue: 0 RcvQue: 0 CngstWnd: 1436

show cluster client

Syntax: show cluster cluster_name | cluster_id client client_name | client_RbridgeID

• cluster_name—Specifies the cluster name.

• cluster_id—Specifies the cluster port ID.

• client_name—Specifies the client name.

• client_RbridgeID—Specifies the client Rbridge ID.

This command displays cluster information for all clients configured in a cluster or for a specified client.

The following output is displayed when the show cluster command is configured with the cluster ID.

Brocade# show cluster 3000 client Client Info:

-----------Number of Clients Configured: 1 Name Rbridge-id Config LACP Port Trunk FSM-State R1 100 Deployed no 1/15 - Preforwarding

Remote

The following output is displayed when the show cluster command is configured with the cluster name.

Brocade# show cluster SX client Client Info:

-----------Number of Clients Configured: 1 Name Rbridge-id Config LACP Port Trunk FSM-State

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 41 53-1003076-02

Page 54

MCT show commands

R1 100 Deployed no 1/15 - Preforwarding

Remote

The command output resembles the following example for the speciifed client..

Brocade# show cluster 1 client c1 Cluster abc 1 ============= Rbridge Id: 101, Session Vlan: 3999, Keep-Alive Vlan: 4001 Cluster State: Deploy Client Isolation Mode: Loose Configured Member Vlan Range: 100 to 105 Active Member Vlan Range: 100 to 105 MCT Peer's Reachability status using Keep-Alive Vlan: Peer Reacheable

Client Info:

-----------Client: c1, rbridge-id: 300, Deployed Client Port: 3/3 State: Up Number of times Local CCEP down: 1 Number of times Remote CCEP down: 0 Number of times Remote Client undeployed: 0 Total CCRR packets sent: 11 Total CCRR packets received: 12

show cluster config

Syntax: show cluster config [cluster_id | cluster_name]

This command displays only the cluster configuration information as shown in the following example.

Brocade# show cluster 1 config cluster abc 1 rbridge-id 20 session-vlan 3999 keep-alive-vlan 4001 icl icl1 ethernet 3/1 peer 10.1.1.1 rbridge-id 100 icl icl1 deploy client c1 rbridge-id 300 client-interface ethernet 3/3 deploy client c2 rbridge-id 301 client-interface ethernet 3/13 deploy

show mac cluster

Syntax: show mac cluster cluster_ID | cluster_name [local | remote | client | vlan]

• cluster_id - Specifies the cluster ID.

• cluster_name - Specifies the cluster name.

• local - Displays MAC entries that are learned locally.

• remote - Displays MAC entries that are learned through the MDUP message from the peer.

42 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 55

MCT show commands

• client - Displays cluster client MAC entries for all clients or for a specified client.

• vlan - Displays cluster MAC entries for the specified VLAN.

The following command output displays all MAC entries for the specified cluster.

Brocade# show mac cluster 3000 Total Cluster Enabled(CL+CR+CCL+CCR) MACs: 4 Total Cluster Local(CL) MACs: 1 Total Cluster Client Macs(CCL+CCR) for all clients: 3 Total Cluster Client Local(CCL) MACs for all clients: 3 CCL: Cluster Client Local CCR:Cluster Client Remote CL:Local CR:Remote Total active entries from all ports = 15 MAC-Address Port Type Index MCT-Type VLAN

0000.0000.0014 17/8 Dynamic 53172 CL 4081

0000.0082.1d89 11/17-11/17 Dynamic 24337 CCL 3359

0000.00a8.9c8f 1/15-1/15 Dynamic 5709 CCL 3203

0000.0082.1d89 11/17-11/17 Dynamic 7199 CCL 3360

The following command output displays all locally learned MAC entries for the specified cluster.

Brocade# show mac cluster 3000 local Total Cluster Local(CL) MACs: 2 CCL: Cluster Client Local CCR:Cluster Client Remote CL:Local CR:Remote Total active entries from all ports = 6 MAC-Address Port Type Index MCT-Type VLAN

0000.0086.8e00 7/5-7/6 Dynamic 33994 CL 3000

0000.0000.0004 7/1 Dynamic 28197 CL 10

The following command output displays all remote MAC entries for the specified cluster.

Brocade# show mac cluster 3000 remote exclude-interface Total Cluster Remote(CR) MACs: 1 CCL: Cluster Client Local CCR:Cluster Client Remote CL:Local CR:Remote Total active entries from all ports = 6 MAC-Address Port Type Index MCT-Type VLAN

0000.0000.0002 7/5-7/6 Dynamic 9111 CR 10

The following command output displays all cluster client MAC entries from all the clients.

Brocade# show mac cluster 3000 client Total Cluster Client Macs(CCL+CCR) for all clients: 2 Total Cluster Client Local(CCL) MACs for all clients: 2 CCL: Cluster Client Local CCR:Cluster Client Remote CL:Local CR:Remote Total active entries from all ports = 6 MAC-Address Port Type Index MCT-Type VLAN

0000.0000.0005 7/7-7/8 Dynamic 44352 CCL 20

0000.0076.92c0 7/7-7/8 Dynamic 15031 CCL 20

The following command output displays all cluster MAC entries for a particular VLAN.

Brocade# show mac cluster 3000 vlan 20 Total Cluster Enabled(CL+CR+CCL+CCR) MACs for vlan 20: 2 Total Cluster Client Macs(CCL+CCR) for all clients in vlan 20: 2 Total Cluster Client Local(CCL) MACs for all clients in vlan 20: 2 CCL: Cluster Client Local CCR:Cluster Client Remote CL:Local CR:Remote Total active entries from VLAN 20 = 2 MAC-Address Port Type Index MCT-Type VLAN

0000.0000.0005 7/7-7/8 Dynamic 44352 CCL 20

0000.0076.92c0 7/7-7/8 Dynamic 15031 CCL 20

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 43 53-1003076-02

Page 56

MCT show commands

show mac mdb

Syntax: show mac mdb source-rbridge Rbridge_id client-rbridge Rbridge_id

• source-rbridge Rbridge_id - Specifies the source Rbridge ID.

• client-rbridge Rbridge_id - Specifies the client Rbridge ID.

This command displays the MDB information of the cluster MAC entries. Command output resembles the following example.

Brocade# show mac mdb source-rbridge 3 Total Local MDB from all ports = 2 Total Remote MDB from all ports = 3 Code- CCL: Cluster Client Local CCR:Cluster Client Remote CL:Local CR:Remote Total active entries from all ports = 6 MAC Address Port VLAN Type S-RBridge C-RBridge P-Portid Cost Best

0000.0000.0005 4/7 20 CCR 3 100 1 *

0000.0000.0004 4/5 10 CR 3 3 384 1 *

0000.0076.92c0 4/7 20 CCR 3 100 1 *

show mac mdup-stats

Syntax: show mac mdup-stats

This command displays the statistics for MDUP packets as shown in the following example.

Brocade# show mac mdup-stats MDUP Information ================ MDUP Data buffers in queue : 0

MDUP Statistics =============== MDUP Update Messages sent: 9 Add Mac sent: 14 Add Intf Mac sent: 0 Del Mac sent: 0 Del Intf Mac sent: 0 Move Mac sent: 0 MDUP Mac Info Messages sent: 19 MDUP Static Mac Messages sent: 0 MDUP Flush Messages sent: 17 MDUP Update Messages received: 6 Add Mac received: 7 Add Intf Mac received: 0 Del Mac received: 2 Del Intf Mac received: 0 Move Mac received: 0 MDUP Mac Info Messages received: 16 MDUP Static Mac Messages received: 0 MDUP Flush Messages received: 11 MDUP Add Mac Errors: 3 MDUP Del MAC Errors: 0 MDUP Move MAC Errors: 0

44 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 57

Packet-capture debug commands

The following debug packet-capture command helps to debug packet flows and capture packets designated for the management module for debugging. This command has additional filter and mode option parameters for refining the traffic sources and the format of the saved data.

debug packet-capture

• all—Displays the debugging information of the packets transmitted and received.

• count-reset—Clears the total packet count of the packets captured.

• count-show —Displays the total packet count of the packets captured for debugging.

• exclude-mgmt-port—Enables debugging of the packets that are excluded for the management

port.

• filter—Enables the raw packet filter for debugging.

• max—Displays the maximum number of packets.

• mode—Displays the various packet modes.

• no-limit—Displays the debugging information of an unlimited number of packets.

• no-mgmt-port—Toggles the display of packets from the management port.

• receive—Debugs only the packets that are received.

• send—Debugs only the packets that are transmitted.

The debug packet-capture command displays information about packet-capture activity.

Packet-capture debug commands

debug packet-capture filter

Syntax: [no] debug packet-capture filter filter_index filter_options

The filter_index parameter specifies the filter number. The decimal value ranges from 1 through

20.

The filter_options parameter specifies the filter option. The following are the various options in filter:

• all—Matches all packet

• arp—Matches an ARP request or response

• broadcast-mac—Matches the destination broadcast MAC address (0000.00FF.FFFF)

• cdp—Matches with the CDP

• clear—Clears the filter entry

• clear-counter—Clears the counter

• cpu-code—Matches the CPU code

• da—Matches the destination MAC address

• dhcp—Matches with the DHCP

• dot1x—Matches the dot1x protocol

• dpa—Matches the destination IP address

• dport—Matches the destination protocol port

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 45 53-1003076-02

Page 58

Packet-capture debug commands

• ether-type—Matches the Ethernet type packets

• fdp—Matches wit h the FDP

• in-port—Matches the input port

• l2-802.1w—Matches the 802.1w BPDU

• l2-lacp—Matches the LACP PDU

• l2-mstp—Matches the MSTP BPDU

• l2-stp—Matches the spanning tree BPDU

• l3-bgp—Matches with the BGP

• l3-ospf—Matches the OSPF protocol

• l3-vrrp—Matches the VRRP

• l3-vrrpe—Matches the VRRP-E

• lldp—Matches the LLDP

• mrp—Matches the MRP

• out-port—Matches the output port

• priority—Matches the priority

• protocol—Matches the IP

• pvst—Matches the PVST protocol

• sa—Matches the source MAC address

• snmp—Matches the SNMP

• spa—Matches the source IP address

• sport—Matches the source protocol port

• udld—Matches the UDLD protocol

• vlan-id—Matches the VLAN ID

• vsrp—Matches the VSRP

This command enables the filter option for the raw packets. There are 32 filter options that can be configured within a single filter. The filter index limit ranges from 1 through 20.

Brocade# debug packet-capture filter 2 protocol

debug packet-capture mode

Syntax: [no] debug packet-capture mode [brief | no-display | normal | pcap-fmt

[default | decimal]]

• brief—Specifies the increment counters and displays the packet summary.

• no-display—Specifies the increment counters alone.

• normal—Specifies the increment counters and displays the packet header and the first 48 raw

bytes.

• pcap-fmt—Specifies the increment counters and dumps the packet in pcap (packet capture)

hexadecimal format.

• default—Specifies the normal mode.

• decimal—Specifies the first 48 bytes of the packets received.

This command displays the format of the packets to be captured for debugging information.

46 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 59

VXLAN debug commands

debug packet-capture filter show

Syntax: debug packet-capture filter show [ all | decimal ] none

This command displays the filter information for the particular filter index. The decimal variable refers to the number of the packet captured for filter.

Execute the following command to display the complete filter information.

Brocade# debug packet-capture filter show all Filter 1: Match STP Filter 2: Match 802.1W

Execute the following command to display filter information for a particular filter number.

Brocade# debug packet-capture filter show 2 Filter 2: Match 802.1W

Execute the following command to remove all the filters that are configured.

Brocade# debug packet-capture filter none

VXLAN debug commands

Virtual eXtensible Local Area Network (VXLAN) is an overlay technology to interconnect two or more logical Layer 2 networks on top of an Layer 3 IP network to support multitenant environment.

This section describes the debug commands used for debugging the VXLAN Layer 2 tunnel configurations.

debug l2-tunnel all

Syntax: [no] debug l2-tunnel all

This command enables debug of all flows of any Layer 2 tunnel. Command output resembles the following example.

Brocade# debug l2-tunnel all [VXLAN]: L2-tunnel 1 - next hop 0.0.0.0 is not router dest - update Tunnel [VXLAN]: Update 2 all maps on L2-tunnel 1 [VXLAN]: Success to update all maps on L2-tunnel 1[VXLAN]: Create vxlan tables for L2-tunnel 1 [VXLAN]: Create L3 intf 65535 for L2-tunnel 1 [VXLAN]: Reusing L3 intf 6096 for L2-tunnel 1 with exising L3 intf 65535 which reused from L2-tunnel 65535 [VXLAN]: Success to create L3 intf 6096 for L2-tunnel 1 [VXLAN]: Create vxlan egress ip tunnel for L2-tunnel 1 with index ffffffff [VXLAN]: Success to create vxlan egress ip tunnel for L2-tunnel 1 with index 4c000002 [VXLAN]: Create Forward nextHop 65535 for L2-tunnel 1 on network port 1/1/2 [VXLAN]: Success to reuse Forward nexthop 66 for L2-tunnel 1 from L2-tunnel 2 on network port 1/1/2 [VXLAN]: Create vxlan terminator for L2-tunnel 1 [VXLAN]: Fail to get vxlan terminator on device 0 : Entry not found [VXLAN]: Success to create vxlan terminator for L2-tunnel 1 [VXLAN]: Success to create vxlan tables for L2-tunnel 1

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 47 53-1003076-02

Page 60

VXLAN debug commands

[VXLAN]: Update 1 all maps on L2-tunnel 1 [VXLAN]: Create VXLAN map for port 1/1/1, vlan 31, vni 3100, L2-tunnel 1 [VXLAN]: Create VXLAN VPN for vni 3100 [VXLAN]: Success to create VXLAN VPN for vni 3100 with VPN 7000 [VXLAN]: Add access port 1/1/1, vlan 31 to vpn 7000 [VXLAN]: Success to create access egress nexthop 100004 [VXLAN]: Success to create access vxlan port 80000001 for access port 1/1/1 on vlan 31 in vpn 7000 [VXLAN]: Add network port 1/1/2 to vpn 7000 with existing vxlan port 80000002 on L2-tunnel 1 [VXLAN]: Success to add network port 1/1/2 to vpn 7000 with new vxlan port 80000002 on L2-tunnel 1 [VXLAN]: Success to create VXLAN map [VXLAN]: Success to update all maps on L2-tunnel 1 [VXLAN]: bring tunnel id 1 up [VXLAN]: Create tunnel id 1 with next hop 64 - old next hop is 4

debug l2-tunnel vxlan all

Syntax: [no] debug l2-tunnel vxlan all

This command enables debug of all flows of a VXLAN tunnel. Command output resembles the following example.

Brocade# debug l2-tunnel vxlan all [VXLAN]: L2-tunnel 1 - next hop 0.0.0.0 is not router dest - update Tunnel [VXLAN]: Update 2 all maps on L2-tunnel 1 [VXLAN]: Success to update all maps on L2-tunnel 1[VXLAN]: Create vxlan tables for L2-tunnel 1 [VXLAN]: Create L3 intf 65535 for L2-tunnel 1 [VXLAN]: Reusing L3 intf 6096 for L2-tunnel 1 with exising L3 intf 65535 which reused from L2-tunnel 65535 [VXLAN]: Success to create L3 intf 6096 for L2-tunnel 1 [VXLAN]: Create vxlan egress ip tunnel for L2-tunnel 1 with index ffffffff [VXLAN]: Success to create vxlan egress ip tunnel for L2-tunnel 1 with index 4c000002 [VXLAN]: Create Forward nextHop 65535 for L2-tunnel 1 on network port 1/1/2 [VXLAN]: Success to reuse Forward nexthop 66 for L2-tunnel 1 from L2-tunnel 2 on network port 1/1/2 [VXLAN]: Create vxlan terminator for L2-tunnel 1 [VXLAN]: Fail to get vxlan terminator on device 0 : Entry not found [VXLAN]: Success to create vxlan terminator for L2-tunnel 1 [VXLAN]: Success to create vxlan tables for L2-tunnel 1 [VXLAN]: Update 1 all maps on L2-tunnel 1 [VXLAN]: Create VXLAN map for port 1/1/1, vlan 31, vni 3100, L2-tunnel 1 [VXLAN]: Create VXLAN VPN for vni 3100 [VXLAN]: Success to create VXLAN VPN for vni 3100 with VPN 7000 [VXLAN]: Add access port 1/1/1, vlan 31 to vpn 7000 [VXLAN]: Success to create access egress nexthop 100004 [VXLAN]: Success to create access vxlan port 80000001 for access port 1/1/1 on vlan 31 in vpn 7000 [VXLAN]: Add network port 1/1/2 to vpn 7000 with existing vxlan port 80000002 on L2-tunnel 1 [VXLAN]: Success to add network port 1/1/2 to vpn 7000 with new vxlan port 80000002 on L2-tunnel 1 [VXLAN]: Success to create VXLAN map [VXLAN]: Success to update all maps on L2-tunnel 1 [VXLAN]: bring tunnel id 1 up [VXLAN]: Create tunnel id 1 with next hop 64 - old next hop is 4

48 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 61

VXLAN debug commands

debug l2-tunnel vxlan tunnel all

Syntax: [no] debug l2-tunnel vxlan tunnel all

This command enables debug of all flows of a VXLAN tunnel creation, updation, and deletion. Command output resembles the following example.

Brocade# debug l2-tunnel vxlan tunnel all [VXLAN]: L2-tunnel 1 - next hop 0.0.0.0 is not router dest - update Tunnel [VXLAN]: Update 2 all maps on L2-tunnel 1 [VXLAN]: Success to update all maps on L2-tunnel 1[VXLAN]: Create vxlan tables for L2-tunnel 1 [VXLAN]: Create L3 intf 65535 for L2-tunnel 1 [VXLAN]: Reusing L3 intf 6096 for L2-tunnel 1 with exising L3 intf 65535 which reused from L2-tunnel 65535 [VXLAN]: Success to create L3 intf 6096 for L2-tunnel 1 [VXLAN]: Create vxlan egress ip tunnel for L2-tunnel 1 with index ffffffff [VXLAN]: Success to create vxlan egress ip tunnel for L2-tunnel 1 with index 4c000002 [VXLAN]: Create Forward nextHop 65535 for L2-tunnel 1 on network port 1/1/2 [VXLAN]: Success to reuse Forward nexthop 66 for L2-tunnel 1 from L2-tunnel 2 on network port 1/1/2 [VXLAN]: Create vxlan terminator for L2-tunnel 1 [VXLAN]: Fail to get vxlan terminator on device 0 : Entry not found [VXLAN]: Success to create vxlan terminator for L2-tunnel 1 [VXLAN]: Success to create vxlan tables for L2-tunnel 1 [VXLAN]: Update 1 all maps on L2-tunnel 1 [VXLAN]: Success to update all maps on L2-tunnel 1 [VXLAN]: bring tunnel id 1 up [VXLAN]: Create tunnel id 1 with next hop 64 - old next hop is 4

debug l2-tunnel vxlan tunnel sw-prog

Syntax: [no] debug l2-tunnel vxlan tunnel sw-prog

This command enables debug of software programming flows of VXLAN tunnel creation, updation, and deletion. Command output resembles the following example.

Brocade# debug l2-tunnel vxlan tunnel sw-prog [VXLAN]: L2-tunnel 1 - next hop 0.0.0.0 is not router dest - update Tunnel [VXLAN]: Update 2 all maps on L2-tunnel 1 [VXLAN]: Success to update all maps on L2-tunnel 1 [VXLAN]: Update 1 all maps on L2-tunnel 1 [VXLAN]: Success to update all maps on L2-tunnel 1 [VXLAN]: bring tunnel id 1 up [VXLAN]: Create tunnel id 1 with next hop 64 - old next hop is 4

debug l2-tunnel vxlan tunnel hw-prog

Syntax: [no] debug l2-tunnel vxlan tunnel hw-prog

This command enables debug of hardware programming flows of VXLAN tunnel creation, updation, and deletion. Command output resembles the following example.

Brocade# debug l2-tunnel vxlan tunnel hw-prog [VXLAN]: Create vxlan tables for L2-tunnel 2 [VXLAN]: Create L3 intf 65535 for L2-tunnel 2 [VXLAN]: Reusing L3 intf 6096 for L2-tunnel 2 with exising L3 intf 65535 which reused from L2-tunnel 65535 [VXLAN]: Success to create L3 intf 6096 for L2-tunnel 2

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 49 53-1003076-02

Page 62

Link aggregation debug commands

NOTE

[VXLAN]: Create vxlan egress ip tunnel for L2-tunnel 2 with index ffffffff [VXLAN]: Success to create vxlan egress ip tunnel for L2-tunnel 2 with index 4c000002 [VXLAN]: Create Forward nextHop 65535 for L2-tunnel 2 on network port 1/1/2 [VXLAN]: Success to reuse Forward nexthop 66 for L2-tunnel 2 from L2-tunnel 1 on network port 1/1/2 [VXLAN]: Create vxlan terminator for L2-tunnel 2 [VXLAN]: Fail to get vxlan terminator on device 0 : Entry not found [VXLAN]: Success to create vxlan terminator for L2-tunnel 2 [VXLAN]: Success to create vxlan tables for L2-tunnel 2

debug l2-tunnel vxlan mapping

Syntax: [no] debug l2-tunnel vxlan mapping

This command enables debug of flows of VXLAN mapping creation, updation, and deletion. Command output resembles the following example.

Brocade# debug l2-tunnel vxlan mapping [VXLAN]: Create VXLAN map for port 1/1/1, vlan 31, vni 3100, L2-tunnel 1 [VXLAN]: Create VXLAN VPN for vni 3100 [VXLAN]: Success to create VXLAN VPN for vni 3100 with VPN 7000 [VXLAN]: Add access port 1/1/1, vlan 31 to vpn 7000 [VXLAN]: Success to create access egress nexthop 100004 [VXLAN]: Success to create access vxlan port 80000001 for access port 1/1/1 on vlan 31 in vpn 7000 [VXLAN]: Add network port 1/1/2 to vpn 7000 with existing vxlan port 80000002 on L2-tunnel 1 [VXLAN]: Success to add network port 1/1/2 to vpn 7000 with new vxlan port 80000002 on L2-tunnel 1 [VXLAN]: Success to create VXLAN map

Link aggregation debug commands

The trunk group feature allows you to manually configure multiple high-speed load-sharing links between two Brocade Layer 2 switches or Layer 3 switches or between a Brocade Layer 2 switch and Layer 3 switch and a server.

In addition to enabling load sharing of traffic, trunk groups provide redundant, alternate paths for traffic if any of the segments fail. Trunk groups are manually configured aggregate links containing multiple ports. The 802.3ad link aggregation protocol dynamically creates and manages trunk groups.

The terms "trunk group" and "link aggregation group" are used interchangeably in this document.

The following commands are used for troubleshooting trunk groups:

• debug pp-trunk-hash

• debug pp-bum-trunk-hash

50 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 63

debug pp-trunk-hash

Traces and displays the output port through which a given packet can be sent out in a trunk.

Syntax debug pp-trunk-hash [trunk_port | ingress_port]

debug pp-trunk-hash trunk_port

unicast-distribution ip dmac smac [dst_ipv4 src_ipv4 dst_tcp/udp_port src_tcp/udp_port | dst_ipv6 src_ipv6 dst_tcp/udp_port src_tcp/udp_port]

unicast-distribution non-ip dmac smac

debug pp-trunk-hash ingress_ port

v4-device sw_ trunk_ ID [registered-multicast vlan vidx | routed-flow dst_ipv4 src_ipv4 IPHdr_Protocol | switched-flow ip dst_ipv4 src_ipv4 | switched-flow non-ip dmac smac | unregistered-multicast vlan]

v6-device sw_trunk_ID [routed-multicast-distribution vlan | unicast-distribution [ip dmac smac [dst_ipv4 src_ipv4 [dst_tcp | udp_port] [src_tcp | udp_port]]| non-ip dmac smac]]

no debug pp-trunk-hash

debug pp-trunk-hash

udp_port] [src_tcp | udp_port] | dst_ipv6 src_ipv6 [dst_tcp |

Parameters trunk_port Specifies the trunk member port number.

ingress_ port Specifies the ingress port number.

unicast-distribution Generates debugging information related to unicast distribution.

ip dmac smac Generates debugging information related to unicast IPv4 and IPv6

distribution for the specified destination MAC address and source MAC address. The following variables are supported with this option.

dst_ipv4 Specifies the destination IPv4 address.

src_ipv4 Specifies the source IPv4 address.

dst_tcp | udp_port

Specifies the destination TCP or UDP port number.

src_tcp | udp_port

Specifies the source TCP or UDP port number.

dst_ipv6 Specifies the destination IPv6 address.

src_ipv6 Specifies the source IPv6 address.

non-ip dmac smac

Generates debugging information related to unicast non-IP distribution for the specified destination MAC address and source MAC address.

sw_ trunk_ ID Specifies the software trunk ID.

v4-device Generates debugging information related to the IPv4 device. The following

parameters are supported with this option.

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 51 53-1003076-02

Page 64

debug pp-trunk-hash

registered-multicast

Generates debugging information related to registered multicast distribution. The following variables must be specified with this option.

vlan Specifies the VLAN ID.

vidx Specifies the multicast ID.

routed-flow Generates debugging information related to routed flow distribution. The

following variables must be specified with this option.

dst_ipv4 Specifies the destination IPv4 address.

src_ipv4 Specifies the source IPv4 address.

IPHdr_Protocol Specifies the protocol value in the IP header.

switched-flow ip

Generates debugging information related to switched flow IPv4 and IPv6 distribution. The following variables must be specified with this option.

dst_ipv4 Specifies the destination IPv4 address.

src_ipv4 Specifies the source IPv4 address.

switched-flow non-ip

dmac Specifies the destination MAC address.

smac Specifies the source MAC address

unregistered-multicast vlan

v6-device Generates debugging information related to the IPv6 device. The following

routed-multicast-distribution vlan

unicast-distribution

ip Generates debugging information related to unicast IP distribution.

non-ip Generates debugging information related to unicast non-IP distribution.

Modes Privileged EXEC mode

Generates debugging information related to switched flow non-IP distribution. The following variables must be specified with this option.

Generates debugging information related to unregistered multicast distribution for the specified VLAN ID.

parameters are supported with this option.

Generates debugging information related to routed multicast distribution for the specified VLAN ID.

Generates debugging information related to unicast distribution.

Usage

Guidelines

52 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

The debug pp-trunk-hash trunk_port command is supported only on Brocade FCX and Brocade ICX devices.

The debug pp-trunk-hash ingress_ port command is supported only on Brocade FastIron SX devices.

53-1003076-02

Page 65

debug pp-trunk-hash

Examples For the unicast IPv4 distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/1/3 unicast-distribution ip 0000.0082.ba04

0000.00c9.5680 10.10.10.2 10.10.10.1 10 10 trunk hashed port: 1/1/2

For the unicast IPv6 distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/1/3 unicast-distribution ip 0000.0082.ba04

0000.00c9.5680 2001:DB8::100:10 2001:DB8::10:19 10 17 trunk hashed port: 1/1/1

For the unicast non-IP distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/1/3 unicast-distribution non-ip 0000.0082.ba04

0000.00c9.5680 trunk hashed port: 1/1/9

For the registered multicast distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/5 v4-device 1 registered-multicast 10 10 trunk hash port: 1/1

For the routed flow distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/5 v4-device 1 routed-flow 10.10.10.1 10.10.10.5 9 trunk hashed port: 1/13

History

Commands

For the switched flow IP distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/5 v4-device 1 switched-flow ip 10.10.10.1

10.10.10.2 trunk hashed port: 2/2

For the switched flow non-IP distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/5 v4-device 1 switched-flow non-ip 0000.00c9.5680

0000.0082.ba04 trunk hash port: 1/1

For the unregistered multicast distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/5 v4-device 1 unregistered-multicast 10 trunk hash port: 1/1

For the routed multicast distribution, the command output resembles the following example.

Brocade# debug pp-trunk-hash 1/1 v6-device 2 routed-multicast-distribution 20 trunk hash port: 1/3

Release Command History

Release 08.0.00a The command was introduced.

debug pp-bum-trunk-hash

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 53 53-1003076-02

Page 66

debug pp-bum-trunk-hash

Traces and displays the output port through which a given packet can be sent out in a trunk for a broadcast, unknown-unicast, and multicast (BUM) flow.

Syntax debug pp-bum-trunk-hash ingress_port sw_trunk_id dmac smac

ipv4 dst_ipv4 src_ipv4 [dst_tcp | udp_port] [src_tcp | udp_port] vlan vidx

ipv6 flow_label dst_ipv6 src_ipv6 [dst_tcp | udp_port] [src_tcp | udp_port] vlan vidx

non-ip

no debug pp-bum-trunk-hash

Parameters ingress_ port Specifies the ingress port number.

sw_ trunk_ id Specifies the software trunk ID.

dmac Specifies the destination MAC address.

smac Specifies the source MAC address.

ipv4 Generates debugging information related to IPv4 distribution for a BUM flow.

ipv6 Generates debugging information related to IPv6 distribution for a BUM flow.

The following variables are supported with the ipv4 and ipv6 options.

dst_ipv4 Specifies the destination IPv4 address.

src_ipv4 Specifies the source IPv4 address.

dst_tcp | udp_port

Specifies the destination TCP or UDP port number.

src_tcp | udp_port

Specifies the source TCP or UDP port number.

vlan Specifies the VLAN ID.

vidx Specifies the multicast ID.

flow_label Specifies the flow label in the IPv6 header.

dst_ipv6 Specifies the destination IPv6 address.

src_ipv6 Specifies the source IPv6 address.

non-ip Generates debugging information related to non-IP distribution for a BUM

flow.

Modes Privileged EXEC mode

Examples For the IPv4 BUM flow, the command output resembles the following example.

Brocade# debug pp-bum-trunk-hash 1/1/1 3 0000.00aa.aaaa 0000.00bb.1111 ipv4

10.1.1.1 10.1.1.2 10 10 1 100 Designated Trunk Port = 1/1/5

For the IPv6 BUM flow, the command output resembles the following example.

54 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 67

History

debug pp-bum-trunk-hash

Brocade# debug pp-bum-trunk-hash 1/1/11 3 0000.00aa.aaaa 0000.00bb.1111 ipv6 128 2001:DB8::1:1 2001:DB8::1:1 10 10 1 100 Designated Trunk Port = 1/1/4

For the non-IP BUM flow, the command output resembles the following example.

Brocade# debug pp-bum-trunk-hash 1/1/1 3 0000.00aa.aaaa 0000.00bb.1111 non-ip Designated Trunk Port = 1/1/5

Release Command History

Release 08.0.00a The command was introduced.

Commands

debug pp-trunk-hash

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 55 53-1003076-02

Page 68

debug pp-bum-trunk-hash

56 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 69

Chapter

IP Diagnostics

This chapter contains the following sections:

•ARP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

•BGP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

•DHCP snooping debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

•GRE debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

•ICMP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

•OSPF debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

•RIP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

•NTP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

•Source Guard debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

•SSH debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

•TCP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

•UDP debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

•VRRP and VRRP-E debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

•Web debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

ARP debug commands

Address Resolution Protocol (ARP) is a standard protocol that enables a router to obtain the Media Access Control (MAC) address of an interface on another device when the router knows the IP address of the interface. ARP is enabled by default and cannot be disabled.

The following commands perform actions related to ARP debugging.

debug ip arp

Syntax: [no] debug ip arp ip-addr

This command activates the debuggging of ARP packets. The ip-addr variable specifies a particular route.

Brocade# debug ip arp 10.29.29.53 ARP: packets debugging is on Brocade# show arp

Total number of ARP entries: 3, maximum capacity: 4000 No. IP Address MAC Address Type Age Port Status 1 10.29.29.53 0000.0034.1b60 Dynamic 0 2/1/15-2/1/16 Valid 2 10.200.200.45 0000.00cf.c400 Dynamic 0 1/1/13-1/1/14 Valid 3 10.30.30.31 0000.0023.0f00 Dynamic 0 2/1/9-2/1/10 Valid

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 57 53-1003076-02

Page 70

BGP debug commands

Brocade# clear arp next hop router 10.29.29.53 ARP mapping deleted Brocade# ARP: sent packet oper=request, src 10.29.29.111 0000.0076.2c80: dst

10.29.29.53 0000.0000.0000: Port v29 ARP: sent packet oper=request, src 10.200.200.111 0000.0076.2c80: dst

10.200.200.45 0000.0000.0000: Port v2000 ARP: sent packet oper=request, src 10.30.30.111 0000.0076.2c80: dst 10.30.30.31

0000.0000.0000: Port v300 ARP: sent packet oper=request, src 10.20.67.111 0000.0076.2c80: dst 10.20.10.11

0000.0000.0000: Port mgmt1

debug ip arp inspection

Syntax: [no] debug ip arp inspection

This command enables the ARP inspection debugging.

Brocade# debug ip arp inspection ARP: inspection debugging is on RX: rcvd ARP packet, brd 1, us 0, vlan 14 port 5/1/2 ARP: rcvd packet oper=request, src 10.3.3.13 0000.009d.8c69: dst 10.3.3.1

0000.0000.0000: Port e5/1/2 ARP: REQ inspection pass, 10.3.3.13->10.3.3.1, port 5/1/2

BGP debug commands

The following debug ip bgp commands display information about Border Gateway Protocol (BGP) IP transactions.

debug ip bgp

Syntax: [no] debug ip bgp neighbor_ip_address

This command enables common BGP debugging information to be displayed for all virtual routing and forwarding events (VRFs) or for a specific VRF. The neighbor_ip_address variable refers to the IP address of the immediate neighbor.

Brocade# debug ip bgp 10.1.34.10 updates BGP: neighbor 10.1.34.10 debugging is on Brocade# BGP: 10.1.34.10 rcv UPDATE w/attr: Origin=IGP AS_PATH=AS_CONFED_SEQUENCE(3) 64519 NextHop=10.1.34.10 MED=0 LOCAL_PREF=100 BGP: 10.1.34.10 rcv UPDATE 10.1.22.0/24 BGP: 10.1.34.10 rcv UPDATE w/attr: Origin=IGP AS_PATH=AS_CONFED_SEQUENCE(3) 64519 NextHop 10.1.34.10 MED=0 LOCAL_PREF=100 BGP: 10.1.34.10 rcv UPDATE 10.1.23.0/24

debug ip bgp dampening

Syntax: [no] debug ip bgp dampening

This command displays information about dampening process configurations, route penalties, durations, restraint, and release. Command output resembles the following example.

Brocade# debug ip bgp dampening BGP: 10.1.1.2 Decay 10.1.1.32/32, ostate <d>, oPnlty=6805, nPnlty=840, time=2712 BGP: 10.1.1.2 reuse_list_index=258, curr_offset=45 BGP: 10.1.1.2 10.1.1.32/32 not ready, state <d>, reuse_threshold=750, new_index=61, offset=45

58 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 71

BGP debug commands

BGP: 10.1.1.2 Decay 10.1.1.32/32, ostate <d>, oPnlty=6805, nPnlty=840, time=2712 BGP: 10.1.1.2 reuse_list_index=258, curr_offset=45 BGP: 10.1.1.2 10.1.1.32/32 not ready, state <d>, reuse_threshold=750, new_index=61, offset=45 BGP: 10.1.1.2 Decay 10.1.1.32/32, ostate <d>, oPnlty=6805, nPnlty=840, time=2712 BGP: 10.1.1.2 reuse_list_index=258, curr_offset=45 BGP: 10.1.1.2 10.1.1.32/32 not ready, state <d>, reuse_threshold=750, new_index=61, offset=45 BGP: 10.1.1.2 Decay 10.1.1.32/32, ostate <d>, oPnlty=6805, nPnlty=840, time=2712 BGP: 10.1.1.2 reuse_list_index=258, curr_offset=45 BGP: 10.1.1.2 10.1.1.32/32 not ready, state <d>, reuse_threshold=750, new_index=61, offset=45 BGP: 10.1.1.2 Decay 10.1.1.32/32, ostate <d>, oPnlty=6805, nPnlty=840, time=2712 BGP: 10.1.1.2 reuse_list_index=258, curr_offset=45 BGP: 10.1.1.2 10.1.1.32/32 not ready, state <d>, reuse_threshold=750, new_index=61, offset=45

debug ip bgp events

Syntax: [no] debug ip bgp events

This command generates information about BGP events, such as connection attempts and keepalive timer activity.

Brocade# debug ip bgp events BGP: events debugging is on Brocade# BGP: 10.1.34.10 rcv notification: CEASE Message BGP: 10.1.34.10 Peer went to IDLE state (Rcv Notification) BGP: 10.1.35.10 rcv notification: CEASE Message BGP: 10.1.35.10 Peer went to IDLE state (Rcv Notification) BGP: 10.1.34.10 sending Graceful Restart cap, rbit 0, fbit 0, time 120, length 6 BGP: 10.1.35.10 sending Graceful Restart cap, rbit 0, fbit 0, time 120, length 6 BGP: 10.1.34.10 rcv GR capability afi/safi=1/1 fbit 0 BGP: 10.1.34.10 Peer went to ESTABLISHED state BGP: 10.1.35.10 rcv GR capability afi/safi=1/1 fbit 0 BGP: 10.1.35.10 Peer went to ESTABLISHED state BGP: 10.1.34.10 rcv UPDATE EOR (0), waiting EOR 0 BGP: 10.1.35.10 rcv UPDATE EOR (0), waiting EOR 0 BGP: 10.1.34.10 sending EOR (safi 0)... BGP: 10.1.35.10 sending EOR (safi 0)...

debug ip bgp graceful-restart

Syntax: [no] debug ip bgp graceful-restart

Enable this command to receive information about BGP graceful restarts. The graceful restart feature minimizes disruptions in forwarding and route flapping when a router restarts.

Brocade# debug ip bgp graceful-restart BGP: graceful-restart debugging is on BGP: 10.1.251.6 save graceful restart parameters, #RIB_out 2 (safi 0)

10.1.251.6 RIB_out peer reset #RIB_out 2 (safi 0) BGP: 10.1.251.6 sending Graceful Restart cap, rbit 0, fbit 0, time 120, length 6 BGP: 10.1.251.6 sending Graceful Restart cap, rbit 0, fbit 0, time 120, length 6 BGP: 10.1.251.6 sending Graceful Restart cap, rbit 0, fbit 0, time 120, length 6 BGP: 10.1.251.6 rcv GR capability afi/safi=1/1 fbit 1 BGP: 10.1.251.6 sending EOR (safi 0)...

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 59 53-1003076-02

Page 72

DHCP snooping debug commands

debug ip bgp keepalives

Syntax: [no] debug ip bgp keepalives

Brocade devices use keepalives to collect information about applications and services. For example, you can configure a keepalive to continually monitor and report on the online status of a resource, such as BGP.

Brocade# debug ip bgp keepalives BGP: 10.1.1.2 sending KEEPALIVE BGP: 10.1.1.2 KEEPALIVE received

debug ip bgp updates

Syntax: [no] debug ip bgp updates

This command displays BGP receive, transmit, or receive and transmit update messages about debug processing.

Brocade# debug ip bgp updates BGP: safi(0): 10.1.1.2 sending UPDATE w/attr: Origin=IGP AS_PATH=65538 NEXT_HOP=10.1.1.1 MED=1 BGP: (0): 10.1.1.2 sending UPDATE Label=0 2001:DB8:83:e8:00:04:78:64:10.1.1.1/32 BGP: 10.1.1.2 rcv bad UPDATE (saif 0) due to AS loop, take as implicit withdraw! BGP: BGP: 10.1.1.2 rcv UPDATE w/attr: Origin=INCOMP AS_PATH= AS_SEQ(2) 3 NextHop=10.1.1.2 MED=30 BGP: (0): 10.1.1.2 rcv UPDATE 10.1.1.2/32 BGP: 10.1.1.2 rcv bad UPDATE (saif 0) due to AS loop, take as implicit withdraw! BGP: BGP: 10.1.1.2 rcv UPDATE w/attr: Origin=IGP AS_PATH= AS_SEQ(2) 3 NextHop=10.1.1.2 MED=5 BGP: (0): 10.1.1.2 rcv UPDATE 10.10.10.10/32 BGP: (0): 10.1.1.2 rcv UPDATE 10.213.0.0/16 BGP: (0): 10.1.1.2 rcv UPDATE 10.200.200.200/32 BGP: (0): 10.1.1.2 rcv UPDATE 10.18.18.0/24 BGP: (0): 10.1.1.2 rcv UPDATE 10.1.1.32/32

DHCP snooping debug commands

Dynamic Host Configuration Protocol (DHCP) snooping enables the Brocade device to filter untrusted DHCP packets in a subnet. DHCP snooping can ward off man-in-the-middle (MiM) attacks, such as a malicious user posing as a DHCP server sending false DHCP server reply packets with the intention of misdirecting other users. DHCP snooping can also stop unauthorized DHCP servers and prevent errors due to user misconfiguration of the DHCP servers.

Often, DHCP snooping is used together with Dynamic ARP Inspection (DAI) and IP Source Guard.

debug ip dhcp-snooping

Syntax: [no] debug ip dhcp-snooping

This command enables debugging of the DHCP snooping activity.

Brocade# debug ip dhcp-snooping Brocade(config-vif-11)# DHCP: snooping on for vlan 14, port 5/1/2 DHCP: rcv on port 5/1/2, intercept DHCP pkt, Discovr DHCP: snooping on port 5/1/2, smac 0000.00ce.ac79, type 1, VRF 1

0.0.0.0->0000.00ce.ac79 DHCP Option82: Adding option 82

60 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 73

DHCP Option82: 20 bytes added. DHCP Option82: Adding option 82 DHCP: snooping on for vlan 14, port 3/1/23 DHCP: rcv on port 3/1/23, intercept DHCP pkt, Offer DHCP Option82: Removing option 82 DHCP Option82: 19 bytes removed. DHCP Option82: Removing option 82 DHCP: snooping on for vlan 14, port 5/1/2 DHCP: rcv on port 5/1/2, intercept DHCP pkt, Request DHCP: snooping on port 5/1/2, smac 0000.00ce.ac79, type 3, VRF 1

0.0.0.0->0000.00ce.ac79 DHCP Option82: Adding option 82 DHCP Option82: 20 bytes added. DHCP Option82: Adding option 82

GRE debug commands

debug ip gre log

Syntax: [no] debug ip gre log

GRE debug commands

This command activates the tunnel events debugging.

Brocade# debug ip gre log Apply mtu 1400 failed for tunnel 11 as all mtu profiles are used Clearing PMTU for tunnel 11 due to ip mtu 1400 configuration Tunnel Create Sync-Receive event for tunnel: 11 Tunnel Create Sync-Successful for tunnel: 11 Tunnel Update TS Sync-Receive event for tunnel: 11 Tunnel Update TS Sync-Successful for tunnel: 11 Tunnel Update Nhop Sync-Receive event for tunnel: 11 Tunnel Update Nhop Sync-Successful for tunnel: 11 Tunnel Update TTI Sync-Receive event for tunnel: 11 Tunnel Port Up Sync-Receive event for tunnel: 11 Tunnel Port Up Sync-Successful for tunnel: 11 Tunnel Port Down Sync-Receive event for tunnel: 11 Tunnel Port Down Sync-Successful for tunnel: 11 Tunnel Update MTU Sync-Receive event for tunnel: 11 Tunnel Update MTU Sync-Successful for tunnel: 11 Tunnel Delete Sync-Receive event for tunnel: 11 Tunnel Delete Sync-Successful for tunnel: 11 Tunnel Delete Nhop Sync-Receive event for tunnel: 11 Tunnel Delete Nhop Sync-Successful for tunnel: 11 Tunnel Delete TTI Sync-Receive event for tunnel: 11 Tunnel Delete Origination entry Sync-Receive event for tunnel: 11 Tunnel Delete Origination entry Sync-Successful for tunnel: 11 process_one_l3_unicast_update: entryType 6 Fill Sync Tunnel Entry-Bad parameters. Failed for tunnel: 11 Fill Sync Tunnel Entry-Bad TS entry. Failed for tunnel: 11 pack_tunnel_entry_change called with tunnel_index: 11 operation: TUNNEL_SYNC_UPDATE_NHOP pack_tunnel_entry_list called with tunnel_index: 11 operation: TUNNEL_SYNC_CREATE_ALL, from_beginning: 1 Sync-ing tunnel entry 11 [pp_puma_tunnel_hotswap_insert] No tunnel start info for tunnel 11 DEBUG 0x8: Tunnel 11 already deleted DEBUG 0x8: Tunnel 11 pp_delete_tunnel_entry

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 61 53-1003076-02

Page 74

GRE debug commands

DEBUG 0x8: Can not find route for tunnel id 11, hw index 23, src 10.22.33.254, dest 10.22.33.252 DEBUG 0x8: create GRE tunnel origination because find route for tunnel id 11, hw index 23, src 10.22.33.254, dest 10.22.33.252 DEBUG 0x8: Route for tunnel id 11 is via another tunnel or management port 22 DEBUG 0x8: Direct route for tunnel id 11 dest 10.22.33.252 has unresolved ARP DEBUG 0x8: indirect route for tunnel id 11 dest 10.22.33.252 next hop 10.11.25.5 has unresolved ARP DEBUG 0x8: indirect route for tunnel id 11 destination 10.22.33.252 next hop

10.11.25.5 has resolved ARP - CMD => route DEBUG 0x8: Set next hop to Drop for tunnel id 11, hw index 23, src 10.22.33.254, dest 10.22.33.252 DEBUG 0x8: Tunnel 11 - next hop 10.11.25.5 has no link-layer DEBUG 0x8: bring tunnel id 11 up with drop DEBUG 0x8: Create tunnel id 11 with next hop 185276677 - old next hop is 125276633 DEBUG 0x8: bring tunnel id 11 up Update_hw_routes for Tunnel 11 Path MTU: Tunnel 11 - reset path mtu timer 456 (3344) Path MTU: Tunnel 11 - failed to reset path mtu timer 456 (3344)

debug ip gre keepalive

Syntax: [no] debug ip gre keepalive

This command activates the Generic Routing Encapsulation (GRE) keepalive debugging.

Brocade# debug ip gre keepalive GRE_MP: Keepalive Bring DOWN GRE Tunnel 11 GRE_MP: Keepalive Bring UP GRE on Tunnel 11 - port is 2/1/2 GRE_MP: RX Keepalive packet on tnnl 11 src 10.22.33.254, dst 10.22.33.252 GRE_MP: TX Keepalive packet on tnnl 11 we need to find outgoing port GRE_MP: TX Keepalive packet on tnnl 11 - outgoing_port is 2/1/2 with mac

0000.00bb.ef40 vlan 2 GRE_MP_KEEPALIVE: NO FREE BUFFER AVAILABLE GRE_MP: For Tunnel 11, Keepalive timeout after 3 seconds GRE_MP: For Tunnel 11, stop keep-alive GRE_MP: For Tunnel 11, start keep-alive GRE_MP: enqueue Keepalive packet on tunnel 11 at index 23 GRE_MP: dequeue Keepalive packet on tunnel 11 at index 23

debug ip gre packet

Syntax: [no] debug ip gre packet

This command activates the debugging of GRE packet processing.

Brocade# debug ip gre packet GRE: Error - IP GRE packet with invalid Ptype 0x1A4 GRE: Error - IP GRE packet with invalid first word 0x2C GRE: Error - IP GRE packet with invalid first word 0x2C GRE fragment : Rx IP GRE Pkt: src 10.22.33.254, dst 224.0.0.5, len 64 id 324 GRE Packet too big - need extra processing: Rx IP GRE Pkt: src 10.22.33.254, dst

224.0.0.5, len 64 GRE Reassembly: Rx IP GRE Pkt: src 10.22.33.254, dst 224.0.0.5, len 64 GRE : Rx IP GRE Pkt: src 10.22.33.254, dst 224.0.0.5, len 64 GRE: Error - Rx IP Pkt with invalid Inner IPv4 header GRE: Error - Rx IP Pkt with 2 GRE headers: Inner src 10.22.33.254, Inner dst

224.0.0.5, len 64 GRE: Dropping the packet as GRE tnnl 11 is not UP GRE_LP: Error - LP TX GRE packet is in LOOP

62 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 75

GRE : FORWARD IP to GRE tunnel 11 - Pkt: src 10.22.33.254, dst 224.0.0.5, len 64 GRE : Failed to FORWARD IP to GRE tunnel 11 - Pkt: src 10.22.33.254, dst

224.0.0.5, No route

ICMP debug commands

The following debug ip icmp commands display information about Internal Control Message Protocol (ICMP) transactions. These commands are useful in determining if a router is sending or receiving ICMP messages, and for troubleshooting end-to-end connections.

debug ip icmp events

Syntax: [no] debug ip icmp events

This command activates the ICMP events debugging.

Brocade# debug ip icmp events ICMP: events debugging is on

Brocade# ICMP: rcvd echo request packet of length 40 from 10.44.22.11 ICMP: send echo reply packet of length 60 to 10.44.22.11 ICMP: rcvd echo request packet of length 40 from 10.44.22.11 ICMP: send echo reply packet of length 60 to 10.44.22.11 ICMP: rcvd echo request packet of length 40 from 10.44.22.11 ICMP: send echo reply packet of length 60 to 10.44.22.11 ICMP: rcvd echo request packet of length 40 from 10.44.22.11 ICMP: send echo reply packet of length 60 to 10.44.22.11

ICMP debug commands

Brocade# no debug ip icmp events ICMP: events debugging is off

debug ip icmp packets

Syntax: [no] debug ip icmp packets

This command activates the ICMP packets debugging.

Brocade# debug ip icmp packets ICMP: packets debugging is on Brocade# !SR_SWITCH_ROUTER!ICMP_DEBUG_RX ICMP: Received message from 10.44.22.11 to 10.44.22.36 port 1/1/1 size 40 !SR_SWITCH_ROUTER!ICMP_DEBUG_RX ICMP: Received message from 10.44.22.11 to 10.44.22.36 port 1/1/1 size 40 !SR_SWITCH_ROUTER!ICMP_DEBUG_RX ICMP: Received message from 10.44.22.11 to 10.44.22.36 port 1/1/1 size 40 !SR_SWITCH_ROUTER!ICMP_DEBUG_RX ICMP: Received message from 10.44.22.11 to 10.44.22.36 port 1/1/1 size 40

Brocade# no debug ip icmp packets ICMP: packets debugging is off

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 63 53-1003076-02

Page 76

OSPF debug commands

The following debug commands display information about Open Shortest Path First (OSPF) transactions.

debug ip ospf

Syntax: [no] debug ip ospf A.B.C.D

This command generates OSPF debugging information for the specified IP address. Output indicates state transitions, hello packets received, LSA acknowledgements received, LSA processing, flooding information, and database descriptions, as shown in the following example.

Brocade# debug ip ospf 10.1.1.2 OSPF: debug ospf neighbor 10.1.1.2 Brocade(config)# OSPF: rcvd hello from 10.1.1.2 area 0 on interface 10.1.1.1, state DR, DR 10.1.1.1, BDR 10.1.1.2 OSPF: Neighbor 10.1.1.2, int v115, state FULL processing event HELLO_RECEIVED OSPF: rcvd hello from 10.1.1.2 area 0 on interface 10.1.1.1, state DR, DR

10.1.1.1, BDR 10.1.1.2 OSPF: Neighbor 10.1.1.2, int v115, state FULL processing event HELLO_RECEIVED OSPF: rcvd hello from 10.1.1.2 area 0 on interface 10.1.1.1, state DR, DR

10.1.1.1, BDR 10.1.1.2 OSPF: Neighbor 10.1.1.2, int v115, state FULL processing event HELLO_RECEIVED

debug ip ospf adj

Syntax: [no] debug ip ospf adj decimal

This command displays information about OSPF adjacencies and authentication, including designated router (DR) and backup designated router (BDR) elections, sent and received hello packets, neighbor state transitions, and database description information. The decimal variable refers to a specific adjacency event.

Brocade# debug ip ospf adj OSPF: adjacency events debugging is on Brocade# debug ip ospf adj OSPF: send hello on area 0 interface 10.1.1.1 OSPF: rcvd hello from 10.1.1.2 area 0 on interface 10.1.1.1, state DR, DR

10.1.1.1, BDR 10.1.1.2 OSPF: Neighbor 10.1.1.2, int v115, state FULL processing event HELLO_RECEIVED OSPF: send hello on area 0 interface 10.1.1.1 OSPF: rcvd hello from 10.1.1.2 area 0 on interface 10.1.1.1, state DR, DR

10.1.1.1, BDR 10.1.1.2 OSPF: Neighbor 10.1.1.2, int v115, state FULL processing event HELLO_RECEIVED

debug ip ospf all-vrfs route

Syntax: [no] debug ip ospf all-vrfs route

This command displays OSPF debugging information for all VPN routing and forwarding activity.

Brocade# debug ip ospf all-vrfs route SPF: redistribute into ospf 10.3.13.0 with ffffff00 forwarding address 10.4.4.3 OSPF: originate external lsa 10.3.13.0 with ffffff00 OSPF: Originate external advs ext fwding address 10.4.4.3

64 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 77

OSPF debug commands

debug ip ospf error

Syntax: [no] debug ip ospf error

This command reports the receipt of OSPF packets with errors, or mismatches between hello packet options.

Brocade# debug ip ospf error OSPF: errors debugging is on Brocade(config-vif-9)# Debug: Jan 1 03:37:11 OSPF: invalid header or unable to find neighbor, drop Debug: Jan 1 03:37:11 OSPF: recv from:10.9.9.2 Intf:ve 9 Hello L:48 A:1 Rid:10.2.2.2 DR:10.9.9.2 BDR:0.0.0.0 Debug: Jan 1 03:37:23 OSPF: invalid header or unable to find neighbor, drop Debug: Jan 1 03:37:23 OSPF: recv from:10.9.9.2 Intf:ve 9 Hello L:48 A:1 Rid:10.2.2.2 DR:10.9.9.2 BDR:0.0.0.0 Debug: Jan 1 03:37:34 OSPF: invalid header or unable to find neighbor, drop Debug: Jan 1 03:37:34 OSPF: recv from:10.9.9.2 Intf:ve 9 Hello L:48 A:1 Rid:10.2.2.2 DR:10.9.9.2 BDR:0.0.0.0

debug ip ospf event

Syntax: [no] debug ip ospf event

This command displays information about internal OSPF events related to configuration or interaction with the standby management processor and interface state transitions.

Brocade# debug ip ospf event OSPF: events debugging is on Brocade# OSPF: Interface ve 18 (10.1.18.1) state Waiting processing event Wait Timer OSPF: DR/BDR election for 10.1.18.1 on ve 18 OSPF: Neighbor 10.213.213.213 int v18, state 2_WAY processing event ADJACENCY_OK OSPF: send DBD to 10.213.213.213 on ve 18 flag 0x7 seq 0x18a3b9 len 32 OSPF: elect BDR(backup designated router): Router ID 10.213.213.213 IP interface

10.1.18.2 OSPF: elect DR(designated router): Router ID 10.10.10.77, IP interface 10.1.18.1 OSPF: Neighbor 10.116.116.1 int 2/1/21, state FULL processing event HELLO_RECEIVED OSPF: Neighbor 10.116.116.1 int v511, state FULL processing event HELLO_RECEIVED OSPF: Neighbor 10.116.116.1 int v911, state FULL processing event HELLO_RECEIVED OSPF: Neighbor 41.41.41.41 int v35, state FULL processing event HELLO_RECEIVED OSPF: Neighbor 10.213.213.213 int 2/1/14, state 2_WAY processing event HELLO_RECEIVED OSPF: Neighbor 10.116.116.1 int v511, state FULL processing event HELLO_RECEIVED OSPF: send DBD to 10.213.213.213 on ve 18 flag 0x7 seq 0x18a3b9 len 32 OSPF: Neighbor 49.2.3.4 int v34, state FULL processing event HELLO_RECEIVED OSPF: Neighbor 10.213.213.213 int v18, state EXCHANGE_START processing event HELLO_RECEIVED OSPF: Neighbor 10.213.213.213 int 4/1/12, state FULL processing event HELLO_RECEIVED

Brocade# OSPF: Interface ethernet 4/1/12 (10.1.51.2) state Down processing event Interface Up virtual interface 10.1.51.2 up, state changed to Other from Point To Point no deOSPF: Neighbor 10.213.213.213 int 4/1/12, state DOWN processing event HELLO_RECEIVED OSPF: Neighbor 10.213.213.213 int 4/1/12, state INITIALIZING processing event ONE_WAY bug ip OSPF: Neighbor 10.213.213.213 int 4/1/12, state INITIALIZING processing event HELLO_RECEIVED

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 65 53-1003076-02

Page 78

OSPF debug commands

OSPF: Neighbor 10.213.213.213 int 4/1/12, state INITIALIZING processing event ONE_WAY ospOSPF: send DBD to 10.213.213.213 on ve 18 flag 0x7 seq 0x18a3b9 len 32 f event Brocade# no debug ip ospf event

OSPF: events debugging is off

debug ip ospf flood

Syntax: [no] debug ip ospf flood

This command displays information about LSA flooding activity as shown in the following example.

Brocade# debug ip ospf flood OSPF: flooding debugging is on Brocade(config-if-e1000-1/1/15)#OSPF: flood LSA Type:1 AdvRtr:10.2.1.1 Age:0 LsId:10.2.1.1 OSPF: flood advertisement 10.2.1.1 throughout a specific area = 0 OSPF: flood LSA Type:1 AdvRtr:10.2.1.1 Age:0 LsId:10.2.1.1 OSPF: flood advertisement 10.2.1.1 throughout a specific area = 0 OSPF: flooding type 1 advertisement out interface 10.1.1.1 OSPF: attempting to flood rcvd LSA area = 0 interface type = 1 OSPF: flood LSA Type:1 AdvRtr:10.3.1.1 Age:1 LsId:10.3.1.1 OSPF: flood advertisement 10.3.1.1 throughout a specific area = 0 OSPF: attempting to flood rcvd LSA area = 0 interface type = 1 OSPF: flood LSA Type:2 AdvRtr:10.3.1.1 Age:3600 LsId:10.1.1.2 OSPF: flood advertisement 10.1.1.2 throughout a specific area = 0 OSPF: flood LSA Type:1 AdvRtr:10.2.1.1 Age:0 LsId:10.2.1.1 OSPF: flood advertisement 10.2.1.1 throughout a specific area = 0 OSPF: flooding type 1 advertisement out interface 10.1.1.1 OSPF: attempting to flood rcvd LSA area = 0 interface type = 1 OSPF: flood LSA Type:1 AdvRtr:10.3.1.1 Age:1 LsId:10.3.1.1 OSPF: flood advertisement 10.3.1.1 throughout a specific area = 0 OSPF: attempting to flood rcvd LSA area = 0 interface type = 1 OSPF: flood LSA Type:2 AdvRtr:10.3.1.1 Age:1 LsId:10.1.1.2 OSPF: flood advertisement 10.1.1.2 throughout a specific area = 0

debug ip ospf graceful-restart

Syntax: [no] debug ip ospf graceful-restart

Enable this command to receive information about OSPF graceful restart events, including restart phases, graceful Link-State Advertisement (LSA) transmit and receive activity, and syslog messages.

Brocade# debug ip ospf graceful-restart OSPF: graceful-restart debugging is on Brocade# LSA flush rcvd Type:4 AdvRtr:83.83.10.11 LsId:10.213.213.213 LSA flush rcvd Type:4 AdvRtr:83.83.10.11 LsId:10.213.213.213 LSA flush rcvd Type:4 AdvRtr:10.116.116.1 LsId:10.205.205.205 LSA flush rcvd Type:4 AdvRtr:10.116.116.1 LsId:10.205.205.205 rcv GRACE LSA from 10.1.14.1, age 0, Adv 10.213.213.213 install new GraceLSA, int 269, neighbor 10.1.14.1, age 0 rcv Grace_LSA from 10.1.14.1, area 0.0.0.10 Recvd grace lsa id=50331648 state=8 0x2dd5d5d5 0x2dd5d5d5 age=0 gr-state=0 neighbor 10.1.14.1 entering graceful restart state, timer 120, lsa age 0, max 120, helping 0 flood grace LSA, AdvRtr:10.213.213.213, Age:0 rcv GRACE LSA from 10.1.51.1, age 0, Adv 10.213.213.213 install new GraceLSA, int 779, neighbor 10.1.51.1, age 0

66 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 79

OSPF debug commands

rcv Grace_LSA from 10.1.51.1, area 0.0.0.10 Recvd grace lsa id=50331648 state=8 0x2dd5d5d5 0x2dd5d5d5 age=0 gr-state=0 neighbor 10.1.51.1 entering graceful restart state, timer 120, lsa age 0, max 120, helping 0 flood grace LSA, AdvRtr:10.213.213.213, Age:0 rcv GRACE LSA from 10.1.18.2, age 0, Adv 10.213.213.213 install new GraceLSA, int 2050, neighbor 10.1.18.2, age 0 rcv Grace_LSA from 10.1.18.2, area 0.0.0.10 Recvd grace lsa id=50331648 state=8 0x2dd5d5d5 0x2dd5d5d5 age=0 gr-state=0 neighbor 10.1.18.2 entering graceful restart state, timer 120, lsa age 0, max 120, helping 0 flood grace LSA, AdvRtr:10.213.213.213, Age:0 rcv GRACE LSA from 10.1.14.1, age 0, Adv 10.213.213.213 Update same instance GRACE LSA age to 0 in database, refresh neighbor 10.1.14.1 restart timer to 120 rcv GRACE LSA from 10.1.51.1, age 0, Adv 10.213.213.213 Update same instance GRACE LSA age to 0 in database, refresh neighbor 10.1.51.1 restart timer to 120 rcv GRACE LSA from 10.1.18.2, age 0, Adv 10.213.213.213 Update same instance GRACE LSA age to 0 in database, refresh neighbor 10.1.18.2 restart timer to 120 rcv GRACE LSA from 10.1.14.1, age 0, Adv 10.213.213.213 Update same instance GRACE LSA age to 0 in database, refresh neighbor 10.1.14.1 restart timer to 120 rcv GRACE LSA from 10.1.51.1, age 0, Adv 10.213.213.213 Update same instance GRACE LSA age to 0 in database, refresh neighbor 10.1.51.1 restart timer to 120 rcv GRACE LSA from 10.1.18.2, age 0, Adv 10.213.213.213 Update same instance GRACE LSA age to 0 in database, refresh neighbor 10.1.18.2 restart timer to 120

Brocade# no debug ip ospf graceful-restart OSPF: graceful-restart debugging is off

debug ip ospf log-empty-lsa

Syntax: [no]debug ip ospf log-empty-lsa

This command displays information about empty link state advertisements (LSAs) as shown in the following example.

Brocade# debug ip ospf log-empty-lsa Brocade(config-if-e1000-1/1/15)# debug ip ospf log-empty-lsa OSPF: empty-LSA logging debugging is on Brocade(config-if-e1000-1/1/15)# debug ip ospf flOSPF: originate router LSA, area 0 OSPF: No difference found, restart 0 OSPF: send ls request to neighbor 10.1.1.2, retran 0 OSPF: sending ls request last size 36, count 1 OSPF: LSA rcvd Type:1 AdvRtr:10.2.1.1 Age:297 LsId:10.2.1.1 Seq-Num 8000000e from Neighbor 10.1.1.2 OSPF: Received self originated LSA type 1 with id = 10.2.1.1 Seq-Num 8000000e OSPF: install a new lsa, type 1, ls_id 10.2.1.1, age 0, seq 8000000f area-id 0 OSPF: NSR Sync ACK received for LSA OSPF: ls_header.id 10.2.1.1 type 1 ToBesyncedState 2 OSPF: NSR : Sync node add, type 1, ls_id 10.2.1.1, age 0, seq 8000000f OSPF: send_ls_update to interface 10.1.1.1 (224.0.0.6) tb 962478204, retran 0 OSPF: tx LSA Type:1 AdvRtr:10.2.1.1 Age:1 LsId:10.2.1.1 OSPF: originate router LSA, area 0

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 67 53-1003076-02

Page 80

OSPF debug commands

OSPF: originate_router_links_advertisement gen new instance set 10.2.1.1 (not sent - wait for MinLSInterval) OSPF: LSA rcvd Type:1 AdvRtr:10.3.1.1 Age:1 LsId:10.3.1.1 Seq-Num 8000000f from Neighbor 10.1.1.2 OSPF: install a new lsa, type 1, ls_id 10.3.1.1, age 1, seq 8000000f area-id 0 OSPF: NSR Sync ACK received for LSA OSPF: ls_header.id 10.3.1.1 type 1 ToBesyncedState 2 OSPF: NSR : Sync node add, type 1, ls_id 10.3.1.1, age 1, seq 8000000f OSPF: LSA rcvd Type:2 AdvRtr:10.3.1.1 Age:3600 LsId:115.1.1.2 Seq-Num 80000005 from Neighbor 10.1.1.2 OSPF: install a new lsa, type 2, ls_id 10.1.1.2, age 3600, seq 80000005 area-id 0 OSPF: NSR Sync ACK received for LSA OSPF: ls_header.id 105.1.1.2 type 2 ToBesyncedState 2 OSPF: NSR : Sync node add, type 2, ls_id 10.1.1.2, age 3600, seq 80000005 oOSPF: trying age out LSA, id 10.1.1.2, len 32, type 2, from 10.3.1.1, age 3600 genNewLsa 0 area 0 OSPF: age out and remove lsa data base 10.1.1.2 odsOSPF: OSPF TIMER: Minlsa: sptr_database_entry generate_new_instance == TRUE for 1.2.1.1 OSPF: originate_delayed LSA, type 1, parm1: 0x0 OSPF: originate router LSA, area 0 OSPF: difference found, restart 0 OSPF: install a new lsa, type 1, ls_id 10.2.1.1, age 0, seq 80000010 area-id 0 OSPF: NSR Sync ACK received for LSA OSPF: ls_header.id 10.2.1.1 type 1 ToBesyncedState 2 OSPF: NSR : Sync node add, type 1, ls_id 10.2.1.1, age 0, seq 80000010 OSPF: OSPF: rcv LSA ack from 10.1.1.2, type 1, id 1.2.1.1, seq 0x8000000f, adv

10.2.1.1, age 1 OSPF: send_ls_update to interface 10.1.1.1 (224.0.0.6) tb 1017253324, retran 0 OSPF: tx LSA Type:1 AdvRtr:10.2.1.1 Age:1 LsId:10.2.1.1 OSPF: LSA rcvd Type:1 AdvRtr:10.3.1.1 Age:1 LsId:10.3.1.1 Seq-Num 80000010 from Neighbor 10.1.1.2 OSPF: install a new lsa, type 1, ls_id 10.3.1.1, age 1, seq 80000010 area-id 0 OSPF: NSR Sync ACK received for LSA OSPF: ls_header.id 10.3.1.1 type 1 ToBesyncedState 2 OSPF: NSR : Sync node add, type 1, ls_id 10.3.1.1, age 1, seq 80000010 OSPF: LSA rcvd Type:2 AdvRtr:10.3.1.1 Age:1 LsId:10.1.1.2 Seq-Num 80000006 from Neighbor 10.1.1.2 OSPF: install a new lsa, type 2, ls_id 10.1.1.2, age 1, seq 80000006 area-id 0 OSPF: NSR Sync ACK received for LSA OSPF: ls_header.id 10.1.1.2 type 2 ToBesyncedState 2 OSPF: NSR : Sync node add, type 2, ls_id 10.1.1.2, age 1, seq 80000006 OSPF: OSPF: rcv LSA ack from 10.1.1.2, type 1, id 10.2.1.1, seq 0x80000010, adv

10.2.1.1, age 1 OSPF: originate router LSA, area 0 OSPF: No difference found, restart 0

debug ip ospf lsa-generation

Syntax: [no] debug ip ospf lsa-generation

This command generates information about LSAs as shown in the following example.

Brocade# debug ip ospf lsa-generation OSPF: lsa generation debugging is on Brocade(config-if-e1000-1/1/15)#OSPF: originate router LSA, area 0 OSPF: trying age out LSA, id 10.2.1.1, len 36, type 1, from 10.2.1.1, age 3600 genNewLsa 0 area 0 OSPF: age out and remove lsa data base 10.2.1.1

68 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 81

OSPF debug commands

NOTE

debug ip ospf lsa-id

Syntax: [no] debug ip ospf lsa-id

This command generates information about OSPF LSA IDs as shown in the following example.

Brocade# debug ip ospf lsa-id Debug message destination: Console IP Routing: OSPF: flooding debugging is on OSPF: lsa generation debugging is on OSPF: ls-id 10.2.2.2 debugging is on

Brocade(config-ospf-router)# Debug: Jan 1 04:12:50 OSPF: LSA rcvd Type:1 AdvRtr:10.2.2.2 Age:1 LsId:10.2.2.2 Seq-Num 8000000e from Neighbor 10.9.9.2 Debug: Jan 1 04:12:50 OSPF: install a new lsa, type 1, ls_id 10.2.2.2, age 1, seq 8000000e area-id 0 Debug: Jan 1 04:12:50 OSPF: NSR Sync ACK received for LSA Debug: Jan 1 04:12:50 OSPF: ls_header.id 10.2.2.2 type 1 ToBesyncedState 2 Debug: Jan 1 04:12:50 OSPF: NSR : Sync node add, type 1, ls_id 10.2.2.2, age 1, seq 8000000e Debug: Jan 1 04:12:50 OSPF: attempting to flood rcvd LSA area = 0 interface type = 1 Debug: Jan 1 04:12:50 OSPF: flood LSA Type:1 AdvRtr:10.2.2.2 Age:1 LsId:10.2.2.2 Debug: Jan 1 04:12:50 OSPF: flood advertisement 10.2.2.2 throughout a specific area = 0 Debug: Jan 1 04:12:51 OSPF: LSA rcvd Type:1 AdvRtr:10.2.2.2 Age:1 LsId:10.2.2.2 Seq-Num 8000000f from Neighbor 10.9.9.2 Debug: Jan 1 04:12:51 OSPF: install a new lsa, type 1, ls_id 10.2.2.2, age 1, seq 8000000f area-id 0 Debug: Jan 1 04:12:51 OSPF: NSR Sync ACK received for LSA Debug: Jan 1 04:12:51 OSPF: ls_header.id 10.2.2.2 type 1 ToBesyncedState 2 Debug: Jan 1 04:12:51 OSPF: NSR : Sync node add, type 1, ls_id 10.2.2.2, age 1, seq 8000000f Debug: Jan 1 04:12:51 OSPF: attempting to flood rcvd LSA area = 0 interface type = 1 Debug: Jan 1 04:12:51 OSPF: flood LSA Type:1 AdvRtr:10.2.2.2 Age:1 LsId:10.2.2.2 Debug: Jan 1 04:12:51 OSPF: flood advertisement 10.2.2.2 throughout a specific area = 0

The debug ip ospf ls-id command must be enabled with debug ip ospf flood or debug ip ospf lsa-generation command.

debug ip ospf max-metric

Syntax: [no] debug ip ospf max-metric

This command displays information about a max-metric configuration.

Brocade# debug ip ospf max-metric OSPF: max-metric debugging is on Brocade(config-ospf-router)# max-metric router-lsa all-lsas Debug: Jan 1 04:20:05 OSPF: Max-metric advertisement started due to configuration change for vrf 0

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 69 53-1003076-02

Page 82

OSPF debug commands

debug ip ospf packet

Syntax: [no] debug ip ospf packet [ detail decimal | in | out | peer ip-addr | port [ethernet

• detail decimal—Refers to the level by bit 0 and 1 and stack trace send by bit 2.

• in—Refers only to the input.

• out—Refers only to the output.

• peer ip-addr—Matches with the peer (advertisement router).

• port—Matches with the I/O port.

• ethernet stackid/slot/port—Refers to the stack ID, slot, or Ethernet port.

• ve decimal—Refers to the number of the virtual Ethernet interface.

• src-ip ip-addr—Matches with the src-ip option and only to the input.

• type—Matches with the packet type.

• ack—Refers to the acknowledgement of the packets received.

• dd—Refers to the number of days.

• hello—Refers to the hello interval period.

• request—Refers to the request sent from a client to a server.

• update—Refers to the update to the packets.

This command generates information about the OSPF packets.

Brocade# debug ip ospf packet Brocade# OSPF: recv from:10.1.14.1 to 224.0.0.5 Intf:e 2/1/14 LS-Ack L:104 Auth:0 ID:10.213.213.213

OSPF: recv from:10.1.18.2 to 224.0.0.5 Intf:ve 18 LS-Ack L:104 Auth:0 ID:10.213.213.213

OSPF: send to:224.0.0.5 Intf:ve 36 Hello L:44 Auth:0 ID:10.10.10.77 DR:10.36.2.1 BDR:0.0.0.0 OSPF: send to:224.0.0.5 Intf:ve 36 Hello L:44 Auth:0 ID:10.10.10.77 DR:10.36.100.1 BDR:0.0.0.0 OSPF: send to:224.0.0.5 Intf:ve 511 Hello L:48 Auth:0 ID:10.10.10.77 DR:10.1.251.7 BDR:10.1.251.6 OSPF: send to:224.0.0.5 Intf:e 2/1/14 Hello L:48 Auth:0 ID:10.10.10.77 DR:10.1.14.2 BDR:10.1.14.1 OSPF: send to:224.0.0.5 Intf:e 2/1/21 LS-Ack L:104 Auth:0 ID:10.10.10.77

OSPF: send to:224.0.0.5 Intf:e 2/1/21 Hello L:48 Auth:0 ID:10.10.10.77 DR:0.0.0.0 BDR:0.0.0.0 OSPF: send to:224.0.0.5 Intf:ve 35 Hello L:48 Auth:0 ID:10.10.10.77 DR:10.1.35.16 BDR:10.1.35.15 OSPF: send to:10.1.251.6 Intf:ve 511 Hello L:48 Auth:0 ID:10.10.10.77 DR:0.0.0.0 BDR:0.0.0.0 OSPF: send to:10.1.18.2 Intf:e 4/1/12 Hello L:48 Auth:0 ID:10.10.10.77 DR:0.0.0.0 BDR:0.0.0.0 OSPF: recv from:10.1.35.15 to 224.0.0.5 Intf:ve 35 LS-Ack L:104 Auth:0 ID:41.41.41.41

OSPF: recv from:10.1.251.18 to 10.1.251.17 Intf:e 2/1/21 Hello L:48 Auth:0 ID:10.116.116.1 DR:0.0.0.0 BDR:0.0.0.0 OSPF: recv from:10.1.34.10 to 224.0.0.5 Intf:ve 34 LS-Ack L:104 Auth:0 ID:49.2.3.4

70 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 83

OSPF debug commands

OSPF: recv from:10.1.34.10 to 224.0.0.5 Intf:ve 34 Hello L:48 Auth:0 ID:49.2.3.4 DR:10.1.34.16 BDR:10.1.34.10 OSPF: recv from:10.1.251.18 to 224.0.0.5 Intf:e 2/1/21 LS-Upd L:136 Auth:0 ID:10.116.116.1 Cnt:3

OSPF: send to:224.0.0.5 Intf:ve 18 LS-Upd L:136 Auth:0 ID:10.10.10.77 Cnt:3 OSPF: send to:224.0.0.5 Intf:e 2/1/14 LS-Upd L:136 Auth:0 ID:10.10.10.77 Cnt:3 OSPF: send to:224.0.0.5 Intf:e 4/1/12 LS-Upd L:136 Auth:0 ID:10.10.10.77 Cnt:3 OSPF: send to:224.0.0.5 Intf:ve 34 LS-Upd L:136 Auth:0 ID:10.10.10.77 Cnt:3 OSPF: send to:224.0.0.5 Intf:ve 35 LS-Upd L:136 Auth:0 ID:10.10.10.77 Cnt:3 OSPF: recv from:10.1.251.6 to 224.0.0.5 Intf:ve 511 LS-Upd L:136 Auth:0 ID:10.116.116.1 Cnt:3 OSPF: send to:10.1.251.6 Intf:ve 511 LS-Ack L:84 Auth:0 ID:10.10.10.77 OSPF: recv from:10.1.91.18 to 224.0.0.5 Intf:ve 911 LS-Upd L:136 Auth:0 ID:10.116.116.1 Cnt:3 OSPF: send to:10.1.91.18 Intf:ve 911 LS-Ack L:84 Auth:0 ID:10.10.10.77 OSPF: recv from:10.1.14.1 to 224.0.0.5 Intf:e 2/1/14 LS-Upd L:136 Auth:0 ID:10.213.213.213 Cnt:3 OSPF: recv from:10.1.51.1 to 224.0.0.5 Intf:e 4/1/12 LS-Upd L:136 Auth:0 ID:10.213.213.213 Cnt:3 OSPF: recv from:10.1.18.2 to 224.0.0.5 Intf:ve 18 LS-Upd L:136 Auth:0 ID:10.213.213.213 Cnt:3 OSPF: recv from:10.1.14.1 to 224.0.0.5 Intf:e 2/1/14 LS-Ack L:84 Auth:0 ID:10.213.213.213 OSPF: recv from:10.1.18.2 to 224.0.0.5 Intf:ve 18 LS-Ack L:84 Auth:0 ID:10.213.213.213 OSPF: send to:224.0.0.5 Intf:ve 911 Hello L:48 Auth:0 ID:10.10.10.77 DR:10.1.91.16 BDR:10.1.91.18 OSPF: send to:224.0.0.5 Intf:loopback 1 Hello L:44 Auth:0 ID:10.10.10.77 DR:10.10.10.77 BDR:0.0.0.0 OSPF: send to:224.0.0.5 Intf:loopback 2 Hello L:44 Auth:0 ID:10.10.10.77 DR:10.10.62.10 BDR:0.0.0.0 OSPF: send to:224.0.0.5 Intf:loopback 3 Hello L:44 Auth:0 ID:10.10.10.77 DR:10.10.63.10 BDR:0.0.0.0 OSPF: send to:224.0.0.5 Intf:loopback 4 Hello L:44 Auth:0 ID:10.10.10.77 DR:10.10.64.10 BDR:0.0.0.0 OSPF: send to:224.0.0.5 Intf:e 2/1/21 LS-Ack L:84 Auth:0 ID:10.10.10.77 OSPF: recv from:10.1.35.15 to 224.0.0.5 Intf:ve 35 LS-Ack L:84 Auth:0 ID:41.41.41.41 OSPF: recv from:10.1.34.10 to 224.0.0.5 Intf:ve 34 LS-Ack L:84 Auth:0 ID:49.2.3.4 OSPF: recv from:10.1.251.18 to 224.0.0.5 Intf:e 2/1/21 LS-Upd L:100 Auth:0 ID:10.116.116.1 Cnt:2 OSPF: send to:224.0.0.5 Intf:ve 18 LS-Upd L:100 Auth:0 ID:10.10.10.77 Cnt:2 OSPF: send to:224.0.0.5 Intf:e 2/1/14 LS-Upd L:100 Auth:0 ID:10.10.10.77 Cnt:2 OSPF: send to:224.0.0.5 Intf:e 4/1/12 LS-Upd L:100 Auth:0 ID:10.10.10.77 Cnt:2 OSPF: send to:224.0.0.5 Intf:ve 34 LS-Upd L:100 Auth:0 ID:10.10.10.77 Cnt:2 OSPF: send to:224.0.0.5 Intf:ve 35 LS-Upd L:100 Auth:0 ID:10.10.10.77 Cnt:2 OSPF: recv from:10.1.251.6 to 224.0.0.5 Intf:ve 511 LS-Upd L:100 Auth:0 ID:10.116.116.1 Cnt:2 OSPF: send to:10.1.251.6 Intf:ve 511 LS-Ack L:64 Auth:0 ID:10.10.10.77 OSPF: recv from:10.1.91.18 to 224.0.0.5 Intf:ve 911 LS-Upd L:100 Auth:0 ID:10.116.116.1 Cnt:2 OSPF: send to:10.1.91.18 Intf:ve 911 LS-Ack L:64 Auth:0 ID:10.10.10.77 OSPF: recv from:10.1.14.1 to 224.0.0.5 Intf:e 2/1/14 LS-Upd L:100 Auth:0 ID:10.213.213.213 Cnt:2 OSPF: recv from:10.1.51.1 to 224.0.0.5 Intf:e 4/1/12 LS-Upd L:100 Auth:0 ID:10.213.213.213 Cnt:2 OSPF: recv from:10.1.18.2 to 224.0.0.5 Intf:ve 18 LS-Upd L:100 Auth:0 ID:10.213.213.213 Cnt:2

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 71 53-1003076-02

Page 84

OSPF debug commands

OSPF: recv from:10.1.251.6 to 224.0.0.5 Intf:ve 511 LS-Upd L:748 Auth:0 ID:10.116.116.1 Cnt:20 OSPF: send to:224.0.0.5 Intf:ve 18 LS-Upd L:748 Auth:0 ID:10.10.10.77 Cnt:20 OSPF: send to:224.0.0.5 Intf:e 2/1/14 LS-Upd L:748 Auth:0 ID:10.10.10.77 Cnt:20 OSPF: send to:224.0.0.5 Intf:e 4/1/12 LS-Upd L:748 Auth:0 ID:10.10.10.77 Cnt:20 OSPF: send to:224.0.0.5 Intf:ve 34 LS-Upd L:748 Auth:0 ID:10.10.10.77 Cnt:20 OSPF: send to:224.0.0.5 Intf:ve 35 LS-Upd L:748 Auth:0 ID:10.10.10.77 Cnt:20

debug ip ospf route

Syntax: [no] debug ip ospf route

Enable this command to receive information about OSPF graceful restart events, including restart phases, graceful Link-State Advertisement (LSA) transmit and receive activity, and syslog messages.

Brocade# debug ip ospf route 10.3.3.0 OSPF: debug ospf route 10.3.3.0 FCX648S-ADV Router(config-if-e1000-1/1/15)# debug ip ospf route 192.168.30.0 OSPF: debug ospf route 192.168.30.0 FCX648S-ADV Router(config-if-e1000-1/1/15)#OSPF: invalidate whole table - entry

192.168.30.0, state 0, path type 3 OSPF: calc ext route 192.168.30.0 OSPF: delete route 192.168.30.0 from rtm 0x367e7270, not_in_main 0 OSPF: calc ext route 192.168.30.0 OSPF: calc ext route 192.168.30.0 OSPF: calc ext route 192.168.30.0 OSPF: calc ext route 192.168.30.0 OSPF: ext route, net = 192.168.30.0, mask = 10.255.255.0 advrtr = 10.3.1.1, fwd =

0.0.0.0 OSPF: ext route changed 192.168.30.0, state 0 OSPF: ext route new 192.168.30.0, state 2, path type 3 OSPF: add route 192.168.30.0 to rtm, next hop 115.1.1.2, type 3, state 3, not_in_main 1 OSPF: add to ospf route table, to valid 192.168.30.0, state 3, path type 3 OSPF: Modify route 192.168.30.0, type 3, state 3, not_in_main 0, next hop 10.1.1.2 OSPF: modify/modify route 192.168.30.0 (fwd 367e7333), type 3, state 3, not_in_main 0, nhp 381c51c0 OSPF: validate route, new->valid 192.168.30.0, state 3, path type 3

debug ip ospf retransmission

Syntax: [no] debug ip ospf retransmission

This command generates internal information about OSPF retransmission of LSAs.

Brocade# debug ip ospf retransmission Brocade(config)# clear ip routeOSPF: examine each neighbor and add advertisement ls-id 10.3.13.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.3.13.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.1.2.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.1.2.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.3.3.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.3.3.0 to the retransmission list if necessary

72 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 85

OSPF debug commands

OSPF: examine each neighbor and add advertisement ls-id 10.1.2.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.1.2.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.24.2.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.24.2.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.3.3.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.3.3.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.3.13.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.3.13.0 to the retransmission list if necessary

Brocade(config)# OSPF: examine each neighbor and add advertisement ls-id 10.24.2.0 to the retransmission list if necessary OSPF: examine each neighbor and add advertisement ls-id 10.24.2.0 to the retransmission list if necessary

debug ip ospf spf

Syntax: [no] debug ip ospf spf

This command generates information about OSPF Shortest Path First (SPF) activity including SPF runs and calculations. Command output resembles the following example.

Brocade# debug ip ospf spf OSPF: spf-short debugging is on Disable neighbor Brocade(config-ospf-router)# Debug: Jan 1 02:38:55 OSPF: Schedule SPF(8001), in prog 0, ospf build_routing_table 0 phase 1 Debug: Jan 1 02:38:55 OSPF: schedule spf, init spf delay 0, next hold 0 (ticks) Debug: Jan 1 02:38:55 OSPF: Add to spf pending list, current time 96788, scheduled 96788, next run 96788 Debug: Jan 1 02:38:55 OSPF: Schedule SPF(7001), in prog 0, ospf build_routing_table 0 phase 1 Debug: Jan 1 02:38:55 OSPF: Schedule SPF(6002), in prog 0, ospf build_routing_table 0 phase 1 Debug: Jan 1 02:38:55 OSPF: timer: give semaphore, start spf phase 1, time 96789, scheduled 96788, run time 96788 Debug: Jan 1 02:38:55 OSPF: begin intra SPF run, chunk-id 0/-1 just_become_abr 0, is_abr 0 Debug: Jan 1 02:38:55 OSPF: invalidate whole routing table, recal_just_become_abr 0, just_become_abr 0 Debug: Jan 1 02:38:55 OSPF: running SPF for area 0 area-18ce7068 nextarea 0 next-area-id -1 Debug: Jan 1 02:38:55 OSPF: completed SPF for all areas Debug: Jan 1 02:38:55 OSPF: ROUTE CALC PHASE_INTRA end at 96789, is_abr 0 Debug: Jan 1 02:38:55 OSPF: ROUTE CALC PHASE_TRANSIT end at 96789 Debug: Jan 1 02:38:55 OSPF: ROUTE CALC PHASE_TYPE5 end at 96789 Debug: Jan 1 02:38:55 OSPF: ROUTE CALC PHASE_TYPE7 end at 96789 Debug: Jan 1 02:38:55 OSPF: summary phase, is_abr 0 Debug: Jan 1 02:38:55 OSPF: ROUTE CALC PHASE_SUMMARY end at 96789 Debug: Jan 1 02:38:55 OSPF: translation phase, is_abr 0 Debug: Jan 1 02:38:55 OSPF: ROUTE CALC PHASE_TRANSLATION end at 96789 Debug: Jan 1 02:38:55 OSPF: SPF_cleanup: current 96789, set next run time 96788, current hold 0, next hold 0

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 73 53-1003076-02

Page 86

RIP debug commands

Debug: Jan 1 02:38:55 OSPF: ROUTE CALC end at 96789, pending 0

debug ip ospf vrf

Syntax: [no] debug ip ospf vrf

This command generates debugging information about the OSPF Virtual Routing and Forwarding (VRF) instance.

Brocade# debug ip ospf vrf OSPF(one): send hello on area 0 interface 10.3.4.1

RIP debug commands

The following debug commands display debugging information for the Routing Information Protocol (RIP).

debug rip database

Syntax: [no] debug rip database

This command displays RIP database events.

Brocade# debug rip database Brocade(config-vif-11)# RIP(default-vrf): (v2) process response packet header: type:RESPONSE PACKET, version:2 RIP(default-vrf): refresh 10.1.2.0/24 metric 3 from 10.5.5.2 ve 11 RIP(default-vrf): existing route metric 2 from 10.4.4.1 ve 12 RIP(default-vrf): refresh 10.24.2.0/24 metric 4 from 10.5.5.2 ve 11 RIP(default-vrf): existing route metric 4 from 10.5.5.2 ve 11 RIP(default-vrf): (v2) process response packet header: type:RESPONSE PACKET, version:2 RIP(default-vrf): refresh 10.24.2.0/24 metric 4 from 10.4.4.2 ve 12 RIP(default-vrf): existing route metric 4 from 10.5.5.2 ve 11

debug rip events

Syntax: [no] debug rip events

This command displays RIP events.

Brocade# debug rip events Brocade(config-vif-11)# RIPng: update timer expired clear ipv routeRIPng: triggered update RIPng: garbage prefix 2001:DB8::/64 timer 1, metric 0, tag 0 from :: on interface NULL RIPng: garbage prefix 2001:DB8::/64 timer 1, metric 0, tag 0 from :: on interface NULL RIPng: Adding local connected route 2001:DB8::1/64 on interface v11 RIPng: Adding local connected route 2001:DB8::1/64 on interface v12 RIPng: update timer expired RIPng: Redistribute add route 2001:DB8::/64, type CONNECTED (1/0) RIPng: Redistribute add route 2001:DB8::/64, type CONNECTED (1/0)

74 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 87

NTP debug commands

This section describes the debug commands that generate debugging information about the NTP configurations.

debug ip ntp

server]

• algorithms - Displays information about the NTP system algorithms.

• association - Displays information about the NTP server and peer association.

• broadcast - Displays information about the NTP broadcast server and client.

• clockadjust - Displays information about the NTP clock-adjust process.

• errors - Displays information about the NTP error events.

• packet - Displays information about the NTP input and output packets.

• server - Displays information about the NTP server.

debug ip ntp algorithms

NTP debug commands

Syntax: [no] debug ip ntp algorithms

This command displays information about the NTP system algorithms. Command output resembles the following example.

Brocade# debug ip ntp algorithms NTP: ntp_peer_unfit: dist exceeded - root dist 16.00527999 of peer 10.25.96.13 has exceeded max dist 1.50096000 NTP: ntp_peer_unfit: unreachable - peer 10.25.96.13 is not reachable [peer->reach 0]

Brocade(config-ntp)# NTP: ntp_clock_filter: Adding offset 0, delay 0, disp 16 to filter[0] for peer 10.25.96.13 NTP: ntp_clock_filter: No acceptable samples available NTP: ntp_clock_filter: Adding offset 0.01133625, delay 0.27379156, disp

0.00001936 to filter[1] for peer 10.25.96.13 NTP: ntp_clock_filter: mitigated sample stats: n 1 offset 0.01133625 del

0.27379156 dsp 7.93750968 jit 0.00001525 NTP: ntp_peer_unfit: dist exceeded - root dist 8.07442072 of peer 10.25.96.13 has exceeded max dist 1.50096000 NTP: ntp_clock_select: number of final survivors 0 and leap vote 0 NTP: ntp_clock_select: No survivors found. sys_peer is set to NULL NTP: ntp_clock_filter: Adding offset 0.02724471, delay 0.30800050, disp

0.00001988 to filter[2] for peer 10.25.96.13 NTP: ntp_clock_filter: mitigated sample stats: n 2 offset 0.02724471 del

0.30800050 dsp 3.93752228 jit 0.00001525 NTP: ntp_peer_unfit: dist exceeded - root dist 4.09153779 of peer 10.25.96.13 has exceeded max dist 1.50096000 NTP: ntp_clock_update: at 430 sample 430 associd 2 NTP: ntp_rstclock: mu 67 new state 5 old state 5 offset -0.00001326

debug ip ntp association

Syntax: [no] debug ip ntp association

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 75 53-1003076-02

Page 88

NTP debug commands

This command displays information about the NTP server and peer association. Command output resembles the following example.

Brocade# debug ip ntp association NTP: peer_clear: peer 10.25.96.13 next 646 refid INIT NTP: newpeer: 10.25.96.13 mode client vers 4 poll 6 10 key 00000000 Flags Flags -> iBURST

SYSLOG: <14>Mar 21 17:44:33 Murali NTP: client association is mobilized for

10.25.96.13.

SYSLOG: <14>Mar 21 17:44:33 Murali NTP: The system clock is not synchronized to any time source. SYSLOG: <14>Mar 21 17:44:40 Murali NTP: Stratum is changed to 2.

SYSLOG: <14>Mar 21 17:44:40 Murali NTP: System clock is synchronized to

10.25.96.13.

debug ip ntp broadcast

Syntax: [no] debug ip ntp broadcast

This command displays information about the NTP broadcast server and client. Command output resembles the following example.

Brocade# debug ip ntp broadcast Oct 19 18:32:46 NTP: ntp_timer: interface mgmt1 is up, we may send broadcast packet Oct 19 18:32:49 NTP: Sending NTP broadcast packet to subnet 10.20.111.255 via port mgmt1 Oct 19 18:33:56 NTP: Sending NTP broadcast packet to subnet 10.20.111.255 via port mgmt1

debug ip ntp clockadjust

Syntax: [no] debug ip ntp clockadjust

This command displays information about the NTP clock-adjust process. Command output resembles the following example.

Brocade# debug ip ntp clockadjust NTP: ntp_clock_update: at 327 sample 327 associd 3 NTP: ntp_local_clock: hufbuf - ptr 1 mindly 0.23329046 huffpuff correction

-0.00067095 NTP: ntp_local_clock: clk offset 0.00917431 clk jit 0 clk stab 0 sys_poll 6 NTP: ntp_set_freq: drift 0.00000010, old freq 50000000 NTP: ntp_set_freq: new freq 49999995 NTP: ntp_adj_host_clock: new offset 0.00917431, freq 49999995 NTP: Adjusting the clock. offset 0.00917431, calib used 251687 NTP: After adjusting the clock. offset 0.00817431, calib used 252687 NTP: Adjusting the clock. offset 0.00817431, calib used 252687 NTP: After adjusting the clock. offset 0.00717431, calib used 253687 NTP: Adjusting the clock. offset 0.00717431, calib used 253687

debug ip ntp errors

Syntax: [no] debug ip ntp errors

This command displays information about the NTP error events.

76 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 89

NTP debug commands

debug ip ntp packet

Syntax: [no] debug ip ntp packet

This command displays information about the NTP input and output packets. Command output resembles the following example.

Brocade# debug ip ntp packet NTP: Sending the NTP client packet to 10.25.96.13 port 123 via port id INVALID

Leap 3, Version 4, Mode client, Stratum 16, Poll 6, Precision 2**-16, Root delay 0, Root disp 167, Ref Id INIT, Ref time 0.0 (00:00:00.0 GMT+00 Mon Jan 01 0) Org 0.0 (00:00:00.0 GMT+00 Mon Jan 01 0) Rec 0.0 (00:00:00.0 GMT+00 Mon Jan 01 0) Xmt 230.745068249 (00:03:50.745068249 GMT+00 Mon Jan 01 0) pkt len = 48 key 0

NTP: Received NTP server packet from 10.25.96.13 on port 123 via port id mgmt1 at 00:03:50.1959316492 GMT+00 Mon Jan 01 0

Leap 0, Version 4, Mode server, Stratum 1, Poll 6, Precision 2**-29, Root delay 0, Root disp 0, Ref Id 10.67.84.83, Ref time 3572876227.2200200252 (17:37:07.2200200252 GMT+00 Thu Mar 21 2013) Org 230.745068249 (00:03:50.745068249 GMT+00 Mon Jan 01 0) Rec 3572876241.37257170 (17:37:21.37257170 GMT+00 Thu Mar 21 2013) Xmt 3572876241.37302765 (17:37:21.37302765 GMT+00 Thu Mar 21 2013) pkt len =

48 key 0

NTP: Sending the NTP client packet to 10.25.96.13 port 123 via port id INVALID

Leap 3, Version 4, Mode client, Stratum 16, Poll 6, Precision 2**-16, Root delay 0, Root disp 169, Ref Id INIT, Ref time 0.0 (00:00:00.0 GMT+00 Mon Jan 01 0) Org 3572876241.37302765 (17:37:21.37302765 GMT+00 Thu Mar 21 2013) Rec 230.1959316492 (00:03:50.1959316492 GMT+00 Mon Jan 01 0) Xmt 232.784360585 (00:03:52.784360585 GMT+00 Mon Jan 01 0) pkt len = 48 key 0

NTP: Received NTP server packet from 10.25.96.13 on port 123 via port id mgmt1 at 00:03:52.1904063455 GMT+00 Mon Jan 01 0

Leap 0, Version 4, Mode server, Stratum 1, Poll 6, Precision 2**-29, Root delay 0, Root disp 0, Ref Id 10.67.84.83, Ref time 3572876227.2200200252 (17:37:07.2200200252 GMT+00 Thu Mar 21 2013) Org 232.784360585 (00:03:52.784360585 GMT+00 Mon Jan 01 0) Rec 3572876243.75963892 (17:37:23.75963892 GMT+00 Thu Mar 21 2013) Xmt 3572876243.76010686 (17:37:23.76010686 GMT+00 Thu Mar 21 2013) pkt len =

48 key 0

debug ip ntp server

Syntax: [no] debug ip ntp server

This command displays information about the NTP server. Command output resembles the following example.

Brocade# debug ip ntp server NTP: Received NTP client packet from 172.26.67.52 on port 123 via port id mgmt1 at 18:02:44.1139927355 GMT+00 Thu Mar 21 2013

Leap 0, Version 4, Mode client, Stratum 3, Poll 6, Precision 2**-16, Root delay 16102, Root disp 90471, Ref Id 172.26.67.65, Ref time 3572877762.1183164018 (18:02:42.1183164018 GMT+00 Thu Mar 21 2013) Org 3572877762.1141785444 (18:02:42.1141785444 GMT+00 Thu Mar 21 2013) Rec 3572877762.1183164018 (18:02:42.1183164018 GMT+00 Thu Mar 21 2013) Xmt 3572877764.1137502159 (18:02:44.1137502159 GMT+00 Thu Mar 21 2013) pkt len

= 48 key 0

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 77 53-1003076-02

Page 90

Source Guard debug commands

Brocade(config-ntp)# NTP: poll_update: for peer 10.250.229.100 hpoll 6 burst 0 retry 0 throttle 62 next poll 64 NTP: Received NTP server packet from 10.250.229.100 on port 123 via port id mgmt1 at 18:03:09.1891314446 GMT+00 Thu Mar 21 2013

Leap 0, Version 4, Mode server, Stratum 1, Poll 6, Precision 2**-29, Root delay 0, Root disp 0, Ref Id 10.67.84.83, Ref time 3572877762.155297680 (18:02:42.155297680 GMT+00 Thu Mar 21 2013) Org 3572877789.878229501 (18:03:09.878229501 GMT+00 Thu Mar 21 2013) Rec 3572877789.1401109720 (18:03:09.1401109720 GMT+00 Thu Mar 21 2013) Xmt 3572877789.1401162509 (18:03:09.1401162509 GMT+00 Thu Mar 21 2013) pkt len

= 48 key 0

NTP: poll_update: for peer 10.250.229.100 hpoll 6 burst 0 retry 0 throttle 62 next poll 67

Source Guard debug commands

The following debug command display information about the Source Guard transactions.

debug ip source guard

Syntax: [no] debug ip source guard

This command activates the IP source guard debugging.

Brocade# debug ip source guard SOURCE GUARD: debugging is on Brocade(config-vif-11)# IPSrcSec: Add ip addr 10.3.3.12 on port 5/1/2 vlan 14

SSH debug commands

The following debug ip ssh command displays information about the Secure Shell (SSH) transactions.

debug ip ssh

Syntax: [no] debug ip ssh

This command activates the SSH debugging.

Brocade# debug ip ssh

SSH: debugging is on

Brocade(config)#SSH: Incoming connection request received SSH: ssh_get_free_session_id: ssh.client[0].in_use is 0 SSH: Client session (0) established SSH: Outgoing connection is ready

ShtcpConnectionStatus[0]: connection established

SSH:ShtcpSend[0]: eSendComplete: the string length [24] !

ShtcpSendStatus[0]: eSendComplete SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [47]

78 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 91

SSH debug commands

SSH:ShtcpSend[0]: eSendComplete: the string length [216] !

ShtcpSendStatus[0]: eSendComplete SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [464] SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [144]

SSH:ShtcpSend[0]: eSendComplete: the string length [640] ! SSH: Outgoing connection is ready SSH: Data is ready to receive SSH: Data is ready to receive SSH: Remote closed connection SSH: ssh_close_session#0, No. of Clients#0.

ShtcpReceiveStatus[0]: Closed SSH: ShListen failed. ShtcpOpenPassive[0]: WaitingForConnection SSH: Incoming connection request received SSH: ssh_get_free_session_id: ssh.client[0].in_use is 0 SSH: Client session (0) established SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpConnectionStatus[0]: connection established

ShtcpReceiveStatus[0]: the string length [47]

SSH:ShtcpSend[0]: eSendComplete: the string length [24] !

ShtcpSendStatus[0]: eSendComplete

SSH:ShtcpSend[0]: eSendComplete: the string length [216] !

ShtcpSendStatus[0]: eSendComplete SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [464] SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [144]

SSH:ShtcpSend[0]: eSendComplete: the string length [640] ! SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [16]

ShtcpSendStatus[0]: eSendComplete

SSH:ShtcpSend[0]: eSendComplete: the string length [16] !

ShtcpSendStatus[0]: eSendComplete SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [52]

SSH:ShtcpSend[0]: eSendComplete: the string length [104] !

ShtcpSendStatus[0]: eSendComplete

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 79 53-1003076-02

Page 92

Synchronization debug commands

SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [68]

SSH:ShtcpSend[0]: eSendComplete: the string length [68] !

ShtcpSendStatus[0]: eSendComplete SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [116]

SSH:ShtcpSend[0]: eSendComplete: the string length [36] ! ShtcpSendStatus[0]: eSendComplete SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [68]

SSH:ShtcpSend[0]: eSendComplete: the string length [52] !

ShtcpSendStatus[0]: eSendComplete SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [148]

SSH:ShtcpSend[0]: eSendComplete: the string length [36] ! SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [68]

ShtcpSendStatus[0]: eSendComplete

SSH:ShtcpSend[0]: eSendComplete: the string length [36] ! SSH: Outgoing connection is ready SSH: Data is ready to receive

ShtcpReceiveStatus[0]: the string length [52]

ShtcpSendStatus[0]: eSendComplete

SSH:send_scp_data_to_ssh_client:buf len: 18, Qlen:18, Qaddr:256cd7e0, Qdepth#1 SSH: ShListen event for SSH session[0].

SSH:ShtcpSend[0]: eSendComplete: the string length [36] !

ShtcpSendStatus[0]: eSendComplete

SSH:ShtcpSend[0]: eSendComplete: the string length [68] !

ShtcpSendStatus[0]: eSendComplete

SSH:ssh_event_handler: Freeing tx_buf 18, QAddress: 256cd7e0 SSH: Outgoing connection is ready SSH: Outgoing connection is ready

Brocade# no debug ip ssh SSH: debugging is off

Synchronization debug commands

You can use the debug ip sync command to debug IP synchronization and faults in synchronization.

80 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 93

debug ip sync

Syntax: debug ip sync

This command displays debugging information about IP synchronization and faults in synchronization.

Brocade# debug ip sync Brocade(config-vif-11)# ND6 add sync: sent ip:2001:DB8::10 mac:none state:INCOMP port:ve 12 vlan:12 isR:0 to all other units ND6 add sync: sent ip:2001:DB8::10 mac:0000.0062.9f2d state:REACH port:e 3/3/1 vlan:12 isR:0 to all other units ND6 add sync: sent ip:2001:DB8::10 mac:0000.0062.9f2d state:STALE port:e 3/3/1 vlan:12 isR:0 to all other units

TCP debug commands

The following debug ip tcp commands display debugging information about the Transmission Control Protocol (TCP) transactions.

debug ip tcp

TCP debug commands

Syntax: [no] debug ip tcp [x:x::x:x | A.B.C.D]

• x:x::x:x - Specifies the IPv6 address.

• A.B.C.D - Specifies the IPv4 address.

This command displays TCP information for the specified IPv6 or IPv4 address. The following is the sample output from the debug ip tcp x:x::x:x command.

Brocade# debug ip tcp 2001:DB8::192:111:101:25 TCP: ipv6 address 2001:DB8::192:111:101:25 debugging is on Debug: Feb 11 10:46:57 TCP: sent packet (len=41) 2001:DB8::192:111:101:111:8197 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:18c2,seqn:11211247,ackn:835929143 Debug: Feb 11 10:46:57 TCP: sent packet (len=41) 2001:DB8::192:111:101:111:8197 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:1,hlen:5,chksum:14ac,seqn:11211268,ackn:835929143 Debug: Feb 11 10:46:57 TCP: rcvd packet (len=20) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8197 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:3bfa,seqn:835929143,ackn:11211268 Debug: Feb 11 10:46:57 TCP: rcvd packet (len=20) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8197 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:3bf9,seqn:835929143,ackn:11211290 Debug: Feb 11 10:46:57 TCP: rcvd packet (len=20) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8197 packet: syn:0,ack:1,rst:0,fin:1,hlen:5,chksum:3bce,seqn:835929143,ackn:11211290 Debug: Feb 11 10:46:57 TCP: sent packet (len=20) 2001:DB8::192:111:101:111:8197 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:1bce,seqn:11211290,ackn:835929144 Debug: Feb 11 10:47:05 TCP: sent packet (len=24) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 81 53-1003076-02

Page 94

TCP debug commands

packet: syn:1,ack:0,rst:0,fin:0,hlen:6,chksum:26f,seqn:4002716695,ackn:0 Debug: Feb 11 10:47:05 TCP: rcvd packet (len=24) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178 packet: syn:1,ack:1,rst:0,fin:0,hlen:6,chksum:17a4,seqn:2607451983,ackn:4002716696 Debug: Feb 11 10:47:05 TCP: sent packet (len=20) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:ef48,seqn:4002716696,ackn:2607451984 Debug: Feb 11 10:47:05 TCP: sent packet (len=75) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:17de,seqn:4002716696,ackn:2607451984 Debug: Feb 11 10:47:05 TCP: rcvd packet (len=20) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:2f49,seqn:2607451984,ackn:4002716751 Debug: Feb 11 10:47:05 TCP: rcvd packet (len=57) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:fc84,seqn:2607451984,ackn:4002716751 Debug: Feb 11 10:47:05 TCP: sent packet (len=20) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:ef11,seqn:4002716751,ackn:2607452021 Debug: Feb 11 10:47:05 TCP: rcvd packet (len=39) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:2af6,seqn:2607452021,ackn:4002716751 Debug: Feb 11 10:47:05 TCP: sent packet (len=20) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:ef11,seqn:4002716751,ackn:2607452040 Debug: Feb 11 10:47:05 TCP: sent packet (len=39) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:eabe,seqn:4002716751,ackn:2607452040 Debug: Feb 11 10:47:05 TCP: rcvd packet (len=20) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:2f11,seqn:2607452040,ackn:4002716770 Debug: Feb 11 10:47:05 TCP: rcvd packet (len=108) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:aa71,seqn:2607452040,ackn:4002716770 Debug: Feb 11 10:47:05 TCP: sent packet (len=20) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:eec6,seqn:4002716770,ackn:2607452128 Debug: Feb 11 10:47:05 TCP: rcvd packet (len=39) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:2a8b,seqn:2607452128,ackn:4002716770 Debug: Feb 11 10:47:05 TCP: sent packet (len=20) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:eec6,seqn:4002716770,ackn:2607452147 Debug: Feb 11 10:47:05 TCP: rcvd packet (len=108) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178

82 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 95

TCP debug commands

packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:80c6,seqn:2607452147,ackn:4002716770 Debug: Feb 11 10:47:05 TCP: sent packet (len=20) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:eec6,seqn:4002716770,ackn:2607452235 Debug: Feb 11 10:47:06 TCP: rcvd packet (len=108) 2001:DB8::192:111:101:25:179 -> 2001:DB8::192:111:101:111:8178 packet: syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:cd4a,seqn:2607452235,ackn:4002716770 Debug: Feb 11 10:47:06 TCP: sent packet (len=20) 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:17

debug ip tcp driver

Syntax: [no] debug ip tcp driver

This command activates the TCP driver events debugging.

Brocade# debug ip tcp driver TCP: driver debugging is on

debug ip tcp memory

Syntax: [no] debug ip tcp memory

This command activates the TCP memory debugging.

Brocade# debug ip tcp memory TCP: memory debugging is on

debug ip tcp packet

Syntax: [no] debug ip tcp packet

This command activates the TCP packets debugging.

Brocade# debug ip tcp packet TCP: packet debugging is on

debug ip tcp sack

Syntax: [no] debug ip tcp sack

This command activates the TCP Selective Acknowledgment (SACK) debugging.

Brocade# debug ip tcp sack TCP: sack debugging is on

debug ip tcp transactions

Syntax: [no] debug ip tcp transactions

This command activates the TCP transactions debugging.

Brocade# debug ip tcp transactions TCP: transactions debugging is on TCP: transactions debugging is on Debug: Feb 11 10:47:39 TCP: 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179: state change ESTABLISHED -> FIN-WAIT-1 Debug: Feb 11 10:47:39 TCP: sending FIN to 2001:DB8::192:111:101:25 port 179

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 83 53-1003076-02

Page 96

UDP debug commands

Debug: Feb 11 10:47:39 TCP: FIN to 2001:DB8::192:111:101:111 port 8178 acked Debug: Feb 11 10:47:39 TCP: 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179: state change FIN-WAIT-1 -> FIN-WAIT-2 Debug: Feb 11 10:47:39 TCP: 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179: state change FIN-WAIT-2 -> TIME-WAIT Debug: Feb 11 10:47:39 TCP: FIN processed Debug: Feb 11 10:47:39 TCP: 2001:DB8::192:111:101:111:8178 -> 2001:DB8::192:111:101:25:179: state change TIME-WAIT -> CLOSED Debug: Feb 11 10:47:39 TCP: TCB 14440934 destroyed Debug: Feb 11 10:47:58 TCP: 2001:DB8::192:111:101:111:8064 -> 2001:DB8::192:111:101:25:179: state change CLOSED -> SYN-SENT Debug: Feb 11 10:47:58 TCP: connected to 2001:DB8::192:111:101:111 port 8064 advertising MSS 1436 Debug: Feb 11 10:47:58 TCP: connection to 10.146.1.17 port 179 received MSS 1436 MSS is 1436 Debug: Feb 11 10:47:58 TCP: 2001:DB8::192:111:101:111:8064 -> 2001:DB8::192:111:101:25:179: state change SYN-SENT -> ESTABLISHED

UDP debug commands

You can use the debug ip udp command to display debugging information about the User Datagram Protocol (UDP) transactions.

debug ip udp

Syntax: [no] debug ip udp

This commands activates the UDP debugging.

Brocade# debug ip udp UDP: debugging is on

VRRP and VRRP-E debug commands

Use the following commands to filter the Virtual Router Redundancy Protocol (VRRP) and Virtual Router Redundancy Protocol - Extended (VRRP-E) messages for IPv4 or IPv6, and to debug specific IPv4 or IPv6 packets within the router.

debug ip vrrp packet

Syntax: [no] debug ip vrrp packet

This command displays debugging information of any VRRP or VRRP-E packets within the device.

Brocade# debug ip vrrp packet VRRP: packet debugging is on VRRP (IPv6): send advertise! ver:3 type:1 vrid:100 pri:255 num of ip:1 adv:100 chk:44853 Num of ip addr 1 2000::7:1 VRRP (IPv4): rcvd packet! ver:2 type:1 vrid:10 pri:255 #ip:1 aut:0 adv:1 chk:52198 Num of ip addr 1 10.10.10.2 from sender 10.10.10.2 VRRP (IPv6): rcvd packet! ver:3 type:1 vrid:10 pri:255 #ip:1 aut:0 adv:100 chk:53518

84 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 97

VRRP and VRRP-E debug commands

Num of ip addr 1 fe80::7:2 from sender 2000::7:2 VRRP (IPv6): rcvd packet! ver:3 type:1 vrid:11 pri:255 #ip:1 aut:0 adv:200 chk:53417 Num of ip addr 1 fe80::8:2 from sender ::

debug ip vrrp packet v4

Syntax: [no] debug ip vrrp packet v4

This command displays debugging information of VRRP or VRRP-E packets specific to IPv4 within the device.

Brocade# debug ip vrrp packet v4 VRRP (IPv4): packet debugging is on VRRP (IPv4): rcvd packet! ver:2 type:1 vrid:10 pri:255 #ip:1 aut:0 adv:1 chk:52198

Num of ip addr 1

10.10.10.2 from sender 10.10.10.2 VRRP (IPv4): rcvd packet! ver:2 type:1 vrid:10 pri:255 #ip:1 aut:0 adv:1 chk:52198

Num of ip addr 1

10.10.10.2 from sender 10.10.10.2 VRRP (IPv4): rcvd packet! ver:2 type:1 vrid:10 pri:255 #ip:1 aut:0 adv:1 chk:52198

Num of ip addr 1

10.10.10.2 from sender 10.10.10.2

debug ip vrrp packet v6

Syntax: [no] debug ip vrrp packet v6

This command displays debugging information of VRRP or VRRP-E packets specific to IPv6 within the device.

Brocade# debug ip vrrp packet v6 VRRP (IPv6): packet debugging is on VRRP (IPv6): rcvd packet! ver:3 type:1 vrid:10 pri:255 #ip:1 aut:0 adv:100 chk:53518 Num of ip addr 1 fe80::7:2 from sender 2000::7:2 VRRP (IPv6): rcvd packet! ver:3 type:1 vrid:11 pri:255 #ip:1 aut:0 adv:200 chk:53417 Num of ip addr 1 fe80::8:2 from sender :: VRRP (IPv6): send advertise! ver:3 type:1 vrid:100 pri:255 num of ip:1 adv:100 chk:44853 Num of ip addr 1 2000::7:1 VRRP (IPv6): rcvd packet! ver:3 type:1 vrid:10 pri:255 #ip:1 aut:0 adv:100 chk:53518 Num of ip addr 1 fe80::7:2 from sender 2000::7:2

10.10.10.2 from sender 10.10.10.2

debug ip vrrp events

Syntax: [no] debug ip vrrp events

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 85 53-1003076-02

Page 98

Web debug commands

This command displays debugging information of VRRP events only within the device.

Brocade# debug ip vrrp events VRRP: events debugging is on [44fd]VRRP (IPv4): 10.10.10.1 transit to master! IP addr 10.10.10.2 vrid 10, pri 100 [44fd]VRRP (IPv6): fe80::7:1 transit to master! IP addr fe80::7:1 vrid 10, pri 100 [4511]VRRP (IPv6): fe80::8:1 transit to master! IP addr fe80::8:1 vrid 11, pri 255

debug ip vrrp vrid

Syntax: [no] debug ip vrrp vrid decimal

This command filters VRRP or VRRP-E debugging using a virtual router identifier (VRID). The decimal variable refers to the VRID.

Brocade# debug ip vrrp vrid 100 Debug VRID: 100 for both IPv4 and IPv6 instances

Web debug commands

The following debug ip web commands display information about the web transactions.

debug ip web

Syntax: [no] debug ip web

This command activates the web debugging.

Brocade# debug ip web WEB: debugging is on

debug ip web-ssl

Syntax: [no] debug ip web-ssl

This commands activates web Secured Socket Layer (SSL) debugging.

Brocade# debug ip web-ssl WEB SSL: debugging is on

86 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Page 99

Chapter

IPv6 Diagnostics

This chapter contains the following sections:

•General IPv6 debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

•IPv6 MLD debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

•IPv6 OSPF debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

•DHCPv6 debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

•DHCPv6 show commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

•IPv6 PIM debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

•IPv6 RIP debug commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

General IPv6 debug commands

The debug ipv6 command enables the collection of information about IPv6 configurations for troubleshooting.

debug ipv6

Syntax: debug ipv6 address cache icmp mld nd packet ra

• address—The IPv6 address.

• cache—The IPv6 cache entry.

• icmp—The Internet Control Message Protocol version 6 (ICMPv6) address.

• mld—The Multicast Listener Discovery (MLD) protocol activity.

• nd—The neighbor discovery.

• packet—The IPv6 packet.

• ra—The router address.

IPv6 MLD debug commands

The following debug commands enable the functions related to Multicast Listening Discovery (MLD) debugging.

debug ipv6 mld

Syntax: [no] debug ipv6 mld

This command displays the debugging information about the received and sent packets of the MLD.

Brocade FastIron SX, FCX, and ICX Diagnostic Reference 87 53-1003076-02

Page 100

IPv6 MLD debug commands

Brocade# debug ipv6 mld Brocade# MLD: rcvd Report-V1(ty=131) g=ff03::26:2641 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:2642 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:2643 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:2644 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:2645 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:2646 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:2647 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:2648 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:2649 resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24 MLD: rcvd Report-V1(ty=131) g=ff03::26:264a resp=0, pkt S=fe80::200:3aff:fe01:3a86, on VL611 (phy 1/3/8), mld_size=24

debug ipv6 mld add-del-oif

Syntax: [no] debug ipv6 mld add-del-oif

This command is enabled with the MLD debug ipv6 mcache-source or debug ipv6 mcache-group commands at the same time.

Brocade# debug ipv6 mld show debug ip6 mld mcache-source 50F5 is enabled debug ip6 mld add-del-oif is enabled Brocade# show ipv6 mld mcache Example: (S G) cnt=: (S G) are the lowest 32 bits, cnt: SW proc. count OIF: 1/1/22 TR(1/1/32,1/1/33), TR is trunk, 1/1/32 primary, 1/1/33 output vlan 400, 0 cache vlan 601, 0 cache vlan 602, 0 cache vlan 701, 0 cache vlan 888, 0 cache vlan 1000, 5 caches. use 1 VIDX 1 (* 24:2402) cnt=85 OIF: tag TR(3/1/12) 7/1/17 age=0m up-time=24m, change=24m vidx=4130 (ref-cnt=0) 2 (* 24:2403) cnt=87 OIF: tag TR(3/1/12) 7/1/17 age=0m up-time=24m, change=24m vidx=4130 (ref-cnt=0) 3 (* 24:2404) cnt=249 OIF: tag TR(3/1/12) 7/1/17 age=0m up-time=24m, change=24m vidx=4130 (ref-cnt=0) 4 (* 24:2400) cnt=88 OIF: tag TR(3/1/12) 7/1/17 age=0m up-time=24m, change=24m vidx=4130 (ref-cnt=0) 5 (* 24:2401) cnt=254 OIF: tag TR(3/1/12) 7/1/17 age=0m up-time=24m, change=24m vidx=4130 (ref-cnt=0) Brocade# Debug: Sep 19 17:39:49 Del 7/1/17 from (0x0 0x242404) vlan 1000 Debug: Sep 19 17:39:49 Del 7/1/17 from (0x0 0x242403) vlan 1000 Debug: Sep 19 17:39:49 Del 7/1/17 from (0x0 0x242402) vlan 1000 Debug: Sep 19 17:39:49 Del 7/1/17 from (0x0 0x242401) vlan 1000

88 Brocade FastIron SX, FCX, and ICX Diagnostic Reference

53-1003076-02

Brocade FastIron SX, FCX, ICX Diagnostic Reference

Specifications and Main Features

Frequently Asked Questions

User Manual

About This Guide

Introduction

Supported Hardware

Audience

Disclaimer

Unsupported features

What’s new in this document

Document conventions

Text formatting

Command syntax conventions

Notes and caution notices

Related publications

Document feedback

Using Diagnostic Commands

Using debug commands

Brief and detail debug options

Generic debug commands

Disabling debug commands

System Level and Layer 1 Diagnostics

Layer 1 debug commands

Hardware backplane debug command

Loop detect debug commands

Port debug commands

System debug commands

Software licensing debug command

Layer 2 Diagnostics

STP debug commands

RSTP debug commands

MSTP debug commands

DHCP debug commands

GVRP debug commands

MAC address debug commands

MCT debug commands

MCT show commands

Packet-capture debug commands

VXLAN debug commands

Link aggregation debug commands

IP Diagnostics

ARP debug commands

BGP debug commands

DHCP snooping debug commands

GRE debug commands

ICMP debug commands

OSPF debug commands

RIP debug commands

NTP debug commands

Source Guard debug commands

SSH debug commands

Synchronization debug commands

TCP debug commands

UDP debug commands

VRRP and VRRP-E debug commands

Web debug commands

IPv6 Diagnostics

General IPv6 debug commands

IPv6 MLD debug commands