[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-poweredge
Subject: Re: [Linux-PowerEdge] Determining chassis type on OEM Ready systems
From: "Mendez, Chris" <Chris_Mendez () reyrey ! com>
Date: 2015-01-28 22:11:24
Message-ID: 46E6656156F8F6408D4EBF1B4EADBB4E0C986E5990 () IS-EXMB03-RP ! ad ! reyrey ! com
[Download RAW message or body]
[Attachment #2 (text/plain)]
Yes, I want the system-product-name but it is NULL/empty. Dell does a really good job \
cleaning the DMI table on the OEM Ready systems.
I was wondering if that information is encoded in one of the OEM-specific DMI table \
entries. I would think that the Dell tools/OMSA would have some way to decrypt it, \
but maybe their tools also display empty values.
[root@R530]# dmidecode -s baseboard-product-name; dmidecode -s system-product-name
0DYFC8
That's a space for system-product-name.
I think you're right, it's probably expected that we populate it with our own values.
Chris Mendez
From: Stephen Dowdy [mailto:sdowdy@ucar.edu]
Sent: Wednesday, January 28, 2015 3:33 PM
To: Mendez, Chris
Cc: linux-poweredge@dell.com
Subject: Re: [Linux-PowerEdge] Determining chassis type on OEM Ready systems
Chris,
On Thu, Jan 22, 2015 at 2:49 PM, Mendez, Chris \
<Chris_Mendez@reyrey.com<mailto:Chris_Mendez@reyrey.com>> wrote:
> I'm looking for a better method to programmatically determine the
> chassic/product type on OEM Ready servers. I've been reporting this
> information by keeping a lookup table of "Product Name" fields that come
> from the dmidecode:
> Handle 0x0200, DMI type 2, 9 bytes
> Base Board Information
> Manufacturer:
> Product Name: 0VD50G
> Version: A05
> ...
>
> But of course this changes over time and requires an ever-growing list to
> handle multiple revisions of 420s, 430s, 520s, 530s, etc..
I suspect maybe you don't want the baseboard product name, but the system product \
name?
I do not have any OEM-ready poweredge systems, so i can't verify what specifically \
you may be looking for, but, i do have a C6100:
[root@node2 ~]# dmidecode -s baseboard-product-name; dmidecode -s system-product-name
0D61XP
C6100
Or a normal R720xd:
# dmidecode -s baseboard-product-name ; dmidecode -s system-product-name
0C4Y3R
PowerEdge R720xd
I suspect that your problem is that the OEM ready systems have a NULL (or similarly \
useless) system-product-name? There's probably a tool that can program a value for \
you, but unless you've got a contract agreement with Dell.....
anyway...
dmis() { for s in $(dmidecode -s help 2>&1 | tail -n +3); do printf "%24s = %s\n" \
"${s}" "$(dmidecode -s ${s} | tr '\n' ' ')"; done ;} [root@node2 ~]# dmis
bios-vendor = Dell Inc.
bios-version = 1.52.00
bios-release-date = 10/28/2010
system-manufacturer = Dell
system-product-name = C6100
system-version = A00
system-serial-number = ***SANITIZED***
system-uuid = 4C4C4544-***SANITIZED***
baseboard-manufacturer = Dell
baseboard-product-name = 0D61XP
baseboard-version = A00
baseboard-serial-number = ..CN7475***SANITIZED***.
baseboard-asset-tag = To Be Filled By O.E.M.
chassis-manufacturer = Inventec
chassis-type = Other
chassis-version = PVT
chassis-serial-number = ***SANITIZED***
chassis-asset-tag = To Be Filled By O.E.M.
processor-family = Xeon Xeon
processor-manufacturer = Intel Intel
processor-version = Intel(R) Xeon(R) CPU X5667 @ 3.07GHz \
Intel(R) Xeon(R) CPU X5667 @ 3.07GHz processor-frequency = 3066 MHz 3066 \
MHz
--stephen
--
Stephen Dowdy - Systems Administrator - NCAR/RAL
303.497.2869 - sdowdy@ucar.edu<mailto:sdowdy@ucar.edu> - \
http://www.ral.ucar.edu/~sdowdy/
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Yes, I want the \
system-product-name but it is NULL/empty. Dell does a really good job cleaning the \
DMI table on the OEM Ready systems.<o:p></o:p></span></p><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p \
class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I \
was wondering if that information is encoded in one of the OEM-specific DMI table \
entries. I would think that the Dell tools/OMSA would have some way to decrypt it, \
but maybe their tools also display empty values.<o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>[root@R530]# dmidecode -s \
baseboard-product-name; dmidecode -s system-product-name<o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>0DYFC8<o:p></o:p></span></p><p \
class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> \
<o:p></o:p></span></p><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>That's a space for \
system-product-name.<o:p></o:p></span></p><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p \
class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I \
think you're right, it's probably expected that we populate it with our own \
values.<o:p></o:p></span></p><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Chris \
Mendez<i><o:p></o:p></i></span></p><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><div \
style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p \
class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Stephen Dowdy \
[mailto:sdowdy@ucar.edu] <br><b>Sent:</b> Wednesday, January 28, 2015 3:33 \
PM<br><b>To:</b> Mendez, Chris<br><b>Cc:</b> \
linux-poweredge@dell.com<br><b>Subject:</b> Re: [Linux-PowerEdge] Determining chassis \
type on OEM Ready systems<o:p></o:p></span></p></div><p \
class=MsoNormal><o:p> </o:p></p><p class=MsoNormal \
style='margin-bottom:12.0pt'>Chris,<br><br>On Thu, Jan 22, 2015 at 2:49 PM, Mendez, \
Chris <<a href="mailto:Chris_Mendez@reyrey.com">Chris_Mendez@reyrey.com</a>> \
wrote:<br><br>> I'm looking for a better method to programmatically determine \
the<br>> chassic/product type on OEM Ready servers. I've been reporting \
this<br>> information by keeping a lookup table of "Product Name" fields that \
come<br>> from the dmidecode:<br><br>> Handle 0x0200, DMI type 2, 9 \
bytes<br>> Base Board Information<br>> \
Manufacturer:<br>> Product Name: 0VD50G<br>> \
Version: A05<br>> \
...<br>><br>> But of course this changes over time and requires an ever-growing \
list to<br>> handle multiple revisions of 420s, 430s, 520s, 530s, etc..<br><br>I \
suspect maybe you don't want the baseboard product name, but the system product \
name?<br><br>I do not have any OEM-ready poweredge systems, so i can't verify what \
specifically you may be looking for, but, i do have a C6100:<br><br><span \
style='font-family:"Courier New"'>[root@node2 ~]# dmidecode -s \
baseboard-product-name; dmidecode -s system-product-name<br>0D61XP<br>C6100<br><br>Or \
a normal R720xd:<br># dmidecode -s baseboard-product-name ; dmidecode -s \
system-product-name<br>0C4Y3R<br>PowerEdge R720xd</span><br><br><br>I suspect that \
your problem is that the OEM ready systems have a NULL (or similarly useless) \
system-product-name?<br>There's probably a tool that can program a value for you, but \
unless you've got a contract agreement with Dell.....<br><br>anyway...<br><br><span \
style='font-family:"Courier New"'>dmis() { for s in $(dmidecode -s help 2>&1 | \
tail -n +3); do printf "%24s = %s\n" "${s}" "$(dmidecode -s \
${s} | tr '\n' ' ')"; done ;}<br>[root@node2 ~]# dmis<br> \
bios-vendor = Dell Inc. <br> \
bios-version = 1.52.00 <br> bios-release-date \
= 10/28/2010 <br> system-manufacturer = Dell \
<br> system-product-name = C6100 \
<br> system-version = A00 <br> \
system-serial-number = ***SANITIZED*** \
<br> system-uuid = \
4C4C4544-***SANITIZED*** <br> baseboard-manufacturer = Dell \
<br> baseboard-product-name = 0D61XP <br> \
baseboard-version = A00 <br> baseboard-serial-number = \
..CN7475***SANITIZED***. <br> \
baseboard-asset-tag = To Be Filled By O.E.M. <br> \
chassis-manufacturer = Inventec <br> \
chassis-type = Other <br> chassis-version = PVT \
<br> chassis-serial-number = ***SANITIZED*** \
<br> chassis-asset-tag = To Be \
Filled By O.E.M. <br> processor-family = Xeon Xeon \
<br> processor-manufacturer = Intel \
Intel <br> \
processor-version = Intel(R) Xeon(R) CPU \
X5667 @ 3.07GHz Intel(R) Xeon(R) CPU \
X5667 @ 3.07GHz <br> \
processor-frequency = 3066 MHz 3066 MHz <br></span><br>--stephen<br><br><br>-- \
<br>Stephen Dowdy - Systems Administrator - \
NCAR/RAL<br>303.497.2869 - <a \
href="mailto:sdowdy@ucar.edu">sdowdy@ucar.edu</a> - \
<a href="http://www.ral.ucar.edu/~sdowdy/">http://www.ral.ucar.edu/~sdowdy/</a><o:p></o:p></p></div></body></html>
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
--===============3607601879113523435==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic