ghbiz
76 Posts
Quote from ghbiz on May 17, 2021, 10:40 pm
Basically the title says it all.
We have witnessed in past upgrades some iscsi path issues when upgrading a node that has active iscsi paths on it.
Might be a good idea to run a script to migrate iscsi paths OFF current node to other nodes one by one with a 30-60 second sleep between path migration tasks to allow Hyper-V / VMware to re-ARP and find the path again.
Basically the title says it all.
We have witnessed in past upgrades some iscsi path issues when upgrading a node that has active iscsi paths on it.
Might be a good idea to run a script to migrate iscsi paths OFF current node to other nodes one by one with a 30-60 second sleep between path migration tasks to allow Hyper-V / VMware to re-ARP and find the path again.
therm
121 Posts
Quote from therm on May 21, 2021, 8:58 am
Hi,
You can and should do this on your own before upgrading an ISCSI server. The dialog of the webui is "Manage iSCSI Disks" -> "Path Assignment" -> "Reassign Paths". You should use a direct target host (not "auto") for migration the paths to.
Thats said there is a command line tool which is able to move paths but this needs some parameters:
# /opt/petasan/scripts/util/move_path.py
usage: move_path.py [-h] -id ID -ip IP
move_path.py: error: argument -id is required
This just moves the path away but is unable to select an target host.
Regards,
Dennis
Hi,
You can and should do this on your own before upgrading an ISCSI server. The dialog of the webui is "Manage iSCSI Disks" -> "Path Assignment" -> "Reassign Paths". You should use a direct target host (not "auto") for migration the paths to.
Thats said there is a command line tool which is able to move paths but this needs some parameters:
# /opt/petasan/scripts/util/move_path.py
usage: move_path.py [-h] -id ID -ip IP
move_path.py: error: argument -id is required
This just moves the path away but is unable to select an target host.
Regards,
Dennis
