Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

raidscan shows two TID# for the same LDEV from XP

CAS_2
Valued Contributor

raidscan shows two TID# for the same LDEV from XP

Hi

I lost my RAID Manager instance configuration file. Then I must recreate it.

I know the LDEVs and the port (CL1-L).

I run

raidscan -fx -CLI -p CL1-C

to get the TID# and LUN#, but raidscan shows two values for the same LDEV:

PORT# /ALPA/C TID# LU# Seq# Num LDEV# P/S Status P-Seq# P-LDEV#
CL1-L d5 10 0 0 0 63063 1 9e P-VOL PSUS 63063 146
CL1-L d5 10 0 0 1 63063 1 9e SMPL - - -
CL1-L d5 10 0 0 2 63063 1 9e SMPL - - -
.
.
.
CL1-L d5 10 2 0 0 63063 1 9e P-VOL PSUS 63063 146
CL1-L d5 10 2 0 1 63063 1 9e SMPL - - -
CL1-L d5 10 2 0 2 63063 1 9e SMPL - - -


Which TID value must use in horcm.conf file ?
Is this behaviour right ?

Thanx in advance
3 REPLIES
Nigel Poulton
Respected Contributor

Re: raidscan shows two TID# for the same LDEV from XP

Just had a *quick* look at your above post, isnt the TID listed as 10 in both sections?

I would have to check my notes to be certain of the readout but it looks like 10 to me.

E.g. the first line -
CL1-L(port) d5(ALPA) 10(TID) 000(LUN) 63063(serial) ......

Correct me if Im wrong, Ive only glanced at it. Also may be you could upload a text files with the full command and entire output?

HTH
Talk about the XP and EVA @ http://blog.nigelpoulton.com
CAS_2
Valued Contributor

Re: raidscan shows two TID# for the same LDEV from XP

The 10 is the C value.
Perhaps, removing the option -CLI, you realize the values:

PORT# /ALPA/C,TID#, LU#..Num(LDEV#....)...P/S, Status, LDEV#,P-Seq#,P-LDEV#
CL1-L /d5/10, 0, 0-0 .1(9e)............P-VOL PSUS 9e, 63063 146
CL1-L /d5/10, 0, 0-1 .1(9e)............SMPL ---- -----, ----- -----
CL1-L /d5/10, 0, 0-2 .1(9e)............SMPL ---- -----, ----- -----
.
.
.
CL1-L /d5/10, 2, 0-0 .1(9e)............P-VOL PSUS 9e, 63063 146
CL1-L /d5/10, 2, 0-1 .1(9e)............SMPL ---- -----, ----- -----
CL1-L /d5/10, 2, 0-2 .1(9e)............SMPL ---- -----, ----- -----
CAS_2
Valued Contributor

Re: raidscan shows two TID# for the same LDEV from XP

Mistery is solved.

"raidscan -p CL1-L" shows LUNs from CL1-L and from CL2-L, not just from CL1-L.

I did the following:

raidscan -fx -p CL1-L > 1L
raidscan -fx -p CL2-L > 2L

After editing both files 1L and 2L to remove the obvious differences (port names and ALPA/C values), the diff command shows 1L and 2L are equal.

The clue was this command line:

# echo /dev/rdsk/c10t0d1 "\n" /dev/rdsk/c11t0d1 | awk '{ print $1 }' | raidscan -find -fx
DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID
/dev/rdsk/c10t0d1 0 F CL1-L 0 0 63063 9E OPEN-E
/dev/rdsk/c11t0d1 0 F CL2-L 2 0 63063 9E OPEN-E

The output shows the TARG is 0 from CL1-L and 2 from CL2-L