- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- AIX, EVA, MPIO and round robin load balancing
Disk Enclosures
1748176
Members
4211
Online
108758
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
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
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
10-01-2008 09:41 AM
10-01-2008 09:41 AM
AIX, EVA, MPIO and round robin load balancing
I'm reading this in an AIX connectivity guide for EVA systems:
Load Balancing (roundrobin)
Load balanced I/O is now supported. Set the attribute “algorithm” to roundrobin
in addition to setting “reserve_policy” to no_reserve for each hdisk in
order for load balanced I/O to access the array Lun.
and:
algorithm fail_over The load balancing algorithm, “fail_over”, will send all IO
over a single path. All other paths are standby paths. The
load balancing algorithm “round_robin” will send I/O over
all available paths. The attribute, reserve_policy, will need to
be set to “no_reserve” for round_robin to work.
However, in the SAN Reference Guide, September edition:
Sidan 183 i SAN Reference guide, September 17 edition
Table 88 IBM AIX SAN configuration rules:
• When using active/active or active/passive for EVA storage systems, zoning is
required to limit each IBM server HBA access to one controller port per controller,
except for Secure Path for IBM AIX. For specific Secure Path zoning requirements,
contact an HP storage representative.
These two rules seem to contradict each other. If I were to use round robin I/O, wouldn't that mean every other I/O would go to the not owning HSV controller? This is possible, but I'd do the I/O across the mirror port.
Load Balancing (roundrobin)
Load balanced I/O is now supported. Set the attribute “algorithm” to roundrobin
in addition to setting “reserve_policy” to no_reserve for each hdisk in
order for load balanced I/O to access the array Lun.
and:
algorithm fail_over The load balancing algorithm, “fail_over”, will send all IO
over a single path. All other paths are standby paths. The
load balancing algorithm “round_robin” will send I/O over
all available paths. The attribute, reserve_policy, will need to
be set to “no_reserve” for round_robin to work.
However, in the SAN Reference Guide, September edition:
Sidan 183 i SAN Reference guide, September 17 edition
Table 88 IBM AIX SAN configuration rules:
• When using active/active or active/passive for EVA storage systems, zoning is
required to limit each IBM server HBA access to one controller port per controller,
except for Secure Path for IBM AIX. For specific Secure Path zoning requirements,
contact an HP storage representative.
These two rules seem to contradict each other. If I were to use round robin I/O, wouldn't that mean every other I/O would go to the not owning HSV controller? This is possible, but I'd do the I/O across the mirror port.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2008 04:07 PM
10-02-2008 04:07 PM
Re: AIX, EVA, MPIO and round robin load balancing
Charles,
That information about zoning to one port of each controller was a restriction for Secure Path some time ago. With the last release of Secure Path for AIX (2.0D SP3), you could present all EVA host ports to the AIX server and Secure Path would choose one host port from each controller. But keep in mind that Secure Path for AIX only supported active-passive.
The information you mentioned above seems to be backward. The single EVA port per HBA only applied to Secure Path and it has never applied to MPIO or AntemetA.
As for MPIO's round_robin load balancing, you could combine path priorities with round_robin to bias I/O to specific host ports on the owning controller.
Best regards,
Bret
That information about zoning to one port of each controller was a restriction for Secure Path some time ago. With the last release of Secure Path for AIX (2.0D SP3), you could present all EVA host ports to the AIX server and Secure Path would choose one host port from each controller. But keep in mind that Secure Path for AIX only supported active-passive.
The information you mentioned above seems to be backward. The single EVA port per HBA only applied to Secure Path and it has never applied to MPIO or AntemetA.
As for MPIO's round_robin load balancing, you could combine path priorities with round_robin to bias I/O to specific host ports on the owning controller.
Best regards,
Bret
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