Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel3

...

2404

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 62406216
1152
10.368
1,892,160

87

2.1 GHz Gold 6230R2104
768
4.3264
911,040


89

2508

120

1254413312

1104

9397.184510

36.130

21,059970,040080


System Configuration

Expand
title1 Interactive node
  • Two 2.3GHz 10-core Intel Xeon E5-2650 v3, 25M Cache
  • 128GB 2133MHz RAM
  • 1TB HDD
  • 10 GbE and 1 GbE network interface
  • CentOS 78.x


Expand
title9 Haswell GPU nodes
  • Two 2.3GHz 10-core Intel Xeon E5-2650 v3, 25M Cache
  • 128GB 2133MHz RAM
  • 1TB HDD
  • 100 Gb/s EDR Infiniband network interface
  • 10 GbE and 1 GbE network interface
  • 8 nodes with one EVGA Geforce GTX 1080 PCIE 8GB GDDR5
  • 1 node with two EVGA Geforce GTX 1080 PCIE 8GB GDDR5
  • CentOS 78.x 


Expand
title33 Haswell GPU nodes
  • Two 2.3GHz 12-core Intel Xeon E5-2670 v3, 30M Cache
  • 128GB 2133MHz RAM
  • 1TB HDD
  • 100 Gb/s EDR Infiniband network interface
  • 10 GbE and 1 GbE network interface
  • 4 nodes with one EVGA Geforce GTX 1080 PCIE 8GB GDDR5
  • 29 nodes with two EVGA Geforce GTX 1080 PCIE 8GB GDDR5
  • CentOS 78.x


Expand
title14 Broadwell Compute nodes
  • Two 2.2GHz 12-core Intel Xeon E5-2650 v4, 30M Cache
  • 64GB 2133MHz RAM
  • 1TB HDD
  • 100 Gb/s EDR Infiniband network interface
  • 10 GbE and 1 GbE network interface
  • CentOS 78.x


Expand
title1 Haswell BigMem node
  • Two 2.6GHz 8-core Intel Xeon E5-2640 v3, 20M Cache
  • 512GB 2400MHz RAM
  • 1TB HDD
  • 100 Gb/s EDR Infiniband network interface
  • 10 GbE and 1 GbE network interface
  • CentOS 78.x


Expand
title12 Skylake Compute nodes
  • Two 2.3GHz 18-core Intel Xeon Gold 6140, 24.75M Cache
  • 192GB 2666MHz RAM
  • 1TB HDD
  • 100 Gb/s EDR Infiniband network interface
  • 10 GbE and 1 GbE network interface
  • CentOS 78.x


Expand
title12 Skylake Quad GPU nodes
  • Two 2.3GHz 18-core Intel Xeon Gold 6140, 24.75M Cache
  • 192GB 2666MHz RAM
  • 1TB HDD
  • 100 Gb/s EDR Infiniband network interface
  • 10 GbE and 1 GbE network interface
  • Four ASUS Geforce RTX 2080 TI PCIE 11GB GDDR6
  • CentOS 78.x


Expand
title6 Cascade Lake Compute nodes
  • Two 2.6GHz 18-core Intel Xeon Gold 6240, 24.75M Cache
  • 192GB 2933MHz RAM
  • 1TB HDD
  • 100 Gb/s EDR Infiniband network interface
  • 10 GbE and 1 GbE network interface
  • CentOS 78.x


Expand
title2 Cascade Lake Refresh Compute nodes
  • Two 2.1GHz 26-core Intel Xeon Gold 6230R,
  • 384GB RAM
  • 1TB HDD
  • 10 GbE and 1 GbE network interface
  • CentOS 8.x

Intel XEON processors AVX2 and AVX512 frequencies

...

Code Block
languagebash
ssh username@sol.cc.lehigh.edu

If you are off campus, then there are two options

  1. Start a vpn session and then login to Sol using the ssh command above
  2. 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
languagebash
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
languagebash
  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
languagebash
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.