mmafmconfig command

Can be used to manage home caching behavior and mapping of gateways and home NFS exported servers.

Synopsis

You can use the mmafmconfig command to -
  • Set up or update mapping for parallel data transfers by using add, update, or delete options.
  • Enable or disable extended attributes/sparse file support from the AFM cache.
mmafmconfig {add | update} MapName --export-map ExportServerMap [--no-server-resolution]

or

mmafmconfig delete {MapName | all}

or

mmafmconfig show [-Y] [MapName | all]

or

mmafmconfig {enable | disable} ExportPath

Availability

Available on all IBM Spectrum Scale editions. Available on AIX® and Linux®.

Description

Start of changeOn the home cluster, this command is usedEnd of change to enable support of extended attributes, sparse files on an AFM cache fileset pointing to this home. You must run the mmafmconfig enable command on the home export or target path. Running this command creates the .afm directory that contains the control-enabled, directio '.afmctl' file. The mmafmconfig disable command removes the .afm directory from the home export or target path and subsequently, the cache will no longersupport synchronization of sparse files and files with extended attributes.

Start of changeOn the cache cluster, you can use the mmafmconfig command with the add, update, delete, or show options to manage the mapping of gateway nodes with home NFS or cloud object servers for parallel data transfers.End of change

You must run the mmafmconfig enable command at a home fileset path before you link the AFM fileset at the cache site.

If the AFM cache fileset was linked without running the mmafmconfig enable command at the home export path, you need to issue the following commands:
  1. Issue the following command at the home:
    # mmafmconfig enable HOME_EXPORT_PATH
  2. Issue the following commands at the cache:
    # mmafmctl FS stop -j AFM_Fileset
    # mmafmctl FS start -j AFM_Fileset

Parameters

MapName
Specifies the name that uniquely identifies the mapping of the gateway nodes with the home NFS exported servers.
--export-map ExportServerMap
Specifies a comma-separated list of pairs of home NFS exported server nodes (ExportServer) and gateway nodes (GatewayNode), in the following format: 
[ExportServer/GatewayNode][,ExportServer/GatewayNode][,...]
where:
ExportServer
Is the IP address or host name of a member node in the home cluster MapName.
GatewayNode
Specifies a gateway node in the cache cluster (the cluster where the command is issued).
--no-server-resolution
When this option is specified, AFM skips the DNS resolution of a specified hostname and creates the mapping. The specified hostname in the mapping is not be replaced with an IP address.Start of change The hostname is collected after the DNS resolution during the creation of mapping.End of change Ensure that the specified hostname is resolvable while the mapping is in operation.
-Y
Displays the command output in a parseable format with a colon (:) as a field delimiter. Each column is described by a header.
Note: Fields that have a colon (:) are encoded to prevent confusion. For the set of characters that might be encoded, see the command documentation of mmclidecode. Use the mmclidecode command to decode the field.
enable
Enables extended attributes or sparse files functions on the AFM cache. Run at the home cluster only.
disable
Disables extended attributes or sparse files functions on the AFM cache. Run at the home cluster only.
ExportPath
Specifies the root of the home exported directory for enabling or disabling the AFM features.
add
Sets up maps for parallel data transfers. Run at cache only.
delete
Deletes maps for parallel data transfers. Run at cache only.
update
Updates maps for parallel data transfers. Run at cache only.
show
Displays all the existing maps. Each map displays the mapping of a gateway node and home NFS server pair that is separated by a comma ','.

Exit status

0
Successful completion.
Nonzero
A failure has occurred.

Security

You must have root authority to run the mmafmconfig command.

The node on which the command is issued must be able to run remote shell commands on any other node in the cluster without the use of a password and without producing any extraneous messages. For more information, see Requirements for administering a GPFS file system.

Example

The following is an example of a mapping for NFS targets, adding all gateway nodes and NFS servers, and using this mapping for creating AFM filesets. In this example, hs22n18, hs22n19, hs22n20, and hs22n21 nodes are assumed as cache gateway nodes. The gateway nodes are mapped to two home NFS servers, js22n01 with an IP address 192.168.200.11, and js22n02 with an IP address 192.168.200.12.
  1. Start of changeCreate an export map.End of change
    # mmafmconfig add mapping1 --export-map js22n01/hs22n18,js22n02/hs22n19,
js22n01/hs22n20,js22n02/hs22n21
    Start of changeA sample output is as follows:
    mmafmconfig: Command successfully completed.
    End of change
  2. Start of changeCheck the created export map.End of change
    # mmafmconfig show
    Start of changeA sample output is as follows:
    
Map name:              mapping1
Export server map:     192.168.200.11/hs22n18.gpfs.net,192.168.200.12/hs22n19.gpfs.net,92.168.200.11/hs22n20.gpfs.net,192.168.200.12/hs22n21.gpfs.net
    End of change
  3. Start of changeCreate an export map by specifying the --no-server-resolution option.
    # mmafmconfig add map1 --export-map nfs1.net/gateway1.net,nfs2.net/gateway2.net
    A sample output is as follows:
    mmafmconfig: Command successfully completed
mmafmconfig: 6027-1371 Propagating the cluster configuration data to all
affected nodes.  This is an asynchronous process.
    End of change
  4. Start of changeCheck the export map that is created by specifying the --no-server-resolution option.
    # mmafmconfig show all
    A sample output is as follows:
    Map name:             map1
Export server map:    nfs1.net/gateway1.net,nfs2.net/gateway2.net
    End of change
  5. Start of changeCreate an export map without the --no-server-resolution option.
    # mmafmconfig add map2 --export-map nfs1.net/gateway1.net,nfs2.net/gateway2.net
    End of change
  6. Start of changeCheck the export map that is created without --no-server-resolution option.
    # mmafmconfig show all
    A sample output is as follows:
    Map name:             map2
Export server map:    192.168.1.10/gateway1.net,192.168.1.11/gateway2.net
    End of change
  7. Issue the following commands to create filesets by using mapping1: 
    # mmcrfileset gpfs1 sw1 –p afmmode=sw,afmtarget=nfs://mapping1/gpfs/gpfs2/swhome --inode-space new
    # mmcrfileset gpfs1 ro1 –p afmmode=ro,afmtarget=nfs://mapping1/gpfs/gpfs2/swhome --inode-space new

See also

Location

/usr/lpp/mmfs/bin