PPPOE L3 down after ISP reboots

lcaruso · ‎05-20-2013

Hi,

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.

Any suggestions would be appreciated.

Thanks.

Subeh Sharma · ‎05-21-2013

Hi,

1. pls describe the topology.

2. Are both the PPPoE connected to the same ASA.

3. Is ASA terminating the PPP connection or the ISP modem? i.e. Do you have any PPP configus on the ASA or on the ISP modem?

4. Have you run some debugs on ASA?

Regards,

Subeh

lcaruso · ‎05-21-2013

Hi,

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.