Outstanding Issues

User Interface and Configuration

• A user cannot log in to the J-Web client through RADIUS or TACACS+ authentication if the user profile already has authorization parameters specified on the server side. As a workaround, ensure that the user profile parameters are not specified or are set with empty values on the server. [PR/94445]

Platform and Infrastructure

• On J-series Services Routers, you cannot use a USB device that provides U3 features (such as the "U3 Titanium" device from SanDisk Corporation) as the media device during system boot. You must remove the U3 support before using the device as external media. For the U3 Titanium device, you can use the U3 Launchpad Removal Tool on a Microsoft Windows system to remove the U3 features. The tool is available for download at http://www.sandisk.com/Retail/Default.aspx?CatID=1415 . (To restore the U3 features, you can use the U3 Launchpad Installer Tool accessible at http://www.sandisk.com/Retail/Default.aspx?CatID=1411.) [PR/102645]
• 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, you should note any changes you make to the BIOS configuration. This allows you to revert to the default BIOS configuration as needed. [PR/237722]

Interfaces and Chassis

• On channelized E1 interfaces, you might be able to configure clocking on ds-pim/0/port:n interfaces, where n is not unit 0. This is an invalid configuration and might cause a clocking selection problem on the other channels. [PR/24722]
• On channelized T3 interfaces, the T1 loopback state does not reflect loopbacks set by facilities data link requests using the remote-loopback-respond statement at the [edit interfaces interface-name t1-options] hierarchy level. [PR/45837]
• For ISDN dialer interfaces, when you configure the no-keepalives statement at the [edit interfaces dl0 unit logical-unit-number] hierarchy level and you issue the show interfaces dl0 command, the Link flags field might still show keepalives. [PR/58520]
• If you disable a services interface by including the disable statement at the [edit interfaces sp-pim/0/port] hierarchy level and then delete the disable statement from the configuration, IPsec service is 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 take an ISDN interface offline, the LEDs on the ISDN PIM might not turn off. [PR/59536]
• On ISDN interfaces in a J-series Services Router, if you include the vrf-table-label statement at the [edit routing-instances instance-name] hierarchy level, packets might be dropped from the connection. [PR/59718]
• On ISDN dialer interfaces, if you configure 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 dl0 command might continue to increment. [PR/59986]
• On ISDN dialer interfaces in a J-series Services Router, when you include the load-threshold 100 statement at the [edit interfaces dl0 unit logical-unit-number dialer-options] hierarchy level and the 56-Kbps bandwidth threshold is exceeded, the interface does not support additional network traffic and might not activate another BRI interface. [PR/60045]
• 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]
• On J4350 and J6350 Services Routers, when an Avaya VoIP TGM550 module is in reset state, the Services Router might not respond to show chassis commands for up to 5 seconds. [PR/78695]
• 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]
• If you ping a nonexistent IPv6 address that belongs to the same subnet as an existing point-to-point link, the packet loops between the two point-to-point interfaces until the time-to-live timer expires. [PR/94954]
• On J-series Services Routers running JUNOS Release 8.3 or later, a Channelized T1/E1/ISDN PRI PIM running firmware version 2.3 or earlier might not initialize or might have clocking problems. After an upgrade to JUNOS 8.3 or later, verify the firmware version of any Channelized T1/E1/ISDN PRI PIM by issuing the show system firmware command. If the firmware version is not 2.4 or later, contact Juniper Networks customer support. [PR/102638]