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.

Platform and Infrastructure

• On J2320, J2350, J4350, and J6350 Services Routers, when you press the F10 key to save and exit from BIOS configuration mode, the operation might not work as expected. As a workaround, use the Save and Exit option from the Exit menu. This issue can be seen on the J4350 and J6350 routers with BIOS Version 080011 and on the J2320 and J2350 routers with BIOS Version 080012. [PR/237721]
• On J2320, J2350, J4350, and J6350 Services Routers, the Clear NVRAM option in the BIOS configuration mode does not work as expected. This issue can be seen on the J4350 and J6350 routers with BIOS Version 080011 and on the J2320 and J2350 routers with BIOS Version 080012. To help mitigate this issue, note any changes you make to the BIOS configuration so that you can revert to the default BIOS configuration as needed. [PR/237722]
• A J4350 or J6350 Services Router running JUNOS Release 8.0 will not function properly if the channelized T1/E1 PIM or the Avaya TGM550, TIM510, TIM514, or TIM521 VoIP modules are installed on the router. In addition, having these modules installed on a router running a JUNOS release that is too early can adversely affect the modules or the router configuration.

  To ensure that the router and the modules operate properly, take the following precautions:

  • Before you install a channelized T1/E1 PIM, upgrade the router to JUNOS Release 8.1 or later.
  • Before you install Avaya VoIP modules, upgrade the router to JUNOS Release 8.2.
  • Before you downgrade from JUNOS 8.2 or 8.1 to JUNOS 8.0, remove any channelized T1/E1 PIMs or Avaya VoIP modules installed on the router.

  [PR/74308]

Services Router User Interface and Configuration

The J-Web event viewer does not display the event ID for any event when you configure the system log file to include the message priority (facility name and severity level) in messages sent to a file:

• In the J-Web interface, by selecting Configuration>System>Syslog>File>filename>Explicit priority
• In the CLI, by including the explicit-priority statement at the [edit system syslog file messages] hierarchy level

You cannot filter events with the J-Web event viewer when you set the timestamp format for a system log file to milliseconds:

• In the J-Web interface, by selecting Configuration>System>Syslog>Time format>Millisecond
• In the CLI, by including the time-format millisecond statement at the [edit system syslog] hierarchy level

[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 a 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]
• 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]
• If you send an RPM ICMP ping probe through an IPSec tunnel and the probe includes the hardware-timestamp statement at the [edit services rpm probe owner-name test test-name] hierarchy level, the probe might not work. [PR/75927]
• On J4350 and J6350 Services Routers, if the MTU is set to more than 6 KB for a built-in Gigabit Ethernet port or a 1-port Gigabit Ethernet ePIM, packets might be discarded with an FCS error. [PR/82245]
• On serial interfaces transmitting either 64–byte or 128–byte packets, the effective bandwidth falls when the interface is highly oversubscribed. [PR/235753]

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]