: Known Issues in VM-Series Plugin 1.0.12
Focus
Focus

Known Issues in VM-Series Plugin 1.0.12

Table of Contents

Known Issues in VM-Series Plugin 1.0.12

The following list describes known issues in the VM-Series Plugin 1.0.12.

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:
  1. Upgrade VM-Series Plugin to version 1.0.12.
  2. Reboot the passive HA peer and wait for it to come up.
  3. 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
:
  1. Reboot the passive firewall. After it boots the active firewall detects 1.0.12 installed and shows a match.
  2. 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-4179

When you bootstrap the VM-Series firewall with
dhcp-accept-server-hostname=yes
in the
init-cfg.txt
file, then subsequently update the hostname for the VM-Series firewall, the hostname does not update in the
<namespace>_dimension
CloudWatch metrics.
Workaround:
To change the hostname after boot up, use one of the following methods to prevent the firewall from accepting the hostname sent by the DHCP server:
  • CLI command:
    dhcp-accept-server-hostname=no
  • init-cfg.txt
    file: Remove
    dhcp-accept-server-hostname=yes
    , or set
    dhcp-accept-server-hostname=no
    .

PLUG-3721

On VM-Series firewalls deployed using a flexible Pay-As-You-Go (PAYG) license, the
Dashboard
and under
Device
Licenses
in the web interface or using
request license info
in the CLI displays the capacity license as VM-300 regardless of the capacity license applied.
Workaround
: Execute the command
show system info
to verify the capacity license applied to your VM-Series firewall.

PLUG-3562

In OCI, if you assign secondary IP addresses to HA interfaces, those IP addresses are incorrectly moved to the passive HA peer in the event of a failover.

Recommended For You