Table of Contents
Advertisement
Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
On SRX5800 devices, the IOC hot swap is not supported with network processing
bundling. If an IOC configured with network processing bundling is unplugged, all traffic
to that network processor bundle will be lost. [PR/441961]
On SRX5800 devices with interfaces in a network processing bundle, the ICMP flood
or UDP flood cannot be detected at the threshold rate. However, it can be detected
at a higher rate when the per-network processor rate reaches the threshold.
[PR/442376]
On an SRX3400 device in combo mode with two SPCs and one NPC, not all sessions
are created under the stress test. [PR/450482]
On J Series devices, there is a drop in throughput on the 64-byte packet size T3 link
when bidirectional traffic is directed. [PR/452652]
On SRX240 PoE and J4350 devices, the first packet on each multilink class is dropped
on reassembly. [PR/455023]
On SRX5600 and SRX5800 devices, system log messages are not generated when
CPU utilization returns to normal. [PR/456304]
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,
data path-debug rate-limit
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]
Copyright © 2011, Juniper Networks, Inc.
157
Advertisement
Table of Contents
