Pppoe; Qos - Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note

For e series broadband services routers
Table of Contents

Advertisement

JUNOSe 10.0.3 Release Notes

PPPoE

QoS

46
Known Problems and Limitations
When you enter the no ip policy-parameter hierarchical parameterName
command or no ipv6 policy-parameter hierarchical parameterName
command for a hierarchical policy-parameter type in Interface Configuration
mode, the explicit reference of the parameter is removed successfully from the
interface. However, the Referenced by interfaces field in the output of the
show policy-parameter command does not change from the previously
configured value to implicit. [Defect ID 183957]
Work-around: To correct this problem, remove the entire interface
configuration.
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]
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]
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]
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.
Egress strict-priority packets may experience high latency on OC3/STM1 ATM
interfaces associated with the ES2 4G 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 ERX-1440 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]
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.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 10.0.3

Table of Contents