I wonder if somebody knows if IBM is working to develop agents to another Linux S.O. Because today the ITM 6.2 agents run only in Suse, Red Hat and so on... I wonder for example, if IBM is developing agents to run on ubuntu, gentoo, slackware and others distributions. I ask it because many webservers and network servers from our customers run on slackware, ubuntu and gentoo.
LPIC-1 Professional Certified
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2008-02-26T14:25:49Z by SystemAdmin
Pinned topic About Linux S.O Agents
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2008-02-26T14:25:49Z at 2008-02-26T14:25:49Z by SystemAdmin
SystemAdmin 110000D4XK6056 PostsACCEPTED ANSWER
Re: About Linux S.O Agents2008-02-26T14:25:49Z in response to SystemAdminHi.
As far as i know, IBM wont develop for linux other than RHEL/SUSE or RPM based distributions (more or less "compatible" of suse/rhel)
The only real technical dependancy when installing Linux OS agent is the RPM based package GlobalSecurityKit of IBM.
Others components are dynamic executables / JAVA.
In a non IBM supported (i guess) environnement, you can manage to install a Linux OS agent that way :
- Extract and install files from gskit RPM (rpm2cpio, alien, etc).
linux-gate.so.1 => (0x00205000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x0099c000)
libm.so.6 => /lib/libm.so.6 (0x0095a000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00110000)
libc.so.6 => /lib/libc.so.6 (0x00206000)
- Install the product with normal installation, except the RPM part, all should work correctly.
If that does not, i had many times deployed agents with a simple TAR of the $CANDLEHOME (+ the gskit so) and managed it to work on debian and slackware.
this is a ldd output of the main binary of the Linux OS agent : klzagent
linux-gate.so.1 => (0x00790000)
libnsl.so.1 => /lib/libnsl.so.1 (0x00ca3000)
libpthread.so.0 => /lib/libpthread.so.0 (0x009fe000)
librt.so.1 => /lib/librt.so.1 (0x00a17000)
libdl.so.2 => /lib/libdl.so.2 (0x003c0000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x02096000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x0043c000)
libm.so.6 => /lib/libm.so.6 (0x003c4000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x07ec7000)
libc.so.6 => /lib/libc.so.6 (0x00a20000)
libgsk7iccs.so => /usr/lib/libgsk7iccs.so (0x007c6000)
libresolv.so.2 => /lib/libresolv.so.2 (0x003eb000)
And by the way, concerning monitoring webservers/network appliances, i would suggest you to look of the side of SNMP monitoring.
This is not only a compatibility advice, but a performance planning one too; for monitoring small parts of informations (as webserver stats, network appliance state, etc), the SNMP is quicker and lighter than the OS Agent.
IBM UNIX & Storage specialist