■
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, when you configure
the SAP listen option using the
protocol sap listen
command in the CLI, listening
fails in 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 SRX 240 Low Memory devices and SRX 240 High Memory devices, the RPM
Server operation does not work when the probe is configured with the option
destination-interface
.[PR/450266]
■
On J Series devices, the DS3 interface does not have an option to configure
multilink-frame-relay-uni-nni (MFR). [PR/453289]
■
On SRX210 devices, the modem moves to the dial-out pending state while
connecting or disconnecting the call. [PR/454996]
■
On SRX100, SRX210, and J Series devices, out-of-band dial-in access using a
serial modem does not work. [PR/458114]
■
On SRX210 PoE devices, the G.SHDSL link does not come up with an octal port
line card of total access 1000 ADTRAN DSLAM. [PR/459554]
■
On J Series devices, tail drops are seen on a bundle for traffic with a bigger packet
size and smaller fragmentation threshold. [PR/461417]
■
On SRX210 High Memory devices, only six logical interfaces come up on the
G.SHDSL ATM interface (including OAM channel). The other two logical interfaces
are down. [PR/466296]
■
On SRX100 and SRX200 devices with VDLS2, multiple carrier transitions (three
to four) are seen during long duration traffic testing with 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, remote end ping fails to go above the packet
size of 1480 as the packets are get dropped for the default MTU which is 1496
on an interface and the default MTU of the remote host ethernet intf is 1514.
[PR/469651]
■
On SRX210 devices, the G.SHDSL ATM logical interface goes down when ATM
CoS is enabled on the interface with OAM. As a workaround, restart the FPC to
bring up the logical interface. [PR/472198]
■
On SRX210 devices with VDLS2, ATM COS VBR related functionality can not be
tested because of lack of support from the vendor. [PR/474297]
■
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, the
show datapath-debug
counter
command gives error messages from the secondary node. [PR/477017]
■
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, link speeds of 100
Mbps and 1 Gbps cannot be configured on the
ae0
interface with child interfaces
configured. When you commit the configuration, the system displays an error
about the mismatch between the
ae0
and child interfaces. [PR/482649]
■
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 will not be received. [PR/482957]
148
■
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
JUNOS 10.1 Software Release Notes
