NSX-T Edge Performance Degradation for North-South Data Traffic
search cancel

NSX-T Edge Performance Degradation for North-South Data Traffic

book

Article ID: 323695

calendar_today

Updated On: 12-23-2024

Products

VMware NSX

Issue/Introduction

  • North South traffic through an NSX Edge has poor performance
  • Traffic flows are not going through the Edge Flow Cache fast path, this is confirmed from root shell on the Edge

    #nsxdp-cli fc  flows get --vlan <VLAN ID> | grep <src IP> | grep <dest IP>
    48  0         100663327 27    SOSLRH  00:50:56:##:##:##   02:50:56:##:##:##    8     101   0     17      <src IP>     <dest IP>      00:00:00:00:00:00   00:00:00:00:00:00   
    49  0         100663327 27    SOSLRH  00:50:56:##:##:##   02:50:56:##:##:##    8     101   0     17      <src IP>     <dest IP>      00:00:00:00:00:00   00:00:00:00:00:00   
    50  0         100663327 27    SOSLRH  00:50:56:##:##:##   02:50:56:##:##:##    8     101   0     17      <src IP>     <dest IP>      00:00:00:00:00:00   00:00:00:00:00:00   
    51  0         100663327 27    SOSLRH  00:50:56:##:##:##   02:50:56:##:##:##    8     101   0     17      <src IP>     <dest IP>      00:00:00:00:00:00   00:00:00:00:00:00

    An S in the ACTN column indicates slow path 


Environment

VMware NSX-T versions prior to 3.2.1.1 

Cause

  • Data packets which flow through the Edge to the uplink do not take the optimized path through the flow cache fast path.

Resolution

  Fix is available in below NSX versions 

  • 4.0.1.0
  • 3.2.1.1 



Additional Information

Impact/Risks:

  • There will be a performance degradation

 

If you are contacting Broadcom support about this issue, please provide the following:

  • NSX version.

  • NSX manager logs.

  • Edge Logs.

  • Esxi log where the Edge resides.

Handling Log Bundles for offline review with Broadcom support