downtime involved when stack member is powered down and powered back

[Rohit Patil]

When I am running 2 switches sw1 and sw2 in stack.

I am continuously pinging from server 1 to server 2 and server 3.

and If I power down the sw1 and power it back again, till the switch reloads and back in service and is member of stack, does it interrupt the services.

Any supporting doc for such scenario.

If there is any method to optimise the downtime.

[Joseph W. Doherty]

"Let's explore few more options, high speed stacking and sso."

SSO, definitely, and if stack is doing routing, I would look at NSF and using the persistent MAC address feature.

As to high speed stacking, sure, although I don't believe it would have any effect on this issue.

1:1 redundancy might short circuit a boot election, saving boot time, but also shouldn't be a factor for an active failure.

Someelse to consider, your .3 release is a ED, but .4 is MD.

[Rohit Patil]

Also xFSU, though it is for software upgrades we can optimise reload by using xFSU, what do you suggest?

[Joseph W. Doherty]

I'm still somewhat hesitant to use the faster upgrade methods.  I prefer doing upgrades during scheduled maintenance that not only has sufficient time for the classical reload but has time to deal with a reload failure.  Never had anyone complain about finishing scheduled maintenance sooner than expected, but quite the opposite when not back on-line when expected.