LUN IDs are different than original LUN IDs and multiple paths to the same LUN have different LUN IDs

You are here:
  • Main
  • Troubleshooting
  • LUN IDs are different than original LUN IDs and multiple paths to the same LUN have different LUN IDs
< All Topics

When VirtuCache is installed, the LUN IDs that you see in VMware are different from the LUN IDs assigned by the storage appliance to that same LUN. This is not a problem.

VMware shows different LUN IDs than the Storage Appliance ID when VirtuCache is installed
VMware shows different LUN IDs than the Storage Appliance LUN ID when VirtuCache is installed.

 

Related to this is the fact that a LUN (device in VMware) can be presented to VMware using different LUN IDs on different paths. Though VMware doesn’t typically support this except when software like ours uses a custom PSP to claim the LUN.

Below is an example of this scenario, where vmhba35 is the VirtuCache pseudo adapter and the remaining vmhbaX are adapters in the host. L2 is the LUN ID of the LUN associated with the device and L3 is the LUN ID assigned to VirtuCache pseudo adapter.  As you can see the LUN IDs on different paths to the same device (LUN) are different. This is not a problem either if VirtuCache is installed. Also note that as stated in the earlier paragraphs, L2 might not be the LUN ID assigned by the storage appliance to the LUN on the appliance, and again this is not a problem.

naa.600140546f5f3f0ctf388fa4969tc6at
vmhba3: C0: T1: L2
vmhba4: C0: T1: L2
vmhba5: C0: T1: L2
vmhba2: C0: T1: L2
vmhba35: C0: T0: L3
vmhba5: C0: T0: L2
vmhba2: C0: T0: L2
vmhba3: C0: T0: L2
vmhba4: C0: T0: L2

Table of Contents
Download Trial Contact Us