Pillar Axiom: Newly added hosts to the NAS Filesystem Access Control List cannot access a share with the expected privilege

Asset ID:	1-72-1519038.1
Update Date:	2014-12-09
Keywords:

Solution Type Problem Resolution Sure

Solution 1519038.1 : Pillar Axiom: Newly added hosts to the NAS Filesystem Access Control List cannot access a share with the expected privilege

Applies to:

Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 300 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

A client host cannot connect to the NAS shares if the Access control list is filled up with the hostnames but works when IP are used.
Problem seems to appear since the Axiom has been upgraded to 4.6.1

Cause

It is unclear if DNS changes have been perform in the customer environement but the NAS debug logs shown errors when trying to reach the DNS.
If a DNS query is unsuccessful, the host mounting the share will be granted the default access if set up or else denied the access.

Solution

For this particular case using the FQDN (Fully Qualified Domain Names) when mounting NFS shares resolved the performance issue.

mount My_NAS_CU_NAME.mydomain:/nfs_share /mountpoint

instead of

mount My_NAS_CU_NAME:/nfs_share /mountpoint

References

<BUG:15908205> - FUJITSU || CANNOT MOUNT FILESYSTEM WHEN HOSTNAME IS USED IN THE ACCESS LIST

Attachments

This solution has no attachment