Creating and managing zone aliases, Creating an alias – HP StorageWorks 2.128 SAN Director Switch User Manual
Page 185
Fabric OS 5.x administrator guide 185
•
QuickLoop: Evaluate whether the fabric will also use QuickLoop Fabric Assist (QLFA) or QuickLoop. If
you are running Fabric OS 4.x, consider the following before creating and setting up QLFA zones:
• QuickLoop Zoning. QuickLoop and QuickLoop zones cannot run on switches running Fabric OS
4.x. However, Fabric OS 4.x can still manage (create, remove, update) QuickLoop zones on any
non-4.x switch.
• QLFA. Fabric OS 4.x cannot have a Fabric Assist host directly connected to it. However, targets on
a Fabric OS 4.x switch can still be part of a Fabric Assist zone if a Fabric Assist host is connected
to a non-4.x switch.
•
Zone changes: Zone changes in a production fabric can cause a disruption of I/O when an RSCN is
generated because of the zone change and the HBA is unable to process the RSCN fast enough.
Although RSCNs are a normal part of a functioning SAN, the pause in I/O might not be acceptable.
For these reasons, perform zone changes only when the resulting behavior is predictable and
acceptable. Changing HBA drivers can rectify the situation.
•
Final verification: After changing or enabling a zone configuration, confirm that the nodes and
storage devices can identify and access one another. Depending on the platform, you might need to
reboot one or more nodes in the fabric with the new changes.
The zone configuration is managed on a fabric basis. Zoning can be implemented and administered from
any switch in the fabric that has an Advanced Zoning license enabled. When a change in the
configuration is saved, enabled, or disabled per the transactional model, it is distributed (by closing the
transaction) to all switches in the fabric, preventing a single point of failure for zone information.
NOTE:
Zoning commands make changes that affect the entire fabric. When executing fabric-level
configuration tasks, allow time for the changes to propagate across the fabric before executing any
subsequent commands. For a large fabric, you might want to wait several minutes between commands.
Creating and managing zone aliases
A zone alias is a logical group of ports, WWNs, or arbitrated loop physical addresses (AL_PAs). You can
simplify the process of creating zones by first specifying aliases, which eliminates the need for long lists of
individual zone-member names.
Note that if you are creating a new alias using
aliCreate w, “1,1”
, and a user in another telnet
session executes
cfgEnable
(or
cfgDisable
or
cfgSave
), the other user’s transaction aborts your
transaction and you receive an error message. Creating a new alias while there is a zone merge taking
place might also abort your transaction. For details about zone merging and zone merge conflicts, see
Creating an alias
1.
Connect to the switch and log in as admin.
2.
Issue the
aliCreate
command.
3.
Issue the
cfgSave
command to save the change to the defined configuration.
For example:
switch:admin> alicreate “array1”, “2,32; 2,33; 2,34; 4,4”
switch:admin> alicreate “array2”, “21:00:00:20:37:0c:66:23; 4,3”
switch:admin> alicreate “loop1”, “4,6”
switch:admin> cfgsave
You are about to save the Defined zoning configuration. This
action will only save the changes on the Defined configuration.
Any changes made on the Effective configuration will not
take effect until it is re-enabled.
Do you want to save Defined zoning configuration only? (yes, y, no, n): [no] y