Setting Service Tag using smbios-sys-info

Xavier Bachelot xavier at bachelot.org
Tue Mar 6 03:30:08 CST 2012


On 03/05/2012 08:44 PM, Ryan Cox wrote:
> Did you reboot after setting the service tag? I'm pretty sure that most,
> if not all, Dell servers require a reboot for the change to be reflected.
>
Before using the DOS tool, I did reboot the server, that didn't help. 
There must be something else. Thanks for the suggestion anyway.

Regards,
Xavier


> On 03/05/2012 07:49 AM, Xavier Bachelot wrote:
>> Hi,
>>
>> I have a couple motherboards without a Service Tag (out of several
>> hundred). I'm trying to fix that using the smbios-sys-info command.
>> The servers are both R410 and R710, running either CentOS 4 or CentOS 5.
>> The CentOS 4 are running OMSA 6.1 and the CentOS 5 are running OMSA 6.5.
>> The smbios stack is version 2.2.26 in both case and is coming from EPEL.
>>
>> I'm able to set the Asset Tag, but I can't set the Service Tag.
>>
>> # smbios-sys-info --service-tag --set=XXXXXXX
>> Current tag value:
>> Service Tag:
>>
>> Setting new tag value: XXXXXXX
>> # omreport chassis info
>> Chassis Information
>>
>> Index : 0
>> Chassis Name : Main System Chassis
>> Host Name : host.example.com
>> iDRAC6 Version : 1.54
>> Chassis Model : PowerEdge R710
>> Chassis Lock : Present
>> Chassis Service Tag :
>> Express Service Code :
>> Chassis Asset Tag :
>> Flash chassis identify LED state : Off
>> Flash chassis identify LED timeout value : 300
>>
>> I had one motherboard fixed using the asset.com DOS tool, but that's not
>> convenient in my environment.
>> Does anyone have any hints on what is going on or any idea to
>> troubleshot this issue ?
>>
>> Regards,
>> Xavier
>>
>> _______________________________________________
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge at dell.com
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>



More information about the Linux-PowerEdge mailing list