HBA Drivers - EMLXS vs LPFC

[GregE]

Not a TSM-specific question, but related to tape.

Anyone using the EMLXS instead of the LPFC?

A pilot IBM XIV is being setup at my site and requires using the EMLXS driver. Works fine connecting to XIV, but not to IBM tape drives using IBMtape driver.

Anyone successfully using IBMtape driver with EMLXS hba driver?

Is this information valid??? I don't like what I see!!! (bottom of the link)

Solaris 10 and IBMTape with TSM

TSM (Tivoli Storage Manager) requires you to use the IBMtape driver and not the native Solaris ST driver to speak to your tapes. If you are using QLC cards, this won’t work. You need to install a QLA or a good old Emulex card. You also need to use LPFC and not the emlxs driver. [WRONG, if anyone is using this post for info] So:

*
Install the 6.02h LPFC driver from Emulex for the card. http://www-dl.emulex.com/support/solaris/602h/emulex.html
*
Install the EMLXemlxu package.
*
Run /opt/EMLXemlxu/bin/emlxdrv and change the driver for your card to be lpfc and not emlxs.
*
Install IBMtape.
*
Configure /usr/kernel/srv/IBMtape.conf - this is well documented and pretty straight forward.
*
Configure /kernel/drv/st.conf so that the Solaris ST driver won’t take over any of the tapes in question.
*
Reboot to activate the LPFC driver.
*
IBMtape tape drives should be visible in /dev/rmt

 

[Mikey D]

Greg,
Before I left my other company we used the Emlxs Driver with IBM tape just fine. It actually seems to be a better choice now of days that LPFC and bit easier to configure.

We we're using it for an EMC VTL emulation IBM LTO tape drives.

 

[GregE]

Excellent to know, thanks!

Do you remember where the persistent binding config was? Right now I have them in lpfc.conf but emlxs.conf doesn't have anything that looks like a sample of that same setup.

 

[Mikey D]

Excellent to know, thanks!

Do you remember where the persistent binding config was? Right now I have them in lpfc.conf but emlxs.conf doesn't have anything that looks like a sample of that same setup.

For persistent binding with EMLXS it's all done in that /etc/devlink.tab. That's the one part that's easier or less work I should say. You'll only have to update IBMtape.conf and /etc/devlink.tab, not /etc/devlink.tab, IBMtape.conf, AND the lpfc.conf.

 

[GregE]

Got it! You're right, it's easier ................... of course, now that we got it working.
Putting the wwn in the devlink.tab file and mapping to the target number right there is a much simpler setup.

Using lpfc driver:
# /etc/devlink.tab entry example.....
type=ddi_byte:tape;addr=10d,0; rmt/269\M0

...AND...

# /kernel/drv/lpfc.conf to match......
fcp-bind-WWPN="5005000000c6c11:lpfc1t269",

Using emlxs driver:
# /etc/devlink.tab entry example.....
type=ddi_byte:tape;addr=w5005000000c6c11,0; rmt/269\M0

Thanks again.

 

[GregE]

Almost. I missed yesterday that there is no library in my tapelist. Should be /dev/rmt/200smc, but is non-existent.

devlink entry being ignored:
type=ddi_byte:tape;addr=w5005000000c6c11,1; rmt/200\M0

Any idea why?

 

[Mikey D]

Almost. I missed yesterday that there is no library in my tapelist. Should be /dev/rmt/200smc, but is non-existent.

devlink entry being ignored:
type=ddi_byte:tape;addr=w5005000000c6c11,1; rmt/200\M0

Any idea why?

I would double check everything looks right in IBMtape.conf, I guess make sure the LUN number is correct for the SMC device too. When you do the add_drv IBMtape it'll create the smc and st devices so should come right in.

Might also want to make sure a /dev/rmt entry isn't already there taking up the number you're binding it too.

 

[GregE]

I assume this is the right alias in IBMtape.conf?

name="IBMtape" parent="emlxs" target=269 lun=0;
name="IBMtape" parent="emlxs" target=269 lun=1;

 

[Mikey D]

I assume this is the right alias in IBMtape.conf?

name="IBMtape" parent="emlxs" target=269 lun=0;
name="IBMtape" parent="emlxs" target=269 lun=1;

You know what Greg, I can't remember at this point but I'm pretty sure you need to change to the WWPN now if you're using the EMLXS driver in the IBMtape.conf

Sort of like this example, can't remember if your parent needs to be emlxs or fp

name="IBMtape" parent="fp" lun=0 fc-port-wwn="500308c098936005";
name="IBMtape" parent="fp" lun=0 fc-port-wwn="500308c098936001";

 

[GregE]

Almost. I missed yesterday that there is no library in my tapelist. Should be /dev/rmt/200smc, but is non-existent.

devlink entry being ignored:
type=ddi_byte:tape;addr=w5005000000c6c11,1; rmt/200\M0

Any idea why?

That piece is solved. The file /etc/driver_aliases calls for the following line for a TS3584 library:
IBMtape "scsiclass,08.vIBM.p03584L32"
....even though, my library frame is a L52. The manuals show L32 and I just thought that was a frame example. Nope, that's actual entry needed.

You know what Greg, I can't remember at this point but I'm pretty sure you need to change to the WWPN now if you're using the EMLXS driver in the IBMtape.conf

Sort of like this example, can't remember if your parent needs to be emlxs or fp

name="IBMtape" parent="fp" lun=0 fc-port-wwn="500308c098936005";
name="IBMtape" parent="fp" lun=0 fc-port-wwn="500308c098936001";

parent="emlxs" seems to be working, and builds the /dev/rmt/XXXst devices. Of course, I tried using "fp" and that also worked.

One thing that bugs me, and I don't know why it's doing it, is in tapelist -l, the Device ULT3580-TD3 is fine, but the ULT3580-TD4 should be showing as ULT3584-TD4(e). I have 5 LTO-4 drives. Sometimes when recreating /rmt/dev/XXXst the tapelist will show one of them with (e), other attempts it shows none, others it has shown 2 or 3. It's not consistent. It just denotes encryption availability on the drive. We don't use encryption, but what bugs me is that if it's not seeing that correctly, it's not seeing something when it's setting the device paths. I don't know what else it's unable to configure correctly. Right now doesn't show (e) on any of them.

               ------------ IBM Tape Device Information --------------- 
Inst#  Special File     Device           Serial No      TGT/LUN Ucode   World Wide NN    World Wide PN    Device Physical Path                         Path Type
----- --------------- ---------------- ---------------- ------- ------ ---------------- ---------------- -------------------------------------------- ----------
10    /dev/rmt/276st  ULT3580-TD4      0007874973       6493971/0   97F2   5005000000c6C18 5005000000c6C18 /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c18,0  N/A   
11    /dev/rmt/277st  ULT3580-TD4      0007874802       6493715/0   97F2   5005000000c6C19 5005000000c6C19 /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c19,0  N/A   
12    /dev/rmt/278st  ULT3580-TD4      0007874613       6493459/0   97F2   5005000000c6C1A 5005000000c6C1A /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c1a,0  N/A   
13    /dev/rmt/279st  ULT3580-TD4      0007874998       6493203/0   97F2   5005000000c6C1B 5005000000c6C1B /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c1b,0  N/A   
1     /dev/rmt/275st  ULT3580-TD4      0007874572       6495251/0   97F2   5005000000c6C17 5005000000c6C17 /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c17,0  N/A   
14    /dev/rmt/270st  ULT3580-TD3      0007808174       6495763/0   93G6   5005000000c6C12 5005000000c6C12 /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c12,0  N/A   
18    /dev/rmt/273st  ULT3580-TD3      0007809153       6495507/0   93G6   5005000000c6C15 5005000000c6C15 /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c15,0  N/A   
16    /dev/rmt/271st  ULT3580-TD3      0007811314       6496275/0   93G6   5005000000c6C13 5005000000c6C13 /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c13,0  N/A   
Not have adapter!
28    /dev/rmt/203smc 03584L32         0000078199000512 6496531/1   8900         N/A             N/A         /devices/pci@8,700000/lpfc@4/fp@0,0/sgen@w50050763004c6c14,1  Primary
19    /dev/rmt/272st  ULT3580-TD3      0007810345       6496531/0   93G6   5005000000c6C14 5005000000c6C14 /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c14,0  N/A   
Not have adapter!
26    /dev/rmt/200smc 03584L32         0000078199000512 6496019/1   8900         N/A             N/A         /devices/pci@8,700000/lpfc@4/fp@0,0/sgen@w50050763004c6c11,1  Alt_path_1
25    /dev/rmt/269st  ULT3580-TD3      0007807688       6496019/0   93G6   5005000000c6C11 5005000000c6C11 /devices/pci@8,700000/lpfc@4/fp@0,0/st@w50050763004c6c11,0  N/A

 

[Lineau]

Oh that was great. Thanks for sharing. I really like it. Really very helpful for me.

work at home business opportunity

 

[GregE]

Using lpfc driver:
# /etc/devlink.tab entry example.....
type=ddi_byte:tape;addr=10d,0; rmt/269\M0

...AND...

# /kernel/drv/lpfc.conf to match......
fcp-bind-WWPN="5005000000c6c11:lpfc1t269",

Using emlxs driver:
# /etc/devlink.tab entry example.....
type=ddi_byte:tape;addr=w5005000000c6c11,0; rmt/269\M0

New question! I'm back on this again (never did do the setup previously, had other issues). Now I'm setting up a new TSM server for our new data center location. I have 2 HBAs for tape. In the switch both HBA's are zoned to all 10 tape drives for failover capability. When I was using the LPFC driver, I would specify the HBA used for a specific tape drive, in the lpfc.conf file. This allowed me to run 5 tape drives on one HBA, and 5 on the other HBA, as follows........

(note lpfc1 and lpfc2 are the two HBA designations)
..from lpfc.conf....
fcp-bind-WWPN="5005000000c6c11:lpfc1t269",
fcp-bind-WWPN="5005000000c6c11:lpfc1t270",
fcp-bind-WWPN="5005000000c6c11:lpfc1t272",
fcp-bind-WWPN="5005000000c6c11:lpfc1t273",
fcp-bind-WWPN="5005000000c6c11:lpfc1t274",
fcp-bind-WWPN="5005000000c6c11:lpfc2t275",
fcp-bind-WWPN="5005000000c6c11:lpfc2t276",
fcp-bind-WWPN="5005000000c6c11:lpfc2t277",
fcp-bind-WWPN="5005000000c6c11:lpfc2t278",
fcp-bind-WWPN="5005000000c6c11:lpfc2t279",

Now using the EMLXS driver, I obviously no longer use lpfc.conf. So if I want to setup my drives for 5 per HBA the same as above (and maybe alternate HBAs for every other tape drive), where would I be able to accomplish this?

I assume in /kernel/drv/emlxs.conf, but in that file there are no examples of the proper method of setting up persistent binding. The lpfc.conf file and documentation explains it nicely for lpfc, but emlxs.conf, nothing I can find.

 

[GregE]

From this document.....(emlxs) http://www-dl.emulex.com/support/solaris/sfs/231h/manual.pdf

Note: The fcp-bind-WWNN, fcp-bind-WWPN and fcp-bind-DID parameters do not apply to a
specific HBA. They are the global parameters. These parameters specify a list of
persistent bindings. Each entry in this list applies to a specific instance of an adapter.
You can only use one type of binding per adapter.

Same thing in this document (lpfc). http://www-dl.emulex.com/support/solaris/620j/manual.pdf

Note: The fcp-bind-WWNN, fcp-bind-WWPN and fcp-bind-DID driver properties do not
apply to a specific HBA. They are the global properties. These properties specify a list
of persistent bindings. Each entry in this list applies to a specific instance of an HBA.
You can only use one type of binding per adapter.
___

The LPFC documentation has much more info about persistent binding. The EMLXS documentation has nothing, though above it does mention fcp-bind-WWPN, though in its table of parameters, it's not mentioned so there's no example of how it would be implemented. In the LPFC document, it's mentioned and explained.

 

[GregE]

Devices are showing up as /dev/rmt/0st, /dev/rmt/1st, etc. Ignoring my numbering. Anyone know what I am missing? Is there a 3rd file I need to be populating? (emlxs.conf?)

(I realize I am missing lines regarding dual pathing. I'll set those but need to figure out how to divide my tape drives between the two HBAs, then I'll have my secondary library path be on the opposite HBA. Persistent binding is a key for that too.)

.../etc/devlink.conf

#
# /dev/rmt/smc (medium changer, ie. tape library) #
#
type=ddi_byte:tape;addr=w500507630F762901,1;    rmt/100\M0
#
# /dev/rmt/st (tape drives)  #
#
type=ddi_byte:tape;addr=w500507630F762901,0;    rmt/101\M0
type=ddi_byte:tape;addr=w500507630F762902,0;    rmt/102\M0
type=ddi_byte:tape;addr=w500507630F762903,0;    rmt/103\M0
type=ddi_byte:tape;addr=w500507630F762904,0;    rmt/104\M0
type=ddi_byte:tape;addr=w500507630F762905,0;    rmt/105\M0
type=ddi_byte:tape;addr=w500507630F762906,0;    rmt/106\M0
type=ddi_byte:tape;addr=w500507630F762907,0;    rmt/107\M0
type=ddi_byte:tape;addr=w500507630F762908,0;    rmt/108\M0
type=ddi_byte:tape;addr=w500507630F762909,0;    rmt/109\M0
type=ddi_byte:tape;addr=w500507630F76290A,0;    rmt/110\M0
#
## Alternate Path ##
#
# /dev/rmt/st (tape drives)  #
#
type=ddi_byte:tape;addr=w500507630F762901,0;    rmt/901\M0
type=ddi_byte:tape;addr=w500507630F762902,0;    rmt/902\M0
type=ddi_byte:tape;addr=w500507630F762903,0;    rmt/903\M0
type=ddi_byte:tape;addr=w500507630F762904,0;    rmt/904\M0
type=ddi_byte:tape;addr=w500507630F762905,0;    rmt/905\M0
type=ddi_byte:tape;addr=w500507630F762906,0;    rmt/906\M0
type=ddi_byte:tape;addr=w500507630F762907,0;    rmt/907\M0
type=ddi_byte:tape;addr=w500507630F762908,0;    rmt/908\M0
type=ddi_byte:tape;addr=w500507630F762909,0;    rmt/909\M0
type=ddi_byte:tape;addr=w500507630F76290A,0;    rmt/910\M0

.../usr/kernel/drv/IBMtape.conf

# Dual Path Support
#
dpf_support=1;

# target=101 lun=0 (tape drive)
# target=101 lun=1 (medium changer, ie. tape library)
#
name="IBMtape" parent="emlxs" target=101 lun=0;
name="IBMtape" parent="emlxs" target=101 lun=1;
name="IBMtape" parent="emlxs" target=102 lun=0;
name="IBMtape" parent="emlxs" target=103 lun=0;
name="IBMtape" parent="emlxs" target=104 lun=0;
name="IBMtape" parent="emlxs" target=105 lun=0;
name="IBMtape" parent="emlxs" target=106 lun=0;
name="IBMtape" parent="emlxs" target=107 lun=0;
name="IBMtape" parent="emlxs" target=108 lun=0;
name="IBMtape" parent="emlxs" target=109 lun=0;
name="IBMtape" parent="emlxs" target=110 lun=0;


# Alternate Path
#
name="IBMtape" parent="emlxs" target=901 lun=0;
name="IBMtape" parent="emlxs" target=901 lun=1;
name="IBMtape" parent="emlxs" target=902 lun=0;
name="IBMtape" parent="emlxs" target=903 lun=0;
name="IBMtape" parent="emlxs" target=904 lun=0;
name="IBMtape" parent="emlxs" target=905 lun=0;
name="IBMtape" parent="emlxs" target=906 lun=0;
name="IBMtape" parent="emlxs" target=907 lun=0;
name="IBMtape" parent="emlxs" target=908 lun=0;
name="IBMtape" parent="emlxs" target=909 lun=0;
name="IBMtape" parent="emlxs" target=910 lun=0;
#

name="IBMtape" parent="pseudo" instance=16382;
name="IBMtape" parent="pseudo" instance=16383;

name="IBMtape" class="scsi" target=101 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=101 lun=1 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=102 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=103 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=104 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=105 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=106 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=107 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=108 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=109 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=110 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;

# Alternate Path
#
name="IBMtape" class="scsi" target=901 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=902 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=903 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=904 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=905 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=906 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=907 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=908 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=909 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=910 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;

 

[Mikey D]

For the st devices look for the st.conf file, believe it's under /kernel/drv and comment this last line out. After you'll need to rem_drv st, mt, ibmtape and clear our /dev/rmt/* and then rerun the add_drv commands. For the dual pathing stuff and number I honestly never had done that before I left my job with all the SUN equipment so I'm not positive what you'd have to do there.

# This line adds support for Fibre Channel Tapes
(comment this out)name="st" parent="fp" target=0;

 

[GregE]

Thanks. Commenting out everything in st.conf and running "rem_drv st" were the first things I did.

"mt" isn't loaded (modinfo | grep -i mt) so I'm ok there too.

Dual pathing shouldn't be a big deal one I know how to get persistent binding done.

 

[Mikey D]

Oh your IBMtape.conf, you can't use targets anymore if you're using EMLXS, needs to be wwpn like this. That should fix the number issue.

name="IBMtape" parent="fp" lun=0 fc-port-wwn="500308c098936005";
name="IBMtape" parent="fp" lun=0 fc-port-wwn="500308c098936001";

 

[GregE]

Thanks Mikey_D, do I use wwpn in the second set of lines? (the ones that establish the tape drive options)

Old...
name="IBMtape" class="scsi" target=101 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;

New?...
name="IBMtape" class="scsi" fc-port-wwn="500507630F762901" lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;

____

EDIT: I've tried it, using "wwn" instead of "target" everywhere in IBMtape.conf. For some reason it is still ignoring my numbering, instead creating /dev/rmt/0st.....1st, 2st, etc.

 

[Mikey D]

I'm honestly not sure on the tape options line Greg, we never even used to set those in our IBMtape.conf files we just did the bare minimums with the parent & lun lines.

Thinking about it more with the numbering still not coming in right makes me thing something is amiss with the devlink.tab.

When you do a cfgadm -al do the wwpn's still match up with the devlink.tab?

 

[GregE]

There really isn't anything to say it's 'matching' devlink.tab, but it shows the drives.

Ap_Id                          Type         Receptacle   Occupant     Condition
c5                             fc-fabric    connected    configured   unknown
c5::500507630f762901           tape         connected    configured   unknown
c5::500507630f762902           tape         connected    configured   unknown
c5::500507630f762903           tape         connected    configured   unknown
c5::500507630f762904           tape         connected    configured   unknown
c5::500507630f762905           tape         connected    configured   unknown
c5::500507630f762906           tape         connected    configured   unknown
c5::500507630f762907           tape         connected    configured   unknown
c5::500507630f762908           tape         connected    configured   unknown
c5::500507630f762909           tape         connected    configured   unknown
c5::500507630f76290a           tape         connected    configured   unknown
c6                             fc-fabric    connected    configured   unknown
c6::500507630f762901           tape         connected    configured   unknown
c6::500507630f762902           tape         connected    configured   unknown
c6::500507630f762903           tape         connected    configured   unknown
c6::500507630f762904           tape         connected    configured   unknown
c6::500507630f762905           tape         connected    configured   unknown
c6::500507630f762906           tape         connected    configured   unknown
c6::500507630f762907           tape         connected    configured   unknown
c6::500507630f762908           tape         connected    configured   unknown
c6::500507630f762909           tape         connected    configured   unknown
c6::500507630f76290a           tape         connected    configured   unknown

I'm getting close. Found out that the uppercase letters in the WWPN in devlink.tab were causing those entries to be ignored. I changed to lower case and /dev/rmt/xxx began using my numbering properly. (changed IBMtape.conf too, but I think devlink.tab was the one that didn't like it)

# ls -l /dev/rmt/*st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/101st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762901,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/102st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762902,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/103st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762903,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/104st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762904,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/105st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762905,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/106st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762906,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/107st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762907,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/108st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762908,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/109st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762909,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/110st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f76290a,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/901st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762901,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/902st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762902,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/903st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762903,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/904st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762904,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/905st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762905,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/906st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762906,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/907st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762907,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/908st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762908,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/909st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f762909,0:st
lrwxrwxrwx   1 root     sys           79 Mar 21 14:16 /dev/rmt/910st -> ../../devices/pci@3,700000/SUNW,emlxs@0,1/fp@0,0/IBMtape@w500507630f76290a,0:st