Details required for adding BIG-IP devices with a CSV file
Before you use a CSV file to add BIG-IP devices to BIG-IQ, you’ll need the following information for each BIG-IP.
Tip: Refer to the About importing BIG-IP services with conflicts section to conflict policy guidelines.
| Device Details | Description and Action |
|---|---|
| Management IP address | Specify the management IP address(es) for the BIG-IP device(s) you are adding. |
| HTTPS Port | Type the management port for this BIG-IP device(s). This 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 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 port65535. |
| admin user name | admin |
| Password | Specify the admin user’s password for the device(s). |
| Cluster Name | Specify if these devices are part of a cluster. |
| DSC Sync Mode | If these devices are part of a DSC, initiate DSC sync when deploying configuration changes by specifying FALSE. |
| Pending Changes | If these devices are part of a DSC, allow deployment of any pending changes by specifying TRUE. |
| Services List | List of services running on these devices, separated by a space. For example: LTM APM ASM AFM SSM DNS FPS |
| Enable Statistics Collection | If these device are collecting statistics, allow data collection by specifying TRUE. |
| Zone | If you are adding data collection devices that need to be in a specific zone, specify the name of the zone to which you want assigned. |
| APM Group | If these devices support the APM service, specify the APM group. |
| APM Shared Import | If these devices are part of an APM group, set this to TRUE only for the first device in the APM group, leave the rest at FALSE. |
| Shared Object Conflict Policy | Specify how you want any shared object conflicts between BIG-IQ and the BIG-IP devices using one of the following values: USE_BIGIQ, USE_BIGIP. |
| Version Object Conflict Policy | Conflict Resolution Policy for Version Specific Objects for LTM monitors and profiles only, specify one of the following values: USE_BIGIQ, USE_BIGIP, KEEP_VERSION. The default is USE_BIGIQ. |
| Device Specific Conflict Policy | Conflict Resolution Policy for Device Specific Objects. Specify one of the following values: USE_BIGIQ, USE_BIGIP. The default is USE_BIGIP. |
| Silo Properties | For LTM services only, specify an existing or new silo to put the BIG-IP device(s) into if a conflict is found. The default is Do Not Use a Silo. |