Re: ITM TSM Agent

Actually, I'll be in the middle, roughly between Ocala and Gainesville. Not
much there except trees, trailers, and horse ranches. John Travolta does
have a place a few miles down the road, and sometimes you can see his 707
parked there.

Loren Cain

On Wed, Nov 14, 2012 at 9:34 AM, Gregory Mendes
<[email protected]>wrote:

>  Hey Loren,
>
> You must be in Melbourne or as I say it Melboring where I am.  LMAO
>
> Gregory R. Mendes
> 770-317-8593
>
>
> ------------------------------
> Date: Wed, 14 Nov 2012 09:19:24 -0500
>
> Subject: Re: [TME10] ITM TSM Agent
> From: [email protected]
> To: [email protected]
>
>
> Will do. I'll be finishing up all my VMware upgrades during the next month
> or so, and will then start on the Tivoli rebuild. You've got me curious
> now, though, so I may try to look at the TSM stuff next week while I'm on
> vacation. I'll be in the Middle of Nowhere, Florida, where there is
> literally nothing to do except sit in a rocking chair staring out the
> window, so I might as well work on Tivoli stuff :)
>
> Loren Cain
>
> On Wed, Nov 14, 2012 at 8:33 AM, Jay Slay <[email protected]> wrote:
>
> Loren,
>
> When you do your rebuild, let me know if you find an sk agent package that
> will allow you to install only support files and the agent.  The latest
> build out there that I (or IBM) could find contains an all-inclusive ITM
> install bundled by the horendous monstrocity of fail that is the
> "Deployment Engine".  You can't install support on an existing TEMS or
> TEPS, and you can not remote deploy or upgrade agent bundles.  Your only
> option is to install the agents locally, and install a fresh TEMS and or
> TEPS from the Monitoring for TSM media.
>
> If you find a normal ITM style package for TSM, I would love to tell IBM
> where it is.
>
>
> Thanks
>
>
>
> On Nov 14, 2012, at 8:18 AM, Loren Cain <[email protected]> wrote:
>
> Back in 2010, I installed the 6.2 version of the 'sk' agent on a number of
> Linux RHEL 5.2 32-bit systems. I performed the installation as a non-root
> user, and had no problems that I can recall (there are no problems
> mentioned in my build notes). The agent installation was performed using
> the silent method, as were the TEMS and TEPS support installations.
>
> In my case, all my TSM servers live in HA clusters, so I install the sk
> agents on the hub TEMS servers and point them at the TSM service IP
> addresses.
>
> In the past, I have gone down more or less the same road Jay did, writing
> custom UA's, and before that, custom ITM5 resource models, for TSM
> monitoring. For me at least, the sk agent worked well enough that I didn't
> need to do that this time.
>
> I will be rebuilding all my Tivoli infrastructure from scratch after the
> first of the year, so I'm sure I will be revisiting the issue then...
>
> Loren Cain
>
>
> On Tue, Nov 13, 2012 at 3:44 PM, Loren Cain <[email protected]> wrote:
>
> I have done it a number of times, but not in the last couple of years. I
> do not recall it being very difficult, once you locate the agent
> installation directories within the larger package. I am out of the office
> at the moment, but can lok into it more when I get home tonight.
> Loren Cain
> On Nov 13, 2012 3:13 PM, "Gregory Mendes" <[email protected]>
> wrote:
>
>  Hello All,
>
> Is there a hack out there for someone trying to install the TSM Reporting
> and Monitoring Agent into an already existing ITM infrastructure?  From
> what I've read and what I've tried, the only way seems to be creating a TSM
> Reporting and Monitoring server.  I'm just trying to take that TSM
> Reporting and Monitoring Agent and add application support to my existing
> ITM infrastructure.
>
> I've installed that agent on a TSM server and it starts and runs fine and
> even connects to the existing ITM infrastructure.  However, when I try to
> add support, nothing happens.
>
> Regards,
>
> Gregory R. Mendes
> Tivoli Architect/Tools Specialist
> Mendes, Inc.
> Tivoli Monitoring 6.2.3 Certified
> 770-317-8593
>
>
> _______________________________________________
> 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]
>
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
>

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