JunosE 12.2.0 Release Notes

Resolved Known Problems

Release 12.2.0 is based on Release 12.1.0 and incorporates all problem resolutions found in that release. The following problems were reported open in Release 12.1.0 and have been resolved in this release, or have been resolved since the 12.1.0 release. For more information about particular resolved problems, you can log in to the JunosE Knowledge Base at https://www2.juniper.net/kb/, enter the defect ID number in the Search by Keyword field, and click Search.

DHCP

• After you create and delete 16,000 DHCP proxy client bindings, the output of the show dhcp proxy-client bindings command displays stale entries. This problem occurs on an E320 router running JunosE Software release 12.2.0. [Defect ID 189450]

IP

• Logical port 20 on the ES2-S3 GE-20 IOA is reserved for the hardware multicast packet replication feature. Logical port 20 and the hardware multicast replication feature are not supported on the ES2-S3 GE-20 IOA in this release. [Defect ID 84727]
• The ES2 4G LM can reset during a unified ISSU after you issue the issu start command on a router configured with 8000 dynamic VCs and 8000 packet-triggered dynamic subscriber interfaces. [Defect ID 86761]

IPSec

• The call setup rate is lower than normal (approximately 2.5 calls per second) when 32,000 PPPv6 subscribers attempt to log in to an E320 router running JunosE Software Release 12.2.0, which is a DHCPv6 local server that delegates IPv6 prefixes to clients. This problem occurs when the following conditions are satisfied: [Defect ID 189210]
• Out of the total of 32,000 subscribers, 16,000 subscribers are logged in to a single port on an ES2 4G LM with ES2-S1 GE-4 IOA.
• Another 8000 subscribers are logged in over one port on an ES2 10G LM with ES2-S1 GE-8 IOA and the remaining 8000 subscribers are logged in over another port on the same ES2 10G LM with ES2-S1 GE-8 IOA.
• Both IPv6 Neighbor Discovery router advertisements and the DHCPv6 Prefix Delegation mechanism are used to delegate prefixes to requesting routers or IPv6 clients.
• RADIUS server is used for authentication of clients.

In such a scenario, when all the 32,000 subscribers are brought up, 32,000 access-internal routes and 32,000 access routes are installed. When the first 16,000 subscriber sessions are established, PPPoE Active Discovery timeouts do not occur.

With the subsequent 16,000 subscriber sessions, the router receives PPPoE Active Discovery Termination packets from some of the clients because of config-request timeout and during the establishment of sessions, the CPU utilization reaches 100 percent.

Also, the call setup rate falls below two calls per second when 48,000 subscribers are brought up in a similar scenario, where both Prefix Delegation and Neighbor Discovery methods are employed.

Subscriber Management

• When you perform a unified ISSU operation from JunosE releases numbered lower than Release 12.2.0 to Release 12.2.0, subscriber traffic outages exceed normal limits. This problem occurs when an ERX router is used as the restarting router and an E120 or E320 router with an ES2 10G ADV line module is used as the helper router. When this slightly increased traffic disruption occurs, the stateful SRP switchover process completes successfully during the unified ISSU procedure and all the line modules except the standby module are active after the stateful SRP switchover operation. [Defect ID 189449]