Skip to content

Commit

Permalink
next instance
Browse files Browse the repository at this point in the history
  • Loading branch information
jimmccarron committed May 8, 2024
1 parent 1f542cc commit 3c85422
Show file tree
Hide file tree
Showing 6 changed files with 21 additions and 4 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions docs/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
18 changes: 17 additions & 1 deletion docs/rseries_deploying_a_bigip_next_tenant.rst
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,10 @@ BIG-IP Next Tenant Deployment via Central Manager

BIG-IP Next tenants (or instances as they are called in Central Manager) can be deployed using an rSeries **Provider**. a Provider in Central Manager provides connectivity to resources such as VELOS, rSeries, or VMware where BIG-IP Next instances can be deployed.

If you need instructions on installing Central Manager, or general BIG-IP Next documents refer to the link below.

`BIG-IP Next Documentation <https://clouddocs.f5.com/bigip-next/latest/>`_

Setting up an rSeries Provider in Central Manager
=================================================

Expand Down Expand Up @@ -211,12 +215,24 @@ Click on **VLANs** and note that the VLANs you previously assigned to the instan
:align: center
:scale: 70%

In the drop-down box for L1 Networks select the **DefaultL1Network** for all of your VLANs, and then click **Next**.
In the drop-down box for L1 Networks select the **DefaultL1Network** for all of your VLANs, and then click **Next**.

.. image:: images/rseries_deploying_a_bigip_next_tenant/default-l1network-pick.png
:align: center
:scale: 70%

Finally, you must assign IP addresses to each VLAN. Click on **IP Addresses**, and then click **Create** for each VLAN.

.. image:: images/rseries_deploying_a_bigip_next_tenant/networking-ip-addresses.png
:align: center
:scale: 70%

You'll need to add an IP address in <x.x.x.x/xx> format for each VLAN before you can assign the VLAN from the drop-down box. Leave the **Device Name** filed blank. When finished, click **Next**.

.. image:: images/rseries_deploying_a_bigip_next_tenant/ip-to-vlan.png
:align: center
:scale: 70%

In the **Troubleshooting** section you will setup a new local username and password for the Next instance that you can utilize for direct troubleshooting access. The default username and password will no longer work. Note that one an instance is under central management all configuration should be done though Central Manager, and not direct to the Next instance. Click **Next**.

.. image:: images/rseries_deploying_a_bigip_next_tenant/admin-cm.png
Expand Down
6 changes: 3 additions & 3 deletions docs/rseries_deploying_a_tenant.rst
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
===========================
Deploying an rSeries Tenant
===========================
==================================
Deploying an rSeries BIG-IP Tenant
==================================


------------------
Expand Down

0 comments on commit 3c85422

Please sign in to comment.