This issue is not seen in PowerPath version 4.6.x. To workaround this issue, you can uninstall the current version of PowerPath and install 4.6.x, or you can do the following to make this work with currently installed version of PowerPath:
1. Log out of all but one connection to the array. 2. In the Microsoft iSCSI initiator, remove the persistent targets for all but the connection in step 1 3. Uninstall PowerPath and reboot 4. Upon reboot, open the Microsoft iSCSI initiator and bind all volumes. This should successfully bind all volumes 5. Re-install PowerPath and reboot 6. Apply the registry settings to the EMCpowsrv service per emc124529
Conor
341 Posts
0
February 28th, 2008 23:00
This issue is not seen in PowerPath version 4.6.x. To workaround this issue, you can uninstall the current version of PowerPath and install 4.6.x, or you can do the following to make this work with currently installed version of PowerPath:
1. Log out of all but one connection to the array.
2. In the Microsoft iSCSI initiator, remove the persistent targets for all but the connection in step 1
3. Uninstall PowerPath and reboot
4. Upon reboot, open the Microsoft iSCSI initiator and bind all volumes. This should successfully bind all volumes
5. Re-install PowerPath and reboot
6. Apply the registry settings to the EMCpowsrv service per emc124529
AllBlack
1 Rookie
•
74 Posts
0
March 2nd, 2008 11:00
cheers
AllBlack
1 Rookie
•
74 Posts
0
March 2nd, 2008 11:00
Anyway, Your solution seems to me that it might be something that needs to be repeated everytime a volume has been added and not a permanent fix?
cheers