This section tells you how to install Caldera Volution Manager and its components. The following information is included:
Hardware Requirements Section 3.1
Software Requirements Section 3.2
Installing VM Clients Section 3.3
Troubleshooting VM Client Installations Section 3.4
A 386, 486, or Pentium compatible PC
A minimum of 32 MB of RAM
6 MB of free space on the hard drive
Volution Manager supports the following as Volution Manager Clients (VM Clients):
Caldera OpenLinux 2.3 (server version), 2.3.1 (server version), 2.4 (desktop version), and 3.1.1 (server and desktop versions)
UnixWare 7.1.1
Open UNIX 8 and LKP
SCO OpenServer 5.0.4, 5.0.5, 5.0.6, and 5.0.6a
Red Hat® Linux® 6.2, 7.0, and 7.1
TurboLinux ® 6.0 (Server and Workstation versions), 6.1 (Server version), and 6.5 (Server version)
SuSE® Linux® 6.4, 7.0, 7.1, 7.2, and 7.3
Mandrake® Linux® 7.0, 7.1, 7.2, 8.0, and 8.1
RedFlag® Linux® Server versions 2.0 and 3.0 and RedFlag Linux Desktop versions 2.0 and 3.0
Laser5 Workstation 6.4
Conectiva® Linux® 6.0
Kondara 1.1 MNU/Linux® (Server and desktop versions)
Note: This list represents a current snapshot at the time of printing. For a more complete list, see the Caldera web site:
http://www.caldera.com/support
Instructions in this section detail how to install VM Clients on Linux, SCO OpenServer, UnixWare, and Open UNIX 8 operating systems. VM Clients are Linux or UNIX systems that can be managed by the VM Server. Each installed VM Client runs the VM Client daemon (volutiond) which includes support for OpenSLP, the protocol the VM Client uses to locate the VM Server.
Use the installation section that matches the VM Client platform you are installing. For information on what distributions of Linux are supported and the supported releases levels of SCO OpenServer, UnixWare, and Open UNIX 8, see Section 3.2.
Important: Update the VM Client installed with OpenLinux 3.1.1 with the release version of the Linux client from the CD.
There are two methods of installing VM Clients running Linux: using the installation script and installing manually.
You can use the installation script./install.sh to install VM Clients on all support platforms.
You can also install VM Clients using the manual installation method. With the manual method you can use all of the options available with the Volution Manager Key Tool. The Key Tool is a command line key and certificate configuration tool that allows you to view, import, and configure keys and certificates installed on your system. Like the installation script, you can manually check the fingerprint of the VM Client CA certificate, but you can also use other features of the tool.
You can install and start VM Clients on all supported platforms of Linux using one script, install.sh. This script installs all of the required RPMs and then automatically starts the VM Client daemon, volutiond. On VM Clients using Linux distributions, this script is particularly useful because it provides an alternative to manually installing the 4 required RPMs and then starting the client daemon. The install.sh installation script automatically starts the VM Client.
Use the -c switch (./install.sh -c) to view the VM Client certificate authority (CA) certificate. The purpose of this is to ensure that it matches the CA certificate on the VM Server. You would only need this extra measure of security if you were concerned that another unauthorized VM Server might be installed in your network. To view the CA certificate on the VM Server, enter the following on the VM Server:
/opt/volution/bin/volutionkeytool cacert list
To run the install.sh script,
Insert and mount the Volution Manager CD.
Note: On Caldera OpenLinux enter /auto/cdrom to automount the CD.
Change to the client directory on the Volution Manager CD.
Enter
./install.sh
Note: Use the -c switch to view the CA certificate at the end of the installation and confirm that the VM Client is contacting the correct VM Server. Use -h to list other available switches.
If prompted for the SLP scope, press enter to accept the default unless you have manually configured Volution Manager to use a different scope. For more information on SLP scopes, see Section 2.7.
If prompted for the hostname or IP address of an SLP DA, enter the name or IP address of the VM Server and press enter. For more information on the SLP DA, see Section 1.1.9 in the subsection, Section 1.1.9.1.3.
The VM Client daemon is installed and started. To verify that the daemon is running enter
ps -ef |grep volutiond
A list of running processes appears.
To install a VM Client on Linux using the manual method, complete the following as a root user and install the RPMs in the order listed:
Insert and mount the Volution Manager CD.
Change to the /mnt/cdrom/client directory.
Install OpenSLP by entering the following:
rpm -Uvh openslp-<versionnumber>.i386.rpm
Install SNMP by entering the following:
rpm -Uvh ucd-snmp-<versionnumber>.i386.rpm
Install OpenSSL by entering the following:
rpm -Uvh openssl-<versionnumber>.i386.rpm
Install the VM Client by entering the following:
rpm -Uvh volution-<versionnumber>.386.rpm
Note: If you are using multiple OpenSLP scopes in your network, change the scope at this time. For information on using multiple scopes refer to, Section 2.7.
Note: This procedure is only required if you are concerned that your managed clients could contact the wrong Volution Manager Server (VM Server). It must be done before you start the VM Client.
The Volution Manager Key Tool is a command line key and certificate configuration tool that allows you to view, import, and configure keys and certificates installed on your system. It provides an extra measure of security. If you have concerns about your managed VM Clients communicating with an unauthorized VM Server or if you have more than one VM Server in your network, use the Volution Manager Key Tool (installed with the VM Client RPM) on each VM Client.
Complete the following as the root user.
Make sure you are logged in as root.
Change to the opt/volution/bin directory.
Enter the following:
./volutionkeytool cacert import
Use the following format for other commands:
./volutionkeytool command
Where command is one of the following:
help (-help or --help)- Displays usage message.
cacert create- Creates a new Volution Manager CA certificate.
cacert import- Imports a Volution Authority certificate.
cacert list- Lists Volution CA certificates on this host.
cert list- Lists Volution certificates that have been issued for this host.
cert issue-Issues (or re-issues) new certificates for this host.
cert request- Issues a new certificate using a certificate request.
crl add- Adds a certificate to the certificate revocation list.
crl list- Lists the certificates on the certificate revocation list.
The issuer, subject, and fingerprint of the CA certificate appears.
To cross check this fingerprint with the fingerprint on the CA certificate installed on the VM Server you must know what the fingerprint on the CA certificate installed on the VM Server is. To display the certificate on the VM Server, enter:
/opt/volution/bin/volutionkeytool cacert list
You must start each of the client services to initiate them. Start the client RPMs by entering the following commands in the order listed:
/etc/rc.d/init.d/slpd restart
/etc/rc.d/init.d/snmpd start
/etc/rc.d/init.d/volutiond start
Once the VM Client daemon named volutiond is installed and started it uses OpenSLP to find the Volution Manager computer creation daemon named volutonccd on the VM Server. The volutionccd sends back the server certificate key and LDAP information to the VM Client so it can securely connect to and be managed by Volution Manager. The volutionccd also creates the computer object for that managed client in the LDAP directory. The VM Client can now be managed by Volution Manager.
You can check if the client daemon is running by entering the following command in a terminal window.
ps -ef|grep volutiond
A list of processes appears.
Note: SCO OpenServer 5.0.4 and 5.0.5 clients require that you install the Practical Extraction and Reporting Language (Perl). Perl is available on the Skunkware CD. For information on where it should be installed, see Section 3.4.
There are two methods of installing VM Clients running SCO OpenServer: using the installation script and installing manually.
You can use the installation script./install.sh to install VM Clients on all support platforms.
You can also install VM Clients using the manual installation method. With the manual method you can use all of the options available with the Volution Manager Key Tool. The Key Tool is a command line key and certificate configuration tool that allows you to view, import, and configure keys and certificates installed on your system. Like the installation script, you can manually check the fingerprint of the VM Client CA certificate, but you can also use other features of the tool.
The install script,./install.sh installs VM Clients on all supported platforms. This script installs required packages then automatically starts the VM Client.
If you have SNMP installed, make sure you use the -s switch (./install.sh -s). The -s switch keeps the VM Client installation from overriding your current SNMP installation.
Use the -c switch to view the VM Client certificate authority (CA) certificate. The purpose of this is to ensure that it matches the CA certificate on the VM Server. You would only need this extra measure of security. To view the CA certificate on the VM Server, enter the following on the VM Server:
/opt/volution/bin/volutionkeytool cacert list
Use both switches (./install.sh -s -c) if you want the script to perform both functions.
To run the install.sh script,
Insert and mount the Volution Manager CD.
Change to the client directory on the Volution Manager CD.
Enter
./install.sh
Note: Use the -s switch if SNMP is already installed. Use the -c switch to view the CA certificate at the end of the installation and confirm that the VM Client is contacting the correct VM Server. Use -h to list other available switches.
If prompted for the SLP scope, press enter to accept the default unless you have manually configured Volution Manager to use a different scope. For more information on SLP scopes, see Section 2.7.
If prompted for the hostname or IP address of an SLP DA, enter the name or IP address of the VM Server and press enter. For more information on the SLP DA, see Section 1.1.9 in the subsection, Section 1.1.9.1.3.
The VM Client daemon is installed and started. To verify that the daemon is running enter,
ps -ef |grep volutiond
A list of running processes appears.
Before you install the VM Client on computers using the SCO OpenServer platform, you must enable SNMP. SNMP provides diagnostic services for the client. If you do not complete these steps, your SCO OpenServer Clients won't be able to use the command line client diagnostic service, voldiag.
Open a terminal window to complete the following steps:
As the root user, enter the following command:
mkdev snmp
The following message appears:
"Do you wish to update or remove the SNMP Agent Configuration files? Please enter: u - to update or r - to remove or enter q to quite [q]:"
Enter u to update.
The following message appears:
"Do you wish to continue installing the SNMP Agent? (y/n)"
Enter y to continue.
The message similar to the following appears:
"Do you wish to continue installing the SNMP Agent? (y/n)"
Enter y to continue.
The MIB System Setup appears with the following prompt:
"Enter Syscontact name:"
Enter the name of the person responsible for the system and press Enter.
A prompt requesting the SysLocation follows.
Enter the physical location of the system and press Enter.
Information on the SNMP Community Setup follows.
Enter q to quit the session.
The SNMP Trap Systems Setup appears.
Enter q to quit the SNMP Trap Systems Setup.
The SMUX Peer Setup appears.
Enter q to quit the SMUX Peer Setup.
The SNMP setup is complete.
Open the /etc/snmpd.comm file.
Make sure that the following line appears and is uncommented.
public 0.0.0.0 read
If a previous version of the VM Client is installed, remove it using the following steps as the root user:
Run custom or select Software Management from the desktop.
Select product, Caldera Volution Client for SCO OpenServer.
Select Software, then click Remove Software.
Click Remove, then click OK.
To install a managed client on the SCO OpenServer platform using the manual method, complete the following:
Insert and mount the Volution Manager CD.
Run custom at the command line or select Software Management from the desktop.
Select Software and then click Install New.
Select From yourcomputername, then click Continue.
From the Media Device drop-down list, select Media Images then click Continue.
In the Image Directory field, enter the path to the directory /mnt/cdrom/client/OSR5 where /mnt/cdrom is the path to the CD and click Enter.
Install OpenSLP, OpenSSL, and Volution Manager Client.
Click Install.
Note: This procedure is only required if you are concerned that your managed clients could contact the wrong Volution Manager Server (VM Server). It must be done before you start the VM Client.
The Volution Manager Key Tool is a command line key and certificate configuration tool that allows you to view, import, and configure keys and certificates installed on your system. It provides an extra measure of security. If you have concerns about your managed VM Clients communicating with an unauthorized VM Server, or if you have more than one VM Server in your network, run the Volution Manager Key Tool on each VM Client. The advantage in using the Volution Manager Key Tool is that you can actually check the fingerprint on the CA certificate to make sure it matches the one installed on the VM Server.
Complete the following as the root user.
Make sure you are logged in as root.
Change to the opt/volution/bin directory.
Enter the following:
./volutionkeytool cacert import
Use the following format for other commands:
./volutionkeytool command
Where command is one of the following:
help (-help or --help)- Displays usage message.
cacert create- Creates a new Volution Manager CA certificate.
cacert import- Imports a Volution Authority certificate.
cacert list- Lists Volution CA certificates on this host.
cert list- Lists Volution certificate that have been issued for this host.
cert issue-Issues (or re-issues) new certificates for this host.
cert request- Issues a new certificate using a certificate request.
crl add- Adds a certificate to the certificate revocation list.
crl list- Lists the certificates on the certificate revocation list.
The issuer, subject, and fingerprint of the CA certificate appears.
To cross check this fingerprint with the fingerprint on the CA certificate installed on the VM Server, you must know what the fingerprint on the CA certificate installed on the VM Server is. To display the certificate on the VM Server, enter:
/opt/volution/bin/volutionkeytool cacert list
To start the SCO OpenServer client, enter the following command:
/etc/init.d/slpd start
/etc/init.d/volutiond start
There are two methods of installing VM Clients running on UnixWare and Open UNIX 8. Use the install script./install.sh to install VM Clients on Linux and UNIX platforms. Use the -c switch to view the VM Client certificate authority (CA) certificate. The purpose of this is to ensure that it matches the CA certificate on the VM Server. This provides an extra measure of security. To view the CA certificate on the VM Server, enter the following on the VM Server:
/opt/volution/bin/volutionkeytool cacert list
You can also install VM Clients using the manual installation method. With the manual method, you can use all of the options available with the Volution Manager Key Tool.The Key Tool is a command line key and certificate configuration tool that allows you to view, import, and configure keys and certificates installed on your system. Like the installation script, you can manually check the fingerprint of the VM Client CA certificate, but you can also use other features of the tool.
You can install and start VM Clients on UnixWare and Open UNIX 8 using one script, install.sh. This script installs all of the required packages and then automatically starts the VM Client daemon, volutiond.
Use the -c switch (./install.sh -c) to view the VM Client certificate authority (CA) certificate. The purpose of this is to ensure that it matches the CA certificate on the VM Server. You would only need this extra measure of security if you were concerned that another unauthorized VM Server might be installed in your network. To view the CA certificate on the VM Server, enter the following on the VM Server:
/opt/volution/bin/volutionkeytool cacert list
To run the install.sh script,
Insert and mount the Volution Manager CD.
Change to the client directory on the Volution Manager CD.
Enter
./install.sh
Note: Use the -c switch to view the CA certificate at the end of the installation and confirm that the VM Client is contacting the correct VM Server. Use -h to list other available switches.
If prompted for the SLP scope, press enter to accept the default unless you have manually configured Volution Manager to use a different scope. For more information on SLP scopes, see Section 2.7.
If prompted for the hostname or IP address of an SLP DA, enter the name or IP address of the VM Server and press enter. For more information on the SLP DA, see Section 1.1.9 in the subsection, Section 1.1.9.1.3.
The VM Client daemon is installed and started. To verify that the daemon is running enter
ps -ef |grep volutiond
A list of running processes appears.
To install VM Clients on UnixWare and Open UNIX 8, complete the following.
If a previous version of the VM Client is installed, remove it by running the following command as the root user:
pkgrm Volution
To install the VM Client on UnixWare and Open UNIX 8, complete the following:
Insert and mount the Volution Manager CD.
Enter the following commands:
pkgadd -d /mnt/cdrom/client/UW/openssl-packagenumber.pkg
pkgadd -d /mnt/cdrom/client/UW/openslp-packagenumber.pkg
pkgadd -d /mnt/cdrom/client/UW/volution -1.1.0.packagenumber.pkg
Note: This procedure is only required if you are concerned that your managed clients could contact the wrong Volution Manager Server (VM Server). It must be done before you start the VM Client.
The Volution Manager Key Tool is a command line key and certificate configuration tool that allows you to view, import, and configure keys and certificates installed on your system. It provides an extra measure of security. If you have concerns about your managed VM Clients communicating with an unauthorized VM Server or if you have more than one VM Server in your network, run the Volution Manager Key Tool on each VM Client. The advantage in using the Volution Manager Key Tool is that you can actually check the fingerprint on the CA certificate to make sure it matches the one installed on the VM Server.
Complete the following as the root user.
Make sure you are logged in as root.
Change to the opt/volution/bin directory.
Enter the following:
./volutionkeytool cacert import
Use the following format for other commands:
./volutionkeytool command
Where command is one of the following:
help (-help or --help)- Displays usage message.
cacert create- Creates a new Volution Manager CA certificate.
cacert import- Imports a Volution Authority certificate.
cacert list- Lists Volution CA certificates on this host.
cert list- Lists Volution certificates that have been issued for this host.
cert issue-Issues (or re-issues) new certificates for this host.
cert request- Issues a new certificate using a certificate request.
crl add- Adds a certificate to the certificate revocation list.
crl list- Lists the certificates on the certificate revocation list.
The issuer, subject, and fingerprint of the CA certificate appears.
To cross check this fingerprint with the fingerprint on the CA certificate installed on the VM Server you must know what the fingerprint on the CA certificate installed on the VM Server is. To display the certificate on the VM Server, enter:
/opt/volution/bin/volutionkeytool cacert list
To start the UnixWare and Open UNIX 8 client, enter the following command:
/etc/init.d/slpd start
/etc/init.d/volutiond start
You can check if the client daemon is running by entering the following commands in a terminal window.
ps -ef |grep volutiond
If your clients aren't contacting the Volution Manager computer creation daemon named volutonccd to populate your directory, check the following:
If the VM Server has been reinstalled, the VM Client might not be using the correct certificate. Use the following commands to remove the certificate and restart the VM Client:
rm -rf /etc/opt/volution/cacert
rm /etc/opt/volutiond.conf
/etc/rc.d/init.d/volutiond restart
If your VM Client is running but is not contacting the VM Server, run voldiag. For information on running voldiag, refer to Section 3.4.1.
If a VM Client is unable to complete a hardware inventory the Practical Extraction and Reporting Language (Perl) might be in an unexpected location.
Volution Manager uses the Perl for obtaining hardware inventory data (a task performed through the VM Management Console). When an Linux VM Client is installed it looks for Perl first in /usr/bin. If it is not found there, it looks in /usr/local/bin.
If you want to use Perl in a different location, edit the file:.
/opt/volution/bin/hwinfo2xml for Linux VM Clients
/opt/volution/bin/os5hwinfo2xml for SCO OpenServer VM Clients
/opt/volution/bin/uw7hwinfo2xml for UnixWare and Open UNIX 8 VM Clients
If health monitoring isn't working properly, Perl might be in an unexpected location. If you want to use Perl in a different location, edit the file:
/opt/volution/bin/os5tsmod.pl for SCO OpenServer VM Clients
/opt/volution/bin/uw7tsmod.pl for UnixWare and Open UNIX 8 VM Clients
Use voldiag to provide diagnostic information on your managed clients. The voldiag tool provides information about the following:
System information, such as platform and architecture.
Network analysis, including basic network functioning and name service resolution.
SLP analysis, including availability of services and system scope.
Information from the daemon's configuration file and current daemon functions.
The voldiag tool is installed as part of the VM Client installation.
To run voldiag:
Log onto the system you want to analyze as the superuser (root).
Enter /opt/volution/bin/voldiag -options at the command line.
You must log on as root because voldiag displays passwords that allow the client to access LDAP and the software repository (the organizational unit in your LDAP directory that includes objects that represent software packages you plan to distribute). In addition, many of the actions you might take as a result of voldiag output -- such as re-starting a system or computer -- require this permissions level.
When run with no options, voldiag performs a standard client analysis. To perform a server or console analysis, use the -all option. Other options allow you to view a subset of voldiag information: use the -h option for a list of options.
The VM Client Analysis section of the voldiag output contains information read from the volutiond configuration file (/etc/opt/volution/volutiond.conf) as well as real-time status of the daemon and the services it detects.
If volutiond.conf cannot be read, because it has been corrupted or is not present, VM Client Configuration Information fails and the daemon does not run correctly. In this case, you need to re-authenticate the VM Client to the server by removing the file if present, then stopping and starting volutiond (/etc /rc.d/init.d/volutiond stop, /etc/rc.d/init.d/volutiond start). The VM Server's computer creation daemon, volutionccd, then creates the configuration file automatically.
If the daemon is not running (if "Is Volution Client Running" is "NO"), you need to re-start the daemon from the client, by entering /etc/rc.d/init.d /volutiond start.
If the daemon is running, voldiag checks to see if it can contact the following services: CCD, DENS, LDAP, and SLP. This is primarily a cross-check at this point, as these systems were located and verified as functional earlier in the diagnostic process.
Based on the ability to access the required services, voldiag reports the system's health. This is simply a quick view of the sum of all diagnostic information.
Note: For more extensive troubleshooting information, see the Volution Manager Administration Guide.