VMware Cloud Community
PocketSam
Contributor
Contributor
Jump to solution

Can't get host nvmeQualifiedName through vCenter

Hi. I've stumbled with a problem I can't get Host nvmeQualifiedName through VC. And this value is used in our tests so it is important.

Connect-VIServer vchostname.local
$vmhost = get-vmhost esxi1
$vmhost.ExtensionData.Hardware.SystemInfo.QualifiedName
<no result>

If I do the same with ESXi host directly I get the data

Connect-VIServer esxi1
$vmhost = get-vmhost
$vmhost.ExtensionData.Hardware.SystemInfo.QualifiedName
Value Type
----- ----
nqn.2014-08.local.site:nvme:esxi1 nvmeQualifiedName

 

In the past it definitely worked, but looks like one of the VC updates broke something.

Any ideas I can try to do to solve this issue?

Thanks!

VC Version: 7.0.3.01600
VC Build number: 21958406

ESXi ESXi-7.0U3n-21930508-standard

Time synced through NTP.

Tried Reconnecting ESXi host.

Reply
0 Kudos
1 Solution

Accepted Solutions
fannol
Enthusiast
Enthusiast
Jump to solution

Try something like this:

 

Get-VMHost | select Name,@{n='NQN';e={(Get-EsxCli -V2 -VMHost $_.Name).nvme.info.get.Invoke().HostNQN}}

 

 

For each host, return the hostname + the Host NQN using esxcli (it is like connecting to each host via ssh)

Blog: PowerCli.net

View solution in original post

Tags (1)
2 Replies
fannol
Enthusiast
Enthusiast
Jump to solution

Try something like this:

 

Get-VMHost | select Name,@{n='NQN';e={(Get-EsxCli -V2 -VMHost $_.Name).nvme.info.get.Invoke().HostNQN}}

 

 

For each host, return the hostname + the Host NQN using esxcli (it is like connecting to each host via ssh)

Blog: PowerCli.net
Tags (1)
PocketSam
Contributor
Contributor
Jump to solution

Thanks for the neat workaround, fannol!

Tags (1)
Reply
0 Kudos