10-16-2012 06:35 AM - edited 03-07-2019 09:29 AM
Good day!
I have noticed that i cant make R4 and also R2 to choose prefered path to R1 over R3...
Where is my mistake?
Can you help me please?
Here is my topology
and configuration of to ABR's
R3:
router eigrp 100
redistribute ospf 1 metric 1544 5 255 1 1500
network 10.1.23.0 0.0.0.255
no auto-summary
!
router ospf 1
log-adjacency-changes
redistribute eigrp 100 subnets route-map MAIN_1
network 10.1.13.0 0.0.0.255 area 0
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
!
access-list 1 permit 10.4.0.0 0.0.0.255
access-list 1 permit 10.4.1.0 0.0.0.255
access-list 2 permit 10.4.2.0 0.0.0.255
access-list 2 permit 10.4.3.0 0.0.0.255
access-list 3 deny 10.4.4.0 0.0.0.255
access-list 50 permit 10.1.0.0 0.0.0.255
access-list 99 permit 10.1.23.0 0.0.0.255
access-list 99 permit 10.1.24.0 0.0.0.255
!
!
!
route-map MAIN permit 10
match ip address 1
set tag 10
!
route-map MAIN deny 11
match tag 10
!
route-map MAIN permit 20
match ip address 2
set tag 20
!
route-map MAIN deny 21
match tag 20
!
route-map MAIN deny 30
match ip address 3
!
route-map MAIN permit 40
match ip address 99
set tag 30
!
route-map MAIN deny 41
match tag 30
!
route-map EI permit 10
match ip address 50
!
route-map EI_1 permit 10
match ip address 50
set tag 101
!
route-map MAIN_1 deny 10
match tag 10
!
route-map MAIN_1 deny 20
match tag 20
!
route-map MAIN_1 deny 30
match tag 30
R2:
router eigrp 100
redistribute ospf 1
network 10.1.23.0 0.0.0.255
network 10.1.24.0 0.0.0.255
default-metric 400 20 255 1 1500
no auto-summary
!
router ospf 1
log-adjacency-changes
redistribute eigrp 100 subnets route-map MAIN
network 10.1.12.0 0.0.0.255 area 0
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
!
access-list 1 permit 10.4.0.0 0.0.0.255
access-list 1 permit 10.4.1.0 0.0.0.255
access-list 2 permit 10.4.2.0 0.0.0.255
access-list 2 permit 10.4.3.0 0.0.0.255
access-list 3 deny 10.4.4.0 0.0.0.255
access-list 50 deny 10.1.0.0 0.0.0.255
access-list 99 permit 10.1.24.0 0.0.0.255
access-list 99 permit 10.1.23.0 0.0.0.255
!
!
!
route-map MAIN permit 10
match ip address 1
set metric 100
set metric-type type-2
set tag 10
!
route-map MAIN permit 20
match ip address 2
set metric 200
set metric-type type-2
set tag 20
!
route-map MAIN deny 30
match ip address 3
!
route-map MAIN permit 40
match ip address 99
set metric 300
set metric-type type-2
set tag 30
!
R3 has filtered enabled to prevent routing loops from eigrp networks. But i cant make R4 and R2 to choose preferd path to R1 Loopback over R3
Solved! Go to Solution.
10-16-2012 07:16 AM
Hi Dima,
The loopback address at R1 is known both to R2 and R3 as OSPF internal network. If R3 redistributes this network into EIGRP and advertises it to R2, EIGRP will try to insert this route into R2's routing table using the administrative distance of 170 (as it is an EIGRP external route). However, the OSPF-learned route on R2 has an administrative distance of 110 and is therefore preferred. No change in the OSPF or EIGRP metrics is going to change this because the administrative distance is the first value that is used to break ties when different protocols try to insert the same network into the routing table.
What you could do is to modify the EIGRP configuration on R2 that it assigns an administrative distance of less than 110 to EIGRP external routes, e.g.:
R2:
router eigrp 100
distance eigrp 90 109
Would this be an option for you?
Best regards,
Peter
10-16-2012 07:16 AM
Hi Dima,
The loopback address at R1 is known both to R2 and R3 as OSPF internal network. If R3 redistributes this network into EIGRP and advertises it to R2, EIGRP will try to insert this route into R2's routing table using the administrative distance of 170 (as it is an EIGRP external route). However, the OSPF-learned route on R2 has an administrative distance of 110 and is therefore preferred. No change in the OSPF or EIGRP metrics is going to change this because the administrative distance is the first value that is used to break ties when different protocols try to insert the same network into the routing table.
What you could do is to modify the EIGRP configuration on R2 that it assigns an administrative distance of less than 110 to EIGRP external routes, e.g.:
R2:
router eigrp 100
distance eigrp 90 109
Would this be an option for you?
Best regards,
Peter
10-16-2012 10:29 AM
Yeah. You are right.
Thank you Peter. I have changed EX metric of EIGRP and i 've recieved D EX route.
Thanks a lot;)
10-16-2012 07:17 AM
Add below command under R2,
access-list 50 permit 10.1.0.0 0.0.0.255
May it will help u
Thnx.
Amit
*Please rate helpful info********
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide