Installing OpManage 8.0 on SLES 10 SP2April 10, 2009
Network and device managers abound, but the OpManage platform from AdventNet keeps building features and capabilities. Unfortunately, their embrace of Windows and Linux installation choices leaves some in the lurch depending on the platform chosen.
Recently I took version 8.0 for a spin on a trimmed-down installation of SLES 10 SP2. As has been typical with this platform on Suse systems, there were some issues requiring resolution before OpManager was up an running. Fortunately, the issues were localized to the apache server that comes with OM8.
First up, in my trimmed-down install (minimal X-windows, no additional servers), no Apache was included as a SLES package (i.e. in an attempt to avoid package collision). This required the following changes to the SLES environment after OM8 installation:
create file: /etc/ld.so.cond.d/opmanage.conf edit, add: /opt/AdventNet/ME/OpManager/apache/lib run: ldconfig
Next, trouble-shooting the remainder of the apache-related issues uncovered the following dependencies:
create link: ln -s /usr/lib/libgdbm.so.3 /usr/lib/libgdbm.so.2 create link: ln -s /usr/lib/libdb-4.3.so /usr/lib/libdb-3.2.so create link: ln -s /usr/lib/libexpat.so /usr/lib/libexpat.so.0
Once completed, test the service by issuing the following:
cd /opt/AdventNet/ME/OpManager/bin run ./StartOpManagerServer.sh
OpManager will point-out the service port you chose during installation. Remember SUSE’s firewall services manager if you get stuck accessing OpManager from the “web client” – it is deny-all by default when enabled.
From the first 15-minutes with the new OpManager, it is clear that AdventNet has come a long way since the early days of the product. There are many new features and devices supported. Check it out for yourself if you’re still shopping for a network/server monitoring system that runs nicely in a virtual machine…
Comments are closed.