Manual Chapter :
Configuring the BIG-IP System as an HNV Gateway
Applies To:
Show Versions
BIG-IP AAM
- 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
BIG-IP APM
- 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
BIG-IP Link Controller
- 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
BIG-IP LTM
- 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
BIG-IP AFM
- 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
BIG-IP ASM
- 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
Configuring the BIG-IP System as an HNV Gateway
Overview: Using the BIG-IP system as a Hyper-V Network Virtualization gateway
You can set up the BIG-IP® system to be an NVGRE gateway from a Microsoft
Hyper-V virtualized network to external networks, and to provide services within the virtualized
network. Each Hyper-V Network Virtualization (HNV) routing domain requires a number of per-subnet
(VSID) NVGRE tunnels. For each HNV routing domain, you need to create a single, inbound-only
tunnel with special inbound packet processing. Inbound NVGRE tunnels process traffic that was
forwarded by HNV distributed routers, which use a special VSID to forward all routed packets to a
gateway. Packets received from the inbound tunnel are internally remapped to the correct
per-subnet tunnel. Thus, all decapsulated packets appear to be arriving only from the correct
per-subnet tunnel.
Creating per-subnet tunnels for Hyper-V Network Virtualization routing domains.
You can configure an NVGRE inbound-only tunnel when you are using the BIG-IP system as a gateway between Microsoft Hyper-V Network
Virtualization networks and external networks.
- On the Main tab, click or .The New Tunnel screen opens.
- In theNamefield, type a unique name for the tunnel.
- From theProfilelist, selectnvgre.This setting tells the system which tunnel profile to use. The system-supplied NVGRE profile is adequate. To change the settings, you can create a new NVGRE profile, which then appears in this list.
- In theKeyfield, type the special Virtual Subnet Identifier (VSID) that is used by Hyper-V Network Virtualization distributed routers to forward all routed packets to a gateway.This field appears above theProfilefield when you select a profile that requires this setting.
- In theLocal Addressfield, type the local endpoint IP address.This should be a floating self IP address.
- In theSecondary Addressfield, selectSpecify, and type the non-floating local IP address of the tunnel.
- For theRemote Addresslist, retain the default selection,Any.
- From theModelist, selectInbound.
- From theTraffic Grouplist, select the traffic group that includes the local IP address for the tunnel.
- ClickFinished.
If you are using the BIG-IP system as a gateway, the preferred method is to install
the F5 Networks HNV Gateway PowerShell Module in the System Center Virtual Machine
Manager (SCVMM) for integration into a Microsoft Hyper-V environment.
