We want to disable smb3 globally, this is to investigate some performance issues between a client and the powerscale using smb3 encryption. however I want to know what impact this will have for all other clients (1000) accessing various different SMB shares, if we disable SMB 3 using  --revert-support-smb3-encryption, will that terminate all current live smb3 connections, will they just get a brief TCP reconnect at smb2? I have also read in the documentation "Making SMB encryption configuration changes requires either restarting or refreshing (less intrusive) the SMB server. You can refresh SMB server service by running the command /usr/likewise/bin/lwsm refresh srv on the PowerScale cluster. ". I wanted to know what does refreshing the service do? does that mean users continue on SMB3 until their connection drops and they reconnect at SMB2, or is it forced through? and how is that different from disabling/enabling SMB service? I need to understand if this an activity that should happen out of hours or not.