EIGRP traffic-share min

when you use the traffic-share command with the keyword min, the traffic is sent only across the minimum-cost path, even when there are multiple paths in the routing table. This is identical to the forwarding behaviour without use of the variance command. However, if you use the traffic-share min command and the variance command, even though traffic is sent over the minimum-cost path only, all feasible routes get installed into the routing table, which decreases convergence times.

1. traffic-share balanced (default):
1. Variance=1 (default):
1. Traffic will be sent to successor(s) only (equal cost load balancing).
2. Feasible successors are kept in EIGRP topology table.
3. Feasible successors are not kept in the routing table.
2. Variance=2+:
1. Traffic will be sent to successor(s) and feasible successors(s).
2. Traffic will be sent inversely proportional to their metrics.
3. All successor(s) and feasible successor(s) are kept in the routing table.
2. traffic-share min across-interfaces:
1. Variance=1 (default):
1. same as (1.1)
2. Variance=2+:
1. Traffic will be sent to successor(s) only (equal cost load balancing).
2. Feasible successors are kept in the routing table.

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a008009437d.shtml

http://blog.ine.com/2009/05/01/understanding-unequal-cost-load-balancing/