Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 8
Registered: ‎02-10-2010

200e Fabric Switch port errors

We have 2 x 200e switches between SAN and Blades Enclosure.  One is for redundancy.

I have just added 4 SFPs to both switches and added the licenses successfully.

1)     But I have just noticed that the ports on the 2nd switch have lots of errors on them.

As the attachment shows, port 9, which has only been in there 2 hours already has 43,000 errors.  Is this normal?

2)     As shown in the attachment, 2 of the new ports on switch 2 (ports 8 and 10) are showing as online, whereas all the others (excluding port 0) are showing in-synch.  Should these be showing as Online or In-Synch for a redundant switch?

All online ports have 0 errors and show as F-Ports.  All In-Synch ports show as U-Ports and a lot of these have a lot of errors.

One In-Synch port has 1 billion errors in 2 years.  Is this normal?

Thanks

Occasional Contributor
Posts: 5
Registered: ‎04-10-2008

Re: 200e Fabric Switch port errors

In-Sync  means that light is being received but that the device at the other end is not 'alive'

Lights are on but no body is home.

Most common cause of port errors is 'encoding out of frame' which for the most part can be ignored.

You should post the output of 'switchshow' and 'porterrshow'

Occasional Contributor
Posts: 8
Registered: ‎02-10-2010

Re: 200e Fabric Switch port errors

Hi - Thanks for the advice.

When a blade is on that uses a port on the primary and a port on the redundant switch, should the port on the redundant switch be showing as Online or In-Synch?  For some reason, 2 of the new ports are showing as online. I'm not sure why.

Below are the results of the commands you mentioned.  Porterrshow is in the attachment.

Primary Switch

switchshow
switchName:    
switchType:     34.0
switchState:    Online
switchMode:     Native
switchRole:     Principal
switchDomain:   1
switchId:       fffc01
switchWwn:     
zoning:         ON
switchBeacon:   OFF

Area Port Media Speed State     Proto
=====================================
  0   0   id    N4   Online           F-Port 
  1   1   id    N4   No_Light
  2   2   id    N4   Online           F-Port 
  3   3   id    N4   Online           F-Port 
  4   4   id    N4   Online           F-Port 
  5   5   id    N4   Online           F-Port 
  6   6   id    N4   Online           F-Port 
  7   7   id    N4   No_Light
  8   8   id    N4   Online           F-Port 
  9   9   id    N4   Online           F-Port 
10  10   id    N4   Online           F-Port 
11  11   id    N4   Online           F-Port 
12  12   --    N4   No_Module        (No POD License) Disabled
13  13   --    N4   No_Module        (No POD License) Disabled
14  14   --    N4   No_Module        (No POD License) Disabled
15  15   --    N4   No_Module        (No POD License) Disabled


Redundant Switch

switchshow
switchName:    
switchType:     34.0
switchState:    Online
switchMode:     Native
switchRole:     Principal
switchDomain:   1
switchId:       fffc01
switchWwn:     
zoning:         ON
switchBeacon:   OFF

Area Port Media Speed State     Proto
=====================================
  0   0   id    N4   Online           F-Port 
  1   1   id    N4   No_Light
  2   2   id    N4   In_Sync
  3   3   id    N4   In_Sync
  4   4   id    N4   In_Sync
  5   5   id    N4   In_Sync
  6   6   id    N4   In_Sync
  7   7   id    N4   No_Light
  8   8   id    N4   Online           F-Port 
  9   9   id    N4   In_Sync
10  10   id    N4   Online           F-Port 
11  11   id    N4   In_Sync
12  12   --    N4   No_Module        (No POD License) Disabled
13  13   --    N4   No_Module        (No POD License) Disabled
14  14   --    N4   No_Module        (No POD License) Disabled
15  15   --    N4   No_Module        (No POD License) Disabled

Thanks

New Contributor
Posts: 3
Registered: ‎04-13-2007

Re: 200e Fabric Switch port errors

Nclarke - regarding your port errors...

I also get these from time to time.  A few categories I find them in:

1.   A host reboots.  On my systems this brings down the HBA during the boot cycle.  When the system comes back up it has to reattach to the fabric which seems to cause a lot of port errors as the autonegotiation takes place.  Once it is on the fabric the port errors stop accumulating.  Of course to check this out you have to know when your hosts reboot.    Not something you need to fix, you just notice the reboots and move on.

2.  Bad cables / dirty connectors / bad optics.  Happily I don't get a lot of these.  I noticed you have a lot of port errors but no actual traffic frames on one of your switches.  (Frames do get sent when the hosts reboot).  You might clean the connectors, change the cables, or try different optics.

3.  Wrong optics.  Gotta laugh about this one.  Had multimode short wave SFP on one end of a cable and single mode long wave on the other side.  Hey - they fit together physically!  Optics could actually tell something was there and was in some form of in_sync with tons of errors.  After scratching my head for two hours I figured it out and put the same optics on both sides and fixed the problem.

4.  Distance too great.  I tried to stretch multimode connections almost a kilometer.  Kind of even worked some of the time.  Took lots of errors and hosts complained that their disk would vanish on them.  Went to single mode and fixed the problem.  Could also be a speed mismatch problem if you hardcode your speed settings.

...Roy

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook