• Books
  • Movies
  • Sports
    • Football
    • Hockey
  • Tech
    • Apps
    • Networking
    • Virtualization
    • Linux
      • CentOS
      • Ubuntu
    • MacOS
    • Microsoft
  • Recipes
  • Family
  • About
  • Home.Lab Project
    • Home.Lab Hardware
      • Storage CentOS Server (Phoenix)
      • Centos Hypervisor (Cyclops)
      • CentOS Hypervisor (Wolverine)
      • Homegrown SuperMicro ESXi Hypervisor (Deadpool)
    • Networking
      • Hypervisor Network
      • Juniper SSG5 Configuration
      • Security Zone Configuration
    • Virtual Machines
      • Black Widow (RHEL 6.4)
    • Hypervisor Technologies
    • Tutorials
      • Creating an iSCSI Target in CentOS 6.4
      • Managing Linux Hypervisors through Windows
Home » Tech » Linux » CentOS » Home.Lab Hardware

Home.Lab Hardware

Posted on July 23, 2013 by Vitaly Posted in CentOS, Linux, Networking, Tech, Ubuntu, Virtualization

This page will include a rundown of the hardware that I will be using for my sandbox. Bear in mind that you do not need the most recent hardware and you don’t need huge amounts of ram and resources. The key for what we are trying to learn here is how everything works together and how to test IT technologies. If you have to use Core 2 Duo processors or can only afford 4GB of ram, use them! Start with machines that use a single core and 1GB of ram to start. The servers that you are virtualizing may run slower and you may discover latency when overloading hardware, but that won’t stop the learning process.

For my home.lab environment, I will be using the following hardware:

  1. Dell R510 Server 1 (Phoenix) 
    • Primary Purpose: Storage
    • CPU: Single E5520 Xeon CPU (quad core)
    • RAM: 8GB DDR3 ECC Registered
    • First RAIDset: Two 160GB SATA drives in RAID1 (Operating System)
    • Second RAIDset: Three 2TB SATA drives in RAID5 (NFS Share)
    • Third RAIDset: Three 2TB SATA drives in RAID5 (iSCSI Share)
    • Ethernet: Bonded quad NIC (bond0) for storage network
    • Ethernet: Bonded dual NIC (bond1) for management network
    • Ethernet: Single NIC for Dell iDRAC/IPMI
  2. Dell R510 Server 2 (Cyclops)
    • Primary Purpose: Hypervisor
    • CPU: Dual E5530 Xeon CPUs (quad core)
    • RAM: 32GB DDR3 ECC Registered
    • First RAIDset: Two 160GB SATA drives in RAID1 (Operating System)
    • Ethernet: Singlel NIC (em2) for storage network
    • Ethernet: Single NIC (em1) for management network
    • Ethernet: Single NIC for Dell iDRAC/IPMI
  3. Dell R510 Server 3 (Wolverine)
    • Primary Purpose: Hypervisor
    • CPU: Dual L5520 Xeon CPUs (quad core)
    • RAM: 32GB DDR3 ECC Registered
    • First RAIDset: Two 160GB SATA drives in RAID1 (Operating System)
    • Ethernet: Dual NICs (bond0)  for storage network
    • Ethernet: Dual NICs (bond1) for management network
    • Ethernet: Single NIC for Dell iDRAC/IPMI
  4. SuperMicro Homegrown Server 1 (Deadpool)
    • Primary Purpose: Hypervisor
    • CPU: Single Xeon E5620 (quad core)
    • RAM: 24GB DDR3 ECC Registered
    • OS Drive: 40GB Intel SSD
    • Ethernet: Single NIC for storage network
    • Ethernet: Single NIC for management network
  5. HP Procurve 1800-24G ethernet switch (Storm) – Ultimate goal will be to have a stacking pair of switches down the road when doing more high-availability setups.
  6. Minuteman Power PDU (Thor)
  7. Juniper SSG-5 firewall (Loki) – will go into interface and zone/vlan setups deeper in the networking section.

I bet you’re wondering, why does one hypervisor have bonded NICs and the other doesn’t? Cash flow! One is obviously less redundant than the other, but I wanted to do the bonds as part of some networking technologies I want to learn as well (such as LACP and NIC failover). Will touch upon those in their individual write-ups for each device. Will attach a picture here of the physical setup once I get my Visio in order and get my schematic the way I like it.

« Creating an iSCSI Target in CentOS 6.4
Hypervisor Technologies »

Leave a comment Cancel reply

Your email address will not be published. Required fields are marked *

Around the Way

July 2013
M T W T F S S
1234567
891011121314
15161718192021
22232425262728
293031  
« Apr   Aug »

Recent Posts

  • Getting spice client console working in Virt-Manager for Mint 19
  • Using RealVNC in Windows to connect to a KVM session
  • Switching the default user when using SSH
  • X-Men Apocalypse Movie Review
  • Getting Virt-Manager working in Ubuntu 16.04 LTS bypassing openssh-askpass

Old School

  • September 2018
  • August 2016
  • July 2016
  • June 2016
  • April 2016
  • February 2016
  • January 2016
  • August 2013
  • July 2013
  • April 2013
  • February 2013
  • December 2012
  • November 2012

Archives

  • September 2018
  • August 2016
  • July 2016
  • June 2016
  • April 2016
  • February 2016
  • January 2016
  • August 2013
  • July 2013
  • April 2013
  • February 2013
  • December 2012
  • November 2012

Recent Posts

  • Getting spice client console working in Virt-Manager for Mint 19
  • Using RealVNC in Windows to connect to a KVM session
  • Switching the default user when using SSH
  • X-Men Apocalypse Movie Review
  • Getting Virt-Manager working in Ubuntu 16.04 LTS bypassing openssh-askpass
© Chubby Apple