Applies To:
Show VersionsBIG-IP AAM
- 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
BIG-IP APM
- 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
BIG-IP LTM
- 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
BIG-IP AFM
- 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
BIG-IP ASM
- 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
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.