F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

dhawal_138341's avatar
dhawal_138341
Icon for Nimbostratus rankNimbostratus
Jan 30, 2014

Synchronize_Configuration failing

I'm using F5 v10 and have Powershell script that uses iControl to make changes to active node and then sync it to standby node using synchronize_configuration. I'm using SyncMode::CONFIGSYNC_ALL. It was working fine till yesterday and suddenly started failing. The error message does not provide enough information. Any idea how to troubleshoot this error:

 

Error: System.Web.Services.Protocols.SoapHeaderException: Exception caught in System::urn:iControl:System/ConfigSync::synchronize_configuration() Exception: Common::OperationFailed primary_error_code : 16908289 (0x01020001) secondary_error_code : 0 error_string : Error synchronizing configuration: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at iControl.SystemConfigSync.synchronize_configuration(SystemConfigSyncSyncMode sync_flag) at CallSite.Target(Closure , CallSite , Object , Int32 )

 

deployment
devops
iControl

8 Replies

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Jan 30, 2014

    I would start by looking in /var/log/ltm and see if you find any messages indicating the problem. If you see nothing of value, it's probably best to open a support case for the issue.

     

    • Cory_50405's avatar
      Cory_50405
      Icon for Noctilucent rankNoctilucent
      Jan 30, 2014
      Feel free to post anything suspicious from your LTM log here for us to review.
  • dhawal_138341's avatar
    dhawal_138341
    Icon for Nimbostratus rankNimbostratus
    Feb 04, 2014

    Restarting the F5 nodes fixed the issue. But6 I have no idea what caused it in the first place.

     

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Feb 04, 2014

    If you looked in /var/log/ltm on the standby unit, you may have noticed a message to the effect of "Sync for device group /Common/name-of-device-group is already in progress to device /Common/name-of-device-in-trust-domain"

     

    This is bug ID 420188 fixed in v11.4.0 HF4

     

    • Cory_50405's avatar
      Cory_50405
      Icon for Noctilucent rankNoctilucent
      Feb 04, 2014
      In the past when we've encountered this issue, yes. Just perform a 'bigstart restart' on the standby unit and once it comes back up, the changes will sync from active to standby.