- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - Linux
- >
- General
- >
- RHEL and Multipath
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
06-07-2010 12:11 AM
06-07-2010 12:11 AM
I got a few Red Hat Enterpice Linux running on Blade 460c g6 servers. They boot from same EVA 4400, but they are in different Blade enclosures.
I haven't done the Blade enclosure or EVA installations my self.
Servers on the other enclosure sees EVA from 4 paths.
mpath3 (3600143800648ac570000500000730000) dm-3 HP,HSV300
[size=300G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=100][active]
\_ 0:0:0:4 sdd 8:48 [active][ready]
\_ 1:0:0:4 sdl 8:176 [active][ready]
\_ round-robin 0 [prio=20][enabled]
\_ 0:0:1:4 sdh 8:112 [active][ready]
\_ 1:0:1:4 sdp 8:240 [active][ready]
And from the other only two
mpath0 (3600143800648ac570000500001120000) dm-0 HP,HSV300
[size=20G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=100][active]
\_ 0:0:0:1 sda 8:0 [active][ready]
\_ 1:0:0:1 sdb 8:16 [active][ready]
Difference in hardware is that the later has Virtual Connect and the first one connects directly to FC switches.
Is this normal "feature" of Virtual Connect or is there something wrong with my environment?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-07-2010 01:39 PM
06-07-2010 01:39 PM
Re: RHEL and Multipath
I could be wrong, but I think this means someone has forgotten to allow your VC enclosure to see the second (stand-by?) controller of the EVA. If your EVA has a controller failure, the first enclosure could automatically switch to the other controller, but the VC enclosure would then be left without access to storage.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-08-2010 09:04 PM
06-08-2010 09:04 PM
Re: RHEL and Multipath
This is mostlikey why there is only two channels. I have no idea if this is redudant or not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-09-2010 12:15 AM
06-09-2010 12:15 AM
SolutionWe don't have EVA storage systems, but I understand there is an "evainfo" tool that should help in verifying the connectivity to EVA. It can identify the EVA controller and port IDs associated with each /dev/sd* device.
Please see these threads:
https://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1432579
(download link, free HP Passport registration required)
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1173146
(usage example)
Unfortunately, there seems to be no separately-packaged evainfo for Linux, but it should be available in the EVA Command View media kit. Your storage admins should have such a media kit: it might be easiest to ask them to give you the Linux version of the evainfo tool.
If the evainfo tool is not available, it might be possible to dig out the equivalent information by using generic Linux tools like sdparm. Some reading of EVA documentation will probably be required too (you have to find out how EVA encodes the controller & port identifiers to the the SCSI attributes of the LUN.)
With the information produced by the evainfo tool, you could easily produce informative problem reports for your SAN admins, for example "My system X sees the LUNs through EVA's controller B only: there is no connectivity from any HBA of system X to controller A".
MK
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP