Vsans Versus Zones - Cisco DS-C9216I-K9 Configuration Manual

VSANs Versus Zones

VSANs Versus Zones

You can define multiple zones in a VSAN. Because two VSANs are equivalent to two nonconnected
SANs, zone A on VSAN 1 is different and separate from zone A in VSAN 2.
differences between VSANs and zones.
Table 11-1
VSANs
VSANs equal SANs with routing, naming, and
zoning protocols.
--
VSANs limit unicast, multicast, and broadcast
traffic.
Membership is typically defined using the VSAN
ID to Fx ports.
An HBA or a storage device may belong only to a
single VSAN--the VSAN associated with the Fx
port.
VSANs enforce membership at each E port, source
port, and destination port.
VSANs are defined for larger environments
(storage service providers).
VSANs encompass the entire fabric.
Figure 11-3
defined: zone A, zone B, and zone C. Zone C overlaps both zone A and zone B as permitted by Fibre
Channel standards. In VSAN 7, two zones are defined: zone A and zone D. No zone crosses the VSAN
boundary--they are completely contained within the VSAN. Zone A defined in VSAN 2 is different and
separate from zone A defined in VSAN 7.
Cisco MDS 9000 Fabric Manager Switch Configuration Guide
11-4
VSAN and Zone Comparison
shows the possible relationships between VSANs and zones. In VSAN 2, three zones are
Chapter 11 Configuring and Managing VSANs
Table 11-1
Zones
These protocols are not available on a per-zone
basis.
Zones are always contained within a VSAN.
Zones never span two VSANs.
Zones limit unicast traffic.
Membership is typically defined by the pWWN.
An HBA or storage device can belong to multiple
zones.
Zones enforce membership only at the source and
destination ports.
Zones are defined for a set of initiators and targets
not visible outside the zone.
Zones are configured at the fabric edge.
lists the
OL-7753-01