First method you mentioned looks correct. Are you getting any error message when you tries the first method? As it is iDRAC network setting it way take up to 30 seconds to apply the setting and new iDRAC IP reachable.

For second method you need to try below data

{"IPv4Addresses":[{
"Address": "10.XXX.X.XX",
"Gateway": "10.XXX.X.X",
"SubnetMask": "255.255.252.0"
}]}

Note : AddressOrigin is a read only attribute and can not be patched. So if you want to change iDRAC IP from DHCP to Static you need to try first method.

We are currently using the first method and the patch operation does not return an error message.

The ip address and the subnet mask are set successfully but the gateway is not. This only occurs on a brand new server (which was been updated to the latest fw) where there has never been set a static ip before.

@digitalo_, Thanks for pointing out the details. Setting the gateway IP is failing when we try for first time on new server. We will work with our engineering to get this issue fixed in upcoming release. Mean time can you try with below payload on redfish/v1/Managers/iDRAC.Embedded.1/Attributes URI

{"Attributes":{
"IPv4Static.1.Address": "100.97.196.10",
"IPv4Static.1.Gateway": "100.97.196.1",
"IPv4Static.1.Netmask": "255.255.255.0",
"IPv4.1.DHCPEnable": "Disabled"
}} 

That seems almost identical to my payload or do you suspect that changing the order would make a difference? (just checking if I'm not missing anything)

Hi,

It’s tricky to pinpoint an exact version for me. From what I’ve found, making sure you have the latest firmware updates for both the iDRAC and Life Cycle Controller is key. But maybe our users can share their experiences.

I am having this problem too and the suggested solution does NOT work. There is a PR about this issue:
https://www.dell.com/support/manuals/en-us/idrac9-lifecycle-controller-v5.x-series/idrac9_pub_rn_5.10.30.05/networking-and-io?guid=guid-32bbd1d4-9e64-47a8-8021-aa1c34da1fba&lang=en-us

The fix is use "IPv4Static" attribute instead of the "IPv4" attribute:

{"Attributes":
{ "IPv4.1.DHCPEnable": "Disabled",
  "IPv4Static.1.Address": "10.XXX.X.XX", 
  "IPv4Static.1.Gateway": "10.XXX.X.X", 
  "IPv4Static.1.Netmask": "255.255.252.0" }}

Hey, I've hit the same issue, but on iDRAC10 - PowerEdge R670;

/redfish/v1/Managers/iDRAC.Embedded.1/Attributes seems to not be a valid URI anymore.

I'm able to set static ips using the payload
{ 'Address': '10.XXX.X.XX',
  'Gateway': '10.XXX.X.X', 
  'SubnetMask': '255.255.252.0' 
} at the URI

/redfish/v1/Managers/iDRAC.Embedded.1/EthernetInterfaces/NIC.1

Since "AddressOrigin" is an RO parameter, its still as "DHCP".

I tried to disable DHCP using below payload at the URI /redfish/v1/Managers/iDRAC.Embedded.1/NetworkProtocol

{"DHCP": {"ProtocolEnabled": false}}

But this is still not changing the "AddressOrigin" to "static" and so ending up losing IPv4 connectivity.

Any suggestions on what could be done?

Thanks in advance :)

Hello,

See if this can help. You can run a GET against

/redfish/v1/Managers/iDRAC.Embedded.1/Oem/Dell/DellAttributes/iDRAC.Embedded.1

Once you have a list of attributes, run a PATCH configuring them with a payload that looks like this:

example that disables DHCP

{"Attributes":{"IPv4.1.DHCPEnable": "Disabled"}}

You will want to include the other attributes with a comma separator such as the address, gateway, subnet or do them one at a time.