AHV networking

  • 15 July 2020
  • 0 replies
  • 368 views

Userlevel 2
Badge +2
  • Nutanix Employee
  • 12 replies

AHV uses Open vSwitch (OVS) to connect the CVM, the hypervisor, and guest VMs to each other and to the physical network. 

 

0HkzVE7FdBZtaokNl6tQebz41zDaRcjJvMdBBBAi0aDk0wMgGxr1W9aKrRMnJqOqeucDgtUI0lXgOx57tLpyIg0jwmm1MEou3YxQIcMN_j6nVRHW3pI4lHS4fX5Gd_W18eTt_Z2J

  • Open vSwitch:

OVS is an open source software switch implemented in the Linux kernel and designed to work in a multiserver virtualization environment. By default, OVS behaves like a layer-2 learning switch that maintains a MAC address table. 

  • Bridges

Bridges act as virtual switches to manage network traffic between physical and virtual network interfaces. The default AHV configuration includes an OVS bridge called br0 and a native Linux bridge called virbr0

  • Ports

Ports are logical constructs created in a bridge that represent connectivity to the virtual switch

  • Bonds
    Bonded ports aggregate the physical interfaces on the AHV host. By default, a bond named br0-up is created in bridge br0

 

VLANs for AHV Hosts and CVMs

 

mXGQt07bmWjiGx91u25hc5gucRADQgGRui7oQenIMQlJtIzQnztND3sKROqAUMdMdrngedKSkgHdLOErF03VfHXVnZprIsRbN1-2EfmobZo-0TS1FNaU27OA4raKgwDjuaZc_gFR

 

The recommended VLAN configuration is to place the CVM and AHV in the default “untagged” (or native) VLAN, as shown below.

 

If you do not want to send untagged traffic to the AHV and CVM, or the security policy doesn’t allow this, refer to the AHV Networking guide

 

For details about AHV networking please refer to the following links:

https://portal.nutanix.com/page/documents/solutions/details/?targetId=BP-2071-AHV-Networking%3ABP-2071-AHV-Networking

https://portal.nutanix.com/page/documents/solutions/details/?targetId=BP-2029_AHV%3ABP-2029_AHV

https://portal.nutanix.com/page/documents/solutions/details/?targetId=BP-2029_AHV:BP-2029_AHV


This topic has been closed for comments