HP AA979A - StorageWorks SAN Switch 2/8V, Administrator'S Manual, Page: 243 / 465

Fabric OS 5.3.0 administrator guide 245
example, in Figure 11 , when the zones for Edge SAN 1 are defined, you do not need to consider the zones
in Edge SAN 2, and vice versa.
Zones that contain hosts and targets that are shared between the two fabrics need to be explicitly
coordinated. Although an LSAN is managed using the same tools as any other zone on the edge fabric,
two behaviors distinguish an LSAN from a conventional zone:
• A required naming convention. The name of an LSAN begins with the prefix “LSAN_”. The LSAN name
is case-insensitive; for example, lsan_ is equivalent to LSAN_ , Lsan_ , and so on.
• Members must be identified by their port WWN because port IDs are not necessarily unique across
fabrics. The names of the zones need not be explicitly the same, and membership lists of the zones
need not be in the same order.
LSAN zones and fabric-to-fabric communications
Because zoning is enforced by all involved fabrics, any communication from one fabric to another must be
allowed by the zoning setup on both fabrics. If the SANs are under separate administrative control, then
separate administrators maintain access control.
If you are managing other switches in a fabric, it is recommended that you run the
defZone
--
show
command on your Fabric OS v5.1.0 or later switches as a precaution. Default zoning behavior in
Fabric OS v5.1.0 and later operates differently compared to other Fabric OS versions (versions 2.x, 3.x 4.x
and 5.0.1).
For example, if you issue the
defZone
--
noaccess
command on a Fabric OS v5.1.0 or later switch,
then default zoning configurations will be created on each switch in the fabric (v2.x, v3.x, v4.x or v5.0.1
switches). Fabric OS v5.1.0 or later switches do not indicate that a default configuration is enabled when
you use the
cfgShow
or
cfgActvShow
commands. For more information about default zoning, refer to
Administering Advanced Zoning , page 369.
The following example procedure illustrates how LSANs control which devices can communicate with each
another. The example procedure shows the creation of two LSANs (called lsan_zone_fabric75 and
lsan_zone_fabric2 ), which involve the following devices:
• Switch1 and the host in fabric75
• Switch2, Target A, and Target B in fabric2
• Switch1 is connected to the 4/256 SAN Director with a B-Series MP Router blade using an EX_Port or
VEX_Port
• Switch2 is connected to the 4/256 SAN Director with an B-Series MP Router blade using another
EX_Port or VEX_Port.
• Host has WWN 10:00:00:00:c9:2b:c9:0c (connected to switch1)
• Target A has WWN 50:05:07:61:00:5b:62:ed (connected to switch2)
• Target B has WWN 50:05:07:61:00:49:20:b4 (connected to switch2)
The following procedure shows how to control device communication with the LSAN.
To control device communication with the LSAN
1. Log in as
admin
and connect to switch1.
2. Enter the
nsShow
command to list the WWN of the host (10:00:00:00:c9:2b:c9:0c).
NOTE: The
nsShow
output displays both the port WWN and node WWN; the port WWN must
be used for LSANs.
switch:admin> nsshow
{
Type Pid COS PortName NodeName TTL(sec)
N 060f00; 2,3; 10:00:00:00:c9:2b:c9:0c; 20:00:00:00:c9:2b:c9:0c; na
FC4s: FCP
NodeSymb: [35] "Emulex LP9002 FV3.91A3 DV5-5.20A6 "
Fabric Port Name: 20:0f:00:05:1e:37:00:44
Permanent Port Name: 10:00:00:00:c9:2b:c9:0c