Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
09-20-2023 01:00 PM
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:
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.
09-21-2023 04:33 AM
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?
09-21-2023 06:09 AM
We've deployed all the Service Connections allocated to us at this point.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
