THIAGO.MORAES at gvt
Feb 24, 2009, 4:23 PM
Post #1 of 1
(1998 views)
Permalink
|
|
RES: ERX terminate reason "lcp peer renegotiate rx confack"
|
|
Are you using L2TP services? I think LNS and LAC regarding of L2TP
environment. Anyway you must send that question to Juniper list(j-nsp),
Hug,
Thiago
-----Mensagem original-----
De: cisco-bba-bounces [at] puck
[mailto:cisco-bba-bounces [at] puck] Em nome de Oliver Boehmer
(oboehmer)
Enviada em: sexta-feira, 20 de fevereiro de 2009 05:33
Para: Victor Lyapunov; cisco-bba [at] puck
Assunto: Re: [cisco-bba] ERX terminate reason "lcp peer renegotiate rx
confack"
Victor Lyapunov <> wrote on Friday, February 20, 2009 09:05:
> Hello all
>
> I have a question regarding Juniper ERX routers, providing PPPoE
> service to broadband users.
> In the radius accounting files we see many PPPoE sessions with
> terminate-reason = "lcp peer
> renegotiate rx conf ack".
>
> Does anyone know what can cause a session to terminate so that the ERX
> generates this as a terminate reason?
well, this is a Cisco list (and I'm a Cisco employee), so I can only
speculate that the LCP options negotiated between client and LAC are not
compatible with the config on the LNS/ERX.. If this was a Cisco LNS, we
would require "lcp renegotiation [on-mismatch|always]" to be configured,
otherwise we would drop the session (much like the ERX?)..
But this is pure speculation :)
oli
_______________________________________________
cisco-bba mailing list
cisco-bba [at] puck
https://puck.nether.net/mailman/listinfo/cisco-bba
_______________________________________________
cisco-bba mailing list
cisco-bba [at] puck
https://puck.nether.net/mailman/listinfo/cisco-bba
|
