Unsolved
This post is more than 5 years old
5 Practitioner
•
274.2K Posts
1
2226
Change Initiator Host Type
Hi all!
I am with a problem with a customer. He register the initiators of all AIX hosts with the Host Type default, now we need to change to aix.
My question is if is safe to change each HBA port initiator at a time (online) or i need to change all at the same time (offline)? It is OK to have different host type for the same host at an Storage View? How will the AIX and PowerPath deal with it? I run the risk of it recognize the disk as different devices?
It will be a temporary situation but i do not have sure how I/O will be affected.
thx
echolaughmk
522 Posts
1
February 19th, 2015 12:00
Hi,
I don't think you will be able to "change" it only fly - it will require to unregister and re-register the initiator:
Ensure that you specify the correct host type in the Host Type column
as this attribute cannot be changed in the Initiator Properties dialog
box once the registration is complete. To change the host type after
registration, you must unregister the initiator and then register it
again using the correct host type.
That being said, with AIX, it will likely change some part of the SCSI presentation of the LUN and the ODM typically doesn't handle that well online so my suggestion would be an offline change. The host will likely need a reboot to see the new presentation changes anyways like other bit settings out there so it is likely safer to change it offline (maybe even remove and rescan the devices again after the changes have taken place so the ODM is current). You might be able to change it online one initiator at a time, but it is probably an unpredictable nature of how the LUN could react...just being safe.
HTH,
-Keith
vsevolod1
12 Posts
1
February 20th, 2015 02:00
Hello!
I had the simillar issue with Solaris host under Solaris Cluster control.
My advice: don't do it. Solaris host had a kernel panic issue with this.
The scenario was: volumes were under control of Solaris Cluster and Solaris volume manager. LUNs from two local VPLEX systems were mirrored with SVM. I knkocked out one of initiators in SV on VPLEX, changed its type, then readd to SV. MPIO got the new path. After I removed the second initiator form SV and IO changed to the new path, the host had paniced. We began with an inactive cluster node so nothing bad happened.
To change the initiator type we had to remove all VPLEX volumes from SVM mirrors, unconfigure Solaris volumes, then remove initiators form SV and change the initiator type and add it back. The volumes started their brand new life in solaris and that worked fine.
So the good and safe way is to plan downtime and fix the problem.