Brocade Fabric OS Command Reference Manual Supporting Fabric OS v6.3.0 (53-1001337-01, July 2009)

924 Fabric OS Command Reference
53-1001337-01
zone
2
3. Creating and managing RD Zones:
--rdcreate Creates a RD Zone for the specified members. The following operands are
required:
host_wwn Specifies the port world wide name of the host.
target_wwn Specifies the port world wide name of the target.
vi_wwn Specifies the port world wide name of the virtual initiator (VI).
vt_wwn Specifies the port world wide name of the virtual target (VT).
policy restartable | nonrestartable
Specifies the policy as either restartable or nonrestartable. A restartable
policy causes traffic flow to revert to the physical host and target
configuration in the event the virtual device should fail. When the policy is
specified as nonrestricted and one of the virtual devices goes offline, the
physical devices are considered offline and no traffic is allowed between the
original host and target.
FCR | noFCR
Indicates whether or not this RD zone should function across a Fibre Channel
router (FCR). Specify FCR to support FCR. Specify noFCR if you do not wish to
support FCR.
--rddelete name Deletes the RD Zone specified by name. RD Zones are unique in that the
zone name is not user-defined. It is derived based on members and the
specified configuration. Use cdfgShow to display currently implemented RD
zone by name.
Examples 1. Specific zone operation commands:
The following example shows a scenario of an invalid configuration. If you attempt to create a zone
z10 with an alias a10, then create a zone with name a10, z10 expects a10 to be an alias and
results in an invalid configuration.
To validate all zones in the currently enforced zone database:
switch:admin>zonecreate z10,a10
switch:admin>zonecreate a10, 1,2
switch:admin> zone --validate
Defined configuration:
zone: a10 1,2*
zone: z10 a10~
Effective configuration:
No Effective configuration: (No Access)
------------------------------------
~ - Invalid configuration
* - Member does not exist
# - Invalid usage of broadcast zone
The reason for not being in the current enforcement table could be one of the following:
• The device is not online.
• The device is online but is not Admin Domain-aware.
• The device is online but it is not part of the current Admin Domain.