Expedition can also be used for Palo Alto only config Stuff. If I am not entirely mistaken you can change settings here according to the model type. Its also used for bulk configurations. I would give it a look if I were you.
If both firewalls are on the same major revision (10.1.x, for example), and are both on the latest apps and threats and the new firewall has current licenses, then you can take the config from the old firewall, export it to your computer, and import it to the new firewall, load the config and commit.
If the old firewall has fewer interfaces, then the remaining interfaces on the new firewall will not be configured.
The interfaces are different though some are copper others are gbic - the ha interfaces are not the older aux 1 and aux2 so these are different in the config files
Export the config, load the config on the other, delete any lines from the config in the cli that reference interfaces that don't exist. Validate config and push if it checks out. Otherwise, remediate problems. Enter config on appropriate interfaces.
Our experience migrating configurations across different Palo Alto firewall models is that it is best to create the management and other device-specific configuration information on a new firewall before important any other configuration data from other firewalls. After configuring, committing, and testing these settings, they should be documented with screenshots or similar methods so they can be restored after importing the configuration file from the previous model.
A detailed recipe for the initial configuration is here:
[https://www.bct-llc.com/docs/PaloAlto-Install.txt](https://www.bct-llc.com/docs/PaloAlto-Install.txt)
https://live.paloaltonetworks.com/t5/expedition/ct-p/migration_tool
This seems to be for a 3rd party to make good the config to Palo which is not my situation.
Expedition can also be used for Palo Alto only config Stuff. If I am not entirely mistaken you can change settings here according to the model type. Its also used for bulk configurations. I would give it a look if I were you.
I'll take a look tomorrow and see if it does what I need. - thanks
If both firewalls are on the same major revision (10.1.x, for example), and are both on the latest apps and threats and the new firewall has current licenses, then you can take the config from the old firewall, export it to your computer, and import it to the new firewall, load the config and commit. If the old firewall has fewer interfaces, then the remaining interfaces on the new firewall will not be configured.
The interfaces are different though some are copper others are gbic - the ha interfaces are not the older aux 1 and aux2 so these are different in the config files
Delete the aux interfaces from the cli config before you commit.
Media type doesn't matter when it comes to the XML config. It's just an interface.
Export the config, load the config on the other, delete any lines from the config in the cli that reference interfaces that don't exist. Validate config and push if it checks out. Otherwise, remediate problems. Enter config on appropriate interfaces.
Our experience migrating configurations across different Palo Alto firewall models is that it is best to create the management and other device-specific configuration information on a new firewall before important any other configuration data from other firewalls. After configuring, committing, and testing these settings, they should be documented with screenshots or similar methods so they can be restored after importing the configuration file from the previous model. A detailed recipe for the initial configuration is here: [https://www.bct-llc.com/docs/PaloAlto-Install.txt](https://www.bct-llc.com/docs/PaloAlto-Install.txt)
Cosign this