For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Navin_130677's avatar
Navin_130677
Icon for Nimbostratus rankNimbostratus
Feb 16, 2016

f5 sync error after VIP was deleted on A device and New VIP created with the IP being same from the deleted VIP

11.5.1 Hotfix HF7 7.0.167

Tried to Sync from a to b device reports the follwing error

StatusSync Failed SummaryA validation error occurred while syncing to a remote device Details Sync error on 1b: Load failed from 1a 01020056:3: Error computing object status for virtual_server (xserver.abc.com). Recommended action: Review the error message and determine corrective action on the device

AFM
config
security

2 Replies

  • AaronJB's avatar
    AaronJB
    Ret. Employee
    Feb 16, 2016

    Although the scenario is not quite as described in the SOL it does look like you are running into the bug described in AskF5 Solution SOL15767.

     

    That's fixed in 11.5.2 and onward; depending on your configuration the workarounds may also be appropriate.

     

    If not that then I would humbly suggest this is a question that might be better asked via F5 Support who can help you review your configuration for any other issues and look at diagnostic data from the device in order to troubleshoot the configuration sync process.

     

  • Navin_130677's avatar
    Navin_130677
    Icon for Nimbostratus rankNimbostratus
    Feb 16, 2016

    Thank Aaron, I had a support call and did the following.

     

    1- Deleted the VIP from the Standby Device. 2- Did Config Sync from Active to Standy, Config was sync but report a message as Not all device are synced message and with a message that sync Active device to Device_trust_group :

     

    Used the below commands

     

    • Below Commands were executed via a Putty session to fix the issue from the active device.

       

    • list cm device-group (This will show Trust Group Details.

       

    • show cm sync-status (This will report the Sync Status)

       

    • run cm config-sync to-group device_trust_group ( Based on the error reported as the reason we had to setup a sync from A to the device Trust Group)