VMware Cloud Community
ass_sie
Contributor
Contributor

Not response on esxcli storage nmp device list commad

Hi,I state that my storage apparently is working correctly and the vm are ok but
When I run this command "esxcli storage nmp device list" I get no response, no errors, simpli return to #
Why?
My Esxi : VMware-VMvisor-Installer-7.0U2a-17867351.x86_64

0 Kudos
13 Replies
depping
Leadership
Leadership

I have the same build, command works fine here... strange.

0 Kudos
ComputingDon
Contributor
Contributor

It sounds like you may have another multipath plugin installed and your storage is using that

I would check the type of storage and if they have their own plugin.  With that they probably have extended the esxcli command space for their product.

0 Kudos
ass_sie
Contributor
Contributor

what command can I \ should I use to show you what you ask for?

0 Kudos
donwant
Contributor
Contributor

You would need to know what Storage Provider that you use so the answer would vary.

If you know what storage product that you have then you could check their documentation or contact them regarding how their product in connected to know what esxcli command would be needed.  

The plugins for a specific brand\model would be either using the 2 native options (NMP or HPP) or a plugin that they developed.

NMP is the Native Multipath Plugin and HPP is the High Performance Plugin.  You could check HPP and if it is not there either then you would need to look at there are different plugins for your storage.

0 Kudos
e_espinel
Virtuoso
Virtuoso

Hello.
If your connection to the Storage is by ISCSI, run the following command, and in the plugin line will be the type of multipath that is using that device

# esxcli storage core path list

List out all the devices being detected by the ESXi host.

# esxcfg-scsidevs -c

 

Enrique Espinel
Senior Technical Support on IBM, Lenovo, Veeam Backup and VMware vSphere.
VSP-SV, VTSP-SV, VTSP-HCI, VTSP
Please mark my comment as Correct Answer or assign Kudos if my answer was helpful to you, Thank you.
Пожалуйста, отметьте мой комментарий как Правильный ответ или поставьте Кудо, если мой ответ был вам полезен, Спасибо.
0 Kudos
ass_sie
Contributor
Contributor

i execute your command :

[root@localhost:~] esxcli storage core path list
sas.52cea7f08ac15700-sas.607089d7192e34b9-naa.62cea7f08ac15700287089d7192e34b9
UID: sas.52cea7f08ac15700-sas.607089d7192e34b9-naa.62cea7f08ac15700287089d7192e34b9
Runtime Name: vmhba0:C2:T0:L0
Device: naa.62cea7f08ac15700287089d7192e34b9
Device Display Name: Local DELL Disk (naa.62cea7f08ac15700287089d7192e34b9)
Adapter: vmhba0
Channel: 2
Target: 0
LUN: 0
Plugin: HPP
State: active
Transport: sas
Adapter Identifier: sas.52cea7f08ac15700
Target Identifier: sas.607089d7192e34b9
Adapter Transport Details: 52cea7f08ac15700
Target Transport Details: 607089d7192e34b9
Maximum IO Size: 262144
[root@localhost:~] esxcfg-scsidevs -c
Device UID Device Type Console Device Size Multipath PluginDisplay Name
naa.62cea7f08ac15700287089d7192e34b9 Direct-Access /vmfs/devices/disks/naa.62cea7f08ac15700287089d7192e34b9 914688MB HPP Local DELL Disk (naa.62cea7f08ac15700287089d7192e34b9)

if execute :

[root@localhost:~] esxcli storage nmp device list
[root@localhost:~]

0 Kudos
ass_sie
Contributor
Contributor

with hpp switch command run;

[root@localhost:~] esxcli storage hpp device list
naa.62cea7f08ac15700287089d7192e34b9
Device Display Name: Local DELL Disk (naa.62cea7f08ac15700287089d7192e34b9)
Path Selection Scheme: FIXED
Path Selection Scheme Config: {preferred=none;}
Current Path: vmhba0:C2:T0:L0
Working Path Set: vmhba0:C2:T0:L0
Is SSD: false
Is Local: true
Paths: vmhba0:C2:T0:L0
Use ANO: false

with esxcli storage nmp path, not...
it seems to be the nmp switch that is not recognized or working

0 Kudos
e_espinel
Virtuoso
Virtuoso

Hello.
According to the result of the executed commands, you have only one local disk connected to the ESXi host with HPP path.
The command "esxcli storage nmp device list" should show the connections with path nmp, you have no devices with path nmp, so the result is an empty prompt return.

 

Enrique Espinel
Senior Technical Support on IBM, Lenovo, Veeam Backup and VMware vSphere.
VSP-SV, VTSP-SV, VTSP-HCI, VTSP
Please mark my comment as Correct Answer or assign Kudos if my answer was helpful to you, Thank you.
Пожалуйста, отметьте мой комментарий как Правильный ответ или поставьте Кудо, если мой ответ был вам полезен, Спасибо.
0 Kudos
ass_sie
Contributor
Contributor

ok but to solve the problem of the Not-SSD display in the storage how do I solve?

0 Kudos
Hizka
Contributor
Contributor

Hi my friend, 

Try this

 

esxcli storage hpp device list

esxcli storage hpp device set -d naa.123youknowthedeviceid -M true

 

and you can check with 

esxcli storage core device list -d naa.123youknowthedeviceid |grep -i ssd

 

 

0 Kudos
jktz83
Contributor
Contributor

 I would like to reactive this thread since I'm having a similar issue.

When I use ESXi 6.7 I'm able to detect all my disks by using the 'esxcli storage nmp device list' command. However when I swap over to 7.0 U3 no devices show up under nmp device list. I'm using a Dell Poweredge R340 with the latest firmware.

Any ideas? Why does it change from 6.7 to 7.0 ? I'm using a PERC H730P with a RAID 10 configuration.

0 Kudos
e_espinel
Virtuoso
Virtuoso

Hello.
It is always advisable to open a new post, as the problem may be similar, but the conditions and environment different.
Please check the driver and the controller firmware
according to the VMware matrix for your version of VMware vSphere.
https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=34852

very few people pay attention to very old and/or solved posts.

 

 

Enrique Espinel
Senior Technical Support on IBM, Lenovo, Veeam Backup and VMware vSphere.
VSP-SV, VTSP-SV, VTSP-HCI, VTSP
Please mark my comment as Correct Answer or assign Kudos if my answer was helpful to you, Thank you.
Пожалуйста, отметьте мой комментарий как Правильный ответ или поставьте Кудо, если мой ответ был вам полезен, Спасибо.
0 Kudos
jktz83
Contributor
Contributor

Thanks for your reply,

 

as far as I can tell it should be supported right?

ESXi 7.0
[root@localhost:~] esxcli storage core adapter list
HBA Name Driver Link State UID Capabilities Description
-------- -------- ---------- -------------------- ------------ -----------
vmhba0 lsi_mr3 link-n/a sas.51866da06192eb00 (0000:02:00.0) Broadcom PERC H730P Adapter

Key Value Instance: lsi_mr3-51866da06192eb00/LSI Incorporation
Listing keys:
Name: MR-DriverVersion
Type: string
value: 7.719.02.00
Name: MR-HBAModel
Type: string
value: MegaRAID 1000:5d:1028:1f42
Name: MR-FWVersion
Type: string
value: Pkg 25.5.9.0001 FW 4.300.00-836
Name: MR-ChipRevision
Type: string
value: Chip Rev. C0
Name: MR-CtrlStatus
Type: string
value: FwState c0000000

ESXi 6.7
[root@localhost:~] esxcli storage core adapter list
HBA Name Driver Link State UID Capabilities Description
-------- -------- ---------- -------------------- ------------ ------------ ------------------------------------------------------
vmhba0 lsi_mr3 link-n/a sas.51866da06192eb00 (0000:02:00. 0) Broadcom PERC H730P Adapter

 

I always thought that ESXi is only able to see the virtual disks which the raid controller provides. Considering I'm using the same raid configuration and drivers I don't see any reason for the difference?

0 Kudos