CIFS session force close before ONTAP upgrade

[sfrmast]

How can we close cifs share connections forcefully. I Tried all but session is keep coming.

Is it mandatory to close all session.

Kindly advice

vserver cifs session file close -node * -session-id <sessionid

cifs session close -node * -vserver vServer-01

cifs session close -node * -vserver vserver_name -connection-id 22XXXXX

[Ontapforrum · Accepted solution]

As you are doing a ONTAP upgrade and CIFS* being connection oriented (*=Non-Continuously available) will drop-out anyway even if it is NDU, so I am sure the end-users are already notified.

There are two types of CIFS shares:
1) Continuously available CIFS shares : Which are accessed by Hyper-V or Microsoft SQL Server clients using the SMB 3.0 protocol, do not need to be terminated before upgrading

:: > vserver cifs session show -continuously-available Yes

2) Non Continuously available : Before upgrading the ONTAP software, you should identify and gracefully terminate any CIFS sessions that are "not continuously" available.
:: > vserver cifs session show -continuously-available !Yes

If the sessions are not CLOSING, as you mentioned, just stop the CIFS Server, provided the CIFS are No-continuously-available shares.

Just follow this steps:
1. Stop the CIFS server
::> vserver cifs stop -vserver vserver_name

2. Start the CIFS server
::> vserver cifs start -vserver vserver_name

3. Check the sessions:
:: > vserver cifs session show

If none. Proceed with the Upgrade.

[sfrmast]

What will happen if see session and we proceed the upgrade , what would be the impact any idea. is it recommended 

[parisi]

Same impact as force closing the sessions. Basically, you're performing the step that the upgrade would do. When you giveback the node, you can use -override-vetoes to ignore open CIFS sessions,

[Ontapforrum]

Do not worry. You will be fine. If your CIFS environment is super busy and you do come across any issue with locks during upgrade , just follow this kb.

Unable to complete Ontap aggregate relocation due to locks - NetApp Knowledge Base