Brocade Fabric OS Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 426)

mapped, the port mapping (including static and preferred port mapping) must be removed before
the D_Port can be used. (Refer to
Saving port mappings on an Access Gateway on page 429.)
• Access Gateway supports D_Port dynamic mode. If the port on the connected HBA is configured as
a D_Port, the Access Gateway port automatically changes to D_Port mode. Once the Access
Gateway port becomes a D_Port, the tests are run automatically, and then whenever the HBA or
the switch port becomes a normal port through static configuration, the Access Gateway port also
switches to normal F_Port mode. However, the Access Gateway-Access Gateway and Access
Gateway-switch port connections require static configuration to become D_Ports.
• On 8-Gbps LWL and ELWL SFP transceivers, only link traffic can be run. Electrical and optical
loopback tests are not available on 8 Gbps SFP transceivers.
• On 8-Gbps LWL and ELWL SFP transceivers, if the cable length is less than or equal to 100
meters, the length is displayed as “unknown”. If the cable length is greater than 100 meters, the
length is displayed accurately.
• On 8-Gbps LWL and ELWL SFP transceivers, D_Port functionality is not supported if a Brocade
HBA is on the other end of the link.
• If a pre-Fabric OS 7.3.0 static D_port is connected to a Fabric OS 7.3.0 port which is not a D_Port
and dynamic D_Port is not enabled, credit loss may happen on Non D_Port interfacing D_Port.
• On-demand D_Port test should not be run on the links having DWDM. If you run, D-Port test may
get stuck during progress. If DWDM is present, configure static D_Port with --dwdm option.
• When you run D_Port test on the links between a FC16-64 port blade and another pizzabox or
blade, run the test on one link at time for short distance links. If you have 100 km long distance
links, start the test on other links only after the test is completed in the 100 km link. However, you
can run the test on a maximum of eight links at a time. If you run on more than eight links
simultaneously, false alarms may be raised. Due to these limitations, blade insert or slot power on
does not trigger on-demand D_Port on FC16-64 port blades.
Also refer to Limitations and considerations for D_Port with HBAs on page 433.
Supported topologies
The following supported topologies illustrate at a high level how D_Port functionality can be used:
• Topology 1: ISLs on page 426
• Topology 2: ICLs on page 427
• Topology 3: Access Gateways on page 428
• Topology 4: HBA to switch on page 429
Topology 1: ISLs
The following figure illustrates inter-switch links (ISLs) that connect multiple switches through a pair of
chassis. The letter E represents E_Ports to be configured as D_Ports.
Supported topologies
426 Fabric OS Administrators Guide
53-1003130-01