ヨタ助

携帯用ページ http://www.google.co.jp/gwt/x?u=http%3a%2f%2funipass.blogspot.com&btngo=go&source=wax&ie=utf-8&oe=utf-8

Saturday, December 04, 2010

7.27 BGP Bestpath Selection - DMZ Link Bandwidth

During this scenario, I got the message below after clear ip bgp * soft done.



*Mar  1 11:27:45.373: %FIB-4-UNEQUAL: Range of unequal path weightings too large for prefix 28.119.16.0/24. Some available paths may not be used.


Example output below is not related to 28.119.16.0/24 prefix, however, the output should be same (I also confirmed it with 28.119.16.0/24). After modifying bandwidth on R6, the error message has not shown up anymore.

After modifying "Bandwidth" of se0/0 on R6 (connected to BB1)
  >> using 2000(K) which following the workbook answer  <<
 Rack1R1#sh ip bgp 112.0.0.0  
BGP routing table entry for 112.0.0.0/8, version 148
Paths: (2 available, best #1, table Default-IP-Routing-Table)
Multipath: iBGP
Flag: 0x8800
  Advertised to update-groups:
        1    2
  54 50 60, (Received from a RR-client)
    204.12.1.254 (metric 2560002816) from 155.1.146.4 (150.1.4.4)
      Origin IGP, metric 0, localpref 100, valid, internal, multipath, best
      DMZ-Link Bw 12500 kbytes
  54 50 60, (Received from a RR-client)
    54.1.1.254 (metric 2560002816) from 155.1.146.6 (150.1.6.6)
      Origin IGP, metric 0, localpref 100, valid, internal, multipath
      DMZ-Link Bw 250 kbytes
Rack1R1#sh ip route 112.0.0.0
Routing entry for 112.0.0.0/8
  Known via "bgp 100", distance 200, metric 0
  Tag 54, type internal
  Last update from 54.1.1.254 00:00:15 ago
  Routing Descriptor Blocks:
  * 204.12.1.254, from 155.1.146.4, 00:00:15 ago
      Route metric is 0, traffic share count is 48
      AS Hops 3
      Route tag 54
    54.1.1.254, from 155.1.146.6, 00:00:15 ago
      Route metric is 0, traffic share count is 1
      AS Hops 3
      Route tag 54


After modifying "Bandwidth" of se0/0 on R6 (connected to BB1)
  >> changed from 2000(K) from the answer from workbook to 4096(K) <<
Rack1R1#sh ip bgp 112.0.0.0 
BGP routing table entry for 112.0.0.0/8, version 163
Paths: (2 available, best #1, table Default-IP-Routing-Table)
Multipath: iBGP
Flag: 0x8800
  Advertised to update-groups:
        1    2
  54 50 60, (Received from a RR-client)
    204.12.1.254 (metric 2560002816) from 155.1.146.4 (150.1.4.4)
      Origin IGP, metric 0, localpref 100, valid, internal, multipath, best
      DMZ-Link Bw 12500 kbytes
  54 50 60, (Received from a RR-client)
    54.1.1.254 (metric 2560002816) from 155.1.146.6 (150.1.6.6)
      Origin IGP, metric 0, localpref 100, valid, internal, multipath
      DMZ-Link Bw 512 kbytes
Rack1R1#sh ip route 112.0.0.0
Routing entry for 112.0.0.0/8
  Known via "bgp 100", distance 200, metric 0
  Tag 54, type internal
  Last update from 54.1.1.254 00:00:06 ago
  Routing Descriptor Blocks:
  * 204.12.1.254, from 155.1.146.4, 00:00:06 ago
      Route metric is 0, traffic share count is 24
      AS Hops 3
      Route tag 54
    54.1.1.254, from 155.1.146.6, 00:00:06 ago
      Route metric is 0, traffic share count is 1
      AS Hops 3
      Route tag 54

Reference URL
http://cciepursuit.wordpress.com/2008/09/15/disabling-eigrp-unequal-cost-load-balancing/

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home