Bug ID 786517: Modifying a monitor Alias Address from the TMUI might cause failed config loads and send monitors to an incorrect address

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP LTM(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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 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, 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

Fixed In:
16.0.0, 15.1.0.5, 14.1.3.1, 13.1.3.5

Opened: May 24, 2019

Severity: 3-Major

Symptoms

- Monitors are firing and are being sent to a pool-member or node address rather than a monitor's alias address. - Running the command 'tmsh load /sys config' reports an error: 01070038:3: Monitor /Common/a-tcp address type requires a port.

Impact

Monitors are sent to an incorrect IP address. tmsh load /sys config will fail to load the configuration.

Conditions

-- Create a monitor without an alias address. -- Modify the monitor later in the TMUI to specify an alias address.

Workaround

There are two workarounds: -- Delete and recreate the monitor and specify the correct alias address at creation time. -- Fix the monitor definition using tmsh.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips