05-28-2015 03:44 PM - edited 03-11-2019 11:00 PM
Hi,
Recently my company bought a new Internet channel and I wan't to route some of our internals IP segments to this new ISP. I checked that with PBR this could work, so, I configured, the ACL, the route-map and actually is applied to the private interface, but the traffic is not being routed to the new ISP.
I think is caused for something I missed in the NAT configuration. Maybe you can help me with a recent example of this scenario? I searched but only found obsolete commands.
Thank you,
Solved! Go to Solution.
05-30-2015 04:23 AM
Hi,
I think it would be better if you can share the configuration which did not work. I think the NAT should use the Egress interface as per the routing requirement.
Refer this for more information on the PBR:-
http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/configuration/general/asa-general-cli/route-policy-based.html
Thanks and Regards,
Vibhor Amrodia
05-30-2015 04:23 AM
Hi,
I think it would be better if you can share the configuration which did not work. I think the NAT should use the Egress interface as per the routing requirement.
Refer this for more information on the PBR:-
http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/configuration/general/asa-general-cli/route-policy-based.html
Thanks and Regards,
Vibhor Amrodia
06-01-2015 02:19 PM
The problem was that I was using standard ACL and PBR doesn't work but with extended ACLs.
Thank you.
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