Resolved Issues

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

• 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: This issue has been resolved.]
• When the chassis process (chassisd) restarted, an erroneous SNMP alarm for power supply failure was logged. [PR/100753: This issue has been resolved.]
• On J-series Services Routers configured with an IPSec tunnel, when you disabled the loopback interface, OSPF randomly chose a router ID and sent a routing update to the remote router using the IPSec tunnel endpoint, causing the packet to loop. Traffic forwarding stopped and a core file was generated. [PR/233271: This issue has been resolved.]
• On a J6350 Services Router with a Crypto Accelerator Module, when fragmented packets were processed the forwarding process generated a core file and stopped operating. [PR/251168: This issue has been resolved]
• When a large number of packets traversed a GRE-over-IPSec tunnel that has a J4350 Services Router with a Crypto Accelerator Module as one of its endpoints, the Services Router stopped forwarding traffic. [PR/101337: This issue has been resolved.]
• If you used a G.SHDSL interface in two-wire mode with an ADTRAN DSLAM, the 320-Kbps line rate did not work. [PR/62177: 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 line flaps at 320 Kbps with an ADTRAN DSLAM. [PR/64727; 64729: This issue has been resolved.]
• On a Dual-Port Channelized T1/E1 PIM, all links might not be available after the 24 individual time slots on one channelized T1 port are dropped and inserted into the 24 individual time slots on another channelized T1 interface on the same PIM. [PR/81976: This issue has been resolved]