[blog@kernstock.net]$

portfolio, computer & more

#HomeLab

I was asked a few times from friends and William Lam from virtuallyghetto collects how HomeLabs from the community looks like, so I thought I’m just going ahead writing a "short" page about my current setup. Latest update was 2020-11-03.

To be more exact, my HomeLab consists out of multiple HomeLabs – three, to be precise. Starting with the most boring one…

HomeLab #1: Germany, Nuernberg.

This is a Dell PowerEdge R730 hosted in Germany, Nuernberg in a datacenter at Hetzner Online GmbH. As this is a rented server, no picture is available – you could search for the server model in a search engine of your choice… but it looks like how a server looks like.

Server Specs:

  • CPU: Intel Xeon E5-2620 v4
  • RAM: 64 GB DDR4 RAM
  • Storage with Hardware-RAID
    • 4x 2 TB Enterprise HDD (RAID10)
    • 2x 250 GB Datacenter SSD (RAID1)
  • Running VMware vSphere ESXi 7.0b

Purpose: As the server runs in a datacenter, this server mostly only runs services which should be publicly accessible – like my mailserver, webserver (where also this website runs on), Nextcloud instance, etc.

HomeLab #2: Ireland, Cork. (Home)

Due to lack of space and possibilities wiring every single corner of the appartment (hi landlord!), the HomeLab is placed on my desk just next to me. Therefore it really needs to be as quiet as possible – otherwise I might drive crazy at some point.

A more detailed list…

Probably the most interesting bits:

  1. Compute Node 1

  2. Compute Node 2

  3. Compute Node 3

  4. Synology NAS

  5. Firewall

    • Model: NRG Systems IPU672
    • Actually a re-branded Qotom Mini PC.
    • Running OPNsense.
    • CPU: Intel Core i5-7200U Kaby Lake-U
    • RAM: 8 GB DDR4 Crucial RAM
    • Disk: 250 GB Samsung SSD SATA
    • Purpose: Doing firewall stuff.

  6. UPS: APC Back-UPS PRO 900VA

Less interesting ones:

  1. Synology DS1513+
    • Purpose: No idea. Owned by my flat mate. Attached to my UPS.
  2. Philips Hue Bridge
  3. RIPE Atlas Probe
  4. Raspberry Pi 4 (4 GB RAM)
  5. Raspberry Pi 3B+

Network-wise:

  1. NETGEAR GS116E 16-Port Gigabit Ethernet Smart Managed Plus Network Switch
  2. NETGEAR GS108Tv2 8-Port Gigabit Smart Managed Pro Switch
  3. WLAN: Unifi AP-AC-LR

If someone cares, some pictures:

Leaning Tower of IT Switchy, the Switch

HomeLab #3: Austria, Lower Austria.

This might be the longest bit. It started with a HPE MicroServer Gen8… and somehow… it escalated quickly. Make a new coffee before you continue reading, might take a while!

So… where do we start…

  1. 3x Identical Compute Nodes, each one consists out of:

    • Model: HPE ProLiant DL360p Gen8
    • CPU: 2x Intel Xeon E5-2650L v2
    • RAM: 96 GB DDR3 RAM
    • Disks (via HPE Smart Array H240 HBA)
    • Dual PSU to two independent UPS
    • NICs: 2x HPE Quad Port 1 GBe, redundancy to two switches
    • Running VMware vSphere ESXi 7.0 U1, booting from SD-Card
    • Purpose: Doing all kind of workload. Using DRS/HA.

  2. Storage

  3. Total of 3x UPS

    • 2x APC Smart-UPS SMT – SMT1500I 1500VA with Network Management Module
      • Each UPS is connected to each server: Each server has Dual-PSU, connected to two differenet UPS for increased redundancy. Also the clustered switches are each connected to a different UPS.
      • Purpose: Powering all servers, storage and redundant switches.
    • 1x APC Back-UPS PRO 900VA
      • Purpose: Powering less essential stuff like modem, Raspberry Pi, management switch, etc.

  4. Raspberry Pi 3B + GPS HAT

    • Powered via PoE from Management Switch, to be able to restart if if required. Secondly it’s also powered through UPS that way.
    • Purpose: NTP Timeserver via Chrony. Pulls current time from GPS satellites, using PPS (Pulse-per-second) for most accurate timing.

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: 2x HPE Aruba 2920-24G-4SFP Switch (J9726A)
    • Those two switches are clustered using dedicated cluster modules on the back-side of the switches. The modules are connected via one DAC cable over 40 GBe.
    • Purpose: Mainly handling storage traffic for iSCSI and vSAN, but also vMotion and internal NSX traffic are going through this switch. Servers are wired to both switches for increased redundancy.

  3. Management Switch

    • Model: HP Switch 3500yl 24G (J8692A)
    • 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

On said HomeLab also runs:

  • VMware vSphere vCenter
  • VMware vSAN
  • VMware NSX-T
  • VMware NSX Intelligence
  • VMware Horizon
  • VMware AppVolumes
  • VMware vRealize Log Insight
  • VMware vRealize Operations Manager

And in case you’re wondering: Yes, that are 2x Philips Hue Light Strips. Because of reasons.

Also, here are some pictures:

Front side…
ESXi hosts One ESXi node
Back side…
Network - back-side of the rack Firewall & SAN cluster

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