HP Surestore 6164 - Switch User manual

user’s guide
version 2.2
Zoning
www.hp.com

Notice
© Hewlett-Packard Company, 2001. All rights reserved.
Edition: E0801
Hewlett-Packard Company makes no warranty of any
kind with regard to this material, including, but not
limited to, the implied warranties of merchantability and
fitness for a particular purpose. Hewlett-Packard shall not
be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing,
performance, or use of this material.
This document contains proprietary information, which is
protected by copyright. No part of this document may be
photocopied, reproduced, or translated into another
language without the prior written consent of
Hewlett-Packard. The information contained in this
document is subject to change without notice.
Use, duplication, or disclosure by government is subject
to restrictions as set forth in subdivision (c) (1) (ii) of the
Rights in Technical Data and Computer Software Clause
at DFARS 252.227.7013.
Warranty
If you have any questions about the warranty for this
product, contact your dealer or local Hewlett-Packard
sales representative.
Trademarks
Brocade, SilkWorm, Brocade Extended Fabrics, Brocade
Fabric Manager, Brocade Fabric OS, Brocade Fabric
Watch, Brocade QuickLoop, Brocade Remote Switch,
Brocade Web Tools, and Brocade Zoning are trademarks
or registered trademarks of Brocade Communications
Systems, Inc. in the United States and/or in other
countries.
All other brands, product or service names are or may be
trademarks or service marks of, and are used to identify
products of services of their respective owners.
Brocade Extended Fabrics, Brocade Fabric Manager,
Brocade Fabric OS, Brocade Fabric Watch, Brocade
QuickLoop, Brocade Remote Switch, Brocade Web Tools,
and Brocade Zoning are hereafter referred to as Extended
Fabrics, Fabric Manager, Fabric OS, Fabric Watch,
QuickLoop, Remote Switch, Web Tools, and Zoning
respectively.
Safety notices
Any servicing, adjustment,maintenance, or repair must be
performed only by authorized service-trained personnel.
Format conventions
variable Indicates that you must supply a value.
output Denotes text displayed on the screen.
[ ] Indicates that the enclosed element is
optional and may be left out.
{ } Indicates that you must specify one of the
listed options.
| Separates alternatives.
. . . Indicates a repetition of the preceding
parameter.
Tip Denotes ideas for enhanced product usage.
Note Denotes significant concepts or operating
instructions.
CAUTION Denotes a hazard that can cause hardware or
software damage.
WARNING Denotes a hazard that can cause personal
injury or death.
2

3
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Getting Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1Introducing Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Implementing Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2Using Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Understanding Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Zone Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Zone Enforcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Enabling a Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Implementing Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuring Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Modifying Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Adding a Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Merging Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
CONTENTS

4 Zoning User’s Guide
3Using QuickLoop Zones . . . . . . . . . . . . . . . . . . . . . . . . . . 25
QuickLoop Zoning Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
QuickLoop Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring QuickLoop Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
AZoning Telnet Commands . . . . . . . . . . . . . . . . . . . . . . . . 29
aliAdd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
aliCreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
aliDelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
aliRemove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
aliShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
cfgAdd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
cfgClear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
cfgCreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
cfgDelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
cfgDisable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
cfgEnable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
cfgRemove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
cfgSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
cfgShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
qloopAdd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
qloopCreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
qloopDelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
qloopRemove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
qloopShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
zoneAdd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
zoneCreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
zoneDelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
zoneRemove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
zoneShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
BZoning Sample Configurations . . . . . . . . . . . . . . . . . . . . 59
Setting Up a Fabric Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 60
Adding a QuickLoop and QuickLoop Zone to Zone Configuration . . . 70
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

5
Revision History
July 2001 First release.

6 Zoning User’s Guide

7
PREFACE
About this Guide
This guide provides information and instructions for using the Zoning
feature that is available with the HP Surestore FC Switch 6164 (FC 6164)
switches. Zoning is supported by Fabric OS a2.4.1.
The information in this guide is organized as follows:
Chapter 1
Introducing Zoning An overview of Zoning.
Chapter 2
Using Zoning Information about using and managing Zoning.
Chapter 3
Using QuickLoop Zones Information about using Zoning with QuickLoop.
Appendix A
Zoning Telnet Commands Zoning Telnet commands.
Appendix B
Zoning Sample
Configurations
Zoning sample configurations.
Glossary Definitions for commonly used terms.

8 Zoning User’s Guide
Related Publications
Related product information can be found in the following publications.
Those publications with part numbers are provided as printed copies with
your product. The HP Surestore FC Switch 6164 Documentation CD
contains all publications listed in the table below and is also provided with
your product..
For information about Fibre Channel standards, visit the Fibre Channel
Association web site, located at
http://www.fibrechannel.com.
Getting Help
For support information, visit the HP web site located at:
http://www.hp.com
Title Part Number
HP Surestore FC Switch 6164 Documentation
CD A7326-11011
HP Surestore FC Switch 6164 Installation and
Reference Guide A7326-90902
HP Surestore FC Switch 6164 Quick Start Guide A7326-90901
Distributed Fabrics User’s Guide, version 2.2 Available only on CD
Fabric OS Reference Manual, version 2.4 Available only on CD
Fabric Watch User’s Guide, version 2.2 Available only on CD
MIB Reference Manual, version 2.3 Available only on CD
QuickLoop User’s Guide, version 2.3 Available only on CD
Web Tools User’s Guide, version 2.3 Available only on CD

Preface 9
Getting Software Updates
Firmware and software updates are found on the HP web site at:
http://www.hp.com
New switch firmware can be installed from the following host operating
systems:
• UNIX
• Windows NT
• Windows 2000
• Windows 98
• Windows 95

10 Zoning User’s Guide

11
1
INTRODUCING ZONING
Zoning allows you to partition your Storage Area Network (SAN) into
logical groupings of devices that can access each other. Using Zoning, you
can arrange fabric-connected devices into logical groups, or zones, over the
physical configuration of 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. Therefore, you can use zones to:
•Administer security
Use zones to provide controlled access to fabric segments and to
establish barriers between operating environments. For example, isolate
systems with different uses or protect systems in a heterogeneous
environment.
•Customize environments
Use zones to create logical subsets of the fabric to accommodate closed
user groups or to create functional areas within the fabric. For example,
include selected devices within a zone for the exclusive use of zone
members, or create separate test or maintenance areas within the fabric.

12 Zoning User’s Guide
•Optimize IT resources
Use zones to consolidate equipment, logically, for IT efficiency, or to
facilitate time-sensitive functions. For example, create a temporary zone
to back up non-member devices.
Figure 1 illustrates three zones with some overlap. It also contains devices
that are not assigned to a zone, and are thus not active in the fabric if
Zoning is enabled.
Figure 1. Fabric with Three Zones
No zone

Introducing Zoning 13
Implementing Zoning
Implementing Zoning simplifies the zoning process in several ways:
•Zoning can be administered from any switch in the fabric.
Changes configured to one switch automatically replicate to all switches
in the fabric; if a new switch is added to an existing fabric, all zone
characteristics are automatically applied to the new switch. Because
each switch stores zoning information, Zoning ensures a high level of
reliability and redundancy.
•Zones can be configured dynamically.
Configuring new zones does not interrupt traffic on unaffected ports or
devices. Further these zones do not affect data traffic across interswitch
links (ISLs) in cascaded switch configurations.
•Zoning uses policy-based administration.
Because Zoning uses policy-based administration, separating zone
specification from zone enforcement, you can manage multiple zone
configurations and easily enable a specific configuration when it is
required. A fabric can store any number of zone configurations;
however, only one configuration is active at a time. But, because the
configurations are predetermined and stored, a new configuration can be
easily enabled.
•Zoning can be configured and administered using Telnet commands or
the optional Web Tools.
For information on Telnet commands, see the Fabric OS Reference
Manual. For information on Web Tools, see the Web Tools User’s
Guide.

14 Zoning User’s Guide

15
2
USING ZONING
This chapter explains both the concept of zoning and how to use Zoning to
partition a fabric into logical groupings of devices.
Understanding Zoning
A zone is a group of fabric-connected devices arranged into a specified
grouping. Any device connected to a fabric can be included in one or more
zones. Devices within a zone possess an awareness of other devices within
the same zone; they are not aware of devices outside of their zone.
Therefore, if zoning is enabled, any device not in a zone cannot
communicate with any other device.
Zone members (ports, WWNs, or aliases) are grouped into a zone; in turn,
zones are grouped in a zone configuration (a collection of zones). Zones
can overlap; that is, a device can belong to more than one zone, and a fabric
can consist of multiple zones. A zone configuration can include both hard
and soft zones and there can be any number of zone configurations resident
on a switch; however only one configuration can be active, that is enabled,
at a time. Because the number of zones allowable is limited only by
memory usage, the maximum number is virtually limitless.

16 Zoning User’s Guide
Zone Types
Zones can be hard (hardware enforced) or soft (advisory). In a hard zone,
sometimes referred to as a port zone, zone members are specified by
physical port number. In a soft zone, at least one zone member is specified
logically by worldwide name (WWN).
Hard Zones
In a hard zone, all zone members are specified as switch ports; any number
of ports in the fabric can be configured to the zone. When a zone member is
specified by port number, only the individual device port specified is
included in the zone.
Hard zones are position-dependent, that is, a device is identified by the
physical port to which it is connected. Switch hardware ensures that there is
no data transfer between unauthorized zone members. However, devices
can transfer data between ports within the same zone. Consequently, hard
zoning provides the greatest security possible; you can use it where security
must be rigidly enforced.
Soft Zones
In a soft zone, at least one zone member is specified by WWN. A device is
included in a zone if either the node WWN or port WWN specified matches
an entry in the name server table.
When a device logs in, it queries the name server for devices within the
fabric. If zoning is in effect, only the devices in the same zone (or zones)
are returned. Other devices are hidden from the name server query reply.
When a WWN is specified, all ports on the specified device are included in
the zone.
Soft zones are name server-dependent and therefore provide more
flexibility - new devices can be attached without regard to physical
location. However, the switch does not control data transfer, so there is no
guarantee against data transfer from unauthorized zone members. You can
use soft zoning where flexibility is important and security can be ensured
by the cooperating hosts.
In addition to hard and soft zones, a third type of zone is available.

Using Zoning 17
Broadcast Zone
Only one broadcast zone can exist within a fabric. This zone is named
“broadcast”and is used to specify those nodes that are to receive broadcast
traffic.
This type of zone is hardware enforced; the switch controls data transfer to
a port.
Zone Enforcement
When zoning is disabled, the fabric is in a nonzoning state and devices can
communicate without regard to zone restrictions. When zoning is enabled,
zoning is enforced throughout the fabric and devices can communicate only
within their zones.
A switch can maintain any number of zone configurations; however, only
one zone configuration can be enabled, or enforced, at a time. Because
multiple configurations reside in the switch, you can switch from one
configuration to another as events dictate. For example, you can set up a
pre-specified zone configuration to be enabled at certain times of the day;
or, in the event of a disaster, you can quickly enable a defined configuration
to implement your disaster policy.
Zone configurations can be defined, enabled, or saved.
Defined
This is the complete set of all zone objects that have been defined in the
fabric. When zone objects are defined, the information initially resides on
RAM; this must be saved to ensure that it is saved to Flash memory, and is
not lost during power down or when a new zone configuration is enabled.
Changes replicate to all switches in the fabric whenever the zone
information is changed. However, changes must be saved to Flash memory
to be committed to persistent store (that is, to remain across reboot).

18 Zoning User’s Guide
Enabled
This is the zone configuration that is enabled (active). This configuration
resides on RAM and must be saved to ensure that it is not lost when a new
configuration is enabled or during power down. Any changes replicate to
all switches in the fabric when the configuration is enabled or saved.
Saved
This is the zone configuration that was last saved. This configuration
resides in Flash memory and is persistent.
In Figure 2, Config5 is defined (created). When this configuration is
defined, it resides only in RAM. To transfer it to Flash memory, to be
permanently stored and accessible across reboots, it must be saved. This
can be accomplished in one of two ways:
•Save the configuration directly to Flash (the recommended method).
•Enable the configuration first, then save it to Flash.
But, until the configuration has been saved to Flash, it is not permanently
stored and available across reboots.
Note Only the enabled configuration (in the shaded area) is enforced.

Using Zoning 19
Enabling a Zone Configuration
When a zone configuration is enabled, all zones within the configuration
are enabled. All devices within an enabled zone are visible to each other;
however, they cannot communicate outside their zone. Zones can overlap
within a zone configuration.
When a zone configuration is enabled, the following sequence occurs:
1. All aliases are expanded.
2. Inconsistencies are checked.
If any inconsistencies are discovered, an error occurs and the previous
state of the fabric is preserved. (For example, if zoning was disabled, it
remains disabled; if an existing configuration was enabled, it remains
enabled.)
Figure 2. Saving a Zone Configuration
Config1
Config2
Config3
Config4
Config5 (new)
Config1 Config1
Config2
Config3
Config4
Save directly to Flash
Enable . . .then save to Flash
Defined Enabled Saved
Enforced

20 Zoning User’s Guide
3. Switch hardware is loaded with the zoning information.
4. Zone members are loaded.
5. Registered state change notifications (RSCNs) are generated.
Implementing Zoning
Zoning can be implemented and administered from any switch in the fabric.
Changes made to one switch are automatically distributed to all switches in
the fabric.
Zoning can be administered in one of two ways:
•Through the Telnet command interface - see Appendix A, “Zoning
Telnet Commands”.
•Through the Web Tools web interface - see the Web Tools User’s Guide.
Configuring Zoning
Zoning is implemented by the following steps:
1. (Optional) Create an alias.
2. Define the zone.
3. Define the zone configuration.
4. Enable the zone configuration.
Each zone object defined (alias, zone, and zone configuration) must have a
unique name; that is, an alias cannot have the same name as another alias,
and it cannot have the same name as a zone or a zone configuration.
Note During the following configuration process, changes should be saved
periodically to ensure that they are stored in flash memory and protected
against loss due to power outage, etc.