4.1 Linux: Setting Up a Basic Teaming Site

You should already have reviewed Section 3.0, Planning a Basic Teaming Installation and filled out the Basic Teaming Installation Summary Sheet. The following sections step you through the process of installing and starting Novell Teaming on Linux.

4.1.1 Performing Pre-Installation Tasks on Linux

  1. Make sure that the Linux server where you plan to install Teaming meets the system requirements listed in Section 2.1, Teaming Server Requirements.

  2. In a terminal window, become root by entering su - and the root password.

  3. Set the Linux open file limit to meet the needs of the Teaming software:

    1. Open the /etc/security/limits.conf file in an ASCII text editor.

    2. Add the following lines to the bottom of the list, following the format of the example lines:

      *    hard    nofile    65535
      *    soft    nofile    4096
      
    3. Save the file, then exit the text editor.

  4. Perform the following conditional tasks if needed:

Stopping and Disabling an Existing Web Server

For example, to stop the Apache Web server and its associated instance of Tomcat:

  1. Enter the following commands to stop Apache and Tomcat:

    /etc/init.d/tomcat5 stop
    /etc/init.d/apache2 stop
    
  2. Enter the following commands to make sure that Apache and Tomcat do not start again when you reboot the server:

    chkconfig --del apache2
    chkconfig --del tomcat5
    

Creating a Teaming User and Group

If the user and group that you want to use for Teaming, as described in Section 3.8.2, Linux User ID for Teaming do not exist yet, create them. It is easier if you create the group first.

  1. Create the Linux group that you want to own the Teaming software and data store directories:

    1. In YaST, click Security and Users > User Management to display the User and Group Administration page.

    2. Click Groups, then click Add.

    3. Specify the group name, then click Accept or OK.

      The group does not need a password.

  2. Create the Linux user that you want Teaming to run as:

    1. Click Users, then click Add.

    2. On the User Data tab, specify the user’s full name, username, and password, then select Disable User Login.

      Like any Linux system user, the Teaming Linux user does not need to manually log in. The Teaming Linux user does not need a password, either, but YaST requires you to provide one.

    3. Click the Details tab.

    4. In the Login Shell drop-down list, select /bin/false, because this user does not need to manually log in.

    5. In the Default Group drop-down list, select the Linux group that you created in Step 1.

    6. In the Groups list, select the Linux group that you created in Step 1.

    7. Click Accept or OK.

  3. Exit YaST.

4.1.2 Running the Linux Teaming Installation Program

When you run the Novell Teaming Installation program for the first time, you typically want to use the GUI interface. However, if you are installing Teaming on a server where the X Window System* is not available, a text-based Installation program is also available. After you are familiar with the Teaming installation process, you can use a silent installation to automate the process.

Using the GUI Installation Program

  1. In a terminal window, enter su - to become the root user, then enter the root password.

    You need root permissions in order to install the Teaming software, but you should not run the Teaming software as root.

  2. Change to the directory where you downloaded and extracted the Teaming software.

  3. Make sure that you have a license-key.xml file in the same directory with the Teaming Installation program.

    more license-key.xml

    The Teaming Installation program does not start without a license file in the same directory, and the license file has a different name when you download it.

    For more information about licensing, see Section 6.0, Updating Your Teaming License.

  4. Enter the following command to start the Teaming Installation program:

    ./installer-teaming.linux

  5. Accept the License Agreement, then click Next.

    Linux Installation program Welcome page
  6. Click Next to accept the default of New installation.

    Installation Type page
  7. Click Next to accept the default of Basic.

  8. Use the information that you have gathered on the Basic Teaming Installation Summary Sheet to provide the information that the Teaming Installation program prompts you for:

    The Installation program stores the information it gathers in the installer.xml file in the same directory where you started the Installation program.

  9. After you have provided all the requested information, click Install to begin the Teaming installation.

  10. When the installation is completed, click Finish to exit the Teaming Installation program.

    Information about the installation process is written to the installer.log file in the same directory where you ran the Installation program. If a problem arises during the installation, the installer.log file provides information that can help you resolve the problem.

  11. Continue with Section 4.1.3, Configuring Teaming to Start Automatically on Reboot.

Using the Text-Based Installation Program

If you try to start the GUI Teaming Installation program in an environment where the X Windows System is not running, the text-based Teaming Installation program starts instead.

Text-based Teaming Installation program

If you want to use the text-based Installation program in an environment where it is starting with a GUI by default, use the following command in the directory where the Installation program is located:

./installer-teaming.linux --text

IMPORTANT:The text-based Teaming Installation program must be run in the same directory where the Teaming license file is located. If the license file is not in the same directory, the text-based Installation program cannot find it.

The text-based Installation program gathers the same configuration information as the GUI Installation program does. This information is stored in the installer.xml file in the directory where you run the Installation program.

The Installation program does not write the information it gathers into the installer.xml file until you exit the Installation program, and you cannot back up when using the text-based Installation program. Therefore, when you use the text-based Installation program, you should plan you installation carefully in advance, using the Basic Teaming Installation Summary Sheet or the Advanced Teaming Installation Summary Sheet. If you make a mistake during the installation, continue to the end of the installation process and exit the Installation program normally, so that all information is saved. Then run the text-based Installation program again. Your previous information is supplied as defaults and you can change the information as needed.

Performing a Silent Installation

If your Novell Teaming system expands beyond one server, you might need to repeatedly install the same Teaming components. A silent installation makes this an easy process. Edit an existing installer.xml file so that it has the hostname of the server where you want to perform the silent installation and copy it to that server. In the directory where the Installation program is located. use the appropriate command to run the Teaming installation program, depending on the action that you want the silent installation to perform:

./installer-teaming.linux --silent install
./installer-teaming.linux --silent update
./installer-teaming.linux --silent reconfigure

The Installation program obtains all the information it needs from the installer.xml file and completes the installation without user interaction.

4.1.3 Configuring Teaming to Start Automatically on Reboot

You can configure Novell Teaming to start automatically each time you reboot the Linux server.

  1. As the Linux root user, enter the following command:

    chkconfig --add teaming

  2. To verify that automatic startup is turned on, enter the following command:

    chkconfig teaming

4.1.4 Setting Up Port Forwarding

In order to make Novell Teaming available on the default HTTP/HTTPS ports of 80 and 443, you must set up port forwarding in order to forward the browser default ports (80 and 443) to the Teaming server ports (8080 and 8443). In addition, you must set up port forwarding if you want to forward the default SMTP mail host port (25) to the default Teaming internal mail host port (2525).

You can set up port forwarding in one of two ways, depending on whether or not you are using the Teaming server as a firewall.

Using the SuSEfirewall2 File

To enable port forwarding on a SUSE Linux server that leverages SuSEfirewall2:

  1. As the Linux root user, open the following file:

    /etc/sysconfig/SuSEfirewall2

  2. Find the following line:

    FW_REDIRECT=""

  3. Between the quotation marks, copy and insert the following string:

    0/0,ip_address,tcp,80,8080 0/0,ip_address,tcp,443,8443 
                                                      0/0,ip_address,tcp,25,2525
    
  4. Replace ip_address with the IP address of the Teaming server.

  5. Save the SuSEfirewall2 file, then exit the text editor.

  6. Use the following command to restart the firewall:

    /sbin/SuSEfirewall2 start

  7. Use the following command to verify that the default browser ports (80 and 443) have been forwarded to the Teaming server ports (8080 and 8443) and that the default SMTP mail host port (25) has been forwarded to the Teaming internal mail host:

    iptables-save | grep REDIRECT

Now, users do not need to include a port number in the Teaming site URL.

Using iptables Commands

To leverage iptables commands to enable port forwarding on any type of Linux server:

  1. As the Linux root user, change to the /etc/init.d directory.

  2. In a text editor, create a new file for a set of iptables commands, for example:

    gedit teaming-iptables
    
  3. Copy and paste the following lines into the teaming-iptables file:

    iptables -t nat -A OUTPUT -d localhost -p tcp --dport 80 
                                           -j REDIRECT --to-ports 8080
    
    iptables -t nat -A OUTPUT -d hostname -p tcp --dport 80 
                                          -j REDIRECT --to-ports 8080
    
    iptables -t nat -A PREROUTING -d hostname -p tcp --dport 80 
                                              -j REDIRECT --to-ports 8080
    
    iptables -t nat -A OUTPUT -d localhost -p tcp --dport 443 
                                           -j REDIRECT --to-ports 8443
    
    iptables -t nat -A OUTPUT -d hostname -p tcp --dport 443 
                                          -j REDIRECT --to-ports 8443
    
    iptables -t nat -A PREROUTING -d hostname -p tcp --dport 443 
                                              -j REDIRECT --to-ports 8443
    
    iptables -t nat -A OUTPUT -d localhost -p tcp --dport 25 
                                           -j REDIRECT --to-ports 2525
    
    iptables -t nat -A OUTPUT -d hostname -p tcp --dport 25 
                                          -j REDIRECT --to-ports 2525
    
    iptables -t nat -A PREROUTING -d hostname -p tcp --dport 25 
                                              -j REDIRECT --to-ports 2525
    

    In this example, the lines are wrapped for readability. When you paste them into the text editor, if the lines are still wrapped, remove the hard returns from the middle of the commands, so that you have six iptables commands, each on its own line.

  4. Replace hostname with the hostname of the Teaming server.

  5. Save the teaming-iptables file, then exit the text editor.

  6. Use the following command to make the file executable:

    chmod +x teaming-iptables

  7. Restart the firewall to put the iptables commands into effect:

    1. Click Security and Users > Firewall.

    2. Click Stop Firewall Now, click Start Firewall Now, then click Next > Accept.

    3. Exit YaST, then return to the terminal window where you are logged in as root.

  8. Use the following command to verify that the default browser ports (80 and 443) have been forwarded to the Teaming server ports (8080 and 8443) and that the default SMTP mail host port (25) has been forwarded to the Teaming internal mail host:

    iptables-save | grep REDIRECT

Now, users do not need to include a port number in the Teaming site URL.

4.1.5 Starting Teaming on Linux

The Novell Teaming Installation program created a teaming startup script in the /etc/init.d directory.

  1. In a terminal window, enter the following command:

    /etc/init.d/teaming start

    IMPORTANT:Do not run Teaming as the Linux root user.

    You should see output similar to the following example:

    Using CATALINA_BASE:    /opt/teaming/apache-tomcat-6.0.18
    Using CATALINA_HOME:    /opt/teaming/apache-tomcat-6.0.18
    Using CATALINA_TEMPDIR: /opt/teaming/apache-tomcat-6.0.1/temp
    Using JRE_HOME:         /use/java/jdk1.5.0_17/jre
    
  2. To make sure that Teaming is ready for work:

    1. Change to the following directory:

      /opt/novell/teaming/apache-tomcat-version/logs

      where version is the version number of Tomcat that was installed along with Teaming (for example, 6.0.18)

    2. Enter the following command to display the end of the Tomcat log:

      tail --f catalina.out

      At the end of the log file listing, you should see:

      INFO: Server startup in nnnn ms 
      
  3. Press Ctrl+C when you are finished viewing the end of the catalina.out file.

4.1.6 Checking the Status of the Teaming Server

You can see if Novell Teaming is running by checking for its process ID (PID).

  1. In a terminal window, enter the following command:

    ps -eaf | grep teaming

    You should see the Teaming PID number, along with a listing of configuration settings.

4.1.7 Restarting Teaming

You need to restart Novell Teaming whenever you use the Teaming Installation program to make configuration changes, as described in Section 10.0, Performing an Advanced Teaming Installation.

  1. In a terminal window, enter the following command:

    /etc/init.d/teaming restart

    You should see the same output as when you originally started Teaming.

4.1.8 Stopping Teaming

  1. In a terminal window, enter the following command:

    /etc/init.d/teaming stop

    You should see the same output as when you started Teaming.

  2. To verify that Teaming has stopped, check for its PID number:

    ps -eaf | grep teaming

    The Teaming PID number, along with a listing of configuration settings, should no longer be displayed.

4.1.9 Uninstalling Teaming

If you move the Novell Teaming site to a different server, you can delete the Teaming files from the original server to reclaim disk space. The default Teaming file locations are:

Teaming Software

/opt/novell/teaming

Teaming File Repository

/var/opt/novell/teaming

MySQL Database

/var/lib/mysql

For a complete list of your Teaming files, check the installer.xml file in the directory where you originally ran the Teaming Installation program.