Install the On-Premises Controller
Table of Contents
Expand All
|
Collapse All
Prisma SD-WAN Docs
-
-
-
-
- AWS Transit Gateway
- Azure vWAN
- Azure vWAN with vION
- ChatBot for MS Teams
- ChatBot for Slack
- CloudBlades Integration with Prisma Access
- GCP NCC
- Service Now
- Zoom QSS
- Zscaler Internet Access
-
-
- ION 5.2
- ION 5.3
- ION 5.4
- ION 5.5
- ION 5.6
- ION 6.0
- ION 6.1
- ION 6.2
- ION 6.3
- ION 6.4
- New Features Guide
- On-Premises Controller
- Prisma Access CloudBlade Cloud Managed
- Prisma Access CloudBlade Panorama Managed
- Prisma SD-WAN CloudBlades
Install the On-Premises Controller
Install the On-Premises Controller.
On-Premises Controller for Prisma SD-WAN offers various scaling profiles to deploy
the controller. Select the right template depending on your scaling requirements.
You can install on-premises controller using the web interface or the CLI commands.
- Host OS must be dedicated to on-premises controller functions.
- Avoid over-subscription of the Kubernetes compute resources.
- Ensure CPU and memory resource reservations.
- Consider 'thick' storage provisioning.
- ESXi/KVM or any hypervisor may host the Ubuntu host O.S.
To start the controller installation,
- One IP address for controller connectivity.
- The DNS and NTP server configuration.
- The name of tenant, for example, Acme Inc.
- The tenant domain, for example, acme.com.
Before the installation starts, validations are done to
confirm the resource capacity of the host for a specific number of sites, OS
version, and packages compatibility.
- Download qcow file. Contact your Palo Alto Networks Partner for assistance.Bring up the VM using the downloaded qcow file.Login to the VM using ubuntu/ubuntu.To format the disk space, execute the CLI command:printf 'd\n\nn\n\n\n\nN\nw' | sudo fdisk /dev/vdaKeep your management IP address handy and ensure it's not configured with DHCP.Access the Prisma SD-WAN Controller Installation user interface by using the URL https://<public IP of VM>:9443/installer.Click Get Started.Select a predefined configuration Template for the deployment and provide Server IP addresses for all nodes.The template configuration such as the number of sites, CPU models, and servers are pre-populated on selecting the template. Choose from the following templates:
- Demo small- single node setup for 10 sites
- Demo Large- multinode setup for 500 sites
- Multinode small- 3 node non-HA deployment for 100 sites
- Multinode HA large- 9 HA deployment for 1000 sites
If you want to set up HA, use a load balancer for high availability deployment. The HA setup requires 9 nodes—3 App nodes, 2 Stats nodes, 2 Ops nodes, 2 Arbiter nodes-1 each for Stats and Ops nodes. Refer to Minimum Hardware Requirements.Click Next.Provide Backup Configuration.Add Backup Schedule Time, Backup Retention Days, and Backup Schedule.Click Next.Setup Tenant by providing the Tenant Name, Tenant Domain, NTP Server IP address, and optionally Use Tenant Domain for southbound connection.Tenant domain for southbound connection is an optional field, if you provide the Tenant Domain for southbound connection when setting up the tenant, the given domain name is used. If you select to use the southbound domain, enter the domain name and IP address.Click Next.Verify the information you specified and then Install the controller.The installation will take approximately 60 minutes. You can view the progress of the installation on the user interface.You will be notified that the installation is complete and the services are running after the installation is complete.Download the login credentials for the Administrator console and the Operator console. Click the links to access the Administrator console or Operator console.