welcome: please sign in

Diff for "Hardware"

Differences between revisions 75 and 78 (spanning 3 versions)
Revision 75 as of 2008-02-20 18:42:11
Size: 4984
Editor: MichaelOlson
Comment: Easy to remember
Revision 78 as of 2008-02-20 18:58:43
Size: 5082
Editor: ClintonEbadi
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from NewSystemHardware
Line 4: Line 3:
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. This page collects information on the hardware that we have installed or plan to install at Peer1 as part of our hosting infrastructure.
Line 8: Line 7:
= deleuze: fileserver, static HTML content = = Peer1 =

This is a list of the stuff that is colocated at Peer1.

=
= deleuze: fileserver, static HTML content ==
Line 20: Line 23:
= abulafia: shell server = == abulafia: shell server ==
Line 27: Line 30:
= mire: dynamic web content = == mire: dynamic web content ==
Line 33: Line 36:
 * RAM: 1 GB  * RAM: 5 GB (initial 2x512M and additional 2x2G)
Line 41: Line 44:
= krunk: secondary KDC and AFS server = == krunk: secondary KDC and AFS server ==
Line 51: Line 54:
= Other components = == Other components ==
Line 53: Line 56:
== Switch == === Switch ===
Line 86: Line 89:
== Serial console == === Serial console ===
Line 91: Line 94:
== IP KVM == === IP KVM ===
Line 94: Line 97:
== Standard KVM == === Standard KVM ===
Line 96: Line 99:

= Tech.Coop =

This is a listing of the (virtual) machines colocated at Tech.Coop.

This page collects information on the hardware that we have installed or plan to install at Peer1 as part of our hosting infrastructure.

TableOfContents()

Peer1

This is a list of the stuff that is colocated at Peer1.

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

  • Processor: 1 x 900 MHz
  • RAM: 512 MB
  • Disks: 40 GB RAID 1 (2 x 40 GB 7200 RPM ATA drives)
  • Extra: 3Ware 6400 PCI ATA RAID controller

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

http://docs.sun.com/source/817-5248-20/index.html http://www.sun.com/servers/entry/v20z/images/gallery/full/img_3.jpg

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

  • KrunkInfoz

  • Donated by: Adam Megacz
  • Model: Sun Netra
  • Processor:
  • RAM:
  • Disks:
    • 2 x 200GB Unknown RPM and Manufacturer

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

Other components

Switch

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.
-Shaun

ES380 AC Power Specs:

  • Input current: 1.5A to 100 AC
  • Input voltage (rms): 100 to 240 VAC at 47 to 63 Hz
  • Power consumption: 150 W
  • Thermal rating: 1000 BTU/hr maximum

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]

IP KVM

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.

Tech.Coop

This is a listing of the (virtual) machines colocated at Tech.Coop.

Hardware (last edited 2021-04-17 15:58:03 by ClintonEbadi)