Installation manual

Configuring a Namespace
Setting NFS Character Encoding
CLI Storage-Management Guide 7-11
Changing Protocols After Import
We strongly recommend that you choose your protocol set carefully, before
configuring any volumes in the namespace. After a managed volume and at least one
of its shares is enabled (as described later in the managed-volume chapter), the
managed volume imports files and directories from its enabled shares. Protocol
changes after this first import require greater care, since they may affect client access
to the volume. The following changes affect client service:
• converting a single-protocol namespace to a multi-protocol namespace,
• removing CIFS, or
• removing all support for one version of the NFS protocol (that is, removing NFS2
or removing both of NFS3 and NFS3/TCP).
To make these conversions, you take the managed volume offline (with NSCK
destage, described in the CLI Maintenance Guide), change the protocol with this
command, and restart the imports by re-enabling the managed volume.
For other protocol changes, such as adding NFSv2 to a running NFSv3 namespace,
you must disable the volume (using
no enable) and its front-end NFS service
(described in a later chapter), change the protocol, then re-enable both. This causes a
shorter service outage.
Setting NFS Character Encoding
NFS character encoding refers to the encoding used for each character in an NFS
filename. This is the mapping of binary numbers to character symbols. ASCII is an
example of a character encoding used commonly in the United States.
A site has a character encoding for NFS filenames that is shared amongst all clients
and servers. This should be well-established before the installation of the ARX.
In a managed volume, a multi-protocol namespace prevents CIFS clients from
creating a filename that cannot translate directly into the NFS character encoding. For
example, if the NFS encoding is ISO 8859–1 (Latin1, a single-byte encoding) and a
CIFS user tries to create a file with Korean (multi-byte) characters in the name, the
namespace rejects the create operation. A multi-protocol namespace only allows
characters that are mappable between NFS and CIFS.