From: Victor Cappuccio (cvictor@protokolgroup.com)
Date: Sat Apr 22 2006 - 01:56:45 GMT-3
Dears sorry the page consufed me more (maybe an english problem) but I
do not get the formula used in this equation:
http://www.cisco.com/warp/public/103/eigrp-toc.html
minimum bandwidth = 56k
total delay = 100 + 100 + 2000 = 2200
[(10000000/56) + 2200] x 256 = (178571 + 2200) x 256 = 180771 x 256 =
46277376
I tested with 4 Routers that I have to any certain route ..
Rack1R1#show ip eigrp topology 192.168.1.0 255.255.255.0
IP-EIGRP (AS 100): Topology entry for 192.168.1.0/24
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 3.154.432
Routing Descriptor Blocks:
164.1.13.3 (Serial0/1), from 164.1.13.3, Send flag is 0x0
Composite metric is (3.154.432/2.642.432), Route is Internal
Vector metric:
Minimum bandwidth is 1280 Kbit
Total delay is 45100 microseconds
164.1.12.2 (Serial0/0), from 164.1.12.2, Send flag is 0x0
Composite metric is (10.642.432/156.160), Route is Internal
Vector metric:
Minimum bandwidth is 256 Kbit
Total delay is 25100 microseconds
The Composite metric gives me 13.545.600 using the following formula
=((10000000/1280)+45100)*256
And Router metric (FD) to the route is 3.154.432
Do I'm missing something?
Victor Cappuccio escribis:
> I found the answer metric = BW + DLY, where the Bw(i) is the min bw
> and the Dly(i) is the sum of delay
>
> I had it in from of my eyes
> Rack1R1#$rp topology 192.168.1.0 255.255.255.0 | in
> (from|bandwidth|delay) 164.1.12.2 (Serial0/0), from 164.1.12.2, Send
> flag is 0x0
> *Minimum bandwidth is 256 Kbit*
> Total delay is 25100 microseconds
> 164.1.13.3 (Serial0/1), from 164.1.13.3, Send flag is 0x0
> *Minimum bandwidth is 256 Kbit*
> Total delay is 45100 microseconds
>
> http://www.cisco.com/warp/public/103/eigrp-toc.html
>
> Sorry for the spam folks
>
>
> Victor Cappuccio escribis:
>> Guys
>>
>> Im trying to understand the command traffic-share in EIGRP but, I
>> think I came to the conclusion that EIGRP by default uses balanced
>> unequal load sharing using the metric to determine how many packets
>> are sent to which interface
>>
>> Please could anyone provide more detailed information on how to
>> modify the DLY when you are not allowed to modify the bandwidth just
>> to get certain ration let say 5:1?
>>
>> Thanks
>> Victor.
>>
>>
>> Rack1R1#show ip route 192.168.1.0
>> Routing entry for 192.168.1.0/24
>> Known via "eigrp 100", distance 90, metric 10642432, type internal
>> Redistributing via eigrp 100
>> Last update from 164.1.13.3 on Serial0/1, 00:00:12 ago
>> Routing Descriptor Blocks:
>> * 164.1.12.2, from 164.1.12.2, 00:00:12 ago, via Serial0/0
>> Route metric is 10642432, traffic share count is 240
>> Total delay is 25100 microseconds, minimum bandwidth is 256 Kbit
>> Reliability 255/255, minimum MTU 1500 bytes
>> Loading 1/255, Hops 2
>> 164.1.13.3, from 164.1.13.3, 00:00:12 ago, via Serial0/1
>> Route metric is 11154432, traffic share count is 229
>> Total delay is 45100 microseconds, minimum bandwidth is 256 Kbit
>> Reliability 255/255, minimum MTU 1500 bytes
>> Loading 1/255, Hops 3
>>
>> Rack1R1#conf te
>> Enter configuration commands, one per line. End with CNTL/Z.
>> Rack1R1(config)#router eigrp 100
>> Rack1R1(config-router)#traffic-share ?
>> balanced Share inversely proportional to metric
>> min All traffic shared among min metric paths
>>
>> Rack1R1(config-router)#traffic-share ba
>> Rack1R1(config-router)#traffic-share balanced ?
>> <cr>
>>
>> Rack1R1(config-router)#traffic-share balanced
>> Rack1R1(config-router)#do crt
>> Rack1R1(config-router)#do show ip route 192.168.1.0
>> Routing entry for 192.168.1.0/24
>> Known via "eigrp 100", distance 90, metric 10642432, type internal
>> Redistributing via eigrp 100
>> Last update from 164.1.13.3 on Serial0/1, 00:00:08 ago
>> Routing Descriptor Blocks:
>> * 164.1.12.2, from 164.1.12.2, 00:00:08 ago, via Serial0/0
>> Route metric is 10642432, traffic share count is 240
>> Total delay is 25100 microseconds, minimum bandwidth is 256 Kbit
>> Reliability 255/255, minimum MTU 1500 bytes
>> Loading 1/255, Hops 2
>> 164.1.13.3, from 164.1.13.3, 00:00:08 ago, via Serial0/1
>> Route metric is 11154432, traffic share count is 229
>> Total delay is 45100 microseconds, minimum bandwidth is 256 Kbit
>> Reliability 255/255, minimum MTU 1500 bytes
>> Loading 1/255, Hops 3
>>
>> Rack1R1(config-router)#traffic-share ?
>> balanced Share inversely proportional to metric
>> min All traffic shared among min metric paths
>>
>> Rack1R1(config-router)#traffic-share min ?
>> across-interfaces Use different interfaces for equal-cost paths
>>
>> Rack1R1(config-router)#traffic-share min ac
>> Rack1R1(config-router)#traffic-share min across-interfaces ?
>> <cr>
>>
>> Rack1R1(config-router)#traffic-share min across-interfaces
>> Rack1R1(config-router)#do show ip route 192.168.1.0
>> *Mar 1 10:41:31.837: %FIB-4-UNEQUAL: Range of unequal path weightings
>> too large for prefix 10.6.6.0/24. Some available path.
>> Rack1R1(config-router)#do crt
>> Rack1R1(config-router)#traffic-share min across-interfaces
>> *Mar 1 10:41:41.877: %FIB-4-UNEQUAL: Range of unequal path weightings
>> too large for prefix 10.6.6.0/24. Some available path.
>> Rack1R1(config-router)#do show ip route 192.168.1.0
>> Routing entry for 192.168.1.0/24
>> Known via "eigrp 100", distance 90, metric 10642432, type internal
>> Redistributing via eigrp 100
>> Last update from 164.1.13.3 on Serial0/1, 00:00:05 ago
>> Routing Descriptor Blocks:
>> * 164.1.12.2, from 164.1.12.2, 00:00:05 ago, via Serial0/0
>> Route metric is 10642432, traffic share count is 1
>> Total delay is 25100 microseconds, minimum bandwidth is 256 Kbit
>> Reliability 255/255, minimum MTU 1500 bytes
>> Loading 1/255, Hops 2
>> 164.1.13.3, from 164.1.13.3, 00:00:05 ago, via Serial0/1
>> Route metric is 11154432, traffic share count is 0
>> Total delay is 45100 microseconds, minimum bandwidth is 256 Kbit
>> Reliability 255/255, minimum MTU 1500 bytes
>> Loading 1/255, Hops 3
>>
>> Rack1R1(config-router)#traffic-share b
>> Rack1R1(config-router)#traffic-share balanced
>> Rack1R1(config-router)#^Z
>> Rack1R1#
This archive was generated by hypermail 2.1.4 : Mon May 01 2006 - 11:41:58 GMT-3