SRX Services Gateway
SRX Services Gateway

DHCP Relay issues on SRX320

‎02-27-2019 07:33 AM

We are experiencing an issue with DHCP relay on a few of our SRX branch devices.  For this post, I will use our test environment, an SRX320, as the example.  It is running 15.1X49-D70.3.

 

We have six /26 subnets on the device each in it's own VLAN.  Each VLAN has a L3-interface on the SRX with an IP address assigned as the gateway for that subnet. 

# show vlans
vlan2800 {
    vlan-id 2800;
    l3-interface irb.2800;
}
vlan2600 {
    vlan-id 2600;
    l3-interface irb.2600;
}
vlan2400 {
    vlan-id 2400;
    l3-interface irb.2400;
}
vlan900 {
    vlan-id 900;
    l3-interface irb.900;
}
vlan2900 {
    vlan-id 2900;
    l3-interface irb.2900;
}
vlan2100 {
    vlan-id 2100;
    l3-interface irb.2100;
}
# show interfaces irb
unit 900 {
    family inet {
        address 172.17.100.1/26;
    }
}
unit 2100 {
    family inet {
        address 172.17.0.129/26;
    }
}
unit 2400 {
    family inet {
        address 172.17.0.65/26 {
            primary;
        }
        address 10.100.0.65/26;
    }
}
unit 2600 {
    family inet {
        address 172.17.100.65/26;
    }
}
unit 2800 {
    family inet {
        address 172.17.0.1/26;
    }
}
unit 2900 {
    family inet {
        address 172.17.0.193/26;
    }
}

 

The DHCP server, a virtual machine running Windows 2012 R2 in an Active Directory environment, is in VLAN 2800 with an IP address of 172.17.0.5.  The SRX is set to forward DHCP requests to 172.17.0.5 with the following code:


# show forwarding-options
dhcp-relay {
    server-group {
        SERVER {
            172.17.0.5;
        }
    }
    group Test {
        active-server-group SERVER;
        interface vlan.900;
        interface vlan.2100;
        interface vlan.2400;
        interface vlan.2600;
        interface vlan.2800;
        interface vlan.2900;
    }
}

The firewall rules are fairly open with any traffic from devices on VLAN 2100 permitted to devices on VLAN 2800 over any application.  The rest of the VLANs are the same.

 

# show security policies from-zone VLAN2100 to-zone VLAN2800
policy 2100-to-2800 {
    description "Permit wired clients to talk to infrastructure devices";
    match {
        source-address vlan2100;
        destination-address vlan2800;
        application any;
    }
    then {
        permit;
    }
}

Hopefully that gives a good idea of our environment.  Here is where the problem comes in.  The above configuration worked just fine for every subnet on the device.  Out of the blue, DHCP requests stopped forwarding on some of the subnets.  We first noticed it on VLAN 900, which is a public wireless network.  The only difference between that network and the others was that network was not on the same /24 network as the other ones, but that doesn't make any sense why that would prevent it from working.  Our workaround was to add a new network adapter to the server virtual machine on VLAN 900 with an IP address in that network without a gateway.  This "fixed" the issue because now the server was on the same network as the devices and could service requests.  Then, other networks stopped working.  We have seen this issue on 15 out of 70 branch devices.  We have plans to forward our DHCP to a central server out of our control so adding a new network adapter isn't possible.  We need to fix this issue properly.  We haven't gathered any logs yet but can do that.  I think we're also going to call support to see if they can fix it but wanted to also reach out to the community to see if anyone can point us in the right direction.

 

Thanks, in advance, for any help!

1 ACCEPTED SOLUTION

Accepted Solutions
SRX Services Gateway
Solution
Accepted by topic author tcw135
‎02-28-2019 05:11 AM

Re: DHCP Relay issues on SRX320

‎02-27-2019 02:21 PM

I suspect you are just mixing configs from different platforms, but to be sure, on the 300 series you need to reference irb interfaces and not vlan.

 

# show forwarding-options
dhcp-relay {
    server-group {
        SERVER {
            172.17.0.5;
        }
    }
    group Test {
        active-server-group SERVER;
        interface vlan.900;
        interface vlan.2100;
        interface vlan.2400;
        interface vlan.2600;
        interface vlan.2800;
        interface vlan.2900;
    }
}

 

10 REPLIES 10
SRX Services Gateway

Re: DHCP Relay issues on SRX320

‎02-27-2019 08:30 AM

I cannot find a specific PR matching this behavior but in general my experience with SRX300 series and Junos below 15.1X49-D110 has been very mixed. I would suggest upgrading to JTAC recommended release 15.1X49-D150 and then debug from that point if the problem still shows.

 

15.1X49-D70 is the firmware which the device was shipped with and was released more than two years ago (December 16th 2016).


--
Best regards,

Jonas Hauge Jensen
Systems Engineer, SEC DATACOM A/S (Denmark)
SRX Services Gateway

Re: DHCP Relay issues on SRX320

[ Edited ]
‎02-27-2019 09:17 AM

Thanks, for the reply!

 

We are seeing this issue on an SRX220H2 running 12.3X48-D4​0.5 which isn't too far behind the recommended version of 12.3X48-D75.

 

I am going to update the firmware on the SRX320 to see if that resolves the issue.

 

EDIT:  Updated firmware to 15.1X49-D150.2-domestic and there is no change in behavior.  

SRX Services Gateway

Re: DHCP Relay issues on SRX320

[ Edited ]
‎02-27-2019 01:15 PM

OK. If you look at the output of 'show dhcp relay statistics' - are there dropped packets or mismatch between sent and received packets?

 

I would suggest enabling traceoptions on the dhcp-service to become wiser what goes on internally in the jdhcpd process.

 

Traceoptions are enabled via the following settings with debug file in /var/log/jdhcpd-debug

set system processes dhcp-service traceoptions file jdhcpd-debug
set system processes dhcp-service traceoptions file size 5m
set system processes dhcp-service traceoptions file files 5
set system processes dhcp-service traceoptions flag all

Please share relevant parts og the output if you need help understand the output.

 

P.S. Please be aware that editing posts will not send out notifications to other contributors in the thread. It was a coincidence that I revisited the thread and saw your edit note regarding the result of the upgrade :-)


--
Best regards,

Jonas Hauge Jensen
Systems Engineer, SEC DATACOM A/S (Denmark)
SRX Services Gateway

Re: DHCP Relay issues on SRX320

‎02-27-2019 01:42 PM

Thanks for the tip about editing posts, I didn't know that.

 

Here is the result of show dhcp relay statistics

> show dhcp relay statistics
Packets dropped:
    Total                      131
    Interface not configured   131

Messages received:
    BOOTREQUEST                0
    DHCPDECLINE                0
    DHCPDISCOVER               0
    DHCPINFORM                 0
    DHCPRELEASE                0
    DHCPREQUEST                0
    DHCPLEASEACTIVE            0
    DHCPLEASEUNASSIGNED        0
    DHCPLEASEUNKNOWN           0
    DHCPLEASEQUERYDONE         0

Messages sent:
    BOOTREPLY                  0
    DHCPOFFER                  0
    DHCPACK                    0
    DHCPNAK                    0
    DHCPFORCERENEW             0
    DHCPLEASEQUERY             0
    DHCPBULKLEASEQUERY         0

This is with and without the extra network adapter on the server.

 

I just enabled traceoptions and will report back with some results.  I was researching that earlier but got sidetracked.  Thank you for providing the code!

 

I also opened a JTAC case with this issue to see if they have any insight.  If they find a solution I will post it in this thread.

SRX Services Gateway

Re: DHCP Relay issues on SRX320

‎02-27-2019 01:51 PM

Here is the log after I did a ipconfig /renew on my test machine on VLAN 2100.

Feb 27 16:48:22.981489 [MSTR][INFO]  jdhcpd_io_recv_pkt: recvmsg() l3_ifindex: 74
Feb 27 16:48:22.981575 [MSTR][NOTE]  jdhcpd_io_recv_pkt: recvmsg() l2_ifindex: 85
Feb 27 16:48:22.982497 [MSTR][INFO] [irb.2100] jdhcpd_io_get_ifs: The L3 interface is 74 and L2 interface is 85, using the L3 interface
Feb 27 16:48:22.982538 [MSTR][NOTE]  jdhcpd_io_reader: Recv DHCP packet on logical-system default, routing-instance default, if irb.2100 size 300
Feb 27 16:48:22.982594 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   from == 0.0.0.0, port == 68 ]--
Feb 27 16:48:22.982681 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   size == 300, op == 1 ]--
Feb 27 16:48:22.982718 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  flags == 8000 ]--
Feb 27 16:48:22.982752 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  htype == 1, hlen == 6 ]--
Feb 27 16:48:22.982785 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   hops == 0, xid == 58d37e3a ]--
Feb 27 16:48:22.982819 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   secs == 0, flags == 8000 ]--
Feb 27 16:48:22.982863 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP ciaddr == 0.0.0.0 ]--
Feb 27 16:48:22.982898 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP yiaddr == 0.0.0.0 ]--
Feb 27 16:48:22.982933 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP siaddr == 0.0.0.0 ]--
Feb 27 16:48:22.982968 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP giaddr == 0.0.0.0 ]--
Feb 27 16:48:22.983022 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP chaddr == 84 7b eb 27 e9 f0 00 00 00 00 00 00 00 00 00 00 ]--
Feb 27 16:48:22.983055 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  sname ==  ]--
Feb 27 16:48:22.983088 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   file ==  ]--
Feb 27 16:48:22.983125 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  53, len   1, data DHCP-DISCOVER ]--
Feb 27 16:48:22.983170 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  61, len   7, data 01 84 7b eb 27 e9 f0 ]--
Feb 27 16:48:22.983246 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  50, len   4, data ac 11 00 82 ]--
Feb 27 16:48:22.983299 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  12, len  13, data 41 47 49 54 2d 4c 2d 54 43 57 31 33 35 ]--
Feb 27 16:48:22.983342 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  60, len   8, data 4d 53 46 54 20 35 2e 30 ]--
Feb 27 16:48:22.983393 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  55, len  14, data 01 03 06 0f 1f 21 2b 2c 2e 2f 77 79 f9 fc ]--
Feb 27 16:48:22.983427 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code 255, len   0 ]--
Feb 27 16:48:22.983625 [MSTR][NOTE] [default:default][RLY][INET][irb.2100] jdhcpd_packet_handle: BOOTPREQUEST irb.2100 arrived on unconfigured interface DISCOVER, flags 3, config 0x0
Feb 27 16:48:26.102776 [MSTR][INFO]  jdhcpd_io_recv_pkt: recvmsg() l3_ifindex: 74
Feb 27 16:48:26.116745 [MSTR][NOTE]  jdhcpd_io_recv_pkt: recvmsg() l2_ifindex: 85
Feb 27 16:48:26.116808 [MSTR][INFO] [irb.2100] jdhcpd_io_get_ifs: The L3 interface is 74 and L2 interface is 85, using the L3 interface
Feb 27 16:48:26.116843 [MSTR][NOTE]  jdhcpd_io_reader: Recv DHCP packet on logical-system default, routing-instance default, if irb.2100 size 300
Feb 27 16:48:26.116897 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   from == 0.0.0.0, port == 68 ]--
Feb 27 16:48:26.116935 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   size == 300, op == 1 ]--
Feb 27 16:48:26.116968 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  flags == 8000 ]--
Feb 27 16:48:26.117001 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  htype == 1, hlen == 6 ]--
Feb 27 16:48:26.117035 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   hops == 0, xid == 58d37e3a ]--
Feb 27 16:48:26.117068 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   secs == 0, flags == 8000 ]--
Feb 27 16:48:26.117165 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP ciaddr == 0.0.0.0 ]--
Feb 27 16:48:26.117206 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP yiaddr == 0.0.0.0 ]--
Feb 27 16:48:26.117241 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP siaddr == 0.0.0.0 ]--
Feb 27 16:48:26.117275 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP giaddr == 0.0.0.0 ]--
Feb 27 16:48:26.117327 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP chaddr == 84 7b eb 27 e9 f0 00 00 00 00 00 00 00 00 00 00 ]--
Feb 27 16:48:26.117360 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  sname ==  ]--
Feb 27 16:48:26.117392 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   file ==  ]--
Feb 27 16:48:26.117429 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  53, len   1, data DHCP-DISCOVER ]--
Feb 27 16:48:26.117474 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  61, len   7, data 01 84 7b eb 27 e9 f0 ]--
Feb 27 16:48:26.117514 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  50, len   4, data ac 11 00 82 ]--
Feb 27 16:48:26.117562 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  12, len  13, data 41 47 49 54 2d 4c 2d 54 43 57 31 33 35 ]--
Feb 27 16:48:26.117604 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  60, len   8, data 4d 53 46 54 20 35 2e 30 ]--
Feb 27 16:48:26.117844 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  55, len  14, data 01 03 06 0f 1f 21 2b 2c 2e 2f 77 79 f9 fc ]--
Feb 27 16:48:26.117899 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code 255, len   0 ]--
Feb 27 16:48:26.117940 [MSTR][NOTE] [default:default][RLY][INET][irb.2100] jdhcpd_packet_handle: BOOTPREQUEST irb.2100 arrived on unconfigured interface DISCOVER, flags 3, config 0x0
Feb 27 16:48:29.224994 [MSTR][INFO]  jdhcpd_io_recv_pkt: recvmsg() l3_ifindex: 74
Feb 27 16:48:29.225105 [MSTR][NOTE]  jdhcpd_io_recv_pkt: recvmsg() l2_ifindex: 85
Feb 27 16:48:29.225861 [MSTR][INFO] [irb.2100] jdhcpd_io_get_ifs: The L3 interface is 74 and L2 interface is 85, using the L3 interface
Feb 27 16:48:29.225898 [MSTR][NOTE]  jdhcpd_io_reader: Recv DHCP packet on logical-system default, routing-instance default, if irb.2100 size 300
Feb 27 16:48:29.225952 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   from == 0.0.0.0, port == 68 ]--
Feb 27 16:48:29.226096 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   size == 300, op == 1 ]--
Feb 27 16:48:29.226133 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  flags == 8000 ]--
Feb 27 16:48:29.226167 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  htype == 1, hlen == 6 ]--
Feb 27 16:48:29.226200 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   hops == 0, xid == 58d37e3a ]--
Feb 27 16:48:29.226233 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   secs == 768, flags == 8000 ]--
Feb 27 16:48:29.226268 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP ciaddr == 0.0.0.0 ]--
Feb 27 16:48:29.226302 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP yiaddr == 0.0.0.0 ]--
Feb 27 16:48:29.226336 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP siaddr == 0.0.0.0 ]--
Feb 27 16:48:29.226370 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP giaddr == 0.0.0.0 ]--
Feb 27 16:48:29.226422 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP chaddr == 84 7b eb 27 e9 f0 00 00 00 00 00 00 00 00 00 00 ]--
Feb 27 16:48:29.226455 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  sname ==  ]--
Feb 27 16:48:29.226489 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   file ==  ]--
Feb 27 16:48:29.226526 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  53, len   1, data DHCP-DISCOVER ]--
Feb 27 16:48:29.226598 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  61, len   7, data 01 84 7b eb 27 e9 f0 ]--
Feb 27 16:48:29.226640 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  50, len   4, data ac 11 00 82 ]--
Feb 27 16:48:29.226688 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  12, len  13, data 41 47 49 54 2d 4c 2d 54 43 57 31 33 35 ]--
Feb 27 16:48:29.226731 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  60, len   8, data 4d 53 46 54 20 35 2e 30 ]--
Feb 27 16:48:29.226781 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  55, len  14, data 01 03 06 0f 1f 21 2b 2c 2e 2f 77 79 f9 fc ]--
Feb 27 16:48:29.226815 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code 255, len   0 ]--
Feb 27 16:48:29.226855 [MSTR][NOTE] [default:default][RLY][INET][irb.2100] jdhcpd_packet_handle: BOOTPREQUEST irb.2100 arrived on unconfigured interface DISCOVER, flags 3, config 0x0
Feb 27 16:48:36.474467 [MSTR][INFO]  jdhcpd_io_recv_pkt: recvmsg() l3_ifindex: 74
Feb 27 16:48:36.474547 [MSTR][NOTE]  jdhcpd_io_recv_pkt: recvmsg() l2_ifindex: 85
Feb 27 16:48:36.474587 [MSTR][INFO] [irb.2100] jdhcpd_io_get_ifs: The L3 interface is 74 and L2 interface is 85, using the L3 interface
Feb 27 16:48:36.474622 [MSTR][NOTE]  jdhcpd_io_reader: Recv DHCP packet on logical-system default, routing-instance default, if irb.2100 size 300
Feb 27 16:48:36.474674 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   from == 0.0.0.0, port == 68 ]--
Feb 27 16:48:36.474711 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   size == 300, op == 1 ]--
Feb 27 16:48:36.474744 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  flags == 8000 ]--
Feb 27 16:48:36.474777 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  htype == 1, hlen == 6 ]--
Feb 27 16:48:36.474812 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   hops == 0, xid == 58d37e3a ]--
Feb 27 16:48:36.474846 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   secs == 2560, flags == 8000 ]--
Feb 27 16:48:36.474918 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP ciaddr == 0.0.0.0 ]--
Feb 27 16:48:36.474955 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP yiaddr == 0.0.0.0 ]--
Feb 27 16:48:36.474990 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP siaddr == 0.0.0.0 ]--
Feb 27 16:48:36.475024 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP giaddr == 0.0.0.0 ]--
Feb 27 16:48:36.475077 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP chaddr == 84 7b eb 27 e9 f0 00 00 00 00 00 00 00 00 00 00 ]--
Feb 27 16:48:36.475111 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  sname ==  ]--
Feb 27 16:48:36.475143 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   file ==  ]--
Feb 27 16:48:36.475180 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  53, len   1, data DHCP-DISCOVER ]--
Feb 27 16:48:36.475226 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  61, len   7, data 01 84 7b eb 27 e9 f0 ]--
Feb 27 16:48:36.475265 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  50, len   4, data ac 11 00 82 ]--
Feb 27 16:48:36.475424 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  12, len  13, data 41 47 49 54 2d 4c 2d 54 43 57 31 33 35 ]--
Feb 27 16:48:36.475486 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  60, len   8, data 4d 53 46 54 20 35 2e 30 ]--
Feb 27 16:48:36.475537 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  55, len  14, data 01 03 06 0f 1f 21 2b 2c 2e 2f 77 79 f9 fc ]--
Feb 27 16:48:36.475572 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code 255, len   0 ]--
Feb 27 16:48:36.475612 [MSTR][NOTE] [default:default][RLY][INET][irb.2100] jdhcpd_packet_handle: BOOTPREQUEST irb.2100 arrived on unconfigured interface DISCOVER, flags 3, config 0x0
Feb 27 16:48:51.981785 [MSTR][INFO]  jdhcpd_io_recv_pkt: recvmsg() l3_ifindex: 74
Feb 27 16:48:51.981866 [MSTR][NOTE]  jdhcpd_io_recv_pkt: recvmsg() l2_ifindex: 85
Feb 27 16:48:51.982628 [MSTR][INFO] [irb.2100] jdhcpd_io_get_ifs: The L3 interface is 74 and L2 interface is 85, using the L3 interface
Feb 27 16:48:51.982666 [MSTR][NOTE]  jdhcpd_io_reader: Recv DHCP packet on logical-system default, routing-instance default, if irb.2100 size 300
Feb 27 16:48:51.982723 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   from == 0.0.0.0, port == 68 ]--
Feb 27 16:48:51.982762 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   size == 300, op == 1 ]--
Feb 27 16:48:51.982795 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  flags == 8000 ]--
Feb 27 16:48:51.982829 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  htype == 1, hlen == 6 ]--
Feb 27 16:48:51.982862 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   hops == 0, xid == 58d37e3a ]--
Feb 27 16:48:51.982895 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   secs == 6400, flags == 8000 ]--
Feb 27 16:48:51.982930 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP ciaddr == 0.0.0.0 ]--
Feb 27 16:48:51.982965 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP yiaddr == 0.0.0.0 ]--
Feb 27 16:48:51.982999 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP siaddr == 0.0.0.0 ]--
Feb 27 16:48:51.983033 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP giaddr == 0.0.0.0 ]--
Feb 27 16:48:51.983086 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP chaddr == 84 7b eb 27 e9 f0 00 00 00 00 00 00 00 00 00 00 ]--
Feb 27 16:48:51.983120 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP  sname ==  ]--
Feb 27 16:48:51.983152 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ DHCP/BOOTP   file ==  ]--
Feb 27 16:48:51.983285 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  53, len   1, data DHCP-DISCOVER ]--
Feb 27 16:48:51.983386 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  61, len   7, data 01 84 7b eb 27 e9 f0 ]--
Feb 27 16:48:51.983430 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  50, len   4, data ac 11 00 82 ]--
Feb 27 16:48:51.983479 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  12, len  13, data 41 47 49 54 2d 4c 2d 54 43 57 31 33 35 ]--
Feb 27 16:48:51.983522 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  60, len   8, data 4d 53 46 54 20 35 2e 30 ]--
Feb 27 16:48:51.983572 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code  55, len  14, data 01 03 06 0f 1f 21 2b 2c 2e 2f 77 79 f9 fc ]--
Feb 27 16:48:51.983606 [MSTR][INFO] [default:default][RLY][INET][irb.2100] --[ OPTION code 255, len   0 ]--
Feb 27 16:48:51.983646 [MSTR][NOTE] [default:default][RLY][INET][irb.2100] jdhcpd_packet_handle: BOOTPREQUEST irb.2100 arrived on unconfigured interface DISCOVER, flags 3, config 0x0
SRX Services Gateway
Solution
Accepted by topic author tcw135
‎02-28-2019 05:11 AM

Re: DHCP Relay issues on SRX320

‎02-27-2019 02:21 PM

I suspect you are just mixing configs from different platforms, but to be sure, on the 300 series you need to reference irb interfaces and not vlan.

 

# show forwarding-options
dhcp-relay {
    server-group {
        SERVER {
            172.17.0.5;
        }
    }
    group Test {
        active-server-group SERVER;
        interface vlan.900;
        interface vlan.2100;
        interface vlan.2400;
        interface vlan.2600;
        interface vlan.2800;
        interface vlan.2900;
    }
}

 

SRX Services Gateway

Re: DHCP Relay issues on SRX320

‎02-27-2019 07:55 PM

Can you confirm if the DHCP clients and servers are on same Routing Instance ? I have seen similar issues when they are on different routing instnaces.

Thanks,
Suraj
Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too
SRX Services Gateway

Re: DHCP Relay issues on SRX320

‎02-28-2019 05:06 AM

I believe we only have one routing instance.

> show route instance
Instance             Type
         Primary RIB                                     Active/holddown/hidden
master               forwarding
         inet.0                                          542/0/2

__juniper_private1__ forwarding
         __juniper_private1__.inet.0                     7/0/0

__juniper_private2__ forwarding
         __juniper_private2__.inet.0                     0/0/1

__master.anon__      forwarding
SRX Services Gateway

Re: DHCP Relay issues on SRX320

‎02-28-2019 05:15 AM

@smicker wrote:

I suspect you are just mixing configs from different platforms, but to be sure, on the 300 series you need to reference irb interfaces and not vlan.

 

# show forwarding-options
dhcp-relay {
    server-group {
        SERVER {
            172.17.0.5;
        }
    }
    group Test {
        active-server-group SERVER;
        interface vlan.900;
        interface vlan.2100;
        interface vlan.2400;
        interface vlan.2600;
        interface vlan.2800;
        interface vlan.2900;
    }
}

 


This looks to be the issue.  In production, we have it defined correctly on the SRX320s but for some reason in our test environment we missed it.  I'm actually surprised it didn't fail commit the way we had it.  And we're still seeing the original issue I described on SRX210s and SRX220s but those are in production so it's hard to test on them.

 

Thank you, for finding our mistake!  Also, thank you everyone else for the help!

SRX Services Gateway

Re: DHCP Relay issues on SRX320

‎02-28-2019 05:33 AM

I'm disappointed in myself for not seeing the incorrect configuration because we are seeing this issue on other devices that are configured correctly.  I was hoping that since this looked to be happening finally on our test environment that we could get it resolved but that doesn't seem to be the case.  I'm hoping I can take some of what was suggested here and troubleshoot further on my own.  I really do appreciate all the suggestions!