Pppoe; Qos - Juniper JUNOSE SOFTWARE 10.3.2 - RELEASE NOTES 9-29-2010 Release Note

PPPoE

QoS

The E Series router erroneously accepts a PADI with a payload length of 0
instead of rejecting it and incrementing the PPPoE Invalid PAD packet length
counter. [Defect ID 48356]
You cannot paste a load-rebalance command string that uses the percent
option into a console or Telnet session from show configuration output
because the output displays the % sign rather than the percent keyword that
was submitted with the command and the percent sign is not recognized by the
CLI. [Defect ID 81705]
The router cannot resolve inconsistent requests caused by two QoS profiles that
modify the same scheduler property inconsistently. [Defect ID 61485]
Work-around: Avoid using two QoS profiles that modify the same scheduler
property inconsistently, such as setting different values for the shaping rate for
the same S-VLAN node.
Simple shared shaping does not function correctly when it is used for 32,000
subscribers on an ES2 10G ADV LM. However, when you change the shaper to
compound shared shaping, it works properly. Also, simple shared shaping does
not function correctly for 16,000 subscribers on an ES2 10G ADV LM. [Defect
ID 183512]
When you perform an SNMP walk of the juniQosQueueStatistics MIB, a timeout
of up to 5 minutes ensues, during which the SRP module CPU utilization goes to
100 percent. [Defect ID 62252]
The compound shared shaping feature does not work properly on egress
forwarding ASIC 2 (EFA2)-based ATM line modules when the shared shaper is
queue-controlled as opposed to node-controlled. In a node-controlled
configuration, in which you configure the shared-shaping rate on the best-effort
scheduler node for the logical interface, integration of the EFA2 and ATM
segmentation and reassembly (SAR) schedulers functions properly. However, in
a queue-controlled configuration, in which you configure the shared-shaping
rate on the best-effort queue for the logical interface, integration of the EFA2
and ATM SAR schedulers does not function properly. [Defect ID 69167]
Work-around: Use node-controlled compound shared shaping configured on
the best-effort scheduler node with EFA2-based ATM line modules.
Egress strict-priority packets may experience high latency on OC3/STM1 ATM
interfaces associated with the LM if you have shaped the port rate to more than
148.5 Mbps. [Defect ID 80378]
Work-around: To ensure low strict-priority latency, shape the port rate to no
more than 148.5 Mbps.
An error message regarding the qos-parameter instance
QosParameterDefinition is erroneously generated on an ERX1440 router when
it is configured for L2C and QoS RAM and receives TLV 144 (DSL Type). The
parameter instantiation actually functions properly. [Defect ID 80620]
Release 10.3.2
Known Problems and Limitations
47