Brocade Communications Systems 8/40 Service Manual download pdf (Page 26)

BCSM IN A NUTSHELL 2008

Page 24 of 44

The fcping command can also be used to identify a marginal link. Issue fcping from the switch with the

questionable connection; use WWN of questionable device as the source and look at the response times,

consider using the length and number of frame operands to send more data. If you have a marginal

connection and send enough frames and/or data you should be able to catch responses with a much

longer response time:

NDA-ST03-B48:admin> fcping 10:00:00:00:c9:27:22:82 22:00:00:04:cf:bd:58:18

Source: 10:00:00:00:c9:27:22:82

Destination: 22:00:00:04:cf:bd:58:18

Zone Check: Zoned

Pinging 10:00:00:00:c9:27:22:82 [0x30c00] with 12 bytes of data:

received reply from 10:00:00:00:c9:27:22:82: 12 bytes time:501 usec

received reply from 10:00:00:00:c9:27:22:82: 12 bytes time:449 usec

received reply from 10:00:00:00:c9:27:22:82: 12 bytes time:473 usec

received reply from 10:00:00:00:c9:27:22:82: 12 bytes time:440 usec

received reply from 10:00:00:00:c9:27:22:82: 12 bytes time:444 usec

5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout

Round-trip min/avg/max = 440/461/501 usec …<truncated output>…

Possible responses to the fcping are: reply, time out (which indicated that the attached device does

not respond to the ELS echo frame request that is used by fcping), or fcping: Error destination

(or source) wwn invalid. This last response occurs when the device is not online or cannot be

discovered online.

Tip #2 – Interface media consists of an SFP or Fibre Channel cable. Remove and reinsert interface media.

Move interface media to a different port. Use porterrshow statistics to determine most likely interface

media to move.

Tip #3 – If the original marginal link error was not initiated by I/O activities or POST, then run porttest to

verify. While porttest is running, check the LLI statistic counts via errshow, porterrshow or

portshow command outputs.

Tip #4 – Always verify that the new media is “known good”. If the error was not initiated by I/O activities or

POST, then run porttest to verify correction.

Tip #5 – You have isolated the problem, it is the Nx_Port (HBA or storage controller card). Use the Nx_Port

utilities to troubleshoot this problem. You may need to verify with the latest HBA/controller driver before

replacing the device. Check the vendor compatibility matrix if it is not a Brocade HBA.

1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 45 46

No comments

Brocade Communications Systems 8/40 Service Manual Page 26