Hi Robert, Thanks for the questions.
I had hoped that the configurations I posted in the original message would shed light on how the users are connecting. I am pretty green at DSL configurations. My impression is that this is PPPoEoA because I am using the pppoe protocol on ATM interfaces. That sounds consistent with what you are saying, as there are also vpdn configurations on the head end router, PVCs are being utilized, and the clients appear to be dialing in (they have Dialers configured). But I might not have the terminology straight. I'll look into PPPoA and see whether we can support that over the underlying infastructure (Verizon DSL). Thanks for offering to share the PPPoA config. Looks like that might be the only alternative, if PPPoEoA is not supported. Thanks, Adam P.S. At the end of this message I have reposted the head-end / client configurations in case that helps at all .... ---- Original Message ----- From: "Robert Boyle" <[EMAIL PROTECTED]> To: "Adam Greene" <[EMAIL PROTECTED]>; <[email protected]> Sent: Saturday, October 06, 2007 10:40 PM Subject: Re: [c-nsp] activating MLP on ATM ADSL > At 05:42 PM 10/5/2007, Adam Greene wrote: >>I've been tasked with bonding some ATM ADSL links together into a >>multilink >>bundle. The objective is to enable customers to double their throughput by >>obtaining (2) DSL lines from us. >> >>The head end is a 7206 (NPE200) running C7200-IS-M 12.3(15b). The CPE end >>is >>a Cisco 1841 running (C1841-IPBASE-M) 12.4(1c). > > Adam, > > You don't mention how your DSL users are connecting. Are you using direct > PVCs? PPPoE? PPPoA? or PPPoEoA? It is not supported over PPPoEoA which is > where a range or single PVC terminates on a vpdn group. You must use > PPPoA. I wish PPPoEoA was supported, but it is not. We are working on a > good PPPoA config now. Once we have it, we will share it. > > -Robert > > Current configurations: ============= 7206 HEAD END ============= ! vpdn enable vpdn ip udp ignore checksum ! vpdn-group 1 accept-dialin protocol pppoe virtual-template 1 ip mtu adjust ! interface ATM1/0 bandwidth 44793 no ip address no ip redirects no ip mroute-cache logging event subif-link-status atm scrambling cell-payload no atm ilmi-keepalive ! interface ATM1/0.304 point-to-point ip unnumbered Loopback0 ip access-group VerizonDSLIn in ip access-group VerizonDSLOut out pvc 1/304 encapsulation aal5snap protocol pppoe ! interface ATM1/0.305 point-to-point ip unnumbered Loopback0 ip access-group VerizonDSLIn in ip access-group VerizonDSLOut out pvc 1/305 encapsulation aal5snap protocol pppoe ! interface Virtual-Template1 mtu 1492 ip unnumbered Loopback0 ip access-group VerizonDSLIn in ip access-group VerizonDSLOut out peer default ip address pool pppoe-pool ppp authentication pap ! ======== 1841 CPE ======== ! interface ATM0/0/0 no ip address no ip mroute-cache no atm ilmi-keepalive dsl operating-mode auto hold-queue 224 in pvc 0/35 encapsulation aal5snap pppoe-client dial-pool-number 1 ! ! interface ATM0/1/0 no ip address no ip mroute-cache no atm ilmi-keepalive dsl operating-mode auto hold-queue 224 in pvc 0/35 encapsulation aal5snap pppoe-client dial-pool-number 2 ! ! interface Dialer1 ip address negotiated ip mtu 1492 encapsulation ppp no ip mroute-cache dialer pool 1 dialer idle-timeout 0 dialer-group 1 ppp authentication pap callin ppp pap sent-username ***** password 7 ***** ! interface Dialer2 ip address negotiated ip mtu 1492 encapsulation ppp no ip mroute-cache dialer pool 2 dialer-group 2 ppp authentication pap callin ppp pap sent-username ***** password 7 ***** ! _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
