| Author |
Message |
sbs
Guest
|
 Posted:
Thu Oct 13, 2005 12:16 am Post subject:
Setting up MPIO |
|
|
Hi Everybody,
I'm a newbie to MPIO. My setup includes a MS initiator talking to an iSCSI
Target, and the initiator system has two NICs. I'm trying to setup multi-path
between the initiator and the target.
The MS Initiator GUI says the the "Enable multi-path" has to be enabled only
if iSCSI multipath software is installed on the system. Where do I get this
software from?
Also, does the target need to have multi-path capability enabled?
Any suggestions on how to go about this are appreciated. Thanks ... |
|
| Back to top |
|
 |
Jeff Goldner [MS]
Guest
|
| Posted:
Thu Oct 13, 2005 4:17 pm Post subject:
Re: Setting up MPIO |
|
|
When you install iSCSI 2.0, you have an option to also install MPIO support
(it's not the default). You will need a target that supports the included
"device specific module" - not all do. In that case, the target vendor needs
to provide you with a DSM for their target.
The iSCSI initiator package ships with a users guide, that should be your
first resource. MPIO setup is discussed there.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:8F970464-8F8A-47EB-ABB1-6FCA189B9BE5@microsoft.com...
| Quote: | Hi Everybody,
I'm a newbie to MPIO. My setup includes a MS initiator talking to an iSCSI
Target, and the initiator system has two NICs. I'm trying to setup
multi-path
between the initiator and the target.
The MS Initiator GUI says the the "Enable multi-path" has to be enabled
only
if iSCSI multipath software is installed on the system. Where do I get
this
software from?
Also, does the target need to have multi-path capability enabled?
Any suggestions on how to go about this are appreciated. Thanks ...
|
|
|
| Back to top |
|
|
sbs
Guest
|
| Posted:
Thu Oct 13, 2005 11:22 pm Post subject:
Re: Setting up MPIO |
|
|
Hi Jeff,
Thanks for the reply.
Since I want to setup MPIO with the soft initiator running over the NICs and
not an ISCSI HBA, we dont need a DSM on the Initiator end, but just the MPIO
module, right? And as you said, it comes with the MS Init 2.0, but when I try
to install the iSCSI Init 2.0, the option for installing MPIO support is
disabled. Do I need to have some license to have that option available? How
can I get that?
I did look into the MS init 2.0 before, as far as I remember, it only
explains what MPIO or MCS is, but not exactly about the software required or
the setup. I'll take another look into it.
Thanks once again ..
"Jeff Goldner [MS]" wrote:
| Quote: | When you install iSCSI 2.0, you have an option to also install MPIO support
(it's not the default). You will need a target that supports the included
"device specific module" - not all do. In that case, the target vendor needs
to provide you with a DSM for their target.
The iSCSI initiator package ships with a users guide, that should be your
first resource. MPIO setup is discussed there.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:8F970464-8F8A-47EB-ABB1-6FCA189B9BE5@microsoft.com...
Hi Everybody,
I'm a newbie to MPIO. My setup includes a MS initiator talking to an iSCSI
Target, and the initiator system has two NICs. I'm trying to setup
multi-path
between the initiator and the target.
The MS Initiator GUI says the the "Enable multi-path" has to be enabled
only
if iSCSI multipath software is installed on the system. Where do I get
this
software from?
Also, does the target need to have multi-path capability enabled?
Any suggestions on how to go about this are appreciated. Thanks ...
|
|
|
| Back to top |
|
|
Jeff Goldner [MS]
Guest
|
| Posted:
Fri Oct 14, 2005 8:16 am Post subject:
Re: Setting up MPIO |
|
|
MPIO consists of three drivers and a DSM. We ship all of this with iSCSI 2.0
but the DSM is not guaranteed to work with all targets - hopefully you have
a logoed target. Some will require a unique DSM provided by the vendor to
get the full benefit of multipathing. Also, if your target supports MCS,
that is a simpler approach when used with NICs (not HBAs).
I'm not sure why this is showing disabled when you try to install, I'll
check into that. No extra licenses are required.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:F6269DA6-3990-4746-982E-A8231F88000B@microsoft.com...
| Quote: | Hi Jeff,
Thanks for the reply.
Since I want to setup MPIO with the soft initiator running over the NICs
and
not an ISCSI HBA, we dont need a DSM on the Initiator end, but just the
MPIO
module, right? And as you said, it comes with the MS Init 2.0, but when I
try
to install the iSCSI Init 2.0, the option for installing MPIO support is
disabled. Do I need to have some license to have that option available?
How
can I get that?
I did look into the MS init 2.0 before, as far as I remember, it only
explains what MPIO or MCS is, but not exactly about the software required
or
the setup. I'll take another look into it.
Thanks once again ..
"Jeff Goldner [MS]" wrote:
When you install iSCSI 2.0, you have an option to also install MPIO
support
(it's not the default). You will need a target that supports the included
"device specific module" - not all do. In that case, the target vendor
needs
to provide you with a DSM for their target.
The iSCSI initiator package ships with a users guide, that should be your
first resource. MPIO setup is discussed there.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:8F970464-8F8A-47EB-ABB1-6FCA189B9BE5@microsoft.com...
Hi Everybody,
I'm a newbie to MPIO. My setup includes a MS initiator talking to an
iSCSI
Target, and the initiator system has two NICs. I'm trying to setup
multi-path
between the initiator and the target.
The MS Initiator GUI says the the "Enable multi-path" has to be enabled
only
if iSCSI multipath software is installed on the system. Where do I get
this
software from?
Also, does the target need to have multi-path capability enabled?
Any suggestions on how to go about this are appreciated. Thanks ...
|
|
|
| Back to top |
|
|
sbs
Guest
|
| Posted:
Fri Oct 14, 2005 11:37 pm Post subject:
Re: Setting up MPIO |
|
|
Jeff,
I figured out why the option for installing MPIO is disabled. This is
probably because I was trying to install it on a WinXP box. It installed fine
on a Windows 2003 server.
I have switched to a EMC AX100SCi Target which I think is logoed. It
probably supports MCS too (I have to check) but I do want to try MPIO
specifically.
Now after installing MPIO, the devices are displayed as MPIO capable, and I
do see a GUI for configuring MPIO in the device details page of the MS
initiator. It shows one path to the target. Can you tell me how how I can add
an additional path to the target so that when I pull out the cable from one
NIC, the connection can be reinstated over the other NIC? Both the NICs that
I have on the system are on the same subnet as the target.
Thanks ....
"Jeff Goldner [MS]" wrote:
| Quote: | MPIO consists of three drivers and a DSM. We ship all of this with iSCSI 2.0
but the DSM is not guaranteed to work with all targets - hopefully you have
a logoed target. Some will require a unique DSM provided by the vendor to
get the full benefit of multipathing. Also, if your target supports MCS,
that is a simpler approach when used with NICs (not HBAs).
I'm not sure why this is showing disabled when you try to install, I'll
check into that. No extra licenses are required.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:F6269DA6-3990-4746-982E-A8231F88000B@microsoft.com...
Hi Jeff,
Thanks for the reply.
Since I want to setup MPIO with the soft initiator running over the NICs
and
not an ISCSI HBA, we dont need a DSM on the Initiator end, but just the
MPIO
module, right? And as you said, it comes with the MS Init 2.0, but when I
try
to install the iSCSI Init 2.0, the option for installing MPIO support is
disabled. Do I need to have some license to have that option available?
How
can I get that?
I did look into the MS init 2.0 before, as far as I remember, it only
explains what MPIO or MCS is, but not exactly about the software required
or
the setup. I'll take another look into it.
Thanks once again ..
"Jeff Goldner [MS]" wrote:
When you install iSCSI 2.0, you have an option to also install MPIO
support
(it's not the default). You will need a target that supports the included
"device specific module" - not all do. In that case, the target vendor
needs
to provide you with a DSM for their target.
The iSCSI initiator package ships with a users guide, that should be your
first resource. MPIO setup is discussed there.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:8F970464-8F8A-47EB-ABB1-6FCA189B9BE5@microsoft.com...
Hi Everybody,
I'm a newbie to MPIO. My setup includes a MS initiator talking to an
iSCSI
Target, and the initiator system has two NICs. I'm trying to setup
multi-path
between the initiator and the target.
The MS Initiator GUI says the the "Enable multi-path" has to be enabled
only
if iSCSI multipath software is installed on the system. Where do I get
this
software from?
Also, does the target need to have multi-path capability enabled?
Any suggestions on how to go about this are appreciated. Thanks ...
|
|
|
| Back to top |
|
|
Jeff Goldner [MS]
Guest
|
| Posted:
Sat Oct 15, 2005 6:07 am Post subject:
Re: Setting up MPIO |
|
|
Sorry, I should have figured out the issue with XP :(
For AX100, you should use PowerPath 1.1 which I believe ships with the
array. This requires a vendor-supplied DSM (included in 1.1) and their
instructions.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:0DEB5E84-295C-4F36-B6B6-32C71FFE2F3C@microsoft.com...
| Quote: | Jeff,
I figured out why the option for installing MPIO is disabled. This is
probably because I was trying to install it on a WinXP box. It installed
fine
on a Windows 2003 server.
I have switched to a EMC AX100SCi Target which I think is logoed. It
probably supports MCS too (I have to check) but I do want to try MPIO
specifically.
Now after installing MPIO, the devices are displayed as MPIO capable, and
I
do see a GUI for configuring MPIO in the device details page of the MS
initiator. It shows one path to the target. Can you tell me how how I can
add
an additional path to the target so that when I pull out the cable from
one
NIC, the connection can be reinstated over the other NIC? Both the NICs
that
I have on the system are on the same subnet as the target.
Thanks ....
"Jeff Goldner [MS]" wrote:
MPIO consists of three drivers and a DSM. We ship all of this with iSCSI
2.0
but the DSM is not guaranteed to work with all targets - hopefully you
have
a logoed target. Some will require a unique DSM provided by the vendor to
get the full benefit of multipathing. Also, if your target supports MCS,
that is a simpler approach when used with NICs (not HBAs).
I'm not sure why this is showing disabled when you try to install, I'll
check into that. No extra licenses are required.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:F6269DA6-3990-4746-982E-A8231F88000B@microsoft.com...
Hi Jeff,
Thanks for the reply.
Since I want to setup MPIO with the soft initiator running over the
NICs
and
not an ISCSI HBA, we dont need a DSM on the Initiator end, but just the
MPIO
module, right? And as you said, it comes with the MS Init 2.0, but when
I
try
to install the iSCSI Init 2.0, the option for installing MPIO support
is
disabled. Do I need to have some license to have that option available?
How
can I get that?
I did look into the MS init 2.0 before, as far as I remember, it only
explains what MPIO or MCS is, but not exactly about the software
required
or
the setup. I'll take another look into it.
Thanks once again ..
"Jeff Goldner [MS]" wrote:
When you install iSCSI 2.0, you have an option to also install MPIO
support
(it's not the default). You will need a target that supports the
included
"device specific module" - not all do. In that case, the target vendor
needs
to provide you with a DSM for their target.
The iSCSI initiator package ships with a users guide, that should be
your
first resource. MPIO setup is discussed there.
"sbs" <sbs@discussions.microsoft.com> wrote in message
news:8F970464-8F8A-47EB-ABB1-6FCA189B9BE5@microsoft.com...
Hi Everybody,
I'm a newbie to MPIO. My setup includes a MS initiator talking to an
iSCSI
Target, and the initiator system has two NICs. I'm trying to setup
multi-path
between the initiator and the target.
The MS Initiator GUI says the the "Enable multi-path" has to be
enabled
only
if iSCSI multipath software is installed on the system. Where do I
get
this
software from?
Also, does the target need to have multi-path capability enabled?
Any suggestions on how to go about this are appreciated. Thanks ...
|
|
|
| Back to top |
|
|
Jan Hugo Prins
Guest
|
| Posted:
Mon Oct 17, 2005 4:17 pm Post subject:
Re: Setting up MPIO |
|
|
On Fri, 14 Oct 2005 11:37:04 -0700, sbs wrote:
| Quote: | Jeff,
I figured out why the option for installing MPIO is disabled. This is
probably because I was trying to install it on a WinXP box. It installed fine
on a Windows 2003 server.
I have switched to a EMC AX100SCi Target which I think is logoed. It
probably supports MCS too (I have to check) but I do want to try MPIO
specifically.
Now after installing MPIO, the devices are displayed as MPIO capable, and I
do see a GUI for configuring MPIO in the device details page of the MS
initiator. It shows one path to the target. Can you tell me how how I can add
an additional path to the target so that when I pull out the cable from one
NIC, the connection can be reinstated over the other NIC? Both the NICs that
I have on the system are on the same subnet as the target.
|
When you want to use multipath on iSCSI you should make sure that the 2
nics are in different subnets. So your SPA and SPB should also in
different subnets. You have to create a subnet for every path that leads
to your iSCSI San.
Jan Hugo Prins |
|
| Back to top |
|
|
Eric Bursley [MVP]
Guest
|
| Posted:
Mon Oct 17, 2005 4:17 pm Post subject:
Re: Setting up MPIO |
|
|
The AX100 as well as all Clariion devices are active / passive devices.
Which means a lun owned by SPA can not be access by SPB unless the lun is
trespassed to SPB. Then the lun could be access by SPB, but not SPA. With
the AX100i, there is 1 NIC port per SP, therefore you can implement failover
between SP's, but not load balance.
Eric Bursley
eric at bursley dot net
Microsoft MVP
RHCE, MCSE, BCFP, EEIE-CS, ESCE-CS
GPG Signature:
Key fingerprint = CEAE CF3A 3876 7ECE 9DA7 946F DA9F DDCA C392 6DCB
"Jan Hugo Prins" <jhp@jhprins.org> wrote in message
news:pan.2005.10.17.11.49.32.400519@jhprins.org...
| Quote: | On Fri, 14 Oct 2005 11:37:04 -0700, sbs wrote:
Jeff,
I figured out why the option for installing MPIO is disabled. This is
probably because I was trying to install it on a WinXP box. It installed
fine
on a Windows 2003 server.
I have switched to a EMC AX100SCi Target which I think is logoed. It
probably supports MCS too (I have to check) but I do want to try MPIO
specifically.
Now after installing MPIO, the devices are displayed as MPIO capable,
and I
do see a GUI for configuring MPIO in the device details page of the MS
initiator. It shows one path to the target. Can you tell me how how I can
add
an additional path to the target so that when I pull out the cable from
one
NIC, the connection can be reinstated over the other NIC? Both the NICs
that
I have on the system are on the same subnet as the target.
When you want to use multipath on iSCSI you should make sure that the 2
nics are in different subnets. So your SPA and SPB should also in
different subnets. You have to create a subnet for every path that leads
to your iSCSI San.
Jan Hugo Prins
|
|
|
| Back to top |
|
|
sbs
Guest
|
| Posted:
Wed Nov 02, 2005 1:25 am Post subject:
Re: Setting up MPIO |
|
|
Just came back from a vacation...thanks for all the replies. I am able to use
MPIO now. What I did not know earlier was how I could login into the target
again. With MPIO enabled, I was expecting a second instance of the same
target to appear, but it is just required to login into the same target
again. That did not occur to me because the service complains that I have
already logged in to this target via another session if MPIO is not enabled.
I dint realise that it is possible to do it when MPIO is enabled.
Thanks once again ....
"Eric Bursley [MVP]" wrote:
| Quote: | The AX100 as well as all Clariion devices are active / passive devices.
Which means a lun owned by SPA can not be access by SPB unless the lun is
trespassed to SPB. Then the lun could be access by SPB, but not SPA. With
the AX100i, there is 1 NIC port per SP, therefore you can implement failover
between SP's, but not load balance.
Eric Bursley
eric at bursley dot net
Microsoft MVP
RHCE, MCSE, BCFP, EEIE-CS, ESCE-CS
GPG Signature:
Key fingerprint = CEAE CF3A 3876 7ECE 9DA7 946F DA9F DDCA C392 6DCB
"Jan Hugo Prins" <jhp@jhprins.org> wrote in message
news:pan.2005.10.17.11.49.32.400519@jhprins.org...
On Fri, 14 Oct 2005 11:37:04 -0700, sbs wrote:
Jeff,
I figured out why the option for installing MPIO is disabled. This is
probably because I was trying to install it on a WinXP box. It installed
fine
on a Windows 2003 server.
I have switched to a EMC AX100SCi Target which I think is logoed. It
probably supports MCS too (I have to check) but I do want to try MPIO
specifically.
Now after installing MPIO, the devices are displayed as MPIO capable,
and I
do see a GUI for configuring MPIO in the device details page of the MS
initiator. It shows one path to the target. Can you tell me how how I can
add
an additional path to the target so that when I pull out the cable from
one
NIC, the connection can be reinstated over the other NIC? Both the NICs
that
I have on the system are on the same subnet as the target.
When you want to use multipath on iSCSI you should make sure that the 2
nics are in different subnets. So your SPA and SPB should also in
different subnets. You have to create a subnet for every path that leads
to your iSCSI San.
Jan Hugo Prins
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in