Table of Contents
Advertisement
Copyright © 2011, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
As a workaround:
Configure the Layer 2 circuit for a nonstandby connection.
1.
Change the configuration to a standby connection.
2.
Add the NSR configuration.
3.
[PR/440743]
On SRX210 Low Memory devices, the E1 interface flaps and traffic does not pass through
the interface if you restart forwarding while traffic is passing through the interface.
[PR/441312]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, when you configure the
SAP listen option using the
both sparse and sparse-dense modes. [PR/441833]
On J Series devices, one member link goes down in a Multilink (ML) bundle during
bidirectional traffic with Multilink Frame Relay (MFR). [PR/445679]
On SRX100, SRX210, and J Series devices, out-of-band dial-in access using a serial
modem does not work. [PR/458114]
On SRX100 and SRX200 devices with VDLS2, multiple carrier transitions (three to
four) are seen during long-duration traffic testing with the ALU 7302 DSLAM. There is
no impact on traffic except for the packet loss after long-duration traffic testing, which
is also seen in the vendor CPE. [PR/467912]
On SRX210 devices with VDLS2, the remote end ping operation fails to go above the
packet size of 1480 because the packets are dropped for the default MTU, which is
1496 on an interface, and because the default MTU of the remote host Ethernet
interface is 1514. [PR/469651]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, when you change the
multicast scoping to a different multicast address, traffic other than which is configured
for multicast scoping is not received. [PR/482957]
On SRX210 High Memory devices, the physical interface module (PIM) shows time in
ADSL2+ ANNEX-M, even though it is configured for ANNEX-M ADSL2. [PR/497129]
On SRX100, SRX210, SRX240, and SRX650 devices, whenever
configured under the
profile
radius times out. As a workaround, configure
under the
access
option. [PR/503717]
On SRX5600 and SRX5800 devices, load balance does not happen within the
aggregated Ethernet
(ae)
incrementing the dst ip. [PR/505840]
On SRX100, SRX210, SRX240, and SRX650 devices, egress queues do not function
on VLAN or IRB interfaces. [PR/510568]
On SRX650 devices, in the 2-port 10G XPIM, when the interface is linked with fiber, the
activity LED does not blink when traffic enters the interface. However, the activity LED
blinks properly when traffic goes out of the interface. [PR/513961]
protocol sap listen
command in the CLI, listening fails in
option, radius server is marked as dead permanently if
radius-server
interface when you prefix the length with /24 while
radius-server
is
outside the
option
profile
161
Advertisement
Table of Contents
