MPIO best practice in Windows 2022

[amarcelin]

Considering the following: Server A is an HP proliant 380L using Windows 2022 and SAN A is an MSA 2060

Server A: 192.168.1.10, 192.168.1.11

SAN A: 192.168.1.20, 192.168.1.21

What is the optimal MPIO path configuration?

a)

192.168.1.10 ----> 192.168.1.20
192.168.1.10 ----> 192.168.1.21
192.168.1.11 ----> 192.168.1.20
192.168.1.11 ----> 192.168.1.21

OR

b)

192.168.1.10 ----> 192.168.1.20
192.168.1.11 ----> 192.168.1.21

Any other consideratios?

Also, when configuring MPIO, a Multiple Connected Session (MCS) path is automatically created. Is that normal? Can I delete it?

Thinks for your help.

[olivia36mcd]

For optimal MPIO path configuration with your HP ProLiant 380L and MSA 2060, Option A is generally recommended:

Option A: 192.168.1.10 ----> 192.168.1.20 192.168.1.10 ----> 192.168.1.21 192.168.1.11 ----> 192.168.1.20 192.168.1.11 ----> 192.168.1.21

This setup provides redundancy and load balancing, ensuring better performance and failover capabilities

Regarding Multiple Connected Session (MCS), it is normal for it to be automatically created when configuring MPIO. MCS allows combining several connections inside a single session for performance and failover purposes. You can delete it if it's not needed, but it's usually beneficial to keep it for redundancy and improved performance.

[Tam92]

Hi,

Hope the queries have been answered. If you have any further queries please let us know?

Thanks,
TAM

[amarcelin]

Hello

I guess I have not asked the correct question. I have seen many posts
cautioning on using different use scenarios of MPIO paths.

What is the recommended best practice by HP on how to configure MPIO path
for optimal performance.

I'm using Proliant servers and MSA 2060 SAN.

Thanks

Adias

[Mr_Techie]

---

@amarcelin wrote:
Hello

I guess I have not asked the correct question. I have seen many posts
cautioning on using different use scenarios of MPIO paths.

What is the recommended best practice by HP on how to configure MPIO path
for optimal performance.

I'm using Proliant servers and MSA 2060 SAN.

Thanks

Adias

---

Hi,

You can follow the below instruction. 

Install MPIO Feature on the Host OS[ Make sure MPIO feature is installed on your host operating system]
HPE provides a custom MPIO DSM specifically optimized for MSA arrays. Download and install the HPE MPIO DSM for MSA Storage from the HPE Support Center.
Check ALUA is enabled on the MSA 2060 array. ALUA ensures proper failover and load balancing by providing information about the optimal paths to the storage controllers.
Use the Round Robin with Subset policy (if available) for balancing the I/O load across active/optimized paths.
Configure a Minimum of Two Paths per Host- Connect each server to both MSA controllers using separate paths (e.g., via redundant SAN switches).
Make sure MSA 2060 firmware, ProLiant server drivers (e.g., HBA and NIC drivers) and MPIO DSM software are upto date.
Configure the proper disk timeout value for storage communication, make sure the retry and failover settings are aligned with the MSA SAN documentation.
Use the HPE MSA Storage Management Utility (SMU) or the HPE OneView/InfoSight monitoring tools to Monitor path utilization and Identify any failed paths or performance bottlenecks.

I hope this helps!. I'm not a expert here, I searched and found the info for you. Let me know how it goes.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".