Last Modified: Jul 13, 2024
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
13.0.0, 12.1.3
Opened: Jan 03, 2017 Severity: 1-Blocking
Assigning a profile with DNS rapid response enabled to a virtual server on a P8 chassis might result in problems with blades and the cluster. Depending on the timing of operations (config is loaded and tmm restarts), blades might never join the cluster properly and you will see errors similar to the following looping in /var/log/tmm: notice CDP: exceeded 1/2 timeout for PG 0 notice CDP: PG 0 timed out notice CDP: New pending state ff -> fe notice CDP: New pending state fe -> ff notice CDP: Selected DAG state from PG 0 for CMP state ff with clock 2445394 notice CDP: exceeded 1/2 timeout for PG 0 notice CDP: PG 0 timed out notice CDP: New pending state ff -> fe notice CDP: New pending state fe -> ff notice CDP: Selected DAG state from PG 0 for CMP state ff with clock 2445416
DNS Rapid Response filters large datagrams. Blades might never join the cluster.
-- Assigning a profile with DNS rapid response enabled to a virtual server. -- P8 chassis. -- Large datagrams being passed.
There is no workaround at this time.
The system now passes through any datagrams too big for DNS rapid response.