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

My Subscriptions

Loading

Knowledge Base

Tape device incorrectly detected as ALUA device on ESXi/ESX hosts (1026157)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 27111Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

VMware ESX or ESXi hosts incorrectly detect a tape drive device as ALUA.

The tape device is not listed in the output of this command:

ESXi 4.x hosts: esxcli nmp device list

ESXi 5.x hosts: esxcli storage nmp device list

The /var/log/vmkernel or /var/log/messages log contains entries similar to:

cpu2:4114)WARNING: VMW_SATP_ALUA: satp_alua_getTargetPortInfo: Could not find relative target port ID for path "vmhba3:C0:T6:L0" - Not found (195887107)
cpu2:4114)WARNING: NMP: nmp_SatpClaimPath: SATP "VMW_SATP_ALUA" could not add path "vmhba3:C0:T6:L0" for device "Unregistered Device". Error Not found
cpu2:4114)WARNING: NMP: nmp_DeviceAlloc: nmp_AddPathToDevice failed Not found (195887107).
cpu2:4114)WARNING: NMP: nmp_DeviceAlloc: Could not allocate NMP device.

Cause

This issue occurs because a catch-all SATP rule has claimed the device, which has registered it as ALUA.

Resolution

To address this issue, you must add a SATP rule for the specific device.

To add an appropriate rule for the specific device:

Rescan your storage adapters in the vSphere Client, or from the terminal use the command:

esxcfg-rescan vmhbax

Review the rescan logging in your system logs.

ESX hosts: grep "ScsiScan" /var/log/vmkernel

ESXi 4.x hosts: grep "ScsiScan" /var/log/messages

ESXi 5.x hosts: grep "ScsiScan" /var/log/vmkernel.log

Check the output for the tape drive and get the vendor and model for the specific device.

For example:

esx2 vmkernel: 0:00:00:29.585 cpu2:4114)ScsiScan: 1059: Path 'vmhba3:C0:T6:L0': Vendor: 'ACME ' Model: 'UltraStore 6-SCSI ' Rev: 'W22W'

Note: If you do not see the tape device from the above output, run the below command to see the tape device details.

ESX/ESXi 4.x : esxcfg-scsidevs -l
ESXi 5.x: esxcli storage core device list (This lists all the devices connected to the host.)

Add a new rule to claim the device by the VMW_SATP_LOCAL plugin, using the command:

ESX/ESXi 4.x hosts: esxcli nmp satp addrule --satp="VMW_SATP_LOCAL" --vendor="vendor_name" --model="model_name"

ESXi 5.x hosts: esxcli storage nmp satp rule add --satp="VMW_SATP_LOCAL" --vendor="vendor_name" --model="model_name"

For example: The command for the vendor (ACME) and model (UltraStore) seen in the output of Step 2 is:

esxcli storage nmp satp rule add --satp="VMW_SATP_LOCAL" --vendor="ACME" --model="^UltraStore*"

Note: Since the VMW_SATP_LOCAL plugin is being used, only a single path to the device is supported.

Unclaim the location using this command:

ESX/ESXi 4.x hosts: esxcli corestorage claiming unclaim -t location -A vmhba3 -C 0 -T 6 -L 0

ESXi 5.x hosts: esxcli storage core claiming unclaim -t location -A vmhba3 -C 0 -T 6 -L 0

Note: Update vmhba, controller, target, and LUN number as required.

This ensures that all paths to the device are unclaimed successfully before running the claim.

Rescan your storage adapters in the vSphere Client, or from the terminal using the command:

esxcfg-rescan vmhbax

Confirm that the device is claimed by the VMW_SATP_LOCAL SATP plugin and is listed in the output of this command:

ESX/ESXi 4.x hosts: esxcli nmp device list

ESX/ESXi 5.x hosts: esxcli storage nmp device list

Related Information

For more information about running tape devices in ESXi/ESX, see:

Understanding support for tape devices with VMware ESX and VMware ESXi (2007904)

Configuring vendor-supported tape drives and media changers on ESX/ESXi 4.x and later (1016407)

Multipathing policies in ESX/ESXi 4.x and ESXi 5.x (1011340)

Multipathing policies in ESXi 5.x and ESXi/ESX 4.x
Configuring vendor-supported tape drives and media changers on VMware ESX/ESXi 4.x/5.x
Understanding support for tape devices with VMware ESXi and VMware ESX
ESXi/ESX ホストでテープ デバイスが間違って ALUA デバイスとして検出される

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

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

KB
•
スナップショットを作成できない：すでにファイルが存在するために操作が失敗するか、ファイルまたはフォルダ [DatastoreName] VMname/VMname.vmx がすでに存在するために操作を実行できない (1008058)

KB
•
Broadcom bnx2x ドライバ バージョン 1.60.50.v41.2 が使用されている VMware ESX/ESXi 4.1 ホストで、バーチャル コネクトを含む HP Blade 上のネットワーク接続が断続的に失われる (1031805)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
VMware ESX 4.x および VMware ESXi 4.x での負荷に基づいたチーミング (1022590)

Results 1-5 of 6

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESX 4.1.x

Take Our Survey

Support Assistant