Last Modified: Jul 13, 2024
Affected Product(s):
BIG-IQ Device
Known Affected Versions:
5.4.0, 5.4.0 HF1, 5.4.0 HF2, 6.0.1, 6.0.1.1, 6.0.1.2, 6.1.0, 7.0.0, 7.0.0.1, 7.0.0.2, 7.1.0, 7.1.0.1, 7.1.0.2, 7.1.0.3, 7.1.6, 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2, 7.1.8, 7.1.8.1, 7.1.8.2, 7.1.8.3, 7.1.8.4, 7.1.8.5, 7.1.9, 7.1.9.7, 7.1.9.8, 7.1.9.9
Opened: May 24, 2018 Severity: 3-Major Related Article:
K23145710
BIG-IQ shows the same BIG-IP device twice in the BIG-IQ device inventory if the BIG-IP device's unique ID was changed. By design, BIG-IQ considers different IDs different devices.
This can cause issues when BIG-IQ tries to manage those devices.
BIG-IP generates a new unique ID during certain operations, for example when removing the f5-rest-device-id file and restarting restjavad. This might also happen if a UCS backup is restored onto a new BIG-IP device.
Identify the duplicate BIG-IP objects, and then remove them. To do this: Confirm there are duplicate device objects representing a single managed BIG-IP device. To do this, create some bash functions. 1. Create helper functions. From the BIG-IQ CLI, type the following commands to create BASH shell script functions: list-devices(){ restcurl shared/resolver/device-groups/cm-bigip-allDevices/devices'?$select=address,hostname,machineId,selfLink'; } list-dups() { list-devices| grep address | cut -d ':' -f2 | tr -d '",' | sort -n | uniq -c | grep -v -w 1; } These two commands create functions that can then be run as commands: -- list-devices <ENTER> gives an abbreviated list of all discovered devices on the BIG-IQ. -- list-dups <ENTER> lists any IP addresses reported for more that one object, and the number of instances in which the IP was found. 2) Run function list-dups to find any objects with more than one instance object using the same IP address. On the BIG-IQ CLI: list-dups <ENTER> -- In the output, the first number is the number of duplicates associated with the trailing IP address. If there is no output, no duplicates were found. -- In the following example, one IP address duplicate was found: # list-dups 2 10.111.0.97 3) List the object duplicates so that the invalid one can be identified. On the BIG-IQ CLI: list-devices | grep -A4 <dup address> Example: # list-devices | grep -A4 10.111.0.97 "address": “10.111.0.97", "hostname": "sdprod1.mydomain.com", "machineId": "22718bcc-71c3-4700-87c4-b28ed959b2df", "selfLink": "https://localhost/mgmt/shared/resolver/device-groups/cm-bigip-allDevices/devices/22718bcc-71c3-4700-87c4-b28ed959b2df" }, -- "address": "10.111.0.97", "hostname": "sdprod1.mydomain.com", "machineId": "4b777e75-ec75-464d-ac9f-548a7153103c", "selfLink": "https://localhost/mgmt/shared/resolver/device-groups/cm-bigip-allDevices/devices/4b777e75-ec75-464d-ac9f-548a7153103c" }, 4) Identify the valid object by going to the CLI of the actual BIG-IP device listed in the last output, and run the following command on its CLI: cat /config/f5-rest-device-id The output is the BIG-IP system's correct UUID. Note: Before proceeding to the next step, it is recommended that you create a UCS snapshot of the BIG-IQ. 5) Remove the invalid device object. Run the following command on the BIG-IQ CLI, substituting the UUID with the incorrect one (i.e., the one that does not match the correct UUID retrieved in the previous step): restcurl shared/resolver/device-groups/cm-bigip-allDevices/devices/<UUID> -X DELETE Example: restcurl shared/resolver/device-groups/cm-bigip-allDevices/devices/22718bcc-71c3-4700-87c4-b28ed959b2df -X DELETE Once all invalid objects are removed from the BIG-IQ, the procedure is finished.
None