[c-nsp] per-packet load sharing.

[Aamer Akhter (aakhter)]

Veranda,

Have you looked at PfR (Performance Routing) to distribute the flows across the links? Differently that the CEF hash, PfR has flow and link utilization awareness, and can very granularly move flows amongst exit links (ie for a site). 



-- 
Aamer Akhter / aa at cisco.com
Ent & Commercial Systems, cisco Systems

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Joe Provo
> Sent: Monday, December 10, 2007 6:42 AM
> To: 'cisco-nsp'
> Subject: Re: [c-nsp] per-packet load sharing.
> 
> On Sun, Dec 09, 2007 at 05:39:07PM -0800, virendra rode // wrote:
> [snip]
> > In order to distribute traffic (load-sharing) across two links I'm
> > looking at enabling equal cost traffic (per-packet load sharing)
> going
> > out both serial links as their data processing is overloading one
> link.
> > The equal cost routes with CEF default load sharing is not
> distributing
> > the load over the 2 links as expected.  MLPPP is not an option for
> > budget reasons hence I'm looking at doing per-packet.
> [snip]
> > Any recommendation and /or feedback will be appreciated.
> 
> ECMP in routing protocols good, per-packet bad.  If you care at all
> about TCP performance or have jitter-sensitive traffic then don't do
> it.  Your best bet is to suss out how much BGP you can eat on the
> platform, get that data and (backfill with 0/0 if you are on a limited
> platform), then slice and dice your load at that level.
> 
> Cheers,
> 
> Joe
> --
>              RSUC / GweepNet / Spunk / FnB / Usenix / SAGE
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/