Vsans Versus Zones - Cisco AJ732A - MDS 9134 Fabric Switch Configuration Manual

Information About VSANs
S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
•
•
•
•
•
Up to 256 VSANs can be configured in a switch. Of these, one is a default VSAN (VSAN 1), and another
is an isolated VSAN (VSAN 4094). User-specified VSAN IDs range from 2 to 4093.

VSANs Versus Zones

Zones are always contained within a VSAN. 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 37-1 VSAN and Zone Comparison
VSAN Characteristic
VSANs equal SANs with routing, naming, and zoning protocols. Routing, naming, and zoning protocols are not available
VSANs limit unicast, multicast, and broadcast traffic.
Membership is typically defined using the VSAN ID to F ports.
An HBA or a storage device can belong only to a single VSAN
(the VSAN associated with the F 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 37-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. Zone A defined in VSAN 2 is different and separate from zone A defined in VSAN 7.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
37-4
Traffic isolation—Traffic is contained within VSAN boundaries and devices reside only in one
VSAN ensuring absolute separation between user groups, if desired.
Scalability—VSANs are overlaid on top of a single physical fabric. The ability to create several
logical VSAN layers increases the scalability of the SAN.
Per VSAN fabric services—Replication of fabric services on a per VSAN basis provides increased
scalability and availability.
Redundancy—Several VSANs created on the same physical SAN ensure redundancy. If one VSAN
fails, redundant protection (to another VSAN in the same physical SAN) is configured using a
backup path between the host and the device.
Ease of configuration—Users can be added, moved, or changed between VSANs without changing
the physical structure of a SAN. Moving a device from one VSAN to another only requires
configuration at the port level, not at a physical level.
shows the possible relationships between VSANs and zones. In VSAN 2, three zones are
Table 37-1 lists the differences between VSANs and zones.
Zone Characteristic
on a per-zone basis.
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.
Chapter 37 Configuring and Managing VSANs
OL-16597-01