topic Telalert as a SG package in Operating System - HP-UX

Telalert as a SG package

Laurie Gellatly — Tue, 14 Jan 2003 20:45:03 GMT

Hi.
Background: Two "identical" L 1000 running
11.0 and SG.
Both machines configured to use the remote port
for the modem for use by telalert.
NNM and VPO driving telalert.
Anyone made telalert a part of the package
of VPO to swap with VPO? Any tricks in so doing
as telalert would be tied to the IP of NNM/VPO
package.
Alternative seems to be to start stop a local
copy of telalert when the VPO package starts
on the machine.
Thanks ...Laurie :{)

Re: Telalert as a SG package

Manju Kampli — Wed, 15 Jan 2003 03:29:04 GMT

Hi Laurie,

you could use the local copy of telalert on both the systems OR install the telalert in the share file system and configure the SG package to use this file system .. so when the package is moved from one node to other, this file system is also moved.'

The second option would be a true SG package

Hope this helps,
Manju

Re: Telalert as a SG package

John Palmer — Wed, 15 Jan 2003 08:04:09 GMT

Hi Laurie,

I have telalert running as part of a Remedy package and don't have any problems with it.

To cope with different pathnames, I have a telelert config file for each server in the cluster and export TELALERTINI=telalert.ini.$(hostname) before starting telalert.

Regards,
John

Re: Telalert as a SG package

Laurie Gellatly — Wed, 15 Jan 2003 08:19:01 GMT

Thanks for the reply.
I already know the difference in terms of
creating a package or standalone.
What I was really trying to find out was how
telalert ties itself the IP address for its
licence. When I try to run it up with the
NNM package's IP as the IP for the licence
telalert tells me that that IP is not an IP
of this server. So how do you make telalert
attach to the package IP so that it flips
with the package from machine to machine?

Thanks ...Laurie :{)

Re: Telalert as a SG package

John Palmer — Wed, 15 Jan 2003 08:29:26 GMT

If I remember correctly, telalert is licensed to an IP address which is configured in the init file with:
HostIPAddress=...

It appears that the version that we use (fairly old) checks that the hostname resolves to an IP address on the server. I do the following when I start telalert:

HOST=$(hostname)
uname -S
telalert -start -init
uname -S ${HOST}

Regards,
John

Re: Telalert as a SG package

Laurie Gellatly — Thu, 16 Jan 2003 10:52:34 GMT

John,
The combination of your answers were just about perfect. Enjoy the points.
I would like to still use the admin gui instead
of editing the file but the telalerts seems
to be tying itself to "localhost:28xxx" and
the gui can't find it. Ideas?

Thanks ...Laurie :{)