Brocade Fabric OS Message Reference - Supporting Fabric OS v5.3.0 (53-1000437-01, June 2007)

Fabric OS Message Reference 373
53-1000437-01
SEC-1166
63
SEC-1166
Message <timestamp>, [SEC-1166], <sequence-number>,, ERROR, <system-name>, Non FCS tries
to commit failover.
Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can
only occur when the primary fabric configurations server (FCS) is distributing the security database
to the other switches in the fabric and local validation finds that there is an error in the security
database. This is a rare occurrence.
Recommended
Action
Run the secFabricShow command to verify that the fabric is still consistent. All the switches should
be in the ready state. If a switch is in the error state, the database might not be correctly updated
for that specific switch.
Severity ERROR
SEC-1167
Message <timestamp>, [SEC-1167], <sequence-number>,, ERROR, <system-name>, Another FCS
failover is in process. Command terminated.
Probable Cause Indicates that because another failover is already in progress, this failover attempt cannot
proceed.
Recommended
Action
Verify that the security event was planned. If the security event was planned, retry fabric
configurations server (FCS) failover after current failover has completed, if this switch should
become primary FCS. If the security event was not planned, take appropriate action as defined by
your enterprise security policy.
Severity ERROR
SEC-1168
Message <timestamp>, [SEC-1168], <sequence-number>,, ERROR, <system-name>, Primary FCS
failover is busy. Please retry later.
Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can
only occur when the primary fabric configurations server (FCS) is distributing the security database
to the other switches in the fabric and local validation finds that there is an error in the security
database. This is a rare occurrence.
Recommended
Action
Run the secFabricShow command to verify that the fabric is still consistent. All the switches should
be in the ready state. If a switch is in the error state, the database might not be correctly updated
for that specific switch.
Severity ERROR