Systems News

In order to more accurately describe the services provided, the Consolidated Customer Assistance Center (CCAC) will be renamed the "HPC Help Desk." This change will be effective 18 May, 2015. On this date, access to the HPC Help Desk ticket system will change from the current location (https://help.ccac.hpc.mil) to the new https://helpdesk.hpc.mil. Accordingly, the email address to contact the HPC Help Desk will be help@helpdesk.hpc.mil. The old URL and email address will remain available with auto forwarding and redirection for a period of time, but you are encouraged to update your bookmarks and contacts with these new addresses starting 18 May 2015. The phone number, 1-877-222-2039, will remain the same.

The ARL DSRC Cray XC-40 system debuted at #19 of the world's TOP 500 list of most powerful supercomputers on November 17th, 2014. ARL took delivery of its most recent HPC system, a 101,184 core Cray XC-40. The system was acquired through the DOD High Performance Computing Modernization Program and will complement a stable of other HPC resources at the ARL DOD Supercomputing Resource Center (DSRC). The ARL DSRC Cray XC-40 system will be one of the largest to date in the DOD HPC Program boasting 101,184 cores augmented with 32 NVIDIA Tesla K40 GPGPUs. The system has a theoretical peak of over 3.7 PETA Flops, 400 TBytes of memory, and 122 TBytes of solid-state disk (or 'flash' storage). ARL's Excalibur system will serve as a key HPC resource for the DOD Research, Development and Test and Evaluation communities.

Image of Excalibur

ARL's newest HPC system, Excalibur, has over 101,000 cores and a theoretical peak speed of 3.7 PETAFlops.

As of December 2, 2014, Copper will have a round-robin login configuration, meaning that one will only have to use copper.ors.hpc.mil when logging in. However, this initially will lead to the following when logging in via Linux:

[user@user ~]$ ssh copper.ors.hpc.mil
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
f8:b5:46:2c:6c:f6:5d:98:9e:01:28:19:ca:cd:2e:df.
Please contact your system administrator.
Add correct host key in /home/user/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/user/.ssh/known_hosts:10
RSA host key for copper01 has changed and you have requested strict checking.
Host key verification failed.

This can be eliminated by editing the known_hosts file in the .ssh directory in the home directory on the system from which one is logging in. The entries for Copper in this file should be deleted. For example here are two for copper01 and copper02:


copper01.ors.hpc.mil,IP_ADDRESS ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQDPmFsykLAmJ/uS+RWMN
Xf4zRGW3m7kk3a2rwxEAjMx2o7AIWwRjtaG2J07aX5sgtcRdZsilUcncff5+6uH1gSzO3pnTmAVuielJ
6QI9XRyCC5HJG6WaYuki38fSMHlGfsOe3Y7DnsUKhEvriWl7K9IoeUhJbFMpgQVa/mzTZShhQ==
copper02,IP_ADDRESS ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQDPmFsykLAmJ/uS+RWMN
Xf4zRGW3m7kk3a2rwxEAjMx2o7AIWwRjtaG2J07aX5sgtcRdZsilUcncff5+6uH1gSzO3pnTmAVuielJ
6QI9XRyCC5HJG6WaYuki38fSMHlGfsOe3Y7DnsUKhEvriWl7K9IoeUhJbFMpgQVa/mzTZShhQ==

The lines for both copper01 and copper02 need to be deleted and then the known_host file saved. Then, on the next login to Copper, the following will require an answer:


The authenticity of host 'copper02 (IP_ADDRESS)' can't be established.
RSA key fingerprint is f8:b5:46:2c:6c:f6:5d:98:9e:01:28:19:ca:cd:2e:df.
Are you sure you want to continue connecting (yes/no)?

Answering "yes" will populate the known_hosts file with an updated copper entry and log one into the system.

*************************************************************************

If logging in from a Windows system, the following message will be displayed:


WARNING - POTENTIAL SECURITY BREACH!
The server's host key does not match the one PuTTY has cached in the registry. This means that either the server administrator has changed the host key, or you have actually connected to another computer pretending to be the server.
The new rsa2 key fingerprint is: ssh-rsa 1024 cc:83:cc:83:d6:h7:94:3f:19:8b:b0:e3:4c:36:e7:cf
If you were expecting this change and trust the new key, hit Yes to update PuTTY's cache and continue connecting. If you want to carry on connecting but without updating the cache, hit No.
If you want to abandon the connection completely, hit Cancel. Hitting Cancel is the ONLY guaranteed safe choice.

One should simply hit Yes and proceed.