During preparation and preliminary information gathering for a new internal project, I had a need to emulate various networking conditions and scenarios. More specifically I’m looking at the possibility of running the vCenter Client over high latency satellite links, with varying bandwidth availability and even packet loss scenarios.
Obviously the best way of testing this, in a controlled environment, is to use some kind of WAN emulator that lets you control the various networking characteristics. WANem is a free WAN emulator and it even comes as a VMware virtual appliance.
Setup is pretty straight forward, and I won’t get into the detailed instructions at this point. If someone requests it, perhaps I’ll make a HOWTO post later on.
After the WANem Virtual Appliance has been started and setup in your network environment, all you have to do is to route your traffic through it. In my test environment, I decided to route all traffic between my local computer and my vCenter Server through the WANem appliance. Doing so is pretty straight forward; Open up a cmd window, with administrator privileges, on your local computer and use the route command to force traffic through WANem:
the command itself is: route add {destination IP} mask 255.255.255.255 {WANem IP}
To tune the network properties of the traffic going through WANem, open the WANem admin page in your browser and work some magic. The screenshots below are from the advanced tab:
As a simple test, I decided to add 500ms latency (delay time) and a packet loss of 25%, which worked fine.
Conclusion #
If you need to test out how your applications or networking infrastructure works when issues like latency, jitter and even dropped packets affects your clients, WANem seems like an easy and free route (pun intended) for testing purposes.
Related Posts
- Installing and Configuring WANem Virtual Appliance — Published
- SolarWinds VM Console — Published
- Developer meets PowerCLI - awesomeness ensues — Published
- VMware vSphere Hypervisor Licensing and Cost — Published
- Redesigning the vCenter Client? — Published