Fabric OS Administrator’s Guide 431
53-1002745-02
Restrictions of FA-PWWN
16
When creating the DCC policy, use the physical device WWN and not the FA-PWWN.
If you use DCC, a policy check is done on the physical PWWN on the servers. In the case of an HBA,
the FA-PWWN is assigned to the HBA only after the DCC check is successful.
Refer to “DCC policy behavior with Fabric-Assigned PWWNs” on page 205 for additional
information.
Restrictions of FA-PWWN
Be aware of the following restrictions when using the FA-PWWN feature:
• FA-PWWN is supported only on Brocade HBAs and adapters. Refer to the release notes for the
supported Brocade HBA or adapter versions.
• FA-PWWN is not supported for the following:
- FCoE devices
- FL_Ports
- Swapped ports (using the portswap command)
- Cascaded Access Gateway topologies
- FICON/FMS mode
- With F_Port trunking on directly attached Brocade HBAs/adapters
FA-PWWN is supported with F_Port trunking on the supported Access Gateway platforms.
Access Gateway N_Port failover with FA-PWWN
If an FA-PWWN F_Port on an Access Gateway fails over to an N_Port that is connected to a different
switch, the FA-PWWN of that Access Gateway F_Port must also be configured on that switch. If not,
the FA-PWWN assigned to the Access Gateway F_Port following a failover will be different than it
was before the failover occurred. This situation may require the host to reboot to bring it back
online. Even after the reboot, the host may potentially go into a different zone because the
FA-PWWN is different.
To Next Page
Loading...
Need help?
General