Known Problems and Limitations
47
Release 10.0.3
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 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 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.
The CLI erroneously enables you to configure a QoS profile with the
ethernet
node group
command. [Defect ID 80861]
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]
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.
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]
Service Manager
When a subscriber has subscribed for a service, service session accounting
records always contains a default Acct-Terminate-Cause value of 10. This value
remains unchanged even after you use the
terminate-code
command to
configure a custom mapping between application terminate reasons and
RADIUS Acct-Terminate-Cause attributes. [Defect ID 181043]
After you activate an independent IPv6 service and issue either of the following
commands on the default virtual router or any other virtual router, except the
one on which the subscriber session is active, no output is displayed in the CLI
interface: [Defect ID 181929]
