Configuring and enabling SMB and NFS protocol services

If you have not previously enabled and started the Cluster Export Services (CES) protocol services, enable and start them now.

Prerequisites

When you enable SMB protocol services, the following prerequisites must be met:

The number of CES nodes must be 16 or lower.
All CES nodes must be running the same system architecture. For example, mixing nodes based on Intel and Power® is not supported.

When you add new CES nodes to a running system where the SMB protocol is enabled, the following prerequisite must be met:

All CES nodes must be in SMB HEALTHY state.

When you remove a CES node from a running system where the SMB protocol is enabled, the following prerequisite must be met:

All CES nodes (except for the node that is being removed) must be in SMB HEALTHY state.

For more information about the SMB states, see mmces command.

Disabling SMB protocol services deletes all configured SMB shares and SMB settings. After SMB is re-enabled, all exports and settings must be re-created and reconfigured. Also, the NFS configuration is removed when NFS is disabled, so whatever you exported previously is lost. To save the NFS configuration, backup the contents of /var/mmfs/ces/nfs-config/ on any protocol node.

Enabling protocol services

Issue the following commands to enable SMB and NFS services on all CES nodes:

```
mmces service enable SMB 
```
```
mmces service enable NFS 
```

GUI navigation

To enable SMB services in the GUI, log on to the IBM Spectrum Scale™ GUI and select Settings > SMB Service.
To enable NFS services in the GUI, log on to the IBM Spectrum Scale GUI and select Settings > NFS Service.

The protocol services that are used need to be started on all CES nodes:

mmces service start SMB -a

mmces service start NFS -a

After you start the protocol services, verify that they are running by issuing the mmces state show command.

Note: The start and stop are maintenance commands. Stopping a service on a particular protocol node without first suspending the node ensures that the public IP addresses on that node stay with that node. In this case, protocol clients that try to connect to the service with these IP addresses will fail.

The sequence of commands to enable file access and then disable file access, using the NFS service as an example, follows:

Enable NFS by using the following command:
```
mmces service enable NFS
```
Note: This command also starts NFS on all CES nodes.

Then you need to set up the authentication before you can add an export. The easiest authentication setup is to use system authentication.
Set up the authentication by using userdefined authentication type and file data access method:
```
mmuserauth service create --data-access-method file --type userdefined
```
Add an export by running the following command, where fs0 is a GPFS™ file system and fset0 is an independent fileset:
```
mmnfs export add /gpfs/fs0/fset0
```
Verify that this is configured and running by using the following commands:
```
mmces service list -a
mmuserauth service list
mmnfs export list
```
Stop NFS and disable NFS protocol on the CES nodes by running the following commands:
```
mmces service stop nfs -a
mmuserauth service remove --data-access-method file
```
Note: Authentication services must be removed for file access before disabling the NFS; and if SMB is enabled and running, then you cannot remove file authentication now.
Disable NFS service on the CES nodes by running the following command:
```
mmces service disable NFS
```
Note: The NFS configuration is removed when NFS is disabled, so whatever you exported previously is lost. To save the NFS configuration, backup the contents of /var/mmfs/ces/nfs-config/ on any protocol node.