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

42 OES 2 SP2: Planning and Implementation Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
Replace this variable with the UID reported for the novlxsrvd user on this server as listed
when you ran the commands in
Step 1 on page 40 .
For example, if the UID for novlxsrvd_uid is 102, change the line to read
novlxsrvd_uid=102
Š <novlxtier_gid>: This is the GID that the system assigned to the local novlxtier group. It
might or might not be the same on each server, depending on whether the
nssid.sh
script
ran successfully.
Replace this variable with the GID reported for the novlxtier group on this server as listed
when you ran the commands in
Step 1 on page 40 .
For example, if the GID for novlxtier_gid is 101, change the line to read
novlxtier_gid=101
6 Make the script executable and then run it on the server.
IMPORTANT: Changes to the XTier files are not reported on the terminal.
Error messages are reported, but you can safely ignore them. The script the entire file system,
and some files are locked because the system is running.
7 Repeat from Step 1 for each of the other servers in the same context.
3.9.10 iFolder 3.8 Considerations
For best results, be sure you read and carefully follow the instructions in the Novell iFolder 3.8
Administration Guide , starting with “ Deploying iFolder Server .” This is especially critical if you
plan to use NSS for your iFolder 3.8 data volume.
3.9.11 Incompatible TLS Configurations Give No Warning
When you install a new eDirectory tree, the eDirectory Configuration - New or Existing Tree screen
has the
Require TLS for Simple Binds with Password option selected by default. If you keep this
configuration setting, the eDirectory LDAP server requires that all communications come through
the secure LDAP port that you specified on the eDirectory Configuration - Local Server
Configuration screen. By default, this is port 636.
Unfortunately, the OES install doesn’t display a warning if you subsequently configure OES
services to use non-TLS (non-secure) LDAP communications (port 389). The installation proceeds
normally but the service configuration fails.
For example, if you accept the TLS default, then configure Novell DHCP to use non-secure
communications (by deselecting the
Use secure channel for configuration option), the OES install
doesn't warn that you have created an incompatible configuration.
After eDirectory and the iManager plug-ins install successfully, the Novell DHCP configuration
fails. You must then use iManager to change either the LDAP server configuration or the Novell
DHCP configuration to support your preferred communication protocol.
Simply enabling non-TLS LDAP communications doesn’t disable TLS. It merely adds support for
non-secure communications with the LDAP server.