3.3 Installing and Configuring NSS on Linux

This section describes only those steps in the install that are directly related to installing Novell Storage Services and its dependencies. For information about installing OES 2 services on Linux, see the OES 2 SP2: Installation Guide.

3.3.1 Installing Linux with EVMS as the Volume Manager of the System Device

If you are installing OES 2 Linux on a system with a single device where you also plan to create NSS volumes, that device must be managed by the Enterprise Volume Management System (EVMS) volume manager instead of the default Linux Volume Manager 2 (LVM2) volume manager. The volume manager for the system device is configured in the Partitioning section of the Installation Settings page for the YaST install. For more information and instructions, see Installing with EVMS as the Volume Manager of the System Device in the OES 2 SP2: Installation Guide.

3.3.2 Selecting the NSS Pattern During the OES 2 Linux Install

  1. In the YaST install, on the Installations Settings page, click Software to go to the Software Selections and System Tasks page.

    For information about the entire OES 2 Linux install process, see the OES 2 SP2: Installation Guide.

  2. From the OES Services options, select Novell Storage Services. Selecting NSS as part of a 64-bit installation automatically installs NSS 64-bit support.

    The following additional OES 2 services are automatically selected:

    • Novell Backup / Storage Management Services™

      SMS makes it possible to back up trustee and other extended attributes for data on NSS volumes. It is also used by Novell Distributed File Services for moving or splitting NSS volumes.

    • Novell eDirectory

      eDirectory supports authentication of users who connect to NSS volumes.

    • Novell Linux User Management

      LUM allows eDirectory users to be enabled for Linux services, such as access via Samba, FTP, and so on. The administrator user for the server is automatically Linux-enabled with LUM. Non-NCP users must be Linux-enabled with LUM in order to access data on NSS volumes with Linux services, utilities, or protocols. The services must also be LUM enabled.

      IMPORTANT:LUM is required even if the administrator user is the only LUM user on the server.

    • NCP Server / Dynamic Storage Technology

      NCP Server provides support to NSS for access control, shadow volumes, commands, and file access. It is required even if you are not using NCP clients to connect to the NSS volume.

    • Novell Remote Manager (NRM)

      NRM provides the NCP Server management plug-in that allows you to create shadow volumes using NSS volumes on Linux. You can also use it to manage NCP connections to the NSS volumes.

    Example of the Software Selection and System Tasks Page for NSS Selections
  3. Optionally select Novell iManager to be installed on the server.

    You must install iManager somewhere in the same tree as the server. If you install iManager and NSS on the same server, the storage-related plug-ins are automatically installed.

    If you install iManager on a different server, make sure you install the storage-related plug-ins that you need to manage NSS file system and services. For information about installing storage-related plug-ins on an existing server, see Section 9.1, Novell iManager and Storage-Related Plug-Ins.

  4. Optionally select non-NCP file access services to be installed on the server.

    NSS requires NCP Server to be installed and running on the server even if you select one or more of these alternate methods for user access.

    • Novell AFP: Allows Macintosh users to connect to NSS volumes with the AFP (Apple Filing Protocol). Novell AFP is available beginning in OES 2 SP1 Linux. For information about configuring and managing AFP, see the OES 2 SP2: Novell AFP For Linux Administration Guide.

    • Novell CIFS: Allows CIFS/Samba users to connect to NSS volumes with the CIFS/Samba protocol. Novell CIFS is available beginning in OES 2 SP1 Linux. For information about configuring and managing Novell CIFS, see the OES 2 SP2: Novell CIFS for Linux Administration Guide.

    • Novell Samba: Allows CIFS/Samba users to connect to NSS volumes with the CIFS/Samba protocol. This service is based on Linux Samba and requires users to be Linux-enabled with Linux User Management. For information about configuring Samba during the install and configuring users for CIFS/Samba access after the install, see the OES2 SP2: Samba Administration Guide.

      IMPORTANT:Novell Samba and Novell CIFS are different file access services that allow CIFS/Samba users to connect to NSS volumes. You can select only one of the two on a given server because of port contention issues.

  5. Optionally select Novell Cluster Services to be installed on the server.

    Install NCS if you plan to share NSS pools in a cluster. For information about installing NCS and configuring shared devices and pools using NCS, see the OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide.

  6. Click Accept to return to the Installation Settings page.

    Licensing dialog boxes might open where you are prompted to accept proprietary modules being installed.

  7. Continue with the OES 2 Linux installation.

  8. After the install, use the Software Updater (or other update methods) to install any NSS patches from the OES 2 Linux patch channel and any EVMS patches from the SUSE® Linux Enterprise Server 10 SP2 patch channel.

3.3.3 Installing NSS on an Existing OES 2 Linux Server

If you did not install Novell Storage Services during the OES 2 Linux installation, you can install it later by using YaST > Open Enterprise Server > OES Install and Configuration.

  1. Log in to the server as the root user.

  2. In YaST, select Open Enterprise Server > OES Install and Configuration.

  3. In the Selection window under OES Services, click Novell Storage Services and any other OES components that you want to install.

    Follow the instruction for selecting NSS and its dependencies described in Section 3.3.2, Selecting the NSS Pattern During the OES 2 Linux Install.

  4. Click Accept to begin the install, then click Continue to accept changed packages.

  5. Follow the on-screen instructions to complete the install.

  6. After the install, enter rcnovell-smdrd restart at the command prompt, or reboot the server before performing any backups, restores, or server consolidations on the NSS file system.

  7. Use the Software Updater (or other update methods) to install patches from the OES 2 Linux patch channel and the SUSE Linux Enterprise Server 10 SP2 patch channel (such as for EVMS).

3.3.4 Enabling or Disabling NSS on Linux

When you install NSS during the initial install, NSS and its dependencies are automatically enabled in the Linux System Services (Runlevel) with Runlevels 2, 3, and 5. NSS is not automatically enabled if you post-install NSS on the server.

Although you can uninstall OES 2 Linux service RPMs through YaST, we do not recommend it because so many modules have interdependencies. Uninstalling services can leave the server in an undesirable state. If you no longer plan to use a server, we recommend disabling the service.

WARNING:NSS must be enabled to use any components or tools for the NSS file system.

To enable or disable NSS on Linux:

  1. Log in to the server as the root user, then start YaST.

  2. Click System > System Services (Runlevel), then click Expert Mode.

  3. Select NSS, then click Set/Reset.

  4. Select one of the following options from the Set/Reset menu:

    • Disable the service

    • Enable the service

  5. Click Finish to save and apply your changes, then exit the YaST Runlevel tool.