Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION, Руководство по внедрению, Страница: 40 / 288

40 OES 2 SP2: Planning and Implementation Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
For NetStorage to run, these XTier users and group must be able to read data on all volume types
that exist on the OES server.
As long as the server only has Linux traditional file systems, such as Ext3 and Reiser, NetStorage
runs without difficulties.
However, if the server has NSS volumes, an additional requirement is introduced. NSS data can only
be accessed by eDirectory users. Consequently, the local XTier users can’t access NSS data, and
NetStorage can’t run properly.
eDirectory Solves the Basic Problem
Therefore, when NSS volumes are created on the server, the XTier users are moved to eDirectory
and enabled for Linux User Management (LUM). See
Section 15.2, “Linux User Management:
Access to Linux for eDirectory Users,” on page 149 .
After the move to eDirectory, they can function as both eDirectory and POSIX users, and they no
longer exist on the local system.
ID Mismatches on OES 1
Problems with OES 1 occurred when additional OES NetStorage servers with NSS volumes were
installed in the same eDirectory container. Because the UIDs and GID were assigned by the Linux
system, unless the installation process was exactly the same for each OES 1 Linux server, the UIDs
and GID didn’t match server-to-server.
When the local XTier UIDs and GID on subsequently installed servers didn’t match the XTier UIDs
and GID in eDirectory, NetStorage couldn’t access the NSS volumes on the server.
The OES 1 Solution: The nssid.sh Script
To solve this problem, the OES 1 installation program looked for XTier ID conflicts, and if the IDs
on a newly installed server didn’t match the IDs in eDirectory, the program generated a script file
named
nssid.sh
. The documentation instructed installers to always check for an
nssid.sh
file on
a newly installed server, and if the file was found, to run it. The
nssid.sh
script synchronized all of
the XTier IDs with those that had already been stored in eDirectory.
This solution remained viable through the first release of OES 2.
OES 2 SP1 or Later Requires a New Approach
Unfortunately, system-level changes in SUSE Linux Enterprise Server 10 SP2 invalidated the
nssid.sh
script solution for OES 2 SP1. Synchronizing the XTier IDs with an OES 1 installation
can now cause instability in other non-OES components. Therefore, starting with OES 2 SP1, you
should standardize all XTier IDs on existing servers before installing a new OES 2 server with
XTier-dependent services.
The OES 2 Solution: Standardizing the UIDs on all OES servers
If your eDirectory tree has ever contained an OES 1 Linux server with NSS and LUM installed, do
the following on each server (including OES 2) that has NSS and LUM installed:
1
Log in as
root
and open a terminal prompt. Then enter the following commands:
id novlxregd