detected at a higher rate when the per-network processor rate reaches the
threshold. [PR/442376]
■ On SRX5600 devices, equal-cost multipath (ECMP) does not work at Layer 4
when transit traffic is passed. [PR/444054]
■ 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 64-byte packet size T3 links
when bidirectional traffic is directed. [PR/452652]
■ On SRX240 PoE and J4350 devices, the first packet on each multilink class gets
dropped on reassembly. [PR/455023]
■
On SRX240 PoE and J Series devices, packet drops are seen on the lsq interface
when transit traffic with a frame length of 128 bytes is sent. [PR/455714]
■ 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 2.3 version 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 jexec event, packet summary trace messages have unknown
IP 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]
■ GPRS tunneling protocol (GTP) application is supported on well-known ports
only. 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 timeslots) should not be bundled
under one ML 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]
Hardware
■ On SRX210 devices, the MTU size is limited to 1518 bytes for the 1-port SFP
Mini-PIM. [PR/296498]
■ On SRX240 and SRX650 devices and 16-port or 24-port GPIMs, the 1G half-duplex
mode of operation is not supported in the autonegotiation mode. [PR/424008]
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers ■ 149
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
To Next Page
Loading...