urbanweasel
asked on
not all fscsiX are used , only one fibre channel is used not both
How do I configure the hdisks to use multiple fscsiX adapters
Adpt# Name State Mode Select Errors Paths Active
0 scsi0 NORMAL ACTIVE 23806339 0 4 4
1 fscsi1 NORMAL ACTIVE 0 0 0 0
2 fscsi1 NORMAL ACTIVE 0 0 2 0
3 fscsi1 NORMAL ACTIVE 0 0 2 0
How do I configure the vpaths to use fscsi0
thanks in advance
Adpt# Name State Mode Select Errors Paths Active
0 scsi0 NORMAL ACTIVE 23806339 0 4 4
1 fscsi1 NORMAL ACTIVE 0 0 0 0
2 fscsi1 NORMAL ACTIVE 0 0 2 0
3 fscsi1 NORMAL ACTIVE 0 0 2 0
How do I configure the vpaths to use fscsi0
thanks in advance
ASKER
Hi gheist
its a type 7026-6h1
running 5.2 -7
scsi1 Available 40-60 Wide/Ultra-2 SCSI I/O Controller
its a type 7026-6h1
running 5.2 -7
scsi1 Available 40-60 Wide/Ultra-2 SCSI I/O Controller
ASKER
I didnt find any book in the box
They are from ibm and they are feature
6239
They are from ibm and they are feature
6239
Did you install TotalStorage MultiPath from CD???
Configured via diag utility it shows after as single adaptor.
Maybe more recent driver than on CD:
http://www-1.ibm.com/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000065&loc=en_US&cs=utf-8&lang=en
Configured via diag utility it shows after as single adaptor.
Maybe more recent driver than on CD:
http://www-1.ibm.com/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000065&loc=en_US&cs=utf-8&lang=en
ASKER
Is that the sdd software
I installed it version was 1.6.0.5
I installed it version was 1.6.0.5
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No it didnt use the alternate path
I tried dropping the adapters and it
still comes back using just one fscsi1
same problem on another box
I tried dropping the adapters and it
still comes back using just one fscsi1
same problem on another box
ASKER
It turned out to be on the shark
It works over one of multiple paths at any given moment.
Be so kind and post output of "oslevel -r", name and model of your server, and name and model of problem adapter.