[cisco-nas] vpdn & radius attribute connect-info

[Tassos Chatzithomaoglou]

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.gr> 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.gr>
***************************************