Developers Guide

22 Fabric OS Troubleshooting and Diagnostics Guide
53-1003141-01
FC-FC routing connectivity
2
Target port is Embedded
Hop In Port Domain ID (Name) Out Port BW Cost
-----------------------------------------------------------------------------
0 2 1 (sw0) 6 4G 500
1 23 2 (sw0) 8 4G 500
2 4 3 (sw0) 3 4G 500
3 2 4 (sw0) 24 4G 10000
4 3 7 (switch_3) 2 4G 500
5 27 5 (switch_3) 24 - -
Reverse path
6 24 5 (switch_3) 27 4G 500
7 2 7 (switch_3) 3 4G 500
8 24 4 (sw0) 2 4G 500
9 3 3 (sw0) 4 4G 10000
10 8 2 (sw0) 23 4G 500
11 6 1 (sw0) 2 - -
(output truncated)
For details about the pathInfo command, refer to 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 set up paths for the proxy
devices. Certain hosts are able to do discovery much faster and, as a result, they end up timing out.
Use the speed tag feature to always present the target proxy to the host. This helps sensitive hosts
to do a quick discovery without timing out or causing an application failure.