Need Help with Hyper-V iSCSI Multipathing Setup

0
50
Asked By SkyHighWizard42 On

I'm working on a setup with a failover cluster using two Hyper-V hosts with Windows Server 2022, connected directly to an HPE MSA 2060. However, I'm having trouble getting iSCSI multipathing to work properly. Here's my current setup:

- HV-01 and HV-02 each have two iSCSI connections, but HV-02 isn't functioning, so I'm focusing on HV-01.
- HV-01 is connected to the MSA2060 with IPs 10.10.10.11 and 10.10.10.12 for iSCSI respectively, while the MSA2060 has various ports configured with IPs like 10.10.10.1 and 10.10.20.1.
- MPIO is installed and configured, but I'm having issues activating multipath sessions for the second half of my connections.
- For network configuration, I'd like advice on whether it's acceptable to have only IPv4 enabled, and if I have the DNS and WINS settings correctly set up. If both hosts are connected on the same iSCSI subnet, should they be able to ping each other? Currently, they can only ping the MSA, not each other. What am I missing?

3 Answers

Answered By NetSage88 On

Have you checked how your MPIO is set up? Are you using a round-robin configuration? It might be worth revisiting that because each NIC should ideally support multiple paths to connected ports on the MSA. If you're directly connected without a switch, that could limit your paths down to one per NIC. Just a thought, make sure your connections can actually communicate with all iSCSI addresses from each host's iSCSI addresses.

Answered By DataDiveHunter On

It sounds like you might be missing out on having a dedicated iSCSI switch. In your current setup, the direct connections could restrict the paths. And about your network configuration, if you've mixed the IPs up, that can definitely cause communication issues between hosts.

Answered By TechGuru99 On

Double-check your IP assignments because your hosts need to be set correctly for multipath to function. If they can't ping each other, that could hint at an IP misconfiguration. Also, make sure your physical network setup is configured to allow traffic between those IPs. A simple PowerShell script could help you test the connectivity options.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.