Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 218)

‐ FC hosts or targets cannot be directly attached to the VDX switch.
‐ The VDX AG switch cannot be connected to a Fabric OS Access Gateway in a Cascaded
configuration.
• Access Gateway does not "bridge" the VCS and FC fabrics:
‐ Hosts connected to VF_Ports mapped to Access Gateway N_Ports appear on the FC
fabric only.
‐ Device FC IDs are assigned by the FC fabric F_Ports connected to the Access Gateway
N_Ports.
‐ VF_Ports and N_Ports are under the Access Gateway dæmeon's configuration.
‐ Fibre Channel OS components, such as management server, name server, and zoning are
restricted on Network OS Access Gateways just as they are on Fabric OS Access
Gateways. Refer to the Fabric OS Access Gateway Administrator's Guide for a complete
list.
‐ Although the show fcoe login command will display FCoE devices connected to the
Access Gateway switch VF_Ports, these devices are in the FC fabric and cannot be
detected by the VCS Fabric name server. Therefore, these devices cannot be zoned in a
VCS Fabric.
FCoE and L2 support and limitations
The following functions are supported:
• The following functionality is supported for a configuration consisting of a vLAG from a host CNA to
two Access Gateway switches or to an AG switch and a VCS Switch (L2 vLAG for top of rack split):
‐ The vLAG links can carry L2 and L3 traffic.
‐ VLAG support is identical to support in native VCS mode.
‐ A separate FCoE device login is supported through each AG switch.
• The following functionality is supported for a configuration with a LAG from an FSB to an AG switch:
‐ LAG specifics, such as number of links and contiguous vs. discontinuous, is identical to
native VCS support.
‐ Multiple LAGs can connect to the AG switch (one per FSB).
‐ LAG carries L2 and L3 traffic.
‐ Devices connected via an FSB LAG cannot talk to a Cisco SAN.
‐ LAGs and direct attached devices are supported on the same AG switch.
• The following functionality is supported for VF_Ports and CEE interfaces:
‐ VF_Ports are dynamically bound to Ethernet interfaces as in native VCS mode.
‐ As in native VCS mode, all CEE interfaces with connected devices must be configured for
FCoE.
‐ The CEE interface will come up as an ISL ET port if it is connected to a peer ET port on
another switch in the VCS Fabric.
‐ As in native VCS mode, 64 VF_Ports are allocated by default.
‐ A VF_Port an accept up to 64 NPIV logins.
‐ As in native VCS mode, VF_Ports are dynamically allocated as devices come up.
‐ As in native VCS mode, VF_Ports can be statically bound to ENodes.
‐ VCS Fabric services run on VCS ports and not under Access Gateway.
‐ As in native VCS mode, the number of VF_Ports allocated can be changed dynamically:
Using Access Gateway
218 Network OS Administrator’s Guide
53-1003225-04