Solved!
Go to SolutionReplacing HBA on a windows server
One of our windows hosts lost two paths out of four to the CX-500. Changing the cables did not solve the problem. I have asked the admin who owns the host to change the HBA card that lost connectivity.
I was looking around powerlink about replacing HBA cards and came across a primus emc131820 saying EMC support should be contacted. is there a reason for it? Once admin schedules down time, I was going to clear the dead paths on the host side, deregister the old paths from the CX-500, replace the HBA card, update the switch zones with the new HBA and rescan on the host,...and back to business...~:)
is there anything more to it? Just curious why EMC wants us to contact support. is there a know issue on windows?
Thanks in advance.
I was looking around powerlink about replacing HBA cards and came across a primus emc131820 saying EMC support should be contacted. is there a reason for it? Once admin schedules down time, I was going to clear the dead paths on the host side, deregister the old paths from the CX-500, replace the HBA card, update the switch zones with the new HBA and rescan on the host,...and back to business...~:)
is there anything more to it? Just curious why EMC wants us to contact support. is there a know issue on windows?
Thanks in advance.
- Thinking back about the "please contact EMC" thing, I think it has to do with verifying that all paths from that host get added to the storage group after you replace the HBA. You can do this by going into connectivity status from the host itself in the procedure. If it was supposed to have 4 paths and you see 4 paths in the storage group (via connectivity status) then your fine.
-Ryan
RyanP2
261 Posts
1375
0
Posted July 13th, 2009 11:00
After replacement of an HBA, the new registered initiator path(s) will NOT be added to the Storage Group. The new initiator(s) must be brought into the Storage Group to allow access to the LUNs.
Follow these steps:
Open Navisphere Manager and verify you're in the Storage Tab.
Expand the array and then the Hosts section.
Right-click the host having the problem and click Connectivity Status.
You will see the initiators that need to be added as they will show up in ~management.
Click Reconnect to have them added to the Storage Group.
Now run whatever procedures are necessary to have the host recognize the devices down the new HBA.
I would first verify the above reconnect procedure is there in you version of flare. Just follow the steps and see if that reconnect button is in that window. If not, then I can put in another procedure.
Primus emc207351 is sited above.
-Ryan