Add devices back to BIG-IQ after deleting them from a silo for LTM conflict resolution

Add a BIG-IP device after removing it from a silo

After you’ve analyzed LTM service conflicts for a BIG-IP device you’ve placed in a silo, and you’ve removed that device from the silo, you can add the device to BIG-IQ and discover all of its services so you can manage it.

This figure illustrates the work flow for using a silo to resolve conflicts triggered by importing a BIG-IP device. Re-importing the devices is the last step in this process.

1. At the top of the screen, click Devices.

2. On the left, click BIG-IP DEVICES.

3. Click the Add Device(s) button.

4. For the Discovery Type setting, select Add BIG-IP device(s) and discover and import services in one step.

5. Click the Add Device(s) button.

6. For IP Address, type the IPv4 or IPv6 address of the device.

7. Click the + button to add another IP address.

8. Type the user name and password for these devices.

9. In the Port box, type the management port for this BIG-IP device.

   The port number must be between 4 and 65535. In many cases, it’s the default port 443.

   Note: Chrome and Safari browsers don’t allow access to web applications running on port 65535. So if you use port 65535 as the management port, you won’t be able to access the BIG-IP device’s interface from BIG-IQ when using Chrome or Safari. You can still discover and manage BIG-IP devices that are using port 65535.

10. For the Target Silo setting, leave Do Not Use a Silo selected.

11. Select the check box next to each licensed service running on the device(s) you are adding.

12. If you are collecting statistics, for Status select the Enabled check box and a zone from the Zone list.

    If you do not define a zone, this device sends its statistics to DCDs assigned to the default zone. Zones are names created to associate BIG-IP devices with one or more DCD systems to help segregate statistic traffic by network topology, load, availability, and so forth, for optimal statistics traffic routing.

13. If this device is part of a DSC group, for the Cluster Display Name setting, specify how to handle it:

    • For an existing DSC group, select Use Existing from the list, and then select the name of the DSC group from the next list.
    • To create a new DSC group, select Create New from the list, and type a name in the field. For BIG-IQ to properly associate the devices in the same DSC group, the Cluster Display Name must be the same for all members in a group.

    There can be up to eight members in a DSC group.

    Important: For BIG-IP devices with ASM services, you can only add five devices at a time. If the BIG-IP device(s) provisioned with ASM is part of a DSC cluster, that device must also be a member of a sync-only device group, and ASM synchronization must be enabled for the device group. Without these DSC group settings, deploying changes to the ASM device can cause the cluster to get out of sync. For more information see https://support.f5.com/csp/article/K12200102, or the ASM Implementations chapter Automatically Synchronizing Application Security Configurations on support.f5.com.

14. If this device is part of a DSC group, for the Cluster Display Name setting, specify how to handle it:

    • For an existing DSC group, select Use Existing from the list, and then select the name of the DSC group from the next list.
    • To create a new DSC group, select Create New from the list, and type a name in the field. For BIG-IQ to properly associate the devices in the same DSC group, the Cluster Display Name must be the same for all members in a group.

    There can be up to eight members in a DSC group.

    Important: For BIG-IP devices with ASM services, you can only add five devices at a time. If the BIG-IP device(s) provisioned with ASM is part of a DSC cluster, that device must also be a member of a sync-only device group, and ASM synchronization must be enabled for the device group. Without these DSC group settings, deploying changes to the ASM device can cause the cluster to get out of sync. For more information see https://support.f5.com/csp/article/K12200102, or the ASM Implementations chapter Automatically Synchronizing Application Security Configurations on support.f5.com.

15. If this device is configured in a DSC group or you are creating a new DSC group, for the Cluster Properties, specify how to handle it:

    • Initiate BIG-IP DSC sync when deploying configuration changes (Recommended): Select this option if you want this device to automatically synchronize configuration changes with other members in the DSC.

    • Allow deployment when DSC configured devices have changes pending ( Not Recommended): Select this option if you want to deploy changes to this device even if there are changes pending for devices in the DSC group.

      Note: This option is not recommended, because it can lead to unpredictable results.

    • Ignore BIG-IP DSC sync when deploying configuration changes: Select this option if you want to manually synchronize configurations changes between members in the DSC group.

16. Click the Save & Close button at the bottom of the screen.

17. When you are ready to discover and import services for these devices, click the Discover and Import button at the bottom of the screen.

    The BIG-IQ system opens communication to the BIG-IP devices, and checks the BIG-IP device framework.

    Note: The BIG-IQ system can properly manage a BIG-IP device only if the BIG-IP device is running a compatible version of the REST framework.

18. If a framework upgrade is required, in the popup window, in the Root User Name and Root Password fields, type the root user name and password for the BIG-IP device, and click Continue.

You can now manage these BIG-IP devices.