| Symptom | Likely Cause | Solution |
|---------|--------------|----------|
| OVA import fails "Invalid OVF" | Corrupted download | Re-download the OVA and verify the checksum. |
| VM boots to black screen | Insufficient RAM | Allocate at least 4 GB RAM. |
| Cannot reach web UI on port 443 | Firewall or Expedition service down | From console: sudo systemctl status expedition; if stopped, sudo systemctl start expedition. |
| DHCP IP changes after reboot | No static IP configured | Follow Part 3 to set a static IP via netplan. |
| "Login failed" repeatedly | Forgotten password | From console: sudo passwd expedition to reset. |
| "502 Bad Gateway" on web UI | PostgreSQL not running | Console: sudo systemctl restart postgresql and sudo systemctl restart expedition. |
Palo Alto Networks Expedition is a free migration tool that helps organizations translate their existing firewall policies (from vendors like Cisco, Check Point, and Juniper) into Palo Alto Networks security policies. download palo alto expedition ova install
This guide outlines the steps to download the Open Virtualization Archive (OVA) file and deploy it on a supported hypervisor (VMware ESXi, Workstation, or Fusion). | Symptom | Likely Cause | Solution |
Console output scrolled, then stopped at a login prompt. Alex used the default credentials (expedition/expedition) from the docs. A quick ip addr showed DHCP had failed—so they set a static IP via nmtui. Palo Alto Networks Expedition is a free migration
On the vSphere client, Alex hit Deploy OVF Template, selected the local OVA file, and gave the VM a name: Expedition-Migrator. Default compute, storage, and disk provisioning (thin was fine). Network? A VLAN with access to both the legacy devices and the new Panorama/firewalls. Power on.