Enabling file audit logging on an owning cluster for a file system that is remotely mounted

Use this information to enable file audit logging on an owning cluster for a file system that is remotely mounted.

Perform the following steps to enable file audit logging for a remotely mounted file system:
  1. Make sure that both the accessing and owning clusters are on IBM Storage Scale 5.0.2 minimum release level.
  2. Make sure that the file systems that are going to be remotely mounted are at IBM Storage Scale 5.0.2 or higher.
  3. Follow the instructions in Accessing a remote GPFS file system.
  4. Validate that the accessing cluster has the required packages installed by referring to Requirements, limitations, and support for file audit logging.
  5. If not already enabled, enable file audit logging in the owning cluster by following the instructions in Configuring file audit logging.
  6. At this point, file audit logging should be logging all file system activity from the accessing cluster nodes that have fulfilled the previous steps.
  7. The file audit logs will be owned and located on the owning cluster. Run mmaudit <device> list on the owning cluster for details.
Note: The file audit logging producers on the accessing cluster will log debug messages to the local /var/adm/ras/mmaudit.log file. But the overall file audit logging status and logging can only be obtained from the owning cluster. For more information, see File audit logging issues.