|
Post by michaeldu on Aug 4, 2020 13:26:44 GMT
Is there a way to associate the EthernetInterface with NetworkPort?
In the EthernetInterface schema, there is navigation property to "NetworkDeviceFunction" only when the EthernetInterfaceType is "Virtual". How about if the EthernetInterfaceType is "Physical"?
My thinking is if there is reference to NetworkDeviceFunction, then the "PhysicalPortAssignment" of it indicates the physical port. So I can know the association between the EthernetInterface and NetworkPort. I don't understand why put restriction on EthernetInterfaceType to "Virtual" only.
|
|
|
Post by fisherman27 on Sept 14, 2021 15:00:13 GMT
I have the same question. It looks like there is complete silence on this question.
In my case, I'm developing an NVMe-oF system where I need to model the PHYSICAL network connection and have an EthernetInterface to set/get IP items such as DHCP and static address.
|
|
|
Post by mraineri on Sept 24, 2021 13:17:14 GMT
We've recently published our 2021.2 schema bundle and one of the things we noticed is that type of reference we had in there really isn't correct. That singular "NetworkDeviceFunction" link found in EthernetInterfaces had two issues: 1) it tied it to be used when it's a "Virtual" interface, 2) it doesn't cover cases where multiple functions may be backing an interface.
So, in 2021.2, we deprecated that property in favor of "NetworkDeviceFunctions" in "Links" for EthernetInterface.
|
|