Analyzing Connection Problems - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

Analyzing connection problems

If a host is unable to detect its target (for example, a storage or tape device), you should begin
troubleshooting the problem in the middle of the data path. Determine if the problem is above or below the
starting point, then continue to divide the suspected problem path in half until you can pinpoint the
problem.
To check the logical connection:
1. Enter the switchShow command.
2. Review the output and determine if the device successfully logged into the switch:
• A device that is logically connected to the switch is registered as an F_Port or L_Port.
• A device that is not logically connected to the switch will be registered as something other than an
F_Port or L_Port, for example a G-Port.
3. If the missing device is logically connected, proceed to the next troubleshooting procedure
the name server
4. If the missing device is not logically connected, check the device and everything on that side of the
data path. Also see
This includes all aspects of the host OS, the driver settings and binaries, the device Basic Input Output
System (BIOS) settings, the SFP, the cable going from the switch to the device, the SFP on the switch side
of that cable, and all switch settings related to the device. See
failure:" on page 318 as the next potential trouble spot.
To check for Fibre Channel connectivity problems:
1. Enter the fcPing command, which:
• Checks the zoning configuration for the two ports specified.
• Generates an Extended Link Service frame (ELS) ECHO request to the source port specified and
validates the response.
• Generates an ELS ECHO request to the destination port specified and validates the response.
Regardless of the device's zoning, the fcPing command sends the ELS frame to the destination port. A
device can take any of the following actions:
• Send an ELS Accept to the ELS request.
• Send an ELS Reject to the ELS request.
• Ignore the ELS request.
There are some devices that do not support the ELS ECHO request. In these cases, the device will either
not respond to the request or send an ELS reject. When a device does not respond to the ELS request,
further debugging is required; however, do not assume that the device is not connected to the Fibre
Channel.
Following is sample output from the fcPing command in which one device accepts the request and
another device rejects the request:
switch:admin> fcping 10:00:00:00:c9:29:0e:c4 21:00:00:20:37:25:ad:05
Source:
Destination: 21:00:00:20:37:25:ad:05
Zone Check:
Pinging 10:00:00:00:c9:29:0e:c4 [0x20800] with 12 bytes of date:
received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1162 usec
received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1013 usec
received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1442 usec
received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1052 usec
received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1012 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
304 Troubleshooting
(NS):" on page 306.
"Correcting link failures" on page 317 for additional information.
10:00:00:00:c9:29:0e:c4
Not Zoned
"To check for a loop initialization
"To check