Shared Iscsi LVM not showing up on new nodes

[mdevilz]

[ANSWERED] Shared Iscsi LVM not showing up on new nodes

Hi,

I am using the following:

pve-manager: 2.0-38 (pve-manager/2.0/af81df02)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 2.0-60
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-1
pve-cluster: 1.0-23
qemu-server: 2.0-25
pve-firmware: 1.0-15
libpve-common-perl: 1.0-17
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-12
vncterm: 1.0-2
vzctl: 3.0.30-2pve1
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-5
ksm-control-daemon: 1.1-1

I have an iscsi mounted lvm's

dir: local
        path /var/lib/vz
        content images,iso,vztmpl,backup,rootdir


iscsi: libnas
        portal 192.168.0.235
        target iqn.2004-04.com.qnap:ts-879u:iscsi.proxmox.cae650
        content none


lvm: ilsservices
        vgname ilsservices
        base libnas:0.0.0.scsi-36001405feaa9279df114d48fbdbac9d7
        shared
        content images


lvm: digitalcollections
        vgname digitalcollections
        base libnas:0.0.1.scsi-36001405ad87c1cbdb526d4f31d955dda
        shared
        content images


lvm: alltherest
        vgname alltherest
        base libnas:0.0.2.scsi-36001405cedf87c1d52f5d4aeed9fbfd4
        shared
        content images


dir: drobo
        path /mnt/drobo
        content backup
        nodes novaprospekt

Any idea why when I added a new node, I cannot use these shared volumes on the node?

Thanks!

 

[Ninjix]

Did you confirm your iSCSI target has ACL setup to allow those nodes access to the same LUN?

 

[mdevilz]

I currently do not have any ACL's for these luns.

 

[Ninjix]

Can you connect manually from the other nodes? What do you see when you run a iSCSI discovery from problem node against the target?

iscsiadm -m discovery -t sendtargets -p <target ip>

iscsiadm -m node

 

[mdevilz]

Got it working. When that failed it got me to realize that the firewall was actually blocking it.

Thanks!