cancel
Showing results for 
Search instead for 
Did you mean: 

disk controller problem

SOLVED
Go to solution
Jeeshan
Honored Contributor

disk controller problem

OS - 11iv1
storage - EMC CX3-40

after assign LUN in this server, i found the hardware path is different

# powermt display
Symmetrix logical device count=0
CLARiiON logical device count=17
Hitachi logical device count=0
Invista logical device count=0
HP xp logical device count=0
Ess logical device count=0
HP HSx logical device count=0
==============================================================================
----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------
### HW Path Summary Total Dead IO/Sec Q-IOs Errors
==============================================================================
8 0/4/2/0.2.0.0.0 optimal 16 0 - 0 0
9 0/4/2/0.2.8.0.0 optimal 16 0 - 0 0
12 0/5/2/0.1.0.0.0 optimal 16 0 - 0 0
13 0/5/2/0.1.8.0.0 optimal 16 0 - 0 0
14 0/5/2/0.1.0.0.1 optimal 1 0 - 0 0
15 0/5/2/0.1.8.0.1 optimal 1 0 - 0 0
16 0/4/2/0.2.0.0.1 optimal 1 0 - 0 0
17 0/4/2/0.2.8.0.1 optimal 1 0 - 0 0

why it's happened? is there any parameters or configuration need to be change to control this hardware path?
a warrior never quits
5 REPLIES
sujit kumar singh
Honored Contributor

Re: disk controller problem

Hi

cant get ur question.

ur system seems to have 2 FC adaoters those are at 0/4/2/0 and 0/5/2/0 .

can u give more details about the same like how u think the hardware path has changed like waht u think the old HW path was or what is the new HW path??

can u post ioscan -fnCdisk O/P?

regards
sujit

Jeeshan
Honored Contributor

Re: disk controller problem

lemme escalate the problem

before allocating LUN the powermt display output was like below. all paths are same.

Symmetrix logical device count=0
CLARiiON logical device count=16
Hitachi logical device count=0
Invista logical device count=0
HP xp logical device count=0
Ess logical device count=0
HP HSx logical device count=0
==============================================================================
----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------
### HW Path Summary Total Dead IO/Sec Q-IOs Errors
==============================================================================
8 0/4/2/0.2.0.0.0 optimal 16 0 - 0 0
9 0/4/2/0.2.8.0.0 optimal 16 0 - 0 0
12 0/5/2/0.1.0.0.0 optimal 16 0 - 0 0
13 0/5/2/0.1.8.0.0 optimal 16 0 - 0 0

but after allocated 1 LUN the outputs like bellow

# powermt display
Symmetrix logical device count=0
CLARiiON logical device count=17
Hitachi logical device count=0
Invista logical device count=0
HP xp logical device count=0
Ess logical device count=0
HP HSx logical device count=0
==============================================================================
----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------
### HW Path Summary Total Dead IO/Sec Q-IOs Errors
==============================================================================
8 0/4/2/0.2.0.0.0 optimal 16 0 - 0 0
9 0/4/2/0.2.8.0.0 optimal 16 0 - 0 0
12 0/5/2/0.1.0.0.0 optimal 16 0 - 0 0
13 0/5/2/0.1.8.0.0 optimal 16 0 - 0 0
14 0/5/2/0.1.0.0.1 optimal 1 0 - 0 0
15 0/5/2/0.1.8.0.1 optimal 1 0 - 0 0
16 0/4/2/0.2.0.0.1 optimal 1 0 - 0 0
17 0/4/2/0.2.8.0.1 optimal 1 0 - 0 0

new 4 paths were generated.

why or which parameter/software configuration are responsible for generating disk's controller number? is this HP problem or SAN problem?
a warrior never quits
Vivek Bhatia
Trusted Contributor

Re: disk controller problem

Hi Ahsan,

1. How many LUNS in total are assigned to this server from this EMC?

2. Can you paste the new ioscan output which shows all the LUNS from this EMC?
ioscan -fnC disk

Will wait for the output.

Thanks
Vivek Bhatia
Jeeshan
Honored Contributor

Re: disk controller problem

here it is.

disk 3 0/4/2/0.2.0.0.0.0.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t0d0 /dev/rdsk/c8t0d0
disk 21 0/4/2/0.2.0.0.0.0.1 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t0d1 /dev/rdsk/c8t0d1
disk 22 0/4/2/0.2.0.0.0.0.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t0d2 /dev/rdsk/c8t0d2
disk 25 0/4/2/0.2.0.0.0.1.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t1d3 /dev/rdsk/c8t1d3
disk 5 0/4/2/0.2.0.0.0.6.7 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t6d7 /dev/rdsk/c8t6d7
disk 7 0/4/2/0.2.0.0.0.7.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t7d2 /dev/rdsk/c8t7d2
disk 8 0/4/2/0.2.0.0.0.7.4 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t7d4 /dev/rdsk/c8t7d4
disk 10 0/4/2/0.2.0.0.0.8.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t8d0 /dev/rdsk/c8t8d0
disk 27 0/4/2/0.2.0.0.0.8.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t8d3 /dev/rdsk/c8t8d3
disk 29 0/4/2/0.2.0.0.0.9.7 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t9d7 /dev/rdsk/c8t9d7
disk 13 0/4/2/0.2.0.0.0.10.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t10d0 /dev/rdsk/c8t10d0
disk 14 0/4/2/0.2.0.0.0.10.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t10d3 /dev/rdsk/c8t10d3
disk 16 0/4/2/0.2.0.0.0.11.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t11d2 /dev/rdsk/c8t11d2
disk 18 0/4/2/0.2.0.0.0.11.6 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t11d6 /dev/rdsk/c8t11d6
disk 31 0/4/2/0.2.0.0.0.12.1 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t12d1 /dev/rdsk/c8t12d1
disk 33 0/4/2/0.2.0.0.0.12.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c8t12d3 /dev/rdsk/c8t12d3
disk 69 0/4/2/0.2.0.0.1.4.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c16t4d3 /dev/rdsk/c16t4d3
disk 4 0/4/2/0.2.8.0.0.0.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t0d0 /dev/rdsk/c9t0d0
disk 23 0/4/2/0.2.8.0.0.0.1 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 24 0/4/2/0.2.8.0.0.0.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t0d2 /dev/rdsk/c9t0d2
disk 26 0/4/2/0.2.8.0.0.1.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t1d3 /dev/rdsk/c9t1d3
disk 6 0/4/2/0.2.8.0.0.6.7 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t6d7 /dev/rdsk/c9t6d7
disk 9 0/4/2/0.2.8.0.0.7.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t7d2 /dev/rdsk/c9t7d2
disk 11 0/4/2/0.2.8.0.0.7.4 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t7d4 /dev/rdsk/c9t7d4
disk 12 0/4/2/0.2.8.0.0.8.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t8d0 /dev/rdsk/c9t8d0
disk 28 0/4/2/0.2.8.0.0.8.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t8d3 /dev/rdsk/c9t8d3
disk 30 0/4/2/0.2.8.0.0.9.7 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t9d7 /dev/rdsk/c9t9d7
disk 15 0/4/2/0.2.8.0.0.10.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t10d0 /dev/rdsk/c9t10d0
disk 17 0/4/2/0.2.8.0.0.10.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t10d3 /dev/rdsk/c9t10d3
disk 19 0/4/2/0.2.8.0.0.11.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t11d2 /dev/rdsk/c9t11d2
disk 20 0/4/2/0.2.8.0.0.11.6 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t11d6 /dev/rdsk/c9t11d6
disk 32 0/4/2/0.2.8.0.0.12.1 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t12d1 /dev/rdsk/c9t12d1
disk 34 0/4/2/0.2.8.0.0.12.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c9t12d3 /dev/rdsk/c9t12d3
disk 68 0/4/2/0.2.8.0.1.4.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c17t4d3 /dev/rdsk/c17t4d3
disk 36 0/5/2/0.1.0.0.0.0.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t0d0 /dev/rdsk/c12t0d0
disk 38 0/5/2/0.1.0.0.0.0.1 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t0d1 /dev/rdsk/c12t0d1
disk 39 0/5/2/0.1.0.0.0.0.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t0d2 /dev/rdsk/c12t0d2
disk 41 0/5/2/0.1.0.0.0.1.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t1d3 /dev/rdsk/c12t1d3
disk 43 0/5/2/0.1.0.0.0.6.7 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t6d7 /dev/rdsk/c12t6d7
disk 45 0/5/2/0.1.0.0.0.7.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t7d2 /dev/rdsk/c12t7d2
disk 46 0/5/2/0.1.0.0.0.7.4 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t7d4 /dev/rdsk/c12t7d4
disk 47 0/5/2/0.1.0.0.0.8.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t8d0 /dev/rdsk/c12t8d0
disk 49 0/5/2/0.1.0.0.0.8.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t8d3 /dev/rdsk/c12t8d3
disk 53 0/5/2/0.1.0.0.0.9.7 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t9d7 /dev/rdsk/c12t9d7
disk 54 0/5/2/0.1.0.0.0.10.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t10d0 /dev/rdsk/c12t10d0
disk 55 0/5/2/0.1.0.0.0.10.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t10d3 /dev/rdsk/c12t10d3
disk 58 0/5/2/0.1.0.0.0.11.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t11d2 /dev/rdsk/c12t11d2
disk 60 0/5/2/0.1.0.0.0.11.6 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t11d6 /dev/rdsk/c12t11d6
disk 61 0/5/2/0.1.0.0.0.12.1 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t12d1 /dev/rdsk/c12t12d1
disk 63 0/5/2/0.1.0.0.0.12.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c12t12d3 /dev/rdsk/c12t12d3
disk 70 0/5/2/0.1.0.0.1.4.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c14t4d3 /dev/rdsk/c14t4d3
disk 35 0/5/2/0.1.8.0.0.0.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t0d0 /dev/rdsk/c13t0d0
disk 37 0/5/2/0.1.8.0.0.0.1 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t0d1 /dev/rdsk/c13t0d1
disk 40 0/5/2/0.1.8.0.0.0.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t0d2 /dev/rdsk/c13t0d2
disk 42 0/5/2/0.1.8.0.0.1.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t1d3 /dev/rdsk/c13t1d3
disk 44 0/5/2/0.1.8.0.0.6.7 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t6d7 /dev/rdsk/c13t6d7
disk 48 0/5/2/0.1.8.0.0.7.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t7d2 /dev/rdsk/c13t7d2
disk 50 0/5/2/0.1.8.0.0.7.4 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t7d4 /dev/rdsk/c13t7d4
disk 51 0/5/2/0.1.8.0.0.8.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t8d0 /dev/rdsk/c13t8d0
disk 52 0/5/2/0.1.8.0.0.8.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t8d3 /dev/rdsk/c13t8d3
disk 56 0/5/2/0.1.8.0.0.9.7 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t9d7 /dev/rdsk/c13t9d7
disk 57 0/5/2/0.1.8.0.0.10.0 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t10d0 /dev/rdsk/c13t10d0
disk 59 0/5/2/0.1.8.0.0.10.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t10d3 /dev/rdsk/c13t10d3
disk 62 0/5/2/0.1.8.0.0.11.2 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t11d2 /dev/rdsk/c13t11d2
disk 64 0/5/2/0.1.8.0.0.11.6 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t11d6 /dev/rdsk/c13t11d6
disk 65 0/5/2/0.1.8.0.0.12.1 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t12d1 /dev/rdsk/c13t12d1
disk 66 0/5/2/0.1.8.0.0.12.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c13t12d3 /dev/rdsk/c13t12d3
disk 67 0/5/2/0.1.8.0.1.4.3 sdisk CLAIMED DEVICE DGC CX3-40WDR5
/dev/dsk/c15t4d3 /dev/rdsk/c15t4d3
a warrior never quits
Duncan Edmonstone
Honored Contributor
Solution

Re: disk controller problem

It's not a problem. Its just the way addressing works in HP-UX11iv1 and 11iv2.

Basically a channel (or controller or virtual bus) can only have 128 devices as LUN numbers run 0-7 and target numbers run 0-15. This is the last 3 digits of a disks hardware path:

vbus.tgt.lun

So present more than 128 LUNs out of a port, and the next LUN will be presented on a new vbus. PowerPath interperets these vbus's as actual controllers - but they are just virtual. This is just down to what PowerPath interperets as a controller. Not what is actually a physical controller.

Some disk arrays (e.g. EVA) can define LUN numbers based on the host they are presented to, so on and EVA if I had 3 LUNs (LUNs 0-2) assigned to a HP-UX system, then 130 LUNs assigned to other systems, then another LUN assigned to the HP-UX system, the LUN number for that fourth LUN would be LUN 3. On a Clariion, the port is just configured as a whole, so with the same configuration these luns would be numbered LUN 0-2 and then LUN 133. Thats over 128, so a new vbus would be created.

See here for more details - disks on fabric login SANs usually use volume set addressing:

http://docs.hp.com/en/A6795-90006/ch01s11.html

HTH

Duncan

HTH

Duncan