[cisco-nas] vpdn - wt-sss| SSS Circuit

[Matt Taber]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We saw this happen when the telco upgraded their DSLAMs and essentially
bricked a certain model of ADSL modem we had about 20 end-users using.

This was a few years ago, I think it was a problem w/ PPP negotiation.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matt Taber                 tabes at wmis.net
WMIS Internet         http://www.wmis.net
616-281-9647               1-888-482-9647
   "Accelerate ... It's a Speed Thing"
PGP:   http://www.wmis.net/pgp/0x3077CD7C
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


jc wrote:
> hi all,
> 
> could somebody please point me to some sort of documentation as to why
> incoming vpdn sessions onto a NPE-G1 would sometimes end up in the wt-sss
> state.
> 
> clns5-cj#sh vpdn | incl sss
> 30516 14    10678 SSS Circuit                        wt-sss 01:36:33 1621
> 30517 33    12593 SSS Circuit                        wt-sss 01:36:29 2128
> 30518 201   14508 SSS Circuit                        wt-sss 01:36:25 2544
> 30519 11    16423 SSS Circuit                        wt-sss 01:36:22 341
> 30521 51    20253 SSS Circuit                        wt-sss 01:24:34 64
> 30553 34    15997 SSS Circuit                        wt-sss 00:14:31 3274
> 
> clns5-cj#sh vpdn | incl 15997
> 15997 7919  rsaweb-honskn est    196.  1        1
> 30553 34    15997 SSS Circuit                        wt-sss 00:14:42 3274
> 
> from doing the google thing, it seems that this could be due to a non
> responsible radius server, which would be my next step in tracing the
> problem.
> 
> 
> j.
> 
> _______________________________________________
> cisco-nas mailing list
> cisco-nas at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHKHmYhqnZajB3zXwRAqupAJ9XzarZX1kQGNxaUm9E76yXVK+FowCffY03
PXMKhI206qoxacYxwRU3/Zc=
=0D0o
-----END PGP SIGNATURE-----