You must have at least 2 interfaces on the host, so that the frontend and backend traffic can be separated out. Having only one network will cause the engine monitoring, client traffic, gluster I/O traffic to all run together and interfere each other. To segregate the backend network, the gluster cluster is formed using the backend network addresses, and the nodes are added to the engine using the frontend network address.

>>>You must have at least 2 interfaces on the host, so that the frontend and backend traffic can be separated out.>>>This part is very clear to me. You need at least 2 NICs.

>>>Having only one network will cause the engine monitoring, client traffic, gluster I/O traffic to all run together and interfere each other. To segregate the backend network, the gluster cluster is formed using the backend network addresses, and the nodes are added to the engine using the frontend network address.>>> Ok, so you definitely need two IPs. What is not clear to me is, do you need to have the IPs in different subnets or can they be in the same subnet?

For reference, I was able to set this up with two IPs in the same subnet and it does seem to work. However, I have noted some slowness issues while connecting storage domains during startup and frequently get messages about needing to restart the HA agent. Usually it seems after I try to restart services I can get the system to recognize the engine storage domain and start the engine. I wonder if my problem is the fact that both my front and backend IPs are in the same subnet? Thanks for your advice.