UMIACS - User contributions [en]

SLURM/JobSubmission

2024-02-12T18:30:53Z

Zadeep92: /* Common srun arguments */ Add --nodelist flag

=Job Submission=
SLURM offers a variety of ways to run jobs. It is important to understand the different options available and how to request the resources required for a job in order for it to run successfully. All job submission should be done from submit nodes; any computational code should be run in a job allocation on compute nodes. The following commands outline how to allocate resources on the compute nodes and submit processes to be run on the allocated nodes.

The cluster that everyone with a [[Accounts#UMIACS_Account | UMIACS account]] has access to is [[Nexus]]. Please visit the Nexus page for instructions on how to connect to your assigned submit nodes.

Please note that the hard maximum number of jobs that the SLURM scheduler can handle at once (on Nexus) is 50000. It is best to limit your number of submitted jobs at any given time to significantly less than this amount in the case that another user also wants to submit a large number of jobs.

'''Computational jobs run on submission nodes will be terminated. Please use compute nodes for running computational jobs.'''

For details on how SLURM decides how to schedule jobs when multiple jobs are waiting in a scheduler's queue, please see [[SLURM/Priority]].

==srun==
<code>srun</code> is the command used to run a process on the compute nodes in the cluster. It works by passing it a command (this could be a script) which will be run on a compute node and then <code>srun</code> will return. <code>srun</code> accepts many command line options to specify the resources required by the command passed to it. Some common command line arguments are listed below and full documentation of all available options is available in the man page for <code>srun</code>, which can be accessed by running <code>man srun</code>.

<pre>
$ srun --qos=default --mem=100mb --time=1:00:00 bash -c 'echo "Hello World from" `hostname`'
Hello World from tron33.umiacs.umd.edu
</pre>

It is important to understand that <code>srun</code> is an interactive command. By default input to <code>srun</code> is broadcast to all compute nodes running your process and output from the compute nodes is redirected to <code>srun</code>. This behavior can be changed; however, '''srun will always wait for the command passed to finish before exiting, so if you start a long running process and end your terminal session, your process will stop running on the compute nodes and your job will end'''. To run a non-interactive submission that will remain running after you logout, you will need to wrap your <code>srun</code> commands in a batch script and submit it with [[#sbatch | sbatch]].

===Common srun arguments===
* <code>--job-name=helloWorld</code> ''name of your job''
* <code>--mem=1gb</code> ''request 1GB of memory, if no unit is given MB is assumed''
* <code>--ntasks=2</code> ''request 2 "tasks" which map to cores on a CPU, if passed to srun the given command will be run concurrently on each core''
* <code>--nodes=2</code> ''if passed to srun, the given command will be run concurrently on each node''
* <code>--nodelist=$NODENAME</code> ''request to run your job on the $NODENAME node''
* <code>--time=hh:mm:ss</code> ''time needed to run your job''
* <code>--error=filename</code> ''file to redirect stderr''
* <code>--partition=$PNAME</code> ''request job run in the $PNAME partition''
* <code>--qos=default</code> ''to see the available QOS options on a cluster, run'' <code>show_qos</code>
* <code>--account=accountname</code> ''use qos specific to an account''
* <code>--output=filename</code> ''file to redirect stdout to''
* <code>--requeue</code> ''automatically requeue your job if it is preempted''

===Interactive Shell Sessions===
An interactive shell session on a compute node can be useful for debugging or developing code that isn't ready to be run as a batch job. To get an interactive shell on a node, use <code>srun</code> to invoke a shell:
<pre>
$ srun --pty --qos=default --mem 1gb --time=01:00:00 bash
$ hostname
tron33.umiacs.umd.edu
</pre>
'''Please do not leave interactive shells running for long periods of time when you are not working. This blocks resources from being used by everyone else.'''

==salloc==
The salloc command can also be used to request resources be allocated without needing a batch script. Running salloc with a list of resources will allocate the resources you requested, create a job, and drop you into a subshell with the environment variables necessary to run commands in the newly created job allocation. When your time is up or you exit the subshell, your job allocation will be relinquished.

<pre>
$ salloc --qos=default -N 1 --mem=2gb --time=01:00:00
salloc: Granted job allocation 159
$ srun /usr/bin/hostname
tron33.umiacs.umd.edu
$ exit
exit
salloc: Relinquishing job allocation 159
</pre>

'''Please note that any commands not invoked with srun will be run locally on the submit node. Please be careful when using salloc.'''

==sbatch==
The sbatch command allows you to write a batch script to be submitted and run non-interactively on the compute nodes. To run a simple Hello World command on the compute nodes you could write a file, helloWorld.sh with the following contents:

<pre>
#!/bin/bash

srun bash -c 'echo Hello World from `hostname`'
</pre>

Then you need to submit the script with sbatch and request resources:

<pre>
$ sbatch --qos=default --mem=1gb --time=1:00:00 helloWorld.sh
Submitted batch job 121
</pre>

SLURM will return a job number that you can use to check the status of your job with squeue:

<pre>
$ squeue
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
121 tron helloWor username R 0:01 1 tron32
</pre>

====Advanced Batch Scripts====
You can also write a batch script with all of your resources/options defined in the script itself. This is useful for jobs that need to be run 10s/100s/1000s of times. You can then handle any necessary environment setup and run commands on the resources you requested by invoking commands with srun. The srun commands can also be more complex and be told to only use portions of your entire job allocation, each of these distinct srun commands makes up one "job step". The batch script will be run on the first node allocated as part of your job allocation and each job step will be run on whatever resources you tell them to. In the following example, we have a batch job that will request 2 nodes in the cluster. We then load a specific version of [[Python]] into our environment and submit two job steps, each one using one node. Since srun is blocks until the command finishes, we use the '&' operator to background the process so that both job steps can run at once; however, this means that we then need to use the wait command to block processing until all background processes have finished.

<pre>
#!/bin/bash

# Lines that begin with #SBATCH specify commands to be used by SLURM for scheduling

#SBATCH --job-name=helloWorld # sets the job name
#SBATCH --output=helloWorld.out.%j # indicates a file to redirect STDOUT to; %j is the jobid. If set, must be set to a file instead of a directory or else submission will fail.
#SBATCH --error=helloWorld.out.%j # indicates a file to redirect STDERR to; %j is the jobid. If set, must be set to a file instead of a directory or else submission will fail.
#SBATCH --time=00:05:00 # how long you would like your job to run; format=hh:mm:ss
#SBATCH --qos=default # set QOS, this will determine what resources can be requested
#SBATCH --nodes=2 # number of nodes to allocate for your job
#SBATCH --ntasks=4 # request 4 cpu cores be reserved for your node total
#SBATCH --ntasks-per-node=2 # request 2 cpu cores be reserved per node
#SBATCH --mem=1gb # memory required by job; if unit is not specified MB will be assumed

srun -N 1 --mem=512mb bash -c "hostname; python3 --version" & # use srun to invoke commands within your job; using an '&'
srun -N 1 --mem=512mb bash -c "hostname; python3 --version" & # will background the process allowing them to run concurrently
wait # wait for any background processes to complete

# once the end of the batch script is reached your job allocation will be revoked
</pre>

Another useful thing to know is that you can pass additional arguments into your sbatch scripts on the command line and reference them as <code>${1}</code> for the first argument and so on.

====More Examples====
* [[SLURM/ArrayJobs]]

===scancel===
The scancel command can be used to cancel job allocations or job steps that are no longer needed. It can be passed individual job IDs or an option to delete all of your jobs or jobs that meet certain criteria.
*<code>scancel 255</code> ''cancel job 255''
*<code>scancel 255.3</code> ''cancel job step 3 of job 255''
*<code>scancel --user username --partition=tron</code> ''cancel all jobs for username in the tron partition''

=Identifying Resources and Features=
The sinfo can show you additional features of nodes in the cluster but you need to ask it to show some non-default options using a command like <code>sinfo -o "%40N %8c %8m %20f %35G"</code>.

<pre>
$ sinfo -o "%40N %8c %8m %20f %35G"
NODELIST CPUS MEMORY AVAIL_FEATURES GRES
tron[22-33,35-45] 16 128521+ rhel8,Zen,EPYC-7302 gpu:rtxa4000:4
tron[06-09,12-15,21] 16 128520+ rhel8,Zen,EPYC-7302P gpu:rtxa4000:4
tron[10-11,16-20,34] 16 128524 rhel8,Zen,EPYC-7313P gpu:rtxa4000:4
legacy00 48 128248 rhel8,Zen,EPYC-7402 (null)
legacy[01-09] 12 128436 rhel8,Xeon,E5-2620 (null)
clip07 8 257570 rhel8,Xeon,E5-2623 gpu:gtx1080ti:3
clip08 32 257565 rhel8,Xeon,E5-2683 gpu:gtx1080ti:8
clip09 32 385350 rhel8,Xeon,6130 gpu:rtx2080ti:5,gpu:gtx1080ti:3
clip00 32 257583 rhel8,Xeon,E5-2683 gpu:gtxtitanx:3
clip01 32 257583 rhel8,Xeon,E5-2683 gpu:gtxtitanx:1,gpu:gtxtitanxp:2
clip02 20 128562 rhel8,Xeon,E5-2630 gpu:gtx1080ti:3
clip03 20 128562 rhel8,Xeon,E5-2630 gpu:rtx2080ti:1,gpu:gtx1080ti:2
clip04 32 257540 rhel8,Zen,EPYC-7302 gpu:rtx3090:4
clip[05-06] 24 128523 rhel8,Zen,EPYC-7352 gpu:rtxa6000:2
gammagpu[01-03] 32 257541 rhel8,Zen,EPYC-7313 gpu:rtxa5000:8
legacy14 20 322068 rhel8,Xeon,E5-2650 gpu:gtxtitanx:4
legacy[15-16] 16 257587 rhel8,Xeon,E5-2630 gpu:teslak80:2
legacy17 44 515501 rhel8,Xeon,E5-2699 gpu:gtx1080ti:4
twist[00-01] 16 64031 rhel8,Xeon,E5-1660 (null)
twist[02-05] 48 257452 rhel8,Xeon,E5-2650 (null)
tron[00-05] 32 257540 rhel8,Zen,EPYC-7302 gpu:rtxa6000:8
tron[46-61] 48 257539 rhel8,Zen,EPYC-7352 gpu:rtxa5000:8
</pre>

Note that all of the nodes shown by this may not necessarily be in a partition you are able to submit to.

There is also a prewritten alias <code>show_nodes</code> on all of our SLURM computing clusters that shows each node's name, number of CPUs, memory, processor type (as AVAIL_FEATURES), GRES, State, and partitions that can submit to it.

You can identify further specific information about a node using [[SLURM/ClusterStatus#scontrol | scontrol]] with various flags.

=Requesting GPUs=
If you need to do processing on a GPU, you will need to request that your job have access to GPUs just as you need to request processors or CPU cores. You will also need to make sure that you submit your job to the correct partition since nodes with GPUs are often put into their own partition to prevent the nodes from being tied up by jobs that don't utilize GPUs. In SLURM, GPUs are considered "generic resources" also known as GRES. To request some number of GPUs be reserved/available for your job, you can use the flag <code>--gres=gpu:2</code>. If there are multiple types of GPUs available in the cluster and you need a specific type, you can provide the type option to the gres flag e.g. <code>--gres=gpu:rtxa5000:1</code>. If you do not request a specific type of GPU, you are likely to be scheduled on an older, lower spec'd GPU.

<pre>
$ srun --pty --gres=gpu:2 nvidia-smi
Thu Aug 25 15:22:15 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.129.06 Driver Version: 470.129.06 CUDA Version: 11.4 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA RTX A4000 Off | 00000000:01:00.0 Off | Off |
| 30% 23C P8 20W / 140W | 0MiB / 16376MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
| 1 NVIDIA RTX A4000 Off | 00000000:41:00.0 Off | Off |
| 30% 24C P8 15W / 140W | 0MiB / 16376MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
</pre>

Please note that your job will only be able to see/access the GPUs you requested. If you only need 1 GPU, please only request 1 GPU. The others on the node (if any) will be left available for other users.

<pre>
$ srun --pty --gres=gpu:rtxa5000:1 nvidia-smi
Thu Aug 25 15:22:15 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.129.06 Driver Version: 470.129.06 CUDA Version: 11.4 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA RTX A5000 Off | 00000000:01:00.0 Off | Off |
| 30% 23C P8 20W / 230W | 0MiB / 24256MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
</pre>

As with all other flags, the <code>--gres</code> flag may also be passed to [[#sbatch | sbatch]] and [[#salloc | salloc]] rather than directly to [[#srun | srun]].

=MPI example=
To run [https://en.wikipedia.org/wiki/Message_Passing_Interface MPI] jobs, you will need to include the <code>--mpi=pmix</code> flag in your submission arguments.

<pre>
#!/usr/bin/bash
#SBATCH --job-name=mpi_test # Job name
#SBATCH --nodes=4 # Number of nodes
#SBATCH --ntasks=8 # Number of MPI ranks
#SBATCH --ntasks-per-node=2 # Number of MPI ranks per node
#SBATCH --ntasks-per-socket=1 # Number of tasks per processor socket on the node
#SBATCH --time=00:30:00 # Time limit hrs:min:sec

srun --mpi=pmix /nfshomes/username/testing/mpi/a.out
</pre>

Network/VPN/macOS

2023-07-24T19:03:45Z

Zadeep92: /* Connecting through the Pulse Secure client */ VPN 22.3.R1

'''Please note that this tutorial assumes you already have a network connection established.'''
'''If you have a UMIACS account, you already have access.'''

The UMIACS VPN is accessible through the Pulse Secure Client. Alternatively, you can establish a connection through a [https://vpn.umiacs.umd.edu/ web browser], but this may fail if you have an outdated version of Pulse Secure already installed.

'''As of May 10th 2019, MFA Authentication is mandatory.'''
==Prerequisites==
* Device enrolled with [[Duo | UMIACS Duo]]
* macOS 11.x or higher as of the current version of the Pulse Secure Client

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure_22.3.R1.dmg|macOS Pulse Secure Client]] 
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up-to-date version of the client with the most recent configuration.''
#'''Open the client and click 'Add' (+) under the connection section.'''
#:[[Image:Ivanti client1.png|thumb|left|510px|[macOS] Click the 'Add' (+) button to create a new connection]] 
#'''In the 'Name' field, enter a descriptive name for this vpn Connection.'''
#'''In the 'Server URL' enter 'vpn.umiacs.umd.edu''''
#:[[Image:Ivanticonnection.png|thumb|left|510px|[macOS] Enter the name of the vpn server]] 
#'''Enter your UMIACS credentials and hit connect.'''
#:[[Image:Ivanticlientmac5.png|thumb|left|510px|[macOS] Enter UMIACS Credentials]] 
#'''Complete the [[Network/VPN/MFA | MFA]] Verification Step. For example, if you wish to push a notification to your device, type the word "push" into the secondary password box.
#:[[Image:SecondaryloginmacOS.png|thumb|left|510px|[macOS] Enter a secondary password.]] 
::The Pulse VPN multi-factor authentication implementation relies on a secondary authentication source to fulfill the [[Network/VPN/MFA | MFA]] requirement. As a result, you will be prompted for credentials twice.

::{|class="wikitable"
!Second Credential Password Value:
! Result
|-
| push
| Send a push verification to your Duo connected device
|-
| phone
| Send a call verification to your Duo connected device.
|-
| <press YubiKey>
| If you have a physical token then you would press the YubiKey for the one time password.
|}

::Please note that registering a YubiKey for use with the VPN requires interaction with UMIACS Tech Staff. Please [[HelpDesk | contact us]] if you would like to register a YubiKey for this purpose.
{{Note|Pro-tip: Select ‘Save Settings’ on the secondary authentication prompt to have Duo automatically use your preferred method.}}

You should now be connected to the UMIACS VPN. You can close the window and the VPN will remain connected.

If you encounter an error, please refer to the "Setup Security Requirement" section bellow.

==Checking VPN Status==
# In the top right hand corner, on your status bar, you should see an S icon in a black circle. If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#: [[Image:CheckingVPNstatus1.png|thumb|left|610px|[macOS] The top image is connected, the bottom image is not.]] 
# You can click this icon, as well, and it will show you the status of your connection.
#:[[Image:CheckingVPN2.png|thumb|left|610px|[macOS] The Pulse drop down menu.]] 
# If the icon is not in the status bar, you can find Pulse Secure in your Applications folder. There you will see a list of connections.

==Setup Security Requirement (Follow these steps if you encounter an error while connecting through the Pulse Secure client) ==

# Click the Apple logo at the top left of your desktop
# Click '''System Settings'''
# Click '''Privacy & Security'''
# Scroll to the '''Security''' section and select '''App Store and identified developers'''
#* You will have to enter your credentials
# Click '''Next''' to the message "System Software From Developers "Pulse Secure LLC" was blocked from loading" if prompted.
# Click '''Allow''' to enable the extension.
# Close the '''System Settings''' window.

Network/VPN/Linux

2023-07-24T15:32:02Z

Zadeep92: /* Connecting through the Pulse Secure client */ Pulse Secure 22.3.R1 64 bit

'''Please note that this tutorial assumes you already have a network connection established.'''
'''If you have a UMIACS account, you already have access.'''

The UMIACS VPN is accessible through the Pulse Secure Client.

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:Pulsesecure_22.3.R1_amd64_ubuntu.deb|Ubuntu 64 bit Pulse Secure Client]] 
#:[[Media:PulseSecure9.1R8.2i386.deb|Ubuntu 32 bit Pulse Secure Client]] 
#'''Navigate to the download location in terminal. e.g.: ''' <tt>cd ~/Downloads</tt>
#'''Install the package with dependencies, providing your password for sudo when requested.'''
#:<code>sudo dpkg -i <insert_filename_here>.deb</code>
#:[[Image:UbuntuPulseInstall.png|thumb|center|500px|]]
# You will need to manually install the packages as shown here: <code>sudo apt-get install libnss3-tools net-tools</code> and then proceed with the Install.
#'''Start the client.'''
#:[[Image:UbuntuPulseDesktop.png|thumb|center|500px|]]
#'''and click 'Add' (+) under the connection section.'''
#:[[Image:UbuntuPulseInterface3.png|thumb|center|500px|Click the 'Add' (+) button to create a new connection.]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:UbuntuPulseInterface1.png|thumb|center|500px|Enter the name of the VPN server.]]
#'''Enter your UMIACS credentials and hit connect.'''
#:[[Image:UbuntuPulseInterface2.png|thumb|center|500px|Enter UMIACS credentials.]]
#'''When prompted for a secondary password, enter one of three options below (push, phone, or <press YubiKey>). For example, if you wish to push a notification to your device, type the word "push" into the secondary password box. '''
::{|class="wikitable"
!Second Credential Password Value:
! Result
|-
| push
| Send a push verification to your Duo connected device
|-
| phone
| Send a call verification to your Duo connected device.
|-
| <press YubiKey>
| If you have a physical token then you would press the YubiKey for the one time password.
|}
::Please note that registering a YubiKey for use with the VPN requires interaction with UMIACS Tech Staff. Please [[HelpDesk | contact us]] if you would like to register a YubiKey for this purpose.
{{Note|Pro-tip: Select ‘Save Settings’ on the secondary authentication prompt to have Duo automatically use your preferred method.}}

You should now be connected to the UMIACS VPN. You can close the window and the VPN will remain connected.

==Checking VPN Status==
# Launch the Pulse Client GUI
#:[[Image:UbuntuPulseDesktop.png|thumb|center|280px|]]
# Select the down arrow to show connection status.
#:[[Image:UbuntuPulseInterface4.png|thumb|center|280px|]]

Network/VPN/Windows

2023-07-24T15:27:38Z

Zadeep92: /* Connecting through the Pulse Secure client (for computers WITHOUT ARM processors) */ Pulse Secure 22.3.R1

The UMIACS VPN is accessible through the Pulse Secure Client. Alternatively, you can establish a connection through a [https://vpn.umiacs.umd.edu/ web browser], but this may fail if you have an outdated version of Pulse Secure already installed.

'''As of May 10th 2019, MFA Authentication is mandatory.'''

'''NOTE: If your computer has an ARM-based processor, you will need to proceed differently from the standard Windows instructions. Please refer to the [[#Connecting through the Pulse Secure client (for computers WITH ARM processors)|instructions here]].'''

==Prerequisites==
* A [[Accounts#UMIACS_Account | full UMIACS account]]
* Device enrolled with [[Duo | UMIACS Duo]]
* An established network connection (wired or wireless)

==Connecting through the Pulse Secure client (for computers WITHOUT ARM processors)==
# '''Download the client:'''
#: [[Media:PulseSecure22.3.R1.x64.msi |Windows 64 bit Pulse Secure Client]] (preferred) 
#: [[Media:PulseSecure22.3.R1.x86.msi |Windows 32 bit Pulse Secure Client]] 
#: ''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
# '''Start the client if it is not already running - it usually starts by default on bootup.'''
#: [[Image:Network VPN Windows Snip1.png|thumb|center|280px|[Windows] Start the client from the Start Menu.]]
# '''If the client is already running, double click its icon from the status bar.'''
#: [[Image:Network VPN Windows Snip2.png|thumb|center|280px|[Windows] Double click its status icon to open.]]
# '''and click 'Add' (+) under the connection section.'''
#: [[Image:Network VPN Windows Snip3.png|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection.]]
# '''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#: [[Image:Network VPN Windows Snip4.png|thumb|center|280px|[Windows] Enter the name of the VPN server.]]
# '''Enter your UMIACS credentials and hit connect.'''
#: [[Image:Network VPN Windows Snip5.png|thumb|center|280px|[Windows] Enter UMIACS credentials.]]
# '''Enter Secondary Password for [[Network/VPN/MFA | MFA]]. For example, if you wish to push a notification to your device, type the word "push" into the secondary password box.'''

:::[[Image:Network VPN Windows Snip6.png|thumb|center|280px|[Windows] Enter Secondary Password.]]

::The Pulse VPN multi-factor authentication implementation relies on a secondary authentication source to fulfill the MFA requirement. As a result, you will be prompted for credentials twice.

::{|class="wikitable"
!Second Credential Password Value:
! Result
|-
| push
| Send a push verification to your Duo connected device
|-
| phone
| Send a call verification to your Duo connected device.
|-
| <press YubiKey>
| If you have a physical token then you would press the YubiKey for the one time password.
|}

:: Please note that registering a YubiKey for use with the VPN requires interaction with UMIACS Tech Staff. Please [[HelpDesk | contact us]] if you would like to register a YubiKey for this purpose.

{{Note|Pro-tip: Select ‘Save Settings’ on the secondary authentication prompt to have Duo automatically use your preferred method.}}

You should now be connected to the UMIACS VPN.

==Connecting through the Pulse Secure client (for computers WITH ARM processors)==
ARM processors cannot natively run x64 or x86 programs without special emulation. However, not all x86 programs run smoothly even with emulation. As such, the best course of action for these sorts of machines is using the version of Pulse Secure that is specifically made for ARM processors, which is offered on the Microsoft Store.

'''Installation Instructions:'''

# [https://www.microsoft.com/en-us/p/pulse-secure/9nblggh3b0bp Go to the Pulse Secure page on the Microsoft Store.]
# Click the "Get" button and wait for it to finish downloading. Once it's finished downloading, the Get button should now say "Install". Click "Install".
# Once Pulse Secure is installed, continue to the Configuration Instructions.

'''Configuration Instructions:'''
# Open Pulse Secure. It should have a green- and black-colored icon in the shape of an S.
# You should now see a gray window. Click on the "VPN Settings..." button in that window.
# You should now see the VPN page in Windows Settings. Click "Add a VPN connection".
# The VPN provider should be Pulse Secure. You will now need to enter the following information:
## Connection name: UMIACS
## Server name or address: vpn.umiacs.umd.edu
## Username: You can put in your UMIACS username if you'd like, or you can leave it blank.
## password: Leave it blank for security reasons.
## Choose to remember sign-in info ONLY if the password field is blank, for security reasons.
## You should now be finished with adding the VPN connection.
# Now under "VPN" and "Add a VPN connection" at the top, you should see a button that says "UMIACS". Click on that button.
# You will now be prompted for your username (if you did not fill it out when adding the connection) and password. Enter your UMIACS credentials, then click the "OK" button.
# You will now be prompted for a "secondary password". This refers to the method of multi-factor authentication you would like to use. Typing in "push" into this field will send a notification to the Duo app on your smart device, whereas "phone" will send a call to your registered phone number. Enter your choice of authentication, then click the "Next" button.
# After completing the multi-factor authentication via push notification or call, you should now be connected to the UMIACS VPN!

In case you would like to manually disconnect from the VPN, go to the same "VPN Settings..."/VPN page in Windows settings, click on the UMIACS connection, and click the "Disconnect" button.

==Checking VPN Status==
# In the bottom right hand corner, in your status bar, you should see an S icon. If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#: [[Image:Network_VPN_Windows_Snip7.png|thumb|center|500px|]]
# You can hover over this icon and it will show you the status of your connection.
#: [[Image:Network_VPN_Windows_Snip8.png|thumb|center|500px|]]

HelpDesk

2022-07-19T19:57:11Z

Zadeep92: Added full address

The UMIACS Help Desk provides Technical Support and Equipment procurement.

; Help Desk Location
: 3109 Brendan Iribe Center for Computer Science and Engineering
: 8125 Paint Branch Drive
: College Park, MD 20742
;; Help Desk Hours
: 9:00am - 5:00pm Monday - Friday (excluding [https://phr-app6.umd.edu/holidays/ University Holidays])
; [[HelpDesk/COVID | COVID-19 specific precautions]]

==How to Contact Support==
; Email
: [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]
; Telephone
: [tel:+13014051775 (301) 405-1775]
; [[Jira | JIRA Request Tracker]]