Merge pull request #183 from boreal321/vgranic-mcn-lab-updates

Intro to MCN lab1 and lab4 updates

docs/class6/module1/lab1.rst

@@ -163,15 +163,21 @@ There are two approaches for setting up your Customer Edge deployment both will
 **Option 1: CLI Site Setup**
 ----------------------
 
-In your browser, you should have a tab open to the UDF course. Under the F5 Distributed Cloud CE, click on **Access >> Console**
+In your browser, you should have a tab open to the UDF course. Under Systems -> Client, click on **Access >> Web Shell**
 
 |
 
-.. image:: ../images/cli-01.png 
+.. image:: ../images/cli-01a.png
 
 |
 
-This should redirect you to the CLI and prompt for authentication. Type in the default username/password:
+This will redirect you to a new browser tab with a shell prompt on the Ubuntu system. From the shell prompt type in the following to SSH to the Customer Edge (CE) Node:
+
+**ssh 10.1.1.5 -l admin**
+
+This will get you connected to the CLI on the CE and prompt for authentication. Type in the default username/password:
+
+Change the password as directed (lowercase, uppercase, number, min 8 characters is the requirement). Remember the new password should you need to log in again. 
 
 ==============================  =====
 Variable                        Value
@@ -182,15 +188,7 @@ Default Password:                **Volterra123**
 
 |
 
-.. image:: ../images/cli-02.png 
-
-|
-
-Change the password as directed. Remember the new password should you need to log in again. 
-
-|
-
-.. image:: ../images/cli-03.png 
+.. image:: ../images/cli-02a.png 
 
 |
 
@@ -251,7 +249,7 @@ Default Password:                **Volterra123**
 
 |
 
-.. image:: ../images/signin.png 
+.. image:: ../images/signin.png
 
 |
 

docs/class6/module2/lab4.rst

@@ -303,15 +303,15 @@ If you search your HTTP Load Balancers for your **animal-name**, you should now
 Testing AWS to Azure LB
 ------------------------
 
-You now have a load balancer running in AWS on the inside interface of your AWS XC Node. The inside interface IP of the AWS XC Node is **10.0.5.101**. 
+You now have a load balancer running in AWS on the inside interface of your AWS XC Node. The inside interface IP of the AWS XC Node is **10.0.5.236**. 
 
 We will now use the In-Container Diag tool to test connectivity.  
 
 If you don't already have a tab open to the Diag tool, in your browser go to: http://[animal-name]-awstool.lab-mcn.f5demos.com
 
 Click on **Run Command** and paste in the following:: 
 
-    curl  http://[animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com --resolve [animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com:80:10.0.5.101
+    curl  http://[animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com --resolve [animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com:80:10.0.5.236
 
 |
 
@@ -324,7 +324,7 @@ In just a few moments, you now have full proxy connectivity between IP Overlappe
 
 Let's try that command again but with the shorthand version by using **\-\-head**::
 
-    curl --head  http://[animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com --resolve [animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com:80:10.0.5.101
+    curl --head  http://[animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com --resolve [animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com:80:10.0.5.236
 
 |
 
@@ -443,7 +443,7 @@ If you don't already have a tab open to the Diag tool, in your browser go to: ht
 
 Try your curl command again **without** the **--head** flag.:: 
 
-    curl http://[animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com --resolve [animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com:80:10.0.5.101
+    curl http://[animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com --resolve [animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com:80:10.0.5.236
 
 
 |
@@ -455,7 +455,7 @@ Try your curl command again **without** the **--head** flag.::
 
 Now run the command again but insert the **\-\-head** command.::
 
-    curl --head  http://[animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com --resolve [animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com:80:10.0.5.101
+    curl --head  http://[animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com --resolve [animal-name]-aws-to-azure-lb.lab-mcn.f5demos.com:80:10.0.5.236
 
 |