Zoning Concepts and Guidelines
58
Zoning Version 3.1.x/4.1.x User Guide
Fabric-Based Zoning Philosophies
This is perhaps the most controversial aspect of zoning. There are a number of
philosophies for the implementation of fabric zoning. All will work in most cases.
However, there are pros and cons to each form. The primary forms are no fabric
zoning, single HBA, grouping by operating system, grouping by application, and
port allocation.
No Fabric Zoning
This is the least desirable zoning option because of the unrestricted access that
devices have on the fabric. All devices have full knowledge of the fabric
membership and potentially have access to all the devices. Additionally, any
device attached to the fabric, intentionally or maliciously, will likewise have
unrestricted access to the fabric. This form of zoning should only be utilized in a
small and tightly controlled environment, such as when host-based zoning or LUN
masking is deployed.
Zoning by Application
In most environments, the concern for availability is by application, not by server,
such as in clusters. This method will most likely require zoning multiple operating
systems into the same zones. Some operating systems have issues co-existing in
the same zone with other operating systems. This method of zoning creates the
possibility that a minor server in the application suite potentially has the ability to
disrupt a major server, such as a web server being able to disrupt a data warehouse
server. Zoning by this method may also result in a zone with a large number of
members that would provide a greater opportunity for administrative errors to
occur, such as RSCNs going out to a larger group than might be necessary.
Zoning by Operating System
The issues here are much the same as zoning by application. In a large site, this
zone may become very large and complex. When zone changes are made they
typically don't involve a particular server type, but are more concerned with
applications. Situations have been encountered with operating system clusters. For
example, if members of different clusters can see storage assigned to another
cluster, they may attempt to own the other cluster's storage and compromise the
stability of the clusters.
Summary of Contents for A7340A - Surestore FC 1Gb/2Gb Switch 16B
Page 12: ...About this Guide 12 Zoning Version 3 1 x 4 1 x User Guide ...
Page 18: ...Introducing Zoning 18 Zoning Version 3 1 x 4 1 x User Guide ...
Page 68: ...Zoning Concepts and Guidelines 68 Zoning Version 3 1 x 4 1 x User Guide ...
Page 70: ...Using Zoning to Administer Security 70 Zoning Version 3 1 x 4 1 x User Guide ...
