[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cifs-protocol
Subject:    Re: [cifs-protocol] MS-SWM Q10 - 3.1.6.1 Server Application Notifies of an Interface Being > Enabled
From:       "Jeff McCashland \(He/him\) via cifs-protocol" <cifs-protocol () lists ! samba ! org>
Date:       2024-01-05 17:57:49
Message-ID: MN0PR21MB3701D2318A9A78E63D4F25C6A3662 () MN0PR21MB3701 ! namprd21 ! prod ! outlook ! com
[Download RAW message or body]

[Hung-Chun and Kristian to BCC]

Hi Stefan, =


I will dig into this and let you know what I find. =


Best regards,
Jeff McCashland (He/him)=A0| Senior Escalation Engineer=A0| Microsoft=A0Pro=
tocol Open Specifications Team
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) P=
acific Time (US and Canada)
Local country phone number found here:=A0http://support.microsoft.com/globa=
lenglish=A0| Extension 1138300

-----Original Message-----
From: Hung-Chun Yu <HungChun.Yu@microsoft.com> =

Sent: Thursday, January 4, 2024 1:59 PM
To: metze <metze@samba.org>
Cc: cifs-protocol@lists.samba.org; Kristian Smith <Kristian.Smith@microsoft=
.com>; Hung-Chun Yu <HungChun.Yu@microsoft.com>; Microsoft Support <support=
mail@microsoft.com>
Subject: MS-SWM Q10 - 3.1.6.1 Server Application Notifies of an Interface B=
eing > Enabled or Disabled - TrackingID#2401040040013236

[BCC dochelp]

Hi Stefan

Since Kristian will be out of office until after Jan 23, 2024. We went ahea=
d and create SR Case - TrackingID#2401040040013236. Do leave this tag in th=
e Subject line for future reference and tracking.

One of our engineers will contact you shortly.

Hung-Chun Yu
hunyu@microsoft.com
Protocol Support

-----Original Message-----
From: Stefan Metzmacher <metze@samba.org>
Sent: Thursday, January 4, 2024 8:52 AM
To: Kristian Smith <Kristian.Smith@microsoft.com>; Interoperability Documen=
tation Help <dochelp@microsoft.com>
Cc: cifs-protocol@lists.samba.org
Subject: Re: [EXTERNAL] Trying to let a Windows client use MS-SWN against a=
 samba cluster

[You don't often get email from metze@samba.org. Learn why this is importan=
t at https://aka.ms/LearnAboutSenderIdentification ]

Am 11.12.23 um 22:15 schrieb Kristian Smith:
> Hi Metze,
>
> I'm reaching out with regard to question 10 from your mail below.
>
> ----------------------------------------------------------------------
> -----------------------------------
> Question 10:
> MS-SWM 3.1.6.1 Server Application Notifies of an Interface Being =

> Enabled or Disabled
>
>     The calling application provides the interface group name, IPv4 and/o=
r IPv6
>     addresses, and state.
>     ...
>     Then for each entry in the WitnessRegistrationList where
>     WitnessRegistration.NetworkName
>     matches the application-provided interface group name ...
>
> This seems to indicate that there's actually just a single =

> InterfaceGroupName matching the single NetworkName.
> ----------------------------------------------------------------------
> -----------------------------------
>
> WitnessRegistration.NetworkName is the NetName provided by the client whe=
n registering.
> InterfaceGroupName is provided by the Server Cluster application.

That's also my understanding.

But on a windows 2012 cluster I saw that the interfaceGroupNames in the Get=
InterfaceList() response are the per node netbios names (something like nod=
e0, node1, node2) that hold the related ip address.

But the NetworkName in th Register[Ex]() request from the client gets the s=
ofs cluster name, something like "sofs-cluster" or "sofs-cluster.example.co=
m" (which has to match ServerGlobalName (See Question 11).

With that the statement:

   Then for each entry in the WitnessRegistrationList where WitnessRegistra=
tion.NetworkName
   matches the application-provided interface group name ...

would never be true and no registration in the list will ever get any notif=
ication...
So it seems to be a documentation bug.

In my code I'm comparing WitnessRegistration.IpAddress being equal to the i=
p address of the changed interface.

> If there are no current registered witnesses (clients), the =

> Interface.InterfaceGroupName would still exist, but there would be no Wit=
nessRegistration.NetworkName This check (referenced in your question) compa=
res the server-application-provided InterfaceGroupName (the one that underw=
ent a state change) to those in the list of registered witnesses. This ensu=
res that the client receives a message about the state change.

It would mean on windows that it compares "node0" to match "sofs-cluster.ex=
ample.com", which can't work.

> Please let me know if there are lingering concerns with Question 10 and I=
'd be happy to dig back in.

Please do :-)

Thanks!
metze

_______________________________________________
cifs-protocol mailing list
cifs-protocol@lists.samba.org
https://lists.samba.org/mailman/listinfo/cifs-protocol
[prev in list] [next in list] [prev in thread] [next in thread]