vxverify failure message vmk_tag: vmk2 shouldn't have vSAN or vMotion

[RobMacKinnon]

I'm running an old version of vxRail manager with internal vCenter. I recently ran vxveriy to verify I'm ready to go from 4.7.540 - 4.7.560. The only failure was on all 4 hosts: vmk_tag: vSAN or vMotion shouldn't be run on vmk2 (paraphrasing).

Thing is, the vSAN serivice has been running on vmk2 since the systems inception and 2 subsequent upgrades. 

My question is this: is it safe to ignore this failure message.? Since my version level is so old, official Broadcom support won't touch it. Even though I have an up-to-date maintenance contract.

TIA

[NickF123]

This is more a question for Dell than VMware/Broadcom, do your physical hosts still have support on them (which should include VxRail software support)?  Also is your environment actually VCF on VxRail or just pure VxRail? I guess VxRail 4.7x aligns with a VCF on VxRail v3.x release - is there a reason you can't go to VCF 4.x or 5.x? (VxRail 7.x/8.x)?

Is the issue you're seeing an error or warning? I usually ignore some warnings from vcfverify/vxverify as it flags up a lot of rubbish but any errors you almost always need to resolve before upgrading.