6 Replies Latest reply on Dec 19, 2017 7:26 AM by Bhuvaneswaran Ekanathan

    mcell not starting - in IS cell - 10.7

    Kaushik KM

      Dear experts,

       

      We tried to integrate SCOM with Truesight using seemless connector.

      we received one test event from SCOM after integrating, but cell stopped responding and not starting after receiving that event.

      Please find the cell logs and mcdb attached...

       

      i tried to run the cell in foreground with "mcell -d -n <cellname>"

      it stops at that particular event received from  SCOM: please find the screenshot below:

       

      we had copied the class rules and collectors and gateway file to the respective folders and made entries at proper places.

      Please look into this what might cause this condition????

        • 1. Re: mcell not starting - in IS cell - 10.7
          Bhuvaneswaran Ekanathan

          Kaushik KM

           

          Did you try to run state builder ?

           

          Try to compile the cell mccomp -n cellname and it will give details of the error. At times, when you are importing class and rules for Adapter based integration, you could run into permission or encryption related issues. Once it is fixed and cell could reload and recompile with the changes, mcell would work fine.

           

          If you are still having issues, you can enable cell trace that will give finer details to look into and resolve

           

          KnowledgeArticle - BMC

           

          Thanks,

          Bhuvan

          • 2. Re: mcell not starting - in IS cell - 10.7
            Kaushik KM

            Hi Bhuvan,

            I tried running state builder, no luck.

             

            I have enabled the rule trace and restarted the cell but i see the following trace, i dont see any error or cell shutting down... cell is just unresponsive.

            Please find the logs attached..

             

            BAROC: BMC_TS-IMC032262V: Upgrade event #5907 @0x24cfa80 to context Engine

            20171208 103734.606000 mcell: RULES: BMC_TS-IMC110004V: Trace rule level set to 2

            20171208 103734.638000 mcell: RULES: BMC_TS-IMC110070I: Starts indexing  of match tables

            20171208 103734.653000 mcell: RULES: BMC_TS-IMC110071I: Indexing  of match tables completed

            20171208 103734.669000 mcell: RULES: BMC_TS-IMC110077V: Start reloading generic actions

            20171208 103734.669000 mcell: RULES: BMC_TS-IMC110079V: generic actions reloaded

            20171208 103734.669000 mcell: SIM: BMC_TS-IMC222048V: Starting topological ordering of the sim model

            20171208 103734.669000 mcell: SIM: BMC_TS-IMC222049V: Topological ordering of the sim model completed

            20171208 103734.685000 mcell: BAROC: BMC_TS-IMC032262V: Upgrade event #5907 @0x24cfa80 to context Engine

            20171208 103734.685000 mcell: EVTPROC: BMC_TS-IMC090106V: Transfer event #5907 @0x24cfa80 to Rule Engine

            20171208 103734.685000 mcell: RULES: BMC_TS-IMC110007V: Starting transaction on event #5907 @0x24cfa80

            20171208 103734.685000 mcell: RULES: BMC_TS-IMC110008V: Analysing event #5907 @0x24cfa80

            20171208 103734.716000 mcell: RULES: BMC_TS-IMC110801I: iimom.mrl, 36: new iimom_alert_duplicate: MOM_EV #5907: Rule execution starting with

            $NEW = 0x24cfa80 (class: MOM_EV,   event_handle: 5907, mc_ueid: iimom_iimom_calidcvwms100.p0lnur.4126874)

            20171208 103734.716000 mcell: RULES: BMC_TS-IMC110801I: im_internal.mrl, 1283: execute im_internal_timeout: MOM_EV #5907: Rule execution starting with

            $EV = 0x24cfa80 (class: MOM_EV,   event_handle: 5907, mc_ueid: iimom_iimom_calidcvwms100.p0lnur.4126874)

            20171208 103734.716000 mcell: RULES: BMC_TS-IMC110806I: im_internal.mrl, 1285: execute im_internal_timeout: MOM_EV #5907: when block execution starting

            20171208 103734.716000 mcell: RULES: BMC_TS-IMC110801I: PWC_reopened_time.mrl, 1: execute reopened_time: MOM_EV #5907: Rule execution starting with

            $EV = 0x24cfa80 (class: MOM_EV,   event_handle: 5907, mc_ueid: iimom_iimom_calidcvwms100.p0lnur.4126874)

            • 3. Re: mcell not starting - in IS cell - 10.7
              Kaushik KM

              Hi Everyone!

               

              Looking at the above logs, we can see that the mcell logs are stopping at the below lines:

              20171208 103734.716000 mcell: RULES: BMC_TS-IMC110801I: PWC_reopened_time.mrl, 1: execute reopened_time: MOM_EV #5907: Rule execution starting with

              $EV = 0x24cfa80 (class: MOM_EV,   event_handle: 5907, mc_ueid: iimom_iimom_calidcvwms100.p0lnur.4126874)

               

               

              The PWC_reopened_time.mrl was not allowing cell to proceed further,

              We removed that rule from load file started cell again,it worked fine!!

              Not sure whats wrong in the logic: Let me know your inputs please

               

              ########################

              execute reopened_time : EVENT($EV)

                 where [$EV.status != CLOSED]

                 when $EV.mc_operations contains 'REOPENED'

                 {

                    $STR = listgetelt($EV.mc_operations, 1);

                    $EV.mc_tool_time = stringtoint($STR);

                 }

                 END

              ############################

              • 4. Re: mcell not starting - in IS cell - 10.7
                Bhuvaneswaran Ekanathan

                Kaushik KM

                 

                Cell performance would be impacted with the current logic. Use below to optimize the MRL,

                 

                • Update ECF in a way, only certain events for which MRL needs to be executed are evaluated

                 

                • Prefer avoiding 'contains' especially in 'execute' phase. Preference is to use 'equals' condition in 'when' clause

                 

                • Wherever possible, use hashed index to improve cell performance

                 

                Indexes in rules - BMC TrueSight Infrastructure Management 11.0

                 

                mc_operations is a LIST_OF STRING slot and with the ECF, every event that is not in 'CLOSED' status will be evaluated to check if it contains 'REOPENED' and could impact cell performance.

                 

                From MRL, I understand you are trying to update mc_tool_time with event reopened time. In the rule, where you are re-opening the event, update mc_tool_time using time_stamp() function

                 

                Thanks,

                Bhuvan

                1 of 1 people found this helpful
                • 5. Re: mcell not starting - in IS cell - 10.7
                  Kaushik KM

                  Hi Bhuvaneswaran Ekanathan

                   

                  Yes you are correct.

                  That mrl is present in our old environment, we caught this while migrating the cell to newer version 10.7

                  We are using the below mrl to do the above task.

                  #########################

                  execute Event_Status: EVENT($EV)

                  where [$EV.blackout_slot == "Blackout"]

                  when $EV.status == OPEN

                  {

                  $EV.mc_tool_time = time_stamp();

                  }

                  END

                  #################################

                  We have another mrl which will update the blackout slot as required by above mrl which is shown below:

                  #################################

                  refine update_mc_tool_key : EVENT($EV)

                  where [$EV.status == BLACKOUT]

                  {

                  $EV.blackout_slot = 'Blackout';

                  }

                  END

                  #################################

                   

                  Thank you again!!

                  • 6. Re: mcell not starting - in IS cell - 10.7
                    Bhuvaneswaran Ekanathan

                    Kaushik KM

                     

                    Glad that it worked.

                     

                    My point is, there is no need to write a separate 'execute' phase [below] to set mc_tool_time with time_stamp() function when event is re-opened.

                     

                    execute Event_Status: EVENT($EV)

                    where [$EV.blackout_slot == "Blackout"]

                    when $EV.status == OPEN

                    {

                    $EV.mc_tool_time = time_stamp();

                    }

                    END

                     

                    In the same rule phase where you are re-opening the event, I believe you will have a timer as part of execute phase, you can set mc_tool_time slot.

                     

                    Thanks,

                    Bhuvan