Addressed Issues in VM-Series Plugin 1.0.13
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.13
The following list describes issues addressed
in the VM-Series plugin version 1.0.13.
PLUG-6015
In some VM-Series firewall HA deployments
on Azure, if the active management server makes a connection request
to Azure that does not resolve, you might see the UI freeze, delayed
commits, or synchronization loss in an HA pair.
This issue is addressed in VM-Series plugin version 1.0.13
and later, and version 2.0.2 and later.
PLUG-5663
For an HA pair deployed on AWS, upgrading
the VM-Series plugin to version 1.0.12 will fail to move interfaces
to the new active peer during failover event.
Workaround:
- Upgrade VM-Series Plugin to version 1.0.12.
- Reboot the passive HA peer and wait for it to come up.
- Reboot the active peer.
This issue is fixed in VM-Series plugin version 1.0.13.
PLUG-5658
After upgrading an HA pair from VM-Series
Plugin 1.0.11 to 1.0.12, the user interface shows a plugin mismatch.
Workaround:
- Reboot the passive firewall. After it boots the active firewall detects 1.0.12 installed and shows a match.
- Reboot the active firewall. After it boots it detects 1.0.12 on the passive firewall and shows the plugins match.
This issue is fixed in VM-Series plugin version 1.0.13.
PLUG-5542
On a VM-Series firewall deployed on Azure,
after shutting down the VM and changing the primary NIC from the
Azure CLI, the firewall is pingable but it is hours before you can
reach it with SSH/HTTPS.
This issue is fixed in VM-Series plugin version 1.0.13.