Bug ID 684649: Inconsistent DAGv2 state between B4400 blades after upgrade

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP GTM, Install/Upgrade(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3

Fixed In:
13.1.1.4

Opened: Sep 20, 2017
Severity: 3-Major

Symptoms

B4400 blades in the VIPRION chassis might encounter inconsistent DAGv2 state after upgrading from v12.1.x to v13.0.0 or v13.1.0. You might see messages similar to the following continuously logged into /var/log/tmm on the Standby unit: notice CDP: Selected DAG state from primary PG 0 for CMP state 03 with clock 6765

Impact

There is no traffic impact on the Active BIG-IP system, but the issue causes the Standby BIG-IP system to constantly update its DAGv2 table.

Conditions

Upgrading VIPRION B4400 blades from v12.1.x to v13.0.0 or v13.1.0.

Workaround

Reboot one of the B4400 blades in the Active BIG-IP system.

Fix Information

DAGv2 state is now consistent between B4400 blades after upgrade.

Behavior Change