I'm not a network guy, but a system administrator by background. I find myself, now, the sole IT guy at a growing business.
(This turned into a long explanation to setup the question, which is at the bottom of the post.)
I have four hosts in a colocation rack, two Synology NAS devices.
Each host is running 2012 R2 Hyper-V.
Each host has four NICs: 3 1gb and 1 10gb.
We talk to the hosts via a PAN firewall/VPN, which fronts a juniper switch, using http, https, RDP, SSL.
When the plan for deployment was written, by a now-departed admin, we ran up a proof of concept using Debian and ...
The 10gb NICs were VLAN/Internal, reserved for internal use only: between the guest VMs, and to the NAS devices. The IPs here were assigned to 10.10.1.x block.
The 3 1gb NICs were teamed in VLAN/External, and were used exclusively for internet traffic. The hosts on this network were assigned IPs in our public /26 block.
Since then we've scaled back the number of hypervisors, switched from Debian to Server 2012 R2, added the PAN firewall/VPN.
I'm not sure the VLAN idea makes any sense, if it ever did. We've added the Firewall at the top of the rack, and we can now NAT the traffic.
And every time I describe this setup to network pros, they sort of look funny, like it's all needlessly complicated. I'd like to simplify this, if possible.
My idea is to give all hosts IPs in the same subnet, using a single VLAN. My sticky point is this;
I'd like to continue to have each hypervisor (and each guest vm) use the 10gb NIC to talk amongst themselves, and to the NAS devices, while sending 'external' traffic (web, RDP) on the 1gb nics.
This will let us do the data crunching and file writing as quickly as possible, which is the whole reason for the exercise.
How do I do that? Use routing on the hypervisor?
By request: from my whiteboard, to tiff.