How to Reset Device Trust – F5 LTM Load Balancing Methods Troubleshooting ConfigSync and Device Clustering
Chris Spillane provides a quick guide to troubleshooting device clustering or config sync for version 11.x.
Notice: This blog post was originally published on Indeni before its acquisition by BlueCat.
The content reflects the expertise and perspectives of the Indeni team at the time of writing. While some references may be outdated, the insights remain valuable. For the latest updates and solutions, explore the rest of our blog
F5 LTM Load Balancing Methods: How to Reset Device Trust.
The official F5 SOL13946 provides information on troubleshooting device clustering and configuration sync for 11v F5 load balancers and other products, however it is rather long winded. This guide is designed as a quick reference when troubleshooting device clustering or config sync. An overview of the config sync process for version 9.x and 10.x units can be found in F5 SOL7024
Version 11.x
- Communication between machines occurs in the following manner to form a device cluster:
mcpd process on the local machine connects to the tmm process on the local machine on port 6699 
- tmm process then contacts the peer’s config sync IP on port 4353
- Once the peer receives, they use tmm to contact mcpd over port 6699 on their local device.
- If this process fails, it is re-attempted every 5 seconds.
- If this process succeeds, there is a mesh between peer mcpd processes.
* local machine here refers to the self IP configured for config sync. Check it under Device Management > Devices > click on device > Device Connectivity > Config Sync, for example.
 
             
             
            