IBM G27, User Reference

Page: 66 / 200

– Advanced File Share
v For NFS shares properties:
– Permissions
– Share
A note on anonymous access: When you create an NFS share, it is
strongly recommended that you not disable anonymous access to
avoid client-connection problems. See “Enabling Server for NFS” for
more details.
f. Click Finish to create the resource.
g. Right-click the resource and select Bring online .
Enabling Server for NFS
To enable Server for NFS, you need to specify where User Name Mapping is
running.
To specify where User Name Mapping is running, follow this path, Services for
UNIX
→
User Name Mapping , and then enter the server name that is running User
Name Mapping in the Computer Name field. For a cluster, this entry must be the
clustered name or IP address, not that of an individual node.
When planning an NFS installation, consider which machines you want to have
particular access-levels to NFS shares. Each class of access should be captured by
defining a separate client group.
v To define a client group, click Services for UNIX → Client Groups , type the
group name in the Group Name field, then click New .
v To add members to a client group, select a group name from the current groups
list; then click
Advanced and type the name of a client (a valid computer name).
v A note on anonymous access: It is strongly recommended that you not disable
anonymous access. If a client presents a UID that is not recognized, Server for
NFS can still grant that client a very limited form of access as a special
nobody
user. This is known as anonymous access, and you can enable or disable on a
per-share basis. This anonymous user will have very limited access to resources
on the NAS: it has only the permissions that are granted to the
Everybody group
in Windows, which corresponds to the other (or world ) bits in a POSIX
permissions mode.
Allowing anonymous access is not a security risk, so disabling it might provide a
false sense of security. (The real security risk is to grant everyone access to
resources that should be protected.) And disabling anonymous access has one
severe consequence: it is so unexpected by NFS clients that they might not be
able to connect as NFS V3 clients at all, and might instead downgrade the
connection to use the NFS V2 protocol.
Recovering from a corrupted Quorum drive
Attention: Restoring a Quorum rolls the cluster back in time to the backup date.
There are impacts to performing this operation that include loss of data. You should
perform this operation only when it is absolutely necessary.
Clustering relies on data stored on the Quorum disk to maintain resource
synchronization between the two nodes in the cluster. In the event of a power loss
to both nodes or a hardware failure that corrupts the Quorum data, the cluster
service might not start, leading to the following event log error:
52
NAS Gateway 300 User’s Reference