Good Day Folks:I am in the process of turning up some Windows Server/SQL Failover clusters using the in-guest iSCSI method. Working as intended with one default NIC on each Windows Failover Cluster VM (when they are in the same subnet as the external services ip/segment). However I started looking at it more and wanted to tune this a bit. IE: Add a secondary NIC on these VMs on a say /24 that is not-routed and use this for the iSCSI traffic. Which in this KB on page 23 you reccomend. "Use a single subnet (broadcast domain) for iSCSI traffic. Avoid routing between the client initiator(s) and CVM target(s)."
http://go.nutanix.com/rs/031-GVQ-112/images/acropolis-block-services.pdfThat does not quite read correct to me, in that same PDF it states, "With the 4.7 AOS release, the data services IP address must be in the same subnet as the eth0 (management) network of the CVMs."So on the guest OS, I use the external data service IP for discovery, which is in the same segment as Prism, AH hosts, etc. How would I create a non route-able segment, for iSCSI traffic if the data services IP must be in the same MGMT network. Are we not just targeting the external services IP for the target discovery? Any help would be appreciated, just trying to understand that better.