UMIACS - User contributions [en]

FilesystemDataStorage

2020-11-19T17:37:54Z

Dgugel: /* Linux Storage Commands */

UMIACS recommends that any and all important data be stored on a redundant, backed-up file server. However, there are a number of cases where this is not feasible.

==Windows Local Storage==
Windows hosts at UMIACS store user directories on their local C drives. Supported, UMIACS-managed hosts automatically back up user data on the C drive nightly using the Institute's backup system. If you have a supported, UMIACS-managed host that has other internal or external hard drives attached to it, please be aware that these drives '''are not''' backed up. Laptops and non-standard hosts are not automatically backed up and should be manually backed up by their users.

==UNIX Remote Storage==
We provide storage to each of our users in our UNIX offerings through the [[OpenLAB]] [[NFShomes]].

This home directory,

/nfshomes/username

is backed up nightly into our [[TSM]] backup system. This volume has [[Snapshots]] enabled for easy user restores.

Users are given a 4 gigabyte [[Quota]].

==UNIX Local Storage==
UNIX machines use redundant, backed-up network file shares for user directories. Research data storage is also stored on redundant, backed-up network file shares and is generally available under /fs/

All UNIX machines also have local storage available for transitory use. These directories may be used to store temporary, local '''''COPIES''''' of data that is permanently stored elsewhere or as a staging point for output.

These directories may not, '''''under any circumstances''''', be used as permanent storage for unique, important data. UMIACS staff cannot recover damaged or deleted data from these directories and will not be responsible for data loss if they are misused.

Please note that '''/tmp''' in particular is at risk for data loss or corruption as that directory is regularly used by system processes and services for temporary storage.

These directories include:

- /tmp
- /scratch0, /scratch1, /scratch*
- any directory named in whole or in part "tmp", "temp", or "scratch".

==Locally Attached Storage==
Locally attached storage like USB flash drives and USB hard drives are very popular. However, these devices are significantly more vulnerable to data loss or theft than internal or networked data storage. In general, UMIACS discourages the use of locally attached network storage when any other option is available. Please note that these devices are prone to high rates of failure and additional steps should be taken to ensure that the data is backed up and that critical or confidential data is not lost or stolen.

==Network Scratch Storage==
Some labs have network-attached storage dedicated for scratch/temporary storage. These shares are named in the same manner as local scratch or temporary storage (i.e. /fs/lab-scratch or /lab/scratch0 ) and are subject to the same policies as local scratch/tmp (discussed above.)

==UNIX Storage Commands==
Below are a few different CLI commands that may prove useful for monitoring your storage usage and performance. For additional information, run <code>[command] --help</code> or <code>man [command]</code>

df - Shows descriptive file system information
<pre>
Usage: df [OPTION]... [FILE]...
Show information about the file system on which each FILE resides,
or all file systems by default.
</pre>

du - Shows disk usage of specific files. Use the -d flag for better depth control.
<pre>
Usage: du [OPTION]... [FILE]...
or: du [OPTION]... --files0-from=F
Summarize disk usage of each FILE, recursively for directories.
</pre>

free - Shows current memory(RAM) usage. Use the -h flag for a human readable format.
<pre>
Usage:
free [options]
</pre>

quota - Shows quota information, this is useful for viewing per filesystem limits in places such as a home directory.
<pre>
quota: Usage: quota [-guqvswim] [-l | [-Q | -A]] [-F quotaformat]
quota [-qvswim] [-l | [-Q | -A]] [-F quotaformat] -u username ...
quota [-qvswim] [-l | [-Q | -A]] [-F quotaformat] -g groupname ...
quota [-qvswugQm] [-F quotaformat] -f filesystem ...
</pre>

iostat - Shows drive utilization, as well as other utilizations. Pair this with the <code>watch</code> command for regular updates.
<pre>
Usage: iostat [ options ] [ <interval> [ <count> ] ]
Options are:
[ -c ] [ -d ] [ -h ] [ -k | -m ] [ -N ] [ -t ] [ -V ] [ -x ] [ -y ] [ -z ]
[ -j { ID | LABEL | PATH | UUID | ... } ]
[ [ -T ] -g <group_name> ] [ -p [ <device> [,...] | ALL ] ]
[ <device> [...] | ALL ]

</pre>

FilesystemDataStorage

2020-11-19T17:30:59Z

Dgugel:

UMIACS recommends that any and all important data be stored on a redundant, backed-up file server. However, there are a number of cases where this is not feasible.

==Windows Local Storage==
Windows hosts at UMIACS store user directories on their local C drives. Supported, UMIACS-managed hosts automatically back up user data on the C drive nightly using the Institute's backup system. If you have a supported, UMIACS-managed host that has other internal or external hard drives attached to it, please be aware that these drives '''are not''' backed up. Laptops and non-standard hosts are not automatically backed up and should be manually backed up by their users.

==UNIX Remote Storage==
We provide storage to each of our users in our UNIX offerings through the [[OpenLAB]] [[NFShomes]].

This home directory,

/nfshomes/username

is backed up nightly into our [[TSM]] backup system. This volume has [[Snapshots]] enabled for easy user restores.

Users are given a 4 gigabyte [[Quota]].

==UNIX Local Storage==
UNIX machines use redundant, backed-up network file shares for user directories. Research data storage is also stored on redundant, backed-up network file shares and is generally available under /fs/

All UNIX machines also have local storage available for transitory use. These directories may be used to store temporary, local '''''COPIES''''' of data that is permanently stored elsewhere or as a staging point for output.

These directories may not, '''''under any circumstances''''', be used as permanent storage for unique, important data. UMIACS staff cannot recover damaged or deleted data from these directories and will not be responsible for data loss if they are misused.

Please note that '''/tmp''' in particular is at risk for data loss or corruption as that directory is regularly used by system processes and services for temporary storage.

These directories include:

- /tmp
- /scratch0, /scratch1, /scratch*
- any directory named in whole or in part "tmp", "temp", or "scratch".

==Locally Attached Storage==
Locally attached storage like USB flash drives and USB hard drives are very popular. However, these devices are significantly more vulnerable to data loss or theft than internal or networked data storage. In general, UMIACS discourages the use of locally attached network storage when any other option is available. Please note that these devices are prone to high rates of failure and additional steps should be taken to ensure that the data is backed up and that critical or confidential data is not lost or stolen.

==Network Scratch Storage==
Some labs have network-attached storage dedicated for scratch/temporary storage. These shares are named in the same manner as local scratch or temporary storage (i.e. /fs/lab-scratch or /lab/scratch0 ) and are subject to the same policies as local scratch/tmp (discussed above.)

==Linux Storage Commands==
Below are a few different CLI commands that may prove useful for monitoring your storage usage and performance. For additional information, run <code>[command] --help</code> or <code>man [command]</code>

df - Shows descriptive file system information
<pre>
Usage: df [OPTION]... [FILE]...
Show information about the file system on which each FILE resides,
or all file systems by default.
</pre>

du - Shows disk usage of specific files. Use the -d flag for better depth control.
<pre>
Usage: du [OPTION]... [FILE]...
or: du [OPTION]... --files0-from=F
Summarize disk usage of each FILE, recursively for directories.
</pre>

free - Shows current memory(RAM) usage. Use the -h flag for a human readable format.
<pre>
Usage:
free [options]
</pre>

quota - Shows quota information, this is useful for viewing per filesystem limits in places such as a home directory.
<pre>
quota: Usage: quota [-guqvswim] [-l | [-Q | -A]] [-F quotaformat]
quota [-qvswim] [-l | [-Q | -A]] [-F quotaformat] -u username ...
quota [-qvswim] [-l | [-Q | -A]] [-F quotaformat] -g groupname ...
quota [-qvswugQm] [-F quotaformat] -f filesystem ...
</pre>

iostat - Shows drive utilization, as well as other utilizations. Pair this with the <code>watch</code> command for regular updates.
<pre>
Usage: iostat [ options ] [ <interval> [ <count> ] ]
Options are:
[ -c ] [ -d ] [ -h ] [ -k | -m ] [ -N ] [ -t ] [ -V ] [ -x ] [ -y ] [ -z ]
[ -j { ID | LABEL | PATH | UUID | ... } ]
[ [ -T ] -g <group_name> ] [ -p [ <device> [,...] | ALL ] ]
[ <device> [...] | ALL ]

</pre>

SLURM/JobSubmission

2020-01-04T06:42:07Z

Dgugel: /* Job Submission */

=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.

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

'''An important notice: computational jobs run on submission nodes will be terminated. Please use the compute nodes for that purpose.'''

==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>
tgray26@opensub01:srun --mem=100mb --time=1:00:00 bash -c 'echo "Hello World from" `hostname`'
Hello World from openlab06.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>--mem=1gb</code> ''if no unit is given MB is assumed''
* <code>--nodes=2</code> ''if passed to srun, the given command will be run concurrently on each node''
* <code>--qos=dpart</code> ''to see the available QOS options on a cluster, run'' <code>show_qos</code>
* <code>--time=hh:mm:ss</code> ''time needed to run your job''
* <code>--job-name=helloWorld</code>
* <code>--output filename</code> ''file to redirect stdout to''
* <code>--error filename</code> ''file to redirect stderr''
* <code>--partition $PNAME</code> ''request job run in the $PNAME partition''
* <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>--account=accountname</code> ''use qos specific to an account''

===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>
tgray26@opensub01:srun --pty --mem 1gb --time=01:00:00 bash
tgray26@openlab06:
</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>
tgray26@opensub00:salloc -N 1 --mem=2gb --time=01:00:00
salloc: Granted job allocation 159
tgray26@opensub00:srun /usr/bin/hostname
openlab00.umiacs.umd.edu
tgray26@opensub00: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>tgray26@opensub00:sbatch --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>
tgray26@opensub00:squeue
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
121 dpart helloWor tgray26 R 0:01 2 openlab[00-01]
</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 I have a batch job that will request 2 nodes in the cluster, then I load a specific version of Python into my environment and submit two job steps, each one using one node. Since srun is blocks until the command finishes, I use the '&' operator to background the process so that both job steps can run at once; however, this means that I 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
#SBATCH --error helloWorld.out.%j # indicates a file to redirect STDERR to; %j is the jobid
#SBATCH --time=00:05:00 # how long you think your job will take to complete; format=hh:mm:ss
#SBATCH --qos=dpart # 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

module load Python/2.7.9 # run any commands necessary to setup your environment

srun -N 1 --mem=512mb bash -c "hostname; python --version" & # use srun to invoke commands within your job; using an '&'
srun -N 1 --mem=512mb bash -c "hostname; python --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 tgray26 --partition dpart</code> ''cancel all jobs for tgray26 in the dpart 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 this
<code>sinfo -o "%15N %10c %10m %25f %10G"</code>.

<pre>
$ sinfo -o "%40N %8c %8m %20f %25G"
NODELIST CPUS MEMORY AVAIL_FEATURES GRES
openlab[30-33] 64 257759 Opteron,6274 (null)
openlab[00-07] 8 7822 Opteron,2354 (null)
openlab[10-11,13-18,20-23,25,27-29] 16 23939 Xeon,x5560 (null)
openlab08 32 128720 Xeon,E5-2690 gpu:k20:2
</pre>

You can also identify further specific information about a node using [https://wiki.umiacs.umd.edu/umiacs/index.php/SLURM/ClusterStatus#scontrol scontrol].

=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> or 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 <code>--gres:k20:1</code>
<pre>
tgray26@opensub01:srun --pty --partition gpu --qos=gpu --gres=gpu:2 nvidia-smi
Wed Jul 13 15:33:18 2016
+------------------------------------------------------+
| NVIDIA-SMI 361.28 Driver Version: 361.28 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Tesla K20c Off | 0000:03:00.0 Off | 0 |
| 30% 24C P0 48W / 225W | 11MiB / 4799MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 Tesla K20c Off | 0000:84:00.0 Off | 0 |
| 30% 23C P0 52W / 225W | 11MiB / 4799MiB | 93% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| 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 request only 1 GPU and the other one will be left available for other users:
<pre>
tgray26@opensub01:srun --pty --partition gpu --qos=gpu --gres=gpu:k20:1 nvidia-smi
Wed Jul 13 15:31:29 2016
+------------------------------------------------------+
| NVIDIA-SMI 361.28 Driver Version: 361.28 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Tesla K20c Off | 0000:03:00.0 Off | 0 |
| 30% 24C P0 50W / 225W | 11MiB / 4799MiB | 92% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
</pre>
The <code>--gres</code> flag may also be passed to [[#sbatch | sbatch]] and [[#salloc | salloc]] rather than directly to [[#srun | srun]]

=MPI example=
<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

module load mpi

srun --mpi=openmpi /nfshomes/derek/testing/mpi/a.out
</pre>

Network/VPN/macOS

2019-06-19T17:58:45Z

Dgugel:

'''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 web browser.

'''As of May 10th 2019, MFA Authentication is mandatory.'''
==Prerequisites==
* Device enrolled with [[Duo | UMIACS Duo]]

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure-MACos.dmg|macOS Pulse Secure Client]] 
#:''Upon starting the client for the first time it will 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:JunosOSX.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:JunosOSXSettings.png|thumb|left|510px|[macOS] Enter the name of the vpn server]] 
#'''Enter your UMIACS credentials and hit connect.'''
#:[[Image:JunosOSXLogin.png|thumb|left|510px|[macOS] Enter UMIACS Credentials]] 
#'''Complete the [[Network/VPN/MFA | MFA]] Verification Step
#:[[Image:mac_mfa_step.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. 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:Check the Status of your ConnectionOSX1.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:AreYouConnected2.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'''
#:[[Image:ClickApple.png|thumb|left|510px|[macOS] Click the apple logo to show menu]] 
# '''Click "System Preferences"'''
#:[[Image:SystemPreferences.png|thumb|left|510px|[macOS] Enter the system preferences]] 
# '''Click "Security & Privacy"'''
#:[[Image:SecurityPrivacy.png|thumb|left|510px|[macOS] Enter the security and privacy settings]] 
# '''Click the "lock" icon at the bottom left and Enter your credentials to enable changes.'''
#:[[Image:EnterCredentials.png|thumb|left|510px|[macOS] Enter credentials to allow changes]] 
# '''In the "General" tab, under "Allow Apps Downloaded From", select "Mac Apps Store and Identified developers"'''
#:[[Image:AppStoreIdentifier.png|thumb|left|510px|[macOS] Select Mac Apps Store and Identified developers]] 
# '''Click "Next" to the message "System Software From Developers "Pulse Secure LLC" was blocked from loading" if prompted.'''
# '''Click "Allow" to enable the extension.'''
#:[[Image:Allow.png|thumb|left|510px|[macOS] Click Allow]] 
# '''Close the "Security & Privacy" window.'''

Network/VPN/macOS

2019-06-19T17:53:57Z

Dgugel:

'''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 web browser.

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure-MACos.dmg|macOS Pulse Secure Client]] 
#:''Upon starting the client for the first time it will 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:JunosOSX.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:JunosOSXSettings.png|thumb|left|510px|[macOS] Enter the name of the vpn server]] 
#'''Enter your UMIACS credentials and hit connect.'''
#:[[Image:JunosOSXLogin.png|thumb|left|510px|[macOS] Enter UMIACS Credentials]] 
#'''Complete the [[Network/VPN/MFA | MFA]] Verification Step
#:[[Image:mac_mfa_step.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. 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:Check the Status of your ConnectionOSX1.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:AreYouConnected2.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'''
#:[[Image:ClickApple.png|thumb|left|510px|[macOS] Click the apple logo to show menu]] 
# '''Click "System Preferences"'''
#:[[Image:SystemPreferences.png|thumb|left|510px|[macOS] Enter the system preferences]] 
# '''Click "Security & Privacy"'''
#:[[Image:SecurityPrivacy.png|thumb|left|510px|[macOS] Enter the security and privacy settings]] 
# '''Click the "lock" icon at the bottom left and Enter your credentials to enable changes.'''
#:[[Image:EnterCredentials.png|thumb|left|510px|[macOS] Enter credentials to allow changes]] 
# '''In the "General" tab, under "Allow Apps Downloaded From", select "Mac Apps Store and Identified developers"'''
#:[[Image:AppStoreIdentifier.png|thumb|left|510px|[macOS] Select Mac Apps Store and Identified developers]] 
# '''Click "Next" to the message "System Software From Developers "Pulse Secure LLC" was blocked from loading" if prompted.'''
# '''Click "Allow" to enable the extension.'''
#:[[Image:Allow.png|thumb|left|510px|[macOS] Click Allow]] 
# '''Close the "Security & Privacy" window.'''

Network/VPN/Windows

2019-06-14T18:39:26Z

Dgugel: