This post is more than 5 years old
7 Posts
0
2675
Isilon one fs 7.2 upgrade and SMB 2 client connection availability.
Would the windows 7 clients running smb 2 get disconnected during one fs 7.2 node upgrades ? The clients that have connection to any node that gets upgraded and rebooted would get disconnected ? My understanding for continuous client availability during node reboots if they need to be on smb3 or windows 8 or windows 10 ? is this true ?
AdamFox
254 Posts
1
February 17th, 2016 11:00
The only way to get continuous availability for SMB and Isilon is if the following conditions are met:
1. Client is using SMB3 (min Win8 or Server 2012R2)
2. Cluster is at least OneFS 8.0 (currently, not as an upgrade target)
3. The SMB share has CA enabled
If any of these conditions are not met, then SMB clients will disconnect if the node to which it is connected goes away. The client will then have to reconnect. This reconnection can be done immediately as the client will ask DNS for a new IP address and will get another IP on another node. For most users this isn't a big deal. They get disconnected and try again and reconnect. For applications, this can be more problematic, the severity will depend on how the application behaves when the SMB session is disconnected. Most do not handle this gracefully, in my experience.
addisdaddy20
65 Posts
0
February 17th, 2016 08:00
Hello Sureshacs,
You are absolutely spot on. CA or continuous availability is only available in the SMB v3 stack and needs a client able to interpret it, so windows 8 and above windows server 2012 or greater. You should also be aware that there is no countinous availability support until OneFS version 8.0.
SMBv2 is a stateful protocol where NFS is stateless. stateful protocols should be using static IP address pools as a result and stateless protocols should be using dynamic IP address pools.
sureshacs1
7 Posts
0
February 17th, 2016 09:00
Thanks one more question , we have a 3 node isilon cluster ( CIFS only) , so if the clients are windows 8 or 2012 with SMBV3 , would the failover be seamless if any of the Isilon node reboots ? Or is there a process we have to follow?
If a Node reboots , and if the clients are on smbv2 , I am guessing the clients will loose connection and there might be a minute or 2 delay until they connect back to an available client ?
sureshacs1
7 Posts
0
February 17th, 2016 12:00
Super , Thanks Adam .
One more question , we are on onefs 7.2 , you mentioned we need to enable CA on a smb share , where is the option to enable that ? or we get that only with Onefs 8 ?
sluetze
300 Posts
0
February 17th, 2016 22:00
As he wrote several times it is OneFS 8.0+ only
Go.Y
2 Intern
2 Intern
•
293 Posts
2
February 17th, 2016 22:00
CA(Continuously Available) is only available for OneFSv8.0 and later.
It's not in OneFSv7.2.1 or before.
Following is the sample of where to check if CA is enabled:
onefs8test-2# isi smb shares view ifs
Share Name: ifs
Path: /ifs
Description: Isilon OneFS
Client-side Caching Policy: manual
Automatically expand user names or domain names: False
Automatically create home directories for users: False
Browsable: True
Permissions:
Account Account Type Run as Root Permission Type Permission
----------------------------------------------------------------
Everyone wellknown False allow full
----------------------------------------------------------------
Total: 1
Access Based Enumeration: No
Access Based Enumeration Root Only: No
Allow Delete Readonly: No
Allow Execute Always: No
Ca Timeout: 120
Continuously Available: No <-------This is CA
sureshacs1
7 Posts
0
February 18th, 2016 06:00
Thank you all guys , this is clear now.