JunosE 13.1.0 Release Notes

Resolved Known Problems

Release 13.1.0 is based on Release 13.0.0 and incorporates all problem resolutions found in that release. The following problems were reported open in Release 13.0.0 and have been resolved in this release, or have been resolved since the 13.0.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.

Forwarding

• An ES2 10G LM resets when you attempt to remove a multicast port in a dual-stack environment that contains both IPv4 and IPv6 subscribers. [Defect ID 189867]

Policy Management

• Although a carriage return, <cr>, is displayed when a question mark (?) is typed after entering the vlan classifier list classifierName command without defining any other keyword or CLACL option, an error message is displayed stating that a VLAN classifier list cannot be configured without any classification criteria when Enter is entered to configure the VLAN CLACL with only the name. [Defect ID 184139]
• If you modify the reference-rate policy-parameter, by using either the policy-parameter reference-rate command at the interface level or the global level or the RADIUS-initiated change-of-authorization (CoA) method, for rate-limit profiles that are used in internal parent groups, the modified rate-limit profile is not considered during the forwarding of traffic on ES2 10G LMs, ES2 10G Uplink LMs, and ES2 10G ADV LMs. The old, stale rate-limit profile is used for forwarding of traffic. This problem occurs with both IPv4 and IPv6 traffic. This behavior is not observed with ES2 4G LMs. [Defect ID 185409]

In such a scenario, although the updated reference-rate policy-parameter value is reflected in the output of the show ip interface and show ipv6 interface commands, the modified reference-rate is not used for processing of forwarded traffic.

• After a stateful SRP switchover on a router acting as an SRC client, provisioning of polices from the COPS server to the SRC client fails. The default output policy configured on the COPS server is not properly applied to users logged in before the stateful switchover. Also, the defined service policies on the COPS server are not applied to new users logging in after the default output policy is configured. [Defect ID 92919]