On Mon, November 19, 2007 8:37 pm, Sebastian Ganschow wrote: > We've got two scenarios: > > 1. The customer is connected with a 10 MBit/s LAN Extension and a 2 > Mbit/s D2MS. The 2 Mbit/s is connected with a Cisco 2600 Series router on > the customer side. But the LAN Extension is directly connected to a > switch. Our Backbone Router is the default router for the customer > network. Because of the costs we don't want to install another router on > the customer side. So BGP isn't working.
You could run HSRP between the backbone router on the primary link and the on-site router on the secondary link, which will work for the outbound. Inbound, you'd need to make sure you have link state forwarding on the LAN extension, so that if there's a fault on the site-to-PoP portion, or someone unplugs from the switch, the corresponding interface on the backbone router goes down and the connected route is withdrawn. Good luck on the second, I've yet to have this working reliably, and always look to run a dynamic routing protocol over 'Ethernet WAN' links. My preference would be to put something like an 1811 in - either instead of the switch, or as well as if you need to maintain a managed switch. It's not that expensive, and it'll handle 10Mb/s of normal traffic fine (ie probably not 10Mb/s of 64 byte packets with NAT and NBAR and QoS and ACLs and...) > 2. The customer is connected with a E3 or more and a 2 MBit/s SDSL. For > the E3 we've got a Cisco 2800 Series Router. But the SDSL Connection is > handled by a cisco 878 wich doesn't support BGP. 878 supports BGP fine. It can't hold a full table, but it'll certainly take a default via BGP (and probably your own customer routes, if that's needed). Regards, Tim. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
