JUNOSe 10.2.1 Release Notes > Release 10.2.1 > Resolved Known Problems

Resolved Known Problems

Release 10.2.1 is based on the 10-2-0p0-3 patch release and incorporates all problem resolutions found in that release. For information about resolved problems in a patch release, customers with valid service agreements may log in to the JUNOSe Download Software page on the Customer Support Center Web site at https://www.juniper.net/support/csc/swdist-erx/. Select the Patch Release History for the JUNOSe release you are interested in.

The following problems were reported open in Release 10.2.0 and have been resolved in this release, or have been resolved since the 10-2-0p0-3 patch 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.

ATM

• The line module resets when you issue the show nbma arp command after you have configured NBMA interfaces on an ATM line module. [Defect ID 178031/88491]
• The atm vp-tunnel 1 cbr command provides incorrect rate range for CBR service category on an ATM data PVC. [Defect ID 89387]

BGP

• The IPv6 neighbor configuration under address family IPv6 is activated without explicitly activating it. [Defect ID 181028]

BGP/MPLS VPNs

• When the stale MPLS forwarding state is flushed after a BGP graceful restart on a warm SRP switchover, BGP/MPLS VPN traffic suffers a one-time loss of traffic for about 350 ms. [Defect ID 74391]

CLI

• After creating a secure classifier list, the CLI session stops operating when executing a show classifier-list command. [Defect ID 86165]

DHCP

• When you erroneously configure DHCP capture on a nonexistent interface, the router does not generate an error message and the capture-enabled interface count is increased. The interface also appears in the output of the show ip interface brief command. If you subsequently try to disable DHCP capture on that interface, the operation fails and the router generates an error message indicating that the specified interface is invalid. The capture-enabled interface count remains unchanged. [Defect ID 177014]

DHCP External Server

• The show ip dhcp-external bindings records wrong server among 2 configured. [Defect ID 87813]

DHCP Server

• When configuring an IP DHCP local pool without specifying the lease time, the lease time will default to 2 minutes. [Defect ID 84572]

DoS

• DoS-protection-group configuration for IpLocalLspPing is not working as expected. [Defect ID 88877]

Ethernet

• The ES2 10G LM module resets when you reconfigure a LAG interface and its upper layer. [Defect ID 178047]
• Dynamic PPPoE subscriber's VLAN subinterface remained in Down state due to overrideAutoDetection functionality. [Defect ID 89280]
• GE-HDE reset in c2QosAgentLag.cc line: 2401 task: scheduler. [Defect ID 89547]
• In the Gigabit Ethernet line modules, the CPU usage increase after upgrade to 9.1.2 due to ISSU changes. [Defect ID 89846]
• When you remove the IP address of a LAG bundle on an ES2 10G LM or an ES2 10G ADV LM, which is configured with a Gigabit Ethernet physical interface as the member interface and assigned an IP address and subnet mask, the line module resets during the time of deletion of the IP address. This problem occurs if you enabled a VRRP instance identifier (VRID), assigned an IP address with the VRID, and configured the VRRP advertisement interval time for the LAG bundle. [Defect ID 181116]

File System

• LM10 reset at : aptationLayer.cc, line: 13954, lr->Hw2IpAdaptationLayer::setOutputLowerL2PolicyCodeBranch. [Defect ID 89716]

Forwarding

• The E series router sends transit packets having unordered sequence numbers through the GRE tunnel. [Defect ID 89518]
• Packets with router alert IP option configured are sent to SRP though the source addresses in the packets are not local and the associated protocol is disabled. [Defect ID 88859]
• Few COA-ACK packets sent from the ERX router are missing under control-plane load. [Defect ID 89788]

Hardware

• ES2 10G LM reset with panic task: scheduler file: ic1Detector.cc egressIxpMePanics: 134217728. [Defect ID 88253]
• ES2 10G LM reset with panic arg (0x40432f) file: aptationLayer.cc line: 7946 task: scheduler. [Defect ID 89231]
• show configuration commands disappear when removing hardware. [Defect ID 89679]
• Memory leak on E-Series line modules in application os:ICC. [Defect ID 89747]
• The ERX router did not respond to ingress L2TP control packets during warm-restart. [Defect ID 89751]
• Implement credit based mechansim for Global recirculation SRA panic. [Defect ID 89877]

IP

• An snmpWalk to the mplsFTNStdMIB becomes very slow and can time out on a router that has a large number of policies attached to interfaces with many IP or IPv6 routes. [Defect ID 178838]
• When you issue the show configuration command the SRP module stops working with the error: ip_Ctrl_19B reset type: processor exception 0x68616c74 (halt). [Defect ID 89303]

IPv6

• When an IPv6 client that is connected to the requesting router using a PPP link is delegated a prefix by the DHCPv6 server, the client binding is not removed when the PPP session terminates and is retained until the lease time expires. As a result, when the same PPP client logs in again and sends a DHCPv6 SOLICIT request to the DHCPv6 server, the SOLICIT request is ignored if the prefix or the local address pool returned by the RADIUS server is different from the prefix or pool that was returned by the RADIUS server for the previous login session, and the existing binding is retained untouched. If RADIUS returns the same prefix or pool information as the previous login session, the DHCPv6 advertise message is returned to the client. This behavior is expected and occurs because the DHCPv6 server does not create a new client binding until the old binding is removed when the lease time expires. [Defect 182020]

IS-IS

• 'ldpGeneral:rsLdpTopologyDriven.cc:519:addRoute:a.b.c.d not found' severity level is incorrectly set to NOTICE [Defect ID 89882]
• The multiple ERX routers failed to invalidate the next-hop for iBGP Next-hops [Defect ID 89930]

L2TP

• L2TP over MPLS is not supported for the ES2 10G ADV LM. L2TP over MPLS is supported for the ES2 4G LM, ES2 10G Uplink LM, and ES2 10G LM in all possible module combinations. [Defect ID 85608]
• Inclusion of the Error-code field in Result Error Code attribute value pair (AVP) in L2TP Call-Disconnect-Notify (CDN) messages. [Defect ID 89579]
• session-out-of-resource-result-code-override result code. [Defect ID 89825]

MLD

• The E Series router does not log a warning when it receives an MLDv1 query but is not configured to use MLDv1 on the interface. [Defect ID 46064]

MPLS

• When both LDP and RSVP-TE routes are available to the same prefix and these routes have the same administrative distance, the LDP route is always selected as the best route. [Defect ID 83096]
• Packet forwarding not working for "forward next-hop: policy to MPLS next hop due to RLI 4254. [Defect ID 89437]

Multicast

• Reoptimization of routes with fast reroute does not happen after a failure unless you have configured a path option. [Defect ID 44317]

Packet Mirroring

• Packet mirroring is not supported on OCx/STMx ATM modules on E Series routers when both of the following are true: [Defect ID 88038]

• The L2TP session comes from an AAL5Mux PVC.
• The LNS is reachable by means of an MPLS next hop.

PPPoE

• The show pppoe interface displays "% Software error: cannot get interface characteristics of PPPoE interface (unknown interfa." [Defect ID 84114]
• acct-terminate-code need to differentiate session down due to client PADT & link down. [Defect ID 84331]
• Windows Vista PPPoE client cannot bind IPv6 address through SLAAC in dual-stack mode with 9.x.x and 10.x.x JUNOSe software [Defect ID 89378]

RSVP-TE

• Few RSVP LSP can be inactive after network churn. [Defect ID 89616]
• Reset with processor exception 0x300 (data access: protection violation (read attempt)) task: rsvp_msgQueue_1. [Defect ID 89048]

SNMP

• When you perform an snmpWalk on the virtual router, regardless of whether IS-IS is configured, CPU utilization on the SRP module stays at 100 percent for a few minutes. [Defect ID 183131]

SRC Software and SDX Software

• The show configuration output has display issues that cause errors when configuring router from saved .scr file. [Defect ID 89449]
• Plugin initialization order causing invalid reference counts on the address mode indication of the interface. [Defect ID 89832]

SRP Redundancy

• Any discrepancy in /ftp directories between the primary SRP module and the redundant (standby) SRP module in the router causes the file synchronization process to fail. The synchronization process completes, but the file systems are not synchronized.

This issue occurs when the /ftp directories do not exist at all on the primary SRP module, but partially exist on the standby SRP module. The discrepancy in /ftp directories is unexpected because the /ftp directories should always exist on the SRP modules regardless of the state of the FTP server. Because the synchronization process cannot handle the /ftp directories recursively, it must first handle all subdirectories and files in each /ftp directory before it can handle the /ftp directory itself. As a result, the synchronization process fails to synchronize the /ftp directories between the SRP modules. [Defect ID 177812]

Unified ISSU

• When L2TP is configured to use the silent failover method for peer resynchronization and the tunnel endpoints are reachable using an IGP distributed route, unified ISSU fails if the IGP reconvergence time exceeds the maximum retransmission retry time for L2TP. [Defect ID 180769]
• When you perform an snmpWalk on the virtual router, regardless of whether IS-IS is configured, CPU utilization on the SRP module stays at 100 percent for a few minutes. [Defect ID 183131]