understanding ioscan

MSwift — Fri, 23 Jan 2009 20:40:55 GMT

Below is my ioscan -fn. How would i go thru an ioscan and ascertain the attached devices, could someone help me please?

Mswift

Class I H/W Path Driver S/W State H/W Type Description
============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapt
er (582)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE HP PCI 10/100Bas
e-TX Core
/dev/ether0
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C896 Fast W
ide Single-Ended
target 0 0/0/1/0.3 tgt CLAIMED DEVICE
tape 0 0/0/1/0.3.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/c0t3d0BESTn
/dev/rmt/0mb /dev/rmt/c0t3d0BESTnb
/dev/rmt/0mn /dev/rmt/c0t3d0DDS
/dev/rmt/0mnb /dev/rmt/c0t3d0DDSb
/dev/rmt/c0t3d0BEST /dev/rmt/c0t3d0DDSn
/dev/rmt/c0t3d0BESTb /dev/rmt/c0t3d0DDSnb
autoch 0 0/0/1/0.3.1 schgr CLAIMED DEVICE HP C1557A
/dev/rac/c0t3d1
target 1 0/0/1/0.7 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra
Wide Single-Ended
target 2 0/0/1/1.2 tgt CLAIMED DEVICE
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
target 3 0/0/1/1.7 tgt CLAIMED DEVICE
ctl 1 0/0/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ext_bus 2 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra
Wide Single-Ended
target 4 0/0/2/0.2 tgt CLAIMED DEVICE
disk 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
target 5 0/0/2/0.7 tgt CLAIMED DEVICE
ctl 2 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ext_bus 3 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Ultra
Wide Single-Ended
target 6 0/0/2/1.2 tgt CLAIMED DEVICE
disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM
305
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
target 7 0/0/2/1.7 tgt CLAIMED DEVICE
ctl 3 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
tty 0 0/0/4/0 asio0 CLAIMED INTERFACE PCI Serial (103c
1048)
/dev/GSPdiag1 /dev/mux0 /dev/tty0p1
/dev/diag/mux0 /dev/tty0p0 /dev/tty0p2
tty 1 0/0/5/0 asio0 CLAIMED INTERFACE PCI Serial (103c
1048)
/dev/GSPdiag2 /dev/mux1
/dev/diag/mux1 /dev/tty1p1
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)
ba 2 0/1/0/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
lan 1 0/1/0/0/4/0 btlan CLAIMED INTERFACE HP A5506A PCI 10
/100Base-TX 4 port
lan 2 0/1/0/0/5/0 btlan CLAIMED INTERFACE HP A5506A PCI 10
/100Base-TX 4 port
lan 3 0/1/0/0/6/0 btlan CLAIMED INTERFACE HP A5506A PCI 10
/100Base-TX 4 port
lan 4 0/1/0/0/7/0 btlan CLAIMED INTERFACE HP A5506A PCI 10
/100Base-TX 4 port
ba 3 0/1/1/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
lan 5 0/1/1/0/4/0 btlan CLAIMED INTERFACE HP A5506A PCI 10
/100Base-TX 4 port
lan 6 0/1/1/0/5/0 btlan CLAIMED INTERFACE HP A5506A PCI 10
/100Base-TX 4 port
lan 7 0/1/1/0/6/0 btlan CLAIMED INTERFACE HP A5506A PCI 10
/100Base-TX 4 port
lan 8 0/1/1/0/7/0 btlan CLAIMED INTERFACE HP A5506A PCI 10
/100Base-TX 4 port
ba 4 0/2 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)
ba 5 0/3 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)
ext_bus 6 0/3/0/0 c720 CLAIMED INTERFACE SCSI C895 Ultra2
Wide LVD
target 8 0/3/0/0.0 tgt CLAIMED DEVICE
disk 17 0/3/0/0.0.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
target 9 0/3/0/0.1 tgt CLAIMED DEVICE
disk 18 0/3/0/0.1.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c6t1d0 /dev/rdsk/c6t1d0
target 10 0/3/0/0.2 tgt CLAIMED DEVICE
disk 19 0/3/0/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404
LC
/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0
target 11 0/3/0/0.3 tgt CLAIMED DEVICE
disk 20 0/3/0/0.3.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c6t3d0 /dev/rdsk/c6t3d0
target 12 0/3/0/0.7 tgt CLAIMED DEVICE
ctl 10 0/3/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c6t7d0
target 13 0/3/0/0.8 tgt CLAIMED DEVICE
disk 21 0/3/0/0.8.0 sdisk CLAIMED DEVICE HP 18.2GST318404
LC
/dev/dsk/c6t8d0 /dev/rdsk/c6t8d0
target 14 0/3/0/0.9 tgt CLAIMED DEVICE
disk 22 0/3/0/0.9.0 sdisk CLAIMED DEVICE SEAGATE ST318404
LC
/dev/dsk/c6t9d0 /dev/rdsk/c6t9d0
target 15 0/3/0/0.10 tgt CLAIMED DEVICE
disk 23 0/3/0/0.10.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c6t10d0 /dev/rdsk/c6t10d0
target 16 0/3/0/0.14 tgt CLAIMED DEVICE
ctl 11 0/3/0/0.14.0 sctl CLAIMED DEVICE HP A5272A
/dev/rscsi/c6t14d0
target 17 0/3/0/0.15 tgt CLAIMED DEVICE
ctl 18 0/3/0/0.15.0 sctl CLAIMED DEVICE HP A5272A
ba 6 0/4 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)
ext_bus 7 0/4/0/0 c720 CLAIMED INTERFACE SCSI C895 Ultra2
Wide LVD
target 18 0/4/0/0.0 tgt CLAIMED DEVICE
disk 24 0/4/0/0.0.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c7t0d0 /dev/rdsk/c7t0d0
target 19 0/4/0/0.1 tgt CLAIMED DEVICE
disk 25 0/4/0/0.1.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c7t1d0 /dev/rdsk/c7t1d0
target 20 0/4/0/0.2 tgt CLAIMED DEVICE
disk 26 0/4/0/0.2.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c7t2d0 /dev/rdsk/c7t2d0
target 21 0/4/0/0.3 tgt CLAIMED DEVICE
disk 27 0/4/0/0.3.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c7t3d0 /dev/rdsk/c7t3d0
target 22 0/4/0/0.7 tgt CLAIMED DEVICE
ctl 12 0/4/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c7t7d0
target 23 0/4/0/0.8 tgt CLAIMED DEVICE
disk 28 0/4/0/0.8.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c7t8d0 /dev/rdsk/c7t8d0
target 24 0/4/0/0.9 tgt CLAIMED DEVICE
disk 29 0/4/0/0.9.0 sdisk CLAIMED DEVICE SEAGATE ST318404
LC
/dev/dsk/c7t9d0 /dev/rdsk/c7t9d0
target 25 0/4/0/0.10 tgt CLAIMED DEVICE
disk 30 0/4/0/0.10.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c7t10d0 /dev/rdsk/c7t10d0
target 26 0/4/0/0.14 tgt CLAIMED DEVICE
ctl 20 0/4/0/0.14.0 sctl CLAIMED DEVICE HP A5272A
/dev/rscsi/c7t14d0
target 27 0/4/0/0.15 tgt CLAIMED DEVICE
ctl 21 0/4/0/0.15.0 sctl CLAIMED DEVICE HP A5272A
/dev/rscsi/c7t15d0
ba 7 0/5 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)
ba 8 0/6 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)
ext_bus 8 0/6/0/0 c720 CLAIMED INTERFACE SCSI C895 Ultra2
Wide LVD
target 28 0/6/0/0.0 tgt CLAIMED DEVICE
disk 31 0/6/0/0.0.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c8t0d0 /dev/rdsk/c8t0d0
target 29 0/6/0/0.1 tgt CLAIMED DEVICE
disk 32 0/6/0/0.1.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c8t1d0 /dev/rdsk/c8t1d0
target 30 0/6/0/0.2 tgt CLAIMED DEVICE
disk 33 0/6/0/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404
LC
/dev/dsk/c8t2d0 /dev/rdsk/c8t2d0
target 31 0/6/0/0.3 tgt CLAIMED DEVICE
disk 34 0/6/0/0.3.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c8t3d0 /dev/rdsk/c8t3d0
target 32 0/6/0/0.6 tgt CLAIMED DEVICE
ctl 16 0/6/0/0.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c8t6d0
target 33 0/6/0/0.8 tgt CLAIMED DEVICE
disk 35 0/6/0/0.8.0 sdisk CLAIMED DEVICE HP 18.2GST318404
LC
/dev/dsk/c8t8d0 /dev/rdsk/c8t8d0
target 34 0/6/0/0.9 tgt CLAIMED DEVICE
disk 36 0/6/0/0.9.0 sdisk CLAIMED DEVICE SEAGATE ST318404
LC
/dev/dsk/c8t9d0 /dev/rdsk/c8t9d0
target 35 0/6/0/0.10 tgt CLAIMED DEVICE
disk 37 0/6/0/0.10.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c8t10d0 /dev/rdsk/c8t10d0
target 36 0/6/0/0.14 tgt CLAIMED DEVICE
ctl 14 0/6/0/0.14.0 sctl CLAIMED DEVICE HP A5272A
/dev/rscsi/c8t14d0
target 37 0/6/0/0.15 tgt CLAIMED DEVICE
ctl 19 0/6/0/0.15.0 sctl CLAIMED DEVICE HP A5272A
ba 9 0/7 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)
ext_bus 9 0/7/0/0 c720 CLAIMED INTERFACE SCSI C895 Ultra2
Wide LVD
target 38 0/7/0/0.0 tgt CLAIMED DEVICE
disk 38 0/7/0/0.0.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c9t0d0 /dev/rdsk/c9t0d0
target 39 0/7/0/0.1 tgt CLAIMED DEVICE
disk 39 0/7/0/0.1.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c9t1d0 /dev/rdsk/c9t1d0
target 40 0/7/0/0.2 tgt CLAIMED DEVICE
disk 40 0/7/0/0.2.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c9t2d0 /dev/rdsk/c9t2d0
target 41 0/7/0/0.3 tgt CLAIMED DEVICE
disk 41 0/7/0/0.3.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c9t3d0 /dev/rdsk/c9t3d0
target 42 0/7/0/0.6 tgt CLAIMED DEVICE
ctl 17 0/7/0/0.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c9t6d0
target 43 0/7/0/0.8 tgt CLAIMED DEVICE
disk 42 0/7/0/0.8.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c9t8d0 /dev/rdsk/c9t8d0
target 44 0/7/0/0.9 tgt CLAIMED DEVICE
disk 43 0/7/0/0.9.0 sdisk CLAIMED DEVICE SEAGATE ST318404
LC
/dev/dsk/c9t9d0 /dev/rdsk/c9t9d0
target 45 0/7/0/0.10 tgt CLAIMED DEVICE
disk 44 0/7/0/0.10.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c9t10d0 /dev/rdsk/c9t10d0
target 46 0/7/0/0.14 tgt CLAIMED DEVICE
ctl 22 0/7/0/0.14.0 sctl CLAIMED DEVICE HP A5272A
/dev/rscsi/c9t14d0
target 47 0/7/0/0.15 tgt CLAIMED DEVICE
ctl 23 0/7/0/0.15.0 sctl CLAIMED DEVICE HP A5272A
/dev/rscsi/c9t15d0
memory 0 8 memory CLAIMED MEMORY Memory
processor 0 160 processor CLAIMED PROCESSOR Processor
processor 1 162 processor CLAIMED PROCESSOR Processor
processor 2 164 processor CLAIMED PROCESSOR Processor
processor 3 166 processor CLAIMED PROCESSOR Processor

Re: understanding ioscan

Patrick Wallek — Fri, 23 Jan 2009 20:54:03 GMT

What kind of attached devices?

# ioscan -kfnC disk
will show all disks attached.

# isocan -kfnC tape
will show tape drives attached.

# ioscan -kfnC lan
will show lan cards.

# ioscan -kfnC fc
will show fibre channel interfaces.

# ioscan -kfnC processor
will show the processors in your system.

I'm not clear on what you are asking. Could you elaborate?

Re: understanding ioscan

sujit kumar singh — Fri, 23 Jan 2009 21:05:08 GMT

hi the simple implication of ioscan is to tell u the Device databse that HP-UX maintains for the devices that the system has in it, running 11.31 this also can tell the health status of the devices.

the headers are self explanatory still :

Class : the type of dev :
disk, ext_bus -- means BUS, processor, memory,lan ,tape,lba -- logical bus adapter, sba --- system bus adapter,ba -- bus adapter, target --where a SCSI Dev can be attached ... etc

Instance NO: the ocuurance of a similar type of device , for similar devices HP-UX gives diff instance nos to identify them,

HW_path : the Device path of the Device starting from the SBA that is System Bus Adapter that is the root of the Device tree.
This is actually encoded in the Minor no of the Devices.

Driver: the software that is the driver for that device that the Kernel uses to Communicate.This has a reference to the Major no of the Device.

Software State: the state that tells that the device driver is bound to the kernel or not. CLAIMED means that is configured in the Kernel. UNCLAIMED means that the Dev is there but there is no software attachmen twith the Kernel.

HW_type: type of HW , more description on type of the Device as it is a Device , Interface or adapter , memory , processor etc.NO_HW means that the device is not sensed by the system as present.

Description:more to describe the device by model etc.

device files: these are the Device files that the Kernel uses for IO with the device.
can be block or character or even special files.

Please refer to the manpages of the command

ioscan --- scan the system HW
lssf --- list dev specisl files
insf --- install the device special files
rmsf --- remove the device specisl files
ioinit --- io initialisation.

Regards
Sujit

Re: understanding ioscan

MSwift — Fri, 23 Jan 2009 21:41:25 GMT

Thanks. I wanted to find out from the output if there were open slots for HBA cards since i may have to attach this to SAN. How would i be able to find that out from the above ioscan -fn output?

Mswift

Re: understanding ioscan

Patrick Wallek — Fri, 23 Jan 2009 22:11:05 GMT

>>>wanted to find out from the output if there were open slots for HBA cards

ioscan won't tell you this information.

If you know all of the possible I/O paths on your system, then you can peruse the ioscan output and look for gaps in the I/O path information given.

Re: understanding ioscan

sujit kumar singh — Fri, 23 Jan 2009 22:38:27 GMT

hi

depending on the HHrdware model and the OS version of ur system u can see by the command as
#rad -q for HP-UX 11.11
#olrad -q for 11.23 and 11.31

this can give u idea about the slots whcih are OLAR capable and also which slots are occupied and if they are occupied are they having the card present in that slot as OLAR capavle or not or if they are Suspended or powered on or off.

but the Hardware and OS shud be both able to run the OLAR command.

i had successsfully run the command even in rx6600 and rx4640(if i remeber 4640 correctly) and sx2000 SDs.

though the O/p format are different for the SD and rx6600.

the first col gives u the Slot location and the rest col givu the details regarding occupancy,OLAR capability, power condition, state of driver as suspended or resumed or not.

in rx6600 the first col is simply the PCI Slot no as numbered on the Chassis
and the same forst col in case of Partitioned Servers is in the form of
Cab-Bay-Chassis-Slot.

Regards
Sujit

Re: understanding ioscan

Torsten. — Mon, 26 Jan 2009 07:36:03 GMT

This looks like an empty slot:

ba 7 0/5 lba CLAIMED BUS_NEXUS Local PCI Bus Ad
apter (782)

But without knowing your server model and other details it is hard to say.

Post

# model
# olrad -q
(or # rad -q)

topic Re: understanding ioscan in Operating System - HP-UX

understanding ioscan

Re: understanding ioscan

Re: understanding ioscan

Re: understanding ioscan

Re: understanding ioscan

Re: understanding ioscan

Re: understanding ioscan