Errata

• J-Web Quick Configuration pages do not support IPv6 addressing and routing. [J-series Services Router Basic LAN and WAN Access Configuration Guide]
• Payload loopback functionality is not supported on ATM-over-SHDSL interfaces. [J-series Services Router Basic LAN and WAN Access Configuration Guide]
• JUNOS supports FRF.12 fragmentation header formats for both FRF.15 (MLFR) and FRF.16 (MFR).

  If you configure a permanent virtual circuit (PVC) between T1, E1, T3, or E3 interfaces in Juniper routing platform and another vendor and the other vendor does not have the same FRF.12 support or supports FRF.12 in a different way, the Juniper interface might discard a fragmented packet containing FRF.12 headers and count it as a "Policed Discard." As a workaround for this issue, configure multilink bundles on both peers and configure fragmentation thresholds on the multilink bundle. [J-series Services Router Basic LAN and WAN Access Configuration Guide]

• For 4-port Fast Ethernet ePIMs on J4350 and J6350 Services Routers, if you apply a CoS scheduler map on outgoing (egress) traffic, the router does not divide the bandwidth appropriately among the CoS queues. As a workaround, configure enforced CoS shaping on the ports. [J-series Services Router Advanced WAN Access Configuration Guide]
• On J-series Services Routers, if you create a policy to match IPv4 traffic with a route filter and assign the traffic to a forwarding class, then apply the policy at the [edit class-of-service forwarding-policy class policy-name] hierarchy level, use of the classification-override statement at the [edit class-of-service forwarding-policy class policy-name] hierarchy level is not supported. [J-series Services Router Advanced WAN Access Configuration Guide]