vSAN Skyline Health alarm: vMotion: Basic (unicast) connectivity check
Article ID: 398426
Updated On:
Products
Issue/Introduction
- In vCenter UI,
Cluster > Monitor > vSAN > Skyline healthshows Network alarm as below:vMotion: Basic (unicast) connectivity check
- Click on the Troubleshoot option in the health warning will show the host which is unable to communicate with other hosts in the cluster.
- Pings to the vMotion network of other hosts in the cluster will fail with 100% packet loss.
[Host-01:~] vmkping -I vmkX 192.168.##.## -S vmotionPING 192.168.##.## (##.###.##.###): 56 data bytes
--- 192.168.##.## ping statistics ---3 packets transmitted, 0 packets received, 100% packet loss
- where 'vmkX' is the vmkernel adaptor used for vMotion.
Environment
VMware vSAN (All Versions)
Cause
- This issue could be caused due to an IP conflict of the vMotion IP with any other device in the environment.
- /var/run/log/vmkernel.log reports that another device in the network have the same IP address of the VMkernel adaptor that is tagged for the vMotion traffic. It will also provide the MAC address of the other device.
YYYY-MM-DDTHH:MM:SS.###Z cpu78:2098609)Tcpip_Vmk: 124: arp: aa:bb:cc:dd:ee:ff is using my IP address 192.168.xx.xx on vmkX!YYYY-MM-DDTHH:MM:SS.###Z cpu78:2098609)Tcpip_Vmk: 124: arp: aa:bb:cc:dd:ee:ff is using my IP address 192.168.xx.xx on vmkX!YYYY-MM-DDTHH:MM:SS.###Z cpu78:2098609)Tcpip_Vmk: 124: arp: aa:bb:cc:dd:ee:ff is using my IP address 192.168.xx.xx on vmkX!YYYY-MM-DDTHH:MM:SS.###Z cpu78:2098609)Tcpip_Vmk: 124: arp: aa:bb:cc:dd:ee:ff is using my IP address 192.168.xx.xx on vmkX!YYYY-MM-DDTHH:MM:SS.###Z cpu78:2098609)Tcpip_Vmk: 124: arp: aa:bb:cc:dd:ee:ff is using my IP address 192.168.xx.xx on vmkX!
Resolution
Engage the network team to further investigate the duplicate IP conflict issues.
Additional Information
Feedback
