JUNOSe 10.3.1 Release Notes
58
Resolved Known Problems
PPPoE
Old PPPoE subinterfaces cause subscriber connectivity problem. [Defect ID
89681]
When you connect a PPPoE subscriber and then shutdown the interface from
the CLI, PPPoE lockout is not activated on the server. Instead if you first log out
the subscriber from the server using the
logout subscriber
command, PPPoE
lockout is activated. [Defect ID 90044]
When many PPPoE subscribers were attempting to reconnect on a line
module, the RADIUS server experienced an outage. Some of the subscribers
were unable to reconnect. Some subscribers recieved PADRs but no PADS
could be sent. [Defect ID 90216]
When you change the configuration of a dynamic PPPoE subinterface, no
warning message is displayed when you use the
no pppoe auto-configure
command. This results in the creation of multiple ghost PPP and IP
subinterfaces. [Defect ID 90266]
Policy Management
When you modify a rate-limit profile in Global Configuration mode after the
system is in a scaled state, changes to the rate-limit profile fail owing to lack of
adequate policy resources. However, the changed value of the rate-limit profile
is displayed in the output of the
show rate-limit profile
command. [Defect ID
184107]
When an interface that the SRC software manages is removed, the static policy
list continues to show references to the removed interface. [Defect ID 89239]
When the services used inherit profile policies, deactivating one of the services,
impacts the other services as well. [Defect ID 89587]
QoS
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]
If a scheduler profile is configured with shaping rate greater than oc3/oc12 port
speed is attached at ATM port interface, then the implicit atm scheduler profile
is used instead of user configured scheduler profile. [Defect ID 183595]
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]
