Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
When removing an "unused" member switch there should be little (stack transit traffic?) to no service interruption.
When removing an "unused" stack master, there can be service interruption, how severe depends on stack configuration. Pure L2 switching should be the least disturbed. L3 routing, more so, although if NSF enable, that should be minimal too. One issue with a stack master change, by default, the master's MAC changes, which can cause issues for SVI IPs and port-channels. Both can be mitigated by configuring the stack to continue to use the original stack master's MAC (until the whole stack is reloaded).
