Memory and Update Redfish about idrac-redfish-scripting HOT 5 CLOSED

@vaidyasaurabh08

On latest iDRAC version 2.60 for 13G servers, if you run a GET on URI "redfish/v1/Systems/System.Embedded.1/Memory", you should see URIs for each DIMM installed which you can run a GET on each of these URI to see detailed DIMM information.

Example of running GET on URI "redfish/v1/Systems/System.Embedded.1/Memory":

For version of Redfish iDRAC uses, there is no way to only update Redfish. Redfish support is added in the iDRAC firmware itself and each iDRAC version that gets posted on Dell support site, more Redfish support is being added. To see what Redfish schema versions are supported in the iDRAC version you have installed, run a GET on URI "redfish/v1/JSONSchemas".

from idrac-redfish-scripting.

Hi @texroemer,

Thank you very much for your reply.
I tried the uri you specified /Systems/System.Embedded.1/Memory
on a R740xd 14 gen with idraac firmware version 3.15.147.15
I got the same error of no resource not found.

I found the redfish version the system is at is again 1.0.2

Can you please advise me on this. I know I an not putting in the path incorrect as it works for all other things.

So I think the question is shouldnt that idrac version have redfish 1.6+ which would then have that jsonSchema.

Also is there any other way I could access DIMM info.

from idrac-redfish-scripting.

On 14G server, did you run GET on this URI "https://"your iDRAC ip"/redfish/v1/Systems/System.Embedded.1/Memory" and it didn't work? 3.21 is the latest firmware version for 14G, can you try this version if you are still seeing the error?

from idrac-redfish-scripting.

@texroemer
I was wondering if I hardcode the urls like this from getLcLog example

https://%s/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Lclog?$skip=%s'

Will such hardcoding work for any redfish version and json schema... as in will the new redfish versions and jsonschemas change old hypermedias or will they be backward compatible.

Also I see in the url the path after the manager is Vendor specific, IDRAC in our example.
So will dell keep this as constant itrespective of redfish version??

Thanks

from idrac-redfish-scripting.

@vaidyasaurabh08

Yes, if you hard code that URI, it will be supported for backwards compatibility.

Correct, this is a Dell OEM extension which the iDRAC firwmare version exposes to Redfish. It's not tied to the Redfish schema version so it will be constant.

Thanks

from idrac-redfish-scripting.