BugZero | F5 BugID 1318625 - The gtm_add sync configuration is in the unintende...

F5 - Defect ID: 1318625

The gtm_add sync configuration is in the unintended direction with large GTM configuration

F5 - Defect ID: 1318625

The gtm_add sync configuration is in the unintended direction with large GTM configuration

Last updated on July 28th, 2026

BugZero Risk Score
8.6 High

Overall: 8.6

Severity: 9.1

Community: 4.2

Lifecycle: 8.7

What is the BugZero Risk Score?

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Bug Details

Priority: 2-Critical
Status: Resolved
Impact Category: Global Traffic Manager (DNS)

Description

Symptoms

A wrong GTM configuration can be pushed to the sync group members after using the script gtm_add.

Impact

GTM devices are given the wrong or unintended configuration.

Conditions

-- Race condition with large GTM configuration while performing gtm_add. -- Following can be seen in GTM debug logs: 011a0200:7: MCP Message queued for resend. 1 backlogged messages. . . . 011a0200:7:MCP Message queued for resend. 1125 backlogged messages.

Workaround

Before running gtm_add make the following changes on the gtm where you intend to execute the gtm_add command: - disable synchronization - disable synchronize-zone-files - change the synchronization group name to match the remote gtm

Fix Information

None

Change history

Links

Original Vendor Announcement

Relevant Products

Click on a version to see all relevant bugs

Affected versions:14.1.5.4, 14.1.5.6, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: No known fixed versions

Top F5 Defects

9.6Defect ID: 546260
TMM can crash if using the v6rd profile
9.6Defect ID: 934133
Unable to Create/delete ltm virtual server via CLI transaction when destination is not specified on the ltm virtual object
9.6Defect ID: 1154417
Profile based attack is not mitigated at hardware on L2 wire setup
9.6Defect ID: 913713
Rebooting a blade causes MCPd to core as it rejoins the cluster
9.6Defect ID: 2141125
Multicast traffic is dropped with incorrect VLAN tagging

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Ready to prevent the next vendor outage?

Get a demo

F5 - Defect ID: 1318625

The gtm_add sync configuration is in the unintended direction with large GTM configuration

F5 - Defect ID: 1318625

The gtm_add sync configuration is in the unintended direction with large GTM configuration

Last updated on July 28th, 2026

BugZero Risk Score8.6 High

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Links

Top F5 Defects

Ready to prevent the next vendor outage?

F5 - Defect ID: 1318625

The gtm_add sync configuration is in the unintended direction with large GTM configuration

F5 - Defect ID: 1318625

The gtm_add sync configuration is in the unintended direction with large GTM configuration

Last updated on July 28th, 2026

BugZero Risk Score8.6 High

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Links

Top F5 Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
8.6 High

BugZero Risk Score
8.6 High