Focus

Prisma Access

Configure Prisma Access Colo-Connect

Table of Contents

Filter

Expand All | Collapse All

Prisma Access Docs

Administration
Version
- Prisma Access China
- 4.0 & Later
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
Integrations
Incidents & Alerts
Release Notes
Version
- 5.0 Preferred and Innovation
- 4.2 Preferred
- 4.1 Preferred
- 4.0 Preferred
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred

Requirements and Prerequisites for Prisma Access Colo-Connect

App Acceleration in Prisma Access

Configure Prisma Access Colo-Connect

Configure a Colo-Connect deployment in Prisma Access.

Where Can I Use This?	What Do I Need?
`Prisma Access (Cloud Management)` `Prisma Access (Panorama Managed)`	A Panorama Managed Prisma Access deployment running a minimum Cloud Services plugin version of 4.1 and a minimum dataplane version of 10.2.4 A Colo-Connect add-on license

Prisma Access Colo-Connect consists of the following components:

Colo
—The colocation facility that provides rack-space, power and connectivity to host networking, private and public cloud infrastructure, such as Equinix.

Dedicated Interconnect
—The dedicated Layer 2 or Layer 3 physical connection between your router and a GCP edge router in a given GCP compute region. A dedicated Interconnect provides a direct physical connection between your on-premises network and the Google network.

Interconnects are called Links
in the Prisma Access UI.

GCP VLAN Attachment
—The logical Layer 2 connection over the link that separates traffic from any other logical connections sharing the same link.

VLAN attachments are called Connections
in the Prisma Access UI.

Partner Interconnect
—The Layer 3 physical connection between a service provider owned router and a GCP edge router in a given GCP compute region. A partner Interconnect provides connectivity between your on-premises and VPC networks through a supported service provider.

Colo-Connect supports both Dedicated and Partner interconnects.

Colo (Customer) Router
—The routing device in the Colo facility that establishes eBGP with the GCP cloud router over the interconnect in the Colo facility, as well as eBGP with Colo-Connect service connection over the GRE tunnel. It is a customer router for a dedicated interconnect, or if the service provider has Layer 2 connectivity with GCP over the partner interconnect. The service provider owns the Colo router when it has Layer 3 connectivity with the GCP cloud-router.

GCP Edge Router
—GCP's network edge equipment to provide physical connectivity between GCP and the customer/partner network via the Colo.

Cloud Router
—The GCP software construct in the cloud that establishes BGP sessions with the networking device (for example, router or Layer 3 firewall) in the Colo and routes traffic between Prisma Access and your network. You are not required to configure this component; it is automatically done by Prisma Access.

To configure Colo-Connect, you must first gather information about your existing network environment and make sure that you have all required network components in place. Ensure you have all prerequisites; then, deploy Colo-Connect in your organization's network using either a partner or a dedicated interconnect.

Panorama

Requirements and Prerequisites for Prisma Access Colo-Connect

App Acceleration in Prisma Access

Prisma Access Docs

Prisma Access

Configure Prisma Access Colo-Connect

Prisma Access Docs

Configure Prisma Access Colo-Connect

Recommended For You

Activation & Onboarding

SASE

Cloud-Delivered Security Services

Network Security

Endpoints

Visibility & Monitoring

Best Practices

Experts Corner