Brocade® Product Training

Probably Failing Modules
50
Structural test fails:
ramtest failed:
portregtest failed:
centralmemorytest failed:
cmitest failed:
(sram,cmem)retentiontest failed:
camtest failed:
turboramtest failed:
Action
replace MB
replace MB
replace MB
replace MB
replace MB
replace MB
replace MB
Group tests:
systemtest failed:
Action
replace MB
MB: main board
© 2005 Brocade Communications Systems, Incorporated.
Revision CFP261-02-2005
Chapter 8 - 50
Each line in the table shows the probable bad components for each failing test. To use this
table, all of the tests must be run and all of the results recorded in the assessment. The
tests must be run in the above sequence. Certain tests depend on others to pass before they
can be expected to pass. For example, the portloopbacktest requires that all of the
tests prior to it must pass before it can be expected to pass.
The high integration of the switch means that the major components that might possibly
fail are limited to either the Loom ASIC or the main board. In the field, the main board is
replaceable, but not the ASIC.
The “circuit” tests are standalone. The error results directly point to the probably failing
modules. For example if Port N fails portregtest,this directly points to a bad Port N
or a bad CPU. To further isolate, the results of the other ports from the same test are
required. If only Port N failed, then the most probable failure is port N. If all ports failed
similarly, then it points to a common problem - the CPU.
The results of the functional tests may need to be correlated with results of the other
functional tests or/and the bit write/read tests. For example if portloopbacktest,
crossporttest, and spinsilk failed while all other tests passed, that implies that
the (B)loom or main board is bad since they appear as probably failing modules among
the failing three tests.
© 2005 Brocade Communications Systems, Incorporated.
Revision CFP261-02-2005
Chapter 8 - 50