12 Replies Latest reply on Dec 19, 2019 10:55 AM by Andrew Waters

    Missing Serial number

    Savita G
      Share This:

      We have around few servers for which ADDM is not able to fetch serial number. All these servers are VM's (Unix RHEL, Solaris )

      But these servers has serial number in them . By seeing session logs we are not able to get much information .

       

      getHostInfo script is successfully executed on these servers . But serial number is set to "NOT SET" in ADDM.

       

      We are using ADDM 11.1.0.8 and  April 2019 TKU

        • 1. Re: Missing Serial number
          Andrew Waters

          Have you given Discovery sufficient permission to get the value?

           

          You are going to have to be more specific to get specific help. What are you seeing in the session logs?

          2 of 2 people found this helpful
          • 2. Re: Missing Serial number
            Savita G

            Yes , the discovery is given sufficient permission required . We are able to see serial number for many servers apart from few

             

            In session logs , I dont see the below command dmidecode that has executed from ADDM on the servers that has issue .

             

            (root) NOPASSWD: /usr/sbin/dmidecode \"\"

            • 3. Re: Missing Serial number
              Andrew Waters

              How have you determined that?

               

              The system builds a function which is executed so the individual command will not appear interspersed in the results.

               

              Presumably, if not using a privileged command, you have defined PRIV_DMIDECODE to use sudo. What happens if you run dmidecode on the machine?

              1 of 1 people found this helpful
              • 4. Re: Missing Serial number
                Lisa Keeler

                We have KA: 000122292 about this common problem.

                 

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

                 

                The KA mentions specific OS, but it contains general information for Linux/Unix servers.

                3 of 3 people found this helpful
                • 5. Re: Missing Serial number
                  Cory Garcia

                  Lisa,

                   

                  This seems to have fixed 2 issue's for me as well - so glad I monitor the community

                   

                  Issue 1 resolved:  Serno Missing for Most Linux (getting it for Unix)

                   

                  Issue 2 resolved: Missing Physical Memory for Linux - I was just about to start playing with a script I found on the community but this change resolved the missing memory issue as well.

                   

                  Question: Why was this change not just implemented in a TKU?

                  note: I ask because I am currently monitoring but have found no adverse affects from this change - want to make sure I am covering my bases.

                   

                  Thanks for your constant monitoring of the community and thanks BMC Discovery team and Peers for supporting our community (its nice to fix issues before they are even reported by my users )

                  1 of 1 people found this helpful
                  • 6. Re: Missing Serial number
                    Lisa Keeler

                    Hi Cory,

                     

                    I assume that you edited the "init" script to add "sudo" like this, per the KA:

                     

                    # 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 "$@"
                    }

                     

                    The "init" script is designed to be edited by the customer to meet the requirements of their environment to utilize sudo as desired.

                     

                    I doubt that the TKU will ever be updated to use sudo by default.  Customer must take action to use sudo.

                     

                    Lisa

                    4 of 4 people found this helpful
                    • 7. Re: Missing Serial number
                      Hitesh Jha

                      Andrew,

                      I have checked in the tw_svc_eca_engine log and unable to found anything related to serial no.

                      Could you please let me know which logs exactly do I need to validate.

                       

                      E01-140062816741120: 2019-12-13 16:30:39,816: engine.actions: INFO: 10.182.2.10: Starting scan

                      E02-140104306063104: 2019-12-13 16:30:39,817: engine.actions: INFO: 10.182.10.11: Starting scan

                      E02-140104306063104: 2019-12-13 16:36:27,569: analysis.connection_linker: INFO: Consider connection details for Host 'fr2pnvlmard1'...

                      E02-140104306063104: 2019-12-13 16:36:27,588: analysis.connection_linker: INFO: fr2pnvlmard1: SIs: 3; candidate SIs: 0; containers: 0; processes: 219; services: 0; connections: 0; listening ports: 0; observed relationships: 0.

                      E02-140104306063104: 2019-12-13 16:36:27,623: analysis.connection_linker: INFO: fr2pnvlmard1: Candidate SI summary: 0 confirmed; 0 created; 0 aging; 0 aged out; 0 replaced.

                      E02-140104306063104: 2019-12-13 16:36:27,624: analysis.connection_linker: INFO: fr2pnvlmard1: Relationship summary: 0 confirmed; 0 created; 0 suppressed; 0 aging; 0 aged out; 0 removed due to suppression.

                      E02-140104306063104: 2019-12-13 16:37:14,798: analysis.model_definition: INFO: Update model definitions for Host 'fr2pnvlmard1'...

                      E02-140104306063104: 2019-12-13 16:37:14,798: analysis.context: INFO: Construct service model (root node state : root node plus one hop) for 1 node (fr2pnvlmard1)...

                      E02-140104306063104: 2019-12-13 16:37:14,852: analysis.context: INFO: Service model complete. 4 nodes, 3 relationships.

                      E02-140104306063104: 2019-12-13 16:37:14,853: analysis.model_definition: INFO: Nodes included in 0 model definitions

                      E02-140104306063104: 2019-12-13 16:37:16,987: engine.actions: INFO: 10.182.10.11: Finished scanning

                      • 8. Re: Missing Serial number
                        Andrew Waters

                        I would not expect anything in that log.

                         

                        If you are running a shell script on the machine being discovered (ssh, rlogin, telnet) then you need to look at the getHostInfo script for that platform. If you do discovery with session logging on then you can look at the interaction with the machine. Alternatively you can run the commands on the machine itself. That should be able to distinguish when something does not have permission or fails to find the value in any specific case.(session logging docs configure on the credential and viewing)

                         

                        It is hard to be specific without details on what you are discovering.

                        1 of 1 people found this helpful
                        • 9. Re: Missing Serial number
                          Hitesh Jha

                          Andrew,

                          Thanks for your response.

                          when I executing the command manually on the target itself getting an error as permission denied using our discover account.

                          I have executed dmidecode and hwinfo as well but same response.

                          Sharing you the o/p for one of the command for reference.

                          But server fr2pnvvlmard1 we are getting the serial no but unable to validate which command it's executing in order to retrieve serial no.

                          Actually for few servers we keep the same level of permission for the discover account and it's working on few of them but not for others.

                          so that's the confusion.

                           

                          [root@fr2pnvlmard1 ~]# lshw -C system|grep -i serial
                              serial: VMware-42 2f 15 85 8f fe ac 77-b8 5c a6 dc 41 8e 96 6e

                           

                           

                          but not able to run the command using discover user

                           

                           

                          [discover@fr2pnvlmard1 ~]$ lshw -C system|grep -i serial
                          WARNING: you should run this program as super-user.
                          WARNING: output may be incomplete or inaccurate, you should run this program as super-user.

                           

                          • 10. Re: Missing Serial number
                            Andrew Waters

                            Do you have privilege escalation allowed from some commands for the discovery account, normally sudo, but not on the machines which you are failing to get the serial number.

                            • 11. Re: Missing Serial number
                              Hitesh Jha

                              How do we check that ?

                              Could you please also let me know which logs do we need to check to understand which command are using to extract the serial no info for particular target.

                              • 12. Re: Missing Serial number
                                Andrew Waters

                                Have you configured any of the the PRIV command scripts to use sudo or some other escalation?

                                 

                                For example PRIV_DMIDECODE, if so then you need to check if your discovery account has rights to use sudo with dmidecode on the machine. If you have defined PRIV_DMIDECODE you can check by running sudo /usr/sbin/dmidecode

                                1 of 1 people found this helpful