Hi, you're welcome.
As far as import of configurations between platforms goes, things that get broken are interface mismatches and any configuration dependant on those interfaces (for example, what might break down.... GP portals or VPN tunnels, perhaps communication with some servers that had data interfaces set up, NAT, service routes).
Once I got new devices, I would test import; if I experience too many breakdowns I would consider either manually configuring rest on the new device, or changing dependant part of the configuration on the old platform to correspond to the interfaces existing on a new platform and than importing again. If discrepancy is too high, you might consider re-designing your network. For what it's worth, you will see full list of whatever is broken when you attempt to import configuration, so you will be able to copy that output and work on the configurations to fix it.
My colleague today correctly pointed my attention to the fact that you could just set up HA once you are sure new active device is set up. This is correct, and expected and "more" proper way to do it, rather than dumping device state. Not that anything would be wrong with device state import; only difference is - you need to set up those passive/secondary device details (hostname, management IP address, HA details at least) prior to setting up and pushing configuration - and if you were importing dumped state you would change them after the import.
Regardless of your production setting of the feature, I might avoid using pre-emption until I am sure of my cluster behaving as expected - just to be sure there aren't any unexpected failovers while you are setting everything up.
Good luck, and as I said - if needed, you always have additional resources in SE and TAC.
Best regards,
Luciano
... View more