Linux client DMI/SMBIOS support

Usage and Config Platform
1

(imported topic written by menke123491)

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.

Machines where dmi ‘exists’

RHEL 4/5

BES Client 6.0.2.68, 7.0.2.39, 7.0.2.103, 7.1.1.315

SMBIOS v2.3, 2.31 (as reported by dmidecode)

Machines where dmi ‘does not exist’

RHEL 5

BES Client 7.0.2.39, 7.0.2.103

SMBIOS v2.5 (as reported by dmidecode)

I’m wondering if the change from SMBIOS v2.3 to 2.5 broke the BES Client DMI query/relevance. Anyone have similiar/conflicting experience?

2

(imported comment written by mhernand91)

Were you able to determine what the problem was with DMI? Are your boxes Dell PE?

3

(imported comment written by menke123491)

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.