The interface IP is the same subnet as the VLAN IP of the switch directly connected to it but RHEL server cannot ping it. The server can however ping the other servers connected to the same VLAN of the same subnet. Why is that?
I tried connecting a.. ehhrmm... windows machine to the switch, used an IP of the same subnet and I can ping the VLAN IP ok.


Interface details:
eth0 Link encap:Ethernet HWaddr 00:21:5E:74:83:B9
inet addr:10.251.47.169 Bcast:10.251.47.191 Mask:255.255.255.192
inet6 addr: fe80::221:5eff:fe74:83b8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:689 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:32212 (31.4 KiB) TX bytes:90480 (88.3 KiB)
Interrupt:169 Memory:ce000000-ce012100

'route -n' output:
Destination Gateway Genmask Flags Metric Ref Use Iface
10.251.47.0 0.0.0.0 255.255.255.240 U 0 0 0 eth1
10.251.47.128 0.0.0.0 255.255.255.192 U 0 0 0 eth0
10.251.21.0 10.251.47.190 255.255.255.0 UG 0 0 0 eth0
10.251.25.0 10.251.47.190 255.255.255.0 UG 0 0 0 eth0
172.16.140.0 172.17.1.254 255.255.255.0 UG 0 0 0 eth2
172.17.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2

'arp -a' output:
? (172.17.1.80) at 00:07:85:17:82:15 [ether] on eth2
? (172.17.1.254) at 00:21:59:CF:1B:80 [ether] on eth2
? (172.17.1.21) at 00:15:17:B0:72:28 [ether] on eth2
? (172.17.1.41) at 00:21:5E:70:1B:2E [ether] on eth2

eth2, 172.17.1.21, is connected to the same switch but on a different VLAN. Why is the connection of eth0 to switch not shown in arp -a?

I'm using a Juniper Ex4200, and the VLAN IP is 10.251.47.190. I cannot ping this IP but when I add it to the ARP table via "arp -s 10.251.47.190 <mac address of switch>", I can ping it.

And I can ping other servers connected to the same VLAN, e.g., 10.251.47.170.

I do not have to add the VLAN IP to the interface's ARP table all the time to be able to ping it don't I?? They're on the same subnet and directly connected!

Thanks in advance.

is the iptables enabled on your RH box? Try iptables -F and then ping again.

If that still does not work then can you sniff the traffic using wireshark to see what is happening?

My thinking is that if you replaced the box with another and it worked i would say that the RH system is sending icmp traffic but that same traffic is being dropped when the response is returned to the RH system