McDATA StorageWorks 2/140 - Director Switch Planning Manual page 172

Implementing SAN Internetworking Solutions
4
McDATA Products in a SAN Environment - Planning Manual
4-30
2. Domain_ID assignment - Manually assign unique Domain_IDs
to all Fibre Channel directors, fabric switches, and SAN router
R_Ports. Ensure the Insistent Domain_ID option is enabled at the
SAN management or SANvergence Manager application. Do not
assign Domain_ID 30 or 31 to any fabric elements. These proxy
Domain_IDs are reserved for routing domains within the SAN
router.
3. Allocate Zone_IDs to mSANs - Allocate an exclusive range of
Zone_IDs for use in each mSAN. For example, each mSAN could
be allocated the range 101 to 512 for local use only. These
Zone_IDs are not assigned to zones shared across mSANs.
At the Zone Preferences dialog box (SANvergence Manager
application), leave the Zone_ID range at the default values
(1 to 512) and track the ranges manually. If Zone_ID ranges are
set, a Zone_ID outside the specified range cannot be created.
4. Allocate Zone_IDs to shared zones - Allocate an exclusive range
of Zone_IDs for shared zones. For example, zones shared across
mSANs could be allocated the range 1 to 100. For exported zones
to merge across iFCP connections, the Zone_IDs must match.
In environments where all zones are shared zones, the local and
shared Zone_ID scheme should be altered to provide different
Zone_ID ranges for different mSANs. Develop a scheme where a
point-to-multipoint scenario (connecting one mSAN to multiple
other mSANs) carves out a range of Zone_IDs shared with each
remote site. For example:
From data center to remote site A: Zone_ID Range 1 to 20.
From data center to remote site B: Zone_ID Range 21 to 40.
From data center to remote site C: Zone_ID Range 41 to 60.
5. Assign common zone names - Even though zone names need not
be identical for zones to merge (only Zone_IDs must be identical),
for simplified tracking it is good practice to assign a common
name to zones that are intended to merge.
6. Encode the Zone_ID in the zone name - If a zone intended for
database replication is assigned a Zone_ID of 7, it is good practice
to include the Zone_ID in the zone name (for example
DB_Replication_7). When sharing zones, this practice avoids
repeatedly searching for the assigned Zone_ID.