Addressed Issues in Panorama Plugin for VMware NSX 3.2.1

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

PLUG-6051

When the NSX manager is added in Panorama, the status displays
UNKNOWN
, and after adding the service definition, you see the error message
out of sync
. This occurs when the Azure configuration is as follows: VNET 1 has public access, VNET2 hosts an NSX deployment but does not have public access, and an express route connects VNET1 and VNET2. A ping between the private NSX manager IP address and Panorama works.
This issue is fixed in Panorama Plugin for NSX, version 3.2.1. With this fix, if the Panorama IP address is not found on the DHCP server, the VM-Series firewall retrieves it from the system disk.

PLUG-6379

The plugin does not correctly handle using the same template to configure different stacks. As a result, NSX-T Manager cannot map the correct zones or service profiles to the correct service definitions. To work around this issue, use unique templates.
This issue is fixed in Panorama Plugin for NSX, version 3.2.1.

PLUG-6658

vSphere 7.0.0 only supports vSphere Web Client HTML5. When you create an NSX Manager > Service Definition, the web UI does not display an option for ESXi 7.0.0. Furthermore, you cannot add a manual entry for ESXi 7.0.0 because the web client does not have configuration access to
NSX
Service Definitions
Manage
Deployment
.
This issue is fixed in Panorama Plugin for NSX, version 3.2.1. With this fix, Panorama Plugin for VMware NSX service definitions support ESXi 7.0.0.

PLUG-6842

This fix addresses an issue where an update to a Panorama device group did not synchronize the dynamic address group IP addresses on the VM-Series firewalls in the updated group.
This issue is fixed in Panorama Plugin for NSX, version 3.2.1.

PLUG-1633

Fixed an issue that caused Panorama to become inaccessible due to the Panorama plugin for NSX incorrectly exhausting disk space with dynamic address updates.

Recommended For You