Pvajdic
Enthusiast
Enthusiast

Preferred path not available Update 3

Jump to solution

Hi all,

Since I updated some of my ESXi hosts to 6.0 Update 3 I'm unable to change Preferred path for my LUNs.It still works on all hosts which are on Update 2 I've also update vCenter server to U3. Anyone else noticed this issue?

PS: Another thing I noticed today, I don't see VM name under Target when automatic DRS migration occurs. For some VM I can see it but mostly this field is empty.

Regards,

Petar.

0 Kudos
1 Solution

Accepted Solutions
erikverbruggen
Hot Shot
Hot Shot

There is a bug in ESXi 6.0 U3, which causes active path information to be missing. It could be that you are hitting the same bug.

Currently there is no work around, Active path information (I/O) missing after update to 6.0 Update 3 (2149992) | VMware KB

View solution in original post

11 Replies
millerj524
Contributor
Contributor

Also having the same issue not being able to select a Preferred path with 6.0 Update 3. We have no issues on our 5.5 hosts but after upgrading it says applying storage policy but never shows Active I/O * for the path we select.

We have Dell Compellent Sans With Vcenter 6.0 U3b.

Thanks

Jon

0 Kudos
erikverbruggen
Hot Shot
Hot Shot

There is a bug in ESXi 6.0 U3, which causes active path information to be missing. It could be that you are hitting the same bug.

Currently there is no work around, Active path information (I/O) missing after update to 6.0 Update 3 (2149992) | VMware KB

Pvajdic
Enthusiast
Enthusiast

Thank you for reply.

0 Kudos
millerj524
Contributor
Contributor

Yes! Thank you for the reply. Felt like VMWare knew nothing of the issue. Hopefully it will be patched asap.

0 Kudos
Petter_Lindgren
Contributor
Contributor

However, the kb article says that it is a cosmetic bug only but that's not true for us.

We have tried to set a preffered path both via the client and cli but the vmware host just ignores it.

We've just logged a case with vmware about this but we need it fixed ASAP!

0 Kudos
Petter_Lindgren
Contributor
Contributor

The KB is wrong!

This is not a cosmetic issue! We are not able to set the preferred patch from the client, webclient or even PowerCLI!

We've created an SR (17504104407) but get no response from vmware other than it will be patched in the future.

We need this fixed ASAP!

0 Kudos
Dongjianhua
Enthusiast
Enthusiast

Hello experts,

I have the same issue, we are using VPLEX metro cross-link, and want to select the perfered path.

Is there a solution currently ?

0 Kudos
Dongjianhua
Enthusiast
Enthusiast

Has anyone resolved this issue ?

0 Kudos
Dongjianhua
Enthusiast
Enthusiast

??????

0 Kudos
Dongjianhua
Enthusiast
Enthusiast

??????

0 Kudos
mentat1
Contributor
Contributor

Hi,

we have also have this problem.

The only workaround for us is, to use escli direct at the host. If the Pathpolicy is already VMW_PSP_FIXED

then for example

esxcli storage nmp psp fixed deviceconfig set --path vmhba2:C0:T1:L36 --device naa.60050768018086cd600000000000003b

will set the preferred path

This will check the result of the command:

esxcli storage nmp device list -d naa.60050768018086cd600000000000003b

yours

0 Kudos