> dhcp Configure DHCP Client > dhcp-client Dynamic Host Configuration Protocol client configuration + apply-groups-except Don't inherit configuration data from these groups + apply-groups Groups from which to inherit configuration data > address Interface address/destination prefix And the CLI is as helpful as usual with this: set interfaces fe-0/0/0.0 family inet ? Here is the old way to configure the Internet interface: show interfaces The DHCP server and client are related to each other as they are run by the same subsystem. My SRX also uses the DHCP client to receive its WAN IP address and the default route. Now, that above was only the DHCP server part. If you need to restart the DHCP process, you will need to use the “ restart dhcp” or “ restart dhcp-service” command accordingly. Confusing? Yes, DHCP is still working fine but in the dhcp-service subsystem. In this case the device was running the new-style configuration, thus the dhcp subsystem was not in use. If you try the wrong commands you will get this kind of not-really-informative error message: show system services dhcp binding warning: dhcp subsystem not running - not needed by configuration.
This gives also differences to the “show” commands: In the old way you used “ show system services dhcp” commands but in the new way you use “ show dhcp” (or even “ show dhcpv6“) commands. The old way uses dhcp subsystem while the new way uses dhcp-service subsystem. The old and new ways are also run by different processes in the device. Note that you cannot just move the configuration from the old place to the new place as there are syntax differences. It is needed for the DHCPv6 configurations anyway. The “access address-assignment” approach is apparently a bit more modular and more flexible. Here is the corresponding new-style configuration: show system servicesĪll this sounds fair. Here is an example of an old-style configuration: show system servicesĪddress-range low 192.168.100.10 high 192.168.100.49 The new way of configuring the DHCP server consists of configuring a DHCP group in the “system services dhcp-local-server” and then configuring the pool settings in “access address-assignment”, instead of having all the configurations in the “system services dhcp” hierarchy. # Warning: Incompatible with 'system services dhcp-local-server group' # Warning: Incompatible with the dhcp server configured under 'system services dhcp' In fact, if trying to configure DHCP (v4) server in both “system services dhcp” and “system services dhcp-local-server” Junos gives me errors: show system services If you can find some specific and clear documentation that describes the situation and guidelines for the SRX family, please comment below. It appears that “system services dhcp” is the “old” way to do things, and “system services dhcp-local-server” and “access address-assignment” is the “new” way. I have been configuring the DHCP server in my SRX in “ system services dhcp” hierarchy, and tried to configure the DHCPv6 feature in “ system services dhcp-local-server” and “ access address-assignment” hierarchies, just like the guides and hints told me.
I realized something in Junos DHCP configurations: people are talking about “old” and “new” ways to configure DHCP server and client in SRX. I gave up at that time, but returned to the matter some days ago. At some point I tried to configure Juniper SRX100 with DHCPv6 server, with no luck.