Known Issues for Panorama Plugin for VMware NSX 3.0.0
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 for Panorama Plugin for VMware NSX 3.0.0
The VM-Series firewall on VMware
NSX-T does not support automatic delicensing. See License the VM-Series Firewall for
information about delicensing the VM-Series firewall.
PAN-121449
The Remove Config button on PanoramaPlugins does
not remove the configuration for any plugins you have set up on
Panorama.
Workaround: Manually delete the plugin configuration.
Select your plugin on Panorama, clear the values from all fields and Commit your
changes.
This issue is fixed in PAN-OS 9.0.4.
PLUG-2223
The NSX-T Manager can connect to a standalone Panorama
appliance. Panorama appliances in an HA configuration is not supported
for your NSX-T deployment.
PLUG-2190
After upgrading the Panorama plugin for
VMware NSX to version 3.0.0 with NSX-V Manager and Service Definitions
configured, that configuration is lost if you downgrade from 3.0.0
to a previous version of the plugin.
PLUG-2163
When you install the VMware NSX plugin version 3.0.0
on a Panorama version earlier than 9.0.3, the installation is not blocked.
However, because Panorama 9.0.3 is the minimum version for the VMware
NSX plugin version 3.0.0, if you install the plugin on an earlier
version of Panorama, you must upgrade Panorama to version 9.0.3
or later to enable support for VMware NSX-T.
PLUG-2050
Changes made to the NSX-T service manager
configuration is not updated on Panorama after multiple Panorama
HA failover events. This causes the service manager status to be
out of sync between the Panorama appliances in the HA pair.
PLUG-1619
The following special characters cannot
be used in a service definition name—’<>&”.
PLUG-1618
You can open the NSX Manager Objects
window from PanoramaVMwareNSX-TService Managers but
displays no information.