StarWind Software

Hi. i can not find a document that specifiy this script will work how frequently run.

Did i have to cron this myself?

Rescan is event-triggered, not time-triggered. There's a logwatcher file (not a *.ps1). Check it out.
We do not expect our users to alter it, though, unless there is any strong need for it.

ok.in two node vsan due to power loss or network problems sometimes surviving nodes cant lose connection to power off ed node or when node came back doesn t resume iscsi connection unsless manuelly rescan hba from esx or run this script manually.

i waited so long time to this script run itself but it doesnt.

which event it will run . can you specifiy.

i have seen id's in logwatcher but this event doesnt work for me.

if i schedule by minute is it get too disruptive to esx

EVENT1="ID_257"
EVENT2="ID_773"
EVENT3="ID_782"
EVENT4="ID_788"
EVENT5="ID_817"

Check this out https://www.starwindsoftware.com/help/E ... dVSAN.html.
You can add "partner became not synchronized", "device became not synchronized", "partner became synchronized"

last question

no rescan even restart of cvm.

log watcher responsible for running hba_rescan.py and i did not filled with user pass
i did for hba_rescan.ps1. which process is responsible for that?

You need to add details to hba_rescan_conf.py. It feeds the credentials into hba_rescan.py.
I've just realized that events are also somewhat built into the script itself, so add them there as well.