Resolved Issues

The following issues have been resolved since JUNOS Release 8.3R3. The identifier following the description is the tracking number in our bug database.

• When you included the vrf-table-label statement at the [edit routing-instances routing-instance-name] hierarchy level, the incoming traffic was incorrectly considered to come from the internal label-switched interface (LSI) associated with the VRF instance that led to the router not accounting for the incoming traffic. [PR/53148: This issue has been resolved.]
• When you oversubscribed an E1 interface, latency on the high-priority queue was higher than expected. [PR/60595: This issue has been resolved.]
• In the J-Web configuration editor, when you selected System>Syslog >File >Messages >Explicit priority, the J-Web event viewer did not show the event ID. When you selected System>Syslog >Time format>Millisecond, the J-Web event viewer did not filter messages. [PR/70523: This issue has been resolved.]
• A J4350 or J6350 router running JUNOS Release 8.0 were not functioning properly when the Channelized T1/E1/ISDN PRI PIM or the Avaya TGM550, TIM510, TIM514, or TIM521 VoIP modules were installed on the router. [PR/74308: This issue has been resolved.]
• Dialer interface traffic statistics from the output of the show interfaces dl0 extensive command did not display input/output bytes in bps or input/output packets in pps. [PR/77922: This issue has been resolved.]