Difference between revisions of "AlphaServer ES45"
(Created page with "thumb|BOB:: and DOUG:: a pair of AlphaServer ES45's == Configuration == {| class="wikitable" !scope="row" align="right"|Node Name |BOB:: and DOUG:...") |
|||
| Line 3: | Line 3: | ||
{| class="wikitable" | {| class="wikitable" | ||
!scope="row" align="right"|Node Name | !scope="row" align="right"|Node Name | ||
| − | |BOB | + | |BOB:: |
|- | |- | ||
!scope="row" align="right"|Node Number | !scope="row" align="right"|Node Number | ||
| − | |42.10 | + | |42.10 |
|- | |- | ||
!scope="row" align="right"|Machine | !scope="row" align="right"|Machine | ||
| Line 12: | Line 12: | ||
|- | |- | ||
!scope="row" align="right"|Model | !scope="row" align="right"|Model | ||
| − | | | + | |DY-68AAA-BA |
|- | |- | ||
!scope="row" align="right"|Serial | !scope="row" align="right"|Serial | ||
| − | | | + | |4216JSPZA094 |
|} | |} | ||
| + | {| class="wikitable" | ||
| + | !scope="row" align="right"|Node Name | ||
| + | |DOUG:: | ||
| + | |- | ||
| + | !scope="row" align="right"|Node Number | ||
| + | |42.11 | ||
| + | |- | ||
| + | !scope="row" align="right"|Machine | ||
| + | |AlphaServer ES45 | ||
| + | |- | ||
| + | !scope="row" align="right"|Model | ||
| + | |DA-68DAA-AL | ||
| + | |- | ||
| + | !scope="row" align="right"|Serial | ||
| + | |4144JSPZA085 | ||
| + | |} | ||
| + | |||
== Documentation == | == Documentation == | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 16:57, 9 November 2021
Configuration
| Node Name | BOB:: |
|---|---|
| Node Number | 42.10 |
| Machine | AlphaServer ES45 |
| Model | DY-68AAA-BA |
| Serial | 4216JSPZA094 |
| Node Name | DOUG:: |
|---|---|
| Node Number | 42.11 |
| Machine | AlphaServer ES45 |
| Model | DA-68DAA-AL |
| Serial | 4144JSPZA085 |
Documentation
| EK-ES240-PD.B01 | Alpha ES40 Tower and Pedestal Basic Installation |
| EK-ES240-RG.B01 | AlphaServer ES40 Rackmount System Installation Guide |
| EK-ES240-RN.C01 | AlphaServer ES40 Release Notes |
| EK-ES240-SV.A01 | AlphaServer ES40 Service Guide |
| EK-ES240-UG.B01 | AlphaServer ES40 and AlphaStation ES40 Owner's Guide |
| EK-ES240-UI.B01 | AlphaServer ES40 and AlphaStation ES40 User Interface Guide |
| EK-ES4M2-UP.A01 | AlphaServer ES40 Model 1 to Model 2 Upgrade |
Pictures
CPU and memory cage
Memory boards
Two CPUs
Closeup of memory board
CPU board
CPU board label
PCI card cage
3X-PBXGG-AA VGA video card (front)
3X-PBXGG-AA video card (back)
DS-KGPSA-CX fibre channel card (1st) (front)
DS-KGPSA-CX fibre channel card (1st) (back)
3X-DEGXA-TB gigabit ethernet card (front)
3X-DEGXA-TB gigabit ethernet card (back)
SN-KZPCA-AX SCSI controller card (front)
SN-KZPCA-AX SCSI controller card (back)
DS-KGPSA-CX fibre channel card (2nd) (front)
DS-KGPSA-CX fibre channel card (2nd) (back)
3X-DEGXA-TR gigabit ethernet card (front)
3X-DEGXA-TR gigabit ethernet card (back)
Adaptec ASC-39160 SCSI controller (front)
Adaptec ASC-39160 SCSI controller (back)
Model/Serial tag
ES40 alive and well in the data centre
Notes
2013/01: The Compaq ES40 arrived in my collection after I made a Cisco router purchase from a computer recycling company in Duncan, BC. During a discussion, my interest in antique DEC computers was mentioned, and I was offered this machine for little more than the cost of ground shipping. From the dust and dirt, I'm sure it had been sitting around their warehouse for quite some time.
I agreed to take the machine sight-unseen, so I wasn't sure what to expect when the crate arrived at the office. Surprisingly, after a good cleaning, the machine was in perfect working order. There were no drives in the machine, so I populated the drive cages with various sizes of drives I had lying around.
At 8U, the machine is a little large for my garage collection, so it's currently located in the data center I manage, where it will probably live until I need the rack space for a paying customer.
After learning about DEC's Galaxy system, I decided to experiment with hardware partitioning. The machine arrived with two of everything (CPUs, ethernet controllers, SCSI controllers, etc) so I'm sure this is how the machine was originally configured. It now lives as two HECnet nodes, FRICK:: and FRACK:: (named after the nick-names my wife has given to our two dogs).