Merge branch 'dev'

f5devcentral · Nov 27, 2024 · 42a786f · 42a786f
2 parents 5a25626 + 5429773
commit 42a786f
Show file tree

Hide file tree

Showing 225 changed files with 4,875 additions and 839 deletions.
diff --git a/docs/automating_rseries.rst b/docs/automating_rseries.rst
@@ -2,21 +2,21 @@
 Automating F5OS on rSeries 
 ===========================================
 
-Since F5OS is an API first architecture, everything is automatable at the F5OS layer. There are F5OS API's for every function, and the GUI and CLI are built on top of the API. API reference materials are published on clouddocs.f5.com in addtion to the most common API workflows. In addition, Terraform providers and Ansible collections are also available for F5OS, and more functionality is being added with each release of those packages.
+Since F5OS is an API first architecture, everything is automatable at the F5OS layer. There are F5OS API's for every function, and the GUI and CLI are built on top of the API. API reference materials are published on clouddocs.f5.com in addition to the most common API workflows. In addition, Terraform providers and Ansible collections are also available for F5OS, and more functionality is being added with each release of those packages.
 
-If you want to see what API functions are available you can view the API reference documentation for the specific F5OS version you are running. As you can see, rSeries / F5OS-A have its own API reference pages and F5OS-C / VELOS have similar pages, most of the API calls are common expcept for those that are specific to the platform.
+If you want to see what API functions are available you can view the API reference documentation for the specific F5OS version you are running. As you can see, rSeries / F5OS-A have its own API reference pages and F5OS-C / VELOS have similar pages, most of the API calls are common except for those that are specific to the platform.
 
 `F5OS-A/F5 rSeries - API <https://clouddocs.f5.com/api/rseries-api/rseries-api-index.html>`_
 
 .. image:: images/automating_rseries/image1.png
   :align: center
   :scale: 70%
 
-The API workflows section has an index which maps to all the common API workflow examples in the rSeries planning guide. In addtion, there is an accompanying Postman collection which can be downloaded and used within your own environment if you want to become familiar with the F5OS API.
+The API workflows section has an index which maps to all the common API workflow examples in the rSeries planning guide. In addition, there is an accompanying Postman collection which can be downloaded and used within your own environment if you want to become familiar with the F5OS API.
 
 `F5 rSeries API Workflows <https://clouddocs.f5.com/training/community/rseries-training/html/rseries_api_workflows.html>`_
 
-Below is a smaple of some of the workflows available in the link above, and there are many more.
+Below is a sample of some of the workflows available in the link above, and there are many more.
 
 .. image:: images/automating_rseries/image2.png
   :align: center
@@ -25,21 +25,29 @@ Below is a smaple of some of the workflows available in the link above, and ther
 F5OS Ansible Collection
 =======================
 
-Ansible collections have been created for F5OS for some of the more common tasks. Addtional API workflows are constantly being added to the collections.
+Ansible collections have been created for F5OS for some of the more common tasks. Additional API workflows are constantly being added to the collections.
 
 
 `F5OS modules Ansible collection <https://clouddocs.f5.com/products/orchestration/ansible/devel/f5os/F5OS-index.html>`_
 
+F5 Professional Services F5OS Ansible Collection
+================================================
+
+Ansible collections have been created for F5OS for some of the more common tasks. The Ansible modules contributed to the F5 DevCentral community by F5 Professional Services. Additional API workflows are constantly being added to the collections.
+
+
+`F5 Professional Services F5OS modules Ansible collection <https://f5devcentral.github.io/f5-ps-ansible/>`_
+
 F5OS Terraform Provider
 =======================
 
-Terraform providers have been created for F5OS for some of the more common tasks. Addtional API workflows are constantly being added to the providers. An overview of the F5OS provider is available using the link below.
+Terraform providers have been created for F5OS for some of the more common tasks. Additional API workflows are constantly being added to the providers. An overview of the F5OS provider is available using the link below.
 
 `F5OS Provider Overview <https://clouddocs.f5.com/products/orchestration/terraform/latest/F5OS/f5os-index.html#f5os-index>`_
 
 The github location of the Terraform provider files is at the following location.
 
-`Terraform Provider F5OS v1.3.0 <https://github.com/F5Networks/terraform-provider-F5OS/releases>`_
+`Terraform Provider F5OS v1.4.0 <https://github.com/F5Networks/terraform-provider-F5OS/releases>`_
 
 Getting Started with F5OS Automation
 ====================================
@@ -171,7 +179,7 @@ Below is the output from the API query above:
 Curl Examples
 ==============
 
-Below is an API call using Curl to an rSeries system. Note, that the Curl request is using **username:password** to authenticate. In the response, an authentication token is generated by F5OS with the header **X-Auth-Token**. This token can be used for future reqests instead of using the basic authentication method until the token times out. At that point you'll need to refresh the token.
+Below is an API call using Curl to an rSeries system. Note, that the Curl request is using **username:password** to authenticate. In the response, an authentication token is generated by F5OS with the header **X-Auth-Token**. This token can be used for future requests instead of using the basic authentication method until the token times out. At that point you'll need to refresh the token.
 
 .. code-block:: bash
 
@@ -194,7 +202,7 @@ Below is an API call using Curl to an rSeries system. Note, that the Curl reques
 
     {"ietf-restconf:restconf":{"data":{},"operations":{},"yang-library-version":"2019-01-04"}}%                                                                                                                                                                                                  prompt% 
 
-You may send API calls to either port 8888 or port 443. The URI path will change slightly depending on which TCP port you choose to use. For API calls sent to port 443, the initial path will be **/api**, while API calls to port 8888 will start with **/restconf**. F5OS also listens on port 80 and will redirect to TCP port 443. The API call below is sent to port 443, note the intial path will be **/api/data**. 
+You may send API calls to either port 8888 or port 443. The URI path will change slightly depending on which TCP port you choose to use. For API calls sent to port 443, the initial path will be **/api**, while API calls to port 8888 will start with **/restconf**. F5OS also listens on port 80 and will redirect to TCP port 443. The API call below is sent to port 443, note the initial path will be **/api/data**. 
 
 .. code-block:: bash
 
@@ -307,7 +315,7 @@ You may send API calls to either port 8888 or port 443. The URI path will change
     }
     prompt% 
 
-You may send API calls to either port 8888 or port 443. The URI path will change slightly depending on which TCP port you choose to use. For API calls sent to port 443, the initial path will be **/api**, while API calls to port 8888 will start with **/restconf**. F5OS also listens on port 80 and will redirect to TCP port 443. The API call below is sent to port 8888, note the intial path will be **/restconf/data**. 
+You may send API calls to either port 8888 or port 443. The URI path will change slightly depending on which TCP port you choose to use. For API calls sent to port 443, the initial path will be **/api**, while API calls to port 8888 will start with **/restconf**. F5OS also listens on port 80 and will redirect to TCP port 443. The API call below is sent to port 8888, note the initial path will be **/restconf/data**. 
 
 .. code-block:: bash
 

diff --git a/docs/images/initial_setup_of_rseries_network_layer/cpu-allocation.png b/docs/images/initial_setup_of_rseries_network_layer/cpu-allocation.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/dashboard.png b/docs/images/initial_setup_of_rseries_network_layer/dashboard.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/image1.png b/docs/images/initial_setup_of_rseries_network_layer/image1.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/image14.png b/docs/images/initial_setup_of_rseries_network_layer/image14.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/image2.png b/docs/images/initial_setup_of_rseries_network_layer/image2.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/image3.png b/docs/images/initial_setup_of_rseries_network_layer/image3.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/image4.png b/docs/images/initial_setup_of_rseries_network_layer/image4.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/image5.png b/docs/images/initial_setup_of_rseries_network_layer/image5.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/image6.png b/docs/images/initial_setup_of_rseries_network_layer/image6.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/memory-utilization.png b/docs/images/initial_setup_of_rseries_network_layer/memory-utilization.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/r10900-arch.png b/docs/images/initial_setup_of_rseries_network_layer/r10900-arch.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/storage-utilization.png b/docs/images/initial_setup_of_rseries_network_layer/storage-utilization.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image1.png b/docs/images/initial_setup_of_rseries_platform_layer/image1.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image12.png b/docs/images/initial_setup_of_rseries_platform_layer/image12.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image14.png b/docs/images/initial_setup_of_rseries_platform_layer/image14.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image15.png b/docs/images/initial_setup_of_rseries_platform_layer/image15.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image16.png b/docs/images/initial_setup_of_rseries_platform_layer/image16.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image2.png b/docs/images/initial_setup_of_rseries_platform_layer/image2.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image28.png b/docs/images/initial_setup_of_rseries_platform_layer/image28.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image3.png b/docs/images/initial_setup_of_rseries_platform_layer/image3.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image4.png b/docs/images/initial_setup_of_rseries_platform_layer/image4.png
diff --git a/docs/images/initial_setup_of_rseries_platform_layer/image5.png b/docs/images/initial_setup_of_rseries_platform_layer/image5.png
diff --git a/docs/images/monitoring_rseries/cpu-allocation.png b/docs/images/monitoring_rseries/cpu-allocation.png
diff --git a/docs/images/monitoring_rseries/image1.png b/docs/images/monitoring_rseries/image1.png
diff --git a/docs/images/monitoring_rseries/image2a.png b/docs/images/monitoring_rseries/image2a.png
diff --git a/docs/images/monitoring_rseries/image3a.png b/docs/images/monitoring_rseries/image3a.png
diff --git a/docs/images/monitoring_rseries/image4a.png b/docs/images/monitoring_rseries/image4a.png
diff --git a/docs/images/monitoring_rseries/r10900-arch.png b/docs/images/monitoring_rseries/r10900-arch.png
diff --git a/docs/images/monitoring_rseries/storage-utilization.png b/docs/images/monitoring_rseries/storage-utilization.png
diff --git a/docs/images/rseries_appliances/image1a.png b/docs/images/rseries_appliances/image1a.png
diff --git a/docs/images/rseries_appliances/image1afips.png b/docs/images/rseries_appliances/image1afips.png
diff --git a/docs/images/rseries_appliances/image1b.png b/docs/images/rseries_appliances/image1b.png
diff --git a/docs/images/rseries_appliances/image2a.png b/docs/images/rseries_appliances/image2a.png
diff --git a/docs/images/rseries_appliances/image2afips.png b/docs/images/rseries_appliances/image2afips.png
diff --git a/docs/images/rseries_appliances/image2b.png b/docs/images/rseries_appliances/image2b.png
diff --git a/docs/images/rseries_appliances/image2e.png b/docs/images/rseries_appliances/image2e.png
diff --git a/docs/images/rseries_appliances/image3b.png b/docs/images/rseries_appliances/image3b.png
diff --git a/docs/images/rseries_appliances/image3d.png b/docs/images/rseries_appliances/image3d.png
diff --git a/docs/images/rseries_appliances/image4b.png b/docs/images/rseries_appliances/image4b.png
diff --git a/docs/images/rseries_appliances/r12000image2.png b/docs/images/rseries_appliances/r12000image2.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/L1-network-interfaces.png b/docs/images/rseries_deploying_a_bigip_next_tenant/L1-network-interfaces.png
diff --git a/...images/rseries_deploying_a_bigip_next_tenant/Pasted_Image_10_29_24__5_38_PM.png b/...images/rseries_deploying_a_bigip_next_tenant/Pasted_Image_10_29_24__5_38_PM.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/add-an-instance-provider.png b/docs/images/rseries_deploying_a_bigip_next_tenant/add-an-instance-provider.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/admin-cm.png b/docs/images/rseries_deploying_a_bigip_next_tenant/admin-cm.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/assign-ip-addresses.png b/docs/images/rseries_deploying_a_bigip_next_tenant/assign-ip-addresses.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/central-manager-home.png b/docs/images/rseries_deploying_a_bigip_next_tenant/central-manager-home.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/cpu-dashboard.png b/docs/images/rseries_deploying_a_bigip_next_tenant/cpu-dashboard.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/create-3-times.png b/docs/images/rseries_deploying_a_bigip_next_tenant/create-3-times.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/create-a-new-instance.png b/docs/images/rseries_deploying_a_bigip_next_tenant/create-a-new-instance.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/create-instance-4k.png b/docs/images/rseries_deploying_a_bigip_next_tenant/create-instance-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/create-second-instance.png b/docs/images/rseries_deploying_a_bigip_next_tenant/create-second-instance.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/creating-instance-4k.png b/docs/images/rseries_deploying_a_bigip_next_tenant/creating-instance-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/creating-instance.png b/docs/images/rseries_deploying_a_bigip_next_tenant/creating-instance.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/dashboard-system.png b/docs/images/rseries_deploying_a_bigip_next_tenant/dashboard-system.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/default-l1network-pick-4k.png b/docs/images/rseries_deploying_a_bigip_next_tenant/default-l1network-pick-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/default-l1network-pick.png b/docs/images/rseries_deploying_a_bigip_next_tenant/default-l1network-pick.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/delete-instance-from-cm.png b/docs/images/rseries_deploying_a_bigip_next_tenant/delete-instance-from-cm.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/delete-tenant-locally.png b/docs/images/rseries_deploying_a_bigip_next_tenant/delete-tenant-locally.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/deletetion-in-progress.png b/docs/images/rseries_deploying_a_bigip_next_tenant/deletetion-in-progress.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/deletion-in-progress.png b/docs/images/rseries_deploying_a_bigip_next_tenant/deletion-in-progress.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/deploy-ha.png b/docs/images/rseries_deploying_a_bigip_next_tenant/deploy-ha.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/enable-ha.png b/docs/images/rseries_deploying_a_bigip_next_tenant/enable-ha.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/file-upload-tenant-body.png b/docs/images/rseries_deploying_a_bigip_next_tenant/file-upload-tenant-body.png
diff --git a/...mages/rseries_deploying_a_bigip_next_tenant/file-upload-tenant-headers-f5os.png b/...mages/rseries_deploying_a_bigip_next_tenant/file-upload-tenant-headers-f5os.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/file-upload-tenant-headers.png b/docs/images/rseries_deploying_a_bigip_next_tenant/file-upload-tenant-headers.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/fingerprint.png b/docs/images/rseries_deploying_a_bigip_next_tenant/fingerprint.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/ha-nodes.png b/docs/images/rseries_deploying_a_bigip_next_tenant/ha-nodes.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/ha-vlans.png b/docs/images/rseries_deploying_a_bigip_next_tenant/ha-vlans.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/healthy-instance.png b/docs/images/rseries_deploying_a_bigip_next_tenant/healthy-instance.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image1.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image1.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image10new.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image10new.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image2.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image2.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image2a.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image2a.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image3.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image3.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image4.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image4.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image40.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image40.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image41.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image41.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image42.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image42.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image5.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image5.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image50.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image50.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image6.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image6.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image7.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image7.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image71.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image71.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image72.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image72.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image73.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image73.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image74.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image74.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image75.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image75.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image76.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image76.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image77.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image77.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image78.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image78.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image79.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image79.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image80.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image80.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image81.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image81.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image82.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image82.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image83.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image83.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image84.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image84.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image85.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image85.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image86.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image86.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image87.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image87.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image88.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image88.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image89.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image89.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/image9new.png b/docs/images/rseries_deploying_a_bigip_next_tenant/image9new.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/infrastructure.png b/docs/images/rseries_deploying_a_bigip_next_tenant/infrastructure.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/ip-to-vlan-4k.png b/docs/images/rseries_deploying_a_bigip_next_tenant/ip-to-vlan-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/ip-to-vlan.png b/docs/images/rseries_deploying_a_bigip_next_tenant/ip-to-vlan.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/l1networks.png b/docs/images/rseries_deploying_a_bigip_next_tenant/l1networks.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/license.png b/docs/images/rseries_deploying_a_bigip_next_tenant/license.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/login.png b/docs/images/rseries_deploying_a_bigip_next_tenant/login.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/lowestnumber.png b/docs/images/rseries_deploying_a_bigip_next_tenant/lowestnumber.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/metrics.png b/docs/images/rseries_deploying_a_bigip_next_tenant/metrics.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/networking-ip-addresses.png b/docs/images/rseries_deploying_a_bigip_next_tenant/networking-ip-addresses.png
diff --git a/...ages/rseries_deploying_a_bigip_next_tenant/next-internal-networking-diagram.png b/...ages/rseries_deploying_a_bigip_next_tenant/next-internal-networking-diagram.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/next-mgmt-addressing-4k.png b/docs/images/rseries_deploying_a_bigip_next_tenant/next-mgmt-addressing-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/next-mgmt-addressing.png b/docs/images/rseries_deploying_a_bigip_next_tenant/next-mgmt-addressing.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/next-networking.png b/docs/images/rseries_deploying_a_bigip_next_tenant/next-networking.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/next-vlans-4k.png b/docs/images/rseries_deploying_a_bigip_next_tenant/next-vlans-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/next-vlans.png b/docs/images/rseries_deploying_a_bigip_next_tenant/next-vlans.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/provider-properties.png b/docs/images/rseries_deploying_a_bigip_next_tenant/provider-properties.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/provider-summary.png b/docs/images/rseries_deploying_a_bigip_next_tenant/provider-summary.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/provider-username.png b/docs/images/rseries_deploying_a_bigip_next_tenant/provider-username.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/providers.png b/docs/images/rseries_deploying_a_bigip_next_tenant/providers.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/r4k-l1-networking-mapping.png b/docs/images/rseries_deploying_a_bigip_next_tenant/r4k-l1-networking-mapping.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/review-and-deploy-second.png b/docs/images/rseries_deploying_a_bigip_next_tenant/review-and-deploy-second.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/rseries-properties-1-4k.png b/docs/images/rseries_deploying_a_bigip_next_tenant/rseries-properties-1-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/rseries-properties-1.png b/docs/images/rseries_deploying_a_bigip_next_tenant/rseries-properties-1.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/second-instance-create.png b/docs/images/rseries_deploying_a_bigip_next_tenant/second-instance-create.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/second-ip-addresses.png b/docs/images/rseries_deploying_a_bigip_next_tenant/second-ip-addresses.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/second-management.png b/docs/images/rseries_deploying_a_bigip_next_tenant/second-management.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/second-vlans.png b/docs/images/rseries_deploying_a_bigip_next_tenant/second-vlans.png
diff --git a/.../images/rseries_deploying_a_bigip_next_tenant/select-bigip-next-instance-4k.png b/.../images/rseries_deploying_a_bigip_next_tenant/select-bigip-next-instance-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/select-bigip-next-instance.png b/docs/images/rseries_deploying_a_bigip_next_tenant/select-bigip-next-instance.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/self-ips-external.png b/docs/images/rseries_deploying_a_bigip_next_tenant/self-ips-external.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/slef-ips.png b/docs/images/rseries_deploying_a_bigip_next_tenant/slef-ips.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/start-adding-instances.png b/docs/images/rseries_deploying_a_bigip_next_tenant/start-adding-instances.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/start-creating-4k.png b/docs/images/rseries_deploying_a_bigip_next_tenant/start-creating-4k.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/start-creating.png b/docs/images/rseries_deploying_a_bigip_next_tenant/start-creating.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/start-managing.png b/docs/images/rseries_deploying_a_bigip_next_tenant/start-managing.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/summary-review-deploy.png b/docs/images/rseries_deploying_a_bigip_next_tenant/summary-review-deploy.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/tenant-overview.png b/docs/images/rseries_deploying_a_bigip_next_tenant/tenant-overview.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/tenant-running.png b/docs/images/rseries_deploying_a_bigip_next_tenant/tenant-running.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11a.png b/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11a.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11aa.png b/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11aa.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11aaa.png b/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11aaa.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11ab.png b/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11ab.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11ac.png b/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11ac.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11b.png b/docs/images/rseries_deploying_a_bigip_next_tenant/tenant11b.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/traffic-vlans.png b/docs/images/rseries_deploying_a_bigip_next_tenant/traffic-vlans.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/upload-id.png b/docs/images/rseries_deploying_a_bigip_next_tenant/upload-id.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/upload-image-api.png b/docs/images/rseries_deploying_a_bigip_next_tenant/upload-image-api.png
diff --git a/docs/images/rseries_deploying_a_bigip_next_tenant/what-youll-need.png b/docs/images/rseries_deploying_a_bigip_next_tenant/what-youll-need.png
diff --git a/docs/images/rseries_deploying_a_tenant/dashboard.png b/docs/images/rseries_deploying_a_tenant/dashboard.png
diff --git a/docs/images/rseries_deploying_a_tenant/image1.png b/docs/images/rseries_deploying_a_tenant/image1.png
diff --git a/docs/images/rseries_deploying_a_tenant/image2.png b/docs/images/rseries_deploying_a_tenant/image2.png
diff --git a/docs/images/rseries_deploying_a_tenant/image3.png b/docs/images/rseries_deploying_a_tenant/image3.png
diff --git a/docs/images/rseries_deploying_a_tenant/image4.png b/docs/images/rseries_deploying_a_tenant/image4.png
diff --git a/docs/images/rseries_deploying_a_tenant/image75.png b/docs/images/rseries_deploying_a_tenant/image75.png
diff --git a/docs/images/rseries_deploying_a_tenant/image77.png b/docs/images/rseries_deploying_a_tenant/image77.png
diff --git a/docs/images/rseries_deploying_a_tenant/image78.png b/docs/images/rseries_deploying_a_tenant/image78.png
diff --git a/docs/images/rseries_deploying_a_tenant/image79.png b/docs/images/rseries_deploying_a_tenant/image79.png
diff --git a/docs/images/rseries_deploying_a_tenant/image80-a.png b/docs/images/rseries_deploying_a_tenant/image80-a.png
diff --git a/docs/images/rseries_deploying_a_tenant/image80.png b/docs/images/rseries_deploying_a_tenant/image80.png
diff --git a/docs/images/rseries_deploying_a_tenant/image81.png b/docs/images/rseries_deploying_a_tenant/image81.png
diff --git a/docs/images/rseries_deploying_a_tenant/image82.png b/docs/images/rseries_deploying_a_tenant/image82.png
diff --git a/docs/images/rseries_deploying_a_tenant/image84.png b/docs/images/rseries_deploying_a_tenant/image84.png
diff --git a/docs/images/rseries_deploying_a_tenant/image85.png b/docs/images/rseries_deploying_a_tenant/image85.png
diff --git a/docs/images/rseries_deploying_a_tenant/image86.png b/docs/images/rseries_deploying_a_tenant/image86.png
diff --git a/docs/images/rseries_deploying_a_tenant/image87.png b/docs/images/rseries_deploying_a_tenant/image87.png
diff --git a/docs/images/rseries_deploying_a_tenant/image88.png b/docs/images/rseries_deploying_a_tenant/image88.png
diff --git a/docs/images/rseries_deploying_a_tenant/storage-utilization.png b/docs/images/rseries_deploying_a_tenant/storage-utilization.png
diff --git a/docs/images/rseries_f5os_configuration_backup_and_restore/download.png b/docs/images/rseries_f5os_configuration_backup_and_restore/download.png
diff --git a/docs/images/rseries_f5os_configuration_backup_and_restore/image1.png b/docs/images/rseries_f5os_configuration_backup_and_restore/image1.png
diff --git a/docs/images/rseries_f5os_configuration_backup_and_restore/image3.png b/docs/images/rseries_f5os_configuration_backup_and_restore/image3.png
diff --git a/docs/images/rseries_inside_the_tenant/image10.png b/docs/images/rseries_inside_the_tenant/image10.png
diff --git a/docs/images/rseries_inside_the_tenant/image11.png b/docs/images/rseries_inside_the_tenant/image11.png
diff --git a/docs/images/rseries_inside_the_tenant/image5.png b/docs/images/rseries_inside_the_tenant/image5.png
diff --git a/docs/images/rseries_inside_the_tenant/image6.png b/docs/images/rseries_inside_the_tenant/image6.png
diff --git a/docs/images/rseries_inside_the_tenant/image8.png b/docs/images/rseries_inside_the_tenant/image8.png
diff --git a/docs/images/rseries_inside_the_tenant/image9.png b/docs/images/rseries_inside_the_tenant/image9.png
diff --git a/docs/images/rseries_monitoring_snmp/image2.png b/docs/images/rseries_monitoring_snmp/image2.png
diff --git a/docs/images/rseries_networking/image2.png b/docs/images/rseries_networking/image2.png
diff --git a/docs/images/rseries_networking/image3.png b/docs/images/rseries_networking/image3.png
diff --git a/docs/images/rseries_security/appliance-mode.png b/docs/images/rseries_security/appliance-mode.png
diff --git a/docs/images/rseries_security/audit-logging.png b/docs/images/rseries_security/audit-logging.png
diff --git a/docs/images/rseries_security/client-cert1.png b/docs/images/rseries_security/client-cert1.png
diff --git a/docs/images/rseries_security/deny-root-ssh.png b/docs/images/rseries_security/deny-root-ssh.png
diff --git a/docs/images/rseries_security/guest-user-restricted.png b/docs/images/rseries_security/guest-user-restricted.png
diff --git a/docs/images/rseries_security/guest-user.png b/docs/images/rseries_security/guest-user.png
diff --git a/docs/images/rseries_security/image2.png b/docs/images/rseries_security/image2.png
diff --git a/docs/images/rseries_security/image4-new.png b/docs/images/rseries_security/image4-new.png
diff --git a/docs/images/rseries_security/image6.png b/docs/images/rseries_security/image6.png
diff --git a/docs/images/rseries_security/imagecert2a.png b/docs/images/rseries_security/imagecert2a.png
diff --git a/docs/images/rseries_security/imagetoken1.png b/docs/images/rseries_security/imagetoken1.png
diff --git a/docs/images/rseries_security/passwordpolicy1.png b/docs/images/rseries_security/passwordpolicy1.png
diff --git a/docs/images/rseries_security/proxy-licensing.png b/docs/images/rseries_security/proxy-licensing.png
diff --git a/docs/images/rseries_security/screenshot.png b/docs/images/rseries_security/screenshot.png
diff --git a/docs/images/rseries_security/security-ciphers.png b/docs/images/rseries_security/security-ciphers.png
diff --git a/docs/images/rseries_security/token-lifetime.png b/docs/images/rseries_security/token-lifetime.png
diff --git a/docs/images/rseries_software_upgrades/image1.png b/docs/images/rseries_software_upgrades/image1.png
diff --git a/docs/images/rseries_software_upgrades/image3.png b/docs/images/rseries_software_upgrades/image3.png
diff --git a/docs/images/rseries_software_upgrades/image4.png b/docs/images/rseries_software_upgrades/image4.png
diff --git a/docs/images/rseries_software_upgrades/image5.png b/docs/images/rseries_software_upgrades/image5.png
diff --git a/docs/images/rseries_software_upgrades/image6.png b/docs/images/rseries_software_upgrades/image6.png
diff --git a/docs/images/rseries_software_upgrades/image7.png b/docs/images/rseries_software_upgrades/image7.png
diff --git a/docs/images/rseries_software_upgrades/image8.png b/docs/images/rseries_software_upgrades/image8.png
diff --git a/docs/index.rst b/docs/index.rst
@@ -16,6 +16,7 @@ Planning for rSeries Guide
    initial_setup_of_rseries_platform_layer.rst
    initial_setup_of_rseries_network_layer.rst
    rseries_deploying_a_tenant.rst
+   rseries_deploying_a_bigip_next_tenant.rst
    rseries_inside_the_tenant.rst
    rseries_security.rst
    rseries_software_upgrades.rst

diff --git a/docs/initial_setup_of_rseries_network_layer.rst b/docs/initial_setup_of_rseries_network_layer.rst
@@ -8,24 +8,53 @@ Initial Setup of the rSeries Network Layer
 rSeries Dashboard
 -----------------
 
-The rSeries Dashboard will provide a visual system summary of the appliance, including **System Summary**, **Network**, **CPU**, and **Active Alarms**. It will also list the total number of vCPUs available for multitenancy and how many are currently in use. There is also a tenant overview showing a quick summary of tenant status and basic parameters. 
+The rSeries Dashboard will provide a visual system summary of the appliance, including **System Summary**, **Tenant Overview**, **Network**, **CPU**, and **Active Alarms**. It will also list the total number of vCPUs available for multitenancy and how many are currently in use. There is also a tenant overview showing a quick summary of tenant status and basic parameters. New in version F5OS-A 1.8.0 is more granular **Memory Utilization** and **Storage Utilization** Details.
 
 .. image:: images/initial_setup_of_rseries_network_layer/image1.png
   :align: center
   :scale: 70% 
 
+More granular **Memory Utilization** is displayed showing how much memory is dedicated and in use by **F5OS System** vs. **F5OS Tenants**.
+
+.. image:: images/initial_setup_of_rseries_network_layer/memory-utilization.png
+  :align: center
+  :scale: 70% 
+
+There is also more granularity showing **Storage Utilization**. In the below example, you can see that F5OS has utilized 60% of the 109.7GB of disk it has dedicated. You can also see that there is 448.6GB available for **F5OS Tenant Disks** (BIG-IP Tenant) virtual disks, and that currently only 5% is used. This is the space shared by all BIG-IP Tenants virtual disks. It is important to remember that TMOS based BIG-IP virtual disks utilize thin provisioning, so the TMOS tenant may think it has more storage but in reality it is using much less capacity on the physical disk. You can see this by the **BIG-IP Tenant** utilizations. In the output below, there are two BIG-IP tenants (fix-ll & test-tenant). One has been allocated 80GB of disk while the other has been allocated 82GB of disk, however the actual size on disk is much lower (~5-7GB each). Lastly, there is a single BIG-IP Next tenant that has 25GB allocated to it, but is currently utilizing 7% of that space.
+
+.. NOTE:: Storage utilization and allocation may be different on various rSeries platforms.
+
+
+.. image:: images/initial_setup_of_rseries_network_layer/storage-utilization.png
+  :align: center
+  :scale: 70% 
+
 The **Network** tab will provide a visual representation of all networking ports on the system. Each port will be color coded **Green** for **Up** status, and **Red** for **Down** status. The current **Pipeline** mapping is also displayed, which shows the external port mapping to internal pipelines.
 
 .. image:: images/initial_setup_of_rseries_network_layer/image2.png
   :align: center
   :scale: 70% 
 
-The **CPU** tab shows all the available CPUs in the system, along with their **Current**, **5 Second**, **1 Minute**, and **5 Minute** averages.
+The **CPU** tab shows all the available CPUs in the system, along with their current utilization. It also displays what functionality is using the CPU. It could be **Tenants**, **F5OS Data Mover**, **F5OS Dedicated** or **F5OS**. The image below depicts an r10900 which has 12 vCPUs dedicated to the F5OS/Datamover functions. 
 
 .. image:: images/initial_setup_of_rseries_network_layer/image3.png
   :align: center
   :scale: 70% 
 
+For reference below is the architecture of the r10900. Note that there are 12 vCPUs dedicated to the F5OS/Datamover functions. Half of those vCPUs are dedicated for F5OS while the other half provide datamover functionality, which is the CPU to FPGA interconnect. 
+
+.. image:: images/initial_setup_of_rseries_network_layer/r10900-arch.png
+  :align: center
+  :scale: 70% 
+
+Currently 25% of the vCPUs are in use by tenants, and this leaves 50% of the CPU's available for F5OS to use as needed. 
+
+.. image:: images/initial_setup_of_rseries_network_layer/cpu-allocation.png
+  :align: center
+  :scale: 70% 
+
+
+
 The  **Active Alarms** tab will display any active alerts or alarms for the system. 
 
 .. image:: images/initial_setup_of_rseries_network_layer/image4.png
@@ -44,6 +73,8 @@ Network Settings - > Port Groups
 
 Before configuring any interfaces, VLANs, or Link Aggregation Groups (LAG’s) you’ll need to configure the portgroups so that physical interfaces on the appliance are configured for the proper speed and bundling. The portgroup component is used to control the mode of the physical ports. This controls whether a port is bundled or unbundled, and the port speed. Currently the high-speed ports do not support unbundling. Adjacent high-speed ports (**1.0** and **2.0** on both the r5000/r10000 series) and (**11.0** & **12.0** on the r10000 series) must be configured in the same mode and speed currently. Either both are configured for 40Gb or both are configured for 100Gb; you cannot mix and match on the adjacent high-speed ports. You cannot break out these ports to lower speeds (25Gb or 10Gb) via a breakout cable as this is currently unsupported. Low speed 25Gb/10Gb ports (**3.0** - **10.0** on both the r5000/r10000 series and **13.0*** - **20.0** on the r10000 series) can be configured independently, and adjacent low speed ports can have different speed values (10Gb or 25Gb). The term, **portgroup** is used rather than simply “port” because some front panel ports may accept different types of SFPs. Depending on the portgroup mode value, a different FPGA version is loaded, and the speed of the port is adjusted accordingly. Changing the portgroup configuration will require a reboot of the appliance to load a new FPGA bitstream. The user can modify the portgroup mode as needed through the F5OS CLI, webUI or API.
 
+.. Note:: The QSFP+ & QSFP28 optics cannot be configured for unbundled mode prior to F5OS-A 1.8.0 - 4 x 25Gb (with a 100Gb QSFP28 optic) or 4 x 10Gb (with a 40Gb QSFP+ optic). F5OS-A 1.8.0 added breakout cable support for 4 x 10Gb on the high-speed ports (**1.0**, **2.0**, **11.0**, **12.0** on the r10000, r12000) & (**1.0**, **2.0** on the r5000). These ports do not support 4 x 25Gb at this time.
+
 .. image:: images/initial_setup_of_rseries_network_layer/image5.png
   :align: center
   :scale: 70% 
@@ -93,7 +124,7 @@ You must commit for any changes to take effect. This will require a reboot of th
     appliance-1(config-portgroup-10)# 
 
 
-Possible options for **MODE** depend on which port you are configuring. For the high-speed ports on the r10000/r5000, supported modes are: **MODE_40GB** or **MODE_100GB**. For the low-speed ports possible options for **MODE** are: **MODE_10GB** and **MODE_25GB**. You can optionally configure the portgroup **name** and ddm **poll frequency**. You can display the current configuration of the existing portgroups by running the CLI command **show running-config portgroups**. Below is the example output from an r5000 appliance:
+Possible options for **MODE** depend on which port you are configuring. For the high-speed ports on the r10000/r5000, supported modes are: **MODE_40GB**, **MODE_100GB**, or **MODE_4x10GB** (added in F5OS-A 1.8.0). For the low-speed ports possible options for **MODE** are: **MODE_10GB** and **MODE_25GB**. You can optionally configure the portgroup **name** and ddm **poll frequency**. You can display the current configuration of the existing portgroups by running the CLI command **show running-config portgroups**. Below is the example output from an r5000 appliance:
 
 .. code-block:: bash
 
@@ -2650,13 +2681,13 @@ Link Aggregation Groups (LAGs) can be configured in the F5OS webUI via the **Net
 
 You can add a new LAG or edit an existing one. For **LAG Type** the options are **LACP** or **STATIC**. If you choose LACP then you have additional options for **LACP Interval** (**SLOW** or **FAST**) and **LACP Mode** (**ACTIVE** or **PASSIVE**). LACP best practices should follow previous BIG-IP examples as outlined in the links below. Note in BIG-IP the term **Trunks** is used in place of LAG which is used in F5OS: 
 
-https://support.f5.com/csp/article/K1689
+`K1689: Overview of trunks on BIG-IP platforms <https://my.f5.com/manage/s/article/K1689>`_
 
-https://support.f5.com/csp/article/K13142
+`K13142: Configure the BIG-IP system to interface with Cisco virtual PortChannel <https://support.f5.com/csp/article/K13142>`_
 
 The following solution article provides guidance for setting up VELOS LAG interfaces and LACP with Cisco Nexus 9000 series switches, and this would be similar guidance for rSeries:
 
-https://support.f5.com/csp/article/K33431212
+`K33431212: Configure LAGs with LACP between the VELOS system and Cisco Nexus 9000 series switches <https://support.f5.com/csp/article/K33431212>`_
 
 
 Once you have configured the **LAG Type** and LACP options, you can add any physical interfaces within the rSeries appliance to be part of a LAG. Finally, you can configure the **Native VLAN** (for untagged VLAN), and what **Trunked VLANs** (tagged) you’d like to add to this LAG interface.

diff --git a/docs/initial_setup_of_rseries_platform_layer.rst b/docs/initial_setup_of_rseries_platform_layer.rst
@@ -338,7 +338,7 @@ To set System Time settings, use the following API call as an example. This will
 
   PATCH https://{{rseries_appliance1_ip}}:8888/restconf/data/
 
-Below is the body of the API call contianing the desired configuration:
+Below is the body of the API call containing the desired configuration:
 
 .. code-block:: json
 
@@ -1105,7 +1105,7 @@ Then send the Base Reg Key in the body of the get-dossier API call below:
 
     POST https://{{rseries_appliance1_ip}}:8888/restconf/data/openconfig-system:system/f5-system-licensing:licensing/f5-system-licensing-install:get-dossier
 
-Within the body of API call, enter your registation-key. Note, in the example below the actual Registration Key has been obfuscated with XXXX's.
+Within the body of API call, enter your registration-key. Note, in the example below the actual Registration Key has been obfuscated with XXXX's.
 
 
 .. code-block:: json
@@ -1653,7 +1653,7 @@ Once the qkview is generated, you can click the checkbox next to it, and then se
   :align: center
   :scale: 70%
 
-If you would like to store iHealth credentials within the configuration you may do so via the CLI. Enter config mode, and then use the system diagnostics ihealth config command to configure a username and password.
+If you would like to store iHealth credentials within the configuration you may do so via the CLI. Enter config mode, and then use the **system diagnostics ihealth config** command to configure a username and password.
 
 .. code-block:: bash
 

diff --git a/docs/migration_to_rseries.rst b/docs/migration_to_rseries.rst
@@ -3,7 +3,7 @@ Migration to rSeries
 =====================
 
 
-F5 understands migrating configurations to new platforms can be a challenge and we’ve developed a tool that will help customers migrate existing BIG-IP configurations into rSeries tenants. F5 BIG-IP Journeys app assists with migrating a configuration from any BIG-IP between versions 11.5.0 and current versions onto the rSeries platforms, which as of now runs on BIG-IP version 15.1.5. It allows:
+F5 understands migrating configurations to new platforms can be a challenge and we’ve developed a tool that will help customers migrate existing BIG-IP configurations into rSeries tenants. F5 BIG-IP Journeys app assists with migrating a configuration from any BIG-IP between versions 11.5.0 and current versions onto the rSeries platforms.
 
 •	Flagging source configuration feature parity gaps and fixing them with custom or F5 recommended solutions, automated deployment of the updated configuration to rSeries tenant and post-deployment validation.
 •	List of possibly unsupported configuration features for the rSeries platform that the journeys app can identify