Proxmox iSCSI login works but LUN not visible when using Nimble group target

[fettmasta]

Hello,

I am setting up a Proxmox host to connect to an HPE Nimble SAN over iSCSI and running into an issue where the host logs in successfully but no LUNs appear.

The host has two dedicated iSCSI interfaces on separate networks. Both can reach the SAN and discovery works correctly.

When I run discovery, two types of targets appear:

• The Nimble group/array target
• A volume-specific target for the LUN I created

If I log in to the group target, the sessions establish successfully across all controller interfaces. However, the host does not see any disks.

Example:

iscsiadm -m session
returns multiple sessions, but:

lsblk
shows no new disks.

Also:

iscsiadm -m session -P 3
shows no attached SCSI devices.

However, if I log in to the volume-specific IQN, the LUN appears immediately and the disk is visible on the host.

The volume is mapped to the host's initiator group and access is set to read/write. CHAP authentication is working and the login itself succeeds.

My questions:

1. Is it expected that Linux/Proxmox only sees the LUN when connecting to the volume IQN instead of the group target?
2. Should Proxmox be configured to use the volume target instead?
3. Is there a Nimble configuration that controls whether volumes appear under the group target?

We have this configured already in our lab and working properly, the only different is we have one iscsi interface on the node and one discovery network on the SAN, in this new setup, I have two iscsi interfaces on the Proxmox node and two discovery IPs on the HPE SAN, both of which display the group and LUN IQN when adding into Proxmox.

Any insight would be appreciated.

 

[bbgeek17]

Hi @fettmasta .

It sounds like you are using iscsiadm to establish the connection. Please keep in mind that there is nothing specific to PVE in the operations you are performing. PVE runs on a Debian userland with a Proxmox-maintained Linux kernel, and the iSCSI stack itself is a standard Linux package.

If the LUN does not appear after connecting to a target, that usually means the LUN is not mapped to that target on the storage side. The Linux host (PVE) has no awareness that one target might be IQN-specific while another is a group target; it simply connects to the target and reports whatever LUNs are presented.

If, in your environment, the group target is expected to present a LUN, my guess would be that the storage configuration is not set up correctly.

I’m not familiar enough with HPE Nimble Storage to comment on the Nimble-specific behavior. Their support team may be able to provide more precise guidance.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox