Apologies for the late reply, I just noticed this in my mailbox and
wanted to address...
The per-packet tag load balancing in JUNOS actually performs per flow
load balancing depending on what ASIC you have. With the IP1 ASIC it
performs per packet load balancing on up to 8 equal cost paths. With
the IP2 ASIC it will perform flow load balancing on up to 16 equal cost
paths. Unfortunately the syntax in this case is a bit misleading. Do
not be deceived by the syntax here: per-packet is what actually turns on
flow based load balancing.
The new tag offered in JUNOS 5.0 called "per-flow" simply allows you to
modify the behaviour already enabled with the "per-packet" tag. More
specifically, it allows you to determine what defines a flow: layer 3
information (IP) or layer 4 information (TCP/UDP). In most cases you
will want to load balance per flow, and NOT per packet, or latency
sensitive applications will start to break.
-- steve
-----Original Message-----
From: Wilson, Michael [mailto:mkwilson@uslec.com]
Sent: Thursday, September 06, 2001 2:42 PM
To: 'juniper-nsp@puck.nether.net'
Subject: load-balancing
It appears to me that the Juniper supports only one kind of
load-balancing.
In older versions, it was called per-packet. But in version 5, they are
calling it per-flow, with an option to load-balance on either just
layer-3,
or layer-3 and layer-4 headers. Is this equivalent to Cisco's
per-destination load-balancing? To me, it seems the Juniper doesn't
support
true per-packet load-balancing.
Michael Wilson
Data Network Engineering
(704) 319-1983 - desk
mkwilson@uslec.com
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:37 EDT