Zoning overview – Dell POWEREDGE M1000E User Manual
Page 278
238
Fabric OS Administrator’s Guide
53-1001763-02
Zoning overview
11
•
QoS zones
Assign high or low priority to designated traffic flows. QoS zones are normal zones with
additional QoS attributes specified by adding a QOS prefix to the zone name. See
SID/DID traffic prioritization”
on page 403 for more information.
•
Traffic Isolation zones (TI zones)
Isolate inter-switch traffic to a specific, dedicated path through the fabric. See
on page 267 for more information.
Zoning overview
NOTE
The information in this chapter applies to Brocade Native mode only. For information about zoning
in InteropMode 2 or 3, see
Chapter 14, “Interoperability for Merged SANs”
.
Zoning enables you to partition your storage area network (SAN) into logical groups of devices that
can access each other. A device can communicate only with other devices connected to the fabric
within its specified zone. For example, you can partition your SAN into two zones, winzone and
unixzone, so that your Windows servers and storage do not interact with your UNIX servers and
storage. When zoning is enabled, devices that are not included in a zone configuration are
inaccessible to other devices in the fabric.
Zones can be configured dynamically. They can vary in size, depending on the number of
fabric-connected devices, and devices can belong to more than one zone. Because zone members
can access only other members of the same zone, a device not included in a zone is not available
to members of that zone.
When using a mixed fabric—that is, a fabric containing two or more switches running different
release levels of fabric operating systems—you should use the switch with the highest Fabric OS
level to perform zoning tasks.
You can use zones to logically consolidate equipment for efficiency or to facilitate time-sensitive
functions; for example, use zoning to create a temporary zone to back up nonmember devices.
Any zone object connected to the fabric can be included in one or more zones. Zone objects can
communicate only with objects within the same zone. For example, consider
page 239, which shows configured zones, Red, Green, and Blue.
•
Server 1 can communicate only with the Loop 1 devices.
•
Server 2 can communicate only with the RAID and Blue zone devices.
•
Server 3 can communicate with the RAID device and the Loop1 device.
•
The Loop 2 JBODs are not assigned to a zone; no other zoned fabric device can access them.