Unsolved

9 Posts

1557

May 10th, 2022 16:00

iDRAC with no IPv4

Hello,

I have three Dell servers that I upgraded iDRAC firmware to the latest version and since then, IPv4 does not work, but IPv6 and OS Pass-through work!

One server is with iDRAC 7 and the two others are with iDRAC 8.  I tried to put the IPv4 in static, DHCP, enable, disable... It does not matter what I do, it does not workl

Anyone knows how to fix the IPv4?  It was working perfectly before the update.

Thanks,

Dominic

6 Operator

 • 

3K Posts

May 10th, 2022 19:00

Can you confirm whether iDRAC is in Dedicated or Shared mode? Can you try rebooting iDRAC or AC Power Cycle the server to see whether you are getting IP address for iDRAC. IF these did not work can you rollback iDRAC FW to previous and see whether you able to get IP address for iDRAC?

9 Posts

May 10th, 2022 20:00

I tried restarting the iDRAC, I think I tried on one to power cycle it, I could retry, I have a server that will not have much impact if I turn it off for a while.  On this server, I upgraded the memory lately so I had to turn it off, but did not remove the power cords.

Can an iDRAC firmware be downgraded?  And to which version?  Since IPv6 was working, I did not notice this issue until recently, because one server did not update the DNS entries on the DNS server and was not reachable anymore, only the IPv4 address was left in the DNS server...

6 Operator

 • 

3K Posts

May 10th, 2022 21:00

From which version to which version you updated iDRAC FW lastly where you saw the issue? Can you ensure IPv4 is enabled on the iDRAC. Please share the network setting page screenshot if possible.

For rollback you can go to iDRAC FW update page where you will find an option to rollback to previous version. 

9 Posts

May 15th, 2022 09:00

I used WireShark to see more about what is happening.  For iDRAC 8, if the DHCP server is pushing two routers, iDRAC send back an ACK but is not able to set and activate its IPv4, so this is definitely a bug within the DHCP client of iDRAC.

For iDRAC7, it sends a DHCP Discover, the DHCP server replies with an Offer, but iDRAC ignores it.  I even tried with a Linux DHCP server instead of a Microsoft, same results.  I am unable to access this server since I deactivated IPv6, because on the third server, with iDRAC8, deactivating IPv6 got the IPv4 working, which is a static IP.

So I do not understand why the third server needed IPv6 deactivated, so to me, it looks like another bug in iDRAC.

For IDRAC7, it has the famous LifeCycle bug and I cannot access it through the BIOS, so since it cannot take the DHCP Offer, I am totally unable to access that iDRAC anymore!  Being able to make its DHCP work again would really help me, because now this iDRAC is alone inside the box, I cannot access it by any mean!

6 Operator

 • 

3K Posts

May 15th, 2022 19:00

If you have access to server operating system you can access iDRAC using Local Racadm or OS BMC Passthrough

Moderator

 • 

5.4K Posts

 • 

37 Points

May 15th, 2022 19:00

Hi, how about connecting the network server directly to set the IP -instead of going through network switch (idrac port)- and get the IPv4 working?

9 Posts

May 22nd, 2022 23:00

They require an IP to work, which the iDrac do not have now because it does not go further into the DHCP offer.  The local USB port to SE is configured, but does not work, I guess because the LifeCycle controller shows as being disabled.  I never taught I would get caught here, otherwise I would have left IPv6 enabled, it was working fine through that protocol...

9 Posts

May 22nd, 2022 23:00

Beside iDrac, the server works great.  Now that iDrac does not program itself through DHCP and IPv6 is disabled, I have no way to get to it anymore to do any kind of modifications.  Without an IP and BIOS access to it, iDrac is not reachable.  It used to have an IPv4 through DHCP, but now I do not know why it never replies to a DHCP offer.

9 Posts

May 22nd, 2022 23:00

They require an IP to work, which the iDrac do not have now because it does not go further into the DHCP offer.

Moderator

 • 

3K Posts

 • 

14.9K Points

May 23rd, 2022 00:00

Hello,
If the following items have been taken care of and the problem persists. You can try to rollback iDRAC or install iDRAC service module. Here I am sharing a video link and article about iDRAC service module

https://dell.to/3LEnHZm

Before enabling OS to iDRAC Pass-through, make sure that:
iDRAC is configured to use dedicated NIC or shared mode (that is, NIC selection is assigned to one of the LOMs).
Host operating system and iDRAC are in the same subnet and same VLAN.
Host operating system IP address is configured.
A card that supports OS to iDRAC pass-through capability is installed.
You have Configure privilege.
When you enable this feature:
In shared mode, the host operating system's IP address is used.
In dedicated mode, you must provide a valid IP address of the host operating system. If more than one LOM is active, enter the first LOM's IP address.
After enabling OS to iDRAC Pass-through feature, if it is not working:
Check whether the iDRAC's dedicated NIC cable is connected properly.
Make sure that at least one LOM is active.

 

Accessing iDRAC via host OS https://dell.to/3lzShJa;

https://dell.to/39KqROi.

No Events found!

Top