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

Last Modified: Sep 29, 2022

Bug Tracker

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,

Fixed In:

Opened: Jun 22, 2021
Severity: 4-Minor


DHCP flows crossing route-domain boundaries might fail.


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


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


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


Behavior Change