Lab 5.2: Resolve conflicts in the silo
--------------------------------------

.. note:: Estimated time to complete: **10 minutes**

.. include:: /accesslab.rst

Tasks
^^^^^

1. Navigate to **BIG-IP Device Silos** under the **Devices** menu and clock on the ``silolab``.

.. image:: ../pictures/img_module5_lab2-1.png
  :scale: 40%
  :align: center

2. Select Target Silo: **Default**, then click on **Compare Silos**.

.. image:: ../pictures/img_module5_lab2-2.png
  :scale: 40%
  :align: center

3. The comparison window opens. You can adjust the diff window with your cursor.

.. image:: ../pictures/img_module5_lab2-3.png
  :scale: 40%
  :align: center

4. Select Profile HTTP ``silo-lab-http-profile`` and look at the differences.

The values of the ``Accept XFF`` and ``Insert X-Forwarded-For`` are different. This is why the original import before adding 
to a Silo failed.

Silos are meant to be temporary so that an Admin can view and then resolve conflicts,. The ultimate goal is to be able to resolve any
conflicts from BIG-IQ and then remove this device from its Silo, and eventually re-import back into the default Silo. 

Let's resolve the conflict by renaming the offending profile from ``silo-lab-http-profile`` to ``silo-lab-http-profile2``.

.. image:: ../pictures/img_module5_lab2-4.png
  :scale: 40%
  :align: center

Click **Save & Close**.

5. Wait for the renaming operation to complete. Then click **Close**.

.. image:: ../pictures/img_module5_lab2-5.png
  :scale: 40%
  :align: center

6. The previous step only made changes on BIG-IQ. You must now deploy the changes to the BIG-IP device. Navigate to **Deployment > Evaluate & Deploy > Local Traffic & Network**.

.. image:: ../pictures/img_module5_lab2-6.png
  :scale: 40%
  :align: center

7. Create a new Evaluation, select the silo ``silolab`` and set a name. Next move the SJC-vBIGIP01 device from the **Available**
box to the **Selected** box.

.. image:: ../pictures/img_module5_lab2-7.png
  :scale: 40%
  :align: center

Click **Create**.

8. After the evaluation completes, review the differences by clicking on **View**. BIG-IQ is going to deploy the new renamed profile and re-deploy
   the VIP with the new profile attached. Then, remove the old profile with the old name.

- ``silo-lab-http-profile`` is removed
- ``silo-lab-http-profile2`` is added
- ``silo-lab-http-profile`` is removed from the VIP ``vip-silo-lab``
- ``silo-lab-http-profile2`` is attached to the VIP ``vip-silo-lab``

.. image:: ../pictures/img_module5_lab2-8.png
  :scale: 40%
  :align: center

9. Now **Deploy** the changes to the BIG-IP.

.. image:: ../pictures/img_module5_lab2-9.png
  :scale: 40%
  :align: center

10. Navigate to **Configuration > Local Traffic > Profile** and filter on ``silo-lab-http-profile``
    to confirm the HTTP profile was renamed. The original conflict that prevented import into the default
    Silo has now been fixed, however the SJC BIG-IP device is still in it's own Silo. The Next steps will
    remove the device form its own Silo and re-import into the default Silo. 

.. image:: ../pictures/img_module5_lab2-10.png
  :scale: 40%
  :align: center

You can eventually go to the BIG-IP **SJC-vBIGIP01.termmarc.com** to verify the profile
has been renamed correctly.