Brocade 8Gb Switches may experience high er_bad_os counts (Doc ID 1117643.1)

Last updated on JUNE 27, 2016

Applies to:

Brocade 300 Switch - Version Not Applicable and later
Information in this document applies to any platform.
Applies to:
Brocade Switches with Fabric OS v6.x and Oracle/STK 8G devices but could effect Oracle/STK devices below 8G (see note below).


Symptoms

The following symptoms maybe a result of the fillword parameter being incorrectly set on the Brocade Switch if they occur against an 8Gb (or above) device.

1. Rapidly increasing "er_bad_os" counts logged by the Brocade Switch.

2. The following Warnings being written to the Brocade fabric log.



Changes

The "portcfgfillword" command has changed in FOS:

In Fabric OS v6.3.0 ---the "portcfgfillword" command was added and the fillword could be hard set to:
0 |-idle-idle Sets IDLE mode in the Link Init and IDLE as the fill word (default), or
1 | -arbff-arbff Sets ARB(ff) in the Link Init and ARB(ff) as the fill word.

 

In Fabric OS v6.3.1 --- the "portcfgfillword" command was modified to allow a setting of one of the following:

MODE:
0 | -idle-idle Sets IDLE mode in the Link Init and IDLE as the fill word (default).
1 | -arbff-arbff Sets ARB(ff) in the Link Init and ARB(ff) as the fill word.
2 | -idlef-arbff Sets IDLE mode in the Link Init and ARB(ff) as the fill word.
3 | -aa-then-ia Attempts hardware arbff-arbff (mode 1) first. If the attempt fails to go into active state, this command executes software idle-arb (mode 2).

Mode 3 is the preferable to modes 1 and 2 as it captures more cases.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms