Brocade Fabric OS Troubleshooting and Diagnostics Guide v6.2.0 (53-1001187-01, April 2009)

Fabric OS Troubleshooting and Diagnostics Guide 19
53-1001187-01
Fibre Channel Router connectivity
2
B/s (1s) - - 0 0
B/s (64s) - - 1 1
Txcrdz (1s) - - 0 -
Txcrdz (64s) - - 0 -
F/s (1s) - - 0 0
F/s (64s) - - 2743 0
Words - - 2752748 2822763
Frames - - 219849 50881
Errors - - - 0
Hop In Port Domain ID (Name) Out Port BW Cost
---------------------------------------------------------
1 3 10 (web229) 12 1G 1000
Port 3 12
Tx Rx Tx Rx
-----------------------------------------------
B/s (1s) 36 76 0 0
B/s (64s) 5 5 5 5
Txcrdz (1s) 0 - 0 -
Txcrdz (64s) 0 - 0 -
F/s (1s) 1 1 0 0
F/s (64s) 0 0 0 0
Words 240434036 2294316 2119951 2121767
Frames 20025929 54999 162338 56710
Errors - 4 - 0
Hop In Port Domain ID (Name) Out Port BW Cost
---------------------------------------------------------
2 14 8 (web228) E - -
(output truncated)
For details about the pathInfo command, see the Fabric OS Command Reference.
Performance issues
Symptom General slow-down in FCR performance and scalability.
Probable cause and recommended action
As LSAN zone databases get bigger, it takes more switch resources to process them. Use the
enforce tag feature to prevent a backbone switch from accepting unwanted LSAN zone databases
into its local database.
Symptom Host application times out.
Probable cause and recommended action
The FCR tends to take a long time, more than 5 seconds, to present and setup paths for the proxy
devices. Certain hosts are able to do discovery much faster as a result they end up timing out. Use
the speed tag feature to always present target proxy to the host and import them faster. This helps
sensitive hosts to do a quick discovery without timing out or cause an application failure.