Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP APM
Known Affected Versions:
11.4.1, 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.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, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.1.0
Opened: Mar 14, 2014
Severity: 2-Critical
APM does not support more than one traffic group with different high availability (HA) order. Here is an example configuration: cm traffic-group /Common/traffic-group-1 { ha-order { /Common/RM-F5-SKY.IT-01.sky.local } unit-id 1 } cm traffic-group /Common/traffic-group-2 { ha-order { /Common/RM-F5-SKY.IT-02.sky.local } unit-id 2 } This configuration causes the creation of an Active/Active HA pair and APM does not support this configuration. APM supports Active/Standby HA pair only.
APM does not support this configuration.
Configure two or more traffic groups with different HA order.
None.
The BIG-IP system no longer allows an invalid configuration where APM services exist in more than one traffic group simultaneously
