Default gateway for appliance showing as 0.0.0.0 in CA PAM deployed in Azure or AWS

book

Article ID: 211261

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM)

Issue/Introduction

Following the documentation for deploying a CA PAM appliance in AWS or Azure:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/privileged-access-manager/3-4-3/deploying/deploy-a-vhd-on-azure.html

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/privileged-access-manager/3-4-3/deploying/deploy-on-an-aws-amazon-machine-image-ami.html

the appliance is deployed in the corresponding VNET and given a Public IP to access.

However, in the network configuration for PAM, the gateway shows as 0.0.0.0 instead of the gateway for the Subnet where PAM has been deployed

Cause

This is normal: routing for PAM when deployed in these cloud platforms is taking care of by the underlying infrastructure, so no specification is needed here

Environment

CA PAM multiple releases

Resolution

This is working as designed and no action must be taken