[cifs-protocol] Question #3 - Trying to let a Windows client use MS-SWN against a samba cluster

[Sreekanth Nadendla]

Hello Metze, in your question #3 below, are you saying that client requests for witness registration occurs as long as the capability bits SMB2_SHARE_CAP_CONTINUOUS_AVAILABILITY and SMB2_SHARE_CAP_CLUSTER are set ?

In that case which part of the following section is incorrect ?
Note that we have to know if SMB2_SHARE_CAP_ASYMMETRIC bit is set to determine whether a TREE_CONNECT request needs to be sent as mentioned in this section.



3.2.5.5 Receiving an SMB2 TREE_CONNECT Response

   ...

   - TreeConnect.IsCAShare MUST be set to TRUE, if the
     SMB2_SHARE_CAP_CONTINUOUS_AVAILABILITY bit is set in the Capabilities
     field of the response.

   ...

   If Connection.Dialect belongs to the SMB 3.x dialect family and the Capabilities
   field in the response includes SMB2_SHARE_CAP_CLUSTER bit, the client SHOULD
   invoke the event as specified in [MS-SWN] section 3.2.4.1 by providing
   Connection.ServerName as Netname parameter.

   ...

   If Connection.Dialect belongs to the SMB 3.x dialect family and the Capabilities
   field in the response includes the SMB2_SHARE_CAP_SCALEOUT bit, the client MUST
   set TreeConnect.IsScaleoutShare to TRUE.

   ...

   If Connection.Dialect is "3.0.2" or "3.1.1" and the Capabilities field in the
   response includes the SMB2_SHARE_CAP_ASYMMETRIC bit, the client MUST verify
   whether both of the following conditions are true:

     ...

     If the SMB2 TREE_CONNECT request is successful, the client SHOULD invoke the
     event as specified in [MS-SWN] section 3.2.4.1 by providing
     Connection.ServerName as the Netname parameter and TreeConnect.ShareName as the
     ShareName parameter, and by setting the IsShareNameNotificationRequired
     parameter to TRUE.

Question 3:
I don't see this happening from a Windows Server 2022 acting as client.
The only relevant flags in order to let the client try a witness connection
are SMB2_SHARE_CAP_CONTINUOUS_AVAILABILITY together with SMB2_SHARE_CAP_CLUSTER.
Can you please update this with a product behavior note reflecting
the reality with all Windows versions.


Regards,

Sreekanth Nadendla

Microsoft Windows Open Specifications


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20231121/160fccb0/attachment.htm>