Applies To:Show Versions
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.
On the Main tab, click
. The New Tunnel screen opens.
- In the Name field, type a unique name for the tunnel.
From the Profile list, select
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 the Key field, 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 the Profile field when you select a profile that requires this setting.
In the Local Address field, type the local endpoint IP
This should be a floating self IP address.
- In the Secondary Address field, select Specify, and type the non-floating local IP address of the tunnel.
- For the Remote Address list, retain the default selection, Any.
- From the Mode list, select Inbound.
- From the Traffic Group list, select the traffic group that includes the local IP address for the tunnel.
- Click Finished.