Configuration of Server SAN with Failover clustering.

Hi, we are looking at some further guidance on setting up failover clustering on two Windows Servers 2019 connecting to a HP MSA2052 SAN.

•      The servers are DL380 Gen10 with 8 NIC ports.
•      The current wiring connections are shown below (we will redo this for redundancy on the controllers)
•      The MSA 2052 has two controllers, each controller has two connections on different subnets connecting to the two servers via one switch with two vlans. (Layer 2 switch)
•      The servers connect to a different production switch for normal data traffic.
•      The iScsi initiators and MPIO have been configured and both servers can see the storage volumes.
•      The Servers can both ping all four ip addresses on the 172.16.*.* subnets, the nics on the 172.16.*.* subnets, don’t have a default gateway configured as per guides we have been reading. Jumbo frames are set up on the iSCSI NICS and switch.
•      The servers are pingable via their full domain name from other devices on the 10.226.*.* production network. The servers are in the correct Server OU.
•      The servers currently don’t have a network setup for a heartbeat and migration.
•      The servers also have Teamed NICs setup for a virtual switch within HyperV manager

The failover clustering invalidate configuration wizard test is failing on:
At least two independent paths to storage target are recommended for each Test Disk
Test Disk 0 from node Server1 (shows FQDN) has 1 usable path to storage target
Test Disk 0 from node Server2 (shows FQDN) has 1 usable path to storage target
At least two independent paths to storage target are recommended for each Test Disk
Test Disk 1 from node Server1 (shows FQDN) has 1 usable path to storage target
Test Disk 1 from node Server2 (shows FQDN) has 1 usable path to storage target

However, we have created a cluster and everything comes up green.
Questions:
The first host that we created a cluster on prompted for an IP Address, we have currently assigned an IP Address from our Production subnet, but this may be wrong and should be on a separate VLAN, please advise.
The second host when entering the name of the cluster also looks good and we can see everything as expected.
Do we need to create a further separate subnet for a heartbeat and if so how is it configured within the software?

After this all correct, do I assume that the VM Guests are configured in HyperV manager and that the location of the Virtual disks points back to the IP address of the Cluster?

What is configured in the Hyper V Manager HyperV SAN Manager?

If possible, an explanation would be better than a URL link as we have already pretty much exhausted most guides found from internet searches. Sorry, i know its a lot of questions.Regards
Rick