Bug ID 422698: LTM Virtual with DHCP address not Auto-Discovered

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP GTM(all modules)

Known Affected Versions:
10.2.4, 11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.1

Opened: Jun 05, 2013

Severity: 3-Major

Related Article: K15190

Symptoms

If GTM attempts to auto-discover LTM Virtual with DHCP address (i.e.: 255.255.255.255 or ff02::1:2), it will fail and Auto-Discovery will halt. Log messages such as the following may appear: BIG-IP46 err mcpd[5861]: 01020060:3: IP Address 255.255.255.255 is invalid, must not be all ones.

Impact

Auto-discovery fails to function.

Conditions

This occurs when GTM attempts to auto-discover LTM Virtual with DHCP address.

Workaround

Use a different IP address for your DHCP virtual.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips