Home » Dell Manuals » Hubs & Switches » Dell Brocade 6520 » Manual Viewer

Dell Brocade 6520 Fabric OS Troubleshooting and Diagnostics Guide v7.1.0 - Page 35

errors are recorded on internal port 0/284 on domain 2, which is the potential faulty link.

Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

FC-FC routing connectivity 2 In the following example, superping is invoked using the fcPing --allpaths command to destination domain 165. The following example displays each hop as (Domain1/Index1-> Domain2/Index2) format. To reach destination domain 165 from source domain 3 there are 2 unique end-to-end paths. In the first path, the frame traverses from egress port index 205 on source domain 3 to ingress port index 25 on domain 207. On domain 207 the frame traverses from egress port index 42 to ingress port index 3 in domain 101. On domain 101 the frame goes from egress port index 16 to ingress port index 99 on domain 165. ECP80:FID128:admin> fcping -allpaths 165 Pinging(size:12 bytes) destination domain 165 through all paths PATH SWITCH1--> SWITCH2--> SWITCH3 SWITCH4 1. (3/EMB, 3/205)[128] (207/25,207/42)[128] (101/3,101/16)[128] (165/99,165/0)[128] 2. (3/EMB, 3/204)[128] (207/27,207/42)[128] (101/3,101/16)[128] (165/99,165/0)[128] STATUS SUCCESS SUCCESS Superping can isolate links with failures so that you can further investigate these ISLs to determine the exact links giving the errors. NOTE Superping provides an indication if all ISLs are covered. If all the ISLs are not covered, you can increase the coverage count and maximum retries to transmit, so that complete coverage of all ISLs is achieved. Consider the following example in which a few errors are recorded on ISLs 3/205-->2/25, 3/204-->2/27, 2/42-->101/3, and 2/1-->101/8. But a maximum of 100 percentage errors are recorded on internal port 0/284 on domain 2, which is the potential faulty link. ISL COVERAGE SNO ISL STATUS 1 3/123[128]--> 165/96[128] SUCCESS(5/5) 2 3/205[128]--> 2/25[128] FAILURE(7/50) 3 3/204[128--> 2/27[128] FAILURE(11/50) 4 165/99[128]--> 101/16[128] SUCCESS(5/5) 6 2/42[128]--> 101/3[128] FAILURE(10/67) 7 2/1[128]--> 101/8[128] FAILURE(8/33) INTERNAL PORT COVERAGE SNO DOMAIN INTRNL_PORT STATUS 1 2[128] 0/272 SUCCESS(40/40) 2 2[128] 0/276 SUCCESS(44/44) 3 2[128] 0/280 SUCCESS(30/30) 4 2[128] 0/284 FAILURE(20/20)

Section	Page
About This Document	11
How this document is organized	11
Supported hardware and software	12
What’s new in this document	12
Document conventions	13
Text formatting	13
Command syntax conventions	13
Command examples	13
Notes, cautions, and warnings	14
Key terms	14
Additional information	14
Brocade resources	14
Other industry resources	15
Getting technical help	15
Document feedback	16
Introduction	17
Troubleshooting overview	17
Network time protocol	17
Most common problem areas	18
Questions for common symptoms	18
Gathering information for your switch support provider	21
Setting up your switch for FTP	21
Capturing a supportSave	21
Capturing output from a console	22
Capturing command output	23
Building a case for your switch support provider	23
Basic information	23
Detailed problem information	24
Gathering additional information	25
General	27
Licenses	27
Time	27
Frame Viewer	28
Switch message logs	28
Switch boot	29
Rolling Reboot Detection	30
FC-FC routing connectivity	32
Generating and routing an ECHO	32
Superping	33
Route and statistical information	36
Performance issues	37
Connectivity	39
Port initialization and FCP auto-discovery process	39
Link issues	41
Connection problems	41
Checking the physical connection	41
Checking the logical connection	42
Checking the Name Server	42
Link failures	44
Determining a successful speed negotiation	44
Checking for a loop initialization failure	45
Checking for a point-to-point initialization failure	45
Correcting a port that has come up in the wrong mode	46
Marginal links	46
Troubleshooting a marginal link	47
Device login issues	49
Pinpointing problems with device logins	49
Media-related issues	51
Testing a port’s external transmit and receive path	52
Testing a switch’s internal components	52
Testing components to and from the HBA	52
Segmented fabrics	52
Reconciling fabric parameters individually	53
Downloading a correct configuration	54
Reconciling a domain ID conflict	54
Reconciling incompatible software features	55
Port mirroring	56
In-Order Delivery	56
Port mirroring considerations	56
Supported platforms	57
Maximum mirror connections	58
Configuring a port to be a mirror port	58
Adding a port mirror connection	58
Deleting a port mirror connection	59
Displaying port mirror connections	59
Configuration	61
Configuration upload and download issues	61
Gathering additional information	64
Brocade configuration form	64
Firmware Download Errors	67
Blade troubleshooting tips	67
Firmware download issues	68
Troubleshooting with the firmwareDownload command	70
Gathering additional information	71
USB error handling	71
Considerations for downgrading firmware	72
Preinstallation messages	72
Blade types	74
Firmware versions	74
Platform	75
Routing	75
Security	77
Passwords	77
Password recovery options	78
Device authentication	78
Protocol and certificate management	79
Gathering additional information	79
SNMP	80
Gathering additional information	80
FIPS	80
Virtual Fabrics	81
General Virtual Fabrics troubleshooting	81
Fabric identification issues	82
Logical Fabric issues	82
Base switch issues	83
Logical switch issues	84
Switch configuration blade compatibility	85
Gathering additional information	86
ISL Trunking	87
Link issues	87
Buffer credit issues	88
Getting out of buffer-limited mode	88
Zoning	89
Overview of corrective action	89
Verifying a fabric merge problem	89
Verifying a TI zone problem	89
Segmented fabrics	90
Zone conflicts	91
Correcting a fabric merge problem quickly	92
Changing the default zone access	93
Editing zone configuration members	93
Reordering the zone member list	93
Checking for Fibre Channel connectivity problems	94
Checking for zoning problems	95
Gathering additional information	96
Diagnostic Features	97
About Fabric OS diagnostics	97
Diagnostic information	97
Power-on self test	98
Disabling POST	100
Enabling POST	100
Switch status	100
Viewing the overall status of the switch	100
Displaying switch information	101
Displaying the uptime for a switch	102
Using the SpinFab and portTest commands	103
Debugging spinFab errors	104
Clearing the error counters	105
Enabling a port	105
Disabling a port	106
Diagnostic Port (D_Port)	106
Understanding D_Port	107
Supported topologies	109
Using D_Port without HBAs	111
Using D_Port with HBAs	113
Controlling testing	116
Example test scenarios and output	116
Port information	121
Viewing the status of a port	121
Displaying the port statistics	122
Displaying a summary of port errors for a switch	123
Equipment status	124
Checking the temperature, fan, and power supply	124
Checking the status of the fans	124
Checking the status of a power supply	125
Checking temperature status	125
System message log	126
Displaying the system message log, with no page breaks	126
Displaying the system message log one message at a time	127
Clearing the system message log	127
Port log	127
Viewing the port log	127
Syslogd configuration	129
Configuring the host	129
Configuring the switch	130
Automatic trace dump transfers	131
Specifying a remote server	131
Enabling the automatic transfer of trace dumps	131
Setting up periodic checking of the remote server	131
Saving comprehensive diagnostic files to the server	132
Switch Type and Blade ID	133
Hexadecimal Conversion	137
Example conversion of the hexadecimal triplet Ox616000	137
Decimal-to-hexadecimal conversion table	138

Match case Limit results 1 per page

Fabric OS Troubleshooting and Diagnostics Guide

53-1002751-01

FC-FC routing connectivity

In the following example, superping is invoked using the

fcPing --allpaths

command to destination

domain 165. The following example displays each hop as (Domain1/Index1-> Domain2/Index2)

format. To reach destination domain 165 from source domain 3 there are 2 unique end-to-end

paths. In the first path, the frame traverses from egress port index 205 on source domain 3 to

ingress port index 25 on domain 207. On domain 207 the frame traverses from egress port index

42 to ingress port index 3 in domain 101. On domain 101 the frame goes from egress port index

16 to ingress port index 99 on domain 165.

ECP80:FID128:admin> fcping -allpaths 165

Pinging(size:12 bytes) destination domain 165 through all paths

PATH SWITCH1-->

SWITCH2-->

SWITCH3

SWITCH4

STATUS

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

(3/EMB, 3/205)[128] (207/25,207/42)[128] (101/3,101/16)[128] (165/99,165/0)[128]

SUCCESS

(3/EMB, 3/204)[128] (207/27,207/42)[128] (101/3,101/16)[128] (165/99,165/0)[128]

SUCCESS

Superping can isolate links with failures so that you can further investigate these ISLs to determine

the exact links giving the errors.

NOTE

Superping provides an indication if all ISLs are covered. If all the ISLs are not covered, you can

increase the coverage count and maximum retries to transmit, so that complete coverage of all ISLs

is achieved.

Consider the following example in which a few errors are recorded on ISLs

3/205-->2/25

3/204-->2/27

2/42-->101/3

, and

2/1-->101/8

. But a maximum of 100 percentage

errors are recorded on internal port 0/284 on domain 2, which is the potential faulty link.

ISL COVERAGE

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

SNO

ISL

STATUS

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

3/123[128]--> 165/96[128] SUCCESS(5/5)

3/205[128]--> 2/25[128]

FAILURE(7/50)

3/204[128--> 2/27[128]

FAILURE(11/50)

165/99[128]--> 101/16[128]

SUCCESS(5/5)

2/42[128]--> 101/3[128]

FAILURE(10/67)

2/1[128]--> 101/8[128]

FAILURE(8/33)

INTERNAL PORT COVERAGE

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

SNO

DOMAIN

INTRNL_PORT

STATUS

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

2[128] 0/272

SUCCESS(40/40)

2[128] 0/276

SUCCESS(44/44)

2[128] 0/280

SUCCESS(30/30)

2[128] 0/284

FAILURE(20/20) <== 100% failure

When an echo frame is dropped, all the ISLs in the path are marked as failed. It is not possible to

determine the exact ISL link that dropped the frame. Due to this, all the ISLs in the path record

some failures. But the ISL with the actual error, has the maximum percentage of failures, as this

ISL when selected in any possible path causes the echo frame to be dropped and accumulates a

higher failure percentage.