I have the same problem even if I Disable-NetAdapterRdma
Switch embedded teaming on non RDMA supported NICS
Hello,
I am setting up a Hyper-V cluster environment between two Win 2022 hosts. I decided to use SET to create virtual NICs for clustering , live migration.. etc. The two 10gb physical NICs used for this virtual switch do not support RDMA. When I run the cluster validation wizard I receive the following warnings:
RDMA Enable/Disable settings across adapters associated with SET Switch 'VM_Switch' on Node 'Server1.XZY.com' are not consistent
Unable to verify that all all adapters associated with SET Switch 'VM_Switch' on Node 'Server2.XZY.com' are of the same RDMA Technology type, some adapters are reporting 'Device Default' or not reporting data at all.
Unable to verify that all adapters associated with SET Switch 'VM_Switch' across all nodes are of the same RDMA Technology type, some adapters are reporting 'Device Default' or not reporting data at all.
Why am I getting these warning?
Do I need RDMA NICs to properly use switch embedded teaming?
Will these warnings affect the creation of my cluster or can this be ignored since I'm not using RDMA?
2 answers
Sort by: Newest
-
-
Erik Tank 21 Reputation points
2022-04-01T23:39:00.743+00:00 I've had weird issues in 2022 as well. If you check - it MIGHT be enabled on your adapter even though it will be labeled "not supported" - it's just silly that it happens.
Disable-NetAdapterRdma -Name "MyAdapter"
Try running that to officially turn it off - I think you can use a wildcard as well * to turn it off on everything to be safe. Turning it off will avoid the validation from running that process/test and thus, not report any irregularities or errors. (I think)
I still cannot get my SET switch test to pass on my 3 node cluster, but everything works fine and I've seen countless others having the same issue... MS bug reported I guess, but no links sorry.
Hope this helps!