346 Administering Advanced Zoning
Zone aliases also simplify repetitive entry of zone objects such as port numbers or a WWN. For example,
you can use the name “Eng” as an alias for “10:00:00:80:33:3f:aa:11”.
A useful convention is to name zones for the initiator they contain. For example, if you use the alias
SRV_MAILSERVER_SLT5 to designate a mail server in PCI slot 5, then the alias for the associated zone is
ZNE_MAILSERVER_SLT5. This clearly identifies the server host bus adapter (HBA) associated with the zone.
Zone configuration naming is more flexible. One configuration should be named PROD_
fabricname
,
where
fabricname
is the name that the fabric has been designated. The purpose of the PROD configuration
is to easily identify the configuration that can be implemented and provide the most generic services. If
other configurations are used for specialized purposes, names such as “BACKUP_A,” “RECOVERY_2,” and
“TEST_18jun02” can be used.
Zone configurations
A
zone configuration
is a group of one or more zones. A zone can be included in more than one zone
configuration. When a zone configuration is in effect, all zones that are members of that configuration are
in effect.
The different types of zone configurations are:
•
Defined Configuration.
The complete set of all zone objects defined in the fabric.
•
Effective Configuration.
A single zone configuration that is currently in effect. The effective
configuration is built when an administrator enables a specified zone configuration.
•
Saved Configuration.
A copy of the defined configuration plus the name of the effective
configuration, which is saved in flash memory by the
cfgSave
command. (You can also use the
configUpload
command to provide a backup of the Zoning configuration and the
configDownload
command to restore the Zoning configuration.) There might be differences between
the saved configuration and the defined configuration if the system administrator has modified any of
the zone definitions and has not saved the configuration.
•
Disabled Configuration.
The effective configuration is removed from flash memory.
On power-up, the switch automatically reloads the saved configuration. If a configuration was active when
it was saved, the same configuration is reinstated on the local switch with an autorun of the
cfgEnable
command.
You can establish a zone by identifying zone objects using one or more of the following
Zoning schemes
:
•
Domain, port number level.
All members are specified by
domain ID
,
port number
, or
domain,
area number
pair or aliases, described in ”
Zone aliases
” on page 346.
•
World Wide Name (WWN) level.
All members are specified only by World Wide Name
(WWNs) or aliases of WWNs. They can be node or port versions of the WWN.
•
Mixed Zoning.
A zone containing members specified by a combination of
domain
,
port number
,
and/or
domain, area number
and WWN.
Zoning enforcement
Hardware and Software-enforced Zoning are supported.
Hardware-enforced Zoning
Hardware-enforced Zoning is specified without using the mixed Zoning scheme (mixed zones contain
domains, ports and WWNs as zone members). The exact methodology varies on different switch models.
Hardware-enforced Zoning (also called
hard Zoning
):
•
Prevents a host from accessing a device it is not authorized to access.
•
Checks each frame before it is delivered to a zone member and discards it if there is a zone mismatch.
When hardware-enforced Zoning is active, the switch monitors the communications and blocks any
frames that do not comply with the effective zone configuration. The switch performs this blocking at the
transmit side of the port on which the destination device is located.
•
Is enforced at the ASIC level. Each ASIC maintains a list of source port IDs that have permission to
access any of the ports on that ASIC.
•
Is available on 1 Gbit/sec, 2 Gbit/sec, and 4 Gbit/sec platforms.
Содержание AE370A - Brocade 4Gb SAN Switch 4/12
Страница 1: ...HP StorageWorks Fabric OS 5 2 x administrator guide Part number 5697 0014 Fifth edition May 2009 ...
Страница 18: ...18 ...
Страница 82: ...82 Managing user accounts ...
Страница 102: ...102 Configuring standard security features ...
Страница 126: ...126 Maintaining configurations ...
Страница 198: ...198 Routing traffic ...
Страница 238: ...238 Using the FC FC routing service ...
Страница 260: ...260 Administering FICON fabrics ...
Страница 280: ...280 Working with diagnostic features ...
Страница 332: ...332 Administering Extended Fabrics ...
Страница 414: ...398 Configuring the PID format ...
Страница 420: ...404 Configuring interoperability mode ...
Страница 426: ...410 Understanding legacy password behaviour ...
Страница 442: ...426 ...
Страница 444: ......
Страница 447: ......