Resolved Issues

The following section describes problems resolved since JUNOS Release 8.1R1. The identifier following the description is the tracking number in the bug database.

• 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: This issue has been resolved.]
• 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: This issue has been resolved]
• 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: This issue has been resolved.]
• On a J2300 Services Router with G.SHDSL interfaces installed, the 320-Kbps line rate might not work with an ADTRAN DSLAM. [PR/64727: This issue has been resolved.]
• On a J2300 Services Router with G.SHDSL interfaces installed, the 440-Kbps line rate might not work with an ADTRAN DSLAM. [PR/64729: This issue has been resolved.]
• If you configure the log-out-on-disconnect statement at the [edit system ports] hierarchy level and the console statement at the [edit system syslog] hierarchy level, and you remove and replace the console cable, the console port might lock. [PR/69459: This issue has been resolved.]
• For Gigabit Ethernet and 4-port Fast Ethernet interfaces installed in J6350 and J4350 Services Routers, MAC address filtering is not supported. [PR/70278: This issue has been resolved.]
• The channelized T1/E1 PIMs in Services Routers do not support a bit error rate test (BERT) at the channel level or interface level. [PR/71435: This issue has been resolved.]
• If you configure a real-time performance monitoring (RPM) UDP ping probe and include the hardware-timestamp statement at the [edit services rpm probe owner-name test test-name] hierarchy level, the round-trip time for the probe does not improve. [PR/75467: This issue has been resolved.]
• On Fast Ethernet interfaces installed in Services Routers, if the interface receives traffic with a destination MAC address set to broadcast (ff:ff:ff:ff:ff:ff), it might handle this traffic as keepalive traffic and limit the throughput to approximately 2500 packets per second. [PR/77376: This issue has been resolved.]
• When you configure data link switching (DLSw), the lt-0/0/0 interface, and other interfaces, and then commit the configuration, DLSw might not become established between peers. As a workaround, restart the DLSw process on both peers to establish the DLSw connection. [PR/79493: This issue has been resolved.]