Dynamic Host Configuration Protocol (Dhcp); Dynamic Vpn; Flow And Processing - Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note

Known Limitations in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
Copyright © 2010, Juniper Networks, Inc.

Dynamic Host Configuration Protocol (DHCP)

SRX Series and J Series devices do not support DHCPv6 client authentication.
NOTE: Existing DHCPv4 configurations in the [
hierarchy are not affected when you upgrade to Junos OS Release 10.4
from an earlier version or enable DHCPv6 server.

Dynamic VPN

SRX100, SRX210, and SRX240 devices have the following limitations:
The IKE configuration for the dynamic VPN client does not support the hexadecimal
preshared key.
The dynamic VPN client IPsec does not support the Authentication Header (AH)
protocol and the Encapsulating Security Payload (ESP) protocol with NULL
authentication.
When you log in through the Web browser (instead of logging in through the dynamic
VPN client) and a new client is available, you are prompted for a client upgrade even
if the force-upgrade option is configured. Conversely, if you log in using the dynamic
VPN client with the
force-upgrade
automatically (without a prompt).

Flow and Processing

On SRX Series devices, data plane logs generated in event mode or in configurations
using set system syslog can increase CPU utilization dramatically, impacting the system
stability, especially in chassis cluster mode.
On SRX100 devices, multicast data traffic is not supported on IRB interfaces.
The service-point zone parameter for the SRX Series MGW configuration is not
supported in Junos OS Release 10.4.
You cannot configure route policies and route patterns in the same dial plan.
You can configure no more than four members in a station group. Station groups are
used for hunt groups and ring groups.
On J Series devices, even when forwarding options are set to drop packets for the ISO
protocol family, the device forms End System-to-Intermediate System (ES-IS)
adjacencies and transmits packets because ES-IS packets are Layer 2 terminating
packets.
On SRX Series and J Series devices, high CPU utilization triggered due to various reasons
like CPU intensive commands, SNMP Walks etc causes the BFD to flap while processing
large BGP updates.
For other limitations in flow and processing, see "Limitations of Flow and Processing" in
the Junos OS Security Configuration Guide.
edit system services dhcp
option configured, the client upgrade occurs
]
135