part2

Author: MattDierick

docs/class4/module4/.DS_Store

@@ -35,9 +35,12 @@ You will see the environment details
 
 .. note:: 
   💡  Your environment is now accessible via the following links:
-  Name        URL                    User           Password       Description
-  ----        ---                    ----           --------       -----------
-  Dashboard   https://localhost:8000 N/A            N/A            API Discovery Dashboard
+  
+  =========  ======================  =============  ============   =======================
+  Name       URL                     User           Password       Description
+  =========  ======================  =============  ============   =======================
+  Dashboard  https://localhost:8000  N/A            N/A            API Discovery Dashboard
+  =========  ======================  =============  ============   =======================
 
   🌐  Usable IP addresses on this host: 10.1.1.9, 10.1.20.9, 172.17.0.1, 172.18.0.1
 
@@ -54,3 +57,4 @@ Connect to LAD Console
    :align: left
    :scale: 50%
 
+Next step is to configure the BIG-IP to send traffic datas to LAD server

docs/class4/module4/lab1/lab1.rst

@@ -1,12 +1,42 @@
 Configure BIG-IP for Local API Discovery
 ========================================
 
-There are multiple options to do Rate Limiting in F5XC. In this lab, we are focusing on API Protection Rate Limiting. 
+Now, we must configure the BIG-IP to collect the datas, format the datas, and send the datas to the LAD server.
 
-The goal is to rate limit an endpoint at risk because we discovered an attack or it is a shadow API and we are not sure if we should allow or block it.
+There is a how-to into the LAD Console for TMUI, iControl REST and TMSH.
+
+Click on ``Integration`` > ``Integration Guide``
+
+.. image:: ../pictures/integration1.png
+   :align: left
+   :scale: 50%
+
+You can see how it works and how it is interconnected.
+
+In a nutshell, an irule attached to the API Application Virtual Server is collecting the requests and responses, formating the datas and send those datas to a pool where the LAD is a member.
+
+
+Configure the BIG-IP via the TMUI
+---------------------------------
+
+Configure the Pool
+^^^^^^^^^^^^^^^^^^
+
+* Go to Local Traffic -> Pools and Create a new External pool for LAD Collector (logging-node-tls). 
+* Pool member port must be ``6514``
+
+.. image:: ../pictures/pool_list.png
+   :align: left
+   :scale: 50%
+
+Configure the Internal VS
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+* Configure a VS (type Internal) named ``syslog-tls-virtual`` 
+* With service port ``6514`` 
+* Server SSL Profile : ``serverssl``
+* Pool : logging-node-tls (created in the previous step)
 
-Enable Rate Limiting from the Security Dashboard
-------------------------------------------------
 
 
 Test your Rate Limiting config