| SysOrb Network Monitoring System Administrator's Guide: For version 4.6.0 | ||
|---|---|---|
| Prev | Chapter 3. Installing SysOrb | Next |
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.
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.
The SysOrb Agent installation package is named:
sysorb-agent-4.6.0-6039.win7-amd64.amd64.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-4.6.0-6039.win7-amd64.amd64.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-4.6.0-6039.win7-amd64.amd64.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.
Users of Red Hat Enterprise linux should download:
sysorb-agent-4.6.0-6039.centos6-amd64.amd64.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: 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-4.6.0-6039.centos6-amd64.amd64.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.
Debian 7.0 users can download the installation package named:
sysorb-agent-4.6.0-6039.debian7-amd64.x64.deb
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-4.6.0-6039.debian7-amd64.x64.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.
To install the SysOrb Agent on a machine running Solaris 11 on an x86_64, you should download the file named:
sysorb-agent-4.6.0-6039.solaris11-amd64.x86.p5p
Please note, you must have root access to the system on which you are installing this software.
In order to install the agent on the global zone of a Solaris 11 system, issue the command:
pkg install -g sysorb-agent-4.6.0-6039.solaris11-amd64.x86.p5p sysorb-agent
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.
The status of the agent service can be inquired using the command svcs soagent. The agent service can be enabled using the command svcadm enable soagent.