Command
weka nfs interface-group addUse the following command line to add an interface group:
weka nfs interface-group add <name> <type> [--subnet subnet] [--gateway gateway] [--allow-manage-gids allow-manage-gids]
The parameter allow-manage-gids determines the type of NFS stack. The default value of this parameter is on, which sets the NFS-W stack. Do not mount the same filesystem by containers residing in interface groups with different values of the allow-manage-gids.
Example:
weka nfs interface-group add nfsw NFS --subnet 255.255.255.0 --gateway 10.0.1.254
Parameters
Name | Type | Value | Limitation | Mandatory | Default |
---|---|---|---|---|---|
name | String | Unique interface group name | Up to 11 characters length | Yes | |
type | String | Group type | Can only be NFS | Yes | |
subnet | String | The subnet mask in the 255.255.0.0 format | Valid netmask | No | 255.255.255.255 |
gateway | String | Gateway IP | Valid IP | No | 255.255.255.255 |
allow-manage-gids | String | Allows the hosts within this interface group to use manage-gids when set in exports. With manage-gids, the list of group IDs received from the client will be replaced by a list of group IDs determined by an appropriate lookup on the server. |
on or off Cannot be set if one of the hosts belongs to an interface group which does not have the allow-manage-gids flag set. |
No | on |
Note: Each host can be set to be part of interface groups with the same value of allow-manage-gids. In addition, you must not mount the same filesystem by the hosts residing in interface groups with different values of allow-manage-gids.
Note:
- Do not mount the same filesystem by containers residing in interface groups with different values of the `allow-manage-gids.
- As a best practice, it is recommended to have only one of the following protocol containers, NFS or SMB installed on the same server.
Starting from version 4.2, setting more than one additional protocol to the existing POSIX is not allowed.