dov
Minnow
Posts: 6
|
Post by dov on Dec 19, 2022 8:49:17 GMT
I am looking for clarity on intended use and differences between the following properties in Port schema:
• Enabled
• InterfaceEnabled
• LinkState
All three properties are writable. The first two are Boolean and LinkState is an Enum with the values “Enabled” or “Disabled”.
From the property description it is unclear to me what functional change each property should have on a port. And it is unclear how the port should behave by setting different permutations of the three (2 enabled & 1 disabled, or the other way around).
|
|
|
|
Post by jautor on Dec 19, 2022 22:51:59 GMT
I agree those need some clarity in the descriptions to better explain their usage. InterfaceEnabled and LinkState were both added to support ports on fabric adapters, so that may help explain the intent. Enabled was an original property for this schema, and therefore is likely the first one you should support - with the others perhaps not being relevant for many types of ports / adapters...
I've opened an issue for the group to take a look at these descriptions - but note that our next meeting is after the holidays, so it will be about two weeks before I can get you a better answer...
Jeff
|
|
dov
Minnow
Posts: 6
|
Post by dov on Feb 7, 2023 8:31:36 GMT
Jeff, Any update?
Thanks,
Dov.
|
|
|
|
Post by mraineri on Feb 7, 2023 13:43:39 GMT
No updates yet, but we are tracking this internally to address.
|
|
|
|
Post by malbolge on Mar 3, 2023 22:52:51 GMT
1. Should you be able to take the PF or VF down from the port schema?
I'm assuming no, that's what the NetworkDeviceFunction/PCIeDevice schema is for, right? So regardless of whatever you do with these three properties, on a NIC, from the Port schema, you shouldn't ever be able to disable a PF/VF. Agree?
2. Does the "Interface" in "InterfaceEnabled" mean the stuff you find on /etc/network/interfaces?
If yes, then it shouldn't be in the schema. That's a OS level construct, and belongs in the NetworkInterface schema, or perhaps some other.
The assumption I'm going with here is that a single schema is owned by a single device. Here, particularly, we're talking about an embedded RDE device owning the schema. Expecting the embedded NIC to force the OS to bring down the OS-level interface structure is swimming upstream. The OS might be booting. It might have crashed. There might be no OS.
3. There's various levels of disabling the port. Which of these three properties, if any, are expected to depower the laser module? If they're supposed to do the same thing, they're redundant. If they're supposed to do different things, what?
|
|
|
|
Post by richien on May 23, 2023 8:39:23 GMT
My understanding is as follows:
1. The InterfaceEnabled property enables/disables OS-level Ethernet interfaces (both physical and virtual) associated with a port.
2. The LinkState property places a port in administratively up/down state.
3. The Enabled property powers up/down a port.
|
|
