: Addressed Issues in Panorama Plugin for VMware NSX 3.2.3
Focus
Focus

Addressed Issues in Panorama Plugin for VMware NSX 3.2.3

Table of Contents

Addressed Issues in Panorama Plugin for VMware NSX 3.2.3

The following issues are addressed in the Panorama plugin for VMware NSX 3.2.3.

PLUG-8404

Upgrading from NSX Plugin 2.0.6 to 3.2.2 resulted in panorama losing the NSX Plugin configuration.
This issue is fixed in Panorama Plugin for NSX, version 3.2.3.

PLUG-8395

An active Panorama should always be in sync with the NSX-T Manager. However after recovering from a split brain (a state where the connectivity between the two Panaromas is down due to which both of them behave as active), it is observed that the active Panorama goes out of sync with the NSX-T Manager.
This issue is addressed in Panorama Plugin for NSX, version 3.2.3 by fixing the timing of the revision number update between the config sync flag and the database.

PLUG-5982

Fixed an issue that caused a commit failure on a FIPS-enabled Panorama with the Panorama Plugin for VMware NSX installed.

PLUG-5425

NSX-T Service Manager displayed the Last Dynamic Update only for the first Service Manager and not the second Service Manager.
This issue is fixed in Panorama Plugin for NSX, version 3.2.3. With this fix, the GUI now displays the Last Dynamic Update for all Service Managers.

PLUG-8219

When the Panorama plugin for VMware NSX checks for connectivity before comparing the configuration between Panorama and the NSX-T Manager, the plugin creates a log entry for the connectivity check. The log can be viewed in plugin_vmware_nsx_nsxt-mon.log.

PLUG-8218

Fixed an issue that caused full-sync API calls, from Panorama to NSX-T Manager, to fail for a given security group due to a connectivity issue between Panorama and NSX-T Manager.

PLUG-8217

You can now use the Panorama CLI to disable the automatic full sync that occurs when the connection status changes (Invalid Credentials to Registered and No Connection to Registered) between Panorama and all NSX-T managers in your deployment.
request plugins vmware_nsx nsx_t trigger-full-sync enable No Do not trigger full sync Yes Trigger full sync

Recommended For You