Loading

×Sorry to interrupt
CSS Error

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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Path Redundancy to Storage Device Degraded message on the ESXi host (1009555)

Last Updated: 2/26/2024Categories: TroubleshootingTotal Views: 129400Language:
Chinese (Simplified)KoreanJapaneseEnglish

26 like this article

Subscribe to get an email
newsletter with new updates

26 people found this helpful Please provide article feedback:

Details

Of the different multi-pathing options that are available when interacting with a storage device, you might hit a scenario where one (or more than one) of these paths might not be available for you to leverage the entire depth of VMware multi-pathing.

At no point in time, even if the VMware connectivity to the back-end device is lost, other available paths can still be leveraged and communication with them should still continue, and there would not be any impact to the VMs or their functionality. However, there could still be a dip observed in the VMs overall performance.

The Task and Events tab of the ESXi host on the vSphere Client reports the error similar to:

Path redundancy to storage device naa.60a9800043346534645a433967325334 degraded. Path vmhba3:C0:T1:L7 is down. Affected datastores: Datastore1.

or

Lost access to volume 5c784594-db4be3e2-5618-0017a4770014 (Datastore1) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.

Solution

Examining this error:

Path redundancy to storage device naa.60a9800043346534645a433967325334 degraded. Path vmhba3:C0:T1:L7 is down. Affected datastores: Datastore1.

The above error message indicates that of the different multi-pathing options in place to interact with device "naa.60a9800043346534645a433967325334", only one path "vmhba3:C0:T1:L7" is down, and this path is no longer usable.

Breaking down the specifics of this path - vmhba3:C0:T1:L7, you can see several interaction points (or potential failure points):

vmhba3 - HBA (Host Bus Adapter)

C0 - Channel 0

T1 - Target 1 (Storage Processor or Storage Controller Port)

L7 - LUN 7 (Logical Unit Number or Disk Unit)

Of these, two of them could be rooted on the VMware stack (HBA/Channel), while the rest of them are external to VMware stack.

Majority of the time, this issue occurs due to some form of miscommunication taking place between the device driver and firmware versions of the PCI devices being used to interact with the storage devices.

Check HBA and NIC driver version and firmware version compatibility. For more information, see Determining Network/Storage firmware and driver version in ESXi and later (1027206).

Note: For naa.60a9800043346534645a433967325334

Network Address Authority Identifier

naa. - The Global Standard abbreviation can be NAA, T10, EUI etc...
6 - Tells us this is IEEE registered extended format 6
0a9800- Hexadecimal IEEE OUI
043346534 - Vendor-specific Identifier
645a433967325334 - Vendor-specific Identifier (extension)

NAA stands for Network Addressing Authority identifier. EUI stands for Extended Unique Identifier. The number is guaranteed to be unique to that LUN. The NAA or EUI identifier is the preferred method of identifying LUNs and the number is generated by the storage device. Since the NAA or EUI is unique to the LUN, if the LUN is presented the same way across all ESXi hosts, the NAA or EUI identifier remains the same. For more information on these standards, see the SPC-3 documentation from the International Committee for Information Technology Standards (T10).

For additional information, see Identifying disks when working with VMware ESXi (1014953).

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.

To investigate the actual failure or to eliminate possible issues

List all the paths for the device by running this command:

esxcfg-mpath -b -d device ID

For example:

esxcfg-mpath -b -d naa.600507680c80852908000000000000b0

vmhba0:C0:T0:L11 LUN:11 state:active fc Adapter: WWNN: 20:00:94:f1:28:be:a1:11 WWPN: 10:00:94:f1:28:be:a1:11  Target: WWNN: 50:05:07:68:0c:00:a4:8c WWPN: 50:05:07:68:0c:57:a4:8c
vmhba0:C0:T1:L11 LUN:11 state:active fc Adapter: WWNN: 20:00:94:f1:28:be:a1:11 WWPN: 10:00:94:f1:28:be:a1:11  Target: WWNN: 50:05:07:68:0c:00:a5:21 WWPN: 50:05:07:68:0c:57:a5:21
vmhba1:C0:T1:L11 LUN:11 state:active fc Adapter: WWNN: 20:00:94:f1:28:be:a1:19 WWPN: 10:00:94:f1:28:be:a1:19  Target: WWNN: 50:05:07:68:0c:00:a5:21 WWPN: 50:05:07:68:0c:58:a5:21
vmhba1:C0:T0:L11 LUN:11 state:dead fc Adapter: Unavailable Target: Unavailable

In this example, you can see that of the four different multipathing options, only one is not active. It is important to understand that the remaining three paths are active and the connectivity to the back end device are not impacted. For more information, see Obtaining LUN pathing information for ESXi hosts (1003973).

Important: A rescan is required after any change is made to see if the targets are detected.

Check that a rescan does not restore visibility to the targets. For more information on rescanning the storage device by using the command-line interface and VMware vSphere Client, see Performing a rescan of the storage on an ESXi host (1003988).

Determine whether the connectivity issue is with the iSCSI storage or the fiber storage. Perform one of these options depending on what your connectivity issue is.

To troubleshoot the connectivity to the iSCSI storage using the software initiator

Check whether a ping to the storage array fails from the ESXi host. For more information, see Testing network connectivity with the ping command (1003486).

Check whether a vmkping to each network portal of the storage array fails. For more information, see Testing VMkernel network connectivity with the vmkping command (1003728).

Check that the initiator is registered on the array. Contact your storage vendor for instructions on this procedure.

Ensure that these physical hardware(s) are correctly functioning:

Ethernet Switch

Ethernet Cables between the ESXi Host and the Switch

Ethernet Cables between the Switch and the Array

To troubleshoot the connectivity to the FC storage

The fiber switch zoning configuration permits the ESX host to see the storage array. Consult your switch vendor if you require assistance.

The fiber switch propagates RSCN messages to the ESXi hosts.

Check the physical hardware, including:

The Storage Processors on the Array

The FC Switch and the Gigabit Interface Converter (GBIC) units in the switch

The FC cables between the Switch and the Array

The Array itself

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)KoreanJapaneseEnglish

Attachments

Additional Resources

No results for undefined

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 8.0

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant