Check from Client1.
Client1#sh ip int brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 10.2.1.3 YES DHCP up up
FastEthernet0/1 unassigned YES NVRAM administratively down down
IP address 10.2.1.3 has assigned. Next step is start ping to 10.1.1.1
Client1#ping 10.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
U.U.U
Success rate is 0 percent (0/5)
Ping failed to reach 10.1.1.1
-----------------------
Try ping to 10.1.4.5 (R4).
Client1#ping 10.1.4.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.4.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/55/80 ms
Ping reach to 10.1.4.5 but failed in R4's exit point 10.1.1.10
Here are the possible cause.
- Route redistribution from OSPF to EIGRP
- Wrong EIGRP AS number
Let's check in R4 first. Check EIGRP neighbour first. Font two neighbours, DSW1 and DSW2. So, R4's EIGRP is working well.
R4#sh ip eigrp neighbors
IP-EIGRP neighbors for process 10
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 10.1.4.10 Fa0/1 14 00:10:20 72 432 0 22
0 10.1.4.6 Fa0/0 11 00:10:26 39 234 0 19
--------------------------
Check OSPF neighbour again and it's also working well with R3.
R4#sh ip ospf neighbor
Neighbor ID Pri State Dead Time Address Interface
3.3.3.3 0 FULL/ - 00:00:39 10.1.1.9 Serial1/0.34
---------------
Check routing table again.
Gateway of last resort is 10.1.1.9 to network 0.0.0.0
4.0.0.0/32 is subnetted, 1 subnets
C 4.4.4.4 is directly connected, Loopback4
10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks
D 10.2.4.12/30 [90/30720] via 10.1.4.10, 00:12:29, FastEthernet0/1
[90/30720] via 10.1.4.6, 00:12:29, FastEthernet0/0
C 10.1.1.8/30 is directly connected, Serial1/0.34
C 10.1.4.8/30 is directly connected, FastEthernet0/1
D 10.2.1.0/24 [90/30720] via 10.1.4.10, 00:12:29, FastEthernet0/1
[90/30720] via 10.1.4.6, 00:12:30, FastEthernet0/0
D 10.2.2.0/24 [90/30720] via 10.1.4.10, 00:12:30, FastEthernet0/1
[90/30720] via 10.1.4.6, 00:12:30, FastEthernet0/0
C 10.1.4.4/30 is directly connected, FastEthernet0/0
O*IA 0.0.0.0/0 [110/65] via 10.1.1.9, 00:11:25, Serial1/0.34
----------------
None of the following networks are appearing in R4 but all can be reach via serial1.0.34 as OSPF is configured with NSSA, only default route is appearing in routing table.
10.1.1.8/30, 10.1.1.4/30 and 10.1.1.0/30
It can conclude that there is problem in redistribution routes.
Check how the default route is appearing in routing table. 10.1.1.9 can be reach from 3.3.3.3 but no route-map is appearing in default route 0.0.0.0
R4#sh ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
Known via "ospf 1", distance 110, metric 65, candidate default path, type inter area
Redistributing via eigrp 10
Last update from 10.1.1.9 on Serial1/0.34, 00:14:56 ago
Routing Descriptor Blocks:
* 10.1.1.9, from 3.3.3.3, 00:14:56 ago, via Serial1/0.34
Route metric is 65, traffic share count is 1
-------------------------------
It's time to check running config of R4 for redistribution. Here is R4's EIGRP process. It is redistributed route from OSPF with route map named "EIGRP->OSPF.
router eigrp 10
redistribute ospf 1 route-map EIGRP->OSPF
network 10.1.4.4 0.0.0.3
network 10.1.4.8 0.0.0.3
no auto-summary
Let's check route map EIGRP->OSPF in details.
route-map EIGRP_OSPF permit 10
set metric 102400 1000 128 1 1500
set tag 10
---------------
Finally, it's because of wrong route map named "EIGRP_OSPF"
Changed to correct route map name and check routing table again.
R4(config)#router eigrp 10
R4(config-router)#no redistribute ospf 1 route-map EIGRP->OSPF
R4(config-router)#redistribute ospf 1 route-map EIGRP_OSPF
R4(config-router)#^Z
------------------------------------
R4#sh ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
Known via "ospf 1", distance 110, metric 65, candidate default path, type inter area
Redistributing via eigrp 10
Advertised by eigrp 10 route-map EIGRP_OSPF
Last update from 10.1.1.9 on Serial1/0.34, 00:20:56 ago
Routing Descriptor Blocks:
* 10.1.1.9, from 3.3.3.3, 00:20:56 ago, via Serial1/0.34
Route metric is 65, traffic share count is 1
-------------
Checking route to 0.0.0.0 (default route) is showing now that it's advertised by route-map EIGRP_OSPF.
So, the fault device is R4 in route redistribution and can fix by changing the route-map name.
No comments:
Post a Comment