Lucent Technologies OptiStar EdgeSwitch, Руководство пользователя

Страница: 109 / 330

OptiStar EdgeSwitch Configuration
365-575-925R1.5
Lucent Technologies
4 - 4 7
Issue 1, April 2002
If active Zone Sets are not compatible, the ports connecting the affected switches go into the “Isolated E_Port”
state and the switches no longer communicate with each other.
Examples of a Failed Zone Merge Operations
Active Zone Set (in Flash)
Enforced Zone Set (in Temp. Memory)
After Zone Merge
Switch A Switch B Switch A Switch B
Zone Set “Backup”
•
Zone “UNIX”
Member:
11 22 33 44 55 66 77 88
Zone Set “Backup”
•
Zone “UNIX”
Member:
21 00 00 20 37 C6 E2 95
Zone Set “Backup”
•
Zone “UNIX”
Member:
11 22 33 44 55 66 77 88
Zone Set “Backup”
•
Zone “UNIX”
Member:
21 00 00 20 37 C6 E2 95
In the above example, the Zone Merge is not successful because the Zone Sets are not compatible. Switch A and
Switch B both have a Zone Set named “Backup”, and each Zone Set contains a Zone named “UNIX”. However,
the UNIX Zone defined on Switch A contains the “11 22 33 44 55 66 77 88” Member, whereas the UNIX Zone
defined on Switch B contains the “21 00 00 20 37 C6 E2 95” Member. The result is separate enforced Zone Sets
and no communication between the switches.
Because results from zone merge operations are stored in temporary memory, deletion of a Zone Set from a
switch does not affect current enforcement. However, this deletion may change the results of the next zone
merge operation. Any unique Zones from the deleted Zone Set will be excluded from the resulting merge. If no
“Active” marked Zone Set definitions exist on any switches in the fabric, then zoning will not be in effect.
4.10.1.6 Joining Zoned Fabrics
When a switch connect already-zoned fabrics through Inter-Switch Links (ISLs), or when switches in some other
way become newly aware of ISLs (such as at power-up), the zone merge operation is initiated. (For more on
Zone Merge see the previous section,
Section 4.10.1.5 . Before you join fabrics that have pre-existing Active
Zone Sets, ensure that the fabrics meet the following conditions:
•
All Domain IDs must be unique.
•
Zones cannot conflict. For example, if multiple switches have a Zone named “video,” then the contents
(list of Members within this Zone) must be identical for each switch; otherwise, an isolated E_Port
condition will occur, as indicated by a blinking-green-LED-and-solid-amber-LED combination on the
affected port.
•
The names of the enforced Zone Sets cannot conflict, though contents may differ. For example, one
fabric may have an enforced Zone Set containing three unique Zones; the other fabric may have an
enforced Zone Set containing two unique Zones. As long as these Zone Sets have the same name,
combination of these fabrics will succeed.
After a successful zone merge operation, the resulting enforced Zone Set may contain more Zones than were
originally defined within the Zone Set. The “enforced Zone Set” display is identical on all switches. (To view
the original definition of the Zone Set, go to the switch on which it was defined, then type the following
command from the Root Menu of the CLI, then follow directions:
config zone wwn zoneset show
).
Note:
The
enforced Zone Set is not persistent; it is regenerated every time one or more switches powers up.
To create a permanent copy of the enforced Zone Set, go to one of the switches and configure a Zone Set with
the same name, Zones, and Members. The configured Zone Set is permanently stored in this switch’s flash. If