Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 162

JUNOS OS 10.4 Release Notes
162
Chassis Cluster
On an SRX210 device in a chassis cluster, there might be a loss of about 5 packets with
20 Mbps of UDP traffic on an RG0 failover. [PR/413642: This issue has been resolved.]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices configured for Layer 2 and
chassis cluster, when there was too much DNS traffic through the device, a core file
was generated. [PR/512888: This issue has been resolved.]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, under certain traffic loads,
traffic was affected when a backup device rebooted and rejoined the cluster.
[PR/520757: This issue has been resolved.]
On SRX5800 devices in a chassis cluster, incorrect jitter messages were displayed.
[PR/526975: This issue has been resolved.]
On SRX5600 devices in an active/active chassis cluster, RG1 and RG2 on preempt
mode, reboot node 0, and RPC traffic were blocked. [PR/527771: This issue has been
resolved.]
Command-Line Interface (CLI)
On SRX650 devices, the
security NAT source rule all
[PR/514470: This issue has been resolved.]
Flow and Processing
On SRX650 devices, the uplinks to the CPU could be exhausted and the system was
limited to 2.5 GB throughput traffic when the device was using similar kinds of source
MAC addresses. [PR/428526: This issue has been resolved.]
On SRX240 PoE and J Series devices, packet drops were seen on the
transit traffic with a frame length of 128 bytes was sent. [PR/455714: This issue has
been resolved.]
On SRX240 High Memory devices, when UTM FAV was enabled in the policy (for SMTP
traffic only), Kaspersky AV stopped working after some time and SMTP traffic was
dropped. [PR/491795: This issue has been resolved.]
On SRX Series and J Series devices, when there were more than 200 IGMP/MLD
source-specific multicast groups (232.0.0.0/8) configured statically on an interface,
and when an unrelated configuration was committed, some groups were removed and
added immediately, causing packet drops on those groups. [PR/509013: This issue
has been resolved.]
On SRX Series and J Series devices, system log messages about interactive commands
to the system log server did not work. [PR/511110: This issue has been resolved.]
On SRX Series devices, because of a memory leak, flow processing failed unexpectedly
when security policies were added, deleted, or updated, impacting the traffic.
[PR/522657: This issue has been resolved.]
On SRX3600 devices, transit traffic to the VRRP MAC address was not policed by
simple-filter policing on the IOC. [PR/528402: This issue has been resolved.]
commands did not show rules position content for
show
and
show security NAT destination rule all
commands.
lsq interface when
Copyright © 2010, Juniper Networks, Inc.
show