Bug ID 699339: Geolocation upgrade files fail to replicate to secondary blades

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,

Fixed In:

Opened: Dec 19, 2017
Severity: 3-Major
Related Article:


Geolocation upgrade files fail to replicate to secondary blades.


Geoip database is not updated to match primary blade.


-- Multiblade VIPRION platforms/vCMP guests. -- Upgrading geolocation files on the primary blade. -- Viewing the geolocation files on the secondary blades.


Use either of the following workarounds: -- Use the root account to manually create the /shared/GeoIP/v2 directory on secondary blades, and then run geoip_update_data on primary blade. -- On primary blade: 1. Edit /etc/csyncd.conf as shown below. 2. Restart csyncd. 3. Run geoip_update_data. To edit /etc/csyncd.conf: Merge the following two terms: monitor dir /shared/GeoIP {...) monitor dir /shared/GeoIP/v2 {...} into one term, as follows: monitor dir /shared/GeoIP { queue geoip pull pri2sec recurse yes defer no lnksync yes md5 no post "/usr/local/bin/geoip_reload_data" }

Fix Information

Geolocation upgrade files now correctly replicate to secondary blades.

Behavior Change