Skip to main content

Palo Alto Prisma Virtual ION Cluster - Create


To create a Palo Alto Prisma Virtual ION Cluster, prepare the Prisma SDWAN credentials for each virtual device and, if you plan to use BGP, determine the VM AS number(s) you will provide. In the console creation form you will select a software image and a flavor, then configure interfaces in this order: "#1 - Internet Interface - management", "#2 - Internet Interface - access", and "#3 - MPLS-VPN interface" (with optional VLAN sub-interfaces 101–108).

Step 1 - Select project​

Select the project in which you want to deploy your virtual Edge:

Select your project

Select your project.

Step 2 - Deployment configuration​

2.1 Name your Virtual Edge (This name will be displayed on the Virtual Network Edge dashboard)

Set Virtual Edge Name

Set Virtual Edge name.

2.2 Select the implementation mode: Cluster
Select implementation mode

Select implementation mode.

Virtual device configuration​

2.3 Fill the Virtual Device name (This name will be used as hostname for the virtual device).

2.4 Select the Orange POP which correspond to the location of POP.

Fill Virtual Device Name, Region and POP

Fill Virtual Device Name, Region and POP.

For Dual or Cluster Topology

For Dual topology, different POP can be chosen for each virtual Device.

For Cluster topology, the Virtual devices must be on the same POP.

Select Internet and MPLS Bandwidth for each Virtual Device.

Select Internet and MPLS bandwidth for the Virtual Device

Select Internet and MPLS bandwidth for the Virtual Device.

Step 3 - Virtual Edge configuration​

3.1 Select the Software version.

Available software versions are :

  • 6.2.1-b3

3.2 Select the Virtual Device flavor.

Available flavors are :

StandardDPDK
Small
2 vCPU
8 GB Mem
64 GB Disk
-
Large
8 vCPU
32 GB Mem
64 GB Disk
8 vCPU
32 GB Mem
64 GB Disk
Notes
  • For Dual topology, different flavors can be selected for each Virtual device.
  • DPDK (Data Plane Development Kit) is a set of libraries and drivers designed to acceler- ate packet processing and optimize performance in network applications. It provides a high-performance framework for managing network traffic at a low level, bypassing the traditional kernel network stack to enhance throughput and reduce latency.
    Pay attention the use of an image with DPDK significantly increases energy consumption and therefore the associated carbon footprint.

3.3 Click on Continue button to continue the journey or click on Save button to save the current deployment configuration.

Step 4 - Interfaces configuration​

Interfaces​

The portal presents the interface configuration in the same order used during provisioning:

  • #1 - Internet Interface - management: informational in the portal. A platform-allocated public IPv4 address for this interface is displayed after provisioning.
  • #2 - Internet Interface - access: informational in the portal. A platform-allocated public IPv4 address for this interface is displayed after provisioning.
  • #3 - MPLS-VPN interface: supports VLAN sub-interfaces 101–108. For each chosen VLAN sub-interface you can add one or more VPN entries. Each VPN entry includes a VPN Name and an optional VPN role. BGP options are available per VLAN sub-interface (toggle Enable BGP and, when relevant, set AS prepend).

Virtual device configuration​

Cloud-init and device userdata are generated by the platform for this VNF. Uploading custom cloud-init or userdata is not allowed in the creation form.

Virtual device configuration

Virtual device configuration.

Step 5 - Service specific parameters​

5.1 Fill in the following service parameters:

  • VM AS number (VM1): Autonomous System number for the virtual machine; the platform accepts 2- or 4-byte AS numbers in the specified range. minValue:1; maxValue:4294967295.
  • VM AS number (VM2): Autonomous System number for the second virtual machine; same constraints as VM1. minValue:1; maxValue:4294967295.
  • Prisma SDWAN key (VM1): Provide the Prisma SDWAN key for the virtual device so the platform can hand it to the Palo Alto orchestrator as part of provisioning. hideValue: true (sensitive)..
  • Prisma SDWAN secret (VM1): Provide the Prisma SDWAN secret for the virtual device so the platform can use it during provisioning with the Palo Alto orchestrator. hideValue: true (sensitive)..
  • Prisma SDWAN key (VM2): Provide the Prisma SDWAN key for VM2 in the provisioning form. hideValue: true.
  • Prisma SDWAN secret (VM2): Provide the Prisma SDWAN secret for VM2 in the provisioning form. hideValue: true.

5.2 Click on Continue button to continue the journey or click on Save button to save the current deployment configuration.

Step 6 - Validation​

After clicking the Continue button, a page summarizing the characteristics of the Virtual Edge will be displayed.

This page is divided into several sections :

  • Projects
  • Deployment
  • Virtual edge configuration
  • Interfaces configuration
  • Service specific parameters

At this stage, it is still possible to modify the characteristics for these sections.

One section is dedicated to display the Carbon footprint of the Virtual Edge :

Carbon footprint for Virtual Edge

Carbon footprint for Virtual Edge.

Click on the Provision button to initiate the provisioning of the Virtual Network Edge. You can also preserve the Virtual Network Edge configuration by clicking the Save and close button and the following toast is displayed.

In this case, you will find the Virtual Network Edge in designed state on the .

correctly saved toast