Table of Contents
Advertisement
Creating IVZs and IVZSs
Zones versus IVZs
Table 16-1
Table 16-1
IVZs
IVZ membership is specified using the VSAN and
pWWN combination.
Default zone policy is always deny (not
configurable).
Automatic IVZ Creation
Figure 16-1
they must be in the same zone in VSAN 1, as well as in VSAN 2. If they are not in the same zone, then
the hard-zoning ACL entries will prohibit pwwn1 from communicating with pwwn2.
Figure 16-1
VSAN1, pwwn1
VSAN2, pwwn2
VSAN2, pwwn3
VSAN3, pwwn4
IVR zone name:
OLTP_Backup
A zone corresponding to each active IVZ is automatically created in each edge VSAN specified in the
active IVZ. All pWWNs in the IVZ are members of these zones in each VSAN.
The zones are created automatically by the IVR process when an IVZS is activated. They are not stored
in a full zone set database and are lost when the switch reboots or when a new zone set is activated. The
IVR feature monitors these events and adds the zones corresponding to the active IVZS configuration
when a new zone set is activated. Like zone sets, IVR zone sets are also activated non-disruptively.
If pwwn1 and pwwn2 are in an IVZ in the current as well as the new IVZS then activation of the new
IVZS does not cause any traffic disruption between them.
Cisco MDS 9000 Fabric Manager Switch Configuration Guide
16-8
identifies the key differences between IVZs and Zones.
Key Differences between IVZs and Zones
depicts an IVZ consisting of four members. To allow pwwn1 to communicate with pwwn2,
IVZ
Active zone in VSAN 1:
Active IVZ
Active zone in VSAN 3:
Zones
Zone membership is specified using pWWN,
fabric WWN, sWWN, or the fabric ID.
Default zone policy is deny (configurable).
pwwn1
pwwn2
pwwn3
pwwn4
Zone name:
IVRZ_OLTP_Backup
pwwn1
pwwn2
pwwn3
pwwn4
Chapter 16
Configuring Inter-VSAN Routing
Active zone in VSAN 2:
pwwn1
pwwn2
pwwn3
pwwn4
OL-7753-01
Advertisement
Chapters
Table of Contents
Troubleshooting
