Wow indeed.... And how do you get it right ? Remove the LUN from the SG and re-insert it again or isn't it possible at all, besides unbinding the LUN and recreating it ?
In order to ensure the migration is not visible to the host OS (so access to the LUN will not be impacted), the LUN's host-visible configuration information has to stay consistent, so the "right" action to accomplish that goal is keeping the host-visible configuration information the same. Note that Navisphere will accurately report the current RAID level; it is narrowly a text string embedded in some of the configuration information (which the host chooses to echo) that retains the original setting. If the goal is to cause the text string to be changed, an unbind/rebind/recreate action would be needed, or consider using SAN Copy (internal to the array) to accomplish the migration - neither of these alternate approaches is seemless.
Did you try a "cfgmgr" and then "lsdev" ? I think it should work.
If not, do you use PowerPath ? Then you could try to do a "rmdev" on a hdisk (the hdiskpower would still be available), then a "cfgmgr" and "lsdev". If it is succesful, do this on the other paths of the hdiskpower.
If the Lun type of Lun presented to an AIX host is changed from Raid5 to Raid10 the AIX host would treat the Lun as a new disk with a new hdisk#. This is why when you use the migrate function the Cx mask the Lun type change to AIX, otherwise it would look like a failed disk along with a new disk added..
Yes I see what you mean with the CLARiiON migrate feature. But I would like you to do a test, just create a RAID 1/0 lun, add it directly in the storage group and see if it is detected correctly. Then we could see if there is a ghost behaviour of the previous RAID 5 lun, or if globaly the server sees every lun as RAID 5.
DGM3
238 Posts
1154
0
Posted April 18th, 2008 14:00
the LUN from the SG and re-insert it again or isn't
it possible at all, besides unbinding the LUN and
recreating it ?
In order to ensure the migration is not visible to the host OS (so access to the LUN will not be impacted), the LUN's host-visible configuration information has to stay consistent, so the "right" action to accomplish that goal is keeping the host-visible configuration information the same. Note that Navisphere will accurately report the current RAID level; it is narrowly a text string embedded in some of the configuration information (which the host chooses to echo) that retains the original setting.
If the goal is to cause the text string to be changed, an unbind/rebind/recreate action would be needed, or consider using SAN Copy (internal to the array) to accomplish the migration - neither of these alternate approaches is seemless.
Regards,
DGM