Deploying F5 BIG IP 12.X VE and BIG IQ VE (Hyper-V appliance) for NVGRE with SCVMM 2012 R2 or 2016 – part 1: prerequisites
Recently I’ve got a new customer to support which has the biggest WAP (Windows Azure Pack) infrastructure I’ve ever seen. This was really exciting because this customer is using multiple technologies on which I’ve never worked so it was a great opportunity for self learning. Indeed this customer is using F5 as firewall and as network service for handling nvgre tunnels in Sytem Center Virtual Machine Manager 2012 R2. Netapp as storage provider for the fabric (hyper-v over SMB3) and Nutanix for scale units compute (hyperconverged solution).
Since I was a “newcomer” on F5 technologies I did decide to work a little bit on that with some self learning. By chance F5 has an hyper-v appliance for BIG IP and BIG IQ and as a Microsoft employee I could get a hand on a lifetime license for both appliances (thanks to our partnership!). So at that point I had nothing to stop me starting to learn F5 capabilities but free time… yes! free time! and you will need a lot of it if you will go through every F5 BIG IP / BIG IQ capabilities.
Another great thing about using F5 BIG IP VE for NVGRE is that it allows you to save a host. When using NVGRE with Windows Server 2012 RRAS, you need to dedicate an hyper-v host for that particular role or at least you won’t be able to deploy any VM which uses HNV on the host hosting the gateway VM.
I’ll only focus on what is required to get BIG IP and BIG IQ up and running for integration with SCVMM 2012 R2 or 2016. I’ll consider that your environment already contains every component required such as logical switch, logical networks, port profiles and so on. I’ll just describe mine as a reminder in case you are missing one of these prerequisites.
First of all you will need to download some pieces from F5:
BIG IP VE 12.X VHD: BIGIP-184.108.40.206.0.606.LTM.vhd.zip
BIG IQ VE 4.6.0: BIG-IQ-220.127.116.11.0.119.vhd.zip
F5 Network Gateway Powershell module: https://onedrive.live.com/redir?resid=D94F6B22E15E4188!40673&authkey=!AOtrHcl5uA8mcRE&ithint=file%2czip
Then now you will need to be sure that your different network are already created and configured in VMM 2012 R2. In my case I’ll be using 3 different networks with their respective IP Pool.
PA network – connected network with HNV: Provider Address Space | Vlan 0 | 10.10.0.0/24
External Network – connected network: provide access to the outside world | Vlan 0 | 192.168.4.0/24
Infrastructure network – connected network: Management network | Vlan 0 | 192.168.2.0/24
Since we are using connected network a VM Network should have appeared for each logical network in VM networks view.
Now you need to be sure that all your network sites are allowed on your teaming used for your logical switch
also provide a Tenant port profile to your switch which has guest ip capability
Check your Uplinks to be sure that all network sites are properly configured. (I have 2 uplink teaming profiles because I have multiple hosts/clusters and I don’t use LACP on all of them.)
Now be sure that your networks are properly routed on your switches. For instance I’m using a CISCO switch which will always be on X.X.X.254 and my ISP box is on 192.168.0.1 for internet connectivity.
now you are done with prerequisites and we can move to part 2 to create the BIG IP VM and configure BIG IP.