View Source


h3. 1. Installing Agent Using YUM

h4. 1.1 Configure YUM Repository

*YUM* is the easiest way to keep programs up-to-date on RedHat-compatible distributions. It downloads and installs the latest version of a program. You should configure the *YUM repository* to manage install and [upgrades|Upgrading Enterprise Agent for Linux] of CDP Agent.

First, create a YUM {{.repo}} file with the R1Soft repository information. Save the file in the {{yum.repos.d}} directory which is typically located in {{/etc/}}.

1. Open the new file with a text editor such as *vi* or *nano*:

{code}# cd /etc/yum.repos.d
# vi r1soft.repo{code}
{code}# nano -w /etc/yum.repos.d/r1soft.repo {code}


2. Insert the following text into the file and save the file:

name=R1Soft Repository Server


3. To verify what is written to the file, use the following command:

{code}# cat /etc/yum/yum.repos.d/r1soft.repo {code}


h4. 1.2 Install the Package

Once you have configured the YUM repository, you can use the following command to install CDP Agent:
{code}# yum install r1soft-cdp-enterprise-agent{code}

!linux agent 6.png|border=1!

h3. 2. Install Agent Manually (Using RPM)

h4. 2.1 Download CDP Agent

See [Obtaining Linux CDP Enterprise Agent].

h4. 2.2 Make Sure You Can Unzip the Download

Most Linux distributions come with the *unzip* utility pre-installed. To determine if you have the *unzip* utility, run:

{code}# which unzip{code}

This should return an output similar to the following:

{code}# which unzip


If it returns the following output, you need to install the *unzip* utility first:

{code}unzip: Command not found.{code}

To install unzip on RHE, CentOS, and Fedora:

{code}# yum install unzip{code}

!install standard.png!

h4. 2.3 Extract the ZIP File

We recommend creating a temporary directory to which you can extract the contents of the ZIP file.

1. Use the {{mkdir}} command to create a temporary directory (in our case, {{cdp-agent}}).

{code}# mkdir cdp-agent{code}

2. Use the {{mv}} command to move the archive to that directory. Note that Linux file names are case sensitive. Make sure you type the name correctly (in our case, "**").

{code}# mv cdp-agent{code}

3. Use the {{cd}} command to go to that directory.

{code}# cd cdp-agent{code}

4. Use the {{unzip}} command to extract the files.

{code}# unzip{code}

h4. 2.4 Install the Package

{note:title=Notice}You must be a Linux root user to install CDP Agent.
The archive you have extracted contains two folders: one with {{.deb}} packages (in our case, "*deb-linux64*") and one with {{.rpm}} packages ("*rpm-linux64*"). On RedHat and CentOS, select the {{.rpm}} package.

Each folder contains a set of CDP components:

* {{r1soft-setup}}
* {{r1soft-cdp-enterprise-agent}}
* {{r1soft-cdp-agent}}
* {{r1soft-cdp-async-agent-2-6}}

You will need to install all of them in one step. Use the {{cd}} command to go to the folder with the packages (in our case, {{rpm-linux64}}) and run the following command:

*RPM 32-bit (x86)* / *RPM 64-bit (x86_64)*

{code}rpm -i *.rpm{code}


h3. 3. Install CDP Linux Device Driver

CDP Device Driver is a proprietary, loadable Linux kernel module distributed by R1Soft. It is loadable at run-time without restarting Linux, and you do *not* need to recompile your Linux kernel to use it. R1Soft does not provide prebuilt modules for the popular kernels anymore, so you will have to compile the module from source.

{note:title=Notice}You need to have loadable modules enabled as a feature in your kernel, and this is standard on all popular Linux distributions.

h4. 3.1 Compiling CDP Kernel Module Against Kernel Headers or Kernel Source Tree

Using a pre-built binary module package is not possible anymore. You will have to compile this module against kernel headers or a kernel source tree. We are not always able to compile kernel modules from kernel-devel packages supplied by most major Linux distributions. In some cases, packages are missing header files (broken), or the packages have been stripped of information that any device driver would need to compile a kernel module. In these cases, we can build using your installed kernel-devel package on your Linux server, as r1soft-setup will obtain the missing information it needs to compile a module from your running kernel.

In order for kernel module compilation to work, you should have Internet connectivity directly from the Linux server you are installing CDP on, to TCP port HTTPS (443), on the host

You can test connectivity with the following command (this may take a minute):

{code}# r1soft-setup --test-connection{code}

h4. 3.2 Install Kernel Sources

If you are using an unmodified kernel provided by CentOS installer, install the kernel-devel package:

{code}# yum install kernel-devel{code}


h4. 3.3 Verify that the Source Matches Your Running Kernel

Sometimes, the kernel-devel package is newer than the installed and running kernel. If the kernel-devel is too old and not found, please follow the instructions on how to setup access to older yum packages as documented [here|kb3:Finding Old kernel-devel Packages For CentOS].

h4. 4.4 Build the CDP Kernel Module Online (direct Internet connection to R1Soft build server)

To attempt to build the kernel module, run the following command (this may take several minutes):

{code}# r1soft-setup --get-module

!install standard 209.png!

If module has been compiled and installed successfully, you will see an output similar to the following:

{code}Saving kernel module to '/lib/modules/r1soft/hcpdriver-cki-2.6.32-220.4.1.el6.x86_64.ko'
Kernel module is now installed.
Use '/etc/init.d/cdp-agent restart' to load the new driver

h4. 3.5 Build the CDP Kernel Module Offline (without direct Internet connection to R1Soft build server)

If there is no direct Internet connection between your CDP server and R1Soft build server, it is still possible to compile the kernel module. In this case, this will be tree-step process. First, you will have to create tarball file with the kernel headers. When you should copy this tarball file from the server to some other computer which has Internet connection to R1Soft build server. From this computer you should upload the tarball to the R1Soft build server and wait for the compilation to finish. When it is finished, you should download binary module and copy it back to the CDP server. Start with executing the following command:

{code}# r1soft-setup --no-binary --kernel-dir /usr/src/kernels/YOUR_KERNEL_TREE
--tarball-only /tmp/kernel-headers-for-r1soft.tar.gz{code}

After running this command, you will see:

{code}# r1soft-setup --no-binary --kernel-dir /usr/src/kernels/2.6.32-220.4.1.el6.x86_64
--tarball-only /tmp/kernel-headers-for-r1soft.tar.gz
Gathering kernel information
Gathering kernel information complete.
Creating kernel headers package
Checking '/usr/src/kernels/2.6.32-220.4.1.el6.x86_64' for kernel headers
Found headers in '/usr/src/kernels/2.6.32-220.4.1.el6.x86_64'
Header package created '/tmp/kernel-headers-for-r1soft.tar.gz'
visit to do an offline module build
After it is complete, you will need to copy the module to /lib/modules/r1soft{code}


h4. Last Step

* Copy the generated {{tar.gz}} file and paste it to a computer with Internet access.
* Go to [] and upload the {{.tar.gz}} file to build a kernel module.
* After the build, you will download a kernel module.
* Copy this module and paste it to your Linux Server and the folder {{/lib/modules/r1soft}}.
* Restart the Server ({{/etc/init.d/cdp-agent restart}}).

{excerpt:hidden=true}Instructions on how to install CDP Agent 4.0 Enterprise Edition on CentOS, RHE, and Fedora.{excerpt}