| HideElements | ||||||
|---|---|---|---|---|---|---|
|
<< Zurück zur Dokumentationsstartseite
| Lrz box | ||||
|---|---|---|---|---|
|
Forgot your Password? click here
Add new user (only for SuperMUC-NG)? click here
Add new IP(only for SuperMUC-NG)? click here
How to write good LRZ Service Requests? click here
System Status (see also:
Access and Overview of HPC Systems)
= fully operational Status colour Green
= operational but experiencing problems with restrictions (see messages below) Status colour Yellow
= not availableStatus colour Red
SuperMUC Phase 2
(will be switched off , all data will be deleted)
| Status | ||||
|---|---|---|---|---|
|
Höchstleistungsrechner (SuperMUC-NG) | |||||
| System: | |||||
| login nodes: skx.supermuc.lrz.de |
| ||||
|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Status colour Green title UP
| archive nodes: skx-arch.supermuc.lrz.de |
| ||||
|
| ||
|
|
|
|
| ||||||||||||
|
|
| ||||||||
Partitions/Queues: | ||||||||
general, large fat, test |
| ||||||||||
|
| |||||||
| Globus Online File Transfer: |
| ||||||
| ||
| Detailed node status | ||
Details:
| ||
Add new user? click here Add new IP? click here |
Linux Cluster |
| CoolMUC-2 |
| lxlogin( | |
| 1,2, |
| 3, |
| 4).lrz.de |
| ||||
| |||||||
| serial partitions: serial |
| ||||||
| |||||
| parallel partitions cm2_(std,large) |
| ||||
|
| |||||
| cluster cm2_tiny |
| ||||
|
| |||||
| interactive partition: cm2_inter |
| ||||
|
|
| c2pap |
| ||||
|
| ||
CoolMUC-3 lxlogin(8,9).lrz.de parallel partition: mpp3_batch | ||
interactive partition: mpp3_inter |
| ||||||||||
|
|
|
| ||
| teramem, kcs | ||
teramem_inter | ||
ivymuc
kcs |
| |||||||||||||
File Systems HOME |
| |||||||||||||
|
|
|
|
|
| ||
Details: | ||
Compute Cloud and |
|---|
Compute Cloud: (https://cc.lrz.de) | ||
| Status | ||||
|---|---|---|---|---|
|
detailed status and free slots: https:// |
| |||||||
| Status | ||||
|---|---|---|---|---|
|
| ||||||||
| LRZ AI Systems |
| |||||||
RStudio Server | ||||||||
| |||||
|
| ||
Details: | ||
| Messages for SuperMUC |
|---|
Change of Access Policy for the tape archive
Due to changed technical specifications for the IBM Spectrum Protect software, we have to change the access policy for the tape archive on SuperMUC-NG.
This will also affect data from SuperMUC, which have already put into the tape archive.
- Permissions to access the data will now be granted to all users of a project i.e., all users in a project group can retrieve data from other users in this project group.
- The previous policy was that only the users who wrote the data into the archive could access it.
- If your project is ‘pr12ab’, you can see the members of this group by
getent group pr12ab-d - You have to add the project in the dsmc commands i.e.
dsmc q ar “/gpfs/work/p12ab/us12ab5/*“ –se=p12ab - Please note the difference between the project (“pr12ab”) and the permission group for data (”pr12ab-d”)
See also: Backup and Archive on SuperMUC-NG
Deletion of data on SuperMUC Phase 2.
Required on your part: Data Migration from SuperMUC to SuperMUC-NG!
skx-arch.supermuc.de (Node for archiving) will not be available before January, 2020
SCRATCH/GPFS unavailable on CoolMUC-3
To avoid file system crashes, we have decided to unmount SCRATCH from all systems associated with CoolMUC-3 for now. We expect to revert this measure again at the next scheduled maintenance .
: HOME directory path will change
You will find all HOME data in the new DSS HOME area, data migration will be performed by LRZ (unless you are specifically notified that you need to perform HOME data migration yourself). For emergency recoveries, the legacy NAS area (pointed to by the HOME_LEGACY variable) will remain available in read-only mode until the end of the year.
Following action is required on your part: Make necessary adjustments to (job) scripts and configuration data to account for the changes in path names. LRZ strongly recommends using relative path names because this minimizes the required work.
Examples:
End of service for NAS systems
NAS paths will be taken offline at the beginning of January, 2020. Please contact the Service Desk for outstanding data migration issues.
NAS PROJECT path is mounted read-only
between and
DSS PROJECT now available on HPC systems:
Following action is required on your part:
Migrate data from the legacy NAS area (pointed to by the PROJECT_LEGACY variable) to the new DSS area. LRZ strongly advises to get rid of unneeded data sets, and/or archive data sets to tape.
Step-by-step procedure for migration:
- On any cluster login node, issue the command
dssusrinfo all
This will list paths to accessible containers, as well as quota information etc. - Edit your shell profile and set the PROJECT and/or WORK variable to a
suitable path value based on the above output, typically one of the DSS
paths with your account name appended to it. - Use the cp or rsync or tar command to migrate your data from
PROJECT_LEGACY to the new storage area. - If your scripts use absolute path names instead of the PROJECT or
WORK variable, they need appropriate updates
User e-Mail notification of DSS PROJECT link
Following actions are required on your part:
- Confirm the e-Mail invitation to validate your access,
- After the Linux Cluster maintenance (see below), store path information in an environment variable on the Cluster (e.g. by setting the PROJECT variable in ~/.bashrc).
One this is done, migrating data from NAS PROJECT to DSS PROJECT can start
Please read the change description on how to handle the significant changes to the Linux cluster configuration performed end of September, 2019
| -NG |
|---|
Please read https://www.lrz.de/aktuell/ali00938.html for details on a scheduled maintenance starting May 16. |
On Monday, April 4, 2022, a new version of the spack-based development and application software stack will be rolled out. The new spack version will be loaded as default starting April 11, 2022 After that date, you will be still able to switch to the previous spack stack with > module switch spack spack/21.1.1 We strongly recommend recompiling self-built applications after the roll-out. See also https://doku.lrz.de/display/PUBLIC/Spack+Modules+Release+22.2.1 for details. |
Base core frequency of jobs has been set to 2.3GHz. Higher frequencies possible using EAR. |
The new hpcreport tool is now available to check job performance and accounting on SuperMUC-NG. Please check out |
| Messages for Linux Clusters |
|---|
There are 4 "new" Remote Visualization (RVS_2021) nodes available. The machines are in production mode. Nodes are operated under Ubuntu OS and NoMachine. Usage is limited to 2 hours and if you need a longer period of time, please file an LRZ Service Request. For more details please refer to the documentation. |
Messages for Cloud and other HPC Systems |
|---|
We have observed and addressed an issue with the LRZ AI Systems that concerned some running user jobs. As of now, newly started jobs should not be affected anymore. The work on the LRZ AI Systems to address the recently observed stability issues has been concluded. All users are invited to continue their work. We closely monitor system operation and will provide additional updates if needed. Thank you for your patience and understanding. We have identified the likely root cause for the ongoing issues with the LRZ AI and MCML Systems following the latest maintenance downtime. We continue work towards a timely resolution and can currently not guarantee uninterrupted & stable system availability. For further details, please see LRZ AI Systems The LRZ AI and MCML Systems did undergo a maintenance procedure from April 25th to April 27th (both inclusive.) During this period, the system was not available to users. Normal user operation did resume on 2022-04-27 16:30. |
HPC Services
|
