Poweredge R620 -- recognizing 'default' network interface (iDRAC vs NICs)

Question

Hi all, I'm a new-to-the-industry network technician assigned to an R620 server in a test environment. I am working on a PlanetLab project, and I'm trying to figure out how to bring this server online. I understand this sounds like a question for PL Support, but we've been stumped and at this point I'm trying to get any help or ideas I can try, in addition to working with PL Support. As part of the installation, I have a bootable CD with a custom Linux kernel. When booted from the CD, the server should initialize network connections then contact the PL central servers and install things. However, I never manage to get past the network initialization. The server has an Enterprise license. I assigned a public IP address to the iDRAC port, and nothing is connected to any of the ethernet port. It is on Dedicated mode. The iDRAC port is reachable remotely, and a test OS shows that I am able to make connections out from the server -- i.e none of the hardware is defective or misconfigured. The error I got was 'Device eth0 does not exist, most likely this CD does not support your hardware.' What I have tried so far: Adding a tag to tell the CD to look for em1 instead of eth0. I get the same message, 'Device em1 does not exist......' Adding a tag to tell the CD to look for the iDRAC MAC address. Changing the mode from Dedicated to Shared and selecting LOM1 as the active interface (with a working plugged in cable). Adding a tag to tell the CD to look for the MAC address of the LOM1 port. The error message remains the same. As a test, I tried using the CD to boot up on a few other Dell desktop computers (I didn't note the model numbers), and this time the CD recognizes eth0 on those machines (running Windows 7 Enterprise, though it shouldn't matter since the OS was not even booted up yet).  So there is something about the way iDRAC vs NICs work. Beyond the basic understanding of the iDRAC being a separate controller with its own network adapter, processor, etc, I am new to the DRAC technology. Unfortunately, I cannot figure out what, and am running out of ideas. At this point, I'd appreciate greatly any ideas I can try to get the CD to recognize the DRAC network adapter. Or even one of the 4 ports.  Thanks so much for reading.

Daniel My · Accepted Answer

If I add another regular server-compatible NIC card (not an NDC), will the Lifecycle Controller be able to detect the new card?

I don't understand why you are concerned with the iDRAC and LCC with your custom OS install. You can use the iDRAC to mount your OS image, but everything past that point should have nothing to do with the iDRAC or LCC.

Mount your ISO using the iDRAC and boot from it. Once it is booted from your ISO it is no different than booting from a DVD/CD. If it is not detecting the network adapter then the issue is likely a driver problem with your OS media.

I don't think this issue has anything to do with the hardware. This is likely either an issue with the driver on your OS media or the installation script. I would suggest booting to your install media to see if it is detecting the network adapter properly. That should be a good starting point to determine whether you need to add additional drivers to the media or make changes to your script for the install to work.

Thanks

Daniel My · Answer

Hello

I have a bootable CD with a custom Linux kernel. When booted from the CD, the server should initialize network connections then contact the PL central servers and install things. However, I never manage to get past the network initialization.

nothing is connected to any of the ethernet port.

The DRAC ethernet port is used to communicate with the DRAC. You need a network cable attached to the NIC/LOM for this to work. Your OS installation/configuration cannot use the iDRAC to route network traffic through for downloading your OS or other items from the network. You should think of the iDRAC as a KVM separate from the server itself. You are trying to route network traffic through a KVM to download your OS software.

Thanks

OrangeParty · Answer

Hello

The DRAC ethernet port is used to communicate with the DRAC. You need a network cable attached to the NIC/LOM for this to work. Your OS installation/configuration cannot use the iDRAC to route network traffic through for downloading your OS or other items from the network. You should think of the iDRAC as a KVM separate from the server itself. You are trying to route network traffic through a KVM to download your OS software.

Thanks

I apologize for the vague wording in my initial post. I did not have anything connected to the ethernet port, but during troubleshooting I have all 4 ports plugged in, and assigned IP address to one of them (the other 3 do not have addresses currently).

If I add another regular server-compatible NIC card (not an NDC), will the Lifecycle Controller be able to detect the new card? I think the bootCD does not see the internal NICs at all for some reason, and I want to try it with a "conventional" NIC card. If it will, any suggestions for a network card model that may work with the Lifecycle Controller?

OrangeParty · Answer

Mount your ISO using the iDRAC and boot from it. Once it is booted from your ISO it is no different than booting from a DVD/CD. If it is not detecting the network adapter then the issue is likely a driver problem with your OS media.

I don't think this issue has anything to do with the hardware. This is likely either an issue with the driver on your OS media or the installation script. I would suggest booting to your install media to see if it is detecting the network adapter properly. That should be a good starting point to determine whether you need to add additional drivers to the media or make changes to your script for the install to work.

This is it, it is looking like a driver issue. The install media is not detecting the network adapter. Thanks for the clarification!

PowerEdge Hardware General

Was this post helpful?