diff --git a/docs/rseries_deploying_a_bigip_next_tenant.rst b/docs/rseries_deploying_a_bigip_next_tenant.rst index 0e3503b..224f84c 100644 --- a/docs/rseries_deploying_a_bigip_next_tenant.rst +++ b/docs/rseries_deploying_a_bigip_next_tenant.rst @@ -146,10 +146,10 @@ The rSeries device will then be added as a Provider into Central Manager, which :align: center :scale: 70% -Creating a BIG-IP Next Instance via the rSeries Provider in Central Manager -=========================================================================== +Creating a BIG-IP Next Instance on rSeries 5k,10k,12k Models via the rSeries Provider in Central Manager +======================================================================================================= -BIG-IP Next Central Manager refers to BIG-IP Next as **Instances**. This is because the BIG-IP Next Instance could be a **Tenant** running on an F5OS-based platform (rSeries,VELOS), or it could be a VE running on a hypervisor such as VMware. The term Instance is a generic term which will apply to both types of environments. To create a BIG-IP Next Instance go to **Instances->My Instances**, and then click the **Start Adding Instances** button. +BIG-IP Next Central Manager refers to BIG-IP Next as **Instances**. This is because the BIG-IP Next Instance could be a **Tenant** running on an F5OS-based platform (rSeries, VELOS), or it could be a VE running on a hypervisor such as VMware. The term Instance is a generic term which will apply to both types of environments. To create a BIG-IP Next Instance go to **Instances -> My Instances**, and then click the **Start Adding Instances** button. .. image:: images/rseries_deploying_a_bigip_next_tenant/start-adding-instances.png :align: center @@ -255,7 +255,114 @@ You can then monitor the status of the instance being created. It will take some :align: center :scale: 70% - +Creating a BIG-IP Next Instance on rSeries 2k,4k Models via the rSeries Provider in Central Manager +======================================================================================================= + +BIG-IP Next Central Manager refers to BIG-IP Next as **Instances**. This is because the BIG-IP Next Instance could be a **Tenant** running on an F5OS-based platform (rSeries, VELOS), or it could be a VE running on a hypervisor such as VMware. The term Instance is a generic term which will apply to both types of environments. To create a BIG-IP Next Instance go to **Instances -> My Instances**, and then click the **Start Adding Instances** button. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/start-adding-instances.png + :align: center + :scale: 70% + +The next option allows you to import a previously created instance, or to create a new one. Select **Create a New Instance**. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/create-a-new-instance.png + :align: center + :scale: 70% + +Review the requirements of what you'll need before proceeding, then click **Next**. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/what-youll-need.png + :align: center + :scale: 70% + +Enter a hostname for the BIG-IP Next instance, and an optional description. Then, in the drop down box select **rSeries Standalone**, and then click the **Start Creating** button. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/start-creating.png + :align: center + :scale: 70% + +From the **rSeries Provider** section select to rseries device that you added previously. Then click **Next**. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/select-bigip-next-instance.png + :align: center + :scale: 70% + +Next configure the rSeries Properties, which includes **Disk Size**, **CPU Cores**, **Tenant Image Name**, **Tenant Deployment File**, and **VLAN IDs**. When finished, click the **Done** button. + +.. Note:: The appropriate BIG-IP Next tenant image file should be loaded on the rSeries platform so that the Tenant Image Name and Tenant Deployment File can be selected in this screen. Currently there is no way to upload the image from Central Manager. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/rseries-properties-1.png + :align: center + :scale: 70% + +Enter the out-of-band **Management IP address**, **Network Prefix Length**, and **Gateway IP Address** and then click **Next**. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/next-mgmt-addressing.png + :align: center + :scale: 70% + +In the next section, you will setup the in-band networking for the Next instance. Here, you will map the internal **L1 Networks** inside the Next instance to VLANs and then add IP addresses to them. These would be the equivalent of self-ip addresses on BIG-IP. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/next-networking.png + :align: center + :scale: 70% + +For VELOS and rSeries r5000 and higher appliances only a single data interface (L1 Network) is surfaced to the BIG-IP Next tenant. For the rSeries r2000/r4000 appliances multiple L1 Networks will be surfaced to the tenant. +The tenant will see either 4, 6, or 8 L1 Networks, depending on the port-mode that is configured on the rSeries appliance. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/next-internal-networking-diagram.png + :align: center + :scale: 70% + + +Below is an example of an r10900 device. Click on **L1 Networks**, and note that the **DefaultL1Network** already exists and is mapped to the internal interface 1.1. Also note that it has zero VLANs assigned. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/l1networks.png + :align: center + :scale: 70% + +Click on **VLANs** and note that the VLANs you previously assigned to the instance are listed, however they are not mapped to any L1 Networks yet. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/next-vlans.png + :align: center + :scale: 70% + +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 an 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 format for each VLAN before you can assign the VLAN from the drop-down box. Leave the **Device Name** field 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 + :align: center + :scale: 70% + +Review all the changes, and then click the **Deploy** button. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/summary-review-deploy.png + :align: center + :scale: 70% + +You can then monitor the status of the instance being created. It will take some time for the deployment to complete. + +.. image:: images/rseries_deploying_a_bigip_next_tenant/creating-instance.png + :align: center + :scale: 70% BIG-IP Next Tenant Deployment via CLI -------------------------------------