We've trialled MLPPP across multiple ADSL. We manage both CPE and LNS (take an L2TP service from ISP). Seems OK so far - but not yet got real world experience.
Elsewhere we have used the "multiple parallel link" solution when it was our only option. By default CEF switching is per session - so user will never see throughput greater on one session than the size of one of the links. Look into CEF per packet switching to get the full benefit. Dean Smith -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rick Kunkel Sent: 20 April 2007 17:49 To: [email protected] Subject: [c-nsp] Bonded DSL solution Hello all, We're looking into offering "bonded" DSL lines to customer who want more speed, but for whom something like a DS-3 is out of the question. I'm currently trying to figure out if Cisco has a solution for something like this. One thing I've considered, which isn't really true "bonding" is to have the customer have X DSL modems plugged into X ethernet ports on a router. I'll assign a different /30 address to each of their X ethernet ports, assign them a larger internal netblock, and then just create X static routes to that netblock. AFAIK, the traffic would round-robin between the different X circuits. And the customer would create X 0.0.0.0/0 routes pointing back to me. Sounds do-able. I think... right? The above seems a little low-tech though... Are there better ways to do it? Multi-link PPP? Some kind Cisco proprietary bonding protocol? The DSL lines all terminate in a Verizon ATM DS-3 plugged into a 7206VXR NPE-G1. Thanks! Rick Kunkel _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
