|
|
Resolved Known Problems
Release 13.2.0 is based on Release 13.1.0 and incorporates all problem resolutions found in that release. The following problems were reported open in Release 13.1.0 and have been resolved in this release, or have been resolved since the 13.1.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
- On an E120 or E320 router that is running JunosE Release 11.2.1, the ES2 10G LM with an ES2-S2 10 GE PR IOA stops egress forwarding because of an egress IXP static RAM (SRAM) parity error. This problem is observed during the removal of the LM from its slot and reinsertion into the same slot when subscriber sessions are established. This behavior also happens when about 6000 subscribers are brought up and user traffic is transmitted. This problem depends on the type of user traffic sent. [Defect ID 189846]
- In a scaled environment, with approximately 25,000 L2TP subscriber sessions established over the tunnel, if you perform a unified ISSU operation to JunosE Release 13.0.0 or higher-numbered releases on the LAC device, some (a few tens to hundreds) of the subscriber sessions are disconnected. This problem occurs when you modify or set the L2TP destruct timeout value to be less than or equal to 30 seconds on the LAC device. [Defect ID 191413]
Work-around: To prevent the termination of such subscriber sessions, configure the maximum time period for which the router maintains dynamic tunnels after they have been destroyed to be 2000 seconds on both the LAC and LNS devices by using the l2tp destruct-timeout seconds command.
IS-IS
- If you configure a loopback interface as an IS-IS passive interface to cause only the IP address associated with it to be advertised in its link-state PDUs and to not send or receive IS-IS packets from the interface, delete the IP address assigned to the interface, and re-add the IP address, the IP prefixes are not advertised in the link-state PDUs. However, this problem does not occur for IS-IS passive interfaces that are not configured as loopback interfaces. [Defect ID 191441]
Work-around: To correct this problem for all loopback interfaces that are configured as IS-IS passive interfaces, after you delete and re-add the IP address associated with the interface using the ip address command in Interface Configuration mode, enter the passive-interface loopback command in Router Configuration mode to enable its IP prefixes to be advertised in the link-state PDUs.
RSVP-TE
|
Copyright © 2012, Juniper Networks, Inc. Report An Error |
|
|