Bug ID 654764: iControl REST cannot stay in sync if /config/f5-rest-device-id is identical on each device

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Mar 31, 2017
Severity: 3-Major

Symptoms

When deploying an application such as an iAppLX application the LX-specific configuration is not synced, and you see a sync error in /var/log/restjavad.0.log.

Impact

Restjavad is unable to synchronize across the devices, as a result iAppLX applications fail to stay in sync.

Conditions

This may occur if you have a device group established, but the /config/f5-rest-device-id contains an identical device ID on each of the devices. This could be triggered in a number of ways: - Cloning BIG-IP VMs - Extracting the same UCS file to each of the devices, then establishing a trust group

Workaround

The first test you should do is to look at the contents of /config/f5-rest-device-id on all devices. If any of the devices contain the same ID, you can perform the following procedure to reset iControl REST trust: Impact of procedure: the following procedure resets the rest storage which removes all iAppLX applications from your configuration. You will need to re-create and re-deploy any iAppLX applications that you had deployed. At the command prompt, run the following: rm /config/f5-rest-device-id; clear-rest-storage This will cause the f5-rest-device-id file to be re-generated and will clear the rest storage, at this point the application should stay in sync across devices once you re-install and re-deploy it.

Fix Information

None

Behavior Change