Configure Prisma Access for Clean Pipe
Enable Multitenancy and Create a Tenant
- Install and activate Prisma Access for Clean Pipe.Prisma Access for Clean Pipe requires a separate license, and activating it creates Clean Pipe-specific tabs in the Cloud Services plugin. The procedure you use to install Prisma Access for Clean Pipe is the same as the procedure you use to activate and install a standard Prisma Access license, including installing the Cloud Services plugin.
- Enable multitenancy if you have not done so already.
- Select.PanoramaCloud ServicesConfiguration
- SelectEnable Multitenancy(located on the upper right of the page).
- ClickOK.TheTenantspage displays.
- In theOptionsarea, selectClean Pipe.
- Enter aNamefor the first tenant.
- Create and configure a newAccess Domainfor the first tenant and clickOK.
- In theClean Pipearea, enter aBandwidth (Mbps)forThis Tenant.Enter a minimum of 100 Mbps for each tenant you create.
- Create zones for the tenant and map those zones for the tenant.
- Select.NetworkZonesMake sure that selected the Clean PipeTemplatefor the tenant you created (cp-tpl-tenant).
- Create zones for the tenant (for example,TrustandUntrust).
- Selectand select thePanoramaCloud ServicesConfigurationTenantfrom the drop-down list.
- Select theClean Pipetab.
- Click the gear icon next toZone Mappingto edit the settings.
- AddandRemovethe zones you created to map them to trusted and untrusted zones.
- Onboard a new Clean Pipe.
- Select.PanoramaCloud ServicesConfigurationClean Pipe
- Adda new Clean Pipe instance for the tenant, entering the following information:
- Name—Specify a name for the clean pipe.
- Bandwidth—Select the Bandwidth to allocate for the clean pipe.You can onboard Clean Pipe instances in increments of 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1000 Mbps, 2000 Mbps, 5000 Mbps, and 10000 Mbps. The amount of bandwidth you specify must be within the licensed bandwidth allocation, and it must match the bandwidth of the VLAN attachment you create in the Partner Interconnect.
- Edge Availability Domain—Select the availability domain you want for the clean pipe. You can choose1,2,ANY, orREDUNDANT.
Be sure that you configure the first availability zone (zone1) as the primary zone on your CPE.You can also build a pair of clean pipes for a single tenant redundancy in different locations; to do so, specify1for the first clean pipe in one location and2for the second clean pipe in a different location.
- SpecifyANYfor a non-redundant Clean Pipe deployment.Make sure that your cloud provider supports this choice; you must also selectANYon the cloud provider side of the partner interconnect. If that choice is not available for your cloud provider, make another choice.
- To specify two VLAN attachments in the same location in an active/backup configuration in the same location, selectREDUNDANT.Prisma Access creates two pairing keys for aREDUNDANTconfiguration (one for each availability zone), and appends the clean pipe name withzone1for the first availability zone andzone2for the second availability zone. For example, if you specify aNameofSan Francisco, Prisma Access creates two zones namedSan Francisco-zone1andSan Francisco-zone2.
- BGP Peer ASN—Enter the BGP Autonomous System Number (ASN).You can specify either a private or public BGP ASN.Make a note of this value; you configure it on the customer edge (CE) router when you complete the Clean Pipe configuration.
- Location—Select the location.We recommend that you use the same location that you use when you create the VLAN attachment for the partner interconnect.
- Add more Clean Pipe instances as required by repeating Step 4.Be sure that each additional Clean Pipe uses a different location.
- Commit and push your changes to make them active in Prisma Access.
- SelectandCommitCommit and PushEdit Selectionsin the Push Scope.
- SelectPrisma Access, then selectClean Pipe.
- ClickOKto save your changes to the Push Scope.
- CommitandPushyour changes.
- Check that your Clean Pipe has been provisioned.
- Select.PanoramaCloud ServicesStatus
- Select theTenantfrom the drop-down list at the top of the page.
- ClickStatus.The Clean Pipe status displays.
- Hover over the Clean PipeConfig Statusand wait until the status changes fromProvisioning in ProgresstoProvisioned.This provisioning can take up to 30 minutes.
- Click theNetwork Detailstab, click theClean Piperadio button, and make a note of thePairing Key.TheMSSP CEandCloud Router IPfields are blank when you start to configure the Clean Pipe. These fields populate after you create the VLAN Attachment when you complete the Clean Pipe configuration.If you specified aREDUNDANTconnection, Prisma Access creates two pairing keys, one for each availability zone, and appends the clean pipe name withzone1for the first availability zone andzone2for the second availability zone. The following screenshot shows theSanFranciscoclean pipe with a redundant configuration; Prisma Access has created two pairing keys, one forSanFrancisco-zone1and one forSanFrancisco-zone2.Be sure that you configure the first availability zone (zone1) as the primary zone on your CPE.
Complete the Clean Pipe Configuration
To complete configuration of Prisma Access for Clean Pipe, you perform configuration in the Partner Interconnect and in Panorama.
Make sure that you can access and configure the CE and cloud routers on the Partner Interconnect (non-Prisma access) side of the Partner Interconnect.
- In the Partner Interconnect side of the configuration, create a VLAN attachment, using thePairing Keythat you retrieved from Panorama.For more information about creating VLAN attachments with Partner Interconnects and configuring customer edge (CE) routers to communicate with cloud routers, refer to the Google Cloud documentation at https://cloud.google.com/interconnect/docs/Make sure that the location and bandwidth you select matches theLocationyou specified in Panorama. The service provider you use for the Partner Interconnect uses the pairing key, along with your requested connection location and capacity, to complete the configuration of your VLAN attachment.
- After the connection comes up, return to Panorama, selectand make a note of thePanoramaCloud ServicesStatusNetwork DetailsClean PipeMSSP CEandCloud Router IPaddresses.These values populate after you enter thePairing Keyon the other side of the VLAN attachment.
- Log in to the CE router and perform the following configuration.
- Enter theMSSP CEaddress as the local IP address.
- Enter theCloud Router IPaddress as the peer IP address.
- Enter a BGP ASN that matches theBGP Peer ASNyou entered when you configured the Clean Pipe in Panorama.Make sure that you enter these values correctly; you cannot change them.
- Check the Clean Pipe status.
- In Panorama, select, select thePanoramaCloud ServicesStatusTenantfrom the drop-down, and check the Clean Pipe’sStatus.
- Select, and click thePanoramaCloud ServicesStatusClean PipeMonitortab to see a map with the status of the deployed Clean Pipes.Click the tabs below the map to see additional statistics for the Clean Pipes.Statustab:
- Compute Region—The compute region where your cloud service infrastructure is deployed for the clean pipe instance.
- Name—The name of the clean pipe instance.
- Allocated Bandwidth (Mbps)—The amount of bandwidth you allocated for the clean pipe instance.
- Config Status—The status of your last configuration push to the service. If you have made a change locally, and not yet pushed the configuration to the cloud, the status showsOut of sync. Hover over the status indicator for more detailed information. After committing and pushing the configuration to Prisma Access, the Config Status changes toIn sync.
- BGP Status—Displays information about the BGP state between the firewall or router at the clean pipe instance and Prisma Access. Although you might temporarily see the status pass through the various BGP states (idle,active,open send,open pend,open confirm, most commonly, the BGP status shows:
- Connect—The router at the clean pipe instance is trying to establish the BGP peer relationship with the cloud firewall.
- Established—The BGP peer relationship has been established.This field will also show if the BGP connection is in an error state:
- Warning—There has not been a BGP status update in more than eight minutes. This may indicate an outage on the firewall.
- Error—The BGP status is unknown.
- Status—The operational status of the connection between Prisma Access and the clean pipe instance.
- Region—The region where your cloud service infrastructure is deployed for the clean pipe instance.
- Name—The name of the clean pipe instance.
- Allocated Bandwidth (Mbps)—The amount of bandwidth you allocated for the remote network location.
- QoS— SelectQoSto display a page that contains graphical QoS statistics.
- Avg Egress Bandwidth 5 Min (Mbps)—The average amount of clean pipe egress bandwidth averaged over 5 minutes.
- Avg Egress Bandwidth 60 Min (Mbps)—The average amount of clean pipe egress bandwidth averaged over 60 minutes.
- Avg Ingress Bandwidth 5 Min (Mbps)—The average amount of clean pipe ingress bandwidth averaged over 5 minutes.
- Avg Ingress Bandwidth 60 Min (Mbps)—The average amount of clean pipe ingress bandwidth averaged over 60 minutes.
- Egress Peak Bandwidth 1 Hour (Mbps)—The amount of peak egress bandwidth for the clean pipe instance for the last 1 hour.
- Egress Peak Bandwidth 24 Hour (Mbps)—The amount of peak egress bandwidth for the clean pipe instance for the last 24 hours.
- Egress Peak Bandwidth 7 Days (Mbps)—The amount of peak egress bandwidth for the clean pipe instance for the last 7 days.
- Egress Peak Bandwidth 30 Days (Mbps)—The amount of peak egress bandwidth for the clean pipe instance for the last 30 days.
- Ingress Peak Bandwidth 1 Hour (Mbps)—The amount of peak ingress bandwidth for the clean pipe instance for the last 1 hour.
- Ingress Peak Bandwidth 24 Hour (Mbps)—The amount of peak ingress bandwidth for the clean pipe instance for the last 24 hours.
- Ingress Peak Bandwidth 7 Days (Mbps)—The amount of peak ingress bandwidth for the clean pipe instance for the last 7 days.
- Ingress Peak Bandwidth 30 Days (Mbps)—The amount of peak ingress bandwidth for the clean pipe instance for the last 30 days.
Recommended For You
Recommended videos not found.