Bug ID 427002: Specific configuration results in error loading same port twice

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1

Fixed In:
11.5.0

Opened: Aug 02, 2013
Severity: 3-Major
Related AskF5 Article:
K14854

Symptoms

A specific configuration of allow-services to self IP addresses leads to an attempt to add a listener for same port twice, resulting in an error. For example, adding 172.16.251.252 (which has a configuration that specifies 'tcp:https' and also 'default') when 'default' tries to add a listener for 443, it fails in response to an E-INUSE error, which occurs because the value 'tcp:https' already exists in the 'default' list.

Impact

When this occurs, the tmm rejects the part of the configuration containing the duplication.

Conditions

This occurs when the configuration contains a definition for a listener on a port that has already been added by 'default.' You can see this list in the /defaults/bigip_base.conf file.

Workaround

To work around this, remove lines in self-IP configurations that try to add a port that is already being added by 'default.' In this case, edit the configuration to remove 'tcp:https.'

Fix Information

If a self-ip has the 'default' list included in the allow-services, then the system will validate all the other entries against the 'default' list. The tmm is now protected from an incorrect configuration with duplicated entries.

Behavior Change