Bug ID 1027805: DHCP flows crossing route-domain boundaries might fail.

Last Modified: Aug 03, 2021

Bug Tracker

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

Known Affected Versions:
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, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.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, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0

Opened: Jun 22, 2021
Severity: 4-Minor

Symptoms

DHCP flows crossing route-domain boundaries might fail.

Impact

The second and subsequent DHCP clients requests will not be forwarded to the DHCP pool members.

Conditions

Example of a configuration leading to the problem: - route-domain RD%2 with parent defined as route-domain RD%1. - Virtual-server in route-domain RD%2. - Pool member configured in RD%2 (sharing IP addressing with RD1) - DHCP client connects to the virtual-server in route-domain RD%2. - Route lookup for a pool member ends up with connection in route-domain RD%1

Workaround

When configuring a DHCP pool member, use the ID of the parent route-domain (the one that will be returned by a route-lookup for the pool member's IP address).

Fix Information

None

Behavior Change