HomeLab

HomeLab

(Last update: 2023-10-07)

My HomeLab is split across multiple locations.

HomeLab #1: Germany, Frankfurt

This lab is a colocation at meerfarbig, hosting the more public-facing workload.

Host specifications:

  • Model: HPE ProLiant DL380 Gen9
  • CPU: 2x Intel Xeon E5-2673 v4 @ 2.30GHz (40 threads)
  • RAM: 384 GB DDR4 RAM (12x 32 GB)
  • Boot: Samsung 980 500 GB NVMe M.2 via NVMe PCIe x16 Adapter
  • Disks (via HPE Smart Array P840ar)
  • Disks (via HPE Smart HBA H240)
  • Dual PSU
  • NICs:
    • 2x HP Ethernet 1Gb 4-port 331i Adapter
    • 1x HP Ethernet 10Gb 2-port 530 FLR-SFP+ Adapter
  • Running VMware vSphere ESXi 7.0

HomeLab #2: Austria, Lower Austria

This might be the longest bit. It started with a HPE MicroServer Gen8… and somehow… it escalated quickly.

Compute cluster

Main workload

Two hosts, each one with following specs:

  • Model: HPE ProLiant DL380 Gen9
  • CPU: 2x Intel Xeon E5-2667 v4 @ 3.20GHz (32 threads)
  • RAM: 320 GB DDR4 RAM (10x 32 GB)
  • Boot: Samsung 980 500 GB NVMe M.2 via NVMe PCIe x16 Adapter
  • Disks (via HPE Smart Array P840ar)
  • Dual PSU to two independent UPS, with TPM 2.0
  • NICs:
    • 2x HP Ethernet 1Gb 4-port 331i Adapter (VM traffic)
    • 1x HP Ethernet 10Gb 2-port 530 FLR-SFP+ Adapter (NSX, vSAN)
  • Running VMware vSphere ESXi 7.0

Test cluster

This cluster is mainly for testing purposes and running vSAN 8.0 ESA.

Two hosts with specifications as follows each:

Storage

  1. Storage NAS

  2. Backup NAS

Network-wise:
Beside the hardware-wise isolation (Core/SAN), there are also about 15 VLANs across all switches to isolate various workloads from each other.

  1. Core Switch

    • Model: 2x HPE Aruba 2930F-24G-4SFP Switch (JL259A)
    • Those two switches are running in a VSF stack, so they are clustered for increased reduncancy.
    • Purpose: Main switch handling all workload like traffic from/to virtual machines, Internet traffic and OSPF/BGP to/from firewall. Uplink over fiber-optic cable to upper floor. Servers are wired to both switches for increased redundancy. LACP in use with Virtual Distributed Switches on the ESXi hosts.
  2. SAN Switch

    • Model: MikroTik CCR2004-1G-12S+2XS (12x 10 GBe, SFP+ + 2x 25 GBe)
    • Purpose: Mainly handling storage traffic for iSCSI, NSX-T, vSAN and vMotion.
  3. Management Switch

    • Model: HPE Aruba 2920-24G-4SFP Switch (J9726A)
    • Purpose: Handling management traffic like iLO to each HPE server, internet traffic from/to modem in separate VLAN, access points, Raspberry Pi GPS time server, etc. There is a uplink of 2x 1 GBe fibre-optic cable to the Core Switch.
  4. Firewall

    • 2x WatchGuard XTM 525 Appliances (unfortunately EOL)
  5. Access Switch

  6. Client Switches

Running following VMware products:

  • VMware ESXi + vCenter
  • VMware vSAN
  • VMware NSX
  • VMware NSX Advanced Load Balancer
  • VMware Horizon
  • VMware Unified Access Gateway
  • VMware AppVolumes
  • VMware vRealize Log Insight
  • VMware vRealize Operations Manager
  • VMware Cloud Director
  • Carbon Black

And in case you’re wondering: Yep, these are indeed 2x Philips Hue Light Strips for some cool lighting. Because of reasons.

Also, here are some pictures:

Servers SAN Switch + Firewall

Rack with Hue Lightstrips! Cat & me taking care about HomeLab