Copyright © 2010, Juniper Networks, Inc.
Known Problems and Limitations
47
Release 11.1.1
z
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.
z
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]
z
When you configure an E120 or E320 router with an ES2 10G ADV LM as a LAC on one
side of an L2TP tunnel and as a LNS to receive packets from the LAC on the other
side of the tunnel, use RADIUS servers for authentication of subscribers on both sides
of the tunnel, and attempt to bring up 16,000 subscribers on the L2TP tunnel, the LM
that has subscribers on the LAC side of the tunnel resets when approximately 8000
logged-in subscribers are logged out and try to reestablish the connection. [Defect ID
184118]
RSVP-TE
z
After 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]
Service Manager
z
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]
−
show service-management subscriber-session
subscriberName
interface
interfaceType interfaceSpecifier
−
show service-management subscriber-session
subscriberName
interface
interfaceType interfaceSpecifier
service-session
serviceName
This problem also occurs when a subscriber is authenticated using a RADIUS server
for a combined IPv4 and IPv6 service in a dual stack.
Work-around
: To avoid this problem, use the
show service-management
owner-session
ownerName ownerId
command to display subscriber session
information based on the session owner, instead of the
show service-management
subscriber-session
subscriberName
interface
interfaceType
command to display
details on subscriber sessions.
z
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]
