Brocade Communications Systems 8 Reference page 596

90
SEC-1082
Probable Cause Indicates the device connection control (DCC) policy name given in the secPolicyCreate command
was the same as another DCC policy.
Recommended Make sure that the DCC policy name has a unique alphanumeric string, and run the
Action secPolicyCreate command again.
Severity ERROR
SEC-1082
Message
<timestamp>, [SEC-1082], <sequence-number>,, ERROR, <system-name>, Failed to
create
Probable Cause Indicates the security policy was not created due to faulty input or low resources.
Recommended Use proper syntax when creating policies. If the security database is too large, you must delete
Action other members within the database before adding new members to a policy.
Severity ERROR
SEC-1083
Message
<timestamp>, [SEC-1083], <sequence-number>,, ERROR, <system-name>, Name already
exists.
Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only
occur when the primary fabric configuration 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 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 specific switch.
Severity ERROR
SEC-1084
Message
<timestamp>, [SEC-1084], <sequence-number>,, ERROR, <system-name>, Name exists
for different type <Policy name>.
Probable Cause Indicates the specified policy already exists.
Recommended No action is required.
Action
Severity ERROR
520
<policy name>
policy.
Fabric OS Message Reference
53-1001767-01