Setting The Cifs Settings; Commit Nfs Synchronously - Quantum DXi4500 Manual

Setting the CIFS
Settings
Commit NFS
Synchronously
NAS Configuration CLI Commands
• --ldapsigning: queries the LDAP client signing setting ("client ldap sasl
wrapping")
• --maxprocesses: queries the limit on the number of smbd processes ("max
smbd processes")
• clientntlmv2auth: queries the setting "client NTLMv2 auth".
• --all: queries all CIFS settings, both global settings and per-share settings.
syscli --set smbsetting { --oplocks disabled|enabled } | { --dbglevel <n> } |
{ --ldapsigning disabled|enabled } | { --maxprocesses
<max_smbd_processes> } | { --clientntlmv2auth yes|no }
Specifically,
• syscli --oplocks disabled|enabled
This CLI command changes the kernel oplocks setting in CIFS. In a bad
network environment the kernel oplocks setting should be disabled.
• syscli –dblevel <n>
This CLI command changes the debug level to n where n is a nonnegative
number. The higher the value, the more verbose the log files are. A value of
zero gives minimum logging (for errors only).
• syscli --ldapsigning disabled|enabled
This CLI command enables or disables LDAP client signing. This setting must
be enabled if and only if the LDAP server signing is enabled on the ADS
server. Otherwise, it must be disabled. For more information on how to
enable LDAP server signing on the ADS server, see Microsoft documentation
at: http://support.microsoft.com/kb/935834
• syscli –maxprocesses <max_smbd_processes>
This CLI command changes the maximum number of smbd processes at any
given time. By default, the limit is 100.
• syscli --clientntlmv2auth yes|no
This CLI changes "client NTLMv2 auth" setting to yes or no. By default, this
setting is set to "yes" and must not be changed unless the domain group
policy on the ADS is set to use the older NTLM (v1) exclusively.
syscli --nfscommit sync {--share <sharename>} | --all
This CLI command allows the admin user to set up NFS shares so that data are
committed synchronously to NFS shares. The user can set up this property for
one NFS share at a time or all NFS shares at the same time. By default, NFS
shares are created to commit data synchronously.
NFS Commit is an NFSv3 client call to request the NFS server to commit cached
data to stable storage. The server has two choices:
a Accelerated mode: This option allows the NFS server to violate the NFS
protocol and reply to commit requests before cached data is committed
Quantum DXi-Series Command Line Interface (CLI) Guide
6-67081-02 Rev A
July 2011
41