cable or SFP issue identify :

====================

SAN port loss of connection, SFP or cable?

There could be many reasons that can cause a fibre link lossing the connection. It
could be HBA issue, SFP, cable or switch problem.

For more SAN switch trouble shooting, see Brocade SAN switch trouble shooting
commands, Here show some tips to determine whether the SFP or a cable is the cause
of the loss of connectivity, perform the following:

Check the output of "porterrshow " from the switch.

"enc out " errors alone imply primarily cable problem.

"enc out " and "crc err " combination imply primarily GBIC/SFP problem.

To find out if source or destination SFP is causing the error, Check the Output of
"portshow x" where x is the port number.

If the pair of "Lr_in " and "Ols_out " as well the "Lr_out " and "Ols_in " values
are "quite" equal, it is a normal case.

If one counter is significantly higher than the other, the link problems either
"reached" the switch ("in" > "out") or are caused by the switch ("out" >
"in").

Note: If the "Ols_in value is higher than the "Lr_out one, then the "problem source
is, in most cases, more related to the attached device (sending those offline
sequences) and the switch responds to them with a "link reset".

enc_out ; Encoding error outside of frames

crc err ; Frames with CRC errors Lr_in ;

Link reset In (primitive sequence), does not apply to FL_Port Lr_out ;

Link reset Out (primitive sequence), does not apply to FL_Port Ols_in ;

Offline reset in (primitive sequence), does not apply to FL_Port Ols_out ;

Offline reset out (primitive sequence), does not apply to FL_Port

Planning Phase

1) Plan your Principal Switch for the fabric

a. You should not allow the fabric to determine the Principal Switch because all
fabric changes (Zone Changes) should occur at the Principal Switch. This switch
should be the most highly available switch in the fabric.

2) Plan your fabric type

a. The type of fabric being created (Full Mesh or Core-Edge) really doesn�t matter
for the merge, but you need to know this to properly plan for your ISLs.
3) Plan your ISLs

a. Plan which ports will be ISLs

4) Plan any server or storage moves as needed.

a. Minimize these and/or perform them a few days after a successful merge.

5) Determine zone merge method

a. The easiest Zone Merge is to determine which Fabric (Zone Config) will be used
as the foundation to the new Fabric, and disable Zoning on the switches in the
other fabric.

i. This is advantageous if you have single switch fabrics.

ii. When you Disable Zoning all existing Zone configurations will be merged, but
disabled.

iii. This choice of which Zone Config to keep should match with the Principal
Switch choice made earlier.

b. The other (more difficult) method is to manually export all Zone Configuration
information from each Fabric and import it into the other. Then you will need to
name the Zone Config�s in both Fabrics to the same name and verify that all the
zone configuration information matches.

6) Order Port Licenses and Fiber cables as needed to perform your merge.

Implementation Phase for Disable Zoning Merge Method

1) Shutdown all servers on the fabric that is to be merged.

2) Disable Zoning on the Principal Switch of the fabric that is to be merged.

a. This should be enough to disable zoning on the whole fabric, if not then Disable
Zoning on every switch in the fabric that is to be merged.

3) Connect ONE ISL from one merged fabric switch to the target fabric.

a. Use the Brocade Web Interface on the target fabric switch to monitor to the
merge.

b. If switches become segmented review the Switch Events for errors and attempt
again.

4) Once the merge is successful you can continue with the configuration.

5) View the current Zone Configuration

a. You should see zones from the merge appear as available, but not active.

6) Update your Active Zone Configuration Set as needed to complete the Merge

a. Save and Activate the new Zone Configuration.

7) Add additional ISL links as needed to make a fault tolerant fabric.

8) Configure the Principal Switch for the new merged fabric.

9) Turn on the servers previously shutdown.