Announcement

Collapse
No announcement yet.

Hyper-V 2016 Lab setup

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hyper-V 2016 Lab setup

    Hi all,

    I am building a home hyper-V lab on Windows 2016 TP4.

    I have 2 (3) physical boxes of reasonably decent spec.

    Box 1
    ================================================== =============
    1 x dual xeon 3ghz
    128gb ram
    14TB of disk (which can be iscsi presented as it is hosted on adaptec 6805Q card)
    2 physical nics
    Windows 2016 TP4 installed with hyper-V

    Box 2
    1​ x I7 3.8hgz
    64GB ram
    ​12TB of disk (which can also be iscsi presented as it is hosted on 3ware 9500s card)
    2 physical nics
    Currently dual booting (windows 10/ / Windows 2016 TP4)

    I also have a bunch of cisco kit which I am trying to avoid having to leave on as it is too noisey.

    Box 3
    An Atom server small form factor low power (low performance)
    2gb ram
    1 x atom process

    I guess I could use the latter as a firewall / online DC or something if needed.

    I have no real need for HA other than to prove my understanding of how HA works in a Hyper-V setup.

    ================================================== ===============
    I was planning on running a number of networks such as in the following setup.

    1 x internal (2016 environment)
    1 x internal (2012 environment)
    1 x external (routed connection to internet)

    ================================================== ===============
    VM1.

    3 nic machine to route / firewall between 2012 / 2016 / internet

    ================================================== ================
    VM 10-20 (2016)

    DC, DHCP, DNS
    SCCM
    EXCHANGE
    SCORCH
    SCOM
    SQL (AAG)

    ================================================== ================
    VM 20-30 (2012)

    DC, DHCP, DNS
    SCCM
    EXCHANGE
    SCORCH
    SCOM
    SQL (AAG)

    My questions are around how I present the networking layer across 2 physical hosts as I would in VMWare with vswitch / dv port groups etc. Also if anyone sees any flaws in the intended way forward. My other concerns is how I secure the physical hosts from the internet layer. Ideally more machines would be good but I am trying to limit the kit to what I have already.

    cheers.

    Ron


Working...
X