Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Tivoli monitoring

Status
Not open for further replies.

php3390

Technical User
Feb 5, 2005
13
SA
Hi,

In our datacenter, Tivoli Management System is installed. Now we would like to monitor a new server ( OS: AIX 5.1 ;ML 03 ) using the Tivoli monitoring system. The new server is henceforth called as "AIX-5.1 endpoint".
The TMA is successfully installed ( version:109)on the same. The TMF being 3.71. Java 1.3 is sucessfully installed on the 'AIX-5.1 enpoint'.
The main Tivoli monitoring server can communicate with the endpoint and report it's status. When we try to distribute using 'wmdist' command, success is reported. Howver when we use "wdmlseng -e name-of-endpoint ", we get following error:

"AMW0250I - No profiles are running on the endpoint."

At the endpoint, we can verify that the profile is running on the endpoint (using 'ps' command of the unix).
Can any one help us please?

Thanks & Regards
Arun
 
did you install distributed monitoring on the Endpoint Gateway. The Dm profiles get pushed to the server only when DM is installed on the Gateway.

Bas
 
check out

wdmlseng -e Endpoint_name

and

wdmlseng -e Endpoint_name -verbose


to see if the monitor is running on the endpoint. This should be run from the TMR, but any managed node will work. Also, follow bas1080's suggestion
 
php3390 - Try to stop and restart the ITM engine and then redistribute the monitors.

1. wdmcmd -stop -e endpoint_name
2. wdmcmd -restart endpoint_name
3. Redistribute the monitors.

=======
 
Hi,
check, if JRE really was distributed. If you have the mdist2 database in place you could run a mdist -l to check the delivery status.
Check on the endoint under lcf/bin/aix4-r1 if there's the JRE directory.
ITM logfiles on the endpoint are under lcf/dat/1/LCFNEW (search for *.log). Reading them you should find out, what's wrong.
And by your endpoint version I can tell, that's from framework 3.7.1 which is not supported anymore but still should work.
Especially make sure to upgrade your ITM to latest level, since there's been millions of bugs.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top