Brocade Error Message Reference Guide v6.1.0 (53-1000600-02, June 2008)

Fabric OS Message Reference 471
53-1000600-02
ZONE-1027
80
ZONE-1027
Message <timestamp>, [ZONE-1027], <sequence-number>,, INFO, <system-name>, Zoning
transaction aborted <error reason>. <AD Id>.
Probable Cause Indicates that the zoning transaction was aborted due to a variety of potential errors. The error
reason variable can be one of the following:
Zone Merge Received: The fabric is in the process of merging two zone databases.
Zone Config update Received: The fabric is in the process of updating the zone database.
Bad Zone Config: The new config is not viable.
Zoning Operation failed: A zoning operation failed.
Shell exited: The command shell has exited.
Unknown: An error was received for an unknown reason.
User Command: A user aborted the current zoning transaction.
Switch Shutting Down: The switch is currently shutting down.
Recommended
Action
Many of the causes of this error message are transitory: for example because two admins are
working with the zoning database concurrently. If you receive this error, wait a few minutes and try
again. Verify that no one else is currently modifying the zone database.
Severity INFO
ZONE-1028
Message <timestamp>, [ZONE-1028], <sequence-number>,, WARNING, <system-name>, Commit zone
DB larger than supported - <zone db size> greater than <max zone db size>.
Probable Cause Indicates that the zone database size is greater than the limit allowed by the fabric. The limit of the
zone database size depends on the lowest level switch in the fabric. Older switches have less
memory and force a smaller zone database for the entire fabric.
Recommended
Action
Edit the zone database to keep it within the allowable limit for the specific switches in your fabric.
Refer to the Fabric OS Administrator’s Guide for information on the zone database sizes supported
for each switch.
Severity WARNING
ZONE-1029
Message <timestamp>, [ZONE-1029], <sequence-number>,, WARNING, <system-name>, Restoring
zone cfg from flash failed - bad config saved to <config file name> [<return
code>].
Probable Cause Indicates that the zone configuration restored from the flash was faulty.
Recommended
Action
This error will save the faulty zone configuration in the zoned core file directory.