Known Issues in Panorama Plugin for VMware NSX 3.2.4
Table of Contents
Expand all | Collapse all
-
-
-
-
- Features Introduced in Zero Touch Provisioning 2.0
- Known Issues in the Zero Touch Provisioning 2.0.4 Release
- Known Issues in the Zero Touch Provisioning 2.0.3 Release
- Known Issues in the Zero Touch Provisioning 2.0.2 Release
- Known Issues in the Zero Touch Provisioning 2.0.1 Release
- Known Issues in the Zero Touch Provisioning 2.0.0 Release
- Limitations
-
-
Known Issues in Panorama Plugin for VMware NSX 3.2.4
The following list describes known issues
in the Panorama plugin for VMware NSX 3.2.4.
PLUG-10766
When downgrading from Panorama plugin
for VMware NSX 4.0.0 or 4.0.1 to 3.2.3 on an operation-centric deployment
running Panorama 10.1.x, new dynamic address group changes are not
seen on Panorama.
Workaround: Downgrade to Panorama plugin for VMware NSX
3.2.4.
PLUG-10652
When upgrading to or downgrading from
Panorama plugin for VMware NSX 3.2.4 or 4.0.1, dynamic objects are
not automatically synchronized.
Workaround: After upgrading or downgrading, select PanoramaVMwareNSX-TService Managers and click Synchronize Dynamic
Objects.
PLUG-5994
After a Panorama HA failover, the service
manager might become Out of Sync with the
message Services list is missing on Panorama...Downloading
new one.
Workaround: Execute the command request plugins reset-plugin only plugin plugin-name vmware_nsx on
Panorama.
PLUG-5987
If you downgrade to the Panorama plugin
for VMware NSX 3.1.0 after creating an NSX-T service definition
with Health Check as Enabled (default) while
the Panorama plugin for VMware NSX 3.2.0 is installed on Panorama,
the service definition create on plugin 3.2.0 will be Out-of-Sync after
downgrade due to a mismatch in Health Check configuration (changed
to Disabled).
Workaround: Set Health Check to Enable on
the out-of-sync service definition and Commit your
changes.
PLUG-5692
When you enable Device Certificate and
add PIN ID and PIN value to an existing NSX-V service definition
that had Device Certificate disabled, the PIN ID and PIN value are
not pushed to NSX-V Manager.
PLUG-5475
If Panorama HA failover occurs while
Panorama is disconnected from NSX-V Manager, the Service Manager
section of NSX-V Manager will display the IP address of the formerly
active (now passive) Panorama peer. This occurs after failover and
the connection between Panorama and NSX-V Manager is reestablished.
Workaround: Perform a manual config sync in Panorama to
display the correct Panorama IP address in NSX-V Manager.
PLUG-2959
Panorama incorrectly allows the modification
of the NSX-T plugin configuration while in a suspended state. Do
not attempt to modify the NSX-T plugin configuration on a suspended
Panorama; this action is not supported.
PLUG-2950
After a Panorama failover event, if there
are some configuration objects in NSX-T Manager but not Panorama,
you must manually remove those objects from NSX-T Manager.
Workaround: Contact VMware for information about manually
removing the objects from NSX-T Manager.
PLUG-2767
In a Panorama HA pair, NSX-T plugin configuration
is not automatically synchronized to the passive Panorama if the
passive Panorama comes up after the active Panorama.
Workaround: On the Panorama dashboard, Synchronize to
Peer on the HA widget.
PLUG-2630
You cannot use a service-definition across
multiple service managers; each service definition is mapped to
a unique service manager.
PLUG-2226
When a device group is added or removed
from an existing notify group, existing dynamic address groups are
not updated to reflect the device group change.
Workaround: Synchronize Dynamic Objects on PanoramaVMwareNSX-TService
Manager to update dynamic address groups.
PLUG-1618
You can open the NSX Manager Objects
window from PanoramaVMwareNSX-TService Managers but
displays no information.