Is SecurePath/XP (aka AutoPath) bundled with XP12000?

[Alzhy]

Or is it purchased separately?

If we are licensed for SecurePath/EVA are we also licensed to use SecurePath/XP?

[Vincent Fleming · Accepted solution]

No, it's not bundled. It's licensed per server.

However, it's not required with XPs. Standard MPIO implementations work with XP's, as well as PVLinks, and VxVM's DMP feature.

There aren't different versions for XP and EVA. One SecurePath does it all, so, Yes, you can are licensed to use it with EVA and XP at the same time.

Cheers,

Vince

[Alzhy]

So if we are licensed for SecurePath/EVA - we're also licensed to use SecurePath/XP - which is essentially the AutoPath product? Starting with SecurePath 3.0D - the CD/tar bundle allows selection of which SecurePath to install.

And which so corrects your statement that "There aren't different versions for XP and EVA". - there is SecurePath for the EVA and SecurePath for the XP (AutoPath).

BTW - if one simply uses Base VxVM (DMP suppressed) with the XP12K - can one have path protection? I know DMP is out of the equation but can AutoPath reliably protect VxVM managed volumes/filesystems?

[Vincent Fleming]

Nelson,

Actually, as of version 3.0E, the XP, VA and EVA versions of the product have converged:

Secure Path v3.0E for HP-UX supports hosts connected to the HP StorageWorks Enterprise Virtual Array (EVA5000, EVA3000), HP StorageWorks Modular Array 8000 (MA8000)/Enterprise Modular Array 12000 (EMA12000)/Enterprise Modular Array 16000 (EMA16000), RAID Array 8000 (RA8000)/Enterprise Storage Array 12000 (ESA12000), and Modular Array 6000 (MA6000) storage solutions. This release also supports hosts connected to the StorageWorks XP48/512, XP256, XP128/1024, XP12000, VA740012000, /7100, and the VA7410/7110.

See the quickspecs for more details:

http://h18000.www1.hp.com/products/quickspecs/11402_na/11402_na.html

In addition, it also supports VxVM, so you can create disk groups with SecurePath devices. (also noted in the quickspecs)

Cheers,

Vince

[Alzhy]

Vincent,

it started actually with 3.0D, they're converged alright BUT still 2 separately installable software(but have they been tested for co-existence?). The following is what one gets during a SecurePath 3.0D/3.0e install:

Please select the software that you want to install

1) Secure Path Ver 3.0E for HP-UX for HSx class of Disk Arrays
2) Secure path Ver 3.0E for HP-UX for XP, VA and SV3000 Disk Arrays
3) Exit Secure path Installation

Enter Choice [1/2/3]:

So there's SecurePath/EVA and another SecurePath/XP (which is really the AutoPath product -- you do not use spmgr commands but autopath commands on XP Luns..)

VxVM (Base & Full ) works fine with SecurePath/EVA and EVA LUNs. However, VxVM (base and Full) does not work with SecurePath/XP (aka AutoPath) and XP LUNs -- during cable pull tests, AutoPath does not correctly interface with VxVM (even if DMP is disabled on the VxVM side).

Full VxVM + XP LUNs (minus SecurePath/XP or AutoPath) works as we have DMP enabled and active and protecting paths to the XP...

[Vincent Fleming]

Sigh. My apologies - I haven't actually installed those versions myself...

That's what I get for relying on Marketing documentation. :-)

As for their testing for co-existance - I'm not sure, but since they made it a "converged" product, I'm guessing that they are capable of co-existance - but I'm not going to say it's so this time. :-)

I saw your other posting with the panic messages... have you opened a case with Support regarding this?

I'm checking what other info I can find interally... let's see...

Is this the System disk (root)???

I'll keep looking and post anything that I think may help...

[Vincent Fleming]

(No points for this please)

For those reading this, Nelson's mention of a VxVM<->AutoPath interaction problem has a patch available, as noted in this article:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=825386

Cheers,

Vince