Re: KLO events sent via ITM

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 
jalvord-r/[email protected]

Cloud & Smarter Infrastructure
IBM Support Portal
Open a New Service Request
Update your PMR via Email
Escalate your PMR
My Blog: Wonderful World of Situations
Secure upload to ECUREP







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

Cloud & Smarter Infrastructure 
IBM Support Portal
Open a New Service Request
Update your PMR via Email
Escalate your PMR
My Blog: Wonderful World of Situations
Secure upload to ECUREP 








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

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

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