VMware Cloud Community
cmutchle
Enthusiast
Enthusiast
Jump to solution

iSCSI target configuration and data stores in VMware 5.5U1

I am working inside of my home lab where I have setup a CentOS 6.5 box to serve as an iSCSI target. The current configuration shows:

[root@localhost ~]# tgtadm --lld iscsi --op show --mode target

Target 1: iqn.2012-10.net.cpd:san.target01

    System information:

        Driver: iscsi

        State: ready

    I_T nexus information:

    LUN information:

        LUN: 0

            Type: controller

            SCSI ID: IET     00010000

            SCSI SN: beaf10

            Size: 0 MB, Block size: 1

            Online: Yes

            Removable media: No

            Prevent removal: No

            Readonly: No

            Backing store type: null

            Backing store path: None

            Backing store flags:

        LUN: 1

            Type: disk

            SCSI ID: IET     00010001

            SCSI SN: beaf11

            Size: 268435 MB, Block size: 512

            Online: Yes

            Removable media: No

            Prevent removal: No

            Readonly: No

            Backing store type: rdwr

            Backing store path: /dev/sdc

            Backing store flags:

    Account information:

    ACL information:

        192.168.1.200

        192.168.1.201

Initially, I had only a single device defined inside iqn.2012-10.net.cpd:san.target01 and I was able to create a datastore on the ESXi hosts that I have running in my lab. I then added a second disk (LUN 1 above), however I still only show the ability to have the original datastore. When I look at the 'Storage Adapters' on either host, the details the iSCSI software adapter show 1 connected target, 2 devices and 2 paths. Shouldn't I be able to mount LUN 1 as a second datastore within the host?

I don't use iSCSI anywhere in production and am only messing with it so that I can familiarize myself with the iSCSI portion for the VCP5-DCV test. Any help would be greatly appreciated. Thanks.

Tags (3)
Reply
0 Kudos
1 Solution

Accepted Solutions
cmutchle
Enthusiast
Enthusiast
Jump to solution

Turned out to be an issue with tgtd. I actually had to reboot the server to get the exports to properly work -- the normal 'service tgtd restart' command was leaving some sort of artifacts around that was preventing VMware from seeing the changes properly.

View solution in original post

Reply
0 Kudos
2 Replies
cmutchle
Enthusiast
Enthusiast
Jump to solution

Turned out to be an issue with tgtd. I actually had to reboot the server to get the exports to properly work -- the normal 'service tgtd restart' command was leaving some sort of artifacts around that was preventing VMware from seeing the changes properly.

Reply
0 Kudos
alfanux2
Contributor
Contributor
Jump to solution

Hi.

The problem is related with two parameters

scsi_id

scsi_sn

Each Lun must to have diferent ids in order to vsphere can differentiate each lun. Remember that you can create those serial and ids based on your own criteria

Anderson Alfaro (Alfanux)

Reply
0 Kudos