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

If you include the vrf-table-label statement at the [edit routing-instances routing-instance-name] hierarchy level, the incoming traffic is considered to come from the internal label-switched interface (LSI) associated with the VRF instance. The traffic is not accounted for by the original incoming logical unit, because the original incoming logical interface is unknown and the LSI, being an internal interface, does not have accounting support. [PR/53148]

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. Moreover, 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 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]
• On J-series Services Routers with multilink-frame-relay-uni-nni (FRF.16) encapsulation, when you issue the show interfaces queue command, the kernel returns only the bundle statistics for FRF.16 and does not return the queue statistics; hence the command fails. [PR/69565]
• A J4350 or J6350 router running JUNOS Release 8.0 will not function properly if the Channelized T1/E1 PIM is installed on the router. Ensure the following:
  • Before you install a Channelized T1/E1 PIM, upgrade the router to JUNOS Release 8.1.
  • Before you downgrade from JUNOS 8.1 to JUNOS 8.0, remove any Channelized T1/E1 PIMs installed on the router.

  [PR/74308]

• 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]
• When two links are part of an MLPPP bundle and the link belonging to the bundle on the remote end is disabled, the output of the show interfaces t1-pim/01/port statistics detail command on the local end displays double the value for the Input bytes field. When the link on the remote end is re-enabled, the value for the Input bytes field is correct. [PR/78692]
• On J4350 and J6350 Services Routers, when you insert an Avaya VoIP TGM550 Telephony Gateway Module and the module is in a reset state, the router might not respond to any show chassis commands for up to 5 seconds. [PR/78695]
• For 1-port Gigabit Ethernet ePIMs installed on J-series Services Routers or built-in Gigabit Ethernet interfaces on the J4350 and J6350 Services Routers, if you configure more than one VRRP group on a port to place the port into promiscuous mode and then you issue a ping command, forwarding performance can be affected and duplicate ICMP messages might be sent in response to the ping. [PR/99796]

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]