Fabric OS Message Reference v6.4.0 (53-1001767-01, June 2010)

518 Fabric OS Message Reference
53-1001767-01
SEC-1075
90
Probable Cause Indicates a security command was run on a switch that is not allowed to run it either because it is in
non-secure mode or because it does not have the required fabric configuration server (FCS)
privilege.
Recommended
Action
If a security operation that is not allowed in non-secure mode is attempted, do not perform the
operation in non-secure mode. In secure mode, run the command from a switch that has required
privilege, that is, either a backup FCS or primary FCS.
Severity ERROR
SEC-1075
Message <timestamp>, [SEC-1075], <sequence-number>,, ERROR, <system-name>, Fail to
<operation> new policy set on all switches.
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
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-1076
Message <timestamp>, [SEC-1076], <sequence-number>,, ERROR, <system-name>,
NoNodeWWNZoning option has been changed.
Probable Cause Indicates the NoNodeWWNZoning option has been changed. If the option is turned on, a zone
member can be added using node WWNs, but the member will not be able to communicate with
others nodes in the zone.
Recommended
Action
Re-enable the current zone configuration for the change to take effect.
Severity ERROR
SEC-1077
Message <timestamp>, [SEC-1077], <sequence-number>,, ERROR, <system-name>, Failed to
activate new policy set on all switches.
Probable Cause Indicates the policy could not be activated. Possible reasons that the policy could not be activated
include not enough memory or a busy switch.
Recommended
Action
Run the secFabricShow command to verify that all switches in the fabric are in the ready state.
Retry the command when all switches are ready.