Legacy DHCPD (DHCP Daemon) configuration syntax will be hidden starting from 15.1X49-D60

Currently, the SRX platform supports two syntax styles for configuring DHCP Client, Server, and Relay. These two configuration syntax styles correspond to two different DHCP daemons, namely the legacy DHCPD, and JDHCP. Moving forward, all the new features and capabilities will be developed on JDHCP. The deprecation plan for DHCPD will begin with the following changes starting from Junos OS Release 15.1X49-D60:

• The factory default DHCP Server / Client configuration is changed to JDHCP style.
• DHCPD configuration syntax will be hidden, but will continue to function and pass commit check as before.
• When upgrading a device to 15.1X49-D60 and onwards (until deprecation is completed), a warning message is displayed if DHCPD configuration syntax is present.
• A commit error is displayed if both DHCPD and JDHCP is configured simultaneously.
• J-Web is updated to support JDHCP exclusively.

      Note: DHCPD configuration style must be manually converted to JDHCP first via CLI before using DHCP with J-Web.

Solution:
To prepare for the future deprecation of DHCPD, it's recommended that the DHCPD's configuration syntax be converted to JDHCP's syntax style. Most of the configuration statements in DHCPD already have an equivalent in the JDHCP configuration style. For those that do not have an equivalent configuration statement, the commands will be added in future Junos OS releases before DHCPD is fully deprecated.

Note: The system does not allow both daemons to run at the same time. If you are using more than one function of the DHCP daemon (for example, both DHCP Client and DHCP Server), you must migrate both of those functions at the same time.


Legend:
Black: Both DHCPD and JDHCP have the same command (top level hierarchy may be different).
Blue: Different keyword for the same function between DHCPD and JDHCP.
Red: The JDHCP equivalent will be implemented in a future Junos release.

DHCP Client:

DHCPD	JDHCP
Hierarchy Level: [edit interfaces interface-name unit logical-unit-number family inet dhcp]	Hierarchy Level: [edit interfaces interface-name unit logical-unit-number family inet dhcp-client]
client-identifier	client-identifier
ascii ascii	userid ascii ascii
hexadecimal hexadecimal	userid hexadecimal hexadecimal
lease-time	lease-time
retransmission-attempt	retransmission-attempt
retransmission-interval	retransmission-interval
server-address	server-address
update-server	update-server
vendor-id	vendor-id

 DHCPD

	JDHCP
Hierarchy Level: [edit system services dhcp pool subnet-ip-address/mask]	Hierarchy Level: [edit access address-assignment pool pool-name family inet]
subnet-ip-address/mask	network network
address-range	range range-name
high address	high address
low address	low address
static-binding	host hostname
mac-address	hardware-address mac-address
fixed-address ip-address	ip-address ip-address
Hierarchy Level: [edit system services dhcp pool subnet-ip-address/mask]	Hierarchy Level: [edit access address-assignment pool pool-name family inet dhcp-attributes]
boot-file	boot-file
boot-server	boot-server
default-lease-time seconds	maximum-lease-time seconds (merged)
domain-name	domain-name
domain-search dns-search-suffix	option 119 string "dns-search-suffix"
exclude-address ip-address	excluded-address ip-address (available starting from 15.1X49-D60)
maximum-lease-time seconds	maximum-lease-time seconds
name-server	name-server
next-server	next-server
option	option
propagate-ppp-settings	propagate-ppp-settings
propagate-settings	propagate-settings
router	router
server-identifier	server-identifier
sip-server	sip-server
address ip-address	ip-address ip-address
name sip-server-name	name sip-server-name
wins-server	wins-server
Hierarchy Level: [edit system services dhcp]	Hierarchy Level: [edit system processes dhcp-service]
traceoptions	traceoptions
Hierarchy Level: [edit system services dhcp]	Hierarchy Level: [edit access address-assignment pool pool-name family inet]
option option-identifier-code	option option-identifier-code
byte-stream decimal-ascii	hex-string hexadecimal-ascii
(all other option-types are equivalent)	(all other option-types are equivalent)

DHCP Relay:

DHCPD	JDHCP
Hierarchy Level: [edit forwarding-options helpers bootp]	Hierarchy Level: [edit forwarding-options dhcp-relay]
client-response-ttl	(to be implemented in a future Junos release)
description	(to be implemented in a future Junos release)
dhcp-option82	(to be implemented in a future Junos release)
interface interface-name	group group-name interface interface-name
maximum-hop-count	(to be implemented in a future Junos release)
minimum-wait-time	(to be implemented in a future Junos release)
relay-agent-option	(to be implemented in a future Junos release)
server address	server-group server-group-name ip-address

Hardware End of Life Announcement – SRX100, SRX210, SRX240 and SRX6 5 0

This EOL announcement is effective immediately with a Last Order Date (LOD) of May 1, 2016. On the last order date, the products are removed from the pricelist and are no longer orderable.
 

AFFECTED PRODUCTS:

SRX100H2
SRX210HE2
SRX210HE2-POE
SRX240H2
SRX240H2-POE
SRX240H2-DC
SRX650-BASE-SRE6-645AP
SRX650-BASE-SRE6-645DP

Configuring Protection Against DDoS Attacks

DDoS protection is enabled by default for all supported protocol groups and packet types. Default values are present for bandwidth, bandwidth scale, burst, burst scale, priority, and recover time. You can change the DDoS configuration for individual packet types within a protocol group or for the aggregate policer for the protocol group. DDoS logging is enabled by default, but you can disable it globally for all DDoS events or for individual packet types within a protocol group. You can also fine-tune monitoring of DDoS events by configuring tracing operations.

You can disable DDoS protection at the Routing Engine and for all line cards either globally or for individual packet types within a protocol group.

DDoS protection is supported only on MX Series routers that have only MPCs installed and T4000 routers that have only FPC5s installed. If the router has other line cards in addition to MPCs or FPC5s, respectively, the CLI accepts the configuration but the other line cards are not protected and so the router is not protected.