What is the hardware configuration of the test cluster?
| Number of cores | Processor Speed (GHz) |
Memory (GB) |
Available Memory (GB) |
Connectivity Type |
Node names | Node Properties |
Gateway Names |
| 6 (3 dual) | 2.0 | 2.0 | 1.8 | Myrinet | testoptnode1 - testoptnode3 | x86,opteron,myrinet | testoptgw1 |
| 12 (3 dual-dual) | 2.4 | 4.0 | 3.8 | Ethernet | testddnode1 - testddnode3 | x86,opteron | testddgw1 |
| 16 (8 dual) | 2.2 | 1.5 | 1.3 | Ethernet (testppcnode1-3 and 8) Myrinet (testppcnode4-7) |
testppcnode1 - testddnode8 | ppc64 | testppcgw1 |
Please note that there are no P4's in the test cluster because they are being taken out of the production cluster on March 10th, 2008.
How do I access the test cluster?
You can use ssh to log on to one of the gateways:ssh you@test[opt|dd|ppc]gw1.accre.vanderbilt.edu
Where are the contents of my home directory / scratch?
Your home directory on the test cluster, while it has the same name as on the production cluster, is NOT the same directory. Your production c luster home directory is, however, available to you by changing directories to /prod/home/you.
You can copy files from your production cluster home directory by executing:
cp /prod/home/you/your_file /home/you
Similarly, /scratch on the test cluster is not the same as /scratch on the production cluster. The production cluster scratch directories are available at /prod/scratch.
What operating system do the nodes in the test cluster run?
All gateways and compute nodes are running RHEL / CentOS 5 (64-bit).
What software packages are available on the test cluster?
You can list the available software packages by typing "pkginfo -l" Here is an updated list of all packages.How do I use the "pkginfo" utility?
"pkginfo" returns various compiler settings for the specified package or tool. If you type "pkginfo", it gives a list of installed packages and their brief description. The utility can be useful when you compile your application with existing libraries. For example, to find out the package include directory, simply use:
To link the libraries, use
pkginfo -p PACKAGE_NAME -L -lc (or -lc++, -lf77, -lf90 depending on the language that the application is written with.)
pkginfo -p PACKAGE_NAME --prefix returns the base directory of the package.
I submitted a job on the test cluster and it did not run. The same script works fine on the old cluster.
You should check the job script to make sure all the resource properties you specified are valid on the test cluster. Some of the previously valid propreties no longer apply to the new cluster, e.g. p4, due to hardware upgrade. You can find all available properties using:
Last modified: March 20 2008 13:30:24 CST.
