Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 148

JUNOS OS 10.4 Release Notes
148
On SRX210, SRX240, and J6350 devices, the serial interface goes down for
long-duration traffic when FPGA version 2.3 is loaded in the device. As a result, the
multilink goes down. This issue is not seen when downgrading the FPGA version from
2.3 to 1.14. [PR/461471]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, in end-to-end debugging,
the cp-lbt event actions are not working. There is no change in behavior with or without
the cp-lbt event. [PR/462288]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, during end-to-end
debugging with the event, packet summary trace messages have unknown IP
jexec
addresses in the packet summary field. [PR/463534]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices,
does not work properly. When users configure a low rate limit for a large number of
trace messages, the system should suspend the trace messages after the configured
maximum is reached. The system is not suspending the trace messages. [PR/464151]
On SRX5800 devices, the GPRS tunneling protocol (GTP) application is supported
only on well-known ports. Customized application on other ports is not supported.
[PR/464357]
On J Series devices, interfaces with different bandwidths (even if they are of same
interface type, for example, serial interfaces with different clock rates or channelized
T1/E1 interfaces with different time slots) should not be bundled under one multilink
bundle. [PR/464410]
SRX3400 and SRX3600 devices with one Services Processing Card and two Network
Processing Cards operating under heavy traffic produce fewer flow sessions.
[PR/478939]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, the input packets and
bytes counter shows random values both in traffic statistics and IPv6 transit statistics,
when VLAN tagging is added or removed from the IPv6 address configured interface.
[PR/489171]
On SRX Series devices, the software upload and install package does not show a
warning message when there are pending changes to be committed. [PR/514853]
On SRX240 Low Memory devices, the LSQ interface transmitting both LLQ and non-LLQ
traffic drops out-of-profile packets of the LLQ traffic faster than it was dropping out
earlier. [PR/536588]
On SRX5800 devices, address overlapping is not supported when dual-stack lite works
with the source NAT and enables any of the following options:
persistent-nat
port no-translation
host-address-base (IP shifting)
[PR/540816]
On SRX3600 devices, if the interface address is changed to a new address that is also
the dual-stack lite concentrator address with the background traffic target to the
data path-debug rate-limit
Copyright © 2010, Juniper Networks, Inc.