4.2 Installing and Configuring NSS

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

4.2.1 Selecting the NSS Pattern During 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 install process, see the Installation Guide.

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

    The following additional services are automatically selected:

    • OES 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 OES Distributed File Services for moving or splitting NSS volumes.

    • NetIQ eDirectory

      eDirectory supports authentication of users who connect to NSS volumes.

    • OES Linux User Management

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

      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.

    • OES Remote Manager (NRM)

      OES Remote Manager (NRM) is a browser-based management utility for monitoring server health, changing the configuration of your server, or performing diagnostic and debugging tasks.

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

  3. Optionally select Unified Management Console (UMC) to be installed on the server. For more information, see Configuring UMC During OES Installation in Unified Management Console Administration Guide.

  4. Optionally select NetIQ 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 10.2, iManager and Storage-Related Plug-Ins.

  5. 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.

  6. Optionally select OES 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 23.4: OES Cluster Services for Linux Administration Guide.

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

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

  8. Novell Identity Translator (NIT) has been introduced in OES. If you would like to change the default NIT range, on the OpenText Open Enterprise Server Configuration screen, click OES Storage Services (NSS) and modify the range. For more information on NIT, see About Novell Identity Translator (NIT) in the Installation Guide.

  9. Continue with the installation.

  10. After the install, use the Software Updater (or other update methods) to install any NSS patches from the OES patch channel.

4.2.2 Installing NSS on an Existing OES Server

If you did not install OES Storage Services during the OES 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 OES Storage Services and any other OES components that you want to install.

    Follow the instruction for selecting NSS and its dependencies described in Section 4.2.1, Selecting the NSS Pattern During 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 patch channel.

4.2.3 Enabling or Disabling NSS

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 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:

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

  2. Click System > Services Manager.

  3. Select novell-nss, then click Enable/Disable to enable or disable the service.

  4. Click Ok to save and apply your changes, then exit the YaST service manager.