01-25-2017 09:55 AM - edited 03-08-2019 09:03 AM
in my topology all router are configured with ospf with area 10.My problem is that i am able to ping different router to eacha router but not able to ping clients.
01-25-2017 10:18 AM
It is not clear whether from a router you can ping to clients connected to that router. Can you clarify on this?
If a router is successful in ping to locally connected clients but fails to ping remote clients then most likely it is either a problem in routing or is a problem with the gateway configured on the clients. If a router is not successful in ping to locally connected clients then most likely the problem is a firewall on he client which does not allow ping.
HTH
Rick
01-25-2017 10:29 AM
hi rick sir thanks for kind support me.
I HAVE 4 ROUTER
R1-SERIAL0/0193.200.200.1/24
F0/0-10.10.30.1/8
CLIENTS 10.10.30.2 GW 10.10.30.1
R2-SERIAL 0/0 193.200.200.2/24
SERIAL0/1-194.200.210.1/24
FO-172.16.32.1
CLENTS-172.16.32.2 GW-172.16.32.1
R3-SERIAL 0/0 194.200.210.2 /24
SERIAL0/1 192.168.1.1/24
FO-172.16.30.1
CLEINTS-172.16.30.2 GW-172.16.30.1
R4-SERIAL 0/1 192.168.1.2/24
FO-172.16.31.1
CLINETS-172.16.31.1 HAVE GATEWAY 172.16.31.1
on router r1
Tracing the route to 192.168.1.2
1 193.200.200.2 38 msec 19 msec 15 msec
2 194.200.210.2 41 msec 47 msec 11 msec
3 192.168.1.2 23 msec 2 msec 1 msec
but when i try to ping his clinets then i am not able to ping.
Regards
Brij
01-25-2017 10:58 AM
Brij
You have provided additional details which may be helpful. But you have not answered the question that I asked. You have demonstrated connectivity between the serial interfaces of r1 and r4. What I asked is whether r1 is able to ping any client in the 10.10.30 network. Would you please answer that question?
HTH
Rick
01-25-2017 10:33 PM
Dear Rich Sir,
I am able to ping 10.10.30. network fro R1 and his clients :-
Below Is route MAp
C 10.0.0.0/8 is directly connected, FastEthernet0/0
O 172.16.0.0/16 [110/65] via 193.200.200.2, 00:02:56, Serial1/0
O 192.168.1.0/24 [110/192] via 193.200.200.2, 00:02:46, Serial1/0
C 193.200.200.0/24 is directly connected, Serial1/0
O 194.200.210.0/24 [110/128] via 193.200.200.2, 00:02:56, Serial1/0
indore#
indore#ping 10.10.30.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.30.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/5/14 ms
indore#ping 10.10.30.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.30.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms
indore#ping 10.10.30.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.30.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/15 ms
regards
Brij
01-26-2017 06:20 AM
Brij
Thank you for the additional information. Seeing the content of the routing table is helpful and does show that r1 appears to have valid routes for the LAN subnets of the other routers. And it is especially helpful to see that r1 is successful in ping to hosts in its own LAN. So that establishes that it is not an issue with a firewall on the host preventing ping. So we need to investigate the possibility of a mistake in the gateway for the hosts. Would you post the output of ipconfig from at least one of the hosts in the LAN of r1?
HTH
Rick
01-26-2017 09:32 AM
Rich sir thank you.Sir can u please guide me as student i will do as you say i have to became like you.
Sir as per topology clients ip are as below :-
FastEthernet0 Connection:(default port)
Link-local IPv6 Address.........: FE80::2E0:B0FF:FE13:592B
IP Address......................: 10.10.30.2
Subnet Mask.....................: 255.0.0.0
Default Gateway.................: 10.10.30.1
We also able to ping serial interface of R1-193.200.200.1
01-26-2017 10:18 AM
Brij
Thank you for the information confirming configuration of the gateway on the client. It is good that you can ping the serial interface. Can you ping the serial interface of the next router at 193.200.200.2?
HTH
Rick
01-26-2017 10:23 AM
rick sir,
i am able to ping every serial interface of each router :-
PC>ping 192.168.1.2
Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time=29ms TTL=252
Reply from 192.168.1.2: bytes=32 time=37ms TTL=252
Reply from 192.168.1.2: bytes=32 time=3ms TTL=252
Reply from 192.168.1.2: bytes=32 time=4ms TTL=252
Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 37ms, Average = 18ms
PC>tracert 192.168.1.2 (r4 router--we trace from r1 lan clinets)
Tracing route to 192.168.1.2 over a maximum of 30 hops:
1 0 ms 0 ms 0 ms 10.10.30.1
2 0 ms 0 ms 0 ms 193.200.200.2
3 0 ms 1 ms 2 ms 194.200.210.2
4 1 ms 2 ms 2 ms 192.168.1.2
regards
Brijendra
01-26-2017 10:36 AM
Brijendra
Thank you for the additional information. It is helpful to see that ping and tracert to the remote router are successful. In looking at the output of your route table from an earlier post I notice something that surprises me. This line of output
O 172.16.0.0/16 [110/65] via 193.200.200.2, 00:02:56, Serial1/0
I would have expected to see routes for the three subnets (172.16.30, 17216.31, 172.16.32) but see only the summary for 172.16.0.0. Can you post the configuration of OSPF from r2? (and perhaps from the other routers also might be helpful)
HTH
Rick
01-26-2017 11:15 AM
rick sir,
below data are from R2 :-
pithamput#show ip ospf da
pithamput#show ip ospf database
OSPF Router with ID (194.200.210.1) (Process ID 10)
Router Link States (Area 10)
Link ID ADV Router Age Seq# Checksum Link count
193.200.200.1 193.200.200.1 35 0x80000004 0x007d7b 3
194.200.210.1 194.200.210.1 35 0x80000006 0x005328 5
192.168.1.2 192.168.1.2 34 0x80000004 0x00b72d 3
194.200.210.2 194.200.210.2 34 0x80000006 0x00e44f 5
pithamput#show ip os
pithamput#show ip ospf n
pithamput#show ip ospf neighbor
Neighbor ID Pri State Dead Time Address Interface
193.200.200.1 0 FULL/ - 00:00:30 193.200.200.1 Serial0/0
194.200.210.2 0 FULL/ - 00:00:36 194.200.210.2 Serial0/1
I configure with AREA 10 and process ID 10 With All routers
R2---Route information :-
O 10.0.0.0/8 [110/65] via 193.200.200.1, 00:02:33, Serial0/0
C 172.16.0.0/16 is directly connected, FastEthernet0/0
O 192.168.1.0/24 [110/128] via 194.200.210.2, 00:02:23, Serial0/1
C 193.200.200.0/24 is directly connected, Serial0/0
C 194.200.210.0/24 is directly connected, Serial0/1
--------------------------------------------------------------------------------------------------------R3-Route
O 10.0.0.0/8 [110/129] via 194.200.210.1, 00:02:58, Serial0/0
C 172.16.0.0/16 is directly connected, FastEthernet0/0
C 192.168.1.0/24 is directly connected, Serial0/1
O 193.200.200.0/24 [110/128] via 194.200.210.1, 00:02:58, Serial0/0
C 194.200.210.0/24 is directly connected, Serial0/0
show ip ospf database
OSPF Router with ID (194.200.210.2) (Process ID 10)
Router Link States (Area 10)
Link ID ADV Router Age Seq# Checksum Link count
192.168.1.2 192.168.1.2 275 0x80000004 0x00b72d 3
194.200.210.2 194.200.210.2 274 0x80000006 0x00e44f 5
194.200.210.1 194.200.210.1 274 0x80000006 0x005328 5
193.200.200.1 193.200.200.1 275 0x80000004 0x007d7b 3
bombay#show ip ospf ne
bombay#show ip ospf neighbor
Neighbor ID Pri State Dead Time Address Interface
194.200.210.1 0 FULL/ - 00:00:38 194.200.210.1 Serial0/0
192.168.1.2 0 FULL/ - 00:00:36 192.168.1.2 Serial0/1
---------------------------------------------------------------------------------------------------------R4- Route
O 10.0.0.0/8 [110/193] via 192.168.1.1, 00:03:40, Serial0/0
C 172.16.0.0/16 is directly connected, FastEthernet0/0
C 192.168.1.0/24 is directly connected, Serial0/0
O 193.200.200.0/24 [110/192] via 192.168.1.1, 00:03:40, Serial0/0
O 194.200.210.0/24 [110/128] via 192.168.1.1, 00:03:40, Serial0/0
kolkata#show ip ospf database
OSPF Router with ID (192.168.1.2) (Process ID 10)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count
192.168.1.2 192.168.1.2 397 0x80000001 0x00b0da 0
Summary Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
172.16.0.0 192.168.1.2 393 0x80000001 0x00ee46
192.168.1.0 192.168.1.2 373 0x80000002 0x002e19
194.200.210.0 192.168.1.2 373 0x80000003 0x000f03
193.200.200.0 192.168.1.2 373 0x80000004 0x000bd0
10.0.0.0 192.168.1.2 373 0x80000005 0x0071b1
Router Link States (Area 10)
Link ID ADV Router Age Seq# Checksum Link count
192.168.1.2 192.168.1.2 388 0x80000004 0x00b72d 3
193.200.200.1 193.200.200.1 388 0x80000004 0x007d7b 3
194.200.210.2 194.200.210.2 383 0x80000006 0x00e44f 5
194.200.210.1 194.200.210.1 383 0x80000006 0x005328 5
regards
brij
01-26-2017 11:51 AM
brij
We are making progress. We do not have the complete answer yet but we are getting closer. What I find particularly interesting is this line of output from the route table
C 172.16.0.0/16 is directly connected, FastEthernet0/0
Each router that has this will consider 172.16.0.0 to be locally connected. I would have expected the locally connected to be 172.13.30.0 or 172.16.31.0, or 172.16.32.0.
As the next step in investigating this problem can you post the interface configuration for each of the LAN interfaces (FastEth0/0)?
HTH
Rick
01-26-2017 10:03 PM
Dear Rich Sir,
R1 Lan interface deatils :-
FastEthernet0/0 is up, line protocol is up (connected)
Internet address is 10.10.30.1/8
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is disabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP Fast switching turbo vector
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Probe proxy name replies are disabled
Policy routing is disabled
Network address translation is disabled
BGP Policy Mapping is disabled
Input features: MCI Check
WCCP Redirect outbound is disabled
WCCP Redirect inbound is disabled
WCCP Redirect exclude is disabled
============================================================
R2
pithamput#show ip interface fastEthernet 0/0
FastEthernet0/0 is up, line protocol is up (connected)
Internet address is 172.16.32.1/16
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is disabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP Fast switching turbo vector
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Probe proxy name replies are disabled
Policy routing is disabled
Network address translation is disabled
BGP Policy Mapping is disabled
Input features: MCI Check
WCCP Redirect outbound is disabled
WCCP Redirect inbound is disabled
WCCP Redirect exclude is disabled
=============================================================
r3
FastEthernet0/0 is up, line protocol is up (connected)
Internet address is 172.16.30.1/16
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is disabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP Fast switching turbo vector
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
Router Discovery is disabled
IP output packet accounting is disabled
IP access violation accounting is disabled
TCP/IP header compression is disabled
RTP/IP header compression is disabled
Probe proxy name replies are disabled
Policy routing is disabled
Network address translation is disabled
BGP Policy Mapping is disabled
Input features: MCI Check
WCCP Redirect outbound is disabled
WCCP Redirect inbound is disabled
WCCP Redirect exclude is disabled
=============================================================
R4
kolkata#show ip inter
kolkata#show ip interface fa
kolkata#show ip interface fastEthernet 0/0
FastEthernet0/0 is up, line protocol is up (connected)
Internet address is 172.16.31.1/16
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is disabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP Fast switching turbo vector
IP multicast fast switching is disabled
IP multicast distributed fast switching is disabled
Router Discovery is disabled
Brij
01-31-2017 07:10 AM
Brij
Thank you for the additional information. It does show what is causing your issue. The mask used for the LAN interfaces is not correct. Here is what is on r2. r3 and r4 are similar.
Internet address is 172.16.32.1/16
So each of the routers believes that it is connected to network 172.16.0.0/16. So when r2 receives an OSPF advertisement from r3 for 172.16.0.0 it believes that it already has that network as a connected network and it does not put the network from r3 (or from r4) into its routing table. If you make the mask on the interface into 255.255.255.0 then things should work as you expect.
HTH
Rick
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