ADDM / Discovery is not discovering UUID or serial number for Linux or Unix servers

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Discovery


    COMPONENT:

    BMC Atrium Discovery and Dependency Mapping


    APPLIES TO:

    BMC Atrium Discovery and Dependency Mapping



    PROBLEM:

    ADDM / Discovery is not discovering UUID or serial number for Oracle Red Hat Enterprise Linux Server, or for other Linux or Unix servers.










     


    CAUSE:

    various


    SOLUTION:

    The Linux platform script commonly uses lshal, dmidecode, and hwinfo to read data from the system BIOS.
    The dmidecode and hwinfo commands require superuser privileges.

    Please see:
    https://docs.bmc.com/docs/display/DISCO111/Adding+privileged+execution+to+commands
    https://docs.bmc.com/docs/display/DISCO111/Privileged+commands

    To edit the Linux platform "init" script, perform these steps:
    Administration->Platforms->Linux
    Click "Edit" to the right of the "init" script (Initialise)
    Click inside the edit window to make it larger

    Change these lines to add the yellow highlighting like this:
    OLD:

    # dmidecode requires superuser privileges to read data from the system BIOS PRIV_DMIDECODE() {     "$@" } # hwinfo requires superuser privileges to read data from the system BIOS PRIV_HWINFO() {     "$@" }
      
    NEW:  
    # dmidecode requires superuser privileges to read data from the system BIOS PRIV_DMIDECODE() {     /usr/bin/sudo "$@" } # hwinfo requires superuser privileges to read data from the system BIOS PRIV_HWINFO() {     /usr/bin/sudo "$@" }
      
    NOTE 1:  It is best to edit this script directly in the edit window.  Don't copy/paste from a Windows editor because this can cause problems with having the wrong kinds of double-quotes. 
    (Don't copy/paste from this KA either).  See KA:  000148423 

    NOTE 2: In addition to calling the dmidecode and hwinfo commands with "sudo" from the Discovery platform script, these commands must have privileges to run with sudo as the Discovery user.  (The sudoers file must allow this on the target system). 

    NOTE 3: In one case, the lshal command was present but not working on one particular server It was working on other servers. The issue seemed to be with the messagebus service on the target server. Once the service was restarted, the scan returned the correct serial number (and uuid) information. 


      

     


    Article Number:

    000122292


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles