RE: KLO events sent via ITM

We have a lot of klo agent, they just works great through situation. Get the alert right the way after the poll interval.



Thanks

Jun Feng Liu

ITS-IDBD-DCS-CS-Monitoring

SOC: (416) 983-9293 | C: (416) 428-4932



http://w4.oam.td.com/oar/monitoring/client/Pages/Default.aspx




From: [email protected] [mailto:[email protected]] On Behalf Of Jay Slay
Sent: Monday, July 29, 2013 12:46 PM
To: Discussion list for Tivoli product and Tivoli Ready products.
Subject: Re: [TME10] KLO events sent via ITM

Yes the sampling interval is greyed out.
We are at 6.2.3 fp1 on osagents and KLO

We never have issues with direct eif events from these agents, but this set of servers is in a DMZ with no eif probe...which I am about to rectify.  That is the only reason we are trying to use the itm route for events.

-JKS

On Jul 29, 2013, at 12:25, John Alvord <[email protected]<mailto:[email protected]>> wrote:
A lot of my suggestions still hold...

I have run into cases where agents were running out of sync - like 15 minutes ahead or behind of the TEMS...

I would recheck that the situation is defined as pure - does the situation editor show a sampling interval of 0 and greyed out?

And - it could always be an agent defect. Are you running uplevel maintenance?

Regards,
______________________________________________

John Alvord
Advisory Engineer
IBM Tivoli Monitoring 6 Platform
Customer Support
Office: 1-720-396-2788
Mobile: none
[email protected]<mailto:[email protected]>

Cloud & Smarter Infrastructure<http://www.ibm.com/software/tivoli/>

IBM Support Portal<https://www.ibm.com/support/>
Open a New Service Request<http://www.ibm.com/support/entry/portal/Open_service_request/>
Update your PMR via Email<https://www-304.ibm.com/jct05001c/de/support/ecurep/send_email.html#naming>
Escalate your PMR<http://www-304.ibm.com/support/customercare/sas/f/handbook/getsupport.html#9>
My Blog: Wonderful World of Situations<https://www.ibm.com/developerworks/mydeveloperworks/blogs/jalvord>
Secure upload to ECUREP<https://www.ecurep.ibm.com/app/upload>








From:        Jay Slay <[email protected]<mailto:[email protected]>>
To:        "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]<mailto:[email protected]>>,
Cc:        "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]<mailto:[email protected]>>
Date:        07/29/2013 08:40 AM
Subject:        Re: [TME10] KLO events sent via ITM
Sent by:        [email protected]<mailto:[email protected]>
________________________________



Hey John...thanks for insight.

The sit is very simple...one attribute only.  It can't get any simpler.
The log entries are showing up in teps...so the agent is working at least that much.  The sit seems to fire 10 minutes later.   TEMS doesn't seem busy and I believe my guy says the same sit is working elsewhere on an similar server.  The RTEMS managing this agent has only around 200 agents on it, so it's pretty bored...or at least should be.


-JKS

On Jul 29, 2013, at 10:44, John Alvord <[email protected]<mailto:[email protected]>> wrote:

It sounds like the agent itself is messed up somehow.

A lot of processing on the remote TEMS is sequential. At any one time there can be real time request, historical data export, situations all queued up and ready to run. If anyone gets stuck in the data provider process, everything else waits.

So... I would recycle the agent and see if that changes things.

Next I would set up a test that is only running the situation and nothing else... see if that changes things.

Next I would peer at the situation - perhaps there is a *TIME which forces a TEMS evaluation and maybe the TEMS is under heavy load. Maybe there is an issue with the remote TEMS to hub TEMS communication.

I would also look at the situation - maybe it has a sampled attribute mixed in - like a LocalTime test to control when it runs. That can really mess things up badly.

I would simplify the situation formula and retest.

Things are never simple when you are "cursed with knowledge"...

Regards,
______________________________________________

John Alvord
Advisory Engineer
IBM Tivoli Monitoring 6 Platform
Customer Support
Office: 1-720-396-2788
Mobile: none
[email protected]<mailto:[email protected]>

Cloud & Smarter Infrastructure<http://www.ibm.com/software/tivoli/>

IBM Support Portal<https://www.ibm.com/support/>
Open a New Service Request<http://www.ibm.com/support/entry/portal/Open_service_request/>
Update your PMR via Email<https://www-304.ibm.com/jct05001c/de/support/ecurep/send_email.html#naming>
Escalate your PMR<http://www-304.ibm.com/support/customercare/sas/f/handbook/getsupport.html#9>
My Blog: Wonderful World of Situations<https://www.ibm.com/developerworks/mydeveloperworks/blogs/jalvord>
Secure upload to ECUREP<https://www.ecurep.ibm.com/app/upload>









From:        Jay Slay <[email protected]<mailto:[email protected]>>
To:        "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]<mailto:[email protected]>>,
Date:        07/29/2013 06:31 AM
Subject:        [TME10] KLO events sent via ITM
Sent by:        [email protected]<mailto:[email protected]>
________________________________



So before I start looking at it...one of our guys says that pure sits from several KLO agents are taking exactly 10 minutes to fire after the agent logs the match...sounds like something simple, but the sits are setup (and appear as if) they are pure as they should be.

Anyone seen this one?

-JKS

_______________________________________________
TME10 mailing list
[email protected]<mailto:[email protected]>
Unsubscribe:[email protected]<mailto:[email protected]>

_______________________________________________
TME10 mailing list
[email protected]<mailto:[email protected]>
Unsubscribe:[email protected]<mailto:[email protected]>_______________________________________________
TME10 mailing list
[email protected]<mailto:[email protected]>
Unsubscribe:[email protected]<mailto:[email protected]>
_______________________________________________
TME10 mailing list
[email protected]<mailto:[email protected]>
Unsubscribe:[email protected]<mailto:[email protected]>

NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to www.td.com/legal for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié. Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière d'aller au www.td.com/francais/avis_juridique pour des instructions.

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]