Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Non Disruptive Upgrade (NDU) of EMC XtremeIO Arrays results in LUN connectivity lost (53519)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 14683Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

In an NMP environment, during a Non Disruptive Upgrade (NDU) of EMC ExtremeIO Arrays, you experience these symptoms:

There is lost connectivity to LUNs with All Paths Down (APD) and Permanent Device Loss (PDL) conditions.

In the /var/log/vmkernel.log file, you see messages showing TUR failing with a PDL on all paths to the device similar to:

2018-01-22T05:43:56.873Z cpu1:69146)WARNING: NMP: vmk_NmpSatpIssueTUR:1043: Device naa.514f0c5b0f800005 path vmhba3:C0:T5:L1 has been unmapped from the array
2018-01-22T05:43:56.873Z cpu2:69146)WARNING: NMP: vmk_NmpSatpIssueTUR:1043: Device naa.514f0c5b0f800005 path vmhba3:C0:T4:L1 has been unmapped from the array

When TUR is failing with PDL and all the paths are down, but the paths are not removed and marked as PDL. In the vobd.log file, you see messages showing that the device lost connectivity at an earlier time and should have been marked as PDL similar to:

2018-01-22T05:29:54.930Z: [scsiCorrelator] 53521051781us: [esx.problem.storage.redundancy.degraded] Path redundancy to storage device naa.514f0c5b0f800005 degraded. Path vmhba2:C0:T5:L1 is down. Affected datastores: "6.0U3_DS1".
2018-01-22T05:43:55.915Z: [scsiCorrelator] 54362036537us: [esx.problem.storage.connectivity.lost] Lost connectivity to storage device naa.514f0c5b0f800005. Path vmhba2:C0:T4:L1 is down. Affected datastores: "6.0U3_DS1".
2018-01-22T05:43:55.915Z: [scsiCorrelator] 54362035359us: [vob.scsi.device.state.permanentloss] Device :naa.514f0c5b0f800005 has been removed or is permanently inaccessible.
2018-01-22T05:43:55.916Z: [scsiCorrelator] 54362036985us: [esx.problem.scsi.device.state.permanentloss] Device: naa.514f0c5b0f800005 has been removed or is permanently inaccessible. Affected datastores (if any): "6.0U3_DS1".

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

Cause

This issue occurs because the storage path is marked as Permanent Device Loss (PDL) even before the TUR (from the Array) has marked the path as PDL.

A PDL is returned from either the target (array) or the firmware on the controller. Some changes/regressions might also cause a PDL to be returned, even if it was marked as a PDL from the Array/Controller. In this situation, any further I/O on the same path is FAST PDL'ed on the VMware layer as those paths would no longer be usable or active. This is exactly what happens during a Non Disruptive Upgrade (NDU).

Resolution

This issue is resolved in:

VMware ESXi 6.0 Patch Release ESXi600-201807001 (Build 9239799), available at VMware Patch Downloads.

VMware ESXi 6.5 Patch Release ESXi650-201811002 (Build 17477841), available at VMware Patch Downloads.

VMware ESXi 6.7 Patch Release ESXi670-201912001 (Build 15160138), available at VMware Patch Downloads.

For more information on downloading patch, see How to download patches in Customer Connect (1021623).

Workaround

To work around this issue if you do not want to upgrade, perform these steps while performing NDU:

Upgrade Controller 1.

To get the dead paths active, run this command:

esxcfg-rescan -d

Note: In case there is any issue with the above command, use the esxcfg-rescan -A command instead.

Upgrade Controller 2.

To get the dead paths active, run this command:

esxcfg-rescan -d

Notes:

In case there is any issue with the above command, use the esxcfg-rescan -A instead.

The commands esxcfg-rescan -d and esxcfg-rescan -A are to be done alternately after each controller upgrade.

Related Information

For more insight into TUR and PDL specific events, see:

Understanding the storage path failover sequence in VMware ESXi native multipathing (1027963)

Storage path does not fail over when TUR command repeatedly returns retry requests (2106770)

"state in doubt; requested fast path state update" error in ESXi (1022026)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
从 vCenter Server 使用的数据库中清除旧数据 (1025914)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant