Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

NetApp NFS41 Server Failover causes NFS41 datastore to go in inaccessible state (76136)

Last Updated: 3/21/2024Categories: TroubleshootingTotal Views: 19602Language:
English

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Symptoms

Failover and failback operations at array side causes connection loss thereby NFS41 datastore experiences All Paths Down(APD) state.

VMkernel logs will report following events:

2018-08-09T06:23:42.864Z cpu2:33728)StorageApdHandler: 1204: APD start for       0x430595afb140 [12345678-561c124e-0000-000000000000]
2018-08-09T06:23:42.864Z cpu0:33076)StorageApdHandler: 421: APD start event for  0x430595afb140 [12345678-561c124e-0000-000000000000]
2018-08-09T06:23:42.576Z cpu2:33728)WARNING: NFS41: NFS41FSAPDNotify:5600: Lost  connection to the server 192.168.xx.xx mount point NFS_Datastore, mounted as 12345678-561c124e-0000-000000000000 ("/NFS_Datastore")

A reboot of ESXi hosts is required to recover from APD.

This issue does not affect NFSv3

Note :The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.

Cause

After failover NFS41 gets new client ID from NFS server. This causes NFS41 to enter into infinite loop of exchange-id request and reply processing thus causing datastore unavailability.

Resolution

Issue is resolved in ESXi 6.7P02 and ESXi 7.0 GA. The issue has been fixed in upcoming release of ESXi 6.5

Workaround

Use NFSv3 to prevent the issue.

Related Information

NetApp KB: VMWare NFSv4.1 Datastores see Disruption During Failover Events Including Upgrade

To troubleshoot NFS APD issues refer to VMware KBs :
Troubleshooting connectivity issues to an NFS datastore on ESX and ESXi hosts
NFS connectivity issues on NetApp NFS filers on ESXi 5.x/6.x
How to troubleshoot NFS APD (All-Paths-Down) issues on VMware ESXi

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice or statements made on third-party websites.Inclusion of such links does not imply that VMware endorses, recommends or accepts any responsibility for the content of such sites.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Downloading and Installing the standalone VMware Remote Console (VMRC) in vSphere (2091284)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant