mmcesdr secondary config should create NFS exports without RW access to all clients

Please can you modify mmcesdr secondary config so that it creates secure NFS exports (for use by AFM) by only exporting to the gateways of the primary cluster, and not all clients.

When mmcesdr is used (mmcesdr secondary config) to set up the secondary cluster for protocol cluster replication, it creates exports that are accessible to ANY client on the network. For example:

secondary# mmnfs export list --nfsdefs /mnt/mygpfs/nfs-cac31
Path Delegations Clients Access_Type Protocols Transports Squash Anonymous_uid Anonymous_gid SecType PrivilegedPort DefaultDelegations Manage_Gids NFS_Commit
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/mnt/mygpfs/nfs-cac31 none * RW 3,4 TCP NO_ROOT_SQUASH -2 -2 SYS FALSE none FALSE FALSE

As a consequence, ANY client can mount ANY of the NFS exports created on the secondary cluster by mmcesdr and access data there. Those exports will contain copies of all the data from the primary (production) cluster, and hence provide a way for unauthorized people to get access to the production data via the secondary cluster export used by AFM.

Mmcesdr should be setting up it NFS exports for use by AFM by only exporting to the gateways at the primary site. mmcesdr should be able to add this information into the DR_Config file that is creates and which is copied to the secondary site prior to the running of the “mmcesdr secondary config” command, so that the NFS exports created for use by AFM are only available to the primary cluster gateways.