To make a rather long and painful story short, this is the dilema I face. We purchased serveral HP Dl380G7s that included dual Qlogic 10Gbe adapters. These handle the iSCSI traffic to our HP 10Gbe Switches and to our HP P4000 SAN.
We have had several failures of these cards, i'm talking 18 out of 66 cards go bad since I stood up the systems last December. HP is going to take the cards back and issue us a refund. In the meantime, we have ordered some Intel adapters.
Now, I have several servers and several volumes. I'm trying to avoid getting handcramps and disconnecting all the volumes on the servers and having to reconnect and setting up MPIO..which is very tedious. My thought is I have to update the latest SAN I/Q software for our SAN and part of that requires the SAN to reboot. I was thinking I could shutdown the SAN, uninstall qlogic crap hardware and software install the intel's update firmware and drivers and configure same IP's..etc, reboot the SAN, finish the SAN i/q update, then power on the servers.
I know, I know, it's lazy, yes..but I have a limited maitenance window, and if you've ever manually added 100's of volumes w/MPIO setup using the MS iSCSI initiator, you should feel my pain..lol.
Any input would be great here..or any other better ideas?
Thanks!
We have had several failures of these cards, i'm talking 18 out of 66 cards go bad since I stood up the systems last December. HP is going to take the cards back and issue us a refund. In the meantime, we have ordered some Intel adapters.
Now, I have several servers and several volumes. I'm trying to avoid getting handcramps and disconnecting all the volumes on the servers and having to reconnect and setting up MPIO..which is very tedious. My thought is I have to update the latest SAN I/Q software for our SAN and part of that requires the SAN to reboot. I was thinking I could shutdown the SAN, uninstall qlogic crap hardware and software install the intel's update firmware and drivers and configure same IP's..etc, reboot the SAN, finish the SAN i/q update, then power on the servers.
I know, I know, it's lazy, yes..but I have a limited maitenance window, and if you've ever manually added 100's of volumes w/MPIO setup using the MS iSCSI initiator, you should feel my pain..lol.
Any input would be great here..or any other better ideas?
Thanks!
Last edited: