Change to ICMP ping response behavior in ESXi 5.1 and ESXi 5.5
Article ID: 321229
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
In ESXi 5.1 and ESXi 5.5, it is no longer possible to ping VMkernel interfaces other than the management VMkernel interface from client machines in other networks and VLANs.
In ESXi 5.1 and ESXi 5.5, it is no longer possible to ping VMkernel interfaces other than the management VMkernel interface from client machines in other networks and VLANs.
Environment
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.5
VMware vSphere ESXi 5.5
Cause
This behavior is a consequence of changes introduced in ESXi 5.1 and maintained in ESXi 5.5. ICMP Echo replies are now only sent back on the same interface that the Echo Request was received on.
This behavior was introduced because it is desired by multi-pathing capable applications. For example, an iSCSI or NFS storage filer may use ICMP pings to determine whether a given VMkernel is reachable or not. For this functionality to work as designed, the host must respond to these echo requests on the same VMkernel interface that they are received on.
There is no change in behavior when pinging from a source within the same subnet as the VMkernel interface, only when the ICMP Echo Reply must be routed to get back to the source.
In previous versions of ESXi, pings originating from a different subnet would simply be replied to based on the host's routing table, normally through the default gateway defined for the management interface, vmk0.
Note: This behavior is applicable only to ICMPv4 traffic. All other forms of TCP/IP traffic are routed normally via the host's routing table.
This behavior was introduced because it is desired by multi-pathing capable applications. For example, an iSCSI or NFS storage filer may use ICMP pings to determine whether a given VMkernel is reachable or not. For this functionality to work as designed, the host must respond to these echo requests on the same VMkernel interface that they are received on.
There is no change in behavior when pinging from a source within the same subnet as the VMkernel interface, only when the ICMP Echo Reply must be routed to get back to the source.
In previous versions of ESXi, pings originating from a different subnet would simply be replied to based on the host's routing table, normally through the default gateway defined for the management interface, vmk0.
Note: This behavior is applicable only to ICMPv4 traffic. All other forms of TCP/IP traffic are routed normally via the host's routing table.
Resolution
When performing network troubleshooting with ESXi 5.5 or ESXi 5.1, ping VMkernel interfaces from a source machine in the same subnet.
For example, ping an ESXi 5.5 or 5.1 host's iSCSI VMkernel interface from the SAN itself, or from another ESXi 5.5 or 5.1 host with a VMkernel interface in the same subnet/VLAN.
For example, ping an ESXi 5.5 or 5.1 host's iSCSI VMkernel interface from the SAN itself, or from another ESXi 5.5 or 5.1 host with a VMkernel interface in the same subnet/VLAN.
For further information see KB 2034971 Understanding Internet Control Message Protocol redirects.
Additional Information
Feedback
Yes
No
Powered by
