Thank you! That helps. I have 12G servers so I used 'chassis info'.
I have one note for anyone else doing this: After setting the tag, 'chassis info' now showed the Asset Tag I set. However, when I used 'smbios-sys-info-lite', it did not immediately show the Asset Tag I set: [root@system]# omreport chassis info | grep Asset Chassis Asset Tag : 2625446 [root@system]# smbios-sys-info-lite | grep Asset Asset Tag: Not Specified After rebooting the system, 'smbios-sys-info-lite' showed the Asset Tag I set. Thanks again! -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, September 12, 2018 1:18 AM To: [email protected]; [email protected] Subject: Dell libsmbios conflict with EPEL6 libsmbios Dell - Internal Use - Confidential Hi Jacobson, Based on below email, looks like you have installed OMSA 9.1.0 on your system. OMSA Command line utility helps you to configure the "Asset Tag" for your system. I recommend you to leverage already installed OMSA utility. Here is the command to configure the Asset Tag: If your server is prior to 13th Generation then use this command: omconfig chassis info index=0 tag=<String> If Your server is 13th Generation or later then use this command: omconfig chassis biossetup attribute=assetag seting=<String>. Please refer OMSA Command Line User guide for more details: https://www.dell.com/support/manuals/us/en/04/dell-openmanage-server-adminis trator-9.1/om_9.1_command_line_interface_guide/introduction?guid=guid-800c0f 9c-94f9-4893-ab05-1c3754260261&lang=en-us Due to some reason, If you have uninstalled OMSA on your system then you can safely remove the libsmbios (libsmbios-2.3.1-2757.12163.el6.x86_64) package which got installed along with OMSA. Now, you should be able to install "smbios-sys-info" without conflict. Let us know if this helps. Regards, Chandra ---------------------------------------------------------------------- Message: 1 Date: Tue, 11 Sep 2018 12:57:09 -0400 From: "Robert Jacobson" <[email protected]> To: <[email protected]> Subject: [Linux-PowerEdge] set asset tag: Dell libsmbios conflict with EPEL6 libsmbios Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" I want to set the asset tag for my systems, but I'm finding that the utility to do so, "smbios-sys-info" cannot be installed due to a library conflict with the Dell-provided libsmbios in OMSA (see below). Is there a workaround for this? Resolving Dependencies --> Running transaction check ---> Package smbios-utils-python.x86_64 0:2.2.26-3.el6 will be installed --> Processing Dependency: python-smbios = 2.2.26-3.el6 for package: smbios-utils-python-2.2.26-3.el6.x86_64 --> Running transaction check ---> Package python-smbios.x86_64 0:2.2.26-3.el6 will be installed --> Processing Dependency: libsmbios = 2.2.26-3.el6 for package: python-smbios-2.2.26-3.el6.x86_64 --> Running transaction check ---> Package libsmbios.i686 0:2.2.26-3.el6 will be installed --> Finished Dependency ResolutionError: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for libsmbios which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libsmbios of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude libsmbios.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of libsmbios installed, but yum can only see an upgrade for one of those arcitectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of libsmbios installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: libsmbios-2.2.26-3.el6.i686 != libsmbios-2.3.1-2757.12163.el6.x86_64non-zero return code -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20180911/cf1 8fb68/attachment-0001.html> ------------------------------ Subject: Digest Footer _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge ------------------------------ End of Linux-PowerEdge Digest, Vol 172, Issue 1 *********************************************** _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
