LUNs are missing after upgrading the hosts to ESXi 6.5

Products

• VMware vSphere ESXi

Issue/Introduction

The purpose of this article is to bring back the LUNs that were present before the upgrade.

Symptoms:

• Upgrading ESXi hosts to 6.5 causes LUN not to be seen.
• In the vmkernel.log you see entries similar to:

2017-03-09T20:38:56.567Z cpu5:65786)ScsiUid: 403: Existing device naa.60060e80101b7280058bb6f80000000f already has uid vml.020001000060060e80101b7280058bb6f80000000f444636303046
2017-03-09T20:38:56.567Z cpu5:65786)ScsiDevice: 4163: Failing registration of device 'naa.60060e80101b7280058bb6f80000000f'
2017-03-09T20:38:56.567Z cpu5:65786)ScsiDevice: 4165: Failed to add legacy uid vml.020001000060060e80101b7280058bb6f80000000f444636303046 on path vmhba4:C0:T2:L1: Already exists
2017-03-09T20:38:56.567Z cpu5:65786)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2017-03-09T20:38:56.567Z cpu5:65786)WARNING: NMP: nmp_RegisterDevice:851: Registration of NMP device with primary uid 'naa.60060e80101b7280058bb6f80000000f' failed. Already exists

Note: The preceding log excerpts are only examples. Date, time and environmental variables may vary depending on your environment.

Environment

VMware vSphere ESXi 6.5

Cause

This issue occurs because the registration of the device fails if it has paths with different LUN IDs.

Resolution

Currently, there is no resolution.

To work around this issue, unpresent and then present the LUN with same LUN ID.

Note: For multipathing to work as expected, VMware recommends that each LUN must present the same LUN ID number to all ESXi hosts. For more information, see the ESXi Fibre Channel SAN Requirements section of the vSphere Storage Guide on page 39.

Additional Information

ホストを ESXi 6.5 にアップデートすると LUN が認識されなくなる
将主机升级到 ESXi 6.5 后 LUN 丢失

Impact/Risks:
Requires Reboot