Focus

VM-Series and Panorama Plugins Release Notes

Known Issues in Panorama Plugin for AWS 4.1.0

Table of Contents

Known Issues in Panorama Plugin for AWS 4.1.0

The following list describes known issues in the Panorama Plugin for AWS 4.1.0.

PLUG-13076

Fixed in Panorama plugin for AWS 5.1.1.

The Panorama plugin for AWS monitoring definition sometimes takes a very long to process IP addresses and update dynamic address groups.

PLUG-12009

During a Dynamic Address Group VM Monitoring, it is observed that the newly added VPC in the AWS console is not displayed.

Workaround: When the number of VPC entries exceed 500, configure the VPC manually using CLI commands.

PLUG-11912

It is observed that the AWS plugin fails to retrieve the Public IPv4 DNS tag and its corresponding Public IPv4 address associated to some network interfaces.

PLUG-11200

While using instance profile on HA peer, ensure that the instance profile is configured on both the AWS (peer) instances.

PLUG-11671

To support rolling upgrade on the Panorama Plugin for AWS 3.0.x or later, the number of the licenses needed must be twice the minimum number of instances in the Auto Scaling group configuration.

PLUG-12882

Fixed in Panorama plugin for AWS 5.1.1.

When using Panorama Plugin for AWS, the CloudFormation template stack deployment fails when creating AWS::EC2::VPCEndpointServicePermissions. To resolve this issue, include the parameter AllowedPrinciples in AWS::EC2::VPCEndpointServicePermissions. For example, the template should resemble:

"VPCEndpointServicePermissions": {
      "Type" : "AWS::EC2::VPCEndpointServicePermissions",
      "Properties" : {
          "AllowedPrincipals" : ["*"],
          "ServiceId" : {"Ref": "VPCEndpointService"}
      },
      "DependsOn": ["VPCEndpointService"]
    },

What's New in Panorama Plugin for AWS 4.1.0

Addressed Issues in Panorama Plugin for AWS 4.1.0