Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

computerli's avatar
computerli
Icon for Altostratus rankAltostratus
Aug 07, 2018

ConfigSync on virtual F5

I need help configuring the Configsync   I initially had two virtual F5s running trial 90 day License. I purchased the Lab licenses and installed on the virtual F5s. The license is configured and...
application delivery
LTM
KevinA_246454's avatar
KevinA_246454
Icon for Cirrostratus rankCirrostratus
Aug 07, 2018

The 1st thing I will check is the config sync ip addresses used and see if if the devices can see each other via ping at least from each config sync ip addresses . Check the config sync self ip address If not mistaken in version 12. upwards the default self ip allow configuration is allowed none. you can change it to allow default which includes the config sync port number then test your config sync again. regarding your second question please read the links below very good material from f5 to guide you understanding the f5 HA concepts

 

  • computerli's avatar
    computerli
    Icon for Altostratus rankAltostratus
    Aug 07, 2018

    Self IPs are pingable , Port are also responding. I have change the Port lockdown to "Allow All"

     

  • Sukesh123456's avatar
    Sukesh123456
    Icon for Altostratus rankAltostratus
    Aug 07, 2018

    Hi DTN,

     

    can you run a config load tmsh load sys config from your text based config on both units and then try and run a sync.

     

    tmsh run cm config-sync to-group device-group-failover

     

    Please share the logs while you do it .