welcome: please sign in

Revision 72 as of 2007-11-24 02:11:38

Clear message


This page collects information on the hardware that we have installed or plan to install at Peer1 as part of our hosting infrastructure. Some older discussion and similar stuff is on NewSystemHardwareArchive.


deleuze: fileserver, static HTML content

Intended use: fileserver and host for all services that don't involve dynamic content provided by non-admins. No user logins.

abulafia: shell server

Intended use: refurbished slightly to serve as a generic shell server and the only machine where usage not strictly related to "Internet hosting" is permitted.

mire: dynamic web content


Intended use: dynamic web content and any other Internet services that involve running arbitrary code from members (including custom daemons, etc.)

krunk: secondary KDC and AFS server

Intended use: secondary KDC and AFS server (backup) in event that the primary server (deleuze) goes down

Other components


We are proceeding under the assumption that we'll use ShaunEmpie's donation (see HardwareDonations), a Nortel (Baystack) 380 switch. He says:

It is not brand new but is working. Here is [http://vpit.net/es380-guide.pdf a guide] that I was able to find to give anyone interested a more in depth view of it.

VLAN Configuration Proposal:

With our new setup, I think it would be best to setup a few different
VLANs for different uses.  For anyone who is unfamiliar with the term, a
VLAN is a virtual lan.  It allows you to have completely separate networks
on the same switch.  This will allow us to setup a private network that
the public and peer1 would have no access to.  This could be handy for
database systems, NAS, backup servers, etc which you'd want to keep off
the public network.
Proposed Configuration:
VLAN 1.     Management VLAN - not used for normal traffic
VLAN 10.    Public VLAN - public/Peer1's network
VLAN 20.    Private VLAN - private subnet for inter-server traffic
For a starting point i think having ports 1-12 in VLAN 10 and ports 13-24
in VLAN 20 would be best.  The VLAN membership of a port can be changed
easily so these would not be set in stone.
The switch allows for many more VLANs than we'll ever need so if anyone
has a suggestion or need for another VLAN it would be trivial to setup.
Any questions/comments, let me know.

ES380 AC Power Specs:

Serial console

Some device to simulate local login over the Internet could be a life saver. JustinLeitgeb mentions a special card that Dell sells that would work with his donation.

There are also some really good KVM-over-IP devices out there fairly cheap these days. My provider has one and it works very well, although on the client side you have to use this ugly Windows ActiveX control. I'm sure by now there are KVM-over-IP boxes that speak plain VNC. These should be well under $500. [AdamMegacz]


The StarTech Server Remote Control External KVM over IP provides access to systems that may have a degraded network. It allows us to monitor Power-On Self Test (POST), configure BIOS/CMOS, and even reinstall operating system software. It must be connected to another multiple port KVM in order to have access to more than one server. See [http://www.startech.com/Data/ProductManuals/SV1110IPEXT.pdf?c=US manual].

Standard KVM

We have a standard KVM to allow remote switching between servers as maintenance requires.