Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UNKNOWN]: Request error: No network adapter or interface data returned for API URL '/redfish/v1/Systems/***/NetworkInterfaces' #147

Closed
lgmu opened this issue Jan 8, 2025 · 9 comments
Labels
awaiting reply waiting for a reply, close issue after 14 days of no response
Milestone

Comments

@lgmu
Copy link

lgmu commented Jan 8, 2025

Hi!

happy new year! We have a problem with a Cisco BE6H-M5-K9, this does not seem to have any built-in network adapters but instead PCIe ones.

This results in
[UNKNOWN]: Request error: No network adapter or interface data returned for API URL '/redfish/v1/Systems/***/NetworkInterfaces'

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/api/4_1/b_Cisco_IMC_REST_API_guide_4_1/b_Cisco_IMC_api_3x60_chapter_010.html#Cisco_Reference.dita_4ba53264-f0ca-4152-bcbb-15b8a195c221

When you follow this guide, you end up with something like this:

"PCIeDevices":  [{
                        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/1"
                }, {
                        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/MRAID"
                }, {
                        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/L"
                }],
        "Model":        "BE6H-M5-K9",
        "PCIeFunctions":        [{
                        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/1/PCIeFunctions/0"
                }, {
                        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/MRAID/PCIeFunctions/0"
                }, {
                        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/L/PCIeFunctions/0"
                }],
                
...

{
        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/1",
        "@odata.type":  "#PCIeDevice.v1_4_0.PCIeDevice",
        "@odata.context":       "/redfish/v1/$metadata#PCIeDevice.PCIeDevice",
        "PCIeFunctions":        {
                "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/1/PCIeFunctions"
        },
        "Links":        {
                "Chassis":      [{
                                "@odata.id":    "/redfish/v1/Chassis/1"
                        }],
                "PCIeFunctions":        [{
                                "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/1/PCIeFunctions/0"
                        }],
                "[email protected]":    1
        },
        "Name": "Intel i350 Quad Port 1Gb Adapter",
        "Description":  "This gives information of PCIeDevices on the system",
        "Id":   "1"
}

...

{
        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/1/PCIeFunctions/0",
        "@odata.type":  "#PCIeFunction.v1_2_3.PCIeFunction",
        "@odata.context":       "/redfish/v1/$metadata#PCIeFunction.PCIeFunction",
        "Links":        {
                "PCIeDevice":   {
                        "@odata.id":    "/redfish/v1/Systems/***/PCIeDevices/1"
                },
                "EthernetInterfaces":   [{
                                "@odata.id":    "/redfish/v1/Systems/***/EthernetInterfaces/1.3"
                        }, {
                                "@odata.id":    "/redfish/v1/Systems/***/EthernetInterfaces/1.4"
                        }, {
                                "@odata.id":    "/redfish/v1/Systems/***/EthernetInterfaces/1.1"
                        }, {
                                "@odata.id":    "/redfish/v1/Systems/***/EthernetInterfaces/1.2"
                        }],
                "[email protected]":       4,
                "StorageControllers":   [],
                "Drives":       [],
                "[email protected]":       0,
                "[email protected]":   0,
                "NetworkDeviceFunctions":       [],
                "[email protected]":   0
        },
        "SubsystemId":  "0x00b9",
        "SubsystemVendorId":    "0x1137",
        "Description":  "This gives information of PCIeFunctions on the system",
        "Id":   "1",
        "Name": "Intel i350 Quad Port 1Gb Adapter",
        "DeviceId":     "0x1521",
        "VendorId":     "0x8086"
}

But this does not contain any status/health information at all so I'm not sure how to work with this, do you have any ideas?

Thanks!

@bb-Ricardo
Copy link
Owner

@bb-Ricardo
Copy link
Owner

Hey @lgmu,

what do you think should we do with this issue? There is not much I can do as the CIMC does not provide any further information.

@bb-Ricardo bb-Ricardo added the awaiting reply waiting for a reply, close issue after 14 days of no response label Jan 16, 2025
@lgmu
Copy link
Author

lgmu commented Feb 4, 2025

Hey,

I'm not sure but the "false positive" message isn't ideal for us.
Maybe we just have to exclude this mode for those hosts

@bb-Ricardo
Copy link
Owner

Well, thinking about it. I could add a --ingore-unavailable-resources flag and report these as OK. What do you think?

@lgmu
Copy link
Author

lgmu commented Feb 5, 2025

That would be great!

@bb-Ricardo
Copy link
Owner

I just pushed a commit to next-release branch. would you be able to test this?

@bb-Ricardo bb-Ricardo added this to the 1.11.0 milestone Feb 10, 2025
@lgmu
Copy link
Author

lgmu commented Feb 12, 2025

Thanks! I'll try to find time to test it this week

@lgmu
Copy link
Author

lgmu commented Feb 12, 2025

[OK]: Request issue: No network adapter or interface data returned for API URL '/redfish/v1/Systems/***/NetworkInterfaces'

Works great!

@bb-Ricardo
Copy link
Owner

Thank you for testing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting reply waiting for a reply, close issue after 14 days of no response
Projects
None yet
Development

No branches or pull requests

2 participants