search

CiscoDevNet / Hyperflex-Hypercheck

Perform pro-active self checks on your Hyperflex cluster to ensure stability and resiliency
MIT License
27 stars 17 forks source link

VMotion vmkping failure false positive #6

Closed sttardy closed 4 years ago

sttardy commented 4 years ago

ESXi VMotion vmk interfaces are often "silent hosts" causing transient / temporary / false positive failures. The VMotion vmkping test should vmkping to/from ALL hosts to assure proper ARP/MAC learning before conducting actual VMotion vmkping test.

HX_Tool_MainReport. . .txt file shows:

| vmkping -I vmk2 -c 3 -d -s 8972 -i 0.01 192.0.2.102 | FAIL                                                                                     |          |

Manually executing same command on same host works successfully.

HXTool. . .log file shows:

<timestamp> - HX_TOOL - INFO - Executing command: vmkping -I vmk2 -c 3 -d -s 8972 -i 0.01 192.0.2.102
<timestamp> - HX_TOOL - INFO - ************************ CMD OUTPUT ************************
<timestamp> - HX_TOOL - INFO - Not able to run the command
<timestamp> - HX_TOOL - INFO - *************************************************************

Workaround: Actively execute vmkping to/from all ESXi hosts to other vmotion interfaces while executing HyperCheck.

avshukla commented 4 years ago

Thanks Steven. We were informed about this once before. Good suggestion till we get this implemented please use the work around in cases where it fails.