Addressed Issues in VM-Series Plugin 1.0.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
-
-
Addressed Issues in VM-Series Plugin 1.0.4
The following list describes issues addressed
in the VM-Series plugin 1.0.4.
PLUG-2077
An intermittent issue with VM-Series on Azure where
interface mapping is incorrect when Azure accelerated networking
was enabled.
This issue is fixed in VM-Series plugin version 1.0.4. You
must install the plugin and reboot the firewall to address interface
mapping when Azure accelerated networking is enabled.
PLUG-1991
When a VM-Series firewall in FIPS mode is upgraded to
PAN-OS 9.0.1 or 9.0.2, you cannot log in to the firewall using your
existing login credentials.
This issue is fixed in PAN-OS 9.0.3 that has the VM-Series
plugin version 1.0.4. If using FIPS mode, use PAN-OS 9.0.3.
Workaround—If you do not want to upgrade to PAN-OS 9.0.3,
after you enable FIPS mode on the firewall running PAN-OS 8.1, add
another administrator before you upgrade to PAN-OS 9.0 and commit
your changes. Then upgrade the VM-Series firewall to PAN-OS 9.0.0
and login with the username and password for the user that you just
added.
PLUG-1872
The authentication key (client secret) associated with
the Active Directory application required for setting up the VM-Series
firewall in an HA configuration, is now encrypted on the firewall
and on Panorama.
Because the key is now encrypted, the
minimum version of the VM-Series plugin that you must install on
Panorama and the managed VM-Series firewalls on Azure is version
1.0.4. Without this version of the plugin, you cannot centrally
manage the firewalls from Panorama.