As you have see in Part 1 in this blog series we were able to get the ESXi host hardware configured as well as the Cloud Builder deployed and ready to power on (but don’t do that yet!).
After you have downloaded pfSense or the router of your choice we need to upload the media.
- Click Libraries in vCD
- Click Media & Other
- Click Add
- Select your catalog
- Click upload
- Navigate to your pfSense ISO and select it
- Click Open
- Click OK
This will upload the iso for your router to vCD. Next we need to build the VM.
Navigate back to your vApp and add a VM
- Name your router VM
- Click New VM as we don’t have a template yet
- Select Linux from the drop down
- Select Other 64bit
- Find your pfSense ISO or other suitable ISO
- Leave CPU count set to 1
- Change memory to a suitable value, here I am going to start with 4gb and update if needed
- Set storage to 12gb
- Click ADD twice to add two network adapters
- Set the value for network adapter 1 to the vAppNet-VCF value created earlier, leave network adapter type as E1000, set DHCP for IP Mode, and set as Primary Nic
- Set the value for network adapter 2 to the vAppNet-VCF value created earlier, leave network adapter type as E1000, and set DHCP for IP Mode
- Click OK
- Click Add (not pictured)
Time to power on our router and configure it, but don’t power on all of the VM’s
- Click the ellipsis next to router
- Click Power
- Click Power On
- Now Click VM Console to view the console to configure our router
- Click Enter key to accept the EULA (not shown)
This is a summarized configuration of pfSense to get us started before adding a Windows client desktop to our vApp.
Choose all the defaults through the installation process. After which you will configure interface eth0 or interface 1 as the WAN interface with the following information:
IP address: 192.168.0.2
Configure interface eth1 or interface 2 as the LAN interface with the following information:
IP address: 10.0.0.1
Choose enter or No Gateway when prompted
Now our router configuration has been started and should be able to be configured the remainder in the UI once our Windows Client is setup and configured. For this step we will assume you can add an additional VM and load it with the installation media for Windows Server in our case.
In our vCD environment our Windows server was configured with the following network information:
IP address: 10.0.0.2
The following packages were installed with the dependencies:
In Part 3 we will configure the Router via the UI as you will need to build your Windows server at this point.