(Ticket 8: Redistribution of EIGRP to OSPF)
Scenario: The implementation group has been using the test bed to do a 'proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing schemes, DHCP services, layer 2 connectivity, FHRP services, and, device security, a trouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address.

Figure 1

Figure 2
Trouble Ticket Statement
Client 1 is not able to reach the WebServer. Initial troubleshooting shows that DSW1 can ping the Fa0/1 interface of R4 but not the s0/0/0/0.34 interface.
Configuration on DSW1
router eigrp 10
network 10.1.4.4 0.0.0.0
network 10.2.1.1 0.0.0.0
network 10.2.4.13 0.0.0.0
no auto-summary
Configuration on DSW2
router eigrp 10
network 10.1.4.8 0.0.0.0
network 10.2.2.1 0.0.0.0
network 10.2.4.14 0.0.0.0
no auto-summary
Configuration on R4
router eigrp 10
network 10.1.4.5 0.0.0.0
no auto-summary
redistribute ospf 1 metric 100 10 255 1 1500 route-map OSPF_to_EIGRP
!
router ospf 1
network 10.1.1.8 0.0.0.0 area 34
redistribute eigrp 10 subnets
!
route-map OSPF->EIGRP
match ip address 1
!
access-list 1 permit 10.0.0.0 0.255.255.255
access-list 1 permit 209.0.0.0 0.255.255.255
The Fault Condition is related to which technology?