BIG-IQ Central Management API automation and programmability - BULK Discovery, Import and Re Import - Perl

Summary In conjunction with the announcement of BIG-IQ 5.0 we are excited to bring the field greater flexibility when centrally managing BIG-IP devices utilizing well defined workflows and the BIG...
Updated Jun 06, 2023
Version 2.0
api
BIG-IQ
bulk discovery
devops
iControlREST
perl
Andrew_Tuttle's avatar
Andrew_Tuttle
Icon for Nimbostratus rankNimbostratus
Jan 13, 2017

Hi Carl,

 

Bingo on the need for automation. We are looking for automated re-import capability on BIG-IQ version 5.x, so I was happy to see these scripts. Overall the bulk discovery script seems to work well, but the bulk re-import (the one I really need) has a couple of issues I'm trying to work through.

 

  1. Wrong BIG-IP instance is re-imported -- When my BIG-IQ contains several BIG-IP instances, and I want to re-import one of those instances only, I edit the CSV file to contain info for that instance. But when I execute the script, the first BIG-IP instance in the list is re-imported, not the BIG-IP instance I entered into the CSV file.
  2. I want to take advantage of the re-import as a periodic sync mechanism between BIG-IP instances and BIG-IQ. But when I change a rule on the target BIG-IP that is first in the list (I have to use the first because of the problem in 1) and execute the re-import, it doesn't identify the difference between BIG-IP and BIG-IQ. The log says 0 conflicts. However if I use the bulk discovery script to discover this BIG-IP from scratch, I do see the conflict that I generated for this test purpose identified in the bulk discover script's log.

Any assistance would be much appreciated. Thanks!

 

-- Andrew