[c-nsp] vpdn aaa attribute nas-port vpdn-nas

[Szilard Matyas]

Hello Dennis!

Now I use 123-5ab2 for the LNS(npe-g1).

This release is sending the attribute 77 connectinfo, but in it there
is something other that I expected.

Send this for modem call : Connect-Info = "115000"
Send this for ISDN, and for Multilink ISDN call : Connect-Info = "64000"

I would like something like this for modem:  Connect-Info
="48000/28800 ......."  I would like to see minimum the rx,tx speed
that it gets from the LAC.
thanks,

szicsu



Thursday, October 21, 2004, 5:46:26 PM, you wrote:

DP> Szilard Matyas [szilard.matyas at enternet.hu] wrote:
>> hello Oliver,
>> 
>> Thanks for your answer. It's an amazing feature of the 12.3T :)
>> On the LNS I see all the AVPs. I also see AVP 24=tx_speed, AVP 38=rx_speed.
>> But I can't put these into the accounting record sent to radius by the LNS. Whichever

DP> There is a bug associated with this, CSCeg06355, in 12.2T and 12.3
DP> mainline. The problem doesn't affect 12.3B or 12.3(4)T or later
DP> because we added support for sending the connection speed in attribute
DP> 77 (Connect-Info). Previously we sent the speed in Cisco-AVPair's.

DP> Dennis

>> way I change the accounting format with the "radius-server attribute
>> nas-port format"  comand, it does not appear in the accounting
>> record. I use "aaa nas extended" and "radius-server vsa send
>> accounting". Now the lns is as5350 with 12.2.15T14
>> 
>> thanks
>> regards,
>> szicsu
>> 
>> 
>> 
>> Thursday, October 21, 2004, 2:49:06 PM, you wrote:
>> 
>> OBo> Hi,
>> 
>> >> cisco say this:
>> >> 
>> >> "vpdn aaa attribute nas-port vpdn-nas
>> >> To enable the L2TP network server (LNS) to send PPP extended NAS-Port
>> >> format values from the L2TP access concentrator (LAC) 
>> >> to the RADIUS server for accounting, use the vpdn aaa attribute
>> >> nas-port vpdn-nas global configuration command"
>> >> 
>> >> It's working, the npe-g1(LNS) sends dialup infos in accounting
>> >> packets like 
>> >> 
>> >> NAS-Port-Type = Async
>> >> Cisco-NAS-Port = "Async2/27"
>> >> Calling-Station-Id = "123456"
>> >> Called-Station-Id = "123456"
>> >> and so on.
>> >> 
>> 
>> >> I can't understand how this information is put to the LNS from the
>> >> LAC. I supposed that the LAC sends this information in L2TP ICRQ or
>> >> ICCN with the standard L2TP AV-PAIRs. But I can't see any kind of AVP
>> >> relating these. I see only the mandatory AVPs.
>> OBo> [...]
>> >> Is there anybody know how LAC send nas-port,clid,dnis information to
>> >> the LNS ? 
>> 
>> OBo> Please take a look at "deb vpdn l2x-packets" at the LNS, we don't decode
>> OBo> the AVPs in the LAC's debug (this was recently added to 12.3T). On the
>> OBo> LNS, you will see
>> 
>> OBo> Tnl41382 L2TP: Parse ICRQ
>> OBo> [...]
>> OBo> Tnl41382 L2TP: Parse  AVP 22, len 16, flag 0x8000 (M)
>> OBo> Tnl41382 L2TP: Calling Number 123456789
>> OBo> Tnl41382 L2TP: Parse  AVP 21, len 8, flag 0x8000 (M)
>> OBo> Tnl41382 L2TP: Called Number 987654321
>> OBo> Tnl41382 L2TP: Parse Cisco AVP 100, len 13, flag 0x0 
>> OBo> Tnl41382 L2TP: Client NAS Port  
>> OBo>          41 73 79 6E 63 31 36
>> OBo> Tnl41382 L2TP: No missing AVPs in ICRQ
>> 
>> >> And how can the LAC send connectinfo(rx,tx) attribute to the LNS? if
>> >> it can.
>> 
>> OBo> AVP 24 and 38, see RFC2661..
>> 
>> OBo> 	oli
>> 
>> _______________________________________________
>> 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/