There are multiple ways to configure a PA-220 out of the box, via Web interface and the console ports.
I have always used standard RJ-45 console ports before but never micro-USB. I thought I would connect the cable provided in the box to my Windows 10 laptop and give it a try. From the quick start guide, a link is provided for setting up the micro USB console port here: Palo Alto Networks Micro USB Console Port
The Microchip USB/driver is installed in Windows 10 by default. After connecting the USB cable to my laptop and the other end to the micro USB port on the front of the PA-220, I checked out device manager in Windows to see that it shows up as a USB Serial Device (COM4.) It may very well show up as a different COM port for you, so your mileage may vary.
|Device manager screenshot, showing USB Serial Device (COM4) under Ports (COM & LPT)|
I always tend to use Putty for terminal emulation in Windows. You can find Putty here: Putty Download
In Putty you will want to select Serial and type in the COM port found in device manager. Leave the speed at 9600 as pictured below.
|Putty settings for the micro USB console port.|
When you click Open in Putty you should see a PA-220 login: prompt.
|PA-220 login prompt|
Of note here, the PA-220 login prompt will only show up when the firewall has completely finished booting. Pay attention to the STAT LED on the front of the firewall, it will be ready to authenticate you when it turns GREEN (from my previous post, this process may take around 9 minutes.) Interpret the LEDs on a PA-220 Firewall
admin/admin is the default password for Palo Alto firewalls out of the box.
After authenticating you should see the following prompt:
|PA-220 - Command prompt.|
If you type a question mark ? you will see a list of commands available at this prompt.
The > prompt indicates operational mode (i.e. non configuration mode.)
You can execute various show commands, ping a device, reboot/restart the firewall or services from this mode of operation.
If you type in a command, followed by a space with another question mark you can step through the commands to find the one you are looking for.
|request ? command.|