Bug ID 1016449: After certain configuration tasks are performed, TMM may run with stale Self IP parameters.

Last Modified: Jun 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
16.1.0, 15.1.0, 14.1.0

Fixed In:
17.0.0, 16.1.2.2, 15.1.5.1, 14.1.4.6

Opened: May 06, 2021
Severity: 3-Major

Symptoms

A Self IP instantiated by performing specific configuration tasks (see Conditions) does not work (e.g. the system does not respond to ARP requests for it). On the contrary, the system continues to use (e.g. respond to ARP requests for) an old version of the Self IP specifying a different address.

Impact

The system does not utilise the configured Self IP address. Traffic will be impacted as a result (for example, in connections to the unit, in snat automap, etc.).

Conditions

This issue is known to occur when one of the following operations is performed: - Restoring a UCS or SCF archive in which a Self IP with a specific name specifies a different address. - Performing a config-sync between redundant units in which the sender changes a Self IP with a specific name to use a different address. For example: tmsh delete net self <name> tmsh create net self <name> address <new_address> ... tmsh run cm config-sync to_group ... - Performing specific tmsh CLI transactions involving Self IP modifications.

Workaround

Restart TMM (bigstart restart tmm) on affected units.

Fix Information

TMM now correctly handles supported Self IP address modifications.

Behavior Change