Thanks Matt, There's also mention in the link below, of BLQ being the
way a dhcpv6 relay agent recovers lost dhcpv6 states and ia_pd routes,
during a reboot of the relay agent
That is my hope. To make BLQ work so that the binding table and
subsequent ia_pd routes are likewise quickly recovered during the time a
juniper router acting as a dhcpv6 relay agent is restarted during
accident, power-outage, intentional software upgrade or mw.
I'm seeing it work, I'm seeing the juniper acx5048 relay agent fire-off
the tcp/547 ipv6 session to the remote KEA DHCPv6 server and pull
leases, and the sys engineer I work with is confirming in KEA logs he is
seeing this activity. ...BUT, we don't see it work if we clear the
dhcpv6 relay binding table on the Juniper router, nor do we see it occur
if the ACX5048 is rebooted. I'm recreating this using vMX in EVE-NG at
the moment, in hopes to see otherwise. Maybe it's a ACX5048
limitation... i don't know. I might try an ACX7100. I need to make it
work on platforms that we use for our residential bb customer base.
https://www.juniper.net/documentation/us/en/software/junos/subscriber-mgmt-sessions/topics/topic-map/dhcp-individual-bulk-leasequery.html
-Aaron
On 2/28/2026 5:44 AM, Matt Peterson wrote:
My understanding is the BLQ implementation is more geared between
Juniper's own DHCP local server, such as when running as a BNG.
--Matt
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
