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
SEC-1085
Message
<timestamp>, [SEC-1085], <sequence-number>,, ERROR, <system-name>, Failed to
create <policy name>.
Probable Cause
Indicates that the security policy was not created.
Recommended
Check that the current policy configuration is valid. For example, the RSNMP policy cannot exist
Action
without the WSNMP policy.
Severity
ERROR
SEC-1086
Message
<timestamp>, [SEC-1086], <sequence-number>,, ERROR, <system-name>, The security
database is too large to fit in flash.
Probable Cause
Indicates the security database has more data than the flash can accommodate.
Fabric OS Message Reference
53-1002448-01
94
SEC-1083
597