Bug ID 846601: Traffic classification does not update when an inactive slot becomes active after upgrade

Last Modified: Apr 29, 2021

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Fixed In:
14.1.4.2

Opened: Nov 06, 2019
Severity: 3-Major

Symptoms

VIPRION platforms have an automated process of joining a newly inserted blade to a cluster. TMOS install, licensing, and configuration including iAppLX are synchronized from primary to the newly inserted blade automatically without manual intervention. Traffic classification update is not occurring as expected under these conditions.

Impact

Traffic policies/rules related to updated installation do not work on inactive slot when it returns to the online state.

Conditions

-- Traffic classification configured. -- Update installation. -- VIPRION blade is inactive, and later comes online.

Workaround

To prevent this issue from occurring, ensure that all blades are online when installation begins. If you insert a blade, run config sync manually from the active blade.

Fix Information

Upgrade script now initiates install when the slot becomes active.

Behavior Change