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

Fabric OS Message Reference 759
53-1002448-01
ZONE-1027
115
ZONE-1027
Message <timestamp>, [ZONE-1027], <sequence-number>,, INFO, <system-name>, Zoning
transaction aborted <error reason>. <AD Id>.
Probable Cause Indicates the zoning transaction was aborted because of one of the following conditions:
• 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 configuration 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.
Most of these error conditions are transitory.
Recommended
Action
Try again after sometime. Verify that only one administrator is modifying with the zone database at
a time.
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
Execute the cfgSize command to view the zone database size information. Edit the zone database
to keep it within the allowable limit for the specific switches in your fabric.
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. This error will save the
faulty zone configuration in the zoned core file directory.