> # VSANs Versus Zones

> You can define multiple zones in a VSAN. Because two VSANs are equivalent to two unconnected SANs, zone A on VSAN 1 is different and separate from zone A in VSAN 2. Table 20-1 lists the differences between VSANs and zones.

> Table 20-1 VSAN and Zone Comparison
> VSAN Characteristic | Zone Characteristic
> --- | ---
> VSANs equal SANs with routing, naming, and zoning protocols. | Routing, naming, and zoning protocols are not available on a per-zone basis.
> — | Zones are always contained within a VSAN. Zones never span two VSANs.
> VSANs limit unicast, multicast, and broadcast traffic. | Zones limit unicast traffic.
> Membership is typically defined using the VSAN ID to Fx ports. | Membership is typically defined by the pWWN.
> An HBA or a storage device can belong only to a single VSAN—the VSAN associated with the Fx port. | An HBA or storage device can belong to multiple zones.
> VSANs enforce membership at each E port, source port, and destination port. | Zones enforce membership only at the source and destination ports.
> VSANs are defined for larger environments (storage service providers). | Zones are defined for a set of initiators and targets not visible outside the zone.
> VSANs encompass the entire fabric. | Zones are configured at the fabric edge.

> Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.