Hyper-V feature restrictions

This section describes the following restricted vRouter features that do not function or require specific Hyper-V configuration in the Hyper-V environment.

Restricted features include:

LACP does not work on Hyper-V
VRRP in RFC-Compliant mode
Currently, no Hyper-V settings allow RFC-compliant MAC address behavior for VRRP interfaces. To prevent RFC compatibility issues when running a vRouter on a Hyper-V platform, by default, RFC-compliant MAC address behavior is not enabled on the vRouter.
Port Mirroring (SPAN, RSPAN, ERSPAN)
Hyper-V must have MAC address spoofing enabled for Port Mirroring to work.

VRRP in RFC-Compliant mode

vRouter features that do not work in the Hyper-V environment include the behavior of RFC-compliant MAC addresses for VRRP interfaces.

The default behavior of non-RFC-compliant MAC addresses is required for any deployment in which Hyper-V provides Layer 2 services, because it appears that Hyper-V does not support delivery of multicast packets sent from a virtual MAC. For more information, refer to Hyper-V documentation.

Port Mirroring (SPAN, RSPAN, ERSPAN)

Regardless of the flavor used, the vRouter replicates traffic to the destination interface from a multitude of MAC addresses from which the traffic was originally received. Hyper-V blocks all such traffic unless a Hyper-V feature called MAC Spoofing is enabled. For more information, refer to Hyper-V documentation.

Note:

A Google search of hyper-v mac spoofing yields good results.

Vyatta documentation

Learn how to install, configure, and operate the Vyatta Network Operating System (Vyatta NOS) and Orchestrator, which help drive our virtual networking and physical platforms portfolio.

Hyper-V feature restrictions

Helpful Links

Key Resources