Merge branch 'dev'

f5devcentral · Jan 9, 2025 · 26e4c80 · 26e4c80
2 parents c7ea354 + 0a4e7e2
commit 26e4c80
Show file tree

Hide file tree

Showing 4 changed files with 30 additions and 1 deletion.
diff --git a/docs/images/rseries_multitenancy/image11.png b/docs/images/rseries_multitenancy/image11.png
diff --git a/docs/images/rseries_performance_and_sizing/image18.png b/docs/images/rseries_performance_and_sizing/image18.png
diff --git a/docs/rseries_performance_and_sizing.rst b/docs/rseries_performance_and_sizing.rst
@@ -250,7 +250,7 @@ The r4600 model has 16 CPUs (The 4000 platform does not utilize hyperthreading/v
 r2000 vCPU Sizing
 ------------------
 
-Each rSeries 2800 model has 8 CPUs (The 2000 platform does not utilize hyperthreading/vCPUs). No CPUs are dedicated to the F5OS platform layer which is different from the mid-range and high-end rSeries appliances. In the r2800 8 CPUs are available to be assigned to tenants (and only one tenant is supported). The diagram below depicts the r2800 CPU allocation: 
+Each rSeries 2800 model has 8 CPUs (The 2000 platform does not utilize hyperthreading/vCPUs). No CPUs are dedicated to the F5OS platform layer which is different from the mid-range and high-end rSeries appliances. In the r2800 8 CPUs are available to be assigned to tenants. Only one tenant is supported prior to F5OS-A 1.8.0, two tenants are supported from F5OS-A 1.8.0 and later. The diagram below depicts the r2800 CPU allocation: 
 
 .. image:: images/rseries_performance_and_sizing/image18.png
   :align: center

diff --git a/docs/rseries_security.rst b/docs/rseries_security.rst
@@ -436,6 +436,35 @@ In the response you will notice the certificate, key, and optional passphrase as
         }
     }
 
+If you would like to create a self-signed certificate, key, and add a passphrase via the API, you can issue the following API POST command.
+
+.. code-block:: bash
+
+    POST https://{{rseries_appliance1_ip}}:8888/restconf/data/openconfig-system:system/aaa/f5-openconfig-aaa-tls:tls/create-self-signed-cert
+
+In the body of the API call enter the following JSON syntax.
+
+.. code-block:: json
+
+    {
+        "f5-openconfig-aaa-tls:key-type": "encrypted-rsa",
+        "f5-openconfig-aaa-tls:key-size": 4096,
+        "f5-openconfig-aaa-tls:days-valid": 365,
+        "f5-openconfig-aaa-tls:key-passphrase": "Pa$$W0rd!23",
+        "f5-openconfig-aaa-tls:confirm-key-passphrase": "Pa$$W0rd!23",
+        "f5-openconfig-aaa-tls:name": "r5900-1-gsa.cpt.f5net.com",
+        "f5-openconfig-aaa-tls:organization": "f5",
+        "f5-openconfig-aaa-tls:unit": "sales",
+        "f5-openconfig-aaa-tls:city": "boston",
+        "f5-openconfig-aaa-tls:region": "ma",
+        "f5-openconfig-aaa-tls:country": "us",
+        "f5-openconfig-aaa-tls:email": "[email protected]",
+        "f5-openconfig-aaa-tls:san": "IP:172.22.50.1",
+        "f5-openconfig-aaa-tls:version": 1,
+        "f5-openconfig-aaa-tls:store-tls": "true"
+    }
+
+
 If you would like to upload a certificate, key, and passphrase you can issue the following API PUT command.
 
 .. code-block:: bash