Access gateway in logical chassis cluster, Access gateway ports – Brocade Network OS Administrator’s Guide v4.1.1 User Manual
Page 213
For more information enabling and disabling AG mode, refer to
on
page 219 and
on page 220.
Access Gateway in logical chassis cluster
Although operations of a VDX switch configured in Access Gateway mode are similar to a node
configured in native VCS mode while in Logical Chassis Cluster mode, there are some unique
considerations that you should be aware of.
Nodes in a logical chassis cluster are configured in Logical Chassis Cluster mode. In this mode, both
the data and configuration paths are distributed to other nodes in the cluster. The entire cluster is
configured from the principal node. For more information, refer to
on page
55 for more information.
Behavior and operations of an Access Gateway node configured in a logical chassis cluster, such as
removing the node from or adding the node to the cluster, are similar to operations in other nodes in the
cluster. Access Gateway does not have any global configuration, so the default configuration for the
node in Access Gateway mode is similar to a cluster node in native VCS mode. Failover in the cluster,
both controlled and uncontrolled, also occurs the same as for an AG switch.
There are two methods for adding an Access Gateway node to the cluster:
• You can enable Access Gateway on a standalone switch, then add the switch to the cluster. Before
adding the switch, enable it for Access Gateway mode and configure Access Gateway features and
policies through the Network OS AG commands.
• You can enable Access Gateway on a switch that is already a node in the cluster by just enabling AG
on the switch. The switch will reboot and join the cluster enabled in AG mode.
Access Gateway ports
Access Gateway supports VF_Ports that connect host systems to the switch, L2 interface ports that
connect the switch to the VCS Fabric cluster, and FC N_Ports that connect the switch to a FC fabric.
In order for hosts attached to VF_Ports on a VDX switch to connect with F_Ports on a FC switch, the
VF_Ports must be mapped to VDX switch N_Ports. Enabling AG mode configures all FC ports as
N_Ports and maps VF_Ports to the N_Ports in a sequential, round-robin fashion. This allows for even
distribution of logins in a typical configuration where VF_Ports are sequentially allocated as ENodes log
in. You can change this default mapping by mapping any VF_Port to an N_Port using Network OS
commands as described in
For details on default port mapping for supported VDX platforms, refer to
225.
The following ports are supported on a VDX switch in AG mode:
• N_Port — Node port that connects a switch in AG mode to the F_Port on the Fibre Channel switch.
Port numbers are specific to the VDX Switch platform:
‐
VDX 6730-76 — Valid N_Ports are 0–16
‐
VDX 6730-32 — Valid N_Ports are 0–7
NOTE
In Network OS commands, N_Ports are designated by the format rbridge-id/port group/N_Port.
Therefore, 5/0/1 designates RBridge 5 and that N_Port 1 resides in port group 0.
• VF_Ports — Virtual Fabric ports for connection of FCoE hosts and devices behind LAG-supported
FSB devices. You can map these ports to specific N_Ports for connection to a Fibre Channel switch.
Consider the following specifications:
Access Gateway in logical chassis cluster
Network OS Administrator’s Guide
213
53-1003225-04