Traceflow

Two virtual machines are not communicating with each other. To discover which logical component is responsible, run a traceflow action to identify which logical component is dropping packets between two virtual machines.

Before you run a traceflow action, create a visual path in the NSX-vSphere Object Path dashboard to show the logical connectivity between two virtual machines, and try to identify any configuration problems. If you did not identify configuration problems, navigate to the NSX-vSphere Troubleshooting dashboard from the Logical Path widget.

Problem

Two virtual machines are not communicating properly.

Cause

There may be a configuration issue with one of the logical components connecting the virtual machines together.

Prerequisites

You have installed the VMware NSX 6.2 system in your environment.

Solution

1. In the NSX-vSphere Troubleshooting dashboard, in the Data Collection Results widget, select Run traceflow from the Choose Action drop-down menu, and click Run Action.
2. Enter the following information:
   • Protocol: Specify any of the following protocols:
     • ICMP
     • UDP
     • TCP
   • Source Port : If you have specified ICMP protocol, you do not have to enter any port information.
   • Destination Port : If you have specified ICMP protocol, you do not have to enter any port information.
3. To view the progress of the action as it runs in the Data Collection results widget, click Show action progress next to the Results drop-down menu.
   A table with the results of the traceflow is displayed. If the traceflow is successful, each component that the packet traversed is shown in the widget. If the traceflow fails, you can see where the packet was dropped together with information related to the component that dropped the packet.