Before installing up.time you must:
All communication with client systems is over TCP using port 9998. However, you can specify a different port during the installation process. All communication originates from the Monitoring Station. When a host that is being monitored is outside a firewall, you only need to configure outbound port access.
The installation procedure creates the user ID uptime on the Monitoring Station. The uptime user ID should also exist on all of the clients, as using this ID will minimize any security risks by not running the agents as a privileged process.
Wherever possible, do not use the root account to run the Monitoring Station or any up.time agents.
You can use other existing user accounts for the agent, such as nobody , bin , or adm . However, using these accounts may pose security risks depending on other system processes that run under these accounts.
On HP/UX, you cannot start processes, such as agents, using the nobody user ID. Also, on Windows operating systems, the agent must be running with Administrator privileges. If it is not, the agent will not be able to access the system performance counters. |
This section describes the system requirements for the up.time Monitoring Station and up.time Agents.
The hardware configurations for a Monitoring Station can change depending on the number of agents that you want to monitor, the reports that you want to generate, and the amount of data that in the up.time DataStore.
Contact uptime software Client Care if you are monitoring more than 50 nodes. |
The following is the recommended minimum hardware:
You can install and use up.time agents to collect data from a number of operating systems. Check the uptime software Client Care Web site for the most up-to-date list of supported platforms and architectures.
up.time can monitor Novell NetWare NRM version 6.5. Earlier versions of NRM are not supported. |
up.time also supports agentless monitors on any operating system, which do not require you to install software on a system or device. See Using Agentless Monitors.
The up.time Monitoring Station is a system running the core up.time software that retrieves information from client systems, either through agents installed on the system or by monitoring services running on the system. The Monitoring Station has a self-contained Web server and database that enables easy access to the application and data.
Before installation, refer to the uptime software support portal ( http://support.uptimesoftware.com ) for the most up-to-date platform lists:
The Monitoring Station is installed a single directory:
On Windows, the up.time Monitoring Station is installed using a graphical installer that guides you through the steps of the installation process. On Solaris or Linux, the installer is a console application.
Before installing up.time, you must be logged in as a local (i.e., non-domain) administrator (in Windows) or as root (in Solaris or Linux). |
In addition to the (included) MySQL database, up.time can also use either an Oracle or MS SQL Server database as its DataStore. If you plan to use either of these databases, refer to our Knowledge Base for the additional steps required to enable up.time to work with these databases.
There are twoways in which to install the up.time Monitoring Station:
If you have downloaded the up.time distribution from the uptime software Web site, copy the archive to a temporary directory on the system that will host the Monitoring Station. For the Windows installer, extract the contents of the archive using a utility like WinZip.
If you are installing up.time as an appliance on an ESX server, you can download the package from the uptime software web site, either directly or through the VMware Virtual Appliance Marketplace. Unarchive the Virtual Appliance package and note its location; you will need to locate the .ovf file during the import procedure.
Once preparations have been made, refer to the appropriate procedure below for details on completing the installation for your platform:
To install the up.time Monitoring Station on Windows, do the following:
up.time may not function properly if the Monitoring Station is installed when you are logged in as a domain or non-local administrator.
up.time-<version#>.<build#>-win32-x86.exe
Where <build#> is the number of the up.time build that you are installing. For example:
up.time-<version#>.<build#>-win32-x86.exe
Because the DataStore can grow very large (in excess of 100 GB), you can install the DataStore in another folder on the file system if you are monitoring a large number of systems and retaining data for extended periods. |
The email address from which the Monitoring Station will send alerts and reports to users.
The number of the port on which the DataStore (the up.time database) will listen for requests. The port number is written to the file uptime.conf .
The name of the computer that is hosting the Web server. This name is written to the file httpd.conf , which contains configuration information for the Web server used by up.time .
The number of the port on which the Web server for the Monitoring Station will listen for requests. The port number is written to the file httpd.conf .
The installation process will take several minutes.
The following occurs:
Installation on Solaris or Linux is done at the command line. In addition to installing the up.time application, the installation process attempts to create the uptime user ID (which run applications in non-privileged mode). If it already exists, then the installer will use that account.
To install the up.time Monitoring Station on Solaris or Linux, do the following:
up.time may not function properly if the Monitoring Station is installed when you are logged in as a domain or non-local administrator.
sh up.time-<version#>.<build#>-<platform>.bin
where <build#> is the number of the up.time build that you are installing, and <platform> is the operating system on which you are installing up.time . For example:
It can take up to several minutes for the components of the installer to be extracted from the .bin file. Wait while this process completes.
The uptime user account must be able to access the directory that you specify. |
Because the DataStore can grow very large (in excess of 100 GB), you can install the DataStore in another folder on the file system if you are monitoring a large number of systems and retaining data for extended periods. |
The name of the computer that is hosting the Web server. This name is written to the file httpd.conf , which contains configuration information for the Web server used by up.time .
The number of the port on which the Web server for the Monitoring Station will listen for requests. The port number is written to the file httpd.conf .
The email address from which the Monitoring Station will send alerts and reports to users.
The number of the port on which the DataStore (the up.time database) will listen for requests. The port number is written to the file uptime.conf .
The installation process will take several minutes.
The following occurs:
It can take up to a minute for the up.time services to start. Wait before attempting to log into the Monitoring Station |
To install the up.time Monitoring Station as a Virtual Appliance, do the following:
Wait for the import process to complete.
The default time zone is PST. The appliance time zone must match that of your monitored infrastructure in order to correctly collect and report performance data.
It can take up to a minute for the up.time services to start. Wait before attempting to log into the Monitoring Station. |
After installing up.time , you will need to do the following:
If this Monitoring Station installation is for a standalone up.time instance that is not part of a multi-datacenter deployment, skip this section and use the default bundled MySQL implementation; otherwise, you must configure the Monitoring Station to write to an Oracle database instance instead of MySQL. To switch the database used by the Monitoring Station, edit the uptime.conf file.
To edit the uptime.conf file to use an Oracle database instance instead of MySQL, do the following:
# dbDriver=com.mysql.jdbc.Driver
# dbType=mysql
# dbHostname=localhost
# dbPort=3308
# dbName=uptime
# dbUsername=uptime
# dbPassword=uptime
If you are using a previous version of up.time and intend to upgrade to version 7.0, you can find detailed information about the upgrade process at the Client Care Web site (http://support.uptimesoftware.com/upgrade.php).
up.time agents are used to retrieve detailed performance statistics - such as CPU, memory, process, disk, and network usage - from the hosts that you are monitoring. The agents can also securely and remotely execute programs. The Windows agent can start and stop services, and reboot the machine.
The installation process for agents varies by operating system. On UNIX, Linux, and IBM pSeries systems installation is done at the command line using a script. On Windows, installation is done using a graphical utility.
All client systems must be accessible via a name. This name should exist in either the /etc/hosts table on the Monitoring Station, or be accessible via a nameserver - for example files, NIS, or DNS. If the host IP is changed then the Monitoring Station may send requests to the incorrect machine. |
The installer for Windows up.time agents uses a wizard that guides you through the installation process.
If the Windows installer requires unavailable service packs - for example, SiteServer or Terminal Server - send an email to [email protected] and request the extracted agent which can be installed without using the Windows installer. |
Note - If the Windows installer requires unavailable service packs - for example, SiteServer or Terminal Server - send an email to [email protected] and request the extracted agent which can be installed without using the Windows installer. |
To install an agent on Windows, do the following:
up.time may not function properly if the Monitoring Station is installed when you are logged in as a domain or non-local administrator.
Alternatively, click the Browse button and use the dialog box that appears to search for the folder.
You install up.time agents for Solaris at the command line.
To install an agent on Solaris, do the following:
You should copy the archive to a temporary directory on the system.
tar -xvf uptmagnt-<version>.tar
Where <version> is the version of the agent, for example solaris-4.0 .
pkgadd -d
You install up.time agents for various UNIX platforms at the command line using a shell script.
To install an agent on a UNIX system, do the following:
You should copy the archive to a temporary directory on the system.
Depending on the version of UNIX, you will need to extract the archive using either the tar command or a combination of the gzip and tar commands. For example, to extract the agent for AIX use the following command:
tar -xvf uptmagnt-AIX-<version>.tar
./INSTALL.sh
You can install up.time agents for Linux using the RPM utility or the Debian package management utility (dpkg). This enables you to easily update and perform mass installations of agents.
Before trying to install an agent, ensure that the RPM or dpkg utilities are installed and are in the path by typing one of the following commands at the command line: which rpm |
To install an agent on a Linux system, do the following:
rpm -i <agent name>
Where <agent name> is the name of the .rpm file for the agent that you are installing. For example, uptimeagent-4.0.rpm .
dpkg -i <agent name>
Where <agent name> is the name of the .deb file for the agent that you are installing. For example, uptimeagent-4.0.deb .
up.time can collect workload information from IBM pSeries servers that have logical partitions (LPARs). To have up.time collect this information, you must install the latest AIX or Linux agents on the on the LPARs whose workloads you want to profile.
There are two options for installing agents on IBM pSeries servers with logical partitions (LPARs):
In both cases, you will need to install the agent on each LPAR; whether you use an HMC determines how the agent is installed on the Virtual I/O (VIO) partition.
Before you can monitor the logical partitions on an IBM pSeries server, you must install an agent on each LPAR and on the VIO. Use the following instructions to install the agent on an IBM pSeries server that is managed by an HMC.
To install an agent on an LPAR that is on IBM pSeries server with an HMC, do the following:
up.time communicates with the HMC to acquire LPAR information.
rpm -i <agent name>.rpm
Where <agent name> is the name of the .rpm file for the agent that you are installing (e.g., UptimeAgent-Linux-<version>.rpm ).
Where <agent name> is the name of the archive that contains the agent that you are installing (e.g., uptmagnt-AIX-<version>.tar ).
./INSTALL.sh
If you are using an HMC, do not install the agent as a Virtual I/O Server by using the “-vio” attribute with the install command. Doing so may lead to conflicts with HMC-managed systems, and can result in incorrect performance statistics. |
oem_setup_env
tar -xvf <agent name>
Where <agent name> is the name of the archive that contains the agent that you are installing (e.g., uptmagnt-AIX-<version>.tar ).
./INSTALL.sh
Before you can monitor the logical partitions on an IBM pSeries server, you must install an agent on each partition. Use the following instructions to install the agent on an IBM pSeries LPAR that is not managed by an HMC, but whose partitions are managed by the Integrated Virtual Manager (IVM).
To install the agent, do the following:
rpm -i <agent name>.rpm
Where <agent name> is the name of the .rpm file for the agent that you are installing (e.g., UptimeAgent-Linux-<version>.rpm ).
tar -xvf <agent name>
Where <agent name> is the name of the archive that contains the agent that you are installing. For example, uptmagnt-AIX-<version>.tar .
./INSTALL.sh -vio
tar -xvf <agent name>
Where <agent name> is the name of the archive that contains the agent that you are installing. For example, uptmagnt-AIX-<version>.tar .
./INSTALL.sh -vio