Site Search

Joomla Templates and Joomla Extensions by JoomlaVision.Com

Latest Topics

Joomla Templates and Joomla Extensions by JoomlaVision.Com

[VMAX]VMAX Replication Technoledge - IBM Storage Line Product Counterparts 

[VMAX]VMAX Single Point of Failure - Engine 

[VMAX] Understand VMAX Virtualisation layers 

[VMAX]What is new with VMAX? 

[VMAX] EMC VMAX - Some Key Points about VMAX 

Pre 1 2 3 4 5 Next

You are here: Home SAN/Storage Brocade

[Brocade] SAN Zoning - Zoning Architecture

PDFPrintE-mail

Below are some useful rules of zoning architecture.
1: Type of Zoning (Hard, Soft, Hardware Enforced, Soft Porting) – If security is a priority, then a Hard Zone-based(Hard Port Zoning) architecture coupled with Hardware Enforcement is recommended


2: Use of Aliases – Aliases are optional with zoning. Using aliases should force some structure when defining your zones. Aliases will also aid future administrators of the zoned fabric. Structure is the word that comes to mind here.
3: Does the site need an extra level of security that Secure Fabric OS provides? – Add Secure Fabric OS into the Zone Architecture if extra security is required.
4: Interoperability Fabric – If the fabric includes a Enterprise level switch like SilkWorm 12000 and the user needs to support a third-party switch product, then he will only be able to do WWN zoning, no QuickLoop etc. This is documented in the SilkWorm 12000 documentation.
5: Testing a (new) zone configuration. – Before implementing a zone the user should run the Zone Analyzer and isolate any possible problems. This is especially useful, as fabrics increase in size.
6: Prep work needed before enabling/changing a zone configuration– Before enabling or changing a fabric configuration, the user should verify that no one is issuing I/O in the zone that will change. This can have a 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 nodes to panic, applications to break etc. Changes to the zone should be done during preventative maintenance. Most sites have an allocated time each day to perform maintenance work.
7: Potential post work requirements after enabling/changing a zone configuration– After changing or enabling a zone configuration, the user should confirm that nodes and storage are able to see and access one another. Depending on the platform, the user may need to reboot one or more nodes in the fabric with the new changes to the zone.
8:LUN Masking must be used in conjunction with fabric zoning for maximum effectiveness.

Note: There are some other factors need to considered also, for example, to have QLFA/QL within the fabric, pleaes refer to vender documentation for recommendations.