Menu

#35 Compatibility with oVirt/RHEV

2.0
open
None
2020-03-22
2020-03-15
Paul Fx
No

Hi Bart,

We have been working well with SCST connected to Oracle VM XEN environment for a number of months now, unfortunately we are unable to connect our oVirt/RHEV environment, yet our HP P2000 G3 & IBM v7000 G1 has no issues connect to oVirt/RHEV enironment.

Do you think this is an oVirt driver issue or SCST not supplying a compatibale config to oVirt?

Cheers

Discussion

  • Bart Van Assche

    Bart Van Assche - 2020-03-16

    Please provide more information. Is SCST running inside an oVirt virtual
    machine? Are you using the iSCSI protocol? If so, has it been verified
    with Wireshark or tcpdump that this really is oVirt related and that
    this is not caused by e.g. firewall configuration?

     
  • Paul Fx

    Paul Fx - 2020-03-22

    Hi Bart,

    Sorry for delay replying, just trying to drill in deeper to the issue.

    oVirt version 3.4.8
    SCST version 3.3.x
    Redhat 7.5
    FC connections only.

    lsmod | grep qla
    qla2x00tgt 81582 0
    scst 2399203 2 qla2x00tgt,scst_vdisk
    qla2xxx_scst 442687 1 qla2x00tgt
    scsi_transport_fc 64007 1 qla2xxx_scst

    lsmod | grep scst
    scst_vdisk 109407 0
    scst 2399203 2 qla2x00tgt,scst_vdisk
    dlm 169891 1 scst
    libcrc32c 12644 4 xfs,nf_nat,scst_vdisk,nf_conntrack
    crc_t10dif 12912 2 scst,sd_mod
    qla2xxx_scst 442687 1 qla2x00tgt
    scsi_transport_fc 64007 1 qla2xxx_scst

    HANDLER vdisk_blockio {
    DEVICE lun0 {
    filename /dev/zvol/apsan2p1/zvol1
    nv_cache 1
    }
    DEVICE lun1 {
    filename /dev/zvol/apsan2p2/zvol1
    nv_cache 1
    }
    }

    TARGET_DRIVER qla2x00t {
    TARGET 21:01:00:1b:32:bd:cf:8d {
    enabled 1
    GROUP ovs {
    LUN 0 lun0
    LUN 1 lun1
    INITIATOR 21:00:00:24:ff:88:94:e9
    INITIATOR 21:00:00:24:ff:2f:aa:6b
    }
    }

    TARGET 21:01:00:1b:32:bd:2a:8c {
        enabled 1
        GROUP ovs {
                LUN 0 lun0
                 LUN 1 lun1
                INITIATOR 21:00:00:24:ff:88:94:e8
                INITIATOR 21:00:00:24:ff:2f:aa:6a
        }
    }
    

    }

    We rebuilt 2 x Redhat 7.5 and 2 x oVirt 3.4.8 hosts, the issue seems to be trying to connect 2 independent head units to same oVirt farm via SCST, the host are getting confused with lun id's, no matter what we do within scst.conf's there is no joy having multiple SCST supplied FC SAN connections to single oVirt Farm, were as this wasn't an issue with Oracle VM Manager (xen based). As we notice within oVirt that lun's were showing 4 paths each instead of 2.

    Am I doing the wrong setup?
    We tried changing 2nd units to lun3 & lun4 but this didn't work...
    Is there a possible solution?

    Cheers

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.