Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP All, Install/Upgrade
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3
Fixed In:
13.1.0, 13.0.1, 12.1.2 HF1, 11.6.1 HF2
Opened: Sep 03, 2015 Severity: 3-Major Related Article:
K40670213
Failover event on traffic-group-1 causes mcpd to generate messages like this: 01070711:3: Caught runtime exception, Failed to collect files (Invalid IP Address: ).. 01070712:3: Caught configuration exception (0), Failed to sync files.. ... 0107134b:3: (Child rsync being terminated due to timeout. Total size in Kb: 0 timeout in secs: 10 start-time: Mon Aug 24 11:35:42 2015 max-end-time: Mon Aug 24 11:35:42 2015 time now: Mon Aug 24 11:35:42 2015 ) errno(0) errstr(). 01070712:3: Caught configuration exception (0), Failed to sync files..
mcpd on the devices running the affected versions may become unresponsive. Upgrade fails. This is fundamentally the result of device group members running different software versions.
This occurs when the following sets of conditions are met: Condition set 1 =============== -- Your BIG-IP high availability (HA) device group members are running BIG-IP 11.6.0 or 11.6.1. -- You upgrade a peer HA device to BIG-IP 12.x or later. -- After you upgrade that peer, a failover event occurs. Condition set 2 =============== -- Your BIG-IP HA device group members are running BIG-IP 12.0.0, 12.1.0, 12.1.1, or 12.1.2. -- You upgrade a peer HA device to BIG-IP 13.x or later. -- After you upgrade that peer, a failover event occurs. Note: This might be most evident with APM configurations.
None.
This release corrects an issue in which a group of devices in a trust domain could potentially cause mcpd to become unresponsive and log failure messages.