"NSX gateway is not available" after upgrade to NSX 4.1.x, when using L2 bridge
search cancel

"NSX gateway is not available" after upgrade to NSX 4.1.x, when using L2 bridge

book

Article ID: 390254

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • After upgrading to NSX version 4.1.x, the communication between the overlay VM and DV portgroup VM, via L2 bridge fails.
  • On the active edge node for the bridge profile, running the command 'get bridge' returns no data.
  • The NSX manager UI does show the edge bridge profile configured and applied correctly, with no error.

Environment

VMware NSX 4.1.x

VMware NSX 4.2.0

Cause

The NSX manager controller service, is missing the bridge port for the bridge endpoint profile ID (schema type: vmware.nsx.nestdb.LogSwitchPortConfigMsg), due to the missing information, the bridge configuration was not pushed from the NSX Manager (MP) to the Edge node(s) (DP), which lead to the datapath interruption.

Resolution

This issue is resolved in VMware NSX 4.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:

Create a new edge bridge profile with identical configuration, with the same edge cluster and Active/Standby edge nodes and assign it to the segments.

Additional Information

If this KB did not help resolve your issue, you can review the following KB for further troubleshooting steps: Troubleshooting NSX L2 Bridging