juniper dhcp relay not working for all reth l3 subinterfaces
[ Edited ]
a month ago
** SEE UPDATE AT BOTTOM **
I'm working with JTAC on this, but they seem to be as confused as I am about why this isn't working. Hoping you all might have some additional insight.
I have an issue where DHCP relay isn't working correctly in a chassis cluster for some of the subinterfaces in a reth group. Basic topology is that the DHCP server lives on vlan 120 and the SRX is relaying dhcp for two vlans: 15 and 140. The cluster physical interface [ge-0/0/4 ge-5/0/4] are connected to a Cisco switch trunk port and all vlans are defined on the switch. Vlan 15 is able to complete the DHCP sequence, but 140 is not. The SRX also provides routing for all vlans. Running dhcp services traceoptions shows only dhcp discover and request traffic. PCAPs on the DHCP server only show DHCP inform from the 140 l3 interface, 192.168.140.1.
This is in a test environment so access is as permissive as I can make it. Here's the relevant config for the interfaces, dhcp relay, security zones, and policies.
UPDATE - Had another session with JTAC today. Wound up rolling the version back from 18.2 to 15.1X49-D190.2 and redid the config from scratch. Relay is working fine now. JTAC is doing some regression testing with 18.2 to determine whether or not it's a bug with the relay itself. I'll update this post when/if they provide additional information.