[nsp] Virtual Interface Question

[Dennis Peng]

Based on the "description: line, I assume you are doing PPPoE. If the
PPPoE connection is not torn down properly, that session will remain
up until an upper layer detects that the session has gone away and
tears down the connection. Usually the mechanism to do this is PPP
keepalives, but you have it disabled. You should re-enable it for
exactly the problem you describe. For PPPoA, this shouldn't be a
problem in your version since there is a static binding between the
PVC and the vaccess. When the session comes back up, the same
virtual-access will be re-used.

Dennis

Carl Jagerski [carll at forcomm.net] wrote:
> 
> Hi Everyone,
>     I have a 7206 router running 12.2(13a).  I am connecting and 
> authenticating DSL through an ATM interface.  I have the following Virtual 
> Template setup for these DSL customers.
> 
> interface Virtual-Template2
>  description pppoe
>  mtu 1492
>  ip unnumbered FastEthernet0/0
>  no keepalive
>  peer default ip address pool dsl1
>  ppp authentication pap
> 
> Everything works fine except when connections are abnormally droped from 
> customer end (reboot, power failure etc.), the Virtual Interface stays 
> active.  If static IP's are assigned to customers, routing continues to the 
> stuck interface and the new one created when they connect back in is not 
> routed.  How can I automatically clear virtual interfaces when they are no 
> longer being used.
> 
> TIA
> 
> 
> Carl Jagerski
> Network Administrator, Forward Communications
> carll at forcomm.net
> 724-378-4490 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/