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

All Paths Down (APD) is not triggered for LUNs behind IBM SAN Volume Controller (SVC) (65204)

Last Updated: 4/3/2019Categories: TroubleshootingTotal Views: 7450Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

All Paths Down (APD) is not triggered for LUNs behind IBM SAN Volume Controller (SVC) target even when no paths can service I/Os.

The vmkernel logs will report repeating messages similar to the below

018-04-02T18:33:01.623Z cpu21:33633)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.600507680c80802c1800000000000072" - issuing command 0x43ba40eaa180
2018-04-02T18:33:01.623Z cpu21:33633)WARNING: vmw_psp_rr: psp_rrSelectPath:1315: Could not select path for device "naa.600507680c80802c1800000000000072".
2018-04-02T18:33:01.623Z cpu21:33633)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.600507680c80802c1800000000000072" - failed to issue command due to Not found (APD), try again...

Cause

Should an issue result in all the paths to the backend storage servicing an IBM SAN Volume Controller (SVC) become unavailable, the ESXi hosts may not report the expected APD state for the affected volumes. e.g. Power failure on the backend storage.

As a result, IO will not be fast failed and the host may become unresponsive which will require a reboot to recover from.

Resolution

Option 1: VMware ESXi Resolution

This issue is resolved in the releases below

ESX6.5P03 (Build 10884925)

ESX6.7Update 1 (Build 10302608)

The fix is disabled by default.

To enable the fix, change the ESXi config option /Scsi/ExtendAPDCondition from the default of 0 to 1.

To edit this advanced configuration, select the ESXi/ESX host in the Inventory Panel, and then navigate to Configuration > Software > Advanced Settings to launch the Settings window.

Change the values of the “Scsi.ExtendAPDCondition” from the default of 0 to 1

For a full list of alternative methods, see Configuring advanced options for ESX/ESXi (1038578).

Option 2: Alternative IBM SVC Resolution

The IBM fix is included in  APAR HU01839 which is available in 8.2.1.0+, 8.1.3.4+ and 7.8.1.8+ releases

This will address the problem only if the host LUN type is changed from generic to 'adminlun' via a cli command or VVOLS using the Storwize GUI.

Please contact IBM support for further information in relation to the IBM resolution, referencing this VMware KB article.

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
•
Como desabilitar a recuperação de espaço em bloco do provisionamento dinâmico VAAI (UNMAP) no ESXi 5.0 (2007427)

KB
•
Deshabilitar VAAI Thin Provisioning Block Space Reclamation (UNMAP) en ESXi 5.0 (2007427)

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

Take Our Survey

Support Assistant