I'm fairly new to NIC Teaming.. So I apologize if I’m not making any sense while describing this. I’ve, of course, set up plenty of simple Active/Active NIC teams for our servers without any issues since it’s pretty straight forward.
It looks like we are trying to save money, but cutting back on switches/cables/ports while still providing redundancy. What sort of complicates things is we have a HUGE variety of Linux/Windows deployments from Server 2003, Red Hat, to Server 2008 (all flavors of all OS's). And every sever is multi-homed. Mostly HP servers DL3xx, DL5xx, but very old G3’s, to very new G7's .. etc. I'm talking well over 8,000 of these running in our data center. The upper management wants to configure the following (and I hope that I'm describing it correctly):
x2 - Catalyst 5000 Switches x1 NIC (Back-End network) using a single CAT5 cable. x1 NIC (Front-End network) using a single CAT5 cable. ---Both networks are completely separate
Active/Passive NIC teaming between both NICs (even though they reside on two completely separate subnets)
They plan on trunking multiple VLANs (Front-End and Back-End) to each switch to provide the redundancy. But I can’t wrap my head around how this would work in Windows (?) I can only assign a single IP to each NIC since they reside on different subnets. Network Engineers claim its somewhat possible but at the driver level, and that it won’t work on 2003 and sort-of works on Server 2008. I can’t seem to find any information on the internet on this.