Scenario 1:3 – Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling –
VMware ESX 49
Summary
We created two VC networks, both with TWO active uplinks. Both VC Networks will pass several VLANs
as configured/defined by the connected switch, without modification or interpreting the VLAN tags.
When VC profile ESX-1 is applied to the server in bay1 and is powered up, it has two NICs, these NICs
are connected to “vNet-PROD-1” and “vNet-PROD-2” respectively, which connects to the network
infrastructure through uplinks. These NICs could be configured within the OS as individual NICs with their
own IP address or as a pair of TEAMED NICs connected to the same vSwitch. Either NIC could be
active. As a result, this server could access the network through either NIC or either set of uplink cables,
depending on which NIC is active at the time.
When additional bandwidth is required, additional uplinks could be added to each vNet.
If additional VLANs needed to be supported by these vNets, simply configure the upstream switch ports
for the new VLANs, then configure the ESX vSwitch with additional port groups to support these VLANs,
no additional Virtual Connect configuration is required.
As additional servers are added to the enclosure, simply create additional profiles, configure the NICs for
vNet-PROD-1 and vNet-PROD-2 and apply them to the appropriate server bays.
Results
The following graphic provides an example of an ESX server with TWO NICs connected to the same
vSwitch, the console is configured for VLAN 101, which was the Default (untagged) VLAN. Additional
port groups were configured to support each additional VLAN.
Figure 1-41
Both NICs for Profile ESX-1are connected to the network through vNet=PROD-1 and vNet-PROD-2,
VLANs are configured as Port Groups within the virtual switch.
Note: if the management/console VLAN was not set to Default within the server Profile, then the console would need
to be configured for the appropriate VLAN