Hello
This is similar to another, recent post but I didn't want to hijack the thread so here goes.
We have a Dell MD3000i with dual controllers hosting a Hyper-V failover cluster. The unit is in production but now out of warranty. Management have told me they are prepared to take the risk while the hardware is retired and replaced so I have sourced spare parts and will have to make do (I know, crazy situation!).
Anyway MDSM reported a problem battery on the RAID controller in slot 1. I followed the instructions in the support guru, taking controller 1 offline so all iSCSI traffic failed over to controller 0, which it did successfully. I pulled the controller in slot 1 and replaced the battery with a spare. I reinserted the controller module and brought it back online in MDSM.
Unfortnately the controller in slot 0 doesnt seem to re-establish the iSCSI connections. It seems to go through a cycle of trying to come online but fails. During this time there is sporadic loss of connectivity to the VMs hosted on the SAN. In the event log the good controller in slot 0 reports the 'RAID controller Module reset by its alternate' before critical 'Optimal wide port becomes degraded' and 'degraded wide port becomes failed' messages.
I let this go on for about 30 mins before offlining the controller in slot 1, removing and reinserting it and trying again. Same problem - so I have taken it offline for now and everything is working through the single controller in slot 0 but without the redundancy. Amber LED is still lit on the unit.
Any ideas what I can try next? Is it worth taking the cluster down and power cycling the SAN?
I do have a spare RAID controller so replacing the slot 1 controller is an option.
Any help will be greatly appreciated (i've attached the support information from the unit)
Many thanks
Charles