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.

Services Router User Interface and Configuration

If you include the explicit-priority statement at the [edit system syslog file messages] hierarchy level, the event ID is not displayed for any event in the J-Web event viewer. If you include system syslog time-format millisecond in the configuration, you cannot filter events in the J-Web event viewer. [PR/70523]

Interfaces and Chassis

• 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 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]
• On a serial PIM of a J-series services router, the member link of an MLPPP bundle might show large, incorrect values for input and output counters when the remote end of the serial connection is not operating. The problem might also happen when the logical interface configuration is deactivated and reactivated. This condition has no operational impact, and after a few minutes the counter values are automatically corrected. [PR/72241]

Class of Service

• 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]
• J4350 and J6350 Services Routers might not have the requisite data buffers needed to meet expected delay-bandwidth requirements. Lack of data buffers might degrade CoS performance with smaller-sized (500 bytes or less) packets. [PR/73054]