Topic
2 replies Latest Post - ‏2012-04-26T11:15:36Z by SystemAdmin
Sammy1984
Sammy1984
46 Posts
ACCEPTED ANSWER

Pinned topic TSRM Gateway Issue

‏2012-04-17T14:05:43Z |
Hello Everyone,

I am facing some serious issue with TSRM gateway. I have configured TSRM gateway to generate tickets for all critical events. This is working perfectly as for every critical event ticket is generated in ITSRM.

By default whenever any critical event gets cleared (changes severity to 0-clear from 5-critical), the status of that ticket should get changed to RESOLVED in ITSRM. This is working fine except for Default Chassis Ping Failed events. Otherwise for all other events this is working fine i.e, when ever critical event gets cleared, the status of that particular event's ticket in ITSRM also set to RESOLVED automatically.

The following are my environment details:
Operating System : RHEL 5.5 64-bit
Netcool Omnibus V7.3.1
TSRM Gateway V3.0

Any advice or help to fix this issue is really appreciated.
Thank you.
Updated on 2012-04-26T11:15:36Z at 2012-04-26T11:15:36Z by SystemAdmin
  • Sammy1984
    Sammy1984
    46 Posts
    ACCEPTED ANSWER

    Re: TSRM Gateway Issue

    ‏2012-04-18T17:40:27Z  in response to Sammy1984
    Can anyone please reply to this post??

    At least give me some hints to look into this issue. I am stuck in the middle of no where...!!!!
    • SystemAdmin
      SystemAdmin
      1283 Posts
      ACCEPTED ANSWER

      Re: TSRM Gateway Issue

      ‏2012-04-26T11:15:36Z  in response to Sammy1984
      Assuming the standard scenario, whatever logic is there in omni-tsrm gw, it is generic for all alerts. But since you say that this is happening only for Default Chassis Ping Failed alerts, check that the Default Chassis alert is not coming again due to policy of itnm running in background...say every 5 mins. If that is happening maybe, that event is overwritten with a new alert?
      Also try inserting a dummy Default chassis ping alert (with exact summary,severity which you use for raising tsrm tickets) manually in objectserver, try to resolve it manually and see how things proceed.

      Abhishek