I kinda got off track and did not register the "simpliest way." If they have a GSR hanging around with a T1 card/BRI card on a 2600 or 3600 then sure why not :) The post was meant to show ways to 1) have true packet by packet load balancing to minimize slow/fast scenarios or 2) providing more traffic to the bigger pipe. Of course one would want to see what their traffic patterns are before implementing this (forgot to mention this as well.) KISS... Right... Kelly ----- Original Message ----- From: "Nate Van Maren" To: Sent: Sunday, June 03, 2001 8:30 PM Subject: Re: How to configure 1601 to load balance 2 Internet circuits [7:7018] > Wouldn't it make more sense to do CEF packet-by-packet? (a lot less load on > the router than process switching), If you wanted it to do it at all... > > It would kind of scare me to turn in on in this case because there is a > GREAT chance of packets arriving out of order (the ones that go out the fast > connection would arrive sooner)... Session-by-session would seem to fit a > little better when the links are so varied in bandwidth. > > http://www.cisco.com/univercd/cc/td/doc/product/software/ios112/ios112p/gsr/ > cef.htm#xtocid2626427 > > in global: > ip cef > on each interface that traffic can go out: > ip load-sharing per-packet > to verify, > sh ip cef 0.0.0.0 0.0.0.0, this will say either per destination or packet > > Thanks > -Nate > > "Kelly Hair" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > And turn off fast switching if you want per packet load balancing: > > > > int s0 > > no ip route-cache > > > > If you do not need process switching then leave the interface it its > default > > switching mode.. I would think you would want to load balance per packet > > so it appears to be equally slow/fast as compared to "this connection > rocks" > > and "why does this connection suck so bad?" > > > > ---- > > > > Assuming the traffic is IP another modifications you can look at that > would > > be pretty easy to setup: > > > > > Setting ip policy on the BRI/serial interfaces with the T1 interface > > transporting packets matching a route-map of say 400 bytes to 1500 bytes > and > > those smaller going across the BRI... > > > > It would look something like this: > > > > int bri0 > > ip address a.a.a.a x.x.x.x > > > > int s0 > > ip address b.b.b.b x.x.x.x > > > > int eth0 > > ip addresss c.c.c.c x.x.x.x > > ip route-cache policy > > ip policy route-map inet > > > > route-map inet permit 10 > > match length 400 1500 > > set ip next-hop > > > > route-map inet permit 20 > > > > ip route 0.0.0.0 0.0.0.0 > > > > -------- > > > > HTH > > Kelly > > > > ----- Original Message ----- > > From: "Mike Nygard" > > To: > > Sent: Saturday, June 02, 2001 4:59 PM > > Subject: Re: How to configure 1601 to load balance 2 Internet circuits > > [7:6911] > > > > > > > Hello Justin, > > > > > > The easiest way to resolve this would be to use multiple default routes > > from > > > global configuration: > > > > > > ip route 0.0.0.0 0.0.0.0 > > > ip route 0.0.0.0 0.0.0.0 > > > > > > The router will load balance between the 2 routes. > > > > > > Thank you, > > > Mike Nygard > > > > > > > > > ""Justin Lofton"" wrote in message > > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > > I have a customer that has a 128k connection to the Internet and they > > are > > > > bringing in a T1 to the Internet but they want to load balance on both > > > > circuits for a week to be sure the new circuit is working properly. > > What > > > is > > > > the simpliest way to configure this scenario? Can I set multiple last > > > > resort gateways or what? Please help! > > > > > > > > Thanks everyone! > > > > > > > > Justin Lofton > > > > Account Executive/CCNA > > > > Tredent Data Systems > > > > [EMAIL PROTECTED] > > > > V: (818) 222-3770 > > > > F: (818) 222-3778 > > > > http://www.tredent.com/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=7191&t=7191 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
