Outstanding J-series Services Router Issues

The following problems currently exist in J-series Services Routers. The identifier following the description is the tracking number in the Juniper Networks bug database.

• For ISDN dialer interfaces, when you include the no-keepalives statement at the [edit interfaces dl0 unit logical-unit-number] hierarchy level and you issue the show interfaces dl0 command, the output might display default keepalive settings. [PR/58520]
• If you disable an adaptive services interface by including the disable statement at the [edit interfaces sp-0/0/0] hierarchy level and then delete the disable statement from the configuration, the IPSec service might not reset correctly. As a workaround, either issue the deactivate services command followed by the activate services command, or issue the request chassis pic offline fpc-slot pim-slot pic-slot 0 command followed by the request chassis pic online fpc-slot pim-slot pic-slot 0 command. [PR/58522]
• When you configure the dialer-watch option, IPv6 prefixes are not monitored. [PR/59143]
• If you take an ISDN interface offline, the LEDs on the ISDN PIM might not turn off. [PR/59536]
• For ISDN interfaces, if you include the vrf-table-label statement at the [edit interfaces routing-instances routing-instance-name] hierarchy level, packets might be dropped from the connection. [PR/59718]
• For ISDN dialer interfaces, if you include the minimum-links statement at the [edit interfaces dl0 unit logical-unit-number] hierarchy level and then deactivate the BRI interface associated with the dialer interface, the output packets counter displayed in the output of the show interfaces command might continue to increment when the specified number of minimum links are not available. [PR/59986]
• For ISDN dialer interfaces, when you configure the load-threshold 100 statement at the [edit interfaces dl0 unit logical-unit-number dialer-options] hierarchy level and the 56-Kbps threshold is exceeded, the interface does not support additional network traffic and might not activate another BRI interface. [PR/60045]
• If you oversubscribe an E1 interface, latency on the high-priority queue might be higher than expected. As a workaround, configure a shaping rate on the E1 interface that is equal to the line rate minus the E1 framing overhead. [PR/60595]
• Host inbound and outbound packets might experience high latency. This does not affect user data traffic. [PR/61208]
• If you are using a G.SHDSL interface in two-wire mode with an ADTRAN DSLAM, the 320-Kbps line rate might not work. [PR/62177]
• A G.SHDSL interface configured in two-wire mode with an ADTRAN DSLAM might show considerable packet loss if the line rate is configured at 448 Kbps. [PR/62179]
• When a G.SHDSL interface initiates negotiations with an ADTRAN DSLAM, the G.SHDSL interface requires more than a minute to negotiate successfully. PR/[62462]
• The Network Control Protocol (NCP) state is shown as Opened in the output of the show interface dlx command, even when the multilink dialer is inactive. [PR/63141]
• For multilink dialer interfaces, the Network Control Protocol (NCP) inet6 status in the output of the show interface dlx command always displays not-configured, even when the IPv6 addresses are configured and are reachable. [PR/63344]
• On a J2300 Services Router with G.SHDSL interfaces installed, the 320-Kbps line rate might not work with an ADTRAN DSLAM. [PR/64727]
• On a J2300 Services Router with G.SHDSL interfaces installed, the 440-Kbps line rate might not work with an ADTRAN DSLAM. [PR/64729]
• If an ISDN dialer interface is configured as a dialer watch interface and is deactivated and configured as a backup interface, the dialer interface does not dial out when the primary interface becomes unavailable. As a workaround, disable the primary interface and commit the configuration, then enable the primary interface and commit the configuration. [PR/67355]
• If you configure an IPSec-over-GRE tunnel, there might be fragmentation issues. As a workaround, delete the clear-dont-fragment statement and the mtu statement on the GRE interface, and include the tunnel-mtu 9192 statement at the [edit services ipsec-vpn rule rule-name term term-name then] hierarchy level on both sides of the connection. [PR/74377]