Hello Sunny

Do you want to run the dynamic routing protocol over the 2 ISPs or on the LAN side ? If we are talking about configuring it over the WAN, are the ISP's routing your public IP traffic, or is it a VPN carrier ? I mean do the sites end to end look like a point to point link ? If you want to do multihoming, then you need to consider BGP.. If we are restricting the post to LAN or point to point routing, then go for EIGRP (considering you have cisco devices).. EIGRP has many advantages over OSPF including better convergence, summarization/route filtering at any boundary, unequal path loadbalancing etc.. there are lots of docs on internet comparing these protocols..

again to answer to your questions:

1.Outbound loadsharing of traffic - possible with BGP/EIGRP.. outbound is more controlled by you..

2.Redundancy failover to other link in case of failures. - possible..

Hope this helps.. all the best.. rate replies if found useful..

Raj

Sunny

If your site has only a central switch and 2 routers then I believe that there is very little to choose between OSPF and EIGRP. They will both work very well in that situation. I believe that they will do equally well in loadsharing of outbound traffic and on redundancy in case of failure.

It is probably more important to work out how the routers will generate a default route and advertise it which is the basic requirement for outbound load sharing. And there may be questions of how the router will recognize that it needs to withdraw its default route (how will it recognize failure) which is the basic requirement for redundancy in case of failure.

HTH

Rick

You mention uplink providers? If this are ISP then you should use BGP and they should supply you BGP. You can get full or partial table updates from your providers. BGP will provide best routing path. You can also configure BGP metrics to modify path selections. You also want to make sure that you are not a pass through for the providers in the advent of a provider goes off the network backbones.

Both OSPF and EIGRP can be used for equal cost load sharing, as can statics. EIGRP also supports varible cost load sharing. Dynamic routing protocols tend to deal well with failures, statics less so, although with Cisco's latest object tracking, they can too.

For routing load sharing it's, more-or-less round robin per flow unless you have packet-by-packet load sharing, which can lead to packet sequencing issues (somthing we often want to avoid).

Cisco latest IOSs also support a new technology, OER/PfR, which can both dynamically load balance and provide best possible performance to flows. Older versions are limited to BGP or statics, latest version support any(?) routing protocol.