CEF uses a hash algorithm to allow for load sharing. This hash algorithm will per default use destination IP to decide, where to send a packet.
The net result is, that all traffic to a specific destination will go through one link. Thus you might encounter situations, where one link is utilized heavily and the other is nearly idle.
"mls ip cef load-sharing full" will use a different hash including TCP/UDP port numbers. Thus each session will go through one link, but traffic to one server IP f.e. will be more evenly distributed. Still the order of packets for a single session is assured.
"ip load-sharing per-packet" will do load sharing on a per packet basis. This will give you the most even load distribution on your two links. The drawback is, however, that packets might be reordered because of different transmission times on both pathes. This is f.e. negative for voip and also might impact TCP throughput (the receiving system needs to reorder TCP segments received in the wrong order).
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...