VM to VM Networking Troubleshooting in AHV

  • 9 October 2020
  • 0 replies
  • 817 views

Userlevel 3
Badge +2

Synopsis:

 The goal of this workflow is to walk-through troubleshooting VM to VM communication issues in a Nutanix Cluster. Most customers are very vague when they state they have a networking issue. We will go through painting a complete picture of the network topology by asking the right questions and running commands on the Hypervisors.

 

AvIOt2XuSahI6pKHBBHb38roEf4rp7DUPmbdsnXpA9YoDEJC8-5S9wdicnvL86sSmgceC7KJfN5CYTZI3vjks6vP4tV1iCarVAeg6K9WeNWSLBfcjcDhGTaPVbhoFP2ynn-QZe1b

 

Initial Triage:

Questions to Ask: 

  • What hypervisor is running on the cluster? 

  • What guestOS is running on the VMs?

  • Are the VMs on the same node or different nodes? 

  • Are the VMs configured to use the same VLAN? 

  • What method is the customer using to test connectivity? 

  • Is there any Firewalls or ACLs that would stop this VM traffic? 

 

Information to gather: 

  • NIC teaming/bond configuration on node.

  • Switch vendor and model from upstream switch.

  • Interface configurations for the interfaces connecting to the nodes.

  • If ESXi is the customer running  on a Standard vSwitch or Distributed vSwitch?

  • VLAN information for each VM.

  • IP and Subnet Mask configuration for each VM.
     

Hypervisor Networking Commands: 

AHV

Information To Gather:

Where to get this information:

Information To Gather:

Where to get this information:

Uplinks used on host

From CVM: manage_ovs show_interfaces

Bond configuration

From CVM: manage_ovs show_uplinks

VLANs used by VMs

Prism VM tab

IP Configuration for the VMs

GuestOS

 

For more info on AHV networking and VM networking:

Ahv Networking Best Practices


This topic has been closed for comments