what are the fcp, fcpdev, fcparray and sctl drivers ?

[Joe Choo]

I have always being wondering what the following device drivers/files are when I run "ioscan" and check the fibre connections. I only know "td" refers to the FC adapter.

Can anyone shed some light ?

fc 1 0/9/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td1
fcp 7 0/9/0/0.29 fcp CLAIMED INTERFACE FCP Domain
ext_bus 26 0/9/0/0.29.2.239.0 fcparray CLAIMED INTERFACE FCP Array Interface

ext_bus 24 0/9/0/0.29.2.255.14 fcpdev CLAIMED INTERFACE FCP Device Interface
ctl 15 0/9/0/0.29.2.255.14.15.0 sctl CLAIMED DEVICE DGC CX700
/dev/rscsi/c24t15d0
…

fcp 12 0/9/0/0.75 fcp CLAIMED INTERFACE FCP Domain
ext_bus 28 0/9/0/0.75.0.228.0 fcparray CLAIMED INTERFACE FCP Array Interface
…

ext_bus 29 0/9/0/0.75.0.232.0 fcparray CLAIMED INTERFACE FCP Array Interface
disk 81 0/9/0/0.75.0.232.0.0.0 sdisk CLAIMED DEVICE DGC CX600WDR3
/dev/dsk/c29t0d0 /dev/rdsk/c29t0d0
...

[Peter Godron]

Joe,
they are the bus drivers used for the different cards:
http://docs.hp.com/en/5187-1841/ch07s03.html

And from another HP doc:
"Virtual Ports

Some driver designs create â virtualâ ports that do not directly correspond to any physical hardware. Virtual ports can normally be identified by the driver that controls them. For example, HP Fibrechannel Mass Storage card drivers create virtual ports with drivers named â fcpâ , â fcpdevâ , â fcparrayâ , and â fcpmuxâ to control different aspects of the fibrechannel mass storage network to which they are attached.

Both SAM and rad do not explicitly list virtual ports when discussing topics that affect physical ports, however both types of ports are suspended and resumed as appropriate.

Since virtual ports are reported by ioscan, they will appear in the Peripheral Devices -> Cards area of SAM with the same slot ID as their corresponding physical port."