[nsp] Keepalive - Port error

[Dennis Peng]

A RADIUS disconnect cause of "Port-Error" means that we stopped
receiving responses to our keepalives. It usually is an indication
that the CPE has gone away (say a customer powered down their DSL
modem) or that traffic has temporarily stopped passing through to the
CPE (maybe a network problem between the LNS and the LAC).

Before you see the "Missed 5 keepalives" message, you'll see an
"echo_cnt X" debug where X is the number of consecutive keepalives we
have missed (we won't print the debug unless X >= 2). When you see
these message, immediately try and ping the user. If that fails, ping
the LAC and make sure connectivity is up. Then try and ping another
user who is on the same LAC (inside the same L2TP tunnel) and see if
they respond. If the first test fails and the second two succeed, then
most likely the user has powered off their CPE device and you
shouldn't worry about it.

Dennis

Mark [netw2004 at hotmail.com] wrote:
> Hi there!!!
> 
> 
>                 I?m having a little problem since I upgraded from  NPE-400 to NPE-G1 on a 7204VXR. We have an L2tp tunnel and lots of sessions coming through it. I have noticed some sessions disconnections. The termination cause on the radius accounting messages is "port-error" and this is what I get when I run a debug:
> 
> sh debugging 
> PPP:
>   PPP protocol errors debugging is on
> 
> 
> Jan 21 07:30:35: Vi2.390 PPP: Missed 5 keepalives, taking LCP down
> Jan 21 07:32:26: Vi2.387 PPP: Missed 5 keepalives, taking LCP down
> 
> I have tried increasing the keepalive period an retry number but without success.
> Hope someone can help me.
> 
> Thanks in advance!
> 
> Mark
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/