Unsolved

This post is more than 5 years old

9 Posts

932

April 10th, 2008 23:00

Powerpath licence / failover questions

Hello
I´m using powerpath 5.1 (unlicenced) with win2003 , msiscsi and a Emc-cx3-20.

I have 4 iscsi ports configured on my cx3-20 (2 /SP)
I have 2 dedicated iSCSI NIC in my win 2003

SPA0 and SPB0 is on 192.168.204. network and SPA1 and SPB1 on 192.168.205. network

NIC 0 is on 192.168.204.
NIC 1 is on 192.168.205.

when i connect the SAN i can see 4 paths in powerpath and the path to SPA0 and SPB0 is marked active and SPA1 and SPB1 is marked unlicensed.

Now to the failover question:
Can i have failover from SPA0 to SPA1 (diffrent NIC) or can failover only be med within one NIC.
If i disconnect NIC 0 i loose the path to SPA0 and SPB0 , i would like powerpath to resume the connection on SPA1 and SPB1 but it´s not

As i pointed out i´m running unlicensed version of powerpath if this is a limitation.

Networkconfig:
SPA0 192.168.204.2
SPB0 192.168.204.3

SPA0 192.168.205.2
SPA1 192.168.205.3

NIC 0 192.168.204.20
NIC 1 192.168.205.20


/bjorn

341 Posts

April 10th, 2008 23:00

Hi Bjorn,

I believe you have hit a limitation with PowerPath using a basic-failover license.

You have two HBAs connected to his array but are using a basic-failover license in PowerPath. This is not supported -- please see emc114228. Basic-failover is supported in single-HBA environments only. That's most likely the reason PowerPath didn't fail across the SPs; it was confused as it had a single-HBA license but noted multiple SCSI bus connections to the array.
You will need to purchase a license, or go to a single-HBA environment as supported without a PowerPath license.

Conor

null

9 Posts

April 11th, 2008 00:00

Ok, many thanks..
/bjorn

9 Posts

April 11th, 2008 00:00

Thank you.

Just so its clear, Powerpath will never failover to NIC1 if my NIC0 goes down when i use Powerpath basic (unlicensed)

So there is no use for two Nics connected to iSCSI and PP-basic

341 Posts

April 11th, 2008 00:00

Exactly... Failover will only occur in the case of an SP failure, or backend storage failures.

0 events found

No Events found!

Top