You install or upgrade vRealize Log Insight agents on Windows or Linux machines, including those with third-party log management systems.
Agents collect events and forward them to the vRealize Log Insight server. During installation, you can specify parameters for the server, port, and protocol settings or choose to keep the default settings.
You can upgrade agents using the same methods you use for installation, or you can use auto-upgrade. Auto-upgrade propagates upgrades to agents when you deploy a new version of vRealize Log Insight. See Automatic Update for vRealize Log Insight Agents for more information. Upgrade is not available for Linux binary packages.
To install and run a vRealize Log Insight agent, your hardware must support the minimum parameters required for hosts/machines that support x86 and x86_64 architecture and MMX, SSE, SSE2, and SSE3 instruction sets.
|Operating System||Processor Architecture|
|Windows 7, Windows 8, Windows 8.1, and Windows 10||x86_64, x86_32|
|Windows Server 2008, Windows Server 2008 R2,||x86_64, x86_32|
|Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016||x86_64|
|RHEL 5, RHEL 6, and RHEL 7||x86_64, x86_32|
|SuSE Enterprise Linux (SLES) 11 SP3 and SLES 12 SP1||x86_64|
|Ubuntu 14.04 LTS and 16.04 LTS||x86_64|
|VMware Photon, version 1 revision 2, and version 2||x86_64|
If you implement a default installation of the Log Insight Linux Agent for a user without root privileges to use, the default configuration might create problems with the data collection. The agent does not log a warning that the subscription to the channel is unsuccessful, and files in the collection do not have read permissions. The message Inaccessible log file ... will try later is repeatedly added to the log. You can comment out the default configuration that is causing the problem or change the user permissions.
If you use an rpm or DEB package to install Linux agents, the init.d script named liagentd is installed as part of the package installation. The bin package adds the script, but does not register it. You can register the script manually.
You can verify that the installation was successful by running the (/sbin/) service liagentd status command.