Juniper JUNOSE 11.1.0 - REV 4-29-2010 Manual page 64

JUNOSe 11.1.0 Release Notes
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]
The CLI erroneously enables you to configure a QoS profile with the ethernet
node group command. [Defect ID 80861]
The dynamic shaping rate calculated by the simple shared shaper can vary
because of the variation in the enqueue rate of the constituent queues. Even
when the offered load is constant, the mechanism that calculates the enqueue
rate introduces a slight variation, introducing a slight variation in the calculated
dynamic shaping rate. [Defect ID 80938]
On a router that has both an ES2 10G LM and an ES2 4G LM installed, the byte
count reported by the show fabric-queue egress-slot command is incorrect.
The reported packet count is correct. [Defect ID 80965]
On the E120 and E320 routers, you cannot attach QoS profiles to L2TP tunnels
by means of the CLI because the CLI does not pass the router ID to QoS.
[Defect ID 81516]
PPP sessions may be dropped if you change the shaping rate in a QoS profile
that affects thousands of circuits while QoS traffic affected by the profile is
being forwarded. [Defect ID 82950]
Work-around: Do not change the shaping rate in a QoS profile that affects
thousands of circuits while QoS traffic is using the profile.
Egress traffic may be dropped on OC12/STM4 ATM interfaces if you have
shaped the port rate to more than 542 Mbps. [Defect ID 83785]
Work-around: Do not exceed a shaped port rate of 542 Mbps.
Incorrect output is sent to the CLI the first time you enter Global Configuration
mode or issue the show subscribers command after viewing the VLAN
subinterface over which a subscriber is connected. [Defect ID 84507]
When QoS resources such as failure nodes and statistics bins are exhausted
because of insufficient memory available on the line module, the failures are
properly logged, but additional log messages are generated every 10 minutes
that report zero failures. [Defect ID 85105]
56
Known Problems and Limitations