Reference Guide

FIGURE 34 Target Driven Zoning example
Limitations and considerations for Target Driven Zoning
The following are the general limitations and considerations for Target Driven Zoning:
∙ A zone configuration must be created and enabled before a principal device adds or activates a Target Driven Peer Zone. If a
zone configuration does not exist or effective zone configuration is disabled, enabling the Target Driven Zoning mode
automatically creates a default zone configuration with the name "tdz___cfg___auto" if the zone database is empty. If any zone
object exists in the defined database, the zone configuration is not automatically created.
∙ The maximum number of devices allowed in a Target Driven Peer Zone, including a principal device is 255.
∙ The Target Driven Zoning configuration mode must be enabled on the F_Port to which the principal device is connected.
∙ Target Driven Peer Zones cannot be created or modified using Brocade Network Advisor (BNA) or the CLI; however, they can
be displayed or deleted using BNA or the CLI.
∙ In Target Driven Peer Zones, devices are identified as WWN devices only.
Target Driven Zoning configuration
Target Driven Zoning can be configured and managed at the port level using the portcfgtdz command.
You must create a zone, add, and enable the zone in the zone database for the Target Driven Zoning. For procedures to create, add, and
enable zones in a zone database, refer to Zone configurations on page 301.
Brocade recommends that all Target Driven Zoning tasks be performed using the zone management interface on the principal device.
Enabling Target Driven Zoning
Use the management interface on the principal device to create and manage Target Driven Zoning.
To create and enable Target Driven Zoning, complete the following steps.
Administering Advanced Zoning
Brocade Fabric OS Administration Guide, 8.0.1
348 53-1004111-02