HOST01 (that spike on the last device isn't abnormal) (see attached screencaps) It ran for 12 hours, so this is no isolated incident. HOST01 gets normal, expected results, whereas FS2 is very problematic. To test this, I setup PingPlotter (a wonderful tool) on HOST01 and FS2 and pinged devices on the local LAN and at each branch office. Ok great.įor some reason though, the Guest VMs are now getting horrible latency and are very loss-y. Checking this box seemed to speed up file transfers, as I would get 60-80MB/sec. Some searching around pointed to an option to set in each Guest VM > Network Adapter>Advanced Features>NIC Teaming>Enable. Initially, for some reason file shares wouldn't transfer at any normal acceptable LAN speeds. Hyper-V virtual switch manager is setup for External Connection type and uses the default "Microsoft Network Adapter Multiplexor Driver". I setup NIC teaming on HOST01 with the four available NICs to Switch Independent/Dynamic load balancing mode. We downgraded to 2012 R2, I'm not waiting for Datto to fix that issue). We probably shouldn't have installed a brand new server OS, but I like shiny things.
(Off topic, our Datto backup service does not work with Server 2016 yet. It's basically not doing anything, I was just getting the backup server configured on everything first. DC1 isn't really configured yet, nothing is joined to the domain. I have another VM running ubuntu 16.04 that I use for syslogs and another VM for Spiceworks. HOST01 basically only runs Hyper-V Manager, and one of the VMs (DC1) is running AD DS, DNS, and DHCP the other VM is a file server with print server and WSUS (FS2). My host os (HOST01) is running Windows 2012 R2 Std with two Windows 2012 R2 Std guest VMs.
0 kommentar(er)
