RE: ITM and AIX WPARs

WPARs are workload subsets of an existing AIX APAR. Before this you would 
need to set up new LPARs.

http://www.ibm.com/developerworks/aix/library/au-wpar61aix/

And here is how the WPAR attributes can be viewed.

http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/index.jsp?topic=%2Fcom.ibm.itm.doc_6.3%2Fosunix%2Fwksp_aix_wpar.htm

Development was asked about installing a UX agent in a WPAR and answered

ITM OS Agent can be installed in WPAR starting from 6.2.3 but it can be
used just for Remote Deployment of other agents, it can't be used to 
collect metrics. It is  the same limitation that KPX agent has. 

Starting from 6.2.3 FP1 you can install our KUX agent in LPAR and get 
metrics from WPAR partitions using KPX metrics added to our agent. 
=====================================================

So among other things that means that other agents can be installed in a 
WPAR if needed. However Unix OS Agent is involved only in a pure remote 
deploy role.

I hope that clarifies things.

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:   M Elleby <[email protected]>
To:     <[email protected]>, 
Cc:     "'Discussion list for Tivoli product and Tivoli Ready products.'" 
<[email protected]>
Date:   07/03/2013 01:36 PM
Subject:        RE: [TME10] ITM and AIX WPARs
Sent by:        [email protected]



Well, from my point of view, since I'm going through a certification 
process for AIX, it won't hurt to look at several options.

It may be that KUX may address what is currently needed.

Mike

"Manish A. Parikh" <[email protected]> wrote:

Wonder if we could use smart cloud monitoring capabilities (from IBM) to 
monitor WPARs?
 
Thank you,
 
V/r,
 
Manish A. Parikh
[email protected]
(919) 720-3699
 
From: [email protected] [
mailto:[email protected]] On Behalf Of John Alvord
Sent: Tuesday, July 02, 2013 1:38 PM
To: Discussion list for Tivoli product and Tivoli Ready products.
Subject: RE: [TME10] ITM and AIX WPARs
 
During ITM 623 and ITM 630, the KPX attributes are mostly being merged 
into the Unix OS Agent. I think there are some exceptions. I think it is 
almost done at current levels. 

The other AIX Premium agents remain - VIOS and HMC??

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:        "Mike Elleby 3.0" <[email protected]> 
To:        "'Discussion list for Tivoli product and Tivoli Ready 
products.'" <[email protected]>, 
Date:        07/02/2013 10:14 AM 
Subject:        RE: [TME10] ITM and AIX WPARs 
Sent by:        [email protected] 




Hey Jon- 
  
Many thanx for the information.  We are actually using KPX, but I had 
heard a rumor that it was being merged into the KUX agent?  So I just 
wanted to get some insight on it before I started digging. 
  
Thanx again. 
  
Mike- 
  
From: [email protected] [
mailto:[email protected]] On Behalf Of Austin, Jon
Sent: Tuesday, July 02, 2013 1:01 PM
To: Discussion list for Tivoli product and Tivoli Ready products.
Subject: RE: [TME10] ITM and AIX WPARs 
  
Mike, 
  
Not had that much hands-on time inside AIX WPAR implementations, but as I 
remember (and may well be wrong), WPARs are 'workload partitions' inside 
LPARS which are 'logical partitions'. The true OS 'machine' is the LPAR, 
and the WPAR is a collection of configuration and process management 
creating a pseudo-virtual set of resources for use, not a true virtual 
machine. In that respect, there may well be sharing of code, log files and 
the like from a common TEMA directory, which wouldn't work well. 
  
Whether you're planning to use the KPX agent (AIX Premium) or in the more 
recent levels where KPX is converging into KUX, I seem to remember many of 
the WPAR-related attribute groups have the WPAR name as an attribute. From 
that, a single TEMA to manage them all in an LPAR makes sense. You can use 
WPAR attributes to scope situations down to the rows that are the 
resources for a give WPAR. The recent KUX OS Agent User's Guide should be 
your guide. Note that at some levels during the convergence there were 
issues with non-root agent installations not having access to all the 
underlying data. It's documented in the User's Guide. 
  
Have fun with that. 
  
_________________________

Jon Austin | Senior Netcool Consultant
WINDWARD IT SOLUTIONS | Strategic thinking.  Real-world results.? 


From: Mike Elleby 3.0 [[email protected]]
Sent: Tuesday, July 02, 2013 9:24 AM
To: 'Discussion list for Tivoli product and Tivoli Ready products.'
Subject: [TME10] ITM and AIX WPARs 
Hey John A.- 
  
If you have your ears on.  I'm currently working on an effort where WPARs 
(AIX) are intending to be used in the environment, and there is a 
perception that TEMAs can't run on a local WPAR, that they can only run in 
the Global, not similar to Solaris Global/Local Zones, where I can run a 
TEMA in either zone.  They haven't started testing yet, but I wanted to be 
proactive and get some information on this item. 
  
Your thoughts? 
  
Thanx in advance. 
  
Mike Elleby 3.0_______________________________________________
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]