Cisco DS-C9216I-K9, Руководство по настройке

Страница: 132 / 436

11-4
Cisco MDS 9000 Fabric Manager Switch Configuration Guide
OL-7753-01
Chapter 11 Configuring and Managing VSANs
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.
Table 11-1 lists the
differences between VSANs and zones.
Figure 11-3 shows the possible relationships between VSANs and zones. In VSAN 2, three zones are
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.
Table 11-1 VSAN and Zone Comparison
VSANs Zones
VSANs equal SANs with routing, naming, and
zoning protocols. These 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 may 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.