EIGRP metric advertise to neighbor

[AleksFly1]

Hi All,

I'm playing wiht this below topology and EIGRP.  Some details about the configuration:

R4: Loopback interface 155.1.4.4/32

R3:

R3#sh ip int br
Interface                  IP-Address      OK? Method Status                Protocol
Ethernet0/0                150.1.37.3      YES manual up                    up
Ethernet0/1                150.1.13.3      YES manual up                    up
Loopback0                  155.1.3.3       YES manual up                    up
!
!
D        155.1.1.1 [90/409600] via 150.1.13.1, 00:35:57, Ethernet0/1
D        155.1.4.4 [90/435200] via 150.1.13.1, 00:35:57, Ethernet0/1
D        155.1.6.6 [90/435200] via 150.1.37.7, 00:35:57, Ethernet0/0
D        155.1.7.7 [90/166400] via 150.1.37.7, 00:35:57, Ethernet0/0

R7:

R7#sh ip int br
Interface                  IP-Address      OK? Method Status                Protocol
Ethernet0/0                150.1.67.7      YES manual up                    up
Ethernet0/1                150.1.37.7      YES manual up                    up
Loopback0                  155.1.7.7       YES manual up                    up
!
!
D        155.1.1.1 [90/435200] via 150.1.37.3, 00:38:33, Ethernet0/1
D        155.1.3.3 [90/409600] via 150.1.37.3, 00:38:33, Ethernet0/1
D        155.1.4.4 [90/435200] via 150.1.67.6, 00:38:33, Ethernet0/0
D        155.1.6.6 [90/409600] via 150.1.67.6, 00:38:34, Ethernet0/0
!
!
R7#sh ip eigrp topology 155.1.4.4/32
EIGRP-IPv4 Topology Entry for AS(100)/ID(155.1.7.7) for 155.1.4.4/32
  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 435200
  Descriptor Blocks:
  150.1.67.6 (Ethernet0/0), from 150.1.67.6, Send flag is 0x0
      Composite metric is (435200/409600), route is Internal
      Vector metric:
        Minimum bandwidth is 10000 Kbit
        Total delay is 7000 microseconds
        Reliability is 255/255
        Load is 1/255
        Minimum MTU is 1500
        Hop count is 2
        Originating router is 155.1.4.4
  150.1.37.3 (Ethernet0/1), from 150.1.37.3, Send flag is 0x0
      Composite metric is (460800/435200), route is Internal
      Vector metric:
        Minimum bandwidth is 10000 Kbit
        Total delay is 8000 microseconds
        Reliability is 255/255
        Load is 1/255
        Minimum MTU is 1500
        Hop count is 3
        Originating router is 155.1.4.4

I would like to modify the configuratoin only on Router R3 so that R7 will choose the path to 155.1.4.4/32 via 150.1.37.3. The change should affect only the R4 lo0 interace.

I know how to achieve this via manipulate the config on other routers via the bandwith, delay, distance, offset-list. I just can't force R3 to be choosen as a better path for 155.1.4.4/32 from R7 instead R6.

Any advise welcome, thanks.

[Julio E. Moisa]

Hi

You can use administrative distance to accomplish this task. Please let me share the config. 

Try with this config on R3

conf t
access-list 4 permit host 155.1.4.4

router eigrp 100
distance 91 150.1.13.1 0.0.0.0 4

clear ip route 155.1.4.4 

Hope it is useful

:-)

[AleksFly1]

Hi Julio,

thanks for reply, but I want to achieve something else. With your proposal I have now:

R3:

D        155.1.1.1 [90/486400] via 150.1.37.7, 00:00:11, Ethernet0/0
C        155.1.3.3 is directly connected, Loopback0
D        155.1.4.4 [90/460800] via 150.1.37.7, 00:00:11, Ethernet0/0
D        155.1.6.6 [90/435200] via 150.1.37.7, 00:00:11, Ethernet0/0
D        155.1.7.7 [90/166400] via 150.1.37.7, 00:00:14, Ethernet0/0
!
!
R7:
D        155.1.1.1 [90/460800] via 150.1.67.6, 00:02:41, Ethernet0/0
D        155.1.3.3 [90/409600] via 150.1.37.3, 00:02:40, Ethernet0/1
D        155.1.4.4 [90/435200] via 150.1.67.6, 01:44:00, Ethernet0/0
D        155.1.6.6 [90/409600] via 150.1.67.6, 01:44:01, Ethernet0/0
C        155.1.7.7 is directly connected, Loopback0

I want to achieve that the router R7 has a route for 155.1.4.4/32 via 150.1.37.3 by modifying only the R3 configuration.

[Georg Pauwen]

Hello,

I hate to say something is impossible, but in this case I think it is. I have changed the bandwidth and the delay to the highest and lowest values on BOTH interfaces on R3, and set the distance to 1 for incoming updates from R1, but that still isn't enough for R7 to prefer the route through R3. That really is all you can do to influence the metric...

[AleksFly1]

Georg,

thanks for trying. I can't figure out either how to achieve this.

[Julio E. Moisa]

Hi

If you want that R3 is preferred than R6 you must configure a lower AD than 90

R3 

conf t
access-list 4 permit host 155.1.4.4

router eigrp 100
distance 89 150.1.13.1 0.0.0.0 4

clear ip route 155.1.4.4 

So R7 will prefer R3 as next hop for the route 155.1.4.4 only, the rest will be known through R7, All the routes included on the ACL 4 will be marked with AD 89.

But if you want to have 2 routes (one to R6 and other to R3) into the routing table you need to have equal metric, so you need to modify the Delay on R3's interface facing to R1 otherwise you will have unequal load balance and just one route will be seen into the routing table. 

:-)

[AleksFly1]

Julio,

that doesn't help either:

R3:
!
router eigrp 100
 network 150.1.0.0
 network 155.1.0.0
 distance 50 150.1.13.1 0.0.0.0 4
!
access-list 4 permit 155.1.4.4
!
!
D        155.1.4.4 [50/435200] via 150.1.13.1, 00:00:04, Ethernet0/1
D        155.1.6.6 [90/435200] via 150.1.37.7, 00:00:04, Ethernet0/0
!
R7:
D        155.1.1.1 [90/435200] via 150.1.37.3, 00:00:09, Ethernet0/1
D        155.1.3.3 [90/409600] via 150.1.37.3, 00:00:09, Ethernet0/1
D        155.1.4.4 [90/435200] via 150.1.67.6, 00:00:09, Ethernet0/0
D        155.1.6.6 [90/409600] via 150.1.67.6, 00:04:01, Ethernet0/0

The AD changed on R3, however this doens't worked for R7.

On Cisco website I found that the Administrative distance is not propagated to other routers ( URL )

[Julio E. Moisa]

That is correct, there is a way  and it is manipulating the hop count, metric maximum-hops <1-255> if you execute show ip route <prefix> you will see the hop count below. This method will work if the restriction is for R3. Otherwise manipulating delay, I dont suggest manipulate BW because it could be used for other service like QoS. 

Please let me think in other way if there is. 

[AleksFly1]

I'm wondering if there is a problem with my virtual environment ? Even if I change the delay on both interfaces on R3, nothing happens:

R3#sh int e0/0 | in DLY
  MTU 1500 bytes, BW 10000 Kbit/sec, DLY 10 usec,
R3#sh int e0/1 | in DLY
  MTU 1500 bytes, BW 10000 Kbit/sec, DLY 10 usec,
!
R7:
D        155.1.1.1 [90/409856] via 150.1.37.3, 00:04:10, Ethernet0/1
D        155.1.3.3 [90/409600] via 150.1.37.3, 00:05:42, Ethernet0/1
D        155.1.4.4 [90/435200] via 150.1.67.6, 00:00:03, Ethernet0/0
D        155.1.6.6 [90/409600] via 150.1.67.6, 00:05:46, Ethernet0/0
C        155.1.7.7 is directly connected, Loopback0
!
R7#sh ip eigrp topology 155.1.4.4/32
EIGRP-IPv4 Topology Entry for AS(100)/ID(155.1.7.7) for 155.1.4.4/32
  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 435200
  Descriptor Blocks:
  150.1.67.6 (Ethernet0/0), from 150.1.67.6, Send flag is 0x0
      Composite metric is (435200/409600), route is Internal
      Vector metric:
        Minimum bandwidth is 10000 Kbit
        Total delay is 7000 microseconds
        Reliability is 255/255
        Load is 1/255
        Minimum MTU is 1500
        Hop count is 2
        Originating router is 155.1.4.4
  150.1.37.3 (Ethernet0/1), from 150.1.37.3, Send flag is 0x0
      Composite metric is (435456/409856), route is Internal
      Vector metric:
        Minimum bandwidth is 10000 Kbit
        Total delay is 7010 microseconds
        Reliability is 255/255
        Load is 1/255
        Minimum MTU is 1500
        Hop count is 3
        Originating router is 155.1.4.4

Or maybe this is not achievable to configure only R3 ??

[Julio E. Moisa]

Hi

Try to set up a delay of 2000 (delay 200) under the R6's interface facing to R4, if nothing happens you can clear  the neighborship

clear ip eigrp neighbor

[AleksFly1]

Hi Julio,

yes this helps if you tweak R6 :)

But my question was, if it's possible to configure only R3 to achieve this. Configuring other routers I was able to get my result.