continual NTCCheckResult messages in vmkernel log - issue

[tarquel]

Hi all

Dont suppose anyone knows why we'd be getting the following about every minute on a vsphere 5.1 U1 host (updated fully as of a few days ago).

2013-08-13T09:44:37.458Z cpu0:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-2!

2013-08-13T09:44:37.476Z cpu0:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-3!

2013-08-13T09:44:44.788Z cpu0:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-1!

2013-08-13T09:45:37.340Z cpu0:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-0!

2013-08-13T09:45:37.462Z cpu0:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-2!

2013-08-13T09:45:37.480Z cpu0:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-3!

2013-08-13T09:45:44.790Z cpu0:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-1!

2013-08-13T09:46:37.341Z cpu6:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-0!

2013-08-13T09:46:37.465Z cpu6:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-2!

2013-08-13T09:46:37.484Z cpu6:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-3!

2013-08-13T09:46:44.791Z cpu6:8802)TeamCheck: NTCCheckResult:930: Please check connectivity on DvsPortset-1!

For info, its been cleanly built and tweaked with the usual things like disabling delayedack etc...  hardware all running latest firmware and vmware drivers for the nics are the latest too.

Have set up Distributed Switches and the host is all setup on them and  all seems to be working well (have a few test vm's running well in this test dc we have for this new vds setup), but just wondering what this message is all about as there doesnt appear to be anything in the vsphere client or on the vsphere web client regarding it - nor does google shed anything regarding it either alas.

Cheers.

[tarquel · Accepted solution]

Just to update this but found the reason I think.

Its down to enabling the Failover Health Check for the four VDS's i have setup but only having one host attached to them i think.

Disabling the check removed the error so its down to that check that's displaying the message and indeed, the reason.

Hope that helps others searching for that specific message