cancel
Showing results for 
Search instead for 
Did you mean: 
JRahm
Community Manager
Community Manager

There are a couple articles on DevCentral that cover VMware Fusion custom networking and a detailed deployment guide. The goal of this article is to prepare VMware Fusion specifically for setting up device services clustering, or DSC, as detailed in knowledge article K02234544 and in this Youtube video.

This is an example environment using time-limited BIG-IP trial licenses for the purpose of learning how to configure the Device Services Clustering feature. If you're reading this you're probably going through it for the very first time, so it's an introduction-by-screenshot.

Note: BIG-IP on VMware Fusion is unsupported by F5 Networks. The YouTube video explaining Device Service Clustering was performed on a laptop running VMware Fusion, but that does not guarantee that it will work in the future.

Requirements

  • VMware Fusion Pro
  • A Mac with 16+ GB RAM
  • A valid account at https://downloads.f5.com

Setup steps

The following steps will get you to the point where you can follow along with the video or article mentioned above.

Setting up Fusion for multiple networks

Open VMware Fusion and click Preferences.

0EM1T000002cDK4.png

Click Network Preferences.

0EM1T000002cDK9.png

Click the golden padlock to allow yourself to make changes, then click the plus button for each of the following networks.

0EM1T000002cDKE.png

The first network will correspond to your management network on the BIG-IP. Ensure that all of the settings shown here are configured. If you have not configured any other networks, the network will be called vmnet2 and it will be assumed to be called vmnet2 in this guide.

0EM1T000002cDKO.png

The second network will correspond to the external VLAN when setting up the BIG-IP.

0EM1T000002cDKT.png

The third network will correspond to the internal VLAN when setting up the BIG-IP.

0EM1T000002cDKY.png

The fourth network will correspond to the HA VLAN when setting up the BIG-IP.

0EM1T000002cDKd.png

Download BIG-IP and obtain a trial license

Obtain a BIG-IP software image at https://downloads.f5.com.

0EM1T000002cDKi.png

Make sure you choose the Virtual-Edition folder, you're looking for a .ova file to download. Any BIG-IP image will do for this lab, but the most recent LTS image at time of publishing is 15.1.2.1 is a good choice.

0EM1T000002cDKn.png

Choose the file that ends with "ALL-vmware.ova" and download it.

0EM1T000002cDKs.png

While you're waiting for the download to complete, you can obtain a trial license by going to https://downloads.f5.com/trial/. You may need to create an account and fill in some contact information. Make sure you generate two trial keys for yourself.

0EM1T000002cDKx.png

F5 will send you an email with the registration keys. The video shows you how to enter these during system setup.

0EM1T000002cDL2.png

Now that the BIG-IP image has downloaded you can import it into VMware Fusion. Click Import.

0EM1T000002cDL7.png

Click Choose File.

0EM1T000002cDLC.png

Choose the file you downloaded.

0EM1T000002cDLH.png

The file will now show up in the list. Choose it.

0EM1T000002cDLM.png

Read and acknowledge the EULA.

0EM1T000002cDLR.png

The deployment defaults of 2 CPU / 4GB is minimum for LTM but it's also about the maximum a 16GB laptop can do with two VMs and an additional VM for your web servers, so leave it at 2 CPU / 4GB RAM.

0EM1T000002cDLW.png

Name the VM something descriptive that implies it will be device #1.

0EM1T000002cDLb.png

It will take a while to import the image.

0EM1T000002cDLg.png

Once the import is complete, click Customize Settings. Do this before powering on the VM.

0EM1T000002cDLl.png

Select Networks. Here is how the networks will end up getting mapped.

0EM1T000002cDLq.png

Choose Network Adapter.

0EM1T000002cDLv.png

Select vmnet2 and then click Show All.
0EM1T000002cDM0.png

Choose Network Adapter 2.

0EM1T000002cDM5.png

Select vmnet3 and then click Show All.

0EM1T000002cDMA.png

Choose Network Adapter 3.

0EM1T000002cDMF.png

Select vmnet4 and then click Show All.
0EM1T000002cDMK.png

Choose Network Adapter 4.

0EM1T000002cDMP.png

Select vmnet5 and then click Show All.

0EM1T000002cDMZ.png

Now that the networks are configured, you can start the VM.

0EM1T000002cDMe.png

While this image is booting, you can create the second virtual machine. Give it a descriptive name implying that it is device #2 so you can recognize it later.

0EM1T000002cDMj.png

Once both VMs have been booted, you will have two command prompts.

0EM1T000002cDNr.png

Log in using the default BIG-IP credentials. You will be prompted to change your root password. In BIG-IP v14.0.0 and higher this is mandatory. You should also use this opportunity to change the password of the management utility (the GUI). You can do this with the following command:

tmsh modify auth user admin password <password>

0EM1T000002cDNm.png

Now run the config command.

0EM1T000002cDNh.png

Press OK

0EM1T000002cDNd.png

Accept IPv4 as the default.

0EM1T000002cDNc.png

Choose 'no' to override the DHCP setting.

0EM1T000002cDNX.png

Set the management IP of BIG-IP #1 to 10.1.1.245.

0EM1T000002cDNS.png

Leave the netmask at 255.255.255.0.

0EM1T000002cDNN.png

Configure the route.

0EM1T000002cDNI.png

Click Yes

0EM1T000002cDND.png

VM #1 is done and ready to log in.

0EM1T000002cDN8.png

Repeat these steps for the second VM, but use 10.1.1.246 as the management IP address.

0EM1T000002cDN3.png

Using your web browser, you can now log into https://10.1.1.245. Note that BIG-IP generates a self-signed management certificate. This will be fine for your local lab but you are required to accept that the SSL certificate is invalid. If using Chrome and it will not let you accept the risk, select a blank spot on the page and type thisisunsafe and it should override the security.

0EM1T000002cDMy.png

You are now logged into the setup utility.

0EM1T000002cDMt.png

Congratulations...you made it!! Now that your VMware Fusion environment is configured, you can proceed to setting up device services clustering, or DSC, as detailed in knowledge article K02234544 and in this Youtube video. Much thanks to Joe Reifel for the detailed diligence in documenting this solution!

Comments
JRahm
Community Manager
Community Manager

Some of this and much of the DSC guide that follows can be automated. In light (and honor) of Francois's charge in his Agility keynote this morning, I'll be following this article up with another to see how much of this manual process can be reduced, even in lab environments.

Version history
Last update:
‎20-Apr-2021 05:49
Updated by:
Contributors