Brocade Communications Systems 8 Reference page 608

90
SEC-1135
SEC-1135
Message
<timestamp>, [SEC-1135], <sequence-number>,, INFO, <system-name>, Secure fabric
version stamp has been reset.
Probable Cause Indicates the version stamp of the secure fabric is reset.
Recommended Verify the security event was planned. If the security event was planned, no action is required. If the
Action security event was not planned, take appropriate action as defined by your enterprise security
policy.
Severity INFO
SEC-1136
Message
<timestamp>, [SEC-1136], <sequence-number>,, ERROR, <system-name>, Failed to
verify signature <data type, MUA, policy, etc.,>.
Probable Cause Indicates the receiving switch fails to validate the security database sent from the primary fabric
configuration server (FCS) switch. This message usually indicates that the data package is
corrupted, the time stamp on the package is out of range as a result of a replay attack or
out-of-sync time service, or the signature verification failed. Signature verification failure indicates
either an internal error (such as losing the primary public key) or an invalid database.
Recommended Run the secFabricShow command to verify that the fabric is still consistent. All the switches should
Action be in the ready state. If a switch is in the error state, the database might not be correctly updated
for that switch. This message might also be the result of an internal corruption or a hacker attack to
the secure fabric.
Severity ERROR
SEC-1137
Message
<timestamp>, [SEC-1137], <sequence-number>,, ERROR, <system-name>, No signature
<data type, MUA, policy, etc.,>
in
Probable Cause Indicates the receiving switch fails to validate the security database sent from the primary fabric
configurations server (FCS) switch. This message usually indicates that the data package is
corrupted, the time stamp on the package is out of range as a result of a replay attack or
out-of-sync time service, or the signature verification failed. Signature verification failure indicates
either an internal error (such as losing the primary public key) or an invalid database.
Recommended Run the secFabricShow command to verify that the fabric is still consistent. All the switches should
Action be in the ready state. If a switch is in the error state, the database might not be correctly updated
for that switch. This message might also be the result of an internal corruption or a hacker attack to
the secure fabric.
Severity ERROR
532
.
Fabric OS Message Reference
53-1001767-01