I’m having a problem accessing DMI on some of our Linux servers. Issuing ‘exists dmi’ returns true on some of our Linux hosts and false on others. However, running ‘dmidecode’ locally works on all of them.
We’re seeing the problem across various HP and IBM servers. If you look at the dmidecode output, it shows where in memory the DMI table resides. I audited some servers that work and some that don’t. For all the servers where “dmi exists”, the table resides in the range 0x000E0010 through 0x000F0450. For all the servers where “dmi does not exist”, the table resides at 0xCFEFE000 - a significantly different part of memory.
I’m speculating the BES client isn’t looking for the DMI table at the higher address space. We opened a ticket with Bigfix support. They indicated they identified the problem, but haven’t communicated a resolution or eta.