Sample WAN Emulation configurations

Sample WAN Emulation configurations
• The following slides provide sample configurations
for WAN Emulation using a variety of physical and
virtual environments.
• Important note: In general it is not recommended to run tests
using concurrent VMs on a single type-2 hypervisor host, such
as VMWare Workstation. One should use a type-1 hypervisor
such as VMWare ESX or MSFT Hyper-V for running multiple
machines concurrently as they allow you to control resource
(CPU, RAM, Network) allocation, reservation and prioritization
and allow more realistic network integration capabilities
including use of virtual switches, vlans, etc.
Pg. 1
Using Physical Hosts
1
Ad-hoc, Dedicated Link*
Client
Server
eth1
eth0
WAN-Bridge
* Note: Use a cross-over cable s if NICs are not GigE
Client and Server must be configured with the same IP Subnet and a static
IP, unless the server is also a DHCP server.Default GW should be set to
127.0.0.1
WANBridge nTop interface can be accessed from Server or Client.
Router
2
Shared Link
eth1
AD/DNS/DHCP Server
eth0
WAN-Bridge
LAN
Server
Pg. 2
Using VMWare Workstation
3
Client
VM
Ad-hoc, all-virtual *
Server VM
VM
VMNET2
VMNET3
VM
eth1
VM
eth0
WAN-Bridge
* Note: VMNET0,1,8 are special purpose networks and should not be used in this
scenario.
Client and Server must be configured with the same IP Subnet and a static IP, unless
the server is also a DHCP server.Default GW should be set to 127.0.0.1
WANBridge nTop interface can be accessed from Server or Client.
Router
4
Virtual clients, physical server
VMs
VM
VMNET2
VMNET0**
eth1
eth0
WAN-Bridge
** Note: VMNET0 (default bridged-mode) will allow access to the
physical LAN. Clients are on the same IP subnet as the LAN. DHCP
requests will be answered by the LAN DHCP server.
Default GW will be retrieved from DHCP or should be set to the LAN
router address for internet access.
WANBridge ETH0 should face the DHCP server as the bridge will
use its MAC address for lease.
Pg. 3
AD/DNS/DHCP Server
LAN
Server
Using VMWare ESX/ESXi
5
Client
VM
Ad-hoc, all-virtual*
VM
Server VM
vSwitch1
vSwitch2
VM
eth1
VM
eth0
WAN-Bridge
* Note: both vSwitches must have security configured to allow promiscuous access.
Client and Server must be configured with the same IP Subnet and a static IP, unless
the server is also a DHCP server. Default GW should be set to 127.0.0.1
WANBridge nTop interface can be accessed from Server or Client.
Physical LAN
vSwitch3
Physical
NIC
NAT Router
6
All-virtual**
(clients & datacenter)
VMs
VM
AD/DNS/DHCP Server
VM
VM
vSwitch1
vSwitch2
eth1
eth0
VM
WAN-Bridge
** Note: vSwitches 1&2 must have security configured to allow promiscuous access.
vSwitch3 will allow access to the physical LAN when using a NAT Router. Clients are
on the same IP subnet as the datacenter (not the physical LAN). DHCP requests will
be answered by the datacenter DHCP server.
Default GW will be retrieved from DHCP or should be set to the Internal leg of the NAT
router address for internet access/physical LAN access.
Pg. 4
VM
Server
Using VMWare ESX/ESXi
7
virtual clients & physical LAN*
VMs
Server
VM
vSwitch1
vSwitch2
eth1
Physical
NIC
eth0
AD/DNS/DHCP Server
WAN-Bridge
* Note: vSwitches 1&2 must have security configured to allow
promiscuous access. Clients are on the same IP subnet as the
Physical LAN. DHCP requests will be answered by the LAN DHCP
server.
Default GW will be retrieved from DHCP or should be set to the
LAN router address for internet access.
8
LAN
Router
virtual clients & physical LAN**
VMs
Server
vSwitch1
Physical
NIC
eth0
eth1
AD/DNS/DHCP Server
WAN-Bridge
** Note: Clients are on the same IP subnet as the Physical LAN.
DHCP requests will be answered by the LAN DHCP server.
Default GW will be retrieved from DHCP or should be set to the
LAN router address for internet access.
LAN
Router
Pg. 5