04-08-2010
USCSICMD ioctl calls for Fibre Channel(FC) devices on Solaris 10?
Hi ,
I have wrtitten a C program that issues USCSICMD ioctl call to the tape devices attached on solaris sparc 10. I was able to get the required information from all SCSI tape devices attached using the utility. But, whenever it is run on FC attached tape drives , the program returns an error saying "Inappropriate ioctl for device".
bash-2.05# inquiry /devices/pci@1f,4000/fibre-channel@2/fp@0,0:devctl
inquiry: /devices/pci@1f,4000/fibre-channel@2/fp@0,0:devctl: scsi inquiry failed: Inappropriate ioctl for device
Is it possible to make an USCSICMD ioctl on FC attached tape devices ?. Can someone please provide an example if possible.
Thanks,
Naveen
9 More Discussions You Might Find Interesting
1. Solaris
i want to use the devfsadm command and understand its function (3 Replies)
Discussion started by: bondoq
3 Replies
2. IP Networking
Is there any facility to filter/identify the data calls and voice calls coming throug modem?
OR
Can we get the data or voice calls information through a script(preferably C Kermit)? (0 Replies)
Discussion started by: pcsaji
0 Replies
3. AIX
Want to configure IBM raid strorage but the aix 5L cds do not have the drivers for the fibre channels. The machine is RS/6000. I have gone to IBM downlaodable sites but i can't find the drivers? help pliz:mad: (4 Replies)
Discussion started by: Zim-Aix-Guru
4 Replies
4. AIX
Hello,
Searched in all IBM Redbooks and on the internet and couldn't find anything about the new feature of POWER 6 which Virtual Fibre ( Fiber ) channel adapter.
It is similar to virtual scsi adapter.
In my client partition I created the virtual Fibre Adapter mapped it with the VIO... (1 Reply)
Discussion started by: filosophizer
1 Replies
5. Hardware
We will be buying new Xeon E5-based servers for our datacenter and were wondering which Fibre Channel host bus adapters we should select for these. The choices are Emulex or QLogic (8Gb FC HBAs). Anybody have any recommendations on which is the better choice?
Thanks in advance. (1 Reply)
Discussion started by: atahmass
1 Replies
6. Solaris
Hi
I had power issue that affected a server, in which I had power ON the server SPARC T1-B3 running solaris 10.
After power on the system stops at ok prompt, them I issued the following commands:
{0} ok setenv auto-boot? false
auto-boot? = false
{0} ok reset-all
SPARC T3-1B,... (10 Replies)
Discussion started by: fretagi
10 Replies
7. AIX
Hello all,
Let me introduce about the context and my environment.
We have an AIX 6.1 system, it has 4 FC channels
/ > lsdev -Cc adapter | grep fcs
fcs0 Available 23-T1 Virtual Fibre Channel Client Adapter
fcs1 Available 23-T1 Virtual Fibre Channel Client Adapter
fcs2 Available 23-T1... (14 Replies)
Discussion started by: Phat
14 Replies
8. Solaris
Hi,
One of my Netra 240 went into hung state and I had to reboot it. I powered it off and tried booting it again but unsuccessful. It is not connected to SAN and have local disks. Not able to boot in failsafe mode too.
There are two disks of 72GB, both are mirrored in SVM. It complains about... (5 Replies)
Discussion started by: solaris_1977
5 Replies
9. Solaris
hi everone
i am experiencing disconnectivity from storage to My database machines. i have doubt on my FC cards in my sparc T4-2 machines. i want to know how should i check from my solaris that whether the cards are ok or not because once the disks get disconnect from SAN so it come back again but... (5 Replies)
Discussion started by: janakors
5 Replies
LEARN ABOUT OPENSOLARIS
inquiry-serial-no
inquiry-device-type(9P) Kernel Properties for Drivers inquiry-device-type(9P)
NAME
inquiry-device-type, inquiry-vendor-id, inquiry-product-id, inquiry-revision-id, inquiry-serial-no - inquiry properties for SCSI devices
DESCRIPTION
These are optional properties, typically created by the system, for SCSI target devices. References to these properties should use their
sys/scsi/impl/inquiry.h defined names.
inquiry-device-type is an integer property. When present, the least significant byte of the value indicates the device type as defined by
the SCSI standard. Consumers of this property should compare the property values with DTYPE_* values defined in sys/scsi/generic/inquiry.h.
inquiry-vendor-id is a string property. When present, it contains the vendor information. This information typically comes from the
scsi_inquiry(9S) "inq_vid" field.
inquiry-product-id is a string property. When present, it contains the product identification. This information typically comes from the
scsi_inquiry(9S) "inq_pid" field.
inquiry-revision-id is a string property. When present, it contains the product revision. This revision typically comes from the
scsi_inquiry(9S) "inq_rev" field.
inquiry-serial-no is a string property. When present, it contains the serial number. The serial number is typically obtained from the EVPD
"Unit Serial Number" SCSI INQUIRY data (page 0x80).
SEE ALSO
scsi_inquiry(9S)
Writing Device Drivers
NOTES
Values established at tran_tgt_init(9E) time by an HBA driver take precedence over values established by the system, and HBA driver values
may not be the same length as the typical scsi_inquiry(9S) field.
SunOS 5.11 18 May 2001 inquiry-device-type(9P)