HP MPIO Windows2008

[FerSAN_2]

Hi,
I am trying to install the HP Mpio downloaded from HP site for Windows 2008 x64 and EVA8000, and when is installing the error "0XBC9" is displayed. And doesn´t finish with the installation.
Somebody have any idea what the problem is about?

Thanks.

[Vinod Kumar Yadav]

Hi,


Frist Present the Vdisk from EVA SAN Storage & then install the latest HP Secure Path MPio.

Then it will sucessfully install other wise please find the below link to get the latest Mpio.

http://h18006.www1.hp.com/products/sanworks/secure-path/

http://h18006.www1.hp.com/products/sanworks/secure-path/index.html

Thanks
Vinod Kumar Yadav



Thanks

[Uwe Zessin]

There is no "Secure Path MPIO" (such a product does not exist) or "Secure Path for Windows for the EVA8000" available. And if you had checked the URLs you've found, you should have seen that Secure Path is not available for Windows 2008.

The EVA8000 is an active/active array and it looks like FerSAN has correctly identified the need to install the full-featured MPIO for the EVA4x00/6x00/8x00.

[Vinod Kumar Yadav]

Hi,

I for got the EVA 3000 is Active Passive Storage that what is told related to Secure Path.

The EVA 8000 is Active Active SAN Storage which use the AutoPath for MPIO


You can download the latest version of Autopath - MPIO & then install.


thanks
Vinod

[Uwe Zessin]

The EVA-3000 can run with active/active firmware, too and then requires a full-featured MPIO on Windows.


There is no "AutoPath for MPIO". "Autopath" was pre-merger HP's "umbrealla name" to cover its own multipath products for the VA7000 series and XP series storage arrays (which are active/active).

The "Autopath" product for HP-UX was put unter the "Compaq classic" umbrella name "Secure Path" and called "Secure Path for active/active arrays". It was also enhanced to provide support for EVAs on HP-UX,
but all this has nothing to do with FerSAN's problem.

[FerSAN_2]

Thanks to both.
But the problem was fixed.
Although the MPIO was installed with an administrator privilege account, the account was not "administrator", and this was the problem.
Thanks for your answers.