Manual Chapter :
Discovering and importing Access Policy Manager using BIG-IQ
Applies To:
Show Versions
BIG-IQ Centralized Management
- 8.2.0, 8.1.0, 8.0.0, 7.1.0
Discovering and importing Access Policy Manager using BIG-IQ
Discover the LTM and APM service configurations
Before you can import configurations from a device, you must first discover that device. To prepare to create an Access configuration on the BIG-IQ system, you must discover the Local Traffic Manager (LTM) service configuration, and then discover the Access Policy Manager (APM) service configuration as APM is dependent upon a discovered LTM service.
- At the top of the screen, clickDevices.
- Navigate to theBIG-IP DEVICEStab and select the name of the device you want to discover the service configuration from.
- On the left, clickServices.
- For Local Traffic Manager (LTM), clickDiscover.You must wait for discovery to complete before you continue. If you have previously discovered LTM for this device, the button will readRe-discover.
- For Access Policy Manager (APM), clickDiscover.If you have previously discovered APM for this device, the button will readRe-discover.
Once you have finished the discovery process, you may import the configuration.
Import APM services
Before importing or reimporting APM configurations to BIG-IQ, you must first discover or rediscover the managed BIG-IP devices. You will also need to discover LTM services.
Follow the procedure below to import or reimport an APM configuration in order to add APM configurations generated on BIG-IP to the source devices in Access Group in BIG-IQ.
- At the top of the screen, clickDevices.
- Navigate to theBIG-IP DEVICEStab and select the name of the device you want to discover the service configuration from.
- On the left, clickServices.
- For Access Policy Manager (APM), clickImport.If you have previously imported a configuration from this device, the button will readRe-import.
- Select one of two configuration types from the popup window to import. You may choose to import either a shared Access Group and device configuration or a device-specific configuration.
- If you select the shared option, you will import Access policies and other shared configurations from the selected device to create a shared Access Group configuration. Reimporting with a missing device-specific object creates default objects for the devices. After importing, review all device-specific objects and make required changes.
- If you select the device-specific option, you will import any device-specific configurations used by the Access Group.
- At this point, you can optionally create a snapshot of the current configuration before overwriting it during import.
Once you have finished importing the configuration from BIG-IP, you will need to resolve any conflicts that arise.
Resolve APM configuration conflicts
You will need to import or reimport APM configurations from BIG-IQ in order to resolve configuration conflicts between BIG-IQ and a managed BIG-IP device.
Sometimes there will be objects configured in your BIG-IQ environment that you will want to overwrite during a configuration import from a source BIG-IP. You may also want to perform the reverse function and discard edits made on the BIG-IP in favor of a configuration made on BIG-IQ. Using conflict resolution will ensure that you have a consistent configuration on all managed devices and in BIG-IQ.
- Once you have completed importing or reimporting an APM configuration, you may need to resolve conflicts that arise between a BIG-IP device and BIG-IQ.If there are any conflicts, a popup will appear where you can resolve the issues.
- Select either Shared or Device-specific to view entries for each type of resource.
- To reject any of the incoming configurations, click the entry you would like to reject and selectDenyin the bottom right corner.
- SelectApplyto accept all incoming configurations and overwrite the current configurations for this device on BIG-IQ.
Once you have resolved conflicts, the import process can finish.
