PPP link btwn L3 switches and ASA5520 L2L tunnel advise

Hello guys,

I have private PPP link between two sites connected to two L3 switches as routed port. Traffic between these two LANs is sailing smoothly via the PPP link bidirectional. I have also implemented IPSec VPN tunnel between the same two sites via the internet as backup in case the private link failed. In this case, the tunnel is working great.

When the PPP link restored on the L3 switch the LAN traffic continue to pass through the tunnel.

How do I configure the firewall or the switch to drop the IPSec tunnel when the PPP link restore?

The trick here is my internet ASA5520 firewall at both sites doesn’t know this route because it is part of the LAN. Can sla monitor and tracking with ACL will work? If so, any advice

Re: PPP link btwn L3 switches and ASA5520 L2L tunnel advise

P, Thank you very much for your lead and already looked into that link.My situation is bit different because both links are not physically connected to my firewall. I have one link from the firewall to ISP and other from the LAN switch to other location’s LAN switch. Just link trunking link but instead it is point-to-point with L3 subnet.

Re: PPP link btwn L3 switches and ASA5520 L2L tunnel advise

Hello Guys,

After testing various config I came accross my old references that I used to design MPLS private link. This tracking SLA policy config works great on L3 switch! Make sure the port that will be use on L3 switch is set to routed port instead of trunking betwn two locations. Use L3 subnet to create PPP link.

Re: PPP link btwn L3 switches and ASA5520 L2L tunnel advise

I just don't see the relevance of the PBR configured especially on the interface facing to the p2p link.

I think if you want to use PBR then would be better to configure on the port facing to your LAN and select the path based on the availability of next hop.

If your p2p goes down the static route should disappear from the routing table and the default route would kick in.

First I was thinking that your goal is to detect a stucked route due to up/up condition of the interface, but that is anyway done by the sla and removes the static route if no response received from 6.6.6.2

We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
view more

Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
view more

In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...
view more