Filter
Top Products
Appendix C StorNext Files
Cluster-Wide Central Control
StorNext 3.5 Installation Guide 135
there to be overlapping in IP address between an individual host and
netgrp, but the individual host should be defined before the netgrp.
The following controls are currently supported:
1 mountReadOnly: Control whether a client should mount as read-
only. The default is read/write.
2 mountDlanClient: Control whether a client can mount as a proxy
client. The default is not allowed.
3 takeOwnership: Control whether users on a Windows client are
allowed to to take ownership of a file or directory in a StorNext file
system.
4 snfsAdmin: Controls whether cvadmin running on a host is allowed
to have super admin privilege to run privileged commands such as
start/stop fs.
5 snfsAdminConnect: Controls whether cvadmin running on a client is
allowed to connect to other fsm via the -H option.
If no match is found for a given client's IP address, the client has no
privileges. If a file system has been defined but the client is not defined in
that file system’s control section (securityControl), the client has no access
privileges to the specified file system.
Cluster-Wide Control File
Example 3
The control file called nss-cct1.xml provides a feature overview and
describes how to configure the central control file. The values entered in
the following sample file are for example purposes only and should not
necessarily be entered in your own control files.
#
# Cluster-wide Central Control File
#
# The nss-cctl.xml file provides a way to restrict the behavior of
# SNFS cluster nodes (fsm, file system client, cvadmin client) from
# a central place, i.e on nss server. As for SNFS 3.5, we support the
# following controls:
# 1. Whether a client is allowed to mount as a proxy client
# 2. Whether a client is allowed to mount as read/write or read-only.
# 3. Whether a user especially local admin on windows is allowed to take