Brocade Fabric OS Message Reference guide v6.2.0 (53-1001157-01, April 2009)

118 Fabric OS Message Reference
53-1001157-01
EM-1058
17
Probable Cause Indicates the blade is being automatically reset because of known resetable transient errors such
as an application-specific integrated circuit (ASIC) parity error.
Recommended
Action
No action is required if the switch does not reach the reset threshold for the switch or blade. If the
reset threshold is reached on the switch or blade, the switch or blade will be faulted and should be
replaced.
Severity WARNING
EM-1058
Message <timestamp>, [EM-1058], <sequence-number>,, WARNING, <system-name>, Switch gets
reset:
<Fault reason>
Probable Cause Indicates the switch is being automatically reset because of a known resetable transient problem
such as an application-specific integrated circuit (ASIC) parity error.
Recommended
Action
No action is required if the switch does not reach the reset threshold for the switch or blade. If the
reset threshold is reached on the switch or blade, the switch or blade will be faulted and should be
replaced.
Severity WARNING
EM-1059
Message <timestamp>, [EM-1059], <sequence-number>, FFDC, CRITICAL, <system-name>, <Slot
number or Switch> with id <FRU Id> cannot be found in the fru description xml
file.
Probable Cause Indicates that a a blade inserted in the specified slot or the switch (for nonbladed switches) is not
compatible with the switch configuration software. The system may not be usable.
Recommended
Action
Replace the blade. Make sure the replacement is compatible with your switch type.
Severity CRITICAL
EM-1060
Message <timestamp>, [EM-1060], <sequence-number>,, WARNING, <system-name>, Stopping
synchronization of the system due to blade incompatibility with software version
on standby CP.
Probable Cause Indicates a blade in the system is not supported by the release on the standby control processor
(CP).
Recommended
Action
Remove all blades of this type or upgrade your standby CP. Once an appropriate action is taken,
this CP must be rebooted or haSyncStart must be run successfully. Until this is done, the system
will remain out of synchronization.