master3117 wrote:
ailean wrote:
Did you see a path reconnect in the logs too, if so how much time was between the two events?
Some of our Solaris hosts saw paths disappear and reappear during node reboots but with less then a second between events. You can't have two port WWNs the same so I'd expect some brief break between the rebooting node ports going offline and the partner node ports presenting the other WWNs.
This was on a 3.3.1MU2 to 3.3.1MU3 upgrade.
Hi,
between path lost and path reinstated passed more than a minute, I recon that happened only because the node that rebooted came back online.
We are looking at our multipath timeout configuration.
TY
I think our MU3 update took around 10mins for each node reboot, so when working you should see a sub second blip for port persistence to take over the rebooting node paths, then 10mins of node restart, then another sub second blip as the paths handed back to the node and then typically the engineer will pause while you check hosts before started the next reboot.
If it's around 60 seconds that sounds like a host timeout value, they are often configured to 30 or 60 seconds by default on a lot of hosts.