F5: Setup Basic Web Load Balancing

KB ID 0001698

Problem

In past articles I’ve got my F5 BIG IP appliance up and running, and I’ve built some web servers to test load balancing. Now to actually connect things together and start testing things. Below is my lab setup, I will be deploying simple web load balancing (Static: Round Robin) between three web servers, each serving a simple HTTP web site.

Test F5 to Web Server Connectivity

For obvious reasons the F5 needs to be able to speak to the web servers, so it needs to be on the same network/VLAN and have connectivity. To test that we can log onto the the F5 console directly, and ‘ping’ the web servers.

So connectivity is good, let’s make sure we can actually see the web content on those boxes, the best tool for that is to use curl, which will make a web request, and the wen server ‘should’ return some HTML.

[box]curl http://10.2.0.11[/box]

F5 BIG-IP Load Balancing Terminology

Yeah I said ‘load balancing‘ and not ADC sue me! There are a number of building blocks that F5 uses, and you need to understand the terminology to put things together, firstly lets look at things BEHIND the F5 appliance;

  • Node: An actual machine/appliance, (be that physical or virtual.) That provides some sort of service or a collections of services e.g. a web server, telnet server, FTP site etc.
  • Pool Member: Is a combination of a Node AND a Port/Service, e.g. 192.168.1.100:80 (IP address and TCP port 80 (or HTTP)).
  • Pool: A Logical collection on Pool Members, that provide the same service e.g a collection of pool members offering a website on TCP port 80.

F5 BIG-IP Adding Nodes

While connected to the web management portal > Local Traffic > Nodes > Create (Note: You can also press the green ‘add’ button on the Node pop-out on newer versions).

Specify a name > Description (optional) > IP address (or FQDN) > ‘Repeat‘ > Continue to add Nodes as required, then click ‘Finished‘.

F5 BIG-IP Adding Pools

Now we have our Nodes, We need to create a Pool. Local Traffic > Pools > Create, (again on newer versions theres a green add button on the pop-out).

Add a Name > Description (Optional) > Add an applicable Health Monitor (in our case http) > Select the ‘Node List’ radio button > Select your first Node > Set the Port/Service  > Add  > Continue to Add the remaining Nodes.

Note: Here is where you add the IPs to the Port/Service and create the Pool Members.

Sorry! Busy Screenshot

When all the Nodes are added > ‘Finished‘.

Your web pool ‘should‘ show healthy, Note: that does not mean ALL the nodes are online!

To make sure ‘all’ the Nodes are healthy > Go to the Members Tab.

F5 BIG-IP Virtual Servers

I’m not a fan of using this term ‘Virtual Server‘ I prefer Virtual IP (or VIP,) but we are where we are! Above we’ve looked at things BEHIND the F5, now we need to present those services IN FRONT of the F5 (Note: I don’t say publicly, because we deploy plenty of BIIG-IP solutions inside  networks). So a Virtual Server is the outside IP address or FQDN of that a ‘consumer’ will connect to;

Local Traffic > Virtual Servers > Create.

Supply a name > Description (optional)  > Destination Address (the ‘available outside’) IP address > Set the service/port > Scroll down to the bottom.

Set the ‘Default Pool’ to the pool you created (above) > ‘Finished‘.

For a brief overview or check what you have created  > Click Local Traffic > Network Map Note: This will look different on older versions of the F5.

Then test the service form the outside, here each web server serves a different colour page so I can test it’s working properly.

My Web Page Does Not Change? If you keep seeing the same colour/page then it’s probably because you chose browser is ‘caching’ web content on your test machine, you may need to disable caching on your chosen web browser, for an accurate test.

So that’s Static Round Robin (Equal Ratio) Based Load Balancing. In the next article I’ll look at how you can manipulate the ratios, to better serve your hardware, and requirements.

Related Articles, References, Credits, or External Links

NA

VMware – Datastore Browser shows “Searching Datastore….”

KB ID 0000401 

Problem

I did a VMware VI3 to vSphere (4.1 U1) upgrade today. While bringing all the guest machines across, suddenly I could no longer browse the datastore, I only had one more guest to “Add to the inventory”, and all the mission critical machines were already migrated. I tried rebooting the virtual center, I tried restarting the ESXi host machines, still it sat saying “Searching Datastore……”.

Solution

1. I found the solution by accident. I was adding virtual machines to the new VSphere inventory, so I went in search of a method of doing it from the console, I was just about to:

Command to add a VMware guest to the inventory

[box]vmware-cmd -s register {full path to virtual machine}MACHINE_NAME.vmx[/box]

But, while looking in the folder with the guest files, I saw thousands of log files, I guess the VI client is struggling to parse them all, and display them. A quick internet search and I found out I can safely delete the log files.

2. Log into the ESX/ESXi servers console, for ESXi servers (version 4.0 and below) see here, for newer versions you can simply enable SSH access from Troubleshooting Mode Options > Enable Remote Tech support (SSH).

3. Log on as root and issue the following command to find the symlink path to your shared storage:

[box]ls -l /vmfs/volumes/[/box]

4. Now you know your symlink, you can change to the folder that contains the affected guest OS.

[box]cd /vmfs/volumes/{your symlink}/{your vm folder}[/box]

5. To get rid of all the log files, simply issue the following command.

[box]rm -f vmware-*.log[/box]

6. Now retry and you should see the folder contents when you “Browse Datastore”.

Related Articles, References, Credits, or External Links

NA

vSphere – Guest VM is shown as (Orphaned)

KB ID 0000414 

Problem

I’ve seen this happen a few times now, while looking at your Virtual infrastructure, one or more client machines is greyed out and shown as (Orphaned).

Solution

If you have many guests VM’s on one host with this problem, you can cure this by removing the parent host and re-adding it to the cluster, then right clicking it and select “Reconfigure for HA“.

Or you can do the following, on a machine by machine basis.

1. Right click the affected VM and select “Remove from Inventory” (nothing gets deleted don’t worry.)

2. Select one of your ESX hosts > Configuration > storage > Right click the storage that holds the virtual machine we are dealing with and select “Browse Datastore” > Locate the machines .vmx file > Right click > Add to inventory > Follow the instructions.

Related Articles, References, Credits, or External Links

For VMware View machines click here

Backup Exec – Error “0xe0009585 – Unable to open a disk of the virtual machine”

KB ID 0000349 

Problem

Seen while using Backup Exec 2010 R2, while attempting to backup an Exchange 2010 server (on Windows server 2008 R2) in a VMware virtualised environment (using the VMware Backup Exec Agent).

Click for Larger Image

Errors Read

Job Completion Status

Completed status: Failed
Final error: 0xe0009585 – Unable to open a disk of the virtual machine.
Final error category: Resource Errors

Errors

Backup- VMVCB::”Virtual infrastructure”
V-79-57344-38277 – Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error: You do not have access rights to this file
V-79-57344-38277 – Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error: You do not have access rights to this file

Solution

This involves two reboots of the target machine start planning downtime, or warning your users.

1. Go to the Virtual Machine that you are trying to backup (in my case the Exchange server)

2. Start > run > appwiz.cpl > Locate and uninstall the VMware tools > when prompted to > reboot.

3. Reinstall the VMware tools but this time choose “CUSTOM INSTALL” > Locate the “Volume shadow Copy Service”.

4. Change the drop down so that this option will not be installed > complete the VMware tools installation and reboot when prompted.

 

Related Articles, References, Credits, or External Links

NA