1752805 Members
5663 Online
108789 Solutions
New Discussion юеВ

Re: Hi

 
SOLVED
Go to solution
Lazar martin
New Member

Hi

How do I read the output of the below cmd?
ioscan -funC disk
What is mean by "134" & "0/2/0/0.200.4.0.0.0.1"

disk 134 0/2/0/0.200.4.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
++++++++++++++++++++++++++++++++++++++++++++++


h1adm01a:/# ioscan -funC disk | more
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST118202LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 304
/dev/cdrom /dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 134 0/2/0/0.200.4.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
disk 135 0/2/0/0.200.4.0.0.0.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c11t0d2 /dev/rdsk/c11t0d2
disk 136 0/2/0/0.200.4.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c11t0d3 /dev/rdsk/c11t0d3
disk 137 0/2/0/0.200.4.0.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c11t0d4 /dev/rdsk/c11t0d4
disk 138 0/2/0/0.200.4.0.0.0.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c11t0d5 /dev/rdsk/c11t0d5
disk 139 0/2/0/0.200.4.0.0.0.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c11t0d6 /dev/rdsk/c11t0d6
disk 56 0/2/0/0.200.33.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c42t0d1 /dev/rdsk/c42t0d1
7 REPLIES 7
Sunny123_1
Esteemed Contributor

Re: Hi

Hi

0/2/0/0.200.4.0.0.0.1

It is the harware path.


Regards
Sunny
Torsten.
Acclaimed Contributor

Re: Hi

"134" is the device instance number,

"0/2/0/0.200.4.0.0.0.1" is the complete hardware path to the lun.

0/2/0/0 is inside the server and points to the slot, "200" stands for the switch domain ID (+offset), "4" is the port where the storage is connected and finally "0.0.1" is the LUN 1.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Lazar martin
New Member

Re: Hi

Thanks, but Yes I know that.. also its the start from the bus no to >>>??? what is the order ?
what are these each numbers refering too

0/2/0/0.200.4.0.0.0.1

0 - ?
2 - ?
0 - ?
0 - ?
200 - ?
4 - ?
0 - ?
0 - ?
0 - ?
1 - ?

Like for example (c39t7d6)
c39 - cylider ??
t7 - Target
d6 - Disk
Sunny123_1
Esteemed Contributor

Re: Hi

Hi

Refer Torsten's reply has provided all the things you wanted.


Regards
Sunny
Lazar martin
New Member

Re: Hi

Yes thanks...
I am clear in HW path :)
Now.. What is mean by Instant no?
and the sym device is just one device from a emc san box, and from the os side it is showing 2 disk as /dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
Is it because of dual pathing (redundant path)

Out put:
========
disk 134 0/2/0/0.200.4.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
Matti_Kurkela
Honored Contributor
Solution

Re: Hi

134 is the instance number, i.e. it's the 134th disk detected since the OS was installed or the "ioinit" command was used.

As Sunny123 said, 0/2/0/0.200.4.0.0.1 is a hardware path. The length of the path indicates this path probably refers to disk connected through a FibreChannel SAN.

The first part of it (0/2/0/0 here) identifies the slot where the HBA is installed. The numbering is specific to the server model, so you'll have to know the model of your server (see the output of the "model" command) and read the User's Guide for your server to find the mapping between I/O paths and card slots. Or if you're physically next to the server, just read the labels beside the card slots.

For the rest, please see:
http://docs.hp.com/en/A6795-90006/ch01s11.html

For more details, ask your SAN administrator.

MK
MK
Lazar martin
New Member

Re: Hi