We need more detailed information to be able to help.
Which version of vSAN do you use?
What do your vsan vmkernel port settings look like?
How did you configure the portgroup for vsan?
Do you use jumbo frames? And if so, are all components configured correctly?
Do you have beacon probing enabled?
1 person found this helpful
A few things I see:
This sounds like a misconfiguration between interfaces and switch. Could be port config, jumbo frames, etc. How are the ports on the switch configured? Trunk? Port channel?
Also, I would recommend having vSAN and vMotion on separate VLANS, as well as using NIOC since you are sharing the same interfaces for both types of traffic. I would actually separate the active interfaces for those two types of traffic. For example, vSAN traffic will have NIC1 active / NIC2 passive. For vMotion NIC2 active, and NIC1 passive. In case one fails, and there is contention when both are on the same NIC, NIOC will kick in to help prioritize vSAN traffic. vMotion can be very bursty, hence the recommendation for NIOC. Only use shares. Set vSAN to high and vMotion to Low or somewhere between low and normal.
Based on your description I would be inclined to say it is a misconfiguration somewhere... BUT I have also seen this behavior when there is a mismatch between Firmware and drivers on NICs. Firmware and drivers come in pairs/groups. I there are mismatched, you will see some weird behavior.
Hope this helps
Thank You for your reply, I found this as very helpful. Because I knew my configuration is fine, so I just focused on your last paragraph which says it can be related to NIC_Drivers/Firmware.
I contacted my vendor and got the NIC drivers/Firmware upgraded and issue stands resolved now. Thanks Again. @