此帖子已超过 5 年
12 消息
0
3733
redhat 6.2 detect DD890 drivers issue
I create 50 drivers, half drivers map to active 1a passive 1b, others map to 1b active passive 1a.
Now redhat can't auto detect drivers which mapped to host2, I have to manualy add drivers via this command.
echo "scsi add-single-device 2 0 1 #" > /proc/scsi/scsi "#" is (2,4,6,8...50)
Quesion: how to resolve the problem, server can auto detect all drivers
zone:
host1----1a
host2----1b
HBA card :emulex driver 8.3.5.45.4p
redhat6.2
[root@eslp92202 dp_depot]# lsscsi
[0:0:0:0] storage HP P410i 5.14 -
[0:0:0:1] disk HP LOGICAL VOLUME 5.14 /dev/sda
[1:0:0:0] mediumx STK L180 0306 /dev/sch0
[1:0:0:1] tape IBM ULTRIUM-TD3 8711 /dev/st0
[1:0:0:3] tape IBM ULTRIUM-TD3 8711 /dev/st1
[1:0:0:5] tape IBM ULTRIUM-TD3 8711 /dev/st2
[1:0:0:7] tape IBM ULTRIUM-TD3 8711 /dev/st3
[1:0:0:9] tape IBM ULTRIUM-TD3 8711 /dev/st4
[1:0:0:11] tape IBM ULTRIUM-TD3 8711 /dev/st5
[1:0:0:13] tape IBM ULTRIUM-TD3 8711 /dev/st6
[1:0:0:15] tape IBM ULTRIUM-TD3 8711 /dev/st7
[1:0:0:17] tape IBM ULTRIUM-TD3 8711 /dev/st8
[1:0:0:19] tape IBM ULTRIUM-TD3 8711 /dev/st9
[1:0:0:21] tape IBM ULTRIUM-TD3 8711 /dev/st10
[1:0:0:23] tape IBM ULTRIUM-TD3 8711 /dev/st11
[1:0:0:25] tape IBM ULTRIUM-TD3 8711 /dev/st12
[1:0:0:27] tape IBM ULTRIUM-TD3 8711 /dev/st13
[1:0:0:29] tape IBM ULTRIUM-TD3 8711 /dev/st14
[1:0:0:31] tape IBM ULTRIUM-TD3 8711 /dev/st15
[1:0:0:33] tape IBM ULTRIUM-TD3 8711 /dev/st16
[1:0:0:35] tape IBM ULTRIUM-TD3 8711 /dev/st17
[1:0:0:37] tape IBM ULTRIUM-TD3 8711 /dev/st18
[1:0:0:39] tape IBM ULTRIUM-TD3 8711 /dev/st19
[1:0:0:41] tape IBM ULTRIUM-TD3 8711 /dev/st20
[1:0:0:43] tape IBM ULTRIUM-TD3 8711 /dev/st21
[1:0:0:45] tape IBM ULTRIUM-TD3 8711 /dev/st22
[1:0:0:47] tape IBM ULTRIUM-TD3 8711 /dev/st23
[1:0:0:49] tape IBM ULTRIUM-TD3 8711 /dev/st24
[1:0:2:0] disk EMC SYMMETRIX 5874 /dev/sdb
[1:0:2:1] disk EMC SYMMETRIX 5874 /dev/sdc
[1:0:3:0] disk EMC SYMMETRIX 5874 /dev/sdd
[1:0:3:1] disk EMC SYMMETRIX 5874 /dev/sde
[2:0:2:0] disk EMC SYMMETRIX 5874 /dev/sdf
[2:0:2:1] disk EMC SYMMETRIX 5874 /dev/sdg
[2:0:3:0] disk EMC SYMMETRIX 5874 /dev/sdh
[2:0:3:1] disk EMC SYMMETRIX 5874 /dev/sdi
Anonymous
5 Practitioner
5 Practitioner
•
274.2K 消息
0
2012年9月4日 23:00
Please create two access groups.
Each access group have one initiator, and start the LUN from 0 for each access group.
Group: ESLP92202_VTL101_1
Initiators:
Initiator Alias Initiator WWPN
--------------- -----------------------
ESLP92202_05 10:00:00:00:c9:d5:c8:8c
--------------- -----------------------
Devices:
Device Name LUN Primary Ports Secondary Ports In-use Ports
-------------------- --- ------------- --------------- ------------
VTL101_Open changer 0 1a 1b 1a
VTL101_Open drive 1 1 1a 1b 1a
VTL101_Open drive 2 2 1a 1b 1a
VTL101_Open drive 3 3 1a 1b 1a
VTL101_Open drive 4 4 1a 1b 1a
.
.
.
.
.
VTL101_Open drive 25 25 1a 1b 1a
-----------
Group: ESLP92202_VTL101_2
Initiators:
Initiator Alias Initiator WWPN
--------------- -----------------------
ESLP92202_06 10:00:00:00:c9:d5:c8:8d
--------------- -----------------------
Devices:
Device Name LUN Primary Ports Secondary Ports In-use Ports
-------------------- --- ------------- --------------- ------------
VTL101_Open drive 26 0 1b 1a 1b
VTL101_Open drive 27 1 1b 1a 1b
VTL101_Open drive 28 2 1b 1a 1b
VTL101_Open drive 29 3 1b 1a 1b
.
.
.
.
.
VTL101_Open drive 50 24 1b 1a 1b
Anonymous
5 Practitioner
5 Practitioner
•
274.2K 消息
0
2012年9月4日 22:00
Please provide the output of below command from DD CLI:
# vtl group show all
Thank you.
Qilei
12 消息
0
2012年9月4日 22:00
Hi Bojianli,
Thanks for your reply. FYI!
~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2012.09.05 07:57:00 =~=~=~=~=~=~=~=~=~=~=~=
vtl group show all
Group: ESLP92202_VTL101_O
Initiators:
Initiator Alias Initiator WWPN
--------------- -----------------------
ESLP92202_05 10:00:00:00:c9:d5:c8:8c
ESLP92202_06 10:00:00:00:c9:d5:c8:8d
--------------- -----------------------
Devices:
Device Name LUN Primary Ports Secondary Ports In-use Ports
-------------------- --- ------------- --------------- ------------
VTL101_Open changer 0 1a 1b 1a
VTL101_Open drive 1 1 1a 1b 1a
VTL101_Open drive 2 2 1b 1a 1b
VTL101_Open drive 3 3 1a 1b 1a
VTL101_Open drive 4 4 1b 1a 1b
VTL101_Open drive 5 5 1a 1b 1a
VTL101_Open drive 6 6 1b 1a 1b
VTL101_Open drive 7 7 1a 1b 1a
VTL101_Open drive 8 8 1b 1a 1b
VTL101_Open drive 9 9 1a 1b 1a
VTL101_Open drive 10 10 1b 1a 1b
VTL101_Open drive 11 11 1a 1b 1a
VTL101_Open drive 12 12 1b 1a 1b
VTL101_Open drive 13 13 1a 1b 1a
VTL101_Open drive 14 14 1b 1a 1b
VTL101_Open drive 15 15 1a 1b 1a
VTL101_Open drive 16 16 1b 1a 1b
VTL101_Open drive 17 17 1a 1b 1a
VTL101_Open drive 18 18 1b 1a 1b
VTL101_Open drive 19 19 1a 1b 1a
VTL101_Open drive 20 20 1b 1a 1b
VTL101_Open drive 21 21 1a 1b 1a
VTL101_Open drive 22 22 1b 1a 1b
VTL101_Open drive 23 23 1a 1b 1a
VTL101_Open drive 24 24 1b 1a 1b
VTL101_Open drive 25 25 1a 1b 1a
VTL101_Open drive 26 26 1b 1a 1b
VTL101_Open drive 27 27 1a 1b 1a
VTL101_Open drive 28 28 1b 1a 1b
VTL101_Open drive 29 29 1a 1b 1a
VTL101_Open drive 30 30 1b 1a 1b
VTL101_Open drive 31 31 1a 1b 1a
VTL101_Open drive 32 32 1b 1a 1b
VTL101_Open drive 33 33 1a 1b 1a
VTL101_Open drive 34 34 1b 1a 1b
VTL101_Open drive 35 35 1a 1b 1a
VTL101_Open drive 36 36 1b 1a 1b
VTL101_Open drive 37 37 1a 1b 1a
VTL101_Open drive 38 38 1b 1a 1b
VTL101_Open drive 39 39 1a 1b 1a
VTL101_Open drive 40 40 1b 1a 1b
VTL101_Open drive 41 41 1a 1b 1a
VTL101_Open drive 42 42 1b 1a 1b
VTL101_Open drive 43 43 1a 1b 1a
VTL101_Open drive 44 44 1b 1a 1b
VTL101_Open drive 45 45 1a 1b 1a
VTL101_Open drive 46 46 1b 1a 1b
VTL101_Open drive 47 47 1a 1b 1a
VTL101_Open drive 48 48 1b 1a 1b
VTL101_Open drive 49 49 1a 1b 1a
VTL101_Open drive 50 50 1b 1a 1b
-------------------- --- ------------- --------------- ------------
Group: TapeServer
Initiators: None
Devices: None
Qilei
12 消息
0
2012年9月5日 00:00
Hi Bojianli
What is the best practice for DD ? it don' t support my old configuration ?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K 消息
0
2012年9月5日 03:00
It is recommended that you have exactly one initiator per access group.
Linux: When assigning access to Linux machines, always use LUN zero as the first LUN in the group, and use contiguous LUN numbers starting at zero with no gaps in the sequence. For example, assigning LUNs 0, 1, 2, 3, 4 is correct, assigning LUNs 0, 2, 4, 5 is incorrect. Always use one primary path on the VTL HBA to the tape drives and changer for the access group.
Qilei
12 消息
0
2012年9月5日 18:00
Hi Bojianli
Thanks for your support, now the server can detect all the drivers.
o17Uu33DCF12520
2 Intern
2 Intern
•
1.1K 消息
0
2012年9月9日 20:00
用中文总结下本帖的问题与回答,以便网友围观。
我有50个驱动器,其中一半映射到了active 1a passive 1b,另一半映射到了1b active 1a passive。现在redhat不能自动识别到映射到host2上的驱动器,我只能用如下命令手动添加。
echo "scsi add-single-device 2 0 1 #" > /proc/scsi/scsi "#" is (2,4,6,8...50)
请问:如何能让redhat自动检测到所有驱动器?
zone:
host1----1a
host2----1b
HBA card :emulex driver 8.3.5.45.4p
redhat6.2
[root@eslp92202 dp_depot]# lsscsi
[0:0:0:0] storage HP P410i 5.14 -
[0:0:0:1] disk HP LOGICAL VOLUME 5.14 /dev/sda
[1:0:0:0] mediumx STK L180 0306 /dev/sch0
[1:0:0:1] tape IBM ULTRIUM-TD3 8711 /dev/st0
[1:0:0:3] tape IBM ULTRIUM-TD3 8711 /dev/st1
[1:0:0:5] tape IBM ULTRIUM-TD3 8711 /dev/st2
[1:0:0:7] tape IBM ULTRIUM-TD3 8711 /dev/st3
[1:0:0:9] tape IBM ULTRIUM-TD3 8711 /dev/st4
[1:0:0:11] tape IBM ULTRIUM-TD3 8711 /dev/st5
[1:0:0:13] tape IBM ULTRIUM-TD3 8711 /dev/st6
[1:0:0:15] tape IBM ULTRIUM-TD3 8711 /dev/st7
[1:0:0:17] tape IBM ULTRIUM-TD3 8711 /dev/st8
[1:0:0:19] tape IBM ULTRIUM-TD3 8711 /dev/st9
[1:0:0:21] tape IBM ULTRIUM-TD3 8711 /dev/st10
[1:0:0:23] tape IBM ULTRIUM-TD3 8711 /dev/st11
[1:0:0:25] tape IBM ULTRIUM-TD3 8711 /dev/st12
[1:0:0:27] tape IBM ULTRIUM-TD3 8711 /dev/st13
[1:0:0:29] tape IBM ULTRIUM-TD3 8711 /dev/st14
[1:0:0:31] tape IBM ULTRIUM-TD3 8711 /dev/st15
[1:0:0:33] tape IBM ULTRIUM-TD3 8711 /dev/st16
[1:0:0:35] tape IBM ULTRIUM-TD3 8711 /dev/st17
[1:0:0:37] tape IBM ULTRIUM-TD3 8711 /dev/st18
[1:0:0:39] tape IBM ULTRIUM-TD3 8711 /dev/st19
[1:0:0:41] tape IBM ULTRIUM-TD3 8711 /dev/st20
[1:0:0:43] tape IBM ULTRIUM-TD3 8711 /dev/st21
[1:0:0:45] tape IBM ULTRIUM-TD3 8711 /dev/st22
[1:0:0:47] tape IBM ULTRIUM-TD3 8711 /dev/st23
[1:0:0:49] tape IBM ULTRIUM-TD3 8711 /dev/st24
[1:0:2:0] disk EMC SYMMETRIX 5874 /dev/sdb
[1:0:2:1] disk EMC SYMMETRIX 5874 /dev/sdc
[1:0:3:0] disk EMC SYMMETRIX 5874 /dev/sdd
[1:0:3:1] disk EMC SYMMETRIX 5874 /dev/sde
[2:0:2:0] disk EMC SYMMETRIX 5874 /dev/sdf
[2:0:2:1] disk EMC SYMMETRIX 5874 /dev/sdg
[2:0:3:0] disk EMC SYMMETRIX 5874 /dev/sdh
[2:0:3:1] disk EMC SYMMETRIX 5874 /dev/sdi
回答:
创建两个access groups,每个group有一个initiator,在每个组上重新启动LUN。
Group: ESLP92202_VTL101_1
Initiators:
Initiator Alias Initiator WWPN
--------------- -----------------------
ESLP92202_05 10:00:00:00:c9:d5:c8:8c
--------------- -----------------------
Devices:
Device Name LUN Primary Ports Secondary Ports In-use Ports
-------------------- --- ------------- --------------- ------------
VTL101_Open changer 0 1a 1b 1a
VTL101_Open drive 1 1 1a 1b 1a
VTL101_Open drive 2 2 1a 1b 1a
VTL101_Open drive 3 3 1a 1b 1a
VTL101_Open drive 4 4 1a 1b 1a
.
.
.
.
.
VTL101_Open drive 25 25 1a 1b 1a
-----------
Group: ESLP92202_VTL101_2
Initiators:
Initiator Alias Initiator WWPN
--------------- -----------------------
ESLP92202_06 10:00:00:00:c9:d5:c8:8d
--------------- -----------------------
Devices:
Device Name LUN Primary Ports Secondary Ports In-use Ports
-------------------- --- ------------- --------------- ------------
VTL101_Open drive 26 0 1b 1a 1b
VTL101_Open drive 27 1 1b 1a 1b
VTL101_Open drive 28 2 1b 1a 1b
VTL101_Open drive 29 3 1b 1a 1b
.
.
.
.
.
VTL101_Open drive 50 24 1b 1a 1b