Manual Chapter : Troubleshooting tips

Applies To:

  • BIG-IP LTM

    21.0.0, 17.5.1, 17.5.0, 17.1.3, 17.1.2, 17.1.1, 17.1.0, 17.0.0, 16.1.6, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0

Updated Date: 07/07/2026

Troubleshooting tips

Several actions are available for users to take to troubleshoot SFC controller deployment issues.

Issue

Actions

The configuration deployment fails.
  1. View the error message displayed in the user interface.
  2. Review the log files /var/log/restnoded/restnoded.log and /var/log/restjavad.0.log
  3. If the above steps fail, try these recovery steps:
    • If the problem is a timeout issue, retry the same operation.
    • If the problem is due to the existence of the object you are creating, delete the MCP object from TMSH and retry.
    • If the problem is an iAppLX block state issue, the timeout might have occurred before the block reached its default (BOUND) state.
    • If the configuration is not already created, retry the operation.

The iAppLX instance does not appear after uploading the RPM.
  1. Wait 2 to 3 minutes.
  2. If the instance is still not visible, delete the RPM and upload it again. The SFC controller iAppLX instance is created automatically during RPM upload.

Note: Do not try to create the iAppLX instance by doing an iAppLX Create action from the template option. This operation does not work reliably.

The iAppLX instance is in an error state (indicated by a red square next to the instance on the user interface screen).

Re-deploy the SFC controller by clicking the Undeploy and Deploy buttons. If this succeeds, you have recovered from the failure situation. If the iAppLX instance is not back to a green state: 1. Run the command bigstart restart restjavad restnoded at a BIG-IP system prompt. 2. Try re-deploying the iAppLX instance if it is not already back to a green state. If this succeeds, you have recovered from the failure situation. If a re-deploy or undeploy action fails, take these actions: - Select the deployed iAppLX instance from the list and delete the application.

Note: Deleting the iAppLX instance deletes its REST data.

-   Delete the RPM and re-upload the RPM.
-   If these recovery steps do not work, you might need to clean up the REST storage by running the command `clear-rest-storge` using the BIG-IP command-line interface. This clears the REST data of any other iAppLX instance that might exist on the device.

Note: The previous steps do not delete the mcpd configuration that the SFC controller created.

After doing the previous steps, use this REST API to clear the old configuration: https://*mgmt\_ip*/mgmt/shared/sfc/manager/settings/cleanup.

The controller displays an OUT_OF_SYNC message.
  1. Compare the oldConfig data and the newConfig data to find the differences. oldConfig represents the data held by the SFC controller, and newConfig represents the mcpd configuration.
  2. Use the appropriate TMSH commands or the graphical user interface to modify/re-create the mcpd configuration that matches the controller data.
  3. Wait x seconds, where x = the audit interval set by the user. The controller should then recover and no longer display the OUT_OF_SYNC error message.