Route based on physical NIC load & failback

Ran into an interesting little problem involving routebased on physical NIC load & failback. With all the other NIC teaming method, if failback is set to no, it'll ignore the nic when it comes back online until the VM is rebooted. Physical NIC load is different. It's dynamic. It shouldn't care what failback is set to (I think). Anyone ever seen any documentation stating one way or other involving physical NIC load & failback?
2018 Certification Goals: Maybe VMware Sales Cert
"Simplify, then add lightness" -Colin Chapman
"Simplify, then add lightness" -Colin Chapman
Comments
As far as I understand - if you set the order to nic0/nic1/nic2, and nic0's load is to high, it should fail back to nic1 once it is backup ...
I believe failback should be "no". Physical nic load checks the load on the nic every 30 sec, so when a failed nic comes back online, it should wait 30 sec, check the load on the nics and balance the load across the nics accordingly. By introducing a 30 sec wait buffer, it can help mitigate network flapping.
The wrinkle in this is what does physical nic load algorithm do when 1 nic fails and it's down to 1 nic? Does it keep checking the nic loads every 30 sec?
Too bad I don't have a lab I could test it against. It's a simple enough test.
"Simplify, then add lightness" -Colin Chapman
Good point, especially without portfast.
Would you consider this a VCDX defense type question or too easy of a problem?
"Simplify, then add lightness" -Colin Chapman