Known Problems and Limitations
47
Release 10.2.2
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]
The
no qos-parameter-define definition
command does not delete the
specified QoS parameter definition. [Defect ID 176844]
Work-around
: Remove the interface and add the desired QoS parameters when
you re-create the interface instead of deleting the definition.
When 32,000 subscribers with 128,000 QoS queues are brought up on an ES2
10G or ES2 10G ADV LM, the LM resets if you modify the QoS profile that
contains the best-effort IP or VLAN node rule, which references a scheduler
profile configured with shared shaping rate, to a scheduler profile configured
with legacy shaping rate. [Defect ID 183291]
Work-around
: To avoid this problem, apply shared shaping on the best-effort
queue, instead of on the best-effort node.
RSVP-TE
After a stateful SRP switchover, forwarding of VPN traffic might not resume if
the core interface that carries an MPLS base tunnel with LDP over RSVP-TE
flaps (constantly goes up and down). [Defect ID 182019]
