JunosE 12.3.0 Release Notes

Resolved Known Problems

Release 12.3.0 is based on Release 12.2.0 and incorporates all problem resolutions found in that release. The following problems were reported open in Release 12.2.0 and have been resolved in this release, or have been resolved since the 12.2.0 release. For more information about problems in this list that were reported by customers, 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. Problems that have not been reported by customers are documented only in these Release Notes.

DHCP

• In the output of the show subscribers ipv6 command, the IPv6 Interface Id field, which denotes the EUI-64 IPv6 address of the subscriber's interface, always displays 0:0:0:0 and the Type field, which denotes the type of the subscriber, always displays unknown for IPv6 subscribers. This problem occurs for IPv6 subscribers in both a dual-stack network that contains both IPv4 and IPv6 subscribers and an environment that contains only IPv6 subscribers. [Defect ID 91618]
• When 32,000 DHCPv6 subscribers are brought up over multiple virtual routers at a call setup rate (CSR) of 24 calls per second, the DHCPv6 local server stops responding. This problem occurs due to a deadlock between two instances of the DHCPv6 local server running on the router while the DHCPv6 client entry is being updated. [Defect ID 189282]

Forwarding

• After you configure fast reroute extensions to RSVP-TE to enable local protection for the ingress router of the primary LSP by using bypass tunnels, forwarding of IPv6 traffic to some of the labeled BGP routes or IPv6 destinations over ES2 10G LMs and ES2 4G LMs fails. [Defect ID 189451]

GRE

• After you perform a unified ISSU operation or a stateful SRP switchover from JunosE Releases 11.2.0 through 12.0.0 to JunosE Release 12.1.0, GRE tunnel interfaces configured on ES2 10G ADV line modules that function as shared tunnel-server ports do not appear. This problem occurs only if you configured the tunnel interface as the analyzer interface. [Defect ID 188593]

Hardware

• Load balancing of IPv6 traffic with prefixes of lengths other than /128 does not occur properly on LAG interfaces and equal-cost multipath (ECMP) links configured on ES2 4G LMs and GE-2 LMs. [Defect ID 189885]
• Load balancing of IPv6 traffic with prefixes of lengths other than /128 does not occur properly on access interfaces in a LAG bundle configured on an ES2 10G LM. [Defect ID 189966]

L2TP

• L2TP subscriber sessions that were previously established are disconnected when you perform a stateful SRP switchover operation in a scaled environment. [Defect ID 187454]

Policy Management

• During packet mirroring for secure IPv6 policies, if you configure SNMP secure packet mirroring traps, the traps do not contain any fields to include the IPv6 prefix. However, for IPv4 policies, the IPv6 address field is present in the packet mirroring traps. [Defect ID 189862]

QoS

• Only the headings for S-VLAN aggregate statistics are contained in the bulk statistics (.sts) file that collects QoS statistics on egress queues for various interface types. The corresponding aggregate statistics are not displayed in the corresponding data fields. This problem occurs only when the manual method of data transfer from the router to the receivers is employed by using the manual-xfer keyword with the bulkstats collector collect-mode command. This behavior is not observed when the automated collection method is configured using the auto keyword with the bulkstats collector collect-mode command for the agent to transfer the bulk statistics file to the host when the interval for which the collector transfers data from the router to the receivers expires. [Defect ID 187592]

System

• Beginning with JunosE Release 11.0.0, the FPGA upgrade feature has been enhanced to reduce the booting time of the system. The FPGA upgrade operation takes place only if a system requirement, such as a cyclic redundancy check (CRC) mismatch, occurs. On E120 and E320 routers, if you upgrade the system from a release that supports the enhanced FPGA upgrade (such as 11.0.3), downgrade the system to a release numbered lower than 11.0.0 that does not contain the enhanced the FPGA upgrade mechanism (for example, 9.0.1p0-7-5-2 or 10.2.1p0-2), and then upgrade the router again to a release that supports the enhanced FPGA upgrade mechanism, the SRP-100 or SRP-320 modules might not upgrade the FPGA correctly. [Defect ID 190012]

In JunosE Release 12.2.0, the SRP module that has an FPGA revision number that is different from 0xbd26 denotes this problem. This error can occur with both unified ISSU or cold upgrade operations. However, this condition does not occur when the SRP module is reset after being powered off and turned on, or when the SRP module is unplugged and reinserted into the same slot.

• A single space is present between the string "lag" and the name of the LAG bundle in the COPS handler messages that are sent. This behavior causes the policy manager to not service video-on-demand (VOD) requests properly. [Defect ID 189872]

Unified ISSU

• When you perform a unified ISSU operation after link flaps in a network from JunosE Release 10.3.3 to Release 11.2.x on a router that contains ES2 4G LMs and is configured with MPLS applications (L3VPNs, L2VPNs, and VPLS), all the ES2 4G LMs reset after the upgrade is completed. [Defect ID 189178]