|
|
Post by shawnw on Jun 25, 2024 10:45:06 GMT
Hi,
I'm working on the the Redfish resource of SharedNetworkPorts and DedicatedNetworkPorts.
I could see the DedicatedNetworkPorts is in the Port schema. However, SharedNetworkPorts doesn't show in it.
Does the schema miss it?
<String>/redfish/v1/Managers/{ManagerId}/SharedNetworkPorts/{PortId}</String>
Many Thanks,
Shawn
|
|
|
|
Post by mraineri on Jun 25, 2024 12:51:01 GMT
That's intentional. The members of that collection will be URIs to the Port resources elsewhere in the model from the network adapter with the shared network port. In the long description: "The members of this collection shall reference Port resources subordinate to NetworkAdapter resources."
For example:
{
"@odata.type": "#PortCollection.PortCollection",
"Name": "Port Collection",
"Description": "Collection of shared network ports for this manager",
"Members@odata.count": 2,
"Members": [
{
"@odata.id": "/redfish/v1/Chassis/1U/NetworkAdapters/Slot1/Ports/SC2KP1"
},
{
"@odata.id": "/redfish/v1/Chassis/1U/NetworkAdapters/Slot1/Ports/SC2KP2"
}
],
"@odata.id": "/redfish/v1/Managers/BMC/SharedNetworkPorts",
"@Redfish.Copyright": "Copyright 2014-2023 DMTF. For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright."
}
|
|
|
|
Post by shawnw on Jun 26, 2024 8:56:43 GMT
Thanks, mraineri. ![]() I found the document describes the new properties and it's exactly the same as what you told me.   But still have some questions. 1. If I have a onboard network port which is designed for Host, so the network port is not attached to a network adapter. In the case, how to present it as a SharedNetworkPort, if it has to be a subordinate to NetworkAdapter resources? 2. Some of NIC cards will filter LLDP response so that we're not able to find the corrsponding port. Some NCSI oem command is able to find the mac on the port but it couldn't apply to every NIC cards. Is it possible to share your experience to get the information? Many Thanks, Shawn |
|
|
|
Post by mraineri on Jun 26, 2024 13:50:57 GMT
1) In that configuration, that is still a network adapter. It's may not be a physical card like an OCP NIC, but it's still an adapter with ports and functions and we recommend modeling it as such to allow for consistent discovery/inventory of the devices.
2) Personally I haven't had to work much in this space, but some folks I asked had not experienced issues like that. You may need to reach out to your NIC vendor for help.
|
|
|
|
Post by shawnw on Jun 27, 2024 0:33:26 GMT
Got it! I appreciate your suggestion.
I'll study more.
Many Thanks.
|
|
