Simplify / improve? testbed Hyper-V network connection setup
I asked a question some time ago that was about a Server testbed I set up.
It's still up and running and useful.
But I perhaps went about setting the static IP addresses on the Server VMs in an overly complicated and dysfunctional way.
So, I'd like to try once more to make it more "conventional".
The network diagram is attached.
The VM setup was the original concern. But I also notice something in the Hyper-V machine interface. So, I'll start with that:
There is a physical interface getting 192.168.13.103 via DHCP AND a virtual interface with static IP 192.168.13.4. Is that normal or is that odd? I wouldn't think that having two IP addresses used up would be normal. BOTH interfaces have the same MAC address.
Now, on to the VMs:
There's a dual-NIC PCI card.
The physical NICs have no configuration.
The virtual NICs are configured with static addresses and have been manually assigned the MAC addresses from the physical NICs they relate to (presumably that's the overkill?)
If this is wrong, then how might I change it so things will continue to work? I don't think that removing the MAC addresses from the VMs did the trick the first time I tried it.
Testbed-Configuration-2019_06_28.pdf
It's still up and running and useful.
But I perhaps went about setting the static IP addresses on the Server VMs in an overly complicated and dysfunctional way.
So, I'd like to try once more to make it more "conventional".
The network diagram is attached.
The VM setup was the original concern. But I also notice something in the Hyper-V machine interface. So, I'll start with that:
There is a physical interface getting 192.168.13.103 via DHCP AND a virtual interface with static IP 192.168.13.4. Is that normal or is that odd? I wouldn't think that having two IP addresses used up would be normal. BOTH interfaces have the same MAC address.
Now, on to the VMs:
There's a dual-NIC PCI card.
The physical NICs have no configuration.
The virtual NICs are configured with static addresses and have been manually assigned the MAC addresses from the physical NICs they relate to (presumably that's the overkill?)
If this is wrong, then how might I change it so things will continue to work? I don't think that removing the MAC addresses from the VMs did the trick the first time I tried it.
Testbed-Configuration-2019_06_28.pdf
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Suggestion: Look into WANEm (WAN Emulator).
Set up in a VM it can provide real world ISP/WAN link conditions.
Would it be helpful?
Set up in a VM it can provide real world ISP/WAN link conditions.
Would it be helpful?
ASKER
Philip Elder: Thanks for that. In this case, there is no WAN involvement really. Just normal web access and not too important except for updates, etc. as we go along with the testbed work. No WAN traffic being simulated.
ASKER
Thanks!!
ASKER
The inter-site link uses what I call an "interim subnet" (192.168.100.0/24) in order to access the inter-site links with a single interface per site and to route between subnets.
Inter-site/inter-subnet communication is a bit involved in the current peer-to-peer network - so the testbed is intended to demonstrate that our incremental approach to DC introduction in the production system is reasonably proven before implementation.
The Hyper-V platform is connected into my existing subnet structure - which could be separate as it is here.
The physical NICs represent physical NICs that are geographically separated and on different subnets in the real world system.
The VMs represent DCs that will be geographically separated in the planned real world system (and in that case, there will be multiple Hyper-V platforms).
But here, 2 DCs is adequate so they are supported on a single Hyper-V platform but with distinct physical NICs for the simulation.
Thanks for the link on Hyper-V articles!