Wednesday, December 21, 2011

EIGRP UNEQUAL COST LOADBALANCING

Ok today I looked at EIGRP Unequal Load Balancing.
EiGRP is one of the only routing protocols that can do unequal cost load balancing.
You control this with the variance command
The rule for use of equal cost load balancing is firstly the route must be a feasible successor
then if variance * feasible successors feasible distance is > than the successor feasible distance the path will be used for unequal cost load balancing
The variance command does not affect the traffic share between the links. Like if you do a high variance it does not affect the traffic share between the 2 links. The traffic share will be decided on by the underlying whether it is gig or fa etc also the current switching that you are using (Cef,process switching)
You can view the traffic share on destiantion after doing the variance by using the
sh ip route "prefix"
under this command you will see the viable routes + there traffic share. Even with this info it is hard to predict which link will take which path ultimately in most enviorments cef will decide
If you wanted to control this you but on process switching
int fa0/0
no ip route cache
ip load-sharing per packet
this is not recommended firstly udp traffic like voice has issue with per packet load balancing as it can not reorganise the sequence of frames and also you are using a legacy switching type
For the LAB
------------
We will use sw2-sw1-r5 as the primary path to r5 5.5.5.5 loopback we will make sw2-sw3-sw4-r5 a feasible successor by lowering the dealy and we will use unequal cost load balancing to 5.5.5.5



Ok so i have configured all routers with eigrp i have edited the delay on sw3 to make the adverised distance feasible
so on sw2 i have the following out put
switch2#sh ip eigrp top 5.5.5.0/24
IP-EIGRP (AS 1): Topology entry for 5.5.5.0/24
  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 158720
  Routing Descriptor Blocks:
  10.229.254.1 (Port-channel2), from 10.229.254.1, Send flag is 0x0
      Composite metric is (158720/156160), Route is Internal
      Vector metric:
        Minimum bandwidth is 100000 Kbit
        Total delay is 5200 microseconds
        Reliability is 255/255
        Load is 1/255
        Minimum MTU is 1500
        Hop count is 2
  172.25.10.2 (Port-channel8), from 172.25.10.2, Send flag is 0x0
      Composite metric is (169216/156416), Route is Internal
      Vector metric:
        Minimum bandwidth is 100000 Kbit
        Total delay is 5610 microseconds
        Reliability is 255/255
        Load is 1/255
        Minimum MTU is 1500
        Hop count is 3
switch2#
so the second path is feasible successor 156416 is less than 158720 the primary routes feasible distance
so on s2

switch2(config)#router eigrp 1
switch2(config-router)#variance 2
switch2(config-router)#

switch2#sh ip route 5.5.5.5
Routing entry for 5.5.5.0/24
  Known via "eigrp 1", distance 90, metric 158720, type internal
  Redistributing via eigrp 1
  Last update from 172.25.10.2 on Port-channel8, 00:00:28 ago
  Routing Descriptor Blocks:
    172.25.10.2, from 172.25.10.2, 00:00:28 ago, via Port-channel8
      Route metric is 169216, traffic share count is 15
      Total delay is 5610 microseconds, minimum bandwidth is 100000 Kbit
      Reliability 255/255, minimum MTU 1500 bytes
      Loading 1/255, Hops 3
  * 10.229.254.1, from 10.229.254.1, 00:00:28 ago, via Port-channel2
      Route metric is 158720, traffic share count is 16
      Total delay is 5200 microseconds, minimum bandwidth is 100000 Kbit
      Reliability 255/255, minimum MTU 1500 bytes
      Loading 1/255, Hops 2
switch2#

No comments:

Post a Comment