Known Issues in Panorama Plugin for VMware vCenter 1.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 in Panorama Plugin for VMware vCenter 1.0.0
Th following list describes known issues
in the Panorama plugin for VMware vCenter 1.0.0.
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-2204
If you enter an invalid vCenter IP address
or FQDN and click Validate, Panorama incorrectly
displays unknown error.
PLUG-1900
IP tags are not removed from a VM-Series firewall when
it is removed from a device group associated with a vCenter monitoring
definition. To remove tags from a VM-Series firewall, you must delete
the monitoring definition.
Workaround: Perform a commit before you synchronize dynamic
objects.
PLUG-1836
If you synchronize dynamic objects before performing
a commit after creating a monitoring definition, Panorama returns
an error message stating that monitoring definition is invalid.
PLUG-1835
The Panorama plugin for vCenter can only retrieve IP-address-to-tag
mapping information from non-VM-Series virtual machines in your
vCenter environment.
PLUG-1795
When the Panorama plugin for VMware vCenter
retrieves updated tags, Panorama deletes updated tags but the firewall
does not. For example, if you change a VM name in vCenter from VM1
to VM2, Panorama removes vmname.VM1 and adds vmname.VM2. However,
the firewall keeps vmname.VM1 and adds vmname.VM2.