Brocade Fabric OS Message Reference - Supporting Fabric OS v7.0.1 (53-1002448-01, March 2012)

Fabric OS Message Reference 579
53-1002448-01
Chapter
94
SEC System Messages
SEC-1001
Message <timestamp>, [SEC-1001], <sequence-number>,, ERROR, <system-name>, RCS process
fails: <reason code>.
Probable Cause Indicates that the reliable commit service (RCS) process failed to complete. RCS is a mechanism
for transferring data from one switch to other switches within the fabric. RCS ensures that either all
or none of the switches commit to the database. RCS can fail if one switch in the fabric is busy or in
an error state that prevents it from accepting the database.
Recommended
Action
The RCS process is invoked when the security database is modified by a security command (for
example, the secPolicySave command, the secPolicyActivate command, or the secVersionReset
command). If the switch is busy, the command might fail the first time. Retry the command.
Run the rcsInfoShow command to view RCS capability on the fabric. RCS must be capable on all
switches in the fabric to be enabled. If all switches are capable, RCS is automatically enabled.
If the message persists, run the supportFtp command (as needed) to set up automatic FTP
transfers; then run the supportSave command and contact your switch service provider.
Severity ERROR
SEC-1002
Message <timestamp>, [SEC-1002], <sequence-number>,, ERROR, <system-name>, Security data
fails: <Reason Text>.
Probable Cause Indicates that the receiving switch fails to validate the security database sent from the primary
fabric configuration server (FCS) switch. This might be caused by several factors: the data package
may be corrupted, the time stamp on the package may be out of range as a result of replay attack
or out-of-sync time service, or the signature verification failed. Signature verification failure may
result from an internal error, such as losing the primary public key or an invalid database.
Recommended
Action
Run the secFabricShow command to verify that the fabric is still consistent. All the switches should
be in Ready state. If a switch is in the error state, the database might not be correctly updated for
that switch. The error might also be a result of an internal corruption or a hacker attack to the
secure fabric. If you have a reason to believe that the error is the result of a possible security
breach, take appropriate action as defined by your enterprise security policy.
Severity ERROR