Resolved Known Problems
Release 6.1.0 is based on Release 6.0.1 and incorporates all problem resolutions found in that release. The following problems were reported open in Release 6.0.0 and have been resolved in this release, or have been resolved since the 6.0.1 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.
Documentation
- Errors in the Securing L2TP and IP Tunnels with IPSec chapter of the JUNOSe Routing Protocols Configuration Guide, Vol. 1.
In the L2TP/IPSec Tunnels section, the second paragraph of the NAT Passthrough Mode subsection incorrectly refers to the router not generating UDP checksums. In IPSec, the router does not control the generation of UDP checksums.
In the Monitoring DVMRP/IPSec, GRE/IPSec, and L2TP/IPSec Tunnels section, the System Event Logs subsection incorrectly lists isVoice as the name of the system event log. The correct system event log name is itm—IPSec transport mode.
- The JUNOSe Physical Layer Configuration Guide and the JUNOSe Link Layer Configuration Guide both incorrectly state that the GE-2 line module and GE-2 APS I/O module combination supports S-VLAN oversubscription. This module combination will support S-VLAN oversubscription in a later release.
- The TSMs, SMs, and Dynamic Tunnel-Server Ports section and the ISMs section in the JUNOSe Physical Layer Configuration Guide, Chapter 9, Managing Tunnel-Service and IPSec-Service Interfaces both incorrectly state that when you have installed multiple modules at the same time, the router distributes tunnel-service interfaces evenly over the modules.
Instead, the router automatically distributes the tunnel-service interfaces over the modules in proportion to the available tunnel-service interfaces.
Packet Mirroring
- In a scenario where an L2TP LAC assigns LAC secure policies to PPP subscribers coming in on a DS3-ATM module, the module resets if aal5mux IP encapsulation is used. This problem is not present ifaal5snap encapsulation is used. [Defect ID 62022]
Policy Management
- Policies with more than 100 empty classifier groups can cause the SRP module to reset when that policy is attached to an interface. An empty classifier group is defined as a classifier group with no action defined. Typically this is the result of an incorrect configuration. [Defect ID 62342]
QoS
- Line modules reset if you remove the shared shaping rate from a scheduler profile that is being referenced on that module. For example, the line module resets if you do all of the following: [Defect ID 62075]
- Configure a shared shaper on the best-effort node for a logical interface in one scheduler profile.
- Configure a shared shaper on the best-effort queue for the same logical interface in a different scheduler profile.
- Configure the no shared-shaping-rate command in either of these scheduler profiles.
SDX
- If you are using the SDX software to manage E-series routers running JUNOSe 6.0.x, contact Juniper Networks for the latest information on this combination. See How to Request Support for contact details. [Defect ID 61338]
SNMP
SONET
- The Unavailable seconds counter erroneously displays a very large number when you issue the show sonet controller command for an OC12 POS module. [Defect ID 62700]
SSH
Stateful SRP Switchover (High Availability) and IP Tunnels
- When high availability is enabled, if the SRP module switches over while the slot erase command is executing, the slot that is being erased comes up in the administratively disabled state on the newly active SRP module. [Defect ID 53397]
Subscriber Manager