One way Ping?!?

[Nay-Sayer]

I have an unusual problem that has me stumped. I have two nodes, the first is a VCenter server running on a Windows 2k8 box with an IP address of 192.68.182.108/24. The second is a Cisco B-Series blade attached to a 2900 series router with a management IP address of 192.168.210.12/24. From the VCenter server box, I can ping the gateway of the 192.168.210.0 network as well as nodes on that same network. From the B-Series blade I can ping the gateway of the 192.68.182.0 network, the VCenter server as well as other nodes on that same network. For some reason, the VCenter server box can not ping the B-Series blade. Pinging from the B-Series blade to the VCenter server box works, just not in the other direction. Any idea of what's going on here?

[Aaron O'Hare]

Is the vCenter's default gateway correct in Windows?

[Nay-Sayer]

Yes, the default gateway for the VCenter server box is configured correctly.

[Masoud Pourshabanian]

Hello,

If ping works one way, it means default gateways are correct. Do you have any access-list on Blade? VCenter has only one IP address? Activate ICMP debug on Blade then ping and check the log.

Debug IP ICMP

Terminal monitor

Masoud

[Dennis Mink]

Is it just ICMP that is not working between the vcentre box and the B-series?  or is it other traffic that is not flowing either? (run wireshark locally to see if you pick up ANY traffic at all from the vcentre server)

could be a heap of different thing

-local FW on the Bseries server

-wrong VLAN tags on the Virtual machine.

-ARP

-Mac table

[Nay-Sayer]

I can connect to the CIMC management service that's running on the B-Series but CIMC is on a different subnet than the esxi host.

The CIMC ip address is 192.168.211.11

The esxi ip addess is 192.168.210.12

[Jon Marshall]

Can you ping 192.168.210.12 from anywhere ?

Jon

[Nay-Sayer]

I can ping 192.168.210.12 from every other node on my network.

[Jon Marshall]

So your ICMP capture shows it responding with an ICMP echo reply.

Are there any acls etc. applied in the path between those servers ?

Jon

[Nay-Sayer]

No acls between the two.

[Nay-Sayer]

I opened a ssh seesion into the esxi host running on the B-Series blade and ran the tcpdump-uw -i vmk0 icmp command to capture incoming ICMP packets.  Here is the output received when sending a ping from the VCenter server box: 

17:26:28.274142 IP ls-vcenter.elasalle.int > cisco-ucse-esxi.elasalle.int: ICMP echo request, id 256, seq 9863, length 40
17:26:28.274262 IP cisco-ucse-esxi.elasalle.int > ls-vcenter.elasalle.int: ICMP echo reply, id 256, seq 9863, length 40
17:26:32.830651 IP ls-vcenter.elasalle.int > cisco-ucse-esxi.elasalle.int: ICMP echo request, id 256, seq 9864, length 40
17:26:32.830756 IP cisco-ucse-esxi.elasalle.int > ls-vcenter.elasalle.int: ICMP echo reply, id 256, seq 9864, length 40
17:26:37.830630 IP ls-vcenter.elasalle.int > cisco-ucse-esxi.elasalle.int: ICMP echo request, id 256, seq 9865, length 40
17:26:37.830753 IP cisco-ucse-esxi.elasalle.int > ls-vcenter.elasalle.int: ICMP echo reply, id 256, seq 9865, length 40
17:26:42.830445 IP ls-vcenter.elasalle.int > cisco-ucse-esxi.elasalle.int: ICMP echo request, id 256, seq 9866, length 40
17:26:42.830580 IP cisco-ucse-esxi.elasalle.int > ls-vcenter.elasalle.int: ICMP echo reply, id 256, seq 9866, length 40

Can someone interpret this?

[Aaron O'Hare]

The B series is showing a ping coming from Is-vcenter.elasalle.int and a ping reply from cisco-ucse.esxi.elasalle.int

This looks to be a successful and valid ICMP transaction.

-AO
Please rate useful posts and mark answers as "correct" if applicable.

[Nay-Sayer]

The ls-vcenter.elasalle.int node gives a "Request timed out" response when sending a ping to the cisco-ucse-esxi.elasalle.int node.

[Nay-Sayer]

While running a tracerout from the VCenter server box I get the following output from tcpdump-uw from the esxi host on the B-Series blade:

18:22:44.322851 IP truncated-ip - 10 bytes missing! cisco-ucse-esxi.elasalle.int > ls-vcenter.elasalle.int: ICMP echo reply, id 256, seq 10170, length 72