Mailing List Archive: Cisco: NAS

vpdn & radius attribute connect-info

Index | Next | Previous | View Threaded

achatz at forthnet

Jan 16, 2006, 3:14 AM

Post #1 of 5 (2359 views)
Permalink

vpdn & radius attribute connect-info

LAC#sh line 9
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int
A 9 TTY - DialIn - - 112 161 0 0/0 -

Line 9, Location: "", Type: ""
Length: 24 lines, Width: 80 columns
Status: Ready, Active, No Exit Banner, Async Interface Active
HW PPP Support Active, Modem Detected, CTS Raised
Capabilities: No Flush-at-Activation, Hardware Flowcontrol In
Hardware Flowcontrol Out, Modem RI is CD, Line usable as async interface
Modem Autoconfigure, Integrated Modem
Modem state: Ready
modem(slot/port)=1/8, state=CONNECTED

The Tx/Rx do not display anything here.

LAC#sh aaa user 135329
Unique id 135329 is currently in use.
Accounting:
log=0x208241
Events recorded :
CALL START
ATTR REPLACE
NET UP
INTERIM START
VPDN NET UP
update method(s) :
NONE
update interval = 0
Outstanding Stop Records : 0
Dynamic attribute list:
639C6550 0 00000001 connect-progress(30) 4 10
639C6564 0 00000001 pre-session-time(237) 4 23(17)
639C6578 0 00000001 elapsed_time(294) 4 233(E9)
639C658C 0 00000001 bytes_in(95) 4 71329(116A1)
639C65A0 0 00000001 bytes_out(221) 4 670875(A3C9B)
639C65B4 0 00000001 pre-bytes-in(233) 4 191(BF)
639C65C8 0 00000001 pre-bytes-out(234) 4 63(3F)
639C65DC 0 00000001 paks_in(96) 4 842(34A)
639C65F0 0 00000001 paks_out(222) 4 1298(512)
639C6604 0 00000001 pre-paks-in(235) 4 6(6)
63B14F08 0 00000001 pre-paks-out(236) 4 3(3)
No data for type EXEC
No data for type CONN
NET: Username=XXX
Session Id=0002B2C6 Unique Id=000210A1
Start Sent=1 Stop Only=N
stop_has_been_sent=N
Method List=62B52290 : Name = RADIUS-AAA
Attribute list:
63B14F08 0 00000001 session-id(291) 4 176838(2B2C6)
63B14F1C 0 00000001 start_time(296) 4 Jan 16 2006 12:53:02
63B14F30 0 00000001 Framed-Protocol(60) 4 1
63B14F44 0 00000009 tunnel-client-endpoint(303) 15 X.X.X.X
63B14F58 0 00000009 tunnel-server-endpoint(309) 15 X.X.X.X
63B14F6C 0 00000009 vpdn-group(321) 10 XXX
63B14F80 0 00000001 tunnel-type(314) 4 2
63B14F94 0 00000009 tunnel-connection-id(310) 10 3614144712
63B14FA8 0 00000009 tunnel-id(304) 10 XXX
63B14FBC 0 00000009 gw-name(305) 8 XXX
No data for type CMD
No data for type SYSTEM
No data for type RM CALL
No data for type RM VPDN
No data for type AUTH PROXY
No data for type IPSEC-TUNNEL
No data for type RESOURCE
No data for type 10
No data for type CALL
Debg: No data available
Radi: 63066238
Interface:
TTY Num = 9
IDB Name = Async9
Parent IDB Name = Serial3:16
Stop Received = 0
Byte/Packet Counts till Call Start:
Start Bytes In = 277999276 Start Bytes Out = 1227616859
Start Paks In = 1974626 Start Paks Out = 1694417
Byte/Packet Counts till Service Up:
Pre Bytes In = 277999467 Pre Bytes Out = 1227616922
Pre Paks In = 1974632 Pre Paks Out = 1694420
Cumulatvie Byte/Packet Counts :
Bytes In = 278070796 Bytes Out = 1228287797
Paks In = 1975474 Paks Out = 1695718
StartTime = 12:53:02 EET Jan 16 2006
AuthenTime = 12:53:25 EET Jan 16 2006
Component = PPP
Authen: service=LOGIN type=ASCII method=RADIUS
Kerb: No data available
Meth: No data available
Preauth: No Preauth data.
General:
Unique Id = 000210A1
TACACS+ IP Address = X.X.X.X
Session Id = 0002B2C6
Attribute List:
635F4E04 0 00000009 clid(25) 10 XXX
635F4E18 0 00000009 dnis(36) 10 XXX
635F4E2C 0 00000001 port-type(154) 4 4
635F4E40 0 00000009 interface(150) 6 Async9
635F4E54 0 00000009 parent-interface(152) 10 Serial3:16
63ABD34C 0 00000001 parent-interface-type(153) 4 1
63ABD360 0 00000009 nas-connect-info(22) 27 52000/26400 V90/V42bis/LAPM
PerU: No data available

The "nas-connect-info" attribute contains the correct modem speed.

LNS#sh aaa user 2010495
Unique id 2010495 is currently in use.
Accounting:
log=0x208261
Events recorded :
CALL START
ATTR ADD
ATTR REPLACE
NET UP
INTERIM START
VPDN NET UP
update method(s) :
NONE
update interval = 0
Outstanding Stop Records : 0
Dynamic attribute list:
6393823C 0 00000001 connect-progress(30) 4 Call Up
63938250 0 00000001 pre-session-time(239) 4 1(1)
63938264 0 00000001 nas-tx-speed(337) 4 115000(1C138)
63938278 0 00000001 nas-rx-speed(33) 4 115000(1C138)
6393828C 0 00000001 elapsed_time(296) 4 946(3B2)
639382A0 0 00000001 bytes_in(97) 4 275876(435A4)
639382B4 0 00000001 bytes_out(223) 4 1775914(1B192A)
639382C8 0 00000001 pre-bytes-in(235) 4 0(0)
639382DC 0 00000001 pre-bytes-out(236) 4 90(5A)
639382F0 0 00000001 paks_in(98) 4 2523(9DB)
63B024E0 0 00000001 paks_out(224) 4 3408(D50)
63B024F4 0 00000001 pre-paks-in(237) 4 0(0)
63B02508 0 00000001 pre-paks-out(238) 4 3(3)
No data for type EXEC
No data for type CONN
NET: Username=XXX
Session Id=00342365 Unique Id=001EAD7F
Start Sent=1 Stop Only=N
stop_has_been_sent=N
Method List=632EDD2C : Name = default
Attribute list:
6393823C 0 00000001 session-id(293) 4 3416933(342365)
63938250 0 00000001 start_time(298) 4 Jan 16 2006 12:53:25
63938264 0 00000009 tunnel-server-endpoint(311) 15 X.X.X.X
63938278 0 00000009 tunnel-client-endpoint(305) 15 X.X.X.X
6393828C 0 00000009 vpdn-group(324) 11 XXX
639382A0 0 00000001 tunnel-type(316) 4 l2tp
639382B4 0 00000009 tunnel-connection-id(312) 10 3614144712
639382C8 0 00000009 tunnel-id(306) 10 XXX
639382DC 0 00000009 gw-name(307) 8 XXX
639382F0 0 00000001 Framed-Protocol(62) 4 PPP
63B024E0 0 00000009 tunnel-client-endpoint(305) 15 X.X.X.X
63B024F4 0 00000009 tunnel-server-endpoint(311) 15 X.X.X.X
63B02508 0 00000009 vpdn-group(324) 9 XXX
63B0251C 0 00000001 tunnel-type(316) 4 l2tp
63B02530 0 00000009 tunnel-connection-id(312) 9 965033538
63B02544 0 00000009 tunnel-id(306) 7 XXX
63B02558 0 00000009 gw-name(307) 5 XXX
No data for type CMD
No data for type SYSTEM
No data for type RM CALL
No data for type RM VPDN
No data for type AUTH PROXY
No data for type IPSEC-TUNNEL
No data for type RESOURCE
No data for type 10
No data for type CALL
Debg: No data available
Radi: No data available
Interface:
TTY Num = -1
Stop Received = 0
Byte/Packet Counts till Call Start:
Start Bytes In = 0 Start Bytes Out = 0
Start Paks In = 0 Start Paks Out = 0
Byte/Packet Counts till Service Up:
Pre Bytes In = 0 Pre Bytes Out = 90
Pre Paks In = 0 Pre Paks Out = 3
Cumulative Byte/Packet Counts :
Bytes In = 275876 Bytes Out = 1776004
Paks In = 2523 Paks Out = 3411
StartTime = 12:53:25 EET Jan 16 2006
AuthenTime = 12:53:26 EET Jan 16 2006
Component = VPDN
Authen: service=NONE type=NONE method=NONE
Kerb: No data available
Meth: No data available
Preauth: No Preauth data.
General:
Unique Id = 001EAD7F
TACACS+ IP Address = X.X.X.X
NAS IP Address = X.X.X.X
Session Id = 00342365
Attribute List:
6393823C 0 00000001 port-type(156) 4 Async
63938250 0 00000009 interface(152) 6 Async9
63938264 0 00000009 clid(25) 10 XXX
63938278 0 00000009 dnis(36) 10 XXX
PerU: No data available

Right now we're getting nas-tx-speed & nas-rx-speed equal to 115000 if we look at the aaa records on
the LNS, which is the same as the default BW description of the physical interface (group-async) on
the LAC.

So we need to find a way to forward the correct modem speed from the LAC to the LNS, like some other
attributes (port-type, interface, clid, dnis) are forwarded.
Is there a way we can "forward" the connect-info (or nas-connect-info?) attribute from a LAC
(AS5300) to a LNS (7200)?
Is there any difference if the LNS is actually a middle LNS/LAC in a vpdn multihop scenario?

Tassos

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

oboehmer at cisco

Jan 16, 2006, 3:46 AM

Post #2 of 5 (2253 views)
Permalink

RE: vpdn & radius attribute connect-info [In reply to]

> Right now we're getting nas-tx-speed & nas-rx-speed equal to 115000
> if we look at the aaa records on the LNS, which is the same as the
> default BW description of the physical interface (group-async) on the
> LAC.
>
> So we need to find a way to forward the correct modem speed from the
> LAC to the LNS, like some other attributes (port-type, interface,
> clid, dnis) are forwarded.
> Is there a way we can "forward" the connect-info (or
> nas-connect-info?) attribute from a LAC (AS5300) to a LNS (7200)?
> Is there any difference if the LNS is actually a middle LNS/LAC in a
> vpdn multihop scenario?

which IOS do you run on the LAC? Can you try an image with
CSCea74569/CSCdm62874 fixed (i.e. 12.3(10) or later)

Can you try to configure
modem poll time 2
modem poll retry 4
on the LAC to see if it makes a difference? "modem link-info poll time
6553" has also been reported to help..

oli

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

achatz at forthnet

Jan 16, 2006, 4:10 AM

Post #3 of 5 (2266 views)
Permalink

Re: vpdn & radius attribute connect-info [In reply to]

Hi Oli,

Oliver Boehmer (oboehmer) wrote on 16/1/2006 1:46 μμ:

>
>>Right now we're getting nas-tx-speed & nas-rx-speed equal to 115000
>>if we look at the aaa records on the LNS, which is the same as the
>>default BW description of the physical interface (group-async) on the
>>LAC.
>>
>>So we need to find a way to forward the correct modem speed from the
>>LAC to the LNS, like some other attributes (port-type, interface,
>>clid, dnis) are forwarded.
>>Is there a way we can "forward" the connect-info (or
>>nas-connect-info?) attribute from a LAC (AS5300) to a LNS (7200)?
>>Is there any difference if the LNS is actually a middle LNS/LAC in a
>>vpdn multihop scenario?
>
>
> which IOS do you run on the LAC? Can you try an image with
> CSCea74569/CSCdm62874 fixed (i.e. 12.3(10) or later)
>

We're running 12.2(15)T16 on the AS5300. Is there a problem with this version?

> Can you try to configure
> modem poll time 2
> modem poll retry 4

I tried configuring the above two but they do not show up in config.
I also tried to change the numbers (in case they were the default ones) but they still do not show up.

> on the LAC to see if it makes a difference? "modem link-info poll time
> 6553" has also been reported to help..
>
I guess you mean 65535 here, because 6553 as a number seems quite strange.
I configured it (this one appears in config), but it doesn't make any difference.

Tassos

> oli
_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

oboehmer at cisco

Jan 16, 2006, 4:17 AM

Post #4 of 5 (2259 views)
Permalink

RE: vpdn & radius attribute connect-info [In reply to]

Tassos Chatzithomaoglou <mailto:achatz [at] forthnet> wrote on Monday, January 16, 2006 1:11 PM:

> Hi Oli,
>
>
> Oliver Boehmer (oboehmer) wrote on 16/1/2006 1:46 ��:
>
>>
>>> Right now we're getting nas-tx-speed & nas-rx-speed equal to 115000
>>> if we look at the aaa records on the LNS, which is the same as the
>>> default BW description of the physical interface (group-async) on
>>> the LAC.
>>>
>>> So we need to find a way to forward the correct modem speed from the
>>> LAC to the LNS, like some other attributes (port-type, interface,
>>> clid, dnis) are forwarded. Is there a way we can "forward" the
>>> connect-info (or nas-connect-info?) attribute from a LAC (AS5300)
>>> to a LNS (7200)?
>>> Is there any difference if the LNS is actually a middle LNS/LAC in a
>>> vpdn multihop scenario?
>>
>>
>> which IOS do you run on the LAC? Can you try an image with
>> CSCea74569/CSCdm62874 fixed (i.e. 12.3(10) or later)
>>
>
> We're running 12.2(15)T16 on the AS5300. Is there a problem with this
> version?

yes, it doesn't have the fix for CSCea74569. please use a more recent 12.3M, like 12.3(17a) and try again since the workarounds didn't work (and yes, I meant 65535)

oli

_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

achatz at forthnet

Feb 14, 2006, 7:21 AM

Post #5 of 5 (2200 views)
Permalink

Re: vpdn & radius attribute connect-info [In reply to]

As correctly noted by Oli, 12.3(17a) seems to solve our problem, but we fell into another 2 bugs
(CSCej89068, CSCsa93526), so we gonna wait until we have them solved too.

Thanks for all your help Oli.

Oliver Boehmer (oboehmer) wrote on 16/1/2006 14:17:
> Tassos Chatzithomaoglou <mailto:achatz [at] forthnet> wrote on Monday, January 16, 2006 1:11 PM:
>
>
>>Hi Oli,
>>
>>
>>Oliver Boehmer (oboehmer) wrote on 16/1/2006 1:46 ��:
>>
>>
>>>>Right now we're getting nas-tx-speed & nas-rx-speed equal to 115000
>>>>if we look at the aaa records on the LNS, which is the same as the
>>>>default BW description of the physical interface (group-async) on
>>>>the LAC.
>>>>
>>>>So we need to find a way to forward the correct modem speed from the
>>>>LAC to the LNS, like some other attributes (port-type, interface,
>>>>clid, dnis) are forwarded. Is there a way we can "forward" the
>>>>connect-info (or nas-connect-info?) attribute from a LAC (AS5300)
>>>>to a LNS (7200)?
>>>>Is there any difference if the LNS is actually a middle LNS/LAC in a
>>>>vpdn multihop scenario?
>>>
>>>
>>>which IOS do you run on the LAC? Can you try an image with
>>>CSCea74569/CSCdm62874 fixed (i.e. 12.3(10) or later)
>>>
>>
>>We're running 12.2(15)T16 on the AS5300. Is there a problem with this
>>version?
>
>
> yes, it doesn't have the fix for CSCea74569. please use a more recent 12.3M, like 12.3(17a) and try again since the workarounds didn't work (and yes, I meant 65535)
>
> oli
>

--
***************************************
Tassos Chatzithomaoglou
Network Design & Development Department
FORTHnet S.A.
<achatz [at] forthnet>
***************************************
_______________________________________________
cisco-nas mailing list
cisco-nas [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nas

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads