Mailing List Archive: strange dsl/pppoa disconnect

strange dsl/pppoa disconnect

Jun 30, 2003, 4:04 AM

Post #1 of 4 (3215 views)

The following are some debug logs from a dsl customer getting strange disconnects.

Although the acct record shows "lost-carrier" which i suppose means telco/copper problem,
i still can't understand the first line which shows a LCP incoming packet.

Any idea what might be happening?

Jun 30 01:00:20.893: Vi17 LCP: I CONFREQ [Open] id 1 len 4
Jun 30 01:00:20.893: Vi17 PPP: Terminating bound session
Jun 30 01:00:20.893: Vi17 PPP: Sending Acct Event[Reneg] id[AF3]
Jun 30 01:00:20.893: Vi17 IPCP: Remove link info for cef entry x.x.x.x
Jun 30 01:00:20.893: Vi17 IPCP: State is Closed
Jun 30 01:00:20.897: Vi17 PPP: Phase is TERMINATING
Jun 30 01:00:20.897: Vi17 LCP: State is Closed
Jun 30 01:00:20.897: Vi17 PPP: Phase is DOWN
Jun 30 01:00:20.897: RADIUS(00000AF3): Using existing nas_port 865
Jun 30 01:00:20.897: RADIUS(00000AF3): Config NAS IP: x.x.x.x
Jun 30 01:00:20.897: RADIUS(00000AF3): sending
Jun 30 01:00:20.897: Vi17 IPCP: Remove route to x.x.x.x
Jun 30 01:00:20.897: Vi17 VPDN: Reseting interface
..
...
Jun 30 01:00:20.897: RADIUS: Vendor, Cisco [26] 35
Jun 30 01:00:20.897: RADIUS: Cisco AVpair [1] 29 "connect-progress=LAN Ses Up"
Jun 30 01:00:20.897: RADIUS: Acct-Terminate-Cause[49] 6 lost-carrier [2]
Jun 30 01:00:20.897: RADIUS: Vendor, Cisco [26] 35
Jun 30 01:00:20.897: RADIUS: Cisco AVpair [1] 29 "disc-cause-ext=Lost Carrier"

PS: Router is a 7206 (12.3(1)) used as a LNS.

--
***********************************
Chatzithomaoglou Anastasios
Network Design & Operations Center
FORTHnet S.A.
<achatz@forthnet.gr>
***********************************

Re: strange dsl/pppoa disconnect [ In reply to ]

dpeng at cisco

Jul 1, 2003, 4:41 PM

Post #2 of 4 (3081 views)

Permalink

In 12.2(13)T and later, LCP renegotation was not being handled for
VPDN sessions. So like the case below, if we receive a LCP CONFREQ for
a sessions which is already up, that triggers a renegotiation and the
session would be dropped. The user should come back up on a different
VPDN session, but we recently fixed this so the user would renegotiate
without the VPDN session dropping and coming back up. The DDTS is
CSCeb30098 and it should be fixed in 12.2(3).

Dennis

Anastassios Chatzithomaoglou [achatz@forthnet.gr] wrote:
> The following are some debug logs from a dsl customer getting strange
> disconnects.
>
> Although the acct record shows "lost-carrier" which i suppose means
> telco/copper problem, i still can't understand the first line which shows a
> LCP incoming packet.
>
> Any idea what might be happening?
>
> Jun 30 01:00:20.893: Vi17 LCP: I CONFREQ [Open] id 1 len 4
> Jun 30 01:00:20.893: Vi17 PPP: Terminating bound session
> Jun 30 01:00:20.893: Vi17 PPP: Sending Acct Event[Reneg] id[AF3]
> Jun 30 01:00:20.893: Vi17 IPCP: Remove link info for cef entry x.x.x.x
> Jun 30 01:00:20.893: Vi17 IPCP: State is Closed
> Jun 30 01:00:20.897: Vi17 PPP: Phase is TERMINATING
> Jun 30 01:00:20.897: Vi17 LCP: State is Closed
> Jun 30 01:00:20.897: Vi17 PPP: Phase is DOWN
> Jun 30 01:00:20.897: RADIUS(00000AF3): Using existing nas_port 865
> Jun 30 01:00:20.897: RADIUS(00000AF3): Config NAS IP: x.x.x.x
> Jun 30 01:00:20.897: RADIUS(00000AF3): sending
> Jun 30 01:00:20.897: Vi17 IPCP: Remove route to x.x.x.x
> Jun 30 01:00:20.897: Vi17 VPDN: Reseting interface
> ..
> ...
> Jun 30 01:00:20.897: RADIUS: Vendor, Cisco [26] 35
> Jun 30 01:00:20.897: RADIUS: Cisco AVpair [1] 29
> "connect-progress=LAN Ses Up"
> Jun 30 01:00:20.897: RADIUS: Acct-Terminate-Cause[49] 6 lost-carrier
> [2]
> Jun 30 01:00:20.897: RADIUS: Vendor, Cisco [26] 35
> Jun 30 01:00:20.897: RADIUS: Cisco AVpair [1] 29
> "disc-cause-ext=Lost Carrier"
>
> PS: Router is a 7206 (12.3(1)) used as a LNS.
>
> --
> ***********************************
> Chatzithomaoglou Anastasios
> Network Design & Operations Center
> FORTHnet S.A.
> <achatz@forthnet.gr>
> ***********************************
>
>
> _______________________________________________
> cisco-bba mailing list
> cisco-bba@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-bba

--
-------------------------------------------------------------------------
|| || Dennis Peng
|| || Cisco Systems, Inc. Escalation Engineer
|||| |||| 170 West Tasman Drive Phone: (408) 526-6143
..:||||||:..:||||||:.. San Jose, CA 95134 Fax: (408) 232-2343
Cisco Systems Inc. dpeng@cisco.com
-------------------------------------------------------------------------

Re: strange dsl/pppoa disconnect [ In reply to ]

achatz at forthnet

Jul 4, 2003, 7:36 AM

Post #3 of 4 (3101 views)

Permalink

Dennis Peng wrote:

> In 12.2(13)T and later, LCP renegotation was not being handled for
> VPDN sessions. So like the case below, if we receive a LCP CONFREQ for
> a sessions which is already up, that triggers a renegotiation and the
> session would be dropped. The user should come back up on a different
> VPDN session, but we recently fixed this so the user would renegotiate
> without the VPDN session dropping and coming back up. The DDTS is
> CSCeb30098 and it should be fixed in 12.2(3).
>
Maybe you mean 12.3(2)? Because i'm already using 12.3(1) ;-)

> Dennis
>
> Anastassios Chatzithomaoglou [achatz@forthnet.gr] wrote:
>
>>The following are some debug logs from a dsl customer getting strange
>>disconnects.
>>
>>Although the acct record shows "lost-carrier" which i suppose means
>>telco/copper problem, i still can't understand the first line which shows a
>>LCP incoming packet.
>>
>>Any idea what might be happening?
>>
>>Jun 30 01:00:20.893: Vi17 LCP: I CONFREQ [Open] id 1 len 4
>>Jun 30 01:00:20.893: Vi17 PPP: Terminating bound session
>>Jun 30 01:00:20.893: Vi17 PPP: Sending Acct Event[Reneg] id[AF3]
>>Jun 30 01:00:20.893: Vi17 IPCP: Remove link info for cef entry x.x.x.x
>>Jun 30 01:00:20.893: Vi17 IPCP: State is Closed
>>Jun 30 01:00:20.897: Vi17 PPP: Phase is TERMINATING
>>Jun 30 01:00:20.897: Vi17 LCP: State is Closed
>>Jun 30 01:00:20.897: Vi17 PPP: Phase is DOWN
>>Jun 30 01:00:20.897: RADIUS(00000AF3): Using existing nas_port 865
>>Jun 30 01:00:20.897: RADIUS(00000AF3): Config NAS IP: x.x.x.x
>>Jun 30 01:00:20.897: RADIUS(00000AF3): sending
>>Jun 30 01:00:20.897: Vi17 IPCP: Remove route to x.x.x.x
>>Jun 30 01:00:20.897: Vi17 VPDN: Reseting interface
>>..
>>...
>>Jun 30 01:00:20.897: RADIUS: Vendor, Cisco [26] 35
>>Jun 30 01:00:20.897: RADIUS: Cisco AVpair [1] 29
>>"connect-progress=LAN Ses Up"
>>Jun 30 01:00:20.897: RADIUS: Acct-Terminate-Cause[49] 6 lost-carrier
>>[2]
>>Jun 30 01:00:20.897: RADIUS: Vendor, Cisco [26] 35
>>Jun 30 01:00:20.897: RADIUS: Cisco AVpair [1] 29
>>"disc-cause-ext=Lost Carrier"
>>
>>PS: Router is a 7206 (12.3(1)) used as a LNS.
>>
>>--
>>***********************************
>> Chatzithomaoglou Anastasios
>>Network Design & Operations Center
>> FORTHnet S.A.
>> <achatz@forthnet.gr>
>>***********************************
>>
>>
>>_______________________________________________
>>cisco-bba mailing list
>>cisco-bba@puck.nether.net
>>http://puck.nether.net/mailman/listinfo/cisco-bba
>
>

--
***********************************
Chatzithomaoglou Anastasios
Network Design & Operations Center
FORTHnet S.A.
<achatz@forthnet.gr>
***********************************

Re: strange dsl/pppoa disconnect [ In reply to ]

dpeng at cisco

Jul 9, 2003, 12:20 PM

Post #4 of 4 (3102 views)

Permalink

Anastassios Chatzithomaoglou [achatz@forthnet.gr] wrote:
>
>
> Dennis Peng wrote:
>
> >In 12.2(13)T and later, LCP renegotation was not being handled for
> >VPDN sessions. So like the case below, if we receive a LCP CONFREQ for
> >a sessions which is already up, that triggers a renegotiation and the
> >session would be dropped. The user should come back up on a different
> >VPDN session, but we recently fixed this so the user would renegotiate
> >without the VPDN session dropping and coming back up. The DDTS is
> >CSCeb30098 and it should be fixed in 12.2(3).
> >
> Maybe you mean 12.3(2)? Because i'm already using 12.3(1) ;-)

Oops, that was a typo. It should be 12.3(3). :)

Dennis

> >Dennis
> >
> >Anastassios Chatzithomaoglou [achatz@forthnet.gr] wrote:
> >
> >>The following are some debug logs from a dsl customer getting strange
> >>disconnects.
> >>
> >>Although the acct record shows "lost-carrier" which i suppose means
> >>telco/copper problem, i still can't understand the first line which shows
> >>a LCP incoming packet.
> >>
> >>Any idea what might be happening?
> >>
> >>Jun 30 01:00:20.893: Vi17 LCP: I CONFREQ [Open] id 1 len 4
> >>Jun 30 01:00:20.893: Vi17 PPP: Terminating bound session
> >>Jun 30 01:00:20.893: Vi17 PPP: Sending Acct Event[Reneg] id[AF3]
> >>Jun 30 01:00:20.893: Vi17 IPCP: Remove link info for cef entry x.x.x.x
> >>Jun 30 01:00:20.893: Vi17 IPCP: State is Closed
> >>Jun 30 01:00:20.897: Vi17 PPP: Phase is TERMINATING
> >>Jun 30 01:00:20.897: Vi17 LCP: State is Closed
> >>Jun 30 01:00:20.897: Vi17 PPP: Phase is DOWN
> >>Jun 30 01:00:20.897: RADIUS(00000AF3): Using existing nas_port 865
> >>Jun 30 01:00:20.897: RADIUS(00000AF3): Config NAS IP: x.x.x.x
> >>Jun 30 01:00:20.897: RADIUS(00000AF3): sending
> >>Jun 30 01:00:20.897: Vi17 IPCP: Remove route to x.x.x.x
> >>Jun 30 01:00:20.897: Vi17 VPDN: Reseting interface
> >>..
> >>...
> >>Jun 30 01:00:20.897: RADIUS: Vendor, Cisco [26] 35
> >>Jun 30 01:00:20.897: RADIUS: Cisco AVpair [1] 29
> >>"connect-progress=LAN Ses Up"
> >>Jun 30 01:00:20.897: RADIUS: Acct-Terminate-Cause[49] 6 lost-carrier
> >>[2]
> >>Jun 30 01:00:20.897: RADIUS: Vendor, Cisco [26] 35
> >>Jun 30 01:00:20.897: RADIUS: Cisco AVpair [1] 29
> >>"disc-cause-ext=Lost Carrier"
> >>
> >>PS: Router is a 7206 (12.3(1)) used as a LNS.
> >>
> >>--
> >>***********************************
> >> Chatzithomaoglou Anastasios
> >>Network Design & Operations Center
> >> FORTHnet S.A.
> >> <achatz@forthnet.gr>
> >>***********************************
> >>
> >>
> >>_______________________________________________
> >>cisco-bba mailing list
> >>cisco-bba@puck.nether.net
> >>http://puck.nether.net/mailman/listinfo/cisco-bba
> >
> >
>
> --
> ***********************************
> Chatzithomaoglou Anastasios
> Network Design & Operations Center
> FORTHnet S.A.
> <achatz@forthnet.gr>
> ***********************************