welcome: please sign in

Diff for "Hardware"

Differences between revisions 80 and 191 (spanning 111 versions)
⇤ ← Revision 80 as of 2008-03-02 21:40:23 →
Size: 5225
Editor: NathanKennedy
Comment:
← Revision 191 as of 2015-05-19 16:20:51 → ⇥
Size: 4608
Editor: ClintonEbadi
Comment: fritz has 24G of RAM since last year and deleuze is finally removed from service
Deletions are marked like this. Additions are marked like this.
Line 3: 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. This page collects information on the hardware that we have installed or plan to install as part of HCoop infrastructure.
Line 5: Line 5:
[[TableOfContents()]] <<TableOfContents>>
Line 9: Line 9:
This is a list of the stuff that is colocated at Peer1. Current pictures of the actual Peer1 cabinet are at [[OnSiteVisits/20130627]].
Line 11: Line 11:
== deleuze: fileserver, static HTML content ==
 * Donated by: Justin Leitgeb
 * Model: Dell PowerEdge 2850
 * Processor: 2 x 2.8 GHz Intel Xeon
 * RAM: 4 GB		 == fritz ==

FritzInfo

 * Location: Peer1
 * Model: Dell PowerEdge 2970
 * Processor: 2x Quad Core AMD Opteron™ 2372HE 2.1GHz 4x512K Cache 1Ghz HyperTrnsprt
 * RAM: 24GB (4x2GB + 4x4GB), 800MHz, Dual Ranked
 * 1x6 Backplane for 3.5-inch Hard Drives
 * Integrated SAS/SATA No RAID
 * Disks: system disks 2x 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in HotPlug Hard Drive , + AFS disks 2x 1 TB Western Digital in RAID 1
 * Redundant Power Supply with Dual Cords
 * Lan: Dual Embedded Broadcom® NetXtreme II 5708 Gigabit Ethernet NIC
 * Form factor: 2U
 * OS: Debian Squeeze
 * User logins: no
 * Source: purchase from Dell store, 2x 1 TB disks from Newegg

'''Use: AndrewFileSystem fileserver, MitKerberos kdc, KernelVirtualMachine host'''

=== KVM: navajos ===

 Location:: virtual machine on fritz
 Allocated Resources:: 6 processors, 6G RAM, 60G storage
 Operating System:: Debian Wheezy AMD64
 User Logins:: No
 Intended Use:: Apache hosting and dynamic web content, including HCoop web services
 Details:: ServerNavajos

=== KVM: bog ===

 Location:: virtual machine on fritz
 Allocated Resources:: 4 processors, 3G RAM, 30G storage
 Operating System:: Debian Wheezy AMD64
 User Logins:: Yes
 Intended Use:: Member shell and server hosting
 Details:: ServerBog

=== KVM: mccarthy ===

 Location:: virtual machine on fritz
 Allocated Resources:: 4 processors, 2G RAM, 45G storage
 Operating System:: Debian Jessie AMD64
 User Logins:: No
 Intended Use:: Mail server
 Details:: ServerMcCarthy
 
== kvm ==

 * Location: Peer1
 * Model: StarTech IP KVM
 * Source: Newegg?

 * [[KvmAccess]]
 * [[http://www.startech.com/Data/ProductManuals/SV1110IPEXT.pdf?c=US|StarTech manual]] ([[http://hcoop.net/~docelic/SV1110IPEXT.pdf|local copy]]).

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.


== hopper ==

 * Location: Peer1
 * Model: IBM xSeries 335
 * Processor: 2 x single-core P4 XEON 2.6Ghz with hyperthreading
 * RAM: 4 GB, 2x1 GB, 1x2 GB (3/4 slots, 8 GB Max, PC2100 ECC registered)
Line 17: Line 77:
  * 4 x 10K Seagate Cheetah SCSI drives, 73GB '''and'''
  * 2 x 10K Seagate Cheetah SCSI drives, 36GB
 * Extra: RAID kit, with battery, etc., 256 MB RAID cache, 2 power supplies
 * [https://dcse.dell.com/selfstudy/Associates_7_0/Enterprise/PowerEdge/PE2850/printer_friendly.asp Maintenance Manual for the PE 2850]
'''Intended use: fileserver and host for all services that don't involve dynamic content provided by non-admins. No user logins.'''		   * 2x SCSI Ultra 320 80 pin. SEAGATE - 5 YEARS MFG WARRANTY. CHEETAH 73.4GB 15000 RPM 80PIN ULTRA320 SCSI HARD DISK DRIVE. 16MB BUFFER 3.5 LOW PROFILE(1.0 INCH). ST373455LC
  * Floppy 3.5"
 * LAN: 2 x 10/100/1000
 * Ports: 3 x USB, 1 x serial, 2 x PCI-X
 * PSU: 1/1
 * Form factor: 1U
 * Dimensions: W 17.5 in / H 1.75 in / D 25.75 in / Weight 33 lbs
 * OS: Debian Squeeze
 * User logins: no
 * Name voting at https://members.hcoop.net/portal/poll?report=17
 * Source: US Ebay, seller lapkosoft. http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=300200776299
 * Real picture:{{http://hcoop.net/~docelic/hopper.hcoop.net.jpg}}
Line 23: Line 90:
== 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.'''		  * [[HopperServiceProcessor]]
 * [[http://www-947.ibm.com/systems/support/supportsite.wss/selectproduct?familyind=5105587&typeind=0&osind=0&continue.x=12&continue.y=13&brandind=5000008&oldbrand=5000008&oldfamily=5105587&oldtype=0&taskind=2&matrix=Y&psid=bm|IBM xSeries 335 Support Page]]
 * {{http://hcoop.net/~docelic/IBM_xSeries335_Front_0Bay.jpg}}
Line 30: Line 94:
== 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
 * Donated by: Ray Racine
 * Model: Sun Fire v20z
 * Processor: 1 x 1.6GHz AMD64 (Opteron)
 * RAM: 5 GB (initial 2x512MB and additional 2x2GB)
 * Disks: 2 x 36 GB Ultra320 SCSI (hot swap)
 * 1U
 * Ultra 320 SCSI controller embedded in mainboard
 * [http://onesearch.sun.com/search/docs/index.jsp?col=docs_en&locale=en&qt=Sun+Fire+v20z Search Sun for Product Documentation, including Maintenance and Troubleshooting Manuals for Sun Fire v20z]		 [[attachment:Back of hopper, taken 24feb09.jpg]]
[[attachment:Hopper card closeup, taken 24feb09.jpg]]
[[attachment:Inside hopper, taken 24feb09.jpg]]
Line 42: Line 98:
'''Intended use: dynamic web content and any other Internet services that involve running arbitrary code from members (including custom daemons, etc.)'''
Line 44: Line 99:
== Xanadu: shell server? ==
 * Donated by: NathanKennedy
 * Model: Dell PowerEdge 1650
 * Dual P3 1.4GHz
 * 2G RAM
 * 18GB SCSI HDD		 '''Use: Secondary KDC, secondary openafs volume and fileserver, and SpamAssassin'''
Line 51: Line 101:
== 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'''		 (The 1x2 GB RAM module was acquired from Newegg, and the two disks from ServerSupply. Purchases were made in Sep 2008, but ServerSupply took good 3 weeks to deliver).
Line 61: Line 103:
== Other components ==
Line 63: Line 104:
=== Switch ===
We are proceeding under the assumption that we'll use ShaunEmpie's donation (see HardwareDonations), a Nortel (Baystack) 380 switch. He says:		 = Linode =
Line 66: Line 106:
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. == outpost ==
Line 68: Line 108:
VLAN Configuration Proposal:  * Location: Linode (hosted at UK data center)
 * Model: Xen VM
 * Processor: 8 cores (1x priority?)
 * RAM: 1024 MB
 * Disk: 40 GB
 * OS: Debian wheezy
 * User logins: no
Line 70: Line 116:
{{{
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:		 '''Use: secondary DNS on a different subnet, all tasks requiring remote location.'''
Line 91: Line 118:
 * 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
Line 96: Line 119:
=== 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.		 = Awaiting setup =
Line 99: Line 121:
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] None.
Line 101: Line 123:
=== 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].		 = Awaiting purchase =
Line 104: Line 125:
=== Standard KVM ===
We have a standard KVM to allow remote switching between servers as maintenance requires.		 We need a new KVM host and drives for staging offsite backups of openafs. See NewServerDiscussion2013
Line 107: Line 127:
= Tech.Coop =
Line 109: Line 128:
This is a listing of the (virtual) machines colocated at Tech.Coop. = Decommissioned =

See [[/Decommissioned]] for older machines

----
CategorySystemAdministration

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

Contents

  1. Peer1
    1. fritz
      1. KVM: navajos
      2. KVM: bog
      3. KVM: mccarthy
    2. kvm
    3. hopper
  2. Linode
    1. outpost
  3. Awaiting setup
  4. Awaiting purchase
  5. Decommissioned

Peer1

Current pictures of the actual Peer1 cabinet are at OnSiteVisits/20130627.

fritz

FritzInfo

  • Location: Peer1

  • Model: Dell PowerEdge 2970

  • Processor: 2x Quad Core AMD Opteron™ 2372HE 2.1GHz 4x512K Cache 1Ghz HyperTrnsprt

  • RAM: 24GB (4x2GB + 4x4GB), 800MHz, Dual Ranked
  • 1x6 Backplane for 3.5-inch Hard Drives
  • Integrated SAS/SATA No RAID

  • Disks: system disks 2x 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in HotPlug Hard Drive , + AFS disks 2x 1 TB Western Digital in RAID 1

  • Redundant Power Supply with Dual Cords

  • Lan: Dual Embedded Broadcom® NetXtreme II 5708 Gigabit Ethernet NIC

  • Form factor: 2U
  • OS: Debian Squeeze
  • User logins: no
  • Source: purchase from Dell store, 2x 1 TB disks from Newegg

Use: AndrewFileSystem fileserver, MitKerberos kdc, KernelVirtualMachine host

KVM: navajos

Location
virtual machine on fritz
Allocated Resources
6 processors, 6G RAM, 60G storage
Operating System
Debian Wheezy AMD64
User Logins
No
Intended Use
Apache hosting and dynamic web content, including HCoop web services
Details

ServerNavajos

KVM: bog

Location
virtual machine on fritz
Allocated Resources
4 processors, 3G RAM, 30G storage
Operating System
Debian Wheezy AMD64
User Logins
Yes
Intended Use
Member shell and server hosting
Details

ServerBog

KVM: mccarthy

Location
virtual machine on fritz
Allocated Resources
4 processors, 2G RAM, 45G storage
Operating System
Debian Jessie AMD64
User Logins
No
Intended Use
Mail server
Details

ServerMcCarthy

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.

hopper

Back of hopper, taken 24feb09.jpg Hopper card closeup, taken 24feb09.jpg Inside hopper, taken 24feb09.jpg

Use: Secondary KDC, secondary openafs volume and fileserver, and SpamAssassin

(The 1x2 GB RAM module was acquired from Newegg, and the two disks from ServerSupply. Purchases were made in Sep 2008, but ServerSupply took good 3 weeks to deliver).

Linode

outpost

  • Location: Linode (hosted at UK data center)
  • Model: Xen VM
  • Processor: 8 cores (1x priority?)
  • RAM: 1024 MB
  • Disk: 40 GB
  • OS: Debian wheezy
  • User logins: no

Use: secondary DNS on a different subnet, all tasks requiring remote location.

Awaiting setup

None.

Awaiting purchase

We need a new KVM host and drives for staging offsite backups of openafs. See NewServerDiscussion2013

Decommissioned

See /Decommissioned for older machines

CategorySystemAdministration

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