Policy parameters for Linux

Table 1. NFS server high availability policy parameters (Linux)
# Parameter description Value Type
Value
1

Enter the name of your SA MP domain.

Provide the name of an existing SA MP domain. The SA MP domain will host the NFS resources that will be configured with this template.

 Value type: String
 
2

Enter your desired prefix for all NFS server resources.

This prefix will be used as a prefix for all SA MP resources that cover the NFS server. For later operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command.

 Value type: String
nfsserver
3

Enter the nodes where you want to automate the NFS server.

These nodes must be listed when you enter the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. NFS server resources will be created for each of the specified nodes

 List of values, value type for each value: Hostname or IP version 4 address (plus additional value checking)
 
4

Select the IP version used in your cluster.

Depending on the IP version you must specify either NetMask for IPv4, or NetPrefix for IPv6.

 One of these values:
  • IPv4
  • IPv6
IPv4
5
This parameter will be ignored unless the following condition is fulfilled:
  • Parameter # 4 has the value IPv4.

Specify a virtual IPv4 address for the NFS server instance.

This IPv4 address will be used as a virtual IP address for the floating NFS server instance.

 Value type: IP version 4 address
 
6
This parameter will be ignored unless the following condition is fulfilled:
  • Parameter # 4 has the value IPv6.

Specify a virtual IPv6 address for the NFS server instance.

This IPv6 address will be used as a virtual IP address for the floating NFS server instance.

 Value type: IP version 6 address
 
7
This parameter will be ignored unless the following condition is fulfilled:
  • Parameter # 4 has the value IPv4.

Enter the netmask for the subnet of the virtual NFS server IP address.

Enter the netmask for the subnet of the virtual NFS server IP address. An example for a netmask is 255.255.255.0

 Value type: IP version 4 address
255.255.255.0
8
This parameter will be ignored unless the following condition is fulfilled:
  • Parameter # 4 has the value IPv6.

Enter the NetPrefix for the virtual NFS server IP address.

Enter the NetPrefix for the virtual NFS server IP address.

Value type: numeric.

Minimum value: 0, maximum value: 128
 
9

Enter the available network interface for the NFS Server. The following network interfaces are available on your local system: (remaining part of description is harvested from running system)

The available network interface specifies to which network interface the virtual NFS server IP address can be bound, for AIX® an example is "en0", for Linux®, an example is "eth0". The same network interface name needs to be available on all nodes where the NFS server will be automated.

 Value type: String (plus additional value checking)
 
10

Specify the name of the IBM.AgFileSystem resource that represents the mount point of the NFS server configuration data directory. The following IBM.AgFileSystems are available in your domain ("Name" "SysMountPoint"): (remaining part of description is harvested from running system)

SA MP will automatically mount the directory with NFS server configuration data prior to starting the NFS server processes, and will automatically unmount the directory after stopping the NFS server processes. You can determine the name of the IBM.AgFileSystem by issuing the command 'lsrsrc -s "ResourceType==1" IBM.AgFileSystem Name SysMountPoint'. This command will return a list of IBM.AgFileSystem resources. Use the name of the resource that represents the mount point of the NFS server configuration data directory.

 Value type: String (plus additional value checking)
 
11

Specify the names of the IBM.AgFileSystem resources that represent the mount points of the directories to be exported. The IBM.AgFileSystem resources can be combined in multiple IBM.ResourceGroups. For each group, the IBM.AgFileSystem resource names have to be specified separately. The following IBM.AgFileSystems are available in your domain ("Name" "SysMountPoint"): the remaining part of description is harvested from the running system.

The values are specified in table form:
  • Each table row (prompted as "value") consists of variable number of columns (each column prompted as "sub-value").
  • The variable number of columns is prompted for each row separately.
  • Each table row will result in a separate IBM.ResourceGroups.
  • Each column within a row represents a single IBM.AgFileSystem resource name, that will be added to one IBM.ResourceGroups.
SA MP will automatically mount and export each directory if the corresponding resource group is started, and will automatically unmount and unexport the directory if the corresponding resource group is stopped. You can determine the name of the IBM.AgFileSystem by issuing the command: 
lsrsrc -s "ResourceType==1" IBM.AgFileSystem Name SysMountPoint'.
This command will return a list of IBM.AgFileSystem resources. Use the name of the resources that represent the mount points of the exported file systems.
Example: 
IBM.ResourceGroup:data1-filesys-rg
- IBM.AgFileSystem:FS1 MNT=/mnt/test_a
- IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one
- IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two
IBM.ResourceGroup:data2-filesys-rg
- IBM.AgFileSystem:FS4 MNT=/mnt/test_b
- IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one

Specify the values in the following form:
Number of columns for value 1: 3
Value 1, sub-value 1: "FS1"
Value 1, sub-value 2: "FS2"
Value 1, sub-value 3: "FS3"
Number of columns for value 2: 2
Value 2, sub-value 1: "FS4"
Value 2, sub-value 2: "FS5"
Number of columns for value 3: Just press ENTER to complete the input.
This parameter must have the same number of values as the following parameters:
  • Parameter # 12
 List of values, each value consisting of a variable number of sub-values, value type for each sub-value: String (plus additional value checking)
 
12

Specify the mount points of the directories to be exported. These mount points must be specified in the same structure as you have specified the IBM.AgFileSystem names in the previous question.

Specify the mount points of the directories to be exported. For each directory, only one export can be configured. The values are specified in table form. Each table row (prompted as "value") consists of variable number of columns (each column prompted as "sub-value"). The variable number of columns is prompted for each row separately. Each table row belongs to an IBM.ResourceGroup specified in the previous question. Each column within a row represents a mount point name.

Example: 
IBM.ResourceGroup:data1-filesys-rg
- IBM.AgFileSystem:FS1 MNT=/mnt/test_a
- IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one
- IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two
IBM.ResourceGroup:data2-filesys-rg
- IBM.AgFileSystem:FS4 MNT=/mnt/test_b
- IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one

Specify the values in the following form:
Number of columns for value 1: 3
Value 1, sub-value 1: "/mnt/test_a"
Value 1, sub-value 2: "/mnt/test_a/one"
Value 1, sub-value 3: "/mnt/test_a/two"
Number of columns for value 2: 2
Value 2, sub-value 1: "/mnt/test_b"
Value 2, sub-value 2: "/mnt/test_b/one"
Number of columns for value 3: Just press ENTER to complete the input.
This parameter must have the same number of values as the following parameters:
  • Parameter # 11
 List of values, each value consisting of a variable number of sub-values, value type for each sub-value: String (plus additional value checking)
 
13

Are you running with NFS version 4?

If the NFS server is running with NFSv4, a separate daemon process, called idmapd has to be started, stopped and monitored. Specify 'yes' if you are running with NFSv4.

 Value type: {yes|no}
 
14
This parameter will be ignored unless all following conditions are fulfilled:
  • Parameter # 13 has the value "yes"

Specify the path of the RPC pipefs directory.

The RPC pipefs is a required directory of the rpc.idmapd daemon for NFSv4. The idmapd is the NFSv4 ID to name mapping daemon. The default path for the pipefs is /var/lib/nfs/rpc_pipefs.

 Value type: String
/var/lib/nfs/rpc_pipefs
15

Are there any nested mount points between mounted file systems within one file system set?

Nested mount points are mount points where one mount point contains another mount point, that is, /mnt/test/ one is a nested mount point to /mnt/test.

 Value type: {yes|no}
no
15.1

Optional; a value for this parameter is only required if parameter # 15 has the value "yes".

Specify the nested mount points that are contained in one file system set. For each nesting level, sub-value number 1 is the nested mount point, sub-value number 2 is the mount point one level above. You need to specify the names of the IBM.AgFileSystem resources for each mount point.

Specify the names of the IBM.AgFileSystems of the nested mount points that are contained in one file system set. The values are specified in table form. Each table row (prompted as "value") consists of two columns (each column prompted as "sub-value"). The first column value is the nested mount point and the second column value is the mount point at the higher directory level. Each row will be used to create a StartAfter relationship from first column value (source) to second column value (target).

Example: 
IBM.ResourceGroup:Group1
- IBM.AgFileSystem:FS1 MNT=/mnt/test_a
- IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one
- IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two
IBM.ResourceGroup:Group2
- IBM.AgFileSystem:FS4 MNT=/mnt/test_b
- IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one

Specify the values in the following form:
Value 1, sub-value 1: "FS2"
Value 1, sub-value 2: "FS1"
Value 2, sub-value 1: "FS3"
Value 2, sub-value 2: "FS1"
Value 3, sub-value 1: "FS5"
Value 3, sub-value 2: "FS4"
Value 4, sub-value 1: just press Enter to complete input
 List of values, each value consisting of the same number of sub-values, value type for each sub-value: String
 
16

Specify the desired state of your NFS server resources.

If you specify Online, the NFS server resources will be started on policy activation, if not already started. If you specify Offline, the NFS server resources will not be started on policy activation, but stopped if they are online.

 One of the following values:

Online

Offline
Offline