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

The combination of front domains and xlate domains allows routing around path failures, including path
failures through the routers. The multiple paths to an xlate domain provide additional bandwidth and
redundancy.
There are some differences in how the xlate domain is presented in the backbone fabric. The backbone
xlate domains are topologically connected to FC routers and participate in FC-FC routing protocol in the
backbone fabric. Front domains are not needed in the backbone fabric. As in the case of an xlate
domain in an edge fabric, backbone fabric xlate domains provide additional bandwidth and redundancy
by being able to present themselves as connected to single or multiple FC routers with each FC router
capable of connecting multiple IFLs to edge fabrics.
Use the fcrXlateConfig command to display or assign a preferred domain ID to a translate domain or,
in some scenarios, to prevent the creation of an unnecessary xlate domain.
Identifying and deleting stale xlate domains
If a remote edge fabric goes unreachable, the xlate domains created in other edge fabrics for this
remote edge fabric are retained and not removed unless there is any disruption in the local edge fabric
or unless you remove them manually.
You can use the fcrXlateConfig command to identify and remove these stale xlate domains without
disrupting the fabric.
1. Connect to the FC router and log in using an account with admin permissions.
2. Enter the fcrXlateConfig --show command to identify any stale xlate domains.
3. Enter the fcrXlateConfig --del command to delete the stale xlate domains.
sw0:root> fcrxlateconfig --show stalexd
Imported FID Stale XD Owner Domain
--------------------------------------------------
012 002 007 ( this FCR )
sw0:root> fcrxlateconfig --del stalexd 12 2
Xlate domain 2 is deleted
FC router authentication
A Brocade FC router (FCR) is capable of forming a secure link across fabrics. The EX_Port-enabled
router exchanges DH-CHAP information with the edge fabric to enable authentication.
Note that while setting secret keys in the edge switch, the front phantom WWN should be used as the
remote switch WWN in the edge fabric. The front phantom domain's WWN is available through the
portCfgExport command of the EX_Port connecting to the edge fabric. The FC router switch should
use the edge switch's WWN to configure the secret keys. Refer to
Secret key pairs for DH-CHAP on
page 227 for more details.
FC-FC routing behaves passively to the authentication requests received from edge fabric switches. An
FC router never initiates authentication on an EX_Port and only responds to the edge fabric requests.
NOTE
Changing the switch authentication policy mode does not affect online EX_Ports, so it is acceptable to
leave the default Passive policy configured on the FC router while the Active or On policy is required on
the edge switch.
Identifying and deleting stale xlate domains
Fabric OS Administrators Guide 543
53-1003130-01