SGI Origin 350

From Nekochan
Revision as of 04:22, 2 December 2009 by Ramq (Talk | contribs) (External link)

Jump to: navigation, search
SGI Origin 350 technical server.
SGI Origin 350, 8-brick config
SGI Origin 350, 8-brick config

The SGI Origin 350 computer system uses MIPS-based processors. Current models run at 600-1000MHz, with dual or quad CPU configurations available.

The Origin 350 is a member of the Chimera family (IP53), which includes Origin 350, Onyx 350, and the Tezro Rackmount. All three systems have the same basic hardware - the Origin 350 (Chimera Server) with a VPro card becomes the Onyx 350 (ChiBlade), and the ChiBlade can be configured into a Chimera Rackmount Workstation (Tezro Rack) using the L1's make rmws 1 command. The Chimera Rackmount Workstation cannot accept remote serial numbers, and therefore cannot be connected via NUMALink.

Each CPU brick has four PCI slots across two PCI busses. Each CPU brick also has a Fuel-style XIO slot, which can accept a DMediaPro DM3 card or a VPro graphics card. The first CPU brick in a system has a single PCI slot holding an IO9 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, audio I/O and a twisted pair Ethernet connection. Other kinds of bricks are available that are dedicated to disk storage or further PCI slots.

Different configurations

Base Compute Module - Includes an IO9, a SCA SCSI backplane (for disks), appropriate cables for disk backplane + IDE CDROM and a daughtercard that provides PS/2 keyboard/mouse and four additional serial ports

Expansion Compute Modules - These may or may not include the IO9+backplane, but lacks the daughtercard/keyboard/mouse/extra serial ports

Memory and PCI Expansion (MPX) Modules - Lacks the IO9+backplane and daughtercard/keyboard/mouse/extra serial ports.

A word of caution:

If you manage to get hold of an O350 brick (module), atleast check the backside of it to verify that it has an IO9 in the lowest slot. Without that you can't use the brick as a standalone system and you're forced to NUMAlink the brick to another brick and thus expanding an existing system. The IO9 BaseIO card is shared with the Tezro so one could still make the system a complete standalone machine, but without the SCSI backplane, disk sleds (and possibly CDROM) you can't boot the system using internal storage so you're forced to use the external SCSI port on the IO9 or use PCI cards for FibreChannel etc. --Ramq 08:50, 2 December 2009 (UTC)

Multiple bricks

Multiple bricks are co-ordinated at startup time via an L2 controller which communicates to the bricks via USB ports. The L2 controller is an external PPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink router (or NUMAlink module) which is another 2U rackmounted unit.

Power consumption

These values are measured using a Watt-meter off a standard 230V wall outlet:

L1 Only (machine off):     13W
Brick #1 on, idle:      215W (4x700MHz, 4GB RAM (8x512MB sticks), two SCSI harddrives, IO9 + extra GbE card)
Brick #1 on, load:      250W (4x700MHz, 4GB RAM (8x512MB sticks), two SCSI harddrives, IO9 + extra GbE card)
Brick #2 on, idle:      160W (4x700MHz, 1GB RAM (2x512MB sticks), no harddrives or PCI cards)
Brick #2 on, load:      185W (4x700MHz, 1GB RAM (2x512MB sticks), no harddrives or PCI cards)

External link