topic Re: Prisma Access GCP Onboarding -- GCP IP Conflict in Prisma Access Discussions

Prisma Access GCP Onboarding -- GCP IP Conflict

JBowerman_SS — Wed, 20 Sep 2023 20:00:29 GMT

I'm attempting to onboard a GCP instance into Prisma Cloud as a Remote Network. I've setup the Prisma Access side and I'm attempting to setup the GCP side of the configuration. I'm using a HA VPN Gateway to have the dual resilient tunnels. However, when attempting to submit the configuration within GCP, I receive an as shown below:GCP Onboarding Error

If I select a non-GCP Node for the RN termination location, the error goes away (Miami-AWS for example). ARIN WHOIS shows the IP space is owned by Palo. Has anyone else encountered this and is there a work around. Using the non-GCP Prisma Access location is not local to the GCP instance (US-East-1) so that's not an optimal performance solution.

Re: Prisma Access GCP Onboarding -- GCP IP Conflict

reaper — Thu, 21 Sep 2023 11:33:18 GMT

since those IP's are attached to GCP (ownership is a bit of a question mark) your short term recourse is to connect to one of the AWS RN-SPNs.

Have you looked into hooking up a service connection instead of RN?

Re: Prisma Access GCP Onboarding -- GCP IP Conflict

JBowerman_SS — Thu, 21 Sep 2023 13:09:41 GMT

We've deployed all the Service Connections allocated to us at this point.