- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- BL490c & HP MPIO
BladeSystem - General
1752565
Members
5346
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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-29-2009 03:42 PM
тАО07-29-2009 03:42 PM
BL490c & HP MPIO
I have two BL460c units running Server 2008.
Using SSP, they both have access to the same LUN on a local MSA unit.
They both report the same drivers being used for the LUN under disk management:
"6.1.7100.0 (winmain_win7rc.090421-1700)"
One of them recongizes the drive as:
"COMPAQ MSA1000 VOLUME Multi-Path Disk Device"
The other only returns:
"COMPAQ MSA1000 VOLUME SCSi Disk Device"
Is there any explanation available for this behaviour?
Thank you,
-Aaron
Using SSP, they both have access to the same LUN on a local MSA unit.
They both report the same drivers being used for the LUN under disk management:
"6.1.7100.0 (winmain_win7rc.090421-1700)"
One of them recongizes the drive as:
"COMPAQ MSA1000 VOLUME Multi-Path Disk Device"
The other only returns:
"COMPAQ MSA1000 VOLUME SCSi Disk Device"
Is there any explanation available for this behaviour?
Thank you,
-Aaron
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2009 01:18 AM
тАО07-30-2009 01:18 AM
Re: BL490c & HP MPIO
This could be due to Zoning errors ?
Did you install the MPIO for EVA ?
You can see visible paths from MPIO Manager
Regards
Did you install the MPIO for EVA ?
You can see visible paths from MPIO Manager
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2009 11:32 PM
тАО07-30-2009 11:32 PM
Re: BL490c & HP MPIO
Aaron,
do you check this on one server at a time or do you have both servers online and possibly accesing that same LUN on the MSA ? If so, do those servers run some kind of cluster s/w ,otherwise this is a no-go because it could corrupt data on the disks since there is no reservation/locking mechanism in place.
Check with one sever powered on at a time and see what that gives you, maybe the first one sees the MSA LUN properly (since he was first) and the second one encounters some issue when trying to access the same LUN.
HTH
Kris
do you check this on one server at a time or do you have both servers online and possibly accesing that same LUN on the MSA ? If so, do those servers run some kind of cluster s/w ,otherwise this is a no-go because it could corrupt data on the disks since there is no reservation/locking mechanism in place.
Check with one sever powered on at a time and see what that gives you, maybe the first one sees the MSA LUN properly (since he was first) and the second one encounters some issue when trying to access the same LUN.
HTH
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2009 10:23 AM
тАО08-04-2009 10:23 AM
Re: BL490c & HP MPIO
To Pedersen:
Why would I need the MPIO for EVA? These are MSA units and would require the MPIO for MSAs no?
To Rombauts:
Fair point on the clustering.
Part of the issue is that this is all in an attempt to get the clustering software to work.
To get Microsoft server Clustering up & running on these boxes, I want to ensure it passes all the tests (because I've been told that's the only way to have any sort of functionality). The box that realizes these are MPIO drives passes it's tests, but the unit that does not realize they are MPIO devices fails. As it fails, the tests fail. Obviously a problem.
I will try with only one of the boxes turned on, see what happens and post another reply.
Thank you both so much,
-Aaron
Why would I need the MPIO for EVA? These are MSA units and would require the MPIO for MSAs no?
To Rombauts:
Fair point on the clustering.
Part of the issue is that this is all in an attempt to get the clustering software to work.
To get Microsoft server Clustering up & running on these boxes, I want to ensure it passes all the tests (because I've been told that's the only way to have any sort of functionality). The box that realizes these are MPIO drives passes it's tests, but the unit that does not realize they are MPIO devices fails. As it fails, the tests fail. Obviously a problem.
I will try with only one of the boxes turned on, see what happens and post another reply.
Thank you both so much,
-Aaron
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP