esos prod_id and t10_vend_id

[Brent Bolin]

Hello All,

Previously I had compiled SCST on ubuntu.  So my scst.conf was all hand created via scstadmin command line.

Below was a typical setup for devices -

HANDLER vdisk_blockio {

DEVICE ID_100 {

filename /dev/vol01/ID_100

prod_id OPEN-V

prod_rev_lvl 7002

t10_vend_id HITACHI

}

I've got a dual port qlogic that I've been using as the target.  Had duplicate devices under each target.  This is a point to point connection between target and initiator.

I'm trying to simulate multipathing between SCST and a Solaris LDOM

The above configuration worked fine for multipathing.  

Using esos it doesn't -

HANDLER vdisk_blockio {

        DEVICE 0 {

                filename /dev/mapper/vg-0

                # Non-key attributes

                blocksize 512

                nv_cache 0

                pr_file_name /var/lib/scst/pr/0

                prod_id 0

                prod_rev_lvl " 302"

                read_only 0

                removable 0

                rotational 1

                t10_dev_id 404e1283-0

                t10_vend_id SCST_BIO

                thin_provisioned 0

                threads_num 1

                threads_pool_type per_initiator

                tst 1

                usn 404e1283

                vend_specific_id 404e1283-0

                write_through 0

        }

prod_id seems to pick up the device name.  Is there some way to hard code this value?

 

[Brent Bolin]

Never mind just realized I can put any value I want when mapping

DEVICE this_name {                     

                filename /dev/mapper/vg-4      

                                               

                # Non-key attributes           

                blocksize 512                  

                nv_cache 0                     

                pr_file_name /var/lib/scst/pr/this_name

                prod_id this_name                      

                prod_rev_lvl " 302"                    

                read_only 0                            

                removable 0                            

                rotational 1                           

                t10_dev_id 796088f9-this_name          

                t10_vend_id SCST_BIO                   

                thin_provisioned 0                     

                threads_num 1                          

                threads_pool_type per_initiator        

                tst 1                                  

                usn 796088f9                           

                vend_specific_id 796088f9-this_name    

                write_through 0                        

[Brent Bolin]

This still turned out to be problem for esos_tui because you can't have dups.

[Marc Smith]

Hi Brent,

I'm not sure I follow... you can't have duplicate SCST devices?


--Marc

> --
> You received this message because you are subscribed to the Google Groups
> "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Brent Bolin]

/usr/local/bin/esos_tui the menu doesn't allow it.

For what I'm using esos for SAN for Sun LDOM needs specific identifiers for multipathing to work

Example:

HANDLER vdisk_blockio {

        DEVICE 0 {

                filename /dev/vg/0

                prod_id OPEN-V

                prod_rev_lvl 7002

                t10_vend_id HITACHI

Here is an example from esos_tui

HANDLER vdisk_blockio {

        DEVICE 0 {

                filename /dev/mapper/vg-0

                # Non-key attributes

                blocksize 512

                nv_cache 0

                pr_file_name /var/lib/scst/pr/0

                prod_id 0

                prod_rev_lvl " 302"

                read_only 0

                removable 0

                rotational 1

                t10_dev_id 404e1283-0

                t10_vend_id SCST_BIO

                thin_provisioned 0

                threads_num 1

                threads_pool_type per_initiator

                tst 1

                usn 404e1283

                vend_specific_id 404e1283-0

                write_through 0

        }

}

Below are key fields I need to make multipathing work on Solaris

prod_id OPEN-V

t10_vend_id HITACHI

I could edit /etc/driver/drv/scsi_vhci.conf for t10_vend_id SCST_BIO but prod_id 0 is a show stopper.

echo|format sees them the inquiry command.  I've only used the key identifiers from some of the supported SAN storage EMC, Hitachi, SUN etc...  But without some kind of identifier when multipathing is enabled it doesn't work.

So unless you know of a work around I can't use the menu.  Really wanted to use it to help myself learn some of the other functions of SCST grouping and alua specifically.

All is not lost.  Still going to use the usb.  Much tighter and better configed them my ubuntu server with SCST compiled etc... .  Edited /etc/profile for direct shell access and some other things.

[Marc Smith]

Hi,

Its not the ESOS TUI that doesn't allow duplicate SCST device names,
it's SCST itself: You can't add two devices with the same device name,
using the same handler. What you're referring to is an attribute for
an SCST device -- the "prod_id" attribute which by default the value
is set to the SCST device name, but its not required they be the same.
So, you could still use the TUI to create the devices, then just
adjust the "prod_id" attribute value after on the CLI:
echo "OPEN-V" > /sys/kernel/scst_tgt/handlers/vdisk_blockio/bio_6ssd_r0/prod_id
conf_sync.sh

Where "bio_6ssd_r0" is the name of the SCST device. Then you can check
the value in /etc/scst.conf the confirm it changed.

There are many TUI enhancements being developed currently, and we plan
to add additional functionality for setting the SCST attributes (for
devices, targets, etc.) using the TUI.


--Marc

[Brent Bolin]

I've attached an scst.conf config to this post.  Works fine lasts a long time.  You can clearly see it has two targets and duplicate mapped luns

My target has dual port Qlogic. adapter (2462 or something don't remember)

02:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 02)

02:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 02)

The solaris box has two single channel Emulex hba's

Marc, I don't claim to be an expert with SAN storage.  I'm a Unix admin solaris, linux, aix and hp-ux

[Marc Smith]

Yes, you can definitely map the same SCST device to multiple LUNs/targets using the TUI (or command line).

--Marc