SCSI devices not visible on initiator client

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create file system on ESOS Host (LSI target HBA (9211-8i))
2. Add virtual disk file on new file system 
3. Create a security group
4. Add infiniband initiator to newly created security group
5. Add a vdisk_fileio device associated to virtual disk file created earlier.
6. Map the newly created device to the newly created group/initiator
7. Enable the infiniband target on the ESOS host (ib_srpt driver)
8. Enable initiator on client to connect to ESOS target.
9. Verify the initiator has connected to target by running scstadmin 
-list_sessions
10.  Run either fdisk -l or lsscsi on initiator client to view new scsi device

What is the expected output? What do you see instead?
To see the new scsi device on the client initiator host, but no device can be 
found.  No errors on the client side in the /var/log/messages file.

What version of the product are you using? On what operating system?
Enterprise Storage OS 0.1-r564M (rebuilt version that I added NVIDIA Ethernet 
driver support to).  Oracle Enterprise Linux 6.4

Please provide any additional information below.
Using Mellanox ConnectX VPI cards in both machines.  MHGH28-XTC.
Client initiator is using OFED 3.5-1 driver.

Original issue reported on code.google.com by skeller...@gmail.com on 13 Jan 2014 at 8:08

Attachments:

• esos_support_pkg-1389640490.tgz

[GoogleCodeExporter]

I see this in your kern.log file:
--snip--
Jan 13 13:11:08 infininas1 kernel: [ 1535.789892] [3387]: scst: 
scst_init_session:6658:Using security group 
"fe80:0000:0000:0000:0002:c903:0000:c47d" for initiator 
"fe80:0000:0000:0000:0002:c903:0000:cef5" (target 
fe80:0000:0000:0000:0002:c903:0000:c47d)
Jan 13 13:11:15 infininas1 kernel: [ 1543.565085] [3387]: scst: 
scst_init_session:6658:Using security group 
"fe80:0000:0000:0000:0002:c903:0000:c47e" for initiator 
"fe80:0000:0000:0000:0002:c903:0000:cef6" (target 
fe80:0000:0000:0000:0002:c903:0000:c47e)
--snip--

So, I think your initiator names are wrong for your security groups... the 
message above says its using a default security group (the target name). I see 
you have these set for your initiators in /etc/scst.conf:
INITIATOR 0000:0000:0000:0000:0002:c903:0000:cef5
INITIATOR 0000:0000:0000:0000:0002:c903:0000:cef6

Change those lines to these:
INITIATOR fe80:0000:0000:0000:0002:c903:0000:cef5
INITIATOR fe80:0000:0000:0000:0002:c903:0000:cef6

In your /etc/scst.conf and run 'scstadmin -config /etc/scst.conf' and see what 
happens.

--Marc

Original comment by msmith...@gmail.com on 14 Jan 2014 at 2:01

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Original comment by msmith...@gmail.com on 14 Jan 2014 at 2:01

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

That did it.  Strange, when I attempted to connect the initiator to both 
targets on ESOS, the /var/log/messages log on ESOS shows:
INITIATOR 0000:0000:0000:0000:0002:c903:0000:cef5
INITIATOR 0000:0000:0000:0000:0002:c903:0000:cef6
which is why they were added to the groups.  From what I can tell you only see 
that it needs "fe80" after setting it up and attempting to login to the target 
once again.  Would this be considered some sort of bug?  

And, many thanks for your help.  I did not notice that small change in the 
logs. 

Original comment by skeller...@gmail.com on 14 Jan 2014 at 5:20

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Good to hear that fixed it.

I'm not sure exactly why its like that with the IB/SRP driver, but I've seen 
other users in the scst-devel list (or somewhere else on the web) mention 
something similar. I don't know what those first 2 bytes represent -- perhaps a 
port ID? I'm not real familiar with the InfiniBand stuff, so if it bugs you, it 
may be worth while checking out the scst-devel list. =)

--Marc

Original comment by msmith...@gmail.com on 14 Jan 2014 at 6:33

• Changed state: Invalid
• Added labels: ****
• Removed labels: ****