Quantum 3.5.1 manual Configuring Ldap, Using Ldap, Changes to Nobody mapping

Configuring LDAP

* transfer buffer size)

For example, consider a Linux Distributed LAN Server that has two NICs used for Distributed LAN traffic, serves four file systems, and uses the default eight server buffers and 256K per buffer. (See the dpserver and sndpscfg man pages for information about viewing and modifying Distributed LAN buffer settings on Linux.) For this case:

Required memory = 1GB + (4 * 2 * 8 * 256K) = 1040MB

Note: This example results in a memory requirement of less than 2GB. However, Quantum recommends that all Distributed LAN Servers contain a minimum of 2GB of RAM.

Configuring LDAP

	This sections describes how to configure the StorNext LDAP functionality
	and describes related features in the Windows configuration utilities.
	StorNext 2.7 introduced support for Light Directory Access Protocol, or
Using LDAP
	LDAP (RFC 2307). This feature allows customers to use Active Directory/
	LDAP for mapping Windows User IDs (SIDs) to UNIX User ID/Group
	IDs.
	Changes to “Nobody” mapping
	If a Windows user cannot be mapped to a UNIX ID, the user is mapped to
	Nobody. StorNext allows administrators to change the value of Nobody
	by using the file system configuration parameters:
	UnixNobodyUidOnWindows 60001
	UnixNobodyGidOnWindows 60001
	These parameters are located in the file system configuration file on the
	server and can be manually modified by the Windows or StorNext Web
	GUI.

StorNext User’s Guide 332