iSCSI connections to SAN

John Allison

Member
Feb 1, 2018
32
3
13
Gateshead UK
www.adlinktech.com
Hi,
I have a number of proxmox hosts, and some connected to a Dell/EMC SAN.
On most of the connected hosts i have added an iSCSI connection to the san and then either used the luns directly or added an LVM volume on top.However i'm trying to set up a new host now, and i can add the iSCSI connection, but i cannot use the luns directory nor can i create an LVM volume.
If i try to create a VM and use a lun directly i select the san connection in the storage field, but then the disk image field is empty. If i try to create an LVM volume i can select the san connection but the base volume field is empty so i cannot select anything.
On my other hosts neither field is empty, and i can see the luns assigned to that host.
I believe i followed the same steps as i always do, but perhaps i missed something, or has something changed in the current version of proxmox which might affect the process for setting this up?

Thanks
 
I believe i followed the same steps as i always do, but perhaps i missed something, or has something changed in the current version of proxmox which might affect the process for setting this up?

Normally no, can you inspect the SAN if the node is logged in? Do you use the internal iSCSI connection in the PVE GUI or the CLI to setup iSCSI? If you use the CLI, you can also look there if you logged in and if not get error messages.
 
Yes, all logged in and from the CLI everything looks good. From Proxmox, I can establish the iSCSI connection fine. Proxmox just doesnt see the LUNS. No error messages.


root@pvhost5:~# iscsiadm -m node --targetname "iqn.1984-05.com.dell:powervault.md3800i.600a098000584f5c00000000539b3d49" --portal "192.168.130.101:3260" --login
Logging in to [iface: default, target: iqn.1984-05.com.dell:powervault.md3800i.600a098000584f5c00000000539b3d49, portal: 192.168.130.101,3260] (multiple)
Login to [iface: default, target: iqn.1984-05.com.dell:powervault.md3800i.600a098000584f5c00000000539b3d49, portal: 192.168.130.101,3260] successful.


Ive been using the GUI to setup the iSCSI.
 

Attachments

  • Capture12.GIF
    Capture12.GIF
    35.5 KB · Views: 21
  • Capture12.GIF
    Capture12.GIF
    19.9 KB · Views: 20
Ive been using the GUI to setup the iSCSI.

I think that that is the "problem". AFAIK, the GUI does its own setup, so if you create the LVM manually on the multipathed device, you should see the LVM from PVE - or logout from the CLI and do everything from the GUI. If your iSCSI server is not configured for multiple login, it could be the problem you see.
 
Ive tried using the CLI but still getting the same results, Im assuming the iSCIS SAN must be configured for multiple logins, as none of the other proxmox boxes have problems, and the luns were all created in the same way.

On the other servers I can select the iSCSI storage config in proxmox GUI and i can see the LUNs (see attached) but nothing on this box.

Its as though proxmox just cannot see the luns, but i cannot see why. As you can see from the sample outputs below, its logged in and the luns are there.
From the command line I can use the lun to create a disk, and then build vm’s on top, but the direct iscsi connection option just isnt working?

Thanks for responding and trying to help me btw :)

root@pvhost5:~# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 02 Id: 00 Lun: 00
Vendor: DELL Model: PERC H710 Rev: 3.13
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi0 Channel: 02 Id: 01 Lun: 00
Vendor: DELL Model: PERC H710 Rev: 3.13
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi5 Channel: 00 Id: 00 Lun: 00
Vendor: HL-DT-ST Model: DVD+-RW GU90N Rev: A300
Type: CD-ROM ANSI SCSI revision: 05
Host: scsi7 Channel: 00 Id: 00 Lun: 00
Vendor: DELL Model: MD38xxi Rev: 0810
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi8 Channel: 00 Id: 00 Lun: 00
Vendor: DELL Model: MD38xxi Rev: 0810
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi9 Channel: 00 Id: 00 Lun: 00
Vendor: DELL Model: MD38xxi Rev: 0810
Type: Direct-Access ANSI SCSI revision: 05

Host: scsi7 Channel: 00 Id: 00 Lun: 31
Vendor: DELL Model: Universal Xport Rev: 0810
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi8 Channel: 00 Id: 00 Lun: 31
Vendor: DELL Model: Universal Xport Rev: 0810
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi9 Channel: 00 Id: 00 Lun: 31
Vendor: DELL Model: Universal Xport Rev: 0810
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi10 Channel: 00 Id: 00 Lun: 00
Vendor: DELL Model: MD38xxi Rev: 0810
Type: Direct-Access ANSI SCSI revision: 05

Host: scsi10 Channel: 00 Id: 00 Lun: 31
Vendor: DELL Model: Universal Xport Rev: 0810
Type: Direct-Access ANSI SCSI revision: 05






root@pvhost5:~# iscsiadm -m session -P 3
iSCSI Transport Class version 2.0-870
version 2.0-874
Target: iqn.1984-05.com.dell:powervault.md3800i.600a098000584f5c00000000539b3d49 (non-flash)
Current Portal: 192.168.131.102:3260,2
Persistent Portal: 192.168.131.102:3260,2
**********
Interface:
**********
Iface Name: default
Iface Transport: tcp
Iface Initiatorname: iqn.1993-08.org.debian:01:d33a9c83e13
Iface IPaddress: 192.168.131.19
Iface HWaddress: <empty>
Iface Netdev: <empty>
SID: 1
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE
*********
Timeouts:
*********
Recovery Timeout: 5
Target Reset Timeout: 30
LUN Reset Timeout: 30
Abort Timeout: 15
*****
CHAP:
*****
username: <empty>
password: ********
username_in: <empty>
password_in: ********
************************
Negotiated iSCSI params:
************************
HeaderDigest: None
DataDigest: None
MaxRecvDataSegmentLength: 262144
MaxXmitDataSegmentLength: 262144
FirstBurstLength: 8192
MaxBurstLength: 1048576
ImmediateData: Yes
InitialR2T: Yes
MaxOutstandingR2T: 1
************************
Attached SCSI devices:
************************
Host Number: 7 State: running
scsi7 Channel 00 Id 0 Lun: 0
Attached scsi disk sdc State: running
scsi7 Channel 00 Id 0 Lun: 31




root@pvhost5:~# ls /dev/disk/by-path/
ip-192.168.130.101:3260-iscsi-iqn.1984-05.com.dell:powervault.md3800i.600a098000584f5c00000000539b3d49-lun-0 pci-0000:02:00.0-scsi-0:2:0:0-part1
ip-192.168.130.102:3260-iscsi-iqn.1984-05.com.dell:powervault.md3800i.600a098000584f5c00000000539b3d49-lun-0 pci-0000:02:00.0-scsi-0:2:1:0
ip-192.168.131.101:3260-iscsi-iqn.1984-05.com.dell:powervault.md3800i.600a098000584f5c00000000539b3d49-lun-0 pci-0000:02:00.0-scsi-0:2:1:0-part1
ip-192.168.131.102:3260-iscsi-iqn.1984-05.com.dell:powervault.md3800i.600a098000584f5c00000000539b3d49-lun-0 pci-0000:02:00.0-scsi-0:2:1:0-part2
pci-0000:00:1f.2-ata-5 pci-0000:02:00.0-scsi-0:2:1:0-part3
pci-0000:02:00.0-scsi-0:2:0:0
 

Attachments

  • Capture12.GIF
    Capture12.GIF
    23.1 KB · Views: 13

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!