Score:1

Server

Using racadm to change from Dedicated to LOM1?

a coder

11/29/23, 2:35 PM

Is it possible to use racadm to change iDRAC config from the default dedicated port to one of the server's main NIC/LOM ports?

There is relatively little in the documentation beyond configuring the network settings (ip/subnet/gateway), which is done with:

racadm setniccfg -s $ipaddress $subnetmask $gateway

I am able to view the full network config (as well as which port the iDRAC is configured to use with:

racadm getniccfg

What options/arguments would I use to change from iDRAC dedicated to NIC1 port?

1058

1 + 0

drac

dell-poweredge

rhel8

Score:1

Server

a coder

11/29/23, 4:16 PM

Continued digging around online and ran across the solution. Reposting here as it was pretty hard to find (Dell server support guys were stumped as well)

Check iDRAC config

racadm getniccfg

Verify which port is in use (change eno1 to eth1 or whatever your server is configured as)

ethtool eno1
ethtool eno2 
ethtool eno3
ethtool eno4
(check last line of output for "Link detected: yes")

Check iDRAC NIC Selection

racadm get iDRAC.NIC.Selection

Set iDRAC to use shared network port LOM1 (look for link detected in output from ethtool above)

racadm set iDRAC.NIC.Selection LOM1

Check iDRAC NIC Selection racadm get iDRAC.NIC.Selection

Set iDRAC network configuration

racadm setniccfg -s <ipv4_address> <subnetmask> <ipv4_gateway>

Check iDRAC config

racadm getniccfg

You should see something like:

LOM Status:
NIC Selection   = LOM1
Link Detected   = No
Speed           = Unknown
Duplex Mode     = Unknown
Active NIC      = None
Active LOM in Shared Mode = None
FailOver LOM in Shared Mode = None

Static IPv4 settings:
Static IP Address    = <ipv4_address>
Static Subnet Mask   = <subnetmask>
Static Gateway       = <ipv4_gateway>

To change back from LOM1 to Dedicated

racadm set iDRAC.NIC.Selection 1

Additional iDRAC.NIC options

For a full list of config options use

racadm help iDRAC.NIC

To view full system config

racadm getsysinfo

+ 2

Grant Curell

11/29/23, 6:20 PM

(Obligatory legal note: I work for Dell) Risking being overly opinionated here: That sort of stuff isn't typically advertised because unless you have a very good reason to do this we do not recommend it. Your management should always be out of band and physically separate from prod. Doing this in a lab it's fine but as a former red teamer who owned more than one SuperMicro server because people would leave the IPMI interface hung out, I would carefully examine the motivation for doing this in production. Example bad (but common) reason: Only wanting to run one cable.

a coder

11/29/23, 8:09 PM

In our case, we have cabling to both dedicated and LOM1, however having spent quite a bit of time with helpful Dell techs, and our own local NOC, we've nearly reached the conclusion that the iDRAC port is borked somehow. Our connectivity is OK over LOM1, but setting it back to Dedicated results in no ping and no access to iDRAC (in spite of NOC seeing device MAC, and confirming cabling is good, and that we have link at the Dedicated port. We all agree that it's 100% better to have the iDRAC on its own dedicated port.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Using racadm to change from Dedicated to LOM1?

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.