Orion System News

13/08/06: Myrinet now available on nodes orion01-orion10, orion12-orion16, orion18, orion20-orion22, orion25-orion31.

14/07/06: Most nodes are now running again after 16 months downtime. Unavailable nodes are orion11, orion17, orion19, orion23, orion24. Node orion39 has network issues accessing SAPAC filesystems.

11/03/05: Due to a large scale water event Orion has been shutdown for the forseeable future. It will need to be relocated and tested before being rebooted.

20/02/03: Myrinet and power problems have been fixed.

04/02/03: There are some problems with power runs to the nodes. Some work will be done on this on Feb 5, which will require nodes orion09, orion18, orion31, orion40 to be shut down.

24/01/03: The Myrinet is not available until further notice due to a power supply failure. Currently the nodes are connected by Ethernet.

30/09/02: A patch was installed for the Myrinet software.

12/07/02: The latest version of the Myrinet software (GM 1.6) has been installed. This gives improved latency and bandwidth, and now supports both 32-bit and 64-bit executables.

12/06/02: Orion was rebooted to fix some lingering problems caused by the shutdown.

11/06/02: Orion was shut down due to an airconditioning failure.

09/11/01: All 40 nodes on Orion have been upgraded to Solaris 2.8, HPC ClusterTools 4.0, and the latest version of the Myrinet software. Sun MPI is now able to use the low-latency Myrinet GM protocol, but only for 64-bit executables. NOTE: 32-bit executables that use Sun MPI will not work.

Jobs should be submitted using the ClusterTools Runtime Environment (CRE).

Orion User's Guide