Topic
7 replies Latest Post - ‏2013-09-06T14:41:44Z by GER_MCC
wxyzabc
wxyzabc
29 Posts
ACCEPTED ANSWER

Pinned topic Service Viewer not reflecting changes acc. to rules in template

‏2013-08-28T11:17:48Z |

Hi All,

I had assigned bad for any bad or marginal for any marginal Rule to a parent Service(_2GVoice_Service).

State Change in the Service Tree is according to Rule but Service Viewer is not reflecting the color changes for  Parent service.

Please help...

Thanks & Regards

WXYZABC

Attachments

  • GER_MCC
    GER_MCC
    13 Posts
    ACCEPTED ANSWER

    Re: Service Viewer not reflecting changes acc. to rules in template

    ‏2013-08-29T10:30:22Z  in response to wxyzabc

    This is the same symptom as APAR IV28219: INCORRECT STATUS DISPLAY IN DASHBOARDS:610.

    The fix is planned for Fix Pack 2 of 610, or FP1 for 6.1.1.

    However, there is a workaround available, as this issue is caused by finer/finest log levels on the Data Server.

    To by pass the issue, the customer has two options:
     

    NOTE1: Because some service instances might already be displaying the reported symptom, it is best to set the trace level and re-start the Data server.

    NOTE2: Please backup the following file on the Data server, prior to making any changes to it:
    <installdir>/tipv2/profiles/TBSMProfile/config/cells/TBSMCell/nodes/TBSM/Node/servers/server1/server.xml

    Option 1:  Disable the "finer" debug tracing on the one module having the issue.
       Edit the above listed server.xml file and locate the following statement:

    startupTraceSpecification="*=info:com.ibm.tbsm.*=finer:com.ibm.tivoli.twa.marker.*=fine:com.micromuse.*=finer"

    Change the statement to look like this:

    startupTraceSpecification="*=info:com.ibm.tbsm.*=finer:com.ibm.tivoli.twa.marker.*=fine:com.micromuse.sla.updatepublisher.RADUpdateServer=fine"


    Option 2: Disable all "finer" debug tracing on all of the modules.  To do so, customer can perform either of these two steps:

       Edit the above listed server.xml file and locate the following statement:

    startupTraceSpecification="*=info:com.ibm.tbsm.*=finer:com.ibm.tivoli.twa.marker.*=fine:com.micromuse.*=finer"

    Change the statement to look like this:

    startupTraceSpecification="*=info:com.ibm.tbsm.*=fine:com.ibm.tivoli.twa.marker.*=fine:com.micromuse.*=fine"

    • wxyzabc
      wxyzabc
      29 Posts
      ACCEPTED ANSWER

      Re: Service Viewer not reflecting changes acc. to rules in template

      ‏2013-09-03T09:39:12Z  in response to GER_MCC

      Hi GER_MCC

      Thanks for your reply....

      Second Step of Option 2 was already set in server.xml.

      I tried to change it for error only like-

      startupTraceSpecification="*=info:com.ibm.tbsm.*=error:com.ibm.tivoli.twa.marker.*=error:com.micromuse.*=error"

      But still facing the same problem ,also service tree Ticket columns(additional colunm to show no. of tickets) are not displaying correct no.

      Please help.

      Thanks & Regards

      wxyzabc

       

      • GER_MCC
        GER_MCC
        13 Posts
        ACCEPTED ANSWER

        Re: Service Viewer not reflecting changes acc. to rules in template

        ‏2013-09-04T14:33:41Z  in response to wxyzabc

        To determine if this is a Dahboard or Data server issue you could re-start the Dashboard and see if the issues persists. If the issue persists, then the issue is likely on the Data Server. If so, enable the Consistency Checker to see if this resolves the problem. If not, you may need to open a PMR.

        • wxyzabc
          wxyzabc
          29 Posts
          ACCEPTED ANSWER

          Re: Service Viewer not reflecting changes acc. to rules in template

          ‏2013-09-06T06:05:14Z  in response to GER_MCC

          Hi GER_MCC,

          As you replied in your 3rd post  "The fix is planned for Fix Pack 2 of 610, or FP1 for 6.1.1.".

          We raised a PMR for the same issue as its not solved it....But PMR people replied that...

          "Prerequisites for installating TBSM 6.1.0 FixPack 2 is "IBM Tivoli Business Service Manager Version 6.1"
          http://www-01.ibm.com/support/docview.wss?uid=swg24032540

          This Fix Pack is scheduled to release Q4, 2013.
          Note: This is a target date and does not represent a formal commitment by IBM. This date is subject to change without notice.
          "

          So can you please clarify which FP2 you were talking about?

          Thanks in advance...

          Regards

          wxyzabc

          • GER_MCC
            GER_MCC
            13 Posts
            ACCEPTED ANSWER

            Re: Service Viewer not reflecting changes acc. to rules in template

            ‏2013-09-06T06:39:58Z  in response to wxyzabc

            I am referring to TBSM 6.1.0 FixPack 2 planned for Q4 2013. However, if an APAR in this FixPack will resolve your issue, we can investigate sending you an APAR specific fix in the meantime. Can you please share the PMR number so I can follow up?

            • wxyzabc
              wxyzabc
              29 Posts
              ACCEPTED ANSWER

              Re: Service Viewer not reflecting changes acc. to rules in template

              ‏2013-09-06T07:10:19Z  in response to GER_MCC

              Hi GER_MCC,

              Thanks for your so quick reply..

              This is the PMR no.-40490689864

              Also, yesterday after restarting DataServer, we observed that everything was working fine (Status and Tickets Columns were updating as it should).But now WebGUI again stucked ,its not updating anymore.Not able to understand cause of the problem.

              Please help.

              Thanks & Regards

              wxyzabc

              • GER_MCC
                GER_MCC
                13 Posts
                ACCEPTED ANSWER

                Re: Service Viewer not reflecting changes acc. to rules in template

                ‏2013-09-06T14:41:44Z  in response to wxyzabc

                Hi - I talked to L2 about this PMR and it seems 610 FP1 is missing from your system. FP1 is a very important FP. Please install FP1 for 6.1.0 and if the problem persists, send logs for the PMR.