| Table of Contents | ||
|---|---|---|
|
...
- In Jan. 2017, each of the 25 Condo nodes were upgraded to include two GTX 1080 GPU cards.
- In 2017, Condo Investments from RCEAS and CBE faculty added 22 nodes and 16 nVIDIA GTX 1080 GPU cards.
- In 2018, Condo Investments from RCEAS and CAS faculty added 24 nodes and 48 nVIDIA RTX 2080 TI GPU cards.
- In Mar. 2019, Condo Investments from RCEAS faculty added 1 node.
- In May-June September 2020, Condo Investments from CAS, RCEAS and COH faculty added 6 8 nodes.
As of Mar. 20192021
Processor Type | Number of Nodes | Number of CPUs | Number of GPUs | CPU Memory (GB) | GPU Memory (GB) | CPU TFLOPs | GPU TFLOPs | Annual SUs |
|---|---|---|---|---|---|---|---|---|
2.3 GHz E5-2650v3 | 9 | 180 | 10 | 1152 | 80 | 5.76 | 2.57 | 1,576,800 |
2.3 GHz E5-2670v3 | 33 | 792 | 62 | 4224 | 496 | 25.344 | 15.934 | 6,937,920 |
2.2 GHz E5-2650v4 | 14 | 336 | 896 | 9.6768 | 2,943,360 | |||
2.6 GHz E5-2640v3 | 1 | 16 | 512 | 0.5632 | 140,160 | |||
2.3 GHz Gold 6140 | 24 | 864 | 48 | 4608 | 528 | 41.472 | 18.392 | 7,568,640 |
| 2.6 GHz Gold 6240 | 6 | 216 | 1152 | 10.368 | 1,892,160 | |||
| 2.1 GHz Gold 6230R | 2 | 104 | 768 | 4.3264 | 911,040 | |||
89 | 2508 | 120 | 13312 | 1104 | 97.510 | 36.130 | 21,970,080 |
...
For example, a PI who estimates requiring 75K SUs annually will need to purchase 80K SUs for $800 annually. Suppose the PI only consumes 60K SUs during the allocation cycle, the unused 20K SUs will not rollover to the next allocation cycle, nor will the PI be reimbursed for the unused SUs. Alternatively, the PI can purchase the minimum 50K SUs for $500 and purchase additional increments of 10K whenever his/her allocation balance is low. The PI should consider that the availability of 10K increments for purchase is not guaranteed.
Revised policy for Accounts & Allocations
Logging into Sol
Sol can be accessed via SSH using a SSH Client. Linux and Mac users can login to Sol by entering the following command in a terminal:
| Code Block | ||
|---|---|---|
| ||
ssh username@sol.cc.lehigh.edu |
If you are off campus, then there are two options
- Start a vpn session and then login to Sol using the ssh command above
- Use ssh gateway as a jump host first and then login to Sol using the above ssh command on the ssh gateway prompt. If your ssh is from the latest version of openssh, then you can use the following command
| Code Block | ||
|---|---|---|
| ||
ssh -J username@ssh.cc.lehigh.edu username@sol.cc.lehigh.edu |
If you are using the ssh gateway, you might want to add the following to your ${HOME}/.ssh/config file on your local system
| Code Block | ||
|---|---|---|
| ||
Host *ssh HostName ssh.cc.lehigh.edu Port 22 # This is an example - replace alp514 with your Lehigh ID User alp514 Host *sol HostName sol.cc.lehigh.edu Port 22 User <LehighID> ProxyCommand ssh ssh nc %h %p |
to simplify the ssh and scp (for file transfer) command. You will be prompted for your password twice - first for ssh and then for sol
| Code Block | ||
|---|---|---|
| ||
ssh sol scp sol:<path to source directory>/filename <path to destination directory>/filename |
If you are using public key authentication, please add a passphrase to your key. Passwordless authentication is a security risk. Use ssh-agent and ssh-add to manage your public keys. See https://kb.iu.edu/d/aeww for details.
Windows users will need to install a SSH Client to access Sol. Lehigh Research Computing recommends MobaXterm since it can be configured to use the SSH Gateway as jump host. DUO Authentication is activated for faculty and staff on the SSH Gateway. If a window pops up for password enter your Lehigh password. The second pop up is for DUO, it only says DUO Login. Enter 1 for Push to DUO or 2 for call to registered phone.