6 Replies Latest reply on Dec 24, 2013 6:50 AM by Gustavo del Gerbo

    Identification of Child CIs if the parent is already identified

    Ryan Wiltshire

      Example, we create a computersystem manually in BMC.ASSET and also create an IPEndpoint record associated to the Computer system via Hosted Access Point.

       

      We import discovery data to an import data set. The computer system identifies and weak relationships are processed identifying the IPEndpoint as well. Both are matched successfully to the existing records in BMC.ASSET.

       

       

      I then create another manual IP address in BMC.ASSET associated to the same Computer System. Discovery runs and finds a new IP address for the computer system. This time when identification runs, the new IP address in the import data set is not matched to the new IP manually created in BMC.ASSET.

       

       

      If a reset the reconciliation identity on the Computer System in the import data set, both IPEndpoint records are identified correctly again.

       

       

      Question: why is identification not processing weak relationships correctly for already identified parent CIs?

       

      Note: CMDB version 7.6.04

        • 1. Re: Identification of Child CIs if the parent is already identified
          Gustavo del Gerbo

          This time when identification runs, the new IP address in the import data set is not matched to the new IP manually created in BMC.ASSET.

          <---- THIS is where the problem is.

           

          Do you have RE logs for that?

          Have you reviewed the identification rules for IP endpoint? Are you using standard rules or custom ID rules?

           

          The below here should not be needed:

          If a reset the reconciliation identity on the Computer System in the import data set, both IPEndpoint records are identified correctly again.

          • 2. Re: Identification of Child CIs if the parent is already identified
            Ryan Wiltshire

            The rules are good. The IP identification is simplified to use only the Name field. The name is set to the IP address.

             

            The rules work when the Parent is not identified. When the parent, in this case a Computer System, gets identified, there seems to a be process to identify all the children. Once the parent is identified, that process seems to skip looking into the destination data set for children and generates a new reconciliation identity for the new children added after the parent has been identified.

             

            [2013/10/20 19:30:55.7534] [DETAILS] [TID: 1081452864]  : Assigning parent instance <class = BMC.CORE:BMC_ComputerSystem, instance id = OI-3f1a9971c1634081b2ff89f99e36b495> to a thread for identification

            [2013/10/20 19:30:55.7535] [DETAILS] [TID: 1081452864]  : Skipping parent instance <class = BMC.CORE:BMC_ComputerSystem, instance id = OI-3f1a9971c1634081b2ff89f99e36b495> for identification as this parent is being identified currently

            [2013/10/20 19:30:55.7536] [DETAILS] [TID: 1081452864]  : Skipping parent instance <class = BMC.CORE:BMC_ComputerSystem, instance id = OI-3f1a9971c1634081b2ff89f99e36b495> for identification as this parent is being identified currently

            [2013/10/20 19:30:55.7538] [DETAILS] [TID: 1081452864]  : Skipping parent instance <class = BMC.CORE:BMC_ComputerSystem, instance id = OI-3f1a9971c1634081b2ff89f99e36b495> for identification as this parent is being identified currently

            [2013/10/20 19:30:55.7539] [DETAILS] [TID: 1081452864]  : Skipping parent instance <class = BMC.CORE:BMC_ComputerSystem, instance id = OI-3f1a9971c1634081b2ff89f99e36b495> for identification as this parent is being identified currently

            • 3. Re: Identification of Child CIs if the parent is already identified
              Devendra Yadav

              Before answering your question - It's never recommended that you create/update data directly in BMC.ASSET, BMC.ASSET should be always populated by reconciliation engine.

               

              On you question for IP End points - Follwing are the OTB rules on IP Endpint

              P1 : 'TokenId' != "0" AND 'TokenId' != $\NULL$ AND 'TokenId' = $TokenId$

              P2 : Name' != $\NULL$ AND 'Name' = $Name$

               

              if CI which you manually created and one which discovered doesn't have same TokenId or Name then RE will create them as different CI and they will bot be merged into one.

               

              Thanks,

              Devendra Yadav

              • 4. Re: Identification of Child CIs if the parent is already identified

                Did you ever figure this out. I see the same behavior but can't find any documentation on when it works and when it doesn't. Nothing from support yet either. Must be a secret.

                • 5. Re: Identification of Child CIs if the parent is already identified
                  Ponnusamy Subramaniam

                  We too had the same issue and BMC provided us with a hot fix. Please create a support ticket with BMC.

                  • 6. Re: Identification of Child CIs if the parent is already identified
                    Gustavo del Gerbo

                    Hi,

                     

                    This issue is resolved in SP5.

                    If you are not in this version I recommend that you upgrade at the earliest. If for some reason you cannot upgrade you can request BMC to send you the SP5 arrecond binaries so that at least you run that product in the latest version.