3.4. Installing the SysOrb Agent

The SysOrb Agent is a very light piece of software, with very few configuration options. It retrieves its configuration from the SysOrb Server during normal operation, so the only configuration actually needed on the agent side (for the basic agent functionality) is the list of SysOrb servers to which the Agent should check in, and a name and a SysOrb domain used by the agent to identify itself to the SysOrb server.

You can use the DNS name of the host as the Agent name, or you can use the host's IP address. Both options will allow the SysOrb server to perform NetChecks and snmpChecks on the host too, provided that the given DNS name or IP address is actually reachable from the SysOrb Server. If you do not need to perform NetChecks or snmpChecks on the host, the Agent name can be chosen freely.

On the SysOrb server you are supposed to create a node with the exact same name as specified in the configuration, in the specified domain.

Tip: Node Labels: It is usually undesirable to have a list of IP addresses displayed in the web interface, as the sole means of identifying one's monitored systems. Yet, it is sometimes a requirement that IP addresses be used for the agent names (for example, if the agent hosts do not have DNS names).

Node Labels are a solution to this problem. When configuring the agent, in the web interface, the user is provided with both an agent host name entry field (which is mandatory), and an optional "node label" entry field. Any descriptive name can be inserted into the node label field - it will then be displayed in the usual web interface host listings afterwards. The node label does not affect interaction with either NetChecks, SNMPChecks, or the agent - it is purely a displayed name.

Notice: When upgrading from version 2.4.0 you must take special care of any log checks activated on a SysOrb Agent. See Section 3.5 for details.

To actually tell the SysOrb Server to monitor a specific SysOrb Agent you need to use the SysOrb Web Interface. See User's Guide to the SysOrb Monitoring System for more information on how to use the SysOrb Web Interface.

3.4.1. Microsoft Windows XP / Server 2003 / Server 2008

The SysOrb Agent installation package is named:

sysorb-agent-3.6.0-4732.winxp-x86.msi

for 32-bit based installation or:

sysorb-agent-3.6.0-4732.winxp-amd64.msi

for a 64-bit based installation.

This file can be downloaded from http://www.evalesco.com. To start the installation procedure, either double click on the downloaded file, or execute the following command in the Command Prompt:

msiexec -i sysorb-agent-3.6.0-4732.winxp-x86.msi

When following the instructions in the installation program, please notice the dialog asking for SysOrb Server Name, SysOrb Domain and SysOrb Agent Name. If the SysOrb Server Name is incorrectly entered the SysOrb Agent will not be able to send monitoring information to the SysOrb Server. If the names cannot be entered during installation they can later be changed as described in Chapter 8 of this document.

Upgrade note: If you need to manually upgrade the SysOrb Agent package, you can proceed in two ways. The simplest way is to start by uninstalling the SysOrb Agent, through Add/Remove Programs, and then install the new package. However that will remove the configuration and requires that the key is released on the SysOrb Server. The other solution is to run the following command in the Command Prompt:

msiexec -i sysorb-agent-3.6.0-4732.winxp-x86.msi REINSTALL=ALL REINSTALLMODE=vomus

Performing the upgrade this way, will retain all your configuration, and will not require a release of the Agent's key. Please note that the upgrade command above is case sensitive and must be written exactely as shown.

3.4.2. Microsoft Windows NT / 2000

The SysOrb Agent installation package is named:

sysorb-agent-3.6.0-4732.win32.ia32.exe

This file can be downloaded from http://www.evalesco.com. Simply run the file to start the installation procedure.

When following the instructions in the installation program, please notice the dialog asking for SysOrb Server Name, SysOrb Domain and SysOrb Agent Name. If the SysOrb Server Name is incorrectly entered the SysOrb Agent will not be able to send monitoring information to the SysOrb Server. If the names cannot be entered during installation they can later be changed as described in Chapter 8 of this document.

Note: On the SysOrb download page an installation HOWTO is available, which provides a screen by screen walk-through of the Agent installation.

3.4.3. Microsoft Windows Server 2003 on Itanium

The SysOrb Agent installation package is named:

sysorb-agent-3.6.0-4732.win64.ia64.msi

This file can be downloaded from http://www.evalesco.com. To start the installation procedure, either double click on the downloaded file, or execute the following command in the Command Prompt:

msiexec -i sysorb-agent-3.6.0-4732.win64.ia64.msi

When following the instructions in the installation program, please notice the dialog asking for SysOrb Server Name, SysOrb Domain and SysOrb Agent Name. If the SysOrb Server Name is incorrectly entered the SysOrb Agent will not be able to send monitoring information to the SysOrb Server. If the names cannot be entered during installation they can later be changed as described in Chapter 8 of this document.

Upgrade note: If you need to manually upgrade the SysOrb Agent package, you can proceed in two ways. The simplest way is to start by uninstalling the SysOrb Agent, through Add/Remove Programs, and then install the new package. However that will remove the configuration and requires that the key is released on the SysOrb Server. The other solution is to run the following command in the Command Prompt:

msiexec -i sysorb-agent-3.6.0-4732.win64.ia64.msi REINSTALL=ALL REINSTALLMODE=vomus

Performing the upgrade this way, will retain all your configuration, and will not require a release of the Agent's key

3.4.4. Red Hat Enterprise Linux 5

Users of Red Hat Enterprisie linux should download either:

sysorb-agent-3.6.0-4732.rhel5-x86.ia32.rpm

for 32-bit based installation or:

sysorb-agent-3.6.0-4732.rhel5-amd64.amd64.rpm

for a 64-bit based installation.

You can download these files from http://www.evalesco.com. Also, you should make sure that you have root access to the system on which you are installing the Agent Software.

Note: These packages are for the newer enterprise Red Hat editions. If you are using an older version of Red Hat Linux, please download and install the package for Red Hat Linux 7.2 instead.

Use the RPM utility to install the package. Example:

rpm -Uvh sysorb-agent-3.6.0-4732.rhel5-x86.ia32.rpm

This should successfully install the SysOrb Agent on your system.

Please read Chapter 8 before you start the agent. The agent must know where to find its server before it will be able to do anything useful.

In order to start the SysOrb Agent after the installation, type in the command: /etc/rc.d/init.d/soagent start. Per default the Agent is configured to start in the runlevels 3 and 5.

3.4.5. Red Hat Linux 7.2, 7.3, 8 and 9

First you should download the appropriate package. For Red Hat 7.2 and newer, it is the file named:

sysorb-agent-3.6.0-4732.rh72.ia32.rpm

You can download these files from http://www.evalesco.com. Also, you should make sure that you have root access to the system on which you are installing the Agent Software.

Note: The package for Red Hat 7.2, also works on newer versions of Red Hat, i.e. 7.3, 8 and 9. For RedHat Enterprise Linux, please follow instructions in the previous section.

Use the RPM utility to install the package. Example:

rpm -Uvh sysorb-agent-3.6.0-4732.rh72.ia32.rpm

This should successfully install the SysOrb Agent on your system.

Please read Chapter 8 before you start the agent. The agent must know where to find its server before it will be able to do anything useful.

In order to start the SysOrb Agent after the installation, type in the command: /etc/rc.d/init.d/soagent start. Per default the Agent is configured to start in the runlevels 3 and 5.

3.4.6. Debian GNU/Linux 5.0 and other Debian based systems

Debian 5.0 users can download the installation package named:

sysorb-agent-3.6.0-4732.debian50.ia32.deb

for the 32-bit version and:

sysorb-agent-3.6.0-4732.debian50-amd64.x64.deb

for the 64-bit version.

The file can be downloaded from http://www.evalesco.com. This should also install on most Debian based distributions, e.g. Ubunutu. Also, you should make sure that you have root access to the system on which you are installing the agent software.

Use the dpkg utility to install the package, e.g.:

dpkg -i sysorb-agent-3.6.0-4732.debian50.ia32.deb

This should successfully install the SysOrb Agent on your system.

Please read Chapter 8 before you start the agent. The agent must know the name of it's server, to be able to checkin.

Then type /etc/init.d/soagent start to start the agent for the first time. Per default the Agent is set up to automatically start in runlevel 2.

3.4.7. Debian GNU/Linux 2.2, 3.0 and 4.0

Users of older Debian based installations (pre 5.0) can download the installation package named:

sysorb-agent-3.6.0-4732.debian22.ia32.deb

The file can be downloaded from http://www.evalesco.com. Also, you should make sure that you have root access to the system on which you are installing the agent software.

Use the dpkg utility to install the package:

dpkg -i sysorb-agent-3.6.0-4732.debian22.ia32.deb

This should successfully install the SysOrb Agent on your system.

Please read Chapter 8 before you start the agent. The agent must know the name of it's server, to be able to checkin.

Then type /etc/init.d/soagent start to start the agent for the first time. Per default the Agent is set up to automatically start in runlevel 2.

3.4.8. Mandrake Linux 9.0

Mandrake users can download the installation package named:

sysorb-agent-3.6.0-4732.mdk90.ia32.rpm

This file can be downloaded from http://www.evalesco.com. Also, you should make sure that you have root access to the system on which you are installing the Agent Software.

Use the RPM utility to install the package. Example:

rpm -Uvh sysorb-agent-3.6.0-4732.mdk90.ia32.rpm

This should successfully install the SysOrb Agent on your system.

Please read Chapter 8 before you start the agent. The agent must know where to find its server before it will be able to do anything useful. You can also run the following command to have the agent detect a suitable configuration if you have a running SysOrb server on the local subnet.

/etc/rc.d/init.d/sysorb-agent configure

In order to start the SysOrb Agent after the installation, type in the command: /etc/rc.d/init.d/sysorb-agent start. Per default the Agent is configured to start in the runlevels 3 and 5.

3.4.9. SuSE Enterprise Linux 11

If you use SuSE Enterprise Linux 11 or any newer version, you should download

sysorb-agent-3.6.0-4732.sles11-x86.ia32.rpm

for the 32-bit version and:

sysorb-agent-3.6.0-4732.sles11-amd64.amd64.rpm

for the 64-bit version.

from http://www.evalesco.com. Also, you should obtain root access to the system where you wish to install the SysOrb Agent.

Use the RPM utility to install the package, eg.:

rpm -Uvh sysorb-agent-3.6.0-4732.sles11-x86.ia32.rpm

This should install the SysOrb Agent on your system.

Please read Chapter 8 before you start the agent. The agent must know where to find its server before it will be able to do anything useful.

3.4.10. SuSE Linux 8.2 and SuSE Linux 9.0

If you use SuSE Linux 8.2 or 9.0, you should download

sysorb-agent-3.6.0-4732.suse82.ia32.rpm

from http://www.evalesco.com. Also, you should obtain root access to the system where you wish to install the SysOrb Agent.

Use the RPM utility to install the package. Example:

rpm -Uvh sysorb-agent-3.6.0-4732.suse82.ia32.rpm

This should install the SysOrb Agent on your system.

Please read Chapter 8 before you start the agent. The agent must know where to find its server before it will be able to do anything useful.

3.4.11. FreeBSD 6.0

To install the SysOrb Agent on a machine running FreeBSD 6.0 or newer, download the file named:

sysorb-agent-3.6.0-4732.freebsd6.ia32.tgz

From http://www.evalesco.com. This package contains everything needed in order to make a computer check in status information regularly to the SysOrb Server.

Note: The FreeBSD 6.0 agent also work with newer releases of FreeBSD, such as FreeBSD 7.0 and 8.0

Please note, you must have root access to the system on which you are installing this software.

You can now type:

pkg_add sysorb-agent-3.6.0-4732.freebsd6.ia32.tgz

This will install the SysOrb Agent for FreeBSD 3.5.

Your SysOrb Agent should now be installed. Please read Chapter 8 to see how the /usr/local/etc/sysorb/agent.conf agent configuration file should be set up.

In order to start the SysOrb Agent after the installation, type /usr/local/etc/rc.d/soagent.sh start.

3.4.12. Sun Solaris 8, 9 and 10

To install the SysOrb Agent on a machine running Solaris 8 or newer on UltraSPARC processor, you should download the file named:

sysorb-agent-3.6.0-4732.solaris8.sparcv9.Z, or

sysorb-agent-3.6.0-4732.solaris10-x86.ia32.Z, if running Solaris 10 on and Intel x86 processor

These files is available from http://www.evalesco.com. The packages contains everything needed in order to install the SysOrb Agent.

Please note, you must have root access to the system on which you are installing this software.

First unpack the file (using the UltraSPARC version as example):

uncompress sysorb-agent-3.6.0-4732.solaris8.sparcv9.Z

You can now type:

pkgadd -d sysorb-agent-3.6.0-4732.solaris8.sparcv9

Your SysOrb Agent should now be installed. Please read Chapter 8 to see how the /etc/sysorb/agent.conf agent configuration file should be set up.

In order to start the SysOrb Agent after the installation, type /etc/init.d/soagent start.

3.4.13. IBM AIX 5.3

To install the SysOrb Agent on a machine running AIX 5.3, download the file named:

sysorb-agent-3.6.0-4732.aix53.pwr2.bff

The file can be downloaded from http://www.evalesco.com. This package contains everything needed in order to install the SysOrb Agent.

Please note, you must have root access to the system on which you are installing this software.

You type:

installp -a -d sysorb-agent-3.6.0-4732.aix53.pwr2.bff all

Your SysOrb Agent should now be installed. Please read Chapter 8 to see how the /etc/sysorb/agent.conf agent configuration file should be set up, or you can run the following command to have the agent detect a suitable configuration if you have a running SysOrb server on the local subnet.

sysorb-testconf /etc/sysorb/agent.conf configure

After configuring the Agent, you can start it by executing /usr/sbin/soagent

3.4.14. Novell NetWare 5.1 and 6.0

To install the SysOrb Agent on Netware 5.1, you need to download the ZIP archive named:

sysorb-agent-3.6.0-4732.nw51.zip

To install the SysOrb Agent on Netware 6.0, you need to download the ZIP archive named:

sysorb-agent-3.6.0-4732.nw60.zip

The file can be downloaded from http://www.evalesco.com. This package contains everything needed in order to install the SysOrb Agent.

On your workstation, follow these steps in order to create a NetWare installation floppy for the agent:

Labeling the floppy disk: When labeling the floppy disk under Windows, users have reported various problems using the graphical user interface to label the disks. A floppy disk can safely be labeled using the command line tools though. Start up a command line (choose "run" in the Start menu, and type either cmd or command), and type the following: label a:soagent1

Now the install floppy disk is ready to be used on your NetWare servers. Follow the installation steps below, to install the agent on your server. The installation happens using the NetWare Console on the server where you are installing the agent

You must now configure your SysOrb Agent. Use the edit editor to edit the agent configuration file SYS:SYSORB\AGENT.CFG. Typically you will need to set three parameters in the file:

Finally, you can load the agent NLM. We recommend that you use the following command line to load the module:

load protected sys:\sysorb\soagent.nlm

In order to ensure that the agent starts again automatically, if the server is rebooted, this command line should be appended to the SYS:SYSTEM\AUTOEXEC.NCF file.