Brocade Virtual ADX Installation and Deployment Guide (Supporting ADX v03.1.00) - Manual (Page 71)

Brocade Virtual ADX Server Load Balancing Deployments
● Brocade Virtual ADX common SLB deployments and configurations.............................71
Brocade Virtual ADX common SLB deployments and configurations
You can deploy the Brocade Virtual ADX in One-arm and In-line topologies. In the following sections,
you will see some examples of these deployments.
In the network diagrams shown below, the mgmt1 port of the Brocade Virtual ADX is connected to a
separate vSwitch that provides connectivity to the management network. The mgmt1 port of the
Brocade Virtual ADX does not belong to any VLAN so this port can receive only untagged traffic. In the
example below, the management network is in VLAN 10 configured on the vSwitch.
Server Load Balancing in One-arm topology without VLAN tagging
Deploying the Brocade Virtual ADX in the One-arm topology
The data ports of the Brocade Virtual ADX, "interface ethernet 1" and "interface ethernet 2" (eth1 and
eth2), are untagged members of VLAN 100 and 200 respectively. The corresponding port groups on the
vSwitch to which eth1 and eth2 are connected are also configured to be in VLAN 100 and VLAN 200
respectively. The real servers RS1 and RS2 are inside the ESX host. These and other real servers
could be inside or outside the ESX host. The vSwitch must be configured to be in the non-promiscuous
mode.
Brocade Virtual ADX Installation and Deployment Guide 71
53-1003241-01