An ISP rebooted their internal PPPOE Server and now a client's ASA is not able to get back L3 connectivity. L2 appears just fine. I've cycled the interface and the onsite people have rebooted the bridged ISP modem, but so far nothing is working to get this connection back online. Onsite techs plugged a laptop into the ISP modem and were able to get to the Intnernet.
Note this configuration is a little unusual in that it has two pppoe connections. The other one is working.
Thanks for your reply. Two pppoe connections the same ASA not load balancing not failover.
We were able to get the primary connection back in service. If you are interested in the details, please see SR 626031471 and the original setup SR 624947349.
Basically we had to remove the configuration for the secondary interface so that the first default route would get successfully instantiated again. Then we added the second interface route which was how this very unusal setup was done orignally.
When the problme occcurred both interfaces were up but sh vpdn pppinterface showed the secondary was id =1 and the primary was id = 2 and the primary needed to be number 1 otherwise the lower cost default route was missing. The only way to see that route was with sh asp table routing.
Do you use Cisco DNA Center? Have you used and are you willing to provide your feedback in using the Cisco DNA Center help and documentation?
If so, we’d like you to complete the survey linked below. Your feedback will help provide more effective and easi...
Listen: https://smarturl.it/CCRS9E18Follow us: https://twitter.com/CiscoChampion Reaching the height of your career is no simple feat. It often requires a combination of pursuing the right education, building the right professional network and being ...
In a typical production SD-WAN deployment, we would probably have many remote sites connected via many different Internet connections to a centralized data center or a regional hub. In most regions in the world, Internet providers will always use some typ...