I have tested this process on Win2K3 successfully and I am planning on migrating some AIX hosts using the same process. The only real difference is that we are using PowerPath and it sounds like you are not.
We have actually done part of this process already on AIX. We have added HBAs to existing hosts and we have replaced HBAs on existing hosts. This isn't EXACTLY the same, but very similar. New paths appear and old ones die.
Just make sure you plan to clean up the old paths (including in PowerPath) after the move is complete so you won't have dead paths lying around to get in the way of troubleshooting after the fact.
When i present new array to a Sun box (sparc), i have to modify lpfc.conf and sd.conf and bounce the box ..so i am afraid you might have to reboot the system to see the new FAs.
Just switch everything to Windows. That way you won't be disappointed when you have to reboot... You'll just expect it and build it into your processes
we're using powerpath and i expect to see the devices visible down 4 paths after allocating to the new FA pair. after verifying data, am going to remove masking and unmap to get down to 2 paths. I have mapped devs to multiple paths initially but not later and was just concerned about data availability issues if any. But sounds like ur experences say its fine.
Good luck, and let us know how it goes. I know based on experience that it should work exactly as planned, but I'd still like to hear that it actually DOES work!
In my sad experience with Solaris, I found that moving from a storage port to a different storage port MAY give headache to PowerPath ..
When you switch from old FA to new FA spend some time in verifying that powerpath discovered new paths ..
I won't swap persistent binding. Simply add new FAs after the existing ones .. Old disks used to be at target 0, new disks will use target 1 .. that's it
Allen Ward
4 Operator
•
2.1K Posts
1
May 30th, 2008 12:00
I have tested this process on Win2K3 successfully and I am planning on migrating some AIX hosts using the same process. The only real difference is that we are using PowerPath and it sounds like you are not.
Allen Ward
4 Operator
•
2.1K Posts
0
May 30th, 2008 12:00
Just make sure you plan to clean up the old paths (including in PowerPath) after the move is complete so you won't have dead paths lying around to get in the way of troubleshooting after the fact.
dynamox
9 Legend
•
20.4K Posts
0
May 30th, 2008 12:00
dynamox
9 Legend
•
20.4K Posts
0
May 30th, 2008 12:00
Allen Ward
4 Operator
•
2.1K Posts
0
May 30th, 2008 12:00
Just switch everything to Windows. That way you won't be disappointed when you have to reboot... You'll just expect it and build it into your processes
vkinva
18 Posts
0
May 30th, 2008 12:00
vkinva
18 Posts
0
May 30th, 2008 12:00
thanks for response,
we're using powerpath and i expect to see the devices visible down 4 paths after allocating to the new FA pair. after verifying data, am going to remove masking and unmap to get down to 2 paths. I have mapped devs to multiple paths initially but not later and was just concerned about data availability issues if any. But sounds like ur experences say its fine.
Allen Ward
4 Operator
•
2.1K Posts
0
May 30th, 2008 12:00
vkinva
18 Posts
0
May 30th, 2008 13:00
xe2sdc
4 Operator
•
2.8K Posts
0
June 1st, 2008 09:00
When you switch from old FA to new FA spend some time in verifying that powerpath discovered new paths ..
I won't swap persistent binding. Simply add new FAs after the existing ones .. Old disks used to be at target 0, new disks will use target 1 .. that's it