- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: HP MPIO Windows2008
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2009 12:21 PM
тАО07-17-2009 12:21 PM
HP MPIO Windows2008
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2009 11:39 AM
тАО07-20-2009 11:39 AM
Re: HP MPIO Windows2008
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2009 11:49 AM
тАО07-20-2009 11:49 AM
Re: HP MPIO Windows2008
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2009 04:02 PM
тАО07-20-2009 04:02 PM
Re: HP MPIO Windows2008
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2009 10:40 PM
тАО07-20-2009 10:40 PM
Re: HP MPIO Windows2008
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2009 04:11 AM
тАО07-21-2009 04:11 AM
Re: HP MPIO Windows2008
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.