Weird Problems On Cisco 2610 Router

[tolgatanriverdi]

Hi In our company there is a 2610 router that connects two branches of our firm but more than 2 weeks there is a weird problem(we didnt change anything on it) router doesnt route some ip addresses

ip address of the router is 10.0.0.4

it has a static routes such as

ip route 0.0.0.0 0.0.0.0 10.0.0.6

ip route 62.41.66.0 255.255.255.0 212.50.38.49

ip route 172.16.0.0 255.255.0.0 10.0.0.6

ip route 192.168.1.0 255.255.255.0 1.0.0.2

ip route 212.50.38.100 255.255.255.252 1.0.0.2

but for example it doesnt route this ip address

62.244.241.54

when i ping this addres via this router it gives

10.0.0.4 : destination host unreacheable

does anyone know why can it be?

Thanks

[smothuku]

Hi ,

Have you checked the Firewall logs when you were trying to ping to 62.244.241.54.

Was it allowing icmp(policy) from router to reach 62.244.241.54.

Try to ping 10.0.0.6 first and then check the Firewall logs.

If there is a policy or icmp is allowed from your company's firewall , try the "EXTENDED PING" from router.

While posting the conversation you mentioned that """Hi In our company there is a 2610 router that connects two branches of our firm but more than 2 weeks there is a weird problem(****we didnt change anything on it) router doesnt route some ip addresses ""

Are you sure nothing was changed on firewall also ?

Thanks,

satish

[tolgatanriverdi]

Yes I'm sure nothing changed on firewall or router for that matter

Because when i changed the pc's(which i ping from) default gateway from this router to our firewall everything works fine

The router doesnt allow that 62.244.241.54 ip address

[Jon Marshall]

Could set the PC's default-gateway to be the router again and then ping

1) 62.182.1.10

2) 57.10.1.2

3) 156.11.1.2

And post results

Jon

[lgijssel]

Perhaps I shouldn't but this thread is becoming so bizarre that i cannot leave it;-)

One of the most important question has not yet been asked, that is: Where is your ping originating from?

The general expectation is that the routing table will select 10.0.0.6 as the next hop.

However, there is a slight chance that you are originating from an adress that matches acl 101 in which case you are policy routed to another device.

If so, you would also see something like "TTL expired in transit" when you look at the right spot.

regards,

Leo