Palo Alto Initial Setup

This will follow the process to do initial setup of vPAN nodes including, admin login password setup and static address configuration.

A web interface will need to be used to access this device. It is recommended to use an external connector (bridge mode) with an unmanaged switch that can be used as out of band management as shown in the topology.

You will need to find a PAVM qcow2 image from a source. I will be providing my node .yaml file. DO NOT modify this file as Panorama OS is a 'picky bitch' when it comes to resources and will not behave properly. Symptoms can include but are not limited to Web login UI not loading and/or intermittent response from the CLI/Web UI.

Lab download:

Node download: vPAN Node



Start the vPANs, they can take up to 20m to startup. They will not allow login until they get past the second login that states:

PA-VM login:

Once booted and given access to a management network (our external connector) it will pull a DHCP address that it will display in the CLI. You can either navigate to this web address using https://<address> or you can login at the CLI.

We will use the web interface. The default credentials are admin/admin, it will prompt to change.


Once you are in the device navigate to Device>Interfaces>Management. From this page you will want to setup static IPs for your management interfaces as well as the services running on them.

You can also limit devices that have access through this management portal from this page.







Popular posts from this blog

  This will be a follow along for studying the ENCOR and any exams that follow. As well as any misc information that relates such as python scripting etc. The first portion will be basic notes that I decided needed to be my base. This includes but isn't limited to topics such as basic network principles, the layer 2 process, SSH setup, IOS upgrades. This first section will most likely align with the CCENT. I will focus on Cisco for the time being, but I would like to get into Junos (OS?) and Aruba OS. Syntax and basic info on documentation Syntax for commands will be as follows: Any portion of the command with "example" should be an object that you can change. For example, in the line ip vrf "name" the portion "name" is a name you can give to identify this specific vrf. At times this "example" will identify an identifier you can change or an option that is needed for input, but it will always denote something that is configurable. The descrip...
Read more