G'day, There ended up being no sane fix for this problem. Despite what other people had reported about BIOS & BMC being out-of-date, that wasn't the case here as I mentioned.  As we had to leave the data centre and travel inter-city, we were forced to work out a fix. That ended up being to re-flash the BMC via FreeDOS which led to several changes: We then power cycled and configured the IP addressing via BIOS > IPMI, which accepted the changes unlike before the re-flash. The NIC was re-configured back to the dedicated card, though it's worth mentioning that the reported MAC address doesn't change in BIOS despite changing the setting UNTIL YOU REBOOT AGAIN. From there, as the MAC had changed after a confirmation check in BIOS, we then had to update our MAC-to-IP binding configuration to match the dedicated NIC's MAC address. We disconnected the NIC, left it for 1-2 minutes, then reconnected and were able to access the IPMI interface through a web browser. Splendid. It's a shame that there's no known fix for this, however we're grateful that the BMC flashing process wipes the configuration. That's not something that I've ever said in my ICT history, or at least not that I can recall!  Hopefully this helps someone in the future, as we were stuck on these bugged-out nodes out of a plethora of hardware that was reconfigured without incident, and were starting to question our sanity.  Cheers,LST-AU
Hi there, We've got a Dell PowerEdge C6100 system where the nodes are reporting the following error when we attempt to use ipmitool against them via the installed operating system (Debian) when using any commands other than "lan 1 active on/off" or setting a VLAN tag (but not setting the VLAN tag to OFF which also leads to the same error). LAN Parameter Data does not match! Write may have failed. There are other threads around which suggest root causes from outdated BIOS/BMC through to write-protection via LAN Failover (LFO) (which was recommended to be fixed via syscfg which we don't believe to be compatible with the C6100 node boards?). In this instance though, the BIOS & BMC on each node is up-to-date (1.81 & 1.33). Our problem is that the VLAN ID shouldn't have been set, so we're now trying to remove the tag from IPMI/BMC so that the interfaces will come up. This isn't possible, nor is specifying a static IP, subnet or default gateway. All fail with the above error after a short while attempting to write the config. User attempting this is root, so it's highly unlikely to be related to the OS or privileges of any kind, but seems to be a peculiar and occasional bug. If we try to change the IP addressing via BIOS > IPMI Configuration the newly-specified addressing doesn't save to the "Current BMC Config" (or similar wording) line after pressing enter on the "Enter new address" (or similar wording) line. Logically, that aligns with a silent failure. BIOS > IPMI has nothing beyond basic configuration, so we're unable to attempt removing the VLAN tag/ID from that route, which would've been the logical fix. Should we be disabling the LFO (LAN Failover) using OpenManage on these nodes? Would that permit the updates that we need to do here? Or is there another solution that we're missing? It's frustrating that it happily accepted the VLAN ID initially and is now refusing to have it removed, and also won't take IP addressing. We can work around the addressing using DHCP, however now that it's tagged, it won't route through our untagged ports. Relevant threads: [URL] [URL] The most interesting one is: [URL] However we're unsure how to SSH into a card that we don't know the IP of (it's reporting none as being set) which also wants a tagged port and won't let us untag it. What's the best course of action here to reset the cards, or otherwise overwrite the erroneous configuration? It's an issue we're not seeing much of with the C6100 model. There are many threads online about this, but most are resolved with a BIOS and BMC/IPMI update, which isn't applicable in this instance. We performed the BIOS and BMC updates successfully in late 2020 using FreeDOS. Just to be clear, we can use DHCP (it accepts the command to move the BMC/IPMI LAN/NIC to use DHCP rather than static) so the only problem that we believe needs fixing is removing the VLAN ID. Or is there a larger issue? Tagging [NAME]-Chris H as he replied in one of the linked threads, however any and all help is appreciated! Many thanks,LST-AU
PE C6100: ipmitool = LAN Parameter Data does not match (Latest BIOS & BMC)