Loading...
Loading...
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).
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.