I've seen this happen a few times in the past with both 2008 R2 and 2012, and have resolved it using a couple of different methods.
The first and least disruptive is to disable the interface that the traffic is currently going over to force a failover to the second adapter. After traffic is going over the second adapter, bring the first back online and traffic will balance across the two. Can't offer a real explanation for why it works, just that it has in all but two instances.
The two times the above method hasn't worked, what I ended up doing was removing the iSCSI configuration, completely uninstalling the HIT Kit, rebooting, and then doing a reinstall and configuration.
MichaelDavis
77 Posts
0
May 16th, 2013 13:00
I've seen this happen a few times in the past with both 2008 R2 and 2012, and have resolved it using a couple of different methods.
The first and least disruptive is to disable the interface that the traffic is currently going over to force a failover to the second adapter. After traffic is going over the second adapter, bring the first back online and traffic will balance across the two. Can't offer a real explanation for why it works, just that it has in all but two instances.
The two times the above method hasn't worked, what I ended up doing was removing the iSCSI configuration, completely uninstalling the HIT Kit, rebooting, and then doing a reinstall and configuration.
huwy
1 Rookie
•
124 Posts
0
May 17th, 2013 05:00
Thanks for your responses guys. I'll try disabling the adaptor on the weekend when I can get some downtime. Failing that will log a support call.
Cheers for your help.
-H