North/South datapath impact for NSX-V workloads during V2T Migration after Edge cutover
search cancel

North/South datapath impact for NSX-V workloads during V2T Migration after Edge cutover

book

Article ID: 319097

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • After Edge cutover in V2T Migration, NSX-V workloads experience N/S impact.
  • On the affected Logical Switch, NSX-V Host VTEPs are not listed, only the MTEP host is listed. 

Environment

VMware NSX

Cause

Due to UFO and Policy changes in NSX-T 3.2, the replication mode defaults to MTEP mode unless it is explicitly defined.

As a fix starting in 3.2.1, the migration switching_plugin.py plugin, explicitly calls out the replication mode.

The Edge does not send the MTEP packet with the MTEP bit set in the VXLAN header, which is why the MTEP host does not replicate it to other local subnet hosts in the CDO TEP List.

The Edge datapath does not honor the MTEP setting when it sends VXLAN packets. This is fine as the expectation during V2T is that the Logical Switches should be in the source replication mode.

Resolution

This issue is resolved in VMware NSX 3.2.1, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

 

Workaround:

If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.