Rule 1: Type of Zoning (Hard zoning, Soft zoning, Hardware Enforced, Soft Porting) – Most of the organize will put the priority on security. Hence the hard zone-base architecture is one of the best solutions.

Rule 2:  The Aliases – In SAN fabric, Aliases is optional with zoning. The good thing about aliases feature is: Aliases will force the structure when defining the zones. Aliases will also aid future administrators of the zoned fabric. Structure is the word that comes to mind here.

Rule 3:  The host needs an extra level of security that Secure Fabric OS provides? – In Brocade Fibre Channel switch  ( FC-SW) , you can enable the secure Fabric OS into the Zone Architecture if extra security is required.

Rule 4: Interoperability Fabric – if the users need to include third-party Fibre Channel  ( FC ) switch product, as simple, the storage administrator just need to do the WWN zoning, and doesn’t required Quickloop and etc.


Rule 5: From where will the fabric be managed? – If a Brocade DS4900 is part of the fabric, then the user should use it to administer zoning within the Fabric.

Rule 6: Testing a (new) zone configuration. – Before implementing a zone the Storage administrator should run the Zone Analyzer and isolate any possible problems. This is best practice as it can help to prevent of the fabrics increase in size.

Rule 7: Is the fabric going to have QLFA or QL in it? – If the user is running Brocade Fabric OS v4.0 or lower, then there are a couple things to consider before creating and setting up QLFA zones:

QuickLoop Fabric Assist
Brocade Fabric OS v4.0 cannot have a Fabric Assist host directly connected to it.
However, in Brocade Fabric OS v4.0, it still allows the fabric assist host that connected to a non v4.0 fibre channel switch.
QuickLoop Zoning
Brocade Fabric OS v4.0 can still manage (create, remove, update) QL zones on any non-v4.0 switch. However, QL/QL zones cannot run on switches running Brocade Fabric OS v4.0.

Rule 8: Note, storage administrator should always ensure there is no one is issuing I/O in the zone that going to enable or making the fabric configuration. Prep work needed before enabling/changing a zone configuration.  Storage administrator should always allocate the “maintenance timeframe” for those zoning activity. For example, after the office hour, the network or Data I/O will become in idle mode. This is the best timing to perform the storage administration task. Failing to do so will cause the serious impact within the fabric like databases breaking, node panics etc. This goes the same for disk(s) that are mounted. If the user changes a zone, and a node is mounting the storage in question, it may “vanish” due to the zone change. This may cause the application down or panic.

Rule 9: Potential post work requirements after enabling/changing a zone configuration. – After enabling a zone configuration, the Storage administrator should always verify that nodes and storage are able to see and access one another. Depending on the platform, the Storage administrator may need to reboot the Host in the fabric in order to take the system effect and presence the new changes to the zone.

Rule 10: LUN masking in general – For the LUN Masking, storage administrator must ensure that the conjunction with fabric zoning for maximum effectiveness.