Overland Storage SnapServer Administrator's Manual page 60

SnapServer 7.0 Administrator's Guide
3. If you select Unix Kerberos security, complete the options in the table below. Note
the following:
• The service will not start unless the TCP/IP domain name
• You must create the NFS and host service entries in the keytab with the fully
• The SnapServer assumes the domain name from the primary Ethernet interface.
4. Click OK to save the configuration.
NOTE: After enabling NFSv4 with Kerberos security, read-write host entries for
To Mount Shares from NFS Clients
A share on a SnapServer is equivalent to an exported filesystem on an NFS server. NFS
users can mount SnapServer shares and access content directly, or mount a subdirectory of
a share, using the following procedure:
1. To mount an NFS client, enter one of the following commands:
a. To mount via NFSv2 or NFSv3:
b. To mount via NFSv4 with standard NFS host-based security, modify the above
c. To mount via NFSv4 with Kerberos security, enter one of the following commands,
10400317-001 10/2011
exactly the same as the keytab.
qualified domain name of the SnapServer.
For more information, see
Option Description
KDC Host Name Enter the host name of the Kerberos server (for example,
kerberos-2000.mit.edu).
Realm Name Enter the Kerberos realm name (For example, ATHENA.MIT.EDU).
NOTE:
Browse to locate and upload the Kerberos key tab file (for
Key Tab File Click
example,
NOTE:
, and
gss/krb5i gss/krb5p
each NFS-enabled share.
mount server_name:/share_name
where server_name is the name or IP address of the server, share_name is the
name of the share you want to mount, and local_mount is the name of the mount
target directory.
command as follows:
server_name:/share_name /local_mount
mount -t nfs4
depending on the level o f security desired:
• Authentication only (client is authenticated via Kerberos):
mount -t nfs4 -o sec=krb5 server_name:/share_name
©2010-11 Overland Storage, Inc.
"TCP/IP Options" on page
Realm names are conventionally specified in all CAPITAL
letters, but this is not required to function correctly.
zeus.keytab).
This file can have any name the administrator wishes to give
it. If you do not have a keytab file for the SnapServer:
– create a host and NFS principle for the SnapServer on the
KDC
– generate a keytab file
– save it to a location the client administering the
SnapServer can access.
are automatically added to the NFS access entries for
/local_mount
3 – Network Access
(page 3-3) is set up
3-3.
gss/krb5
/local_mount
,
3-17