Strata Copilot
    Strata Multitenant Cloud Manager
    : Configure Shared Interconnect
    Focus
    Download PDF
    Focus
    1. Home
    2. Secure Access Service Edge
    3. Strata Multitenant Cloud Manager
    4. Service Provider Interconnects
    5. Manage Service Provider Interconnects
    6. Configure Shared Interconnect
    Download PDF

    Strata Multitenant Cloud Manager

    Configure Shared Interconnect

    Table of Contents

    Configure Shared Interconnect

    Explains how to configure shared interconnect
    Where Can I Use This?What Do I Need?
    • Role: Multitenant Superuser or Superuser
    A shared interconnect uses a single connection to carry traffic for multiple tenants at the same time. This approach simplifies management, scales easily, and enables faster deployment when connecting multiple tenants.
    To set up a shared interconnect, perform the following:
    1. Access the Strata Multitenant Cloud Manager and select Configuration Configuration Center Set up Shared Interconnect.
    2. Configure the Cloud Service Provider:
      1. Select the Compute Region to view available or applicable Cloud Service providers.
      2. Select the Cloud Service Provider, such as GCP, and proceed to the next step.
    3. Configure Interconnect:
      1. Enter a unique Interconnect Name.
      2. Enter a unique SP Partner Name.
      3. Enter a valid email address for the partner.
      Currently, only partner interconnect type is supported which is selected by default.
    4. Configure the VLAN Attachments.
      • For AWS, specify the following:
        • Enter the VLAN Attachment Name.
        • Enter the public or private Border Gateway Protocol (BGP) Autonomous System Number (ASN) to establish peering for route exchange between the service provider network and the public cloud.
      • For GCP, specify the following:
        1. Enter the VLAN Attachment Name.
        2. Select the IP Stack Type: IPv4(single-stack) or IPv4 and IPv6(dual-stack)
        3. Specify the public or private Border Gateway Protocol (BGP) Autonomous System Number (ASN) to establish peering for route exchange between the service provider network and the public cloud.
        4. Enable BGP MD5 Authentication to use the hash algorithm, or Disable it to use plain text authentication.
        5. BFD Session Initialization mode for BGP peer: Passive or Disabled.
          • Passive: The cloud router will wait for the peer router to initiate the BFD session. For the router to wait, you must specify the BFD Transmission Interval, BFD Receive Interval, and BFD Multiplier.
          • Disabled: BFD will be disabled for this BGP peer.
    5. (Optional) Configure IP Pools.
      You can configure the IP Pool either now or later.
      1. Select Yes to configure the IP Pool, and provide the following details:
        • Prisma Access IP: Select this option to use a Prisma Access-assigned IP.
        • Bring Your Own IP: Select this option to configure the Ingress and Egress IP Pool.
      2. Select No to configure the IP Pool later. Until then, Prisma Access will use its own assigned IP.
    6. Review the configuration summary and Create Interconnect.

    © 2025 Palo Alto Networks, Inc. All rights reserved.