ComapreLUNNumber set to 1 and not 0

[cmhippy]

VCSA upgraded to 7.0.3

Nimble SW updated to 6.1.1.100

In the process of upgrading ESXi Hosts to 7.0.7 and Storage Connection Manager to 7.0-7.0.2

Remove previous NCM VIBs, restart host, Upgrade and patch ESXi Hosts to 7.0.3, restart host, Install Strorage Connection Manager 7.0.2 via Lifecycle Manager, restarting the Host at least twice.

Verify VIBs and Components. OK

However on certain ESXi Hosts, after all the steps above CompareLUNNumber is set to 1 and not 0. The Nimble VMware Integration Guide states it shoud come up as 0. Other Hosts, even in the same Cluster are correct.

What is going on?

Thanks

[Mahesh202]

Hi cmhippy

If the CompareLUNNumber is set to 1 on certain ESXi Hosts after upgrading to ESXi 7.0.3 and installing the Nimble Connection Manager (NCM), it could indicate an issue with the installation or configuration of the NCM on those hosts.

According to the Nimble VMware Integration Guide, CompareLUNNumber should be set to 0 after installing the NCM on ESXi hosts. This setting ensures that the NCM correctly identifies the LUN numbers assigned by the Nimble array and avoids issues with storage connectivity.

Here are some possible reasons why the CompareLUNNumber is set to 1 on certain ESXi Hosts:

1. Installation or Configuration Issue: There may have been an issue during the installation or configuration of the NCM on those hosts, causing the CompareLUNNumber to be set incorrectly. To address this, you can try uninstalling and reinstalling the NCM on the affected hosts, ensuring that you follow the installation instructions provided by Nimble.
2. Hardware or Firmware Issue: It is possible that the affected hosts have different hardware or firmware versions that are not fully compatible with the NCM. You can check with HPE Nimble Tech support to confirm the hardware and firmware compatibility for the NCM.
3. Network Configuration Issue: Another possible cause of the issue could be network misconfiguration.
For example, if the NCM cannot communicate with the Nimble array due to a network issue, it may not correctly identify the LUN numbers. You can check the network settings on the affected hosts and ensure that they match the recommended settings in the Nimble VMware Integration Guide.

It may also be helpful to compare the settings and configurations of the affected hosts with those of the hosts that are working correctly to identify any differences that may be causing the issue.

If you are unable to resolve the issue, you may contact HPE Nimble Tech support for further assistance.

Hope this helps.!!

Regards
Mahesh.

[cmhippy]

Mahesh202, Thanks!

I'll start by uninstalling and then reinstalling NCM from the affected ESXi Host first and see how that goes.

I will post a reply as soon as I find out.

[Mahesh202]

Hi cmhippy

That's a good first step. Make sure to follow the installation instructions provided by Nimble to ensure that the NCM is installed correctly on the affected ESXi hosts. After reinstalling NCM, verify that the CompareLUNNumber is set to 0 on those hosts.

If the issue persists after reinstalling NCM, you may need to check for other possible causes such as hardware or firmware compatibility or network misconfigurations. Comparing the settings and configurations of the affected hosts with those of the hosts that are working correctly may also help you identify any differences that may be causing the issue.

If you are still unable to resolve the issue, you may contact HPE Nimble Tech support for further assistance.

Hope this helps.!!

Regards
Mahesh.

[Sunitha_Mod]

Hello @cmhippy,

Let us know if you were able to resolve the issue.

If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.