Deployment Guide

Administering Zoning
● Zoning overview............................................................................................................ 139
● Zoning configurations ...................................................................................................140
● Zoning management..................................................................................................... 141
● Zone configuration and zoning database management................................................ 151
● Best practices for zoning...............................................................................................158
Zoning overview
This chapter describes zoning and provides the procedures for managing zoning. The Zone Admin
window provides two zoning options on the left pane:
• Basic zones
• Traffic Isolation zones
You can perform basic zoning and Traffic Isolation zones using Web Tools and Web Tools with the
EGM license.
Basic zones
Basic zoning enables you to partition a storage area network (SAN) into logical groups of devices that
can access each other. For example, you can partition a SAN into two zones, winzone and unixzone, so
that the Windows servers and storage do not interact with UNIX servers and storage.
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.
Traffic Isolation zones
A Traffic Isolation zone (TI zone) is a special zone that creates a dedicated path for a specific traffic
flow. TI zones are primarily for shaping and controlling traffic rather than partitioning access to storage.
LSAN zone requirements
An LSAN zone enables device connectivity between fabrics connected in Fibre Channel Routing (FCR)
configurations without forcing you to merge fabrics. Extension switches provide multiple mechanisms to
manage interfabric device connectivity. Zones that contain hosts and targets that are shared between
the two fabrics need to be explicitly coordinated. To share devices between any two fabrics, you must
create an LSAN zone in both fabrics considering the following:
• The name of an LSAN begins with the prefix LSAN_. The prefix is not case-sensitive.
• Members must be identified by their port WWN because port IDs are not necessarily unique across
fabrics.
Web Tools Administrator's Guide
139
53-1003169-01