RedHat 6.9 NFS client is not getting reconnected to VCS-controlled NFS server after its failover

book

Article ID: 100043033

calendar_today

Updated On:

Description

Error Message

There was no error as such on the NFS client. However, the mountpoint entered a hung state for about 10-15 minutes after the NFS server had been successfully failed over to another node in the cluster.

Cause

Cause was unclear, although it was suggested to upgrade the client OS.

Resolution

It was suggested to upgrade the RedHat client to RHEL 7.4 (from 6.9). The hang of the NFS client after successful NFS server failover then reduced from 10-15 minutes to about 20 seconds.

NFS client ( rehat server) is not getting reconnected and mounted to NFS server which AIX and VCS. During the VCS (NFS share) failover, NFS client is not getting remounted once NFS shares are available. Intially, we have AIX TL4 SP1, in that setup, NFS server and Client worked Properly during the VCS failover. But after upgrade to SP4, we are facing this issue. Already ticket was raised for this issue and ticket no is 180120-000187. IBM saying there is no problem with SP4, it is problem with VCS handling the NFS. We want to know if any VCS patch is available to support AIX TL4 SP4. Please check and confirm. It's high priority issue. Customer expecting the fix ASAP

Issue/Introduction

After failover of VCS-controlled NFS server, RedHat 6.9 client took 10-15 minutes before it could access files. Configuration was as follows: NFS server (under Cluster Server (VCS) control): AIX 7.1TL4 and Cluster Server 6.0.5 NFS client: RedHat 6.9 It was proven that VCS played no part in the hang on the NFS client as it also hung for about 10-15 minutes, regardless of whether the NFS server was under VCS control or not.
Powered by Wolken Software