03-06-2020 09:15 AM - edited 03-06-2020 09:16 AM
Hi Guys,
We are migrating our DC firewalls from ASA to the Palo Alto. We will be moving the whole configuration to the PA except the SSL Client VPN.
We want to use the ASA just for AnyConnect and rest all functionality should be there on PA. Since all firewalls in our environment are ASA's and we'll be migrating to PA phase-wise hence our plan is to keep AnyConnect at all the locations including this one till full migration.
Can someone help me with how this can be done?
Thanks
03-06-2020 09:36 AM
you can leave the VPN based config as in to ASA and migrate rest.
But you need to re-IP for Palo external side IP, since ASA already using same IP address.
Other than that you can build the configuration on Palo and deploy along with ASA in the network.
03-06-2020 09:51 AM
03-07-2020 03:04 AM
Create a DMZ interface on the Palo Alto where you connect the ASA - either directly or via a switch with a DMZ VLAN. Create a NAT rule for the ASA's outside interface to a public address on the Palo Alto outside interface - it could even be the same address formerly used as by the ASA. Create an ACL entry on the Palo Alto allowing incoming https traffic to the ASA to service the SSL VPN users.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide