I can ping but I can't pong

Answered Question
Aug 16th, 2007

I am having weird communication problems.

PC 1

IP 172.30.66.2

SM 255.255.0.0

GW 172.30.4.70

PC 2

IP 10.30.0.12

SM 255.255.224.0

GW 10.30.30.70

If I ping from PC 1 (or any pc on that vlan):

Ping 172.30.4.33 OK

Ping 172.30.4.70 OK

Ping 172.30.4.63 OK

Ping 10.30.30.33 Request timed out.

Ping 10.30.30.70 Request timed out.

Ping 10.30.30.63 OK

If I ping from PC 2 (or any pc on that vlan):

Ping 172.30.4.33 OK

Ping 172.30.4.70 OK

Ping 172.30.4.63 OK

Ping 10.30.30.33 ok

Ping 10.30.30.70 ok

Ping 10.30.30.63 OK

Router 1

interface Vlan1

description Administration

ip address 172.30.4.33 255.255.0.0

no ip redirects

ip route-cache flow

standby ip 172.30.4.70

standby priority 150

standby preempt delay sync 0

standby name fensw-cls01

interface Vlan6

description Usine

ip address 10.30.30.33 255.255.224.0

no ip redirects

ip route-cache flow

standby 1 ip 10.30.30.70

standby 1 priority 100

standby 1 preempt

standby 1 name VLAN6-HSRP

This is the output of sh ip route for both vlan:

C 10.30.0.0/19 is directly connected, Vlan6

C 172.30.0.0/16 is directly connected, Vlan1

sh standby

Vlan1 - Group 0

Local state is Active, priority 150, may preempt

Preemption delayed at most a further 0 secs for syncs

Hellotime 3 sec, holdtime 10 sec

Next hello sent in 0.054

Virtual IP address is 172.30.4.70 configured

Active router is local

Standby router is 172.30.4.63 expires in 8.536

Virtual mac address is 0000.0c07.ac00

1 state changes, last state change 23:51:59

IP redundancy name is "fensw-cls01" (cfgd)

Vlan6 - Group 1

Local state is Standby, priority 100, may preempt

Hellotime 3 sec, holdtime 10 sec

Next hello sent in 0.330

Virtual IP address is 10.30.30.70 configured

Active router is 10.30.30.63, priority 200 expires in 8.724

Standby router is local

1 state changes, last state change 23:51:57

IP redundancy name is "VLAN6-HSRP" (cfgd)

Router 2

interface Vlan1

ip address 172.30.4.63 255.255.0.0

no ip redirects

ip route-cache flow

standby ip 172.30.4.70

standby priority 100

standby preempt delay sync 0

standby name fensw-cls01

interface Vlan6

ip address 10.30.30.63 255.255.224.0

no ip redirects

ip route-cache flow

standby 1 ip 10.30.30.70

standby 1 priority 200

standby 1 preempt

standby 1 name VLAN6-HSRP

This is the output of sh ip route for both vlan:

C 10.30.0.0/19 is directly connected, Vlan6

C 172.30.0.0/16 is directly connected, Vlan1

sh standby

Vlan1 - Group 0

Local state is Standby, priority 100, may preempt

Preemption delayed at most a further 0 secs for syncs

Hellotime 3 sec, holdtime 10 sec

Next hello sent in 1.032

Virtual IP address is 172.30.4.70 configured

Active router is 172.30.4.33, priority 150 expires in 9.280

Standby router is local

4 state changes, last state change 23:57:23

IP redundancy name is "fensw-cls01" (cfgd)

Vlan6 - Group 1

Local state is Active, priority 200, may preempt

Hellotime 3 sec, holdtime 10 sec

Next hello sent in 1.052

Virtual IP address is 10.30.30.70 configured

Active router is local

Standby router is 10.30.30.33 expires in 9.936

Virtual mac address is 0000.0c07.ac01

2 state changes, last state change 1w3d

IP redundancy name is "VLAN6-HSRP" (cfgd)

Any idea were my problem could be?

I have this problem too.
0 votes
Correct Answer by binhkdinh about 9 years 3 months ago

we had two routers in the same cluster group and directly connected. If you don't have the same situation, then your problems must be something else I think. -Binh

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
glen.grant Thu, 08/16/2007 - 07:05

I would say your devices on 10.30.30.33 and .70 have incorrect or missing default gateway . if you ping from pc1 on 172 net they won't reply . If you ping from pc2 and the same subnet they will because you don't need a default gateway to ping anything on the same subnet.

msaulnier Thu, 08/16/2007 - 07:44

Pc1 and Pc2 can ping each other no problems there.

I double checked the gateway

Pc1 is set to 172.30.4.70

Pc2 is set to 10.30.30.70

lamav Tue, 08/21/2007 - 11:43

This has nothign to do with routing because you cant even PING the hosts from within the same subnet.

Besides checking whether a personal FW is installed and active on the PCs,

have you tried runnning any PING tests from the hosts themselves?

Can those hosts PING their default gateways?

Is the IP information (address, mask, DG, etc) configured correctly on those PCs?

Do you see the MAC addresses of those PCs in the local access switch's CAM/mac address table?

Are the switchports that those PCs are connected to in an "up, up" state?

Just a few things to check...

HTH

binhkdinh Tue, 08/21/2007 - 12:32

Marc, do you happen to use "cluser" in your configs? If yes, try to add "routing-redundancy" to the end of "cluster standby-group ...":

Example:

cluster standby-group my_hsrp routing-redundancy

We had similar problems a few months back, and "routing-redundancy" made it work.

-BD

msaulnier Thu, 08/23/2007 - 07:38

Yes, we are using cluster. But the 2 are not in the same cluster group. I tried this :

cluster standby-group fensw-cls01 Routing-redundancy

but I got this error:

%ERROR: Cluster is already bound. Please unbind first.

I will try to unbind and rebind the cluster.

Binhkdinh, are 2 device in the same group ?

Correct Answer
binhkdinh Thu, 08/23/2007 - 08:59

we had two routers in the same cluster group and directly connected. If you don't have the same situation, then your problems must be something else I think. -Binh

msaulnier Thu, 08/23/2007 - 09:31

I disabled the cluster and now every thing is ok ! Thanks !

Actions

This Discussion