If you have a large number of hosts communicating then you shouldnt need to go per packet. Per packet is generally considered a no-no as it leads to out of order packets arriving at the remote host, which then has to reorder the stream. This kippers the performance of the hosts in most circumstances.
per destination load balancing builds a hash of streams to interface so a particular stream will always go the same route and so packet arrive in order. Different streams are balanced across as many equal routes as youve got. Sometimes this hashing can get polarised which is bad (sending more down one route than the other) so you need to configure "ip cef load-sharing algorithm universal. NB: when I say stream here I mean Source/destination pairs, not including port numbers etc. like netflow. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72300&t=72232 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
