Explanation
The gtmd process updates the “commit-id” value and Writes the new configuration to /config/bigip_gtm.conf file.
The Local big3d process will start to communicate the new “commit-id” value to all remote gtmd processes
Correct selection
The remote gtmd process will use “iqsyncer “ utility to pull the new configuration related to the new “commit-id”
The “mmsh” will communicate the Configuration changes to the “ncpd” process
The mcpd process will forward the Configuration changes to the gtmd process
The ltmd process updates the “commit-id” value and Writes the new configuration to /config/bigip_ltm.conf file.
The Local big3d process will start to communicate the new “commit-id” value to all remote gtmd processes
In the communication flow when changing the configuration of the Synchronization Group, the "tmsh" process is responsible for communicating the configuration changes to the "mcpd" process. The "mcpd" process then forwards these changes to the "gtmd" process to ensure synchronization across devices.
During the configuration change process, the "gtmd" process is responsible for updating the "commit-id" value and writing the new configuration to the /config/bigip_gtm.conf file. Subsequently, the local "big3d" process initiates communication of the new "commit-id" value to all remote gtmd processes to maintain consistency.
Following the update of the "commit-id" value and writing the new configuration to the /config/bigip_gtm.conf file, the remote gtmd process utilizes the "iqsyncer" utility to pull the new configuration related to the updated "commit-id" value. This ensures that all devices in the Synchronization Group have the latest configuration.
Domain
iQuery Synchronization issue
Submit