[c-nsp] Re: DSL aggregation on 122-25.S5

[Roger Weeks]

I'm not sure about multipoint, but I can speak from experience and  
tell you that in the 12.2(S) train of IOS, one thing is definitely  
broken that you may end up using with DSL aggregation:

range pvc

We were running our 7206 on 12.2.25(S) initially and we had quite a  
number of range pvc entries.  At some point I ran into a bug where I  
would enter a new range, and IOS would create all of the range as  
seperate sub-interfaces instead.

I opened a TAC case and was eventually told that although the 'range  
pvc' feature was there in the (S) train, it was "not supported".  I  
ended up going to 12.3T to get support for PVC ranges in RBE.

--
Roger J. Weeks
Systems & Network Administrator
Mendocino Community Network

On Jul 15, 2005, at 3:47 AM, cisco-nsp-request at puck.nether.net wrote:

> Message: 4
> Date: Fri, 15 Jul 2005 00:33:42 -0700
> From: Chris Cappuccio <chris at nmedia.net>
> Subject: Re: [c-nsp] DSL aggregation on 122-25.S5
> To: james edwards <hackerwacker at cybermesa.com>
> Cc: cisco-nsp at puck.nether.net
> Message-ID: <20050715073342.GR28407 at ref.nmedia.net>
> Content-Type: text/plain; charset=us-ascii
>
> None of what you're doing look like they would be broke in 12.2(18) 
> S or
> 12.2(14)S either.
>
> james edwards [hackerwacker at cybermesa.com] wrote:
>
>> I understand that DSL aggregation features are being added to the  
>> S train. I
>> would like to know
>> if current S train will support my DSL configs. I opened a case  
>> with TAC;
>> all they did is load my config
>> and tell me "It loads without error".  I was seeking a bit more  
>> guidance.
>>
>> Here are the DSL configs I use for DSL, is anyone doing DSL agg on  
>> S or can
>> someone from Cisco
>> comment on if my basic requirements for DSL agg are now supported  
>> by current
>> 12S ?
>> I am using Radius to provide auth (AAA) for the PPPoA.
>>
>> Multipoint, bridged and routed:
>>
>> !
>> interface ATM3/0.1 multipoint
>>  description xxxxx bridged customer connections
>>  no ip mroute-cache
>>  atm pvc 131 1 31 aal5snap
>>  atm pvc 134 1 34 aal5snap
>>  bridge-group 1
>>  bridge-group 1 spanning-disabled
>>
>> !
>> interface ATM3/0.2 multipoint
>>  description #1 xxxxx routed customer connections
>>  ip address 216.253.145.129 255.255.255.128
>>  no ip mroute-cache
>>  pvc 1/46
>>   protocol ip 216.253.145.133 no broadcast
>>
>>
>> PPPoA:
>>
>>
>> !
>> interface ATM4/0.32 point-to-point
>>  description xxxx DSL
>>  no ip mroute-cache
>>  pvc 1/32
>>   encapsulation aal5mux ppp Virtual-Template1
>>
>>
>> !
>> interface Virtual-Template1
>>  description xxxx_WAN1 DSL customers
>>  ip unnumbered Loopback1
>>  ip verify unicast source reachable-via rx allow-self-ping
>>  peer default ip address pool xxxxx_WAN1
>>  keepalive 15
>>  ppp authentication pap
>>
>>
>> Route-bride IP:
>>
>> !
>> interface ATM4/0.60 point-to-point
>>  description xxxx DSL
>>  ip unnumbered Loopback2
>>  no ip mroute-cache
>>  atm route-bridged ip
>>  atm arp-server self
>>  pvc 1/60
>>   encapsulation aal5snap
>>  !
>>  arp timeout 1200
>>
>> ip route 1.1.1.1 255.255.255.255 ATM4/0.60
>>
>>
>> James H. Edwards
>> Routing and Security Administrator
>> At the Santa Fe Office: Internet at Cyber Mesa
>> jamesh at cybermesa.com  noc at cybermesa.com
>> http://www.cybermesa.com/ContactCM
>> (505) 795-7101
>>
>> _______________________________________________
>> 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/
>