RE: Correlated situation overhead on ITM HTEMS

"Redus, James E CIV DISA CSD (US)" <[email protected]>
Newsgroups gmane.comp.sysutils.tivoli.general,gmane.comp.sysutils.tivoli.tme10
Message-ID <087B7894D2E468479A9A241ED6ECE84D10849F53@ugunad06.easf.csd.disa.mil>
Thanks Frank and John - glad I asked!

I was already starting to think about how to do this in Netcool after reading John's reply. Another possibility for getting user's correlation info to Netcool might be to pass some data in EIF slots of one of the to-be-correlated SITs.

Thanks again!

-James

From: [email protected] [mailto:[email protected]] On Behalf Of Dr. Frank Tate
Sent: Thursday, March 14, 2013 20:47
To: Discussion list for Tivoli product and Tivoli Ready products.
Subject: Re: [TME10] Correlated situation overhead on ITM HTEMS


I've got to agree - this should REALLY be done in Omnibus or Impact, James. And you can set up all kinds of self service possibilities (look at the MWM implementation in Impact for one example, and you can copy and modify that easily to create a notification subscription service, for example).

Frank - from my phone
On Mar 14, 2013 5:34 PM, "John Alvord" <jalvord-r/[email protected]<mailto:[email protected]>> wrote:
Be very wary...

TEMS Storage Growth and Correlated Situations
http://www.ibm.com/support/docview.wss?uid=swg21579095

Regards,




John Alvord - Ph: 1-720-396-2788<tel:1-720-396-2788>    Cell: none
Customer Support - Tivoli Software - jalvord-r/[email protected]<mailto:[email protected]>
Advisory Engineer - Tivoli Monitoring - ITM infrastructure
Follow us on Twitter! @Tivolisupport<http://twitter.com/TivoliSupport> and Facebook<https://www.facebook.com/IBMTivoliSupport>
Personalize your support needs with the IBM Support Portal<http://www.ibm.com/support/electronicsupport/>
Use Service Request<http://www.ibm.com/software/support/servicerequest/quick_start.html> to get assistance!
For emails regarding a PMR, copy [email protected]<mailto:[email protected]>
For secure browser uploads: https://www.ecurep.ibm.com/app/upload
For Customer Support guidance: IBM Software Support Handbook<http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html>









From:        "Redus, James E CIV DISA CSD (US)" <[email protected]<mailto:[email protected]>>
To:        "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]<mailto:[email protected]>>,
Date:        03/14/2013 02:12 PM
Subject:        [TME10] Correlated situation overhead on ITM HTEMS
Sent by:        [email protected]<mailto:[email protected]>
________________________________



Hi List.

A question came up recently about the growing number of ITM Correlated Situations running in our environ. These SITs run on the HTEMS, and we'd like to know if they consume a significant amount of HTEMS resources, and if so, what is a reasonable number to have running? Currently we have about 2 dozen correlated SITS.

I would think that since correlated SITs are based on a comparison of true/false values from other SITs, that the HTEMS is probably not sifting thru much data and could handle a pretty good number of these.  We have a pretty healthy 24-CPU, 16GB mem Sparc Solaris HTEMS, with a load avg that rarely goes above 2, and about 6400 OS agents in the environ (ITM 622, FP5).

Any experiences running a large number of correlated SITs?

Thanks in advance,

-James

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


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

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.