# Paragon Automation 2.0 Lab

**Welcome to the hands-on lab!**

![Guacamole](./images/Guacamole.png)


## Overview

### Lab Objective

The objective of this Lab is to:

1.	Get hands of experience of Paragon Automation 2.x family.
2.	Perform Active Assurance Tests and Monitors using Templates and Observability of test results.
3.	Execute various Assurance Use-Cases from Activation Testing to Performance Monitoring.
4.	Execute scripts to demonstrate seamless integration with third party applications by using REST APIs. 

<div class="alert alert-info">
<strong>Note:</strong> As you are going to work in a shared environment with write access role, please be careful on the performed actions.
</div>


### Topology

Consists of a pair of MX204 or MX304 connected via an Impairment vm with Paragon Automation Test Agent Application running VM’s to send traffic streams.

![topology](./images/topology.png)


## Lab Steps

Test 1 – Reachability: Test Ping, DNS. 

Once the network or service is activated, we can test and check if its functioning at optimal level by observing the KPI’s like delay, jitter, loss.

Test 2 – Cloud Apps Reachability: Test Ping and Access to Cloud Apps (AWS, Azure, GCP etc.)

Test 3 & 4 – Performance Monitoring: Periodic Synthetic traffic to assure network or service is at optimal level without impact to revenue traffic by observing the KPI’s.

### Login to Paragon

1. Login to Paragon portal.
    1. Open Chrome browser and navigate to **<https://100.123.42.100>**

You should see the login page to Paragon Automation UI.

![paragon_login](./images/paragon_login.png)

Login using following credentials  
Username: <jcluser@juniper.net>  
Password: Juniper!1

2. Navigate to the pre-configured Test Templates
    1. Click on **Inventory** > **Test Templates**

    ![test_templates](./images/test_templates.png)

    This page will show all the pre-configured Templates that we’ll be using for Test. 

    ![test_templates2](./images/test_templates2.png)

    &lt;List the Tests available for HOL and 1 liner no need to go detail&gt;

    Test1 – Reachability – Test DNS, Ping – Once the network or service is built activate this network and be assured that the network or service is functioning at optimal level by way of observing the KPI’s like delay , jitter, loss

    Test2 – Not only networking and reachability but also service reachability

    Test 3, 4 – Performance Monitoring – periodic Synthetic traffic to assure network or service is at optimal level without impact to revenue traffic by observing the KPI’s

### Test 1 – Reachability

In this test we’ll check the reachability between Branches and Branch to Internet.

1. Go to **Test Templates** page and Click on **Test 1 – Reachability**

![reachability](./images/reachability.png)

![reachability2](./images/reachability2.png)

The test is further divided into Sub tasks.

- Task 1.1: DNS Resolution

     This test will try to resolve google.com

- Task 1.2: Ping from Branch to Internet

     This test will do a PING from the Branch to the Internet (Google).

- Task 1.3: Ping from Branch to Branch

     This test will do a PING from one Branch to another Branch

- Task 2.1: TCP throughput from Branch to Branch

     This test will perform a Bandwidth test from one Branch LAN to another Branch LAN

2.  Test execution

- Click on **Run** to execute the tests.

![execution](./images/execution.png)

- All the tests will run in sequence; Task 1.1 > Task 1.2 > Task 1.3 > Task 2.1

![execution2](./images/execution2.png)

![execution3](./images/execution3.png)

- Once all the tests are completed, we can check the **Task Status** to see whether the tests are **Passed** or **Failed**

![execution4](./images/execution4.png)

![execution5](./images/execution5.png)

- You can also go to Tests page and check the Status of particular Test. Click on **Observability** > **Tests**

![execution6](./images/execution6.png)

![execution7](./images/execution7.png)

- To check more details of any test. Click on a particular **Stream**

![execution8](./images/execution8.png)

### Test 2 – Cloud Apps Reachability
    
1. Navigate to **Inventory** > **Test Templates**

![cloud_reachability](./images/cloud_reachability.png)

2. Click on **Test 2 – Cloud Apps Reachability / Access**

![cloud_reachability2](./images/cloud_reachability2.png)

3. Click on **Run** to execute the test.

![cloud_reachability3](./images/cloud_reachability3.png)

4. Go to **Tests** page to check the status.

![cloud_reachability4](./images/cloud_reachability4.png)

![cloud_reachability5](./images/cloud_reachability5.png)

![cloud_reachability6](./images/cloud_reachability6.png)

![cloud_reachability7](./images/cloud_reachability7.png)

### Test 3 - TWAMP (Two-Way Active Measurement Protocol)
    
1. Navigate to **Inventory** > **Test Templates**

![twamp](./images/twamp.png)

2. Click on **Test 3 – TWAMP**

![twamp2](./images/twamp2.png)

3. Click on **Run** to execute the test.

![twamp3](./images/twamp3.png)

4. Go to **Tests** page to check the status.

![twamp4](./images/twamp4.png)

![twamp5](./images/twamp5.png)

5. Click on the Stream to get detailed result.

![twamp6](./images/twamp6.png)

![twamp7](./images/twamp7.png)

![twamp8](./images/twamp8.png)

### Test 4 - Y.1731

Y.1731 testing basically measures loss, delay, and delay variation (jitter) for traffic from the Test Agent towards a Y.1731-capable device.

1. Click on **Observability > Monitors**
   
![y1731](./images/y1731.png)

2. Click on **Test_DM**
   
![y1731_2](./images/y1731_2.png)

3. Click on the Stream
   
![y1731_3](./images/y1731_3.png)

4. Monitoring the Results
   
![y1731_4](./images/y1731_4.png)

![y1731_5](./images/y1731_5.png)

![y1731_6](./images/y1731_6.png)

### Test 5 - Execution of REST API based Tests from Helper VM

1. Access Helper VM via SSH from Windows Host using PuTTY. Click on Open.

![rest_api](./images/rest_api.png)

- IP - 100.123.0.8
- Username - labuser
- Password - Juniper!1

![rest_api2](./images/rest_api2.png)

2. Execute script using command **python3_paa-api-test-user- { }.py**
   
{ } – to be filled as per allocation by the lab instructor. 
a to f – whichever roll is allocated to you.
     
For example, for a participant allocated {a}

![rest_api3](./images/rest_api3.png)

For example, for a participant allocated {b}

![rest_api4](./images/rest_api4.png)

![rest_api5](./images/rest_api5.png)

3. Check execution of tests from Paragon UI matching the roll {A to H}

![rest_api6](./images/rest_api6.png)

![rest_api7](./images/rest_api7.png)

Congratulations, you have completed the lab!

<div class="alert alert-info">
<strong>Note:</strong> -	A special shout out to Juniper Sales Engineering Labs in building and executing the labs.

Visit https://portal.cloudlabs.juniper.net/ for many more labs and demos.
</div>

## Lab Survey

Please take 2 minutes and complet the [AWAN Paragon 2.0 Hands-On Lab Survey](https://www.surveymonkey.com/r/SYWRVXB)

![Paragon-HOL-Survey-qr-code](./images/Paragon-HOL-Survey-qr-code.png)