EIGRP REDISTRIBUTION CONNECTED AND OTHER EIGRP PROCESS


Hello Experts,

I have a scenario which ROUTER dont redistribute routes connected and other eigrp process :

There are two routers conected directly R8 - R10 running 2 EIGRP Process.

Task: In R10 redistribuited Lo100 (redistributed connected with route-map matching only lo100) and Lo101 (belong to other eigrp 200), see this prefix in R8.

Problem: Lo101 is not redistribuited

R10#show ip int b | ex ass 

Interface                 
IP-Address      OK? Method
Status                Protocol 

Ethernet0/1.108           
155.1.108.10    YES NVRAM  up                    up     

Loopback100               
10.10.10.10     YES manual up                    up     

Loopback101               
10.10.10.11     YES manual up                    up     

 

R10#show run | sec route-map

route-map conected permit 10

 match interface
Loopback100

R10#show run |  s r e

router eigrp 100

 network 150.1.0.0

 network 155.1.0.0

 redistribute
connected metric 10000 1 255 1 1500 route-map conected

 redistribute eigrp
200 metric 1 1 1 1 1

router eigrp 200

 network 10.10.10.11
0.0.0.0

 

Result:

R8#show ip ro | sec 10.10.10.10
D EX     10.10.10.10 [170/1541120] via 155.1.108.10, 00:20:14, Ethernet0/1.108
      150.1.0.0/32 is subnetted, 8 subnets
R8#show ip ro  10.10.10.11    
% Subnet not in table

 

Troubleshooting:I see that neighbor and Lo101 belong to the process 200, but I dont understand why is not redistribute in eigrp 100. I think that the redistribute connected with route-map is not allowing that redistribution because think lo101 is connected and not match in route-map


R10#show ip eigrp 100 topology  | sec 10.10.10.10
P 10.10.10.10/32, 1 successors, FD is 256256
        via Rconnected (256256/0)
R10#show ip eigrp 200 topology  | sec 10.10.10.11
P 10.10.10.11/32, 1 successors, FD is 128256
        via Connected, Loopback101

 R10#show ip ei 100 int

EIGRP-IPv4 Interfaces for AS(100)

                             
Xmit Queue   PeerQ        Mean  
Pacing Time   Multicast    Pending

Interface             
Peers  Un/Reliable  Un/Reliable 
SRTT   Un/Reliable   Flow Timer  
Routes

Lo0                     
0        0/0       0/0           0       0/0            0           0

Et0/1.108               
1        0/0       0/0           8       0/2           50           0

R10#show ip ei 200 in

EIGRP-IPv4 Interfaces for AS(200)

                             
Xmit Queue   PeerQ        Mean  
Pacing Time   Multicast    Pending

Interface             
Peers  Un/Reliable  Un/Reliable 
SRTT   Un/Reliable   Flow Timer  
Routes

Lo101                   
0        0/0       0/0           0       0/0            0           0

 

thanks for your help.

 

 

Comments

  • When you redistribute connected with a route-map, the routing protocols will no longer automatically redistribute the connected interfaces for that protocol. You'll need to add those interfaces into the route-map used with the redistribute connected statement.

  • Thanks for the answer. I agree with you but the problem is not the route-map without matching lo101. The problem is that lo101 is not redistributed although there is redistribution eigrp 200 into eigrp 100:

    R10#show run |  s r e

    router eigrp 100

     network 150.1.0.0

     network 155.1.0.0

     redistribute
    connected metric 10000 1 255 1 1500 route-map conected

     redistribute eigrp
    200 metric 1 1 1 1 1   ==> cisco doc:  metric eigrp into eigrp is optional

    !

    router eigrp 200

     network 10.10.10.11
    0.0.0.0

     

     

  • So, answer is plain easy: you redistribute EIGRP 200 into EIGRP 100; this means the router will bring into EIGRP 100 topology all routes learned through EIGRP 200 from its neighbors and installed in the RIB and also all connected links o which you run EIGRP 100 which means loopback of 10.10.10.11. But because in EIGRP 100 you have a connected redistribution which says that you allow to bring into EIGRP 100 only connected prefixes which are allowed by the route-map, and that's why 10.10.10.11 does not get into EIGRP 100 topology and it is not advertised out. Solution:

    1. remove the connected redistribution from EIGRP 100

    2. add 10.10.10.11 into your connected route-map used for reditribution

  • Thanks, Cristian and Martin for the explanation.

Sign In or Register to comment.