Bug ID 496679: Configuration loads may fail because the 'default-device' on a traffic-group object does not contain a valid value.

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1, 11.5.4 HF2

Opened: Dec 15, 2014
Severity: 3-Major
Related AskF5 Article:


After renaming a CM device object, or performing an upgrade from a version prior to 11.4.0, configuration loads may fail because the 'default-device' on a traffic-group object does not contain a valid value.


Although the configuration can be saved, it fails when being loaded (for example, in response to a ConfigSync operation, during software upgrade, or when running the command: 'tmsh load sys config').


This issue occurs when one of the following conditions is met: -- You load the BIG-IP configuration. -- You upgrade the BIG-IP system software. -- You perform a configuration synchronization (ConfigSync) operation for the device group. The 'default-device' attribute has been deprecated beginning in 11.4.0 in favor of new functionality. Prior to 11.4.0, default-device was used to specify the device-group member that failback tries to make active. From 11.4.0 and later, when auto-failback is enabled, the system uses the first member of the 'Failover Order' ('ha-order' in tmsh). In 11.4.0 and later, this field is not used, but will fail validation if it contains a value that does not reference the name of an existing device-group member, or the value 'none'.


Modify any traffic-group default-device attributes that refer to the now-deprecated, default-device name. Note: The system does not use this value, regardless of how you set it. To work around this issue, you can modify the traffic-group default-device attribute to refer to default-device none. To do so, perform the following procedure: 1. Log in to the Traffic Management Shell (tmsh) by typing the following command: tmsh 2. To list the configured default device for a traffic group, use the following command syntax: list /cm traffic-group <traffic group name> For example, to list the configured default device for traffic-group-1, type the following command: list /cm traffic-group traffic-group-1 3. Use none as the default device for your traffic group using the following command syntax: modify cm traffic-group <traffic group name> default-device <default device name>. For example, to modify your default device to none for traffic-group-1, type the following command: modify cm traffic-group traffic-group-1 default-device none 4. Save the configuration changes by typing the following command: save /sys config

Fix Information

Renaming a device also renames the associated traffic-group's default device, so configuration load now completes successfully.

Behavior Change