Previous Releases

8.3R3

The following issues have been resolved since JUNOS Release 8.3R2. The identifier following the description is the tracking number in our bug database.

Platform and Infrastructure

• On M-series and J-series routing platforms, when you include the vrf-table-label statement at the [edit routing-instances routing-instance-name] hierarchy level, the incoming traffic is considered to come from the internal label-switched interface (LSI) associated with the VRF instance. The original incoming logical interface is unknown, so the traffic is not accounted for by the original incoming logical unit. Furthermore, the LSI is an internal interface and has no accounting support. [PR/53148: This issue has been resolved.]
• If you enable the copy-PLP and filter-class features simultaneously, an unusable topology might be installed in the Packet Forwarding Engine, and control traffic might not be handled properly by the system. As a workaround, disable either the copy-PLP or the filter-class feature. [PR/62511: This issue has been resolved.]
• When you configure port mirroring, the Packet Forwarding Engine might not handle memory properly, which causes it to lose connection with the Routing Engine and then reboot. [PR/76668: This issue has been resolved.]
• Messages like the following might appear in the system log, indicating that the system clock went backward by 1 microsecond: “check_kernel_exec_time: microuptime() went backwards(<seconds>.<microseconds> -> <seconds>.<microseconds>-1).” There is no operational effect. [PR/77411: This issue has been resolved.]
• On M20 routers, if you take an FPC offline, extract a PIC, reinsert the PIC, and attempt to bring the FPC online, the online operation might fail, the System and Switching Board (SSB) might dump core, and the router might reboot automatically. [PR/78988: This issue has been resolved.]
• The show pfe fpc and show pfe feb commands might fail to produce output and instead display the message “error: Unrecognized command.” [PR/97014: This issue has been resolved.]
• SRAM memory testing failed on System Control Board (SCB) platforms because the written value and read value are not the same at one specific address in SRAM. [PR/97066: This issue has been resolved.]
• On a router with VPLS enabled, the indirect-next-hop statement is not supported at the [edit routing-options forwarding-table] hierarchy level. [PR/97070: This issue has been resolved.]
• If you enable the Virtual Router Redundancy Protocol (VRRP) in a routing matrix, the T640 routing nodes might generate core files and stop functioning. [PR/104673: This issue has been resolved.]
• On a backup Routing Engine, the following error message might appear in the log file: “rt_rpf_info_update_work: Replicate got iflist 0 nhlist 0 allocated iflist 8.” It is caused by the interface list not replicating properly when a new next hop is added. [PR/227833: This issue has been resolved.]
• On OC768 PICs installed in Type 4 FPCs, if the routing platform experiences heavy, bursty traffic conditions, almost all traffic going through one queue might be dropped by the random early detection (RED) algorithm. As a workaround, reboot the FPC. [PR/228909: This issue has been resolved.]
• If tricolor marking is configured on an interface and the interface is repeatedly disabled and enabled, memory that has been allocated might not be released properly. [PR/232472: This issue has been resolved.]
• On J-series Services Routers configured with an IPSec tunnel, when you disable the loopback interface, OSPF randomly chooses a router ID and sends a routing update to the remote router using the IPSec tunnel endpoint, causing the packet to loop. Traffic forwarding stops and a core file is generated. As a workaround, prevent looping by including the router-id statement at the [edit routing-options] hierarchy level on both routers. [PR/233271: This issue has been resolved.]
• If there are large numbers of routes and next hops, the MultiServices PIC might not be able to allocate enough memory to install all of them into its internal database. [PR/235368: This issue has been resolved.]
• If a routing platform uses an aggregated Ethernet interface as the only Internal Gateway Protocol (IGP) facing interface and has many external peering sessions on other interfaces not traversing the aggregated Ethernet interface, when the aggregated Ethernet interface goes down and up several times, the memory buffer of the routing platform might overflow. This can cause a switchover to the backup Routing Engine (on dual Routing Engine platforms) or cause the Routing Engine to become unreachable (on single Routing Engine platforms). [PR/236258: This issue has been resolved.]
• When show interfaces commands are run from the PIC console on Adaptive Services or MultiServices PICs with redundant LSQ configuration, the PICs might restart unexpectedly. [PR/237156: This issue has been resolved.]
• If you configure a large number of MD5 authentication keys for BGP sessions, and then deactivate and reactivate the keys, the router might generate a commit error and MD5 authentication might not be applied on some of the BGP sessions. [PR/237690: This issue has been resolved.]
• Unrestricted proxy Address Resolution Protocol (ARP) was not working correctly. [PR/237985: This issue has been resolved.]
• If the router receives a request to create a ping MIB row by using the createAndGo method, the rmopd process might produce a segmentation fault. [PR/251555: This issue has been resolved.]

User Interface and Configuration

• If the configuration includes a commit script that uses the jcs:invoke routine, the router fails to boot successfully. [PR/95960: This issue has been resolved.]
• After a Routing Engine switchover, an erroneous EVENTD_POLICY_ENTRY_NOT_FOUND message might be logged. [PR/99561: This issue has been resolved.]
• If you include the traceoptions statement in a configuration that also includes the apply-groups statement, the JUNOS software process responsible for generating the trace might generate a core file and stop functioning. The process might continue to malfunction when restarted. [PR/101491: This issue has been resolved.]
• When you activate and deactivate VRF routing instances, the routing protocol process might generate a core file and stop operating. [PR/102088: This issue has been resolved.]
• During reboot of the router, the previously active configuration is automatically committed. If the commit operation does not completely succeed and you then issue the show configuration command, the JUNOS management process (mgd) generates a core file and stops functioning. [PR/102442: This issue has been resolved.]
• Change in Daylight Saving Time (DST) from normal user mode does not synchronize immediately after configuration. [PR/103724: This issue has been resolved.]
• JUNOScope user passwords were previously limited to a maximum of 48 characters. They can now be a minimum of 6 characters and a maximum of 128 characters. [PR/105151: This issue has been resolved.]
• If you configure a user login class containing deny commands, and the regular expression that is used to define which commands are denied includes a top-level statement or command (such as configure), the user might still be able to gain access to the statement or command. [PR/228617: This issue has been resolved.]
• In JUNOS 8.2 and later releases, user permissions are sometimes not calculated correctly. As a result, users might not be able to perform actions for which they have the required permission. [PR/229424: This issue has been resolved.]
• If you upgrade a TX Matrix platform to JUNOS Release 8.4, the following error message might be generated: “corruption lcc0-master lcc0-fpc0 PFEMAN: trying master connection, attempt 140.” Although this message indicates a delay in synchronizing the configuration files between chassis components, the synchronization eventually succeeds within 5 minutes. [PR/229857: This issue has been resolved.]
• If the system log host is configured and you commit a configuration change to the event process, an event policy execution causes the child event process to freeze. A subsequent commit operation to the event process causes the main event process to fail. The child event process remains active. [PR/230064: This issue has been resolved.]
• When JUNOScope is installed on Linux machines that have more than the minimum specified RAM size (1 GB), the JUNOScope server might not start because of the high JVM (Java Virtual Machine) heap size value specified for JUNOScope startup. For Linux, the JVM heap size value depends on the total physical memory available in the machine and increases with an increase in total physical memory.

  To resolve this issue, JVM heap size has been made a JUNOScope installation parameter and a new prompt that asks you to enter the value for the JVM heap size has been added during the JUNOScope installation. The default and minimum value of the JVM heap size specified during installation is 675 MB. You can specify a higher JVM heap size value for better performance, but a very high JVM heap size might impede startup. [PR/230376: This issue has been resolved.]

• When you reference apply groups in a routing instance and attempt to commit the configuration, the commit operation might fail and cause foreign file propagation (ffp) and management process (mgd) core dumps. [PR/233470: This issue has been resolved.]
• If the event process (eventd) receives corrupted data from another process, it might generate a core file. [PR/236599: This issue has been resolved.]
• When a secondary path is added to a label-switched path, the commit might trigger a core dump. This occurs when MPLS fails to find a matching next hop for the added path, but continues to operate on an invalid next hop template. [PR/251288: This issue has been resolved.]
• Users configured to have permission all do not have all the permissions. [PR/251722: This issue has been resolved.]

Interfaces and Chassis

• A PL4 bus error can occur during reboot or shutdown. DIP4 errors can occur during reboot or shutdown without affecting the normal operation of the router, as long as the errors do not persist. [PR/43787: This issue has been resolved.]
• On Channelized STM1 PICs, a tributary unit alarm indication signal (TU-AIS) alarm enabled for one channel might cause another channel to shut down. [PR/55357: This issue has been resolved.]
• When an Ethernet PIC operating in cut-through mode receives a packet without a destination MAC address, the output of the show interfaces interface-name extensive command might include incorrect values. This event correctly increments the value in the Input DA rejects output field, but incorrectly also increments the value in the L3 incompletes field. [PR/56750: This issue has been resolved.]
• When you manually disable the active Automatic Protection Switching (APS) interface to switch between the working and protect circuits, APS might not function properly. [PR/71083: This issue has been resolved.]
• If you modify a time slot on a member link of a redundant link services (rlsq-) interface bundle when the Routing Engine is unusually busy (because of route flaps, for example), that particular member link might stop forwarding traffic. [PR/78591: This issue has been resolved.]
• When the router is upgraded to JUNOS Release 8.0 or later, the default framing method of DS0 changes automatically from ESF to SF. [PR/97277: This issue has been resolved.]
• With JUNOS Release 8.0 or later, some XENPAK transceivers might report spurious temperature, laser bias, laser output, and receive optical power alarms that are cleared again after about 10 seconds. There is no operational impact. [PR/98428: This issue has been resolved.]
• When interchassis Automatic Protection Switching (APS) is configured with channelized OC12 PICs and the working circuit fails, it takes longer than expected to fail over to the protect circuit. [PR/98488: This issue has been resolved.]
• If you clear IPv6 statistics, deactivate IPv6 route accounting at the [edit forwarding-options family inet6 route-accounting] hierarchy level, and resume IPv6 traffic across an interface, the Input bytes and Input packets fields in the output of the show interfaces extensive command might show incorrect values. [PR/99461: This issue has been resolved.]
• On J-series Services Routers, configuring more than one VRRP group on a port puts the port into promiscuous mode. Forwarding performance can be affected and duplicate ICMP messages might be sent in response to the ping command. This problem applies to 1-port Gigabit Ethernet ePIMs on all J-series platforms, and built-in Gigabit Ethernet interfaces on the J4350 and J6350 Services Routers. [PR/99796: This issue has been resolved.]
• When a large number of packets traverses a GRE-over-IPSec tunnel that has a J4350 Services Router with a Crypto Accelerator Module as one of its endpoints, the Services Router might stop forwarding traffic. [PR/101337: This issue has been resolved.]
• When graceful Routing Engine switchover is configured and a switchover occurs, the kernel might reset and generate a core file. [PR/101359: This issue has been resolved.]
• IQ2 egress queued packet counters were not available because of a hardware limitation. An approximation of the queued counters is now calculated by the software from queue depth, assuming that one frame buffer holds one packet. When very large packets are enqueued, the queued packets (and queued bytes in some cases) counter is an overestimate of the actual values. Note: this overestimation is present only when the traffic is transiting; if the traffic is stopped, the counters are accurate. [PR/103077: This issue has been resolved.]
• On SONET/SDH and ATM interfaces, in some cases interface monitoring can cause a bad page fault due to a race condition. [PR/103589: This issue has been resolved.]
• On an M120 routing platform, if you take an Ethernet IQ PIC offline and traffic is received on the PIC interface, it might not be possible to bring it back online. To recover, you need to restart the Forwarding Engine Board (FEB) connected to the FPC where the Ethernet IQ PIC is installed. [PR/104762: This issue has been resolved.]
• If a member link in an aggregated Ethernet interface becomes inoperative, multicast packets might not be routed through other member links. [PR/105136: This issue has been resolved.]
• When a switchover event occurs on a routing platform with a configuration that includes a large number of IPv6 routing instances, the Routing Engine that was previously the master might not be able to synchronize with the kernel database. [PR/105268: This issue has been resolved.]
• The delay between VRRP advertisements might be longer than the value specified by the fast-interval statement at the [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-group group-number] hierarchy level. [PR/105436: This issue has been resolved.]
• On the 10-Gigabit Ethernet IQ2 PIC, the default weighted random early detection (WRED) profile is incorrect, causing incorrect RED handling on queue 0. [PR/228742: This issue has been resolved.]
• When you issue the monitor interface command for an OC768 PIC running at line rate, the byte count and bps rate values are longer than the space allotted for them, which causes the delta value to appear on the line below instead of the same line. [PR/229494: This issue has been resolved.]
• When an aggregated interface child link is brought down at the remote side of a bundle, the multicast packet or byte traffic rate at the local end retains a stale value. [PR/229605: This issue has been resolved.]
• On Channelized OC12 intelligent queuing (IQ) interfaces, the output-traffic-control-profile statement at the [edit class-of-service interfaces interface-name] hierarchy level is not supported. [PR/229880: This issue has been resolved.]
• When you issue the show interfaces command for physical interfaces on a Channelized IQ PIC, the value in the Last flapped field of the output might not be consistent for related interfaces. [PR/230248: This issue has been resolved.]
• When scheduler maps are applied to more than one interface, the interface process (dcd) might not release memory that it has allocated. [PR/230770: This issue has been resolved.]
• If configuration for an interface is defined in both an internal system file and the JUNOS configuration, an internal database maintained by the interface process (dcd) might include invalid pointers. When the process tries to free the pointers, it generates a core file. [PR/231145: This issue has been resolved.]
• When graceful restart is configured for routing protocols on a TX Matrix router, multicast routing might fail when a member link of an aggregated Ethernet interface is taken down. [PR/231772: This issue has been resolved.]
• On T640 and M320 routing platforms, if you configure link services IQ (LSQ) services and a link PIC to provide links to the LSQ bundles, when the FPC that houses the link PIC is taken offline, the show interfaces command might display invalid statistics for interfaces on the PIC. [PR/234521: This issue has been resolved.]
• When you add an interface configuration to a deactivated hierarchy, the link fault management process might fail and then roll back the configuration. [PR/234753: This issue has been resolved.]
• On a Channelized DS3 IQ PIC with loopback enabled for CT1 or T1 interfaces in a bundle, if you use the configuration mode copy command to create a new interface in the bundle based on one of the existing interfaces, the new interface does not come online until the PIC resets. [PR/235228: This issue has been resolved.]
• Adding or deleting a T1 member link causes one to two packets to drop on unrelated multilink PPP interfaces. [PR/236014: This issue has been resolved.]
• If you use an ATM2 Intelligent Queuing (IQ) interface as the protect circuit of an Automatic Protection Switching (APS) connection and a graceful Routing Engine switchover (GRES) event occurs, the logical interface might be marked as hardware down rather than device down. If an APS circuit switchover happens after the GRES switchover, the ATM2 IQ interface does not clear the aps_disable flag, and traffic loss might occur on the connection. [PR/236610: This issue has been resolved.]
• When IPv6 route accounting is configured on a TX Matrix platform (by including the route-accounting statement at the [edit forwarding options family inet6] hierarchy level), the configuration is not copied to the T640 routing nodes in the matrix. As a result, the fields in the IPv6 transit statistics section of the output from the show interfaces command do not increment. [PR/237054: This issue has been resolved.]
• When a graceful Routing Engine switchover occurs and a member link of an aggregated Ethernet interface is taken offline, multicast traffic might not be rerouted through other member links as expected. [PR/237098: This issue has been resolved.]
• For link services IQ (LSQ) interfaces configured on AS PICs or MultiServices PICs, if you try to include the unit 1023 statement at the [edit interfaces lsq-fpc/pic/port] hierarchy level and then commit the configuration, you might receive the following error message: “ifl number: linkservice pic unit number out of range (0 to 1023).” [PR/237983: This issue has been resolved.]
• If you apply more than one class-of-service rewrite rule to interfaces on an IQ2 PIC, only the first rule works correctly on all interfaces. [PR/238250: This issue has been resolved.]
• When you delete a VLAN, the IEEE 8021p rewrite map is deleted from the IQ PIC even if the same map is being used by other VLANs. [PR/252869: This issue has been resolved.]

Services Applications

• If initiator and response packets for TCP flows arrive at nearly the same time, the Adaptive Services PIC might generate a core file and stop functioning. [PR/94388: This issue has been resolved.]
• If a large number of flows expire in a short period of time, the Adaptive Services PIC might generate a core file and stop functioning. [PR/101117: This issue has been resolved.]
• When you configure a Session Initiation Protocol (SIP) application-level gateway (ALG) on an AS PIC, the PIC might stop operating and generate a core file. [PR/103973: This issue has been resolved.]
• Export packets generated by flow aggregation version 9 might use zero for the number of packets and bytes for a flow. [PR/105589: This issue has been resolved.]
• If you perform numerous commit operations, the key management process (kmd) might generate a core file and stop operating because of an incorrect memory allocation procedure. [PR/232085: This issue has been resolved.]
• When multiple Layer 2 Tunneling Protocol (L2TP) tunnels from different tunnel groups are being set up simultaneously, the same tunnel identifier might be assigned to more than one tunnel and some tunnel attributes might be assigned to the wrong L2TP session. As a workaround, issue the clear services l2tp tunnel command to clear the L2TP tunnels. [PR/233184: This issue has been resolved.]
• When a lot of PFEMAN messages must be processed by the meta-db toolkit, the AS PIC might restart unexpectedly. [PR/235654: This issue has been resolved.]

General Routing

• When an interface is configured with more than one IP address in the same subnet, the routing process might restart unexpectedly. [PR/99396: This issue has been resolved.]
• A configured prefix list that contains only inactive prefixes is rejected with a policy error. [PR/237205: This issue has been resolved.]
• When a prefix list is empty, the router software attempts to merge it with other prefix lists. This action erroneously causes the configuration check to fail. If the software attempts to merge two prefix lists with different address families, an error message is logged. [PR/237457: This issue has been resolved.]

Routing Protocols

• For JUNOS releases in which nonstop routing for multicast protocols is not supported, multicast routing options are ignored on the backup Routing Engine. [PR/70771: This issue has been resolved.]
• An error in handling interface information when a Routing Engine assumes mastership might cause the routing protocol process (rpd) to generate a core file and stop operating. [PR/105705: This issue has been resolved.]
• If you configure Bidirectional Forwarding Detection (BFD) for a static route in a separate routing table group and associate it with an interface, the output of the show bfd session command might show the BFD session as AdminDown and the BFD session might not become established. [PR/105780: This issue has been resolved.]
• When route reflection is configured in Layer 3 VPN networks along with label aggregation, label aggregation does not work properly. [PR/228039: This issue has been resolved.]
• When an OSPF area border router (ABR) receives two or more summary link-state advertisements (LSAs) that have the same identifier but different prefix lengths, the routing protocol process (rpd) might stop operating. [PR/230127: This issue has been resolved.]
• If a policy with a community delete action deletes all communities, the routing process will leak memory. [PR/230207: This issue has been resolved.]
• When multiple MPLS LSPs are configured, the mplsTunnelReoptimized trap is triggered on every expiration of the value set for the optimize-timer statement at the [edit protocols mpls label-switched-path path-name] hierarchy level. In addition, the no-trap statement set at the [edit protocols mpls log-updown] hierarchy level does not block the traps defined in RFC 3812, Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB). [PR/231678: This issue has been resolved.]
• When the upstream interface toward the rendezvous point (RP) becomes unavailable for a *,G entry that is receiving data on the rendezvous-point tree, the routing protocol process (rpd) might stop. [PR/231876: This issue has been resolved.]
• Configuring a PIM bootstrap export policy (by including the export statement at the [edit protocols pim rp bootstrap family family-name] hierarchy level) has no effect. PIM bootstrap import policies work as expected. [PR/232200: This issue has been resolved.]
• If a local route is imported from another routing instance, it might not be installed into the forwarding table. A message like the following might appear in the system log: “<timestamp> <router> rpd[<PID>]: KRT ADD for 10.10.10.10/32 => { ifl <interface-index> addr 10.10.10.10 } failed, error "ENOENT -- Item not found".” [PR/234918: This issue has been resolved.]
• Continuous flapping of ATM virtual circuits might trigger a race condition that could cause the routing protocol process (rpd) to restart unexpectedly. [PR/252422: This issue has been resolved.]

MPLS Applications

• After the show mpls lsp extensive command is issued, the routing process might log messages reporting that there was a scheduler slip and BGP sessions might be disrupted. [PR/104179: This issue has been resolved.]
• If one or more logical routers are configured, MPLS graceful restart might not function in the main routing protocol process (rpd). [PR/228195: This issue has been resolved.]
• The router might begin to receive LDP hellos and start to establish an LDP adjacency even if the interface is not fully operational. [PR/228298: This issue has been resolved.]
• If the configuration for an LSP includes more than 16 equal-cost multipaths (ECMPs), RSVP might not function correctly. [PR/228338: This issue has been resolved.]
• If an LDP adjacency times out while a router is acting as helper for another router that is undergoing LDP graceful restart, the graceful restart might not complete successfully. [PR/229848: This issue has been resolved.]
• When RSVP PATH messages are sent, the session name includes extra characters. Per RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels, the session name should instead be padded with trailing NULL characters. [PR/232926: This issue has been resolved.]
• When RSVP aggregation is negotiated on a point-to-point link, RSVP PATH messages are not bundled. [PR/234545: This issue has been resolved.]
• The mplsLspPathUp and mplsLspPathDown SNMP traps are enabled when either or both of the (syslog|no-syslog) and (trap|no-trap) statements are included at the [edit protocols mpls log-updown] hierarchy level. The correct behavior is for the traps to be enabled only when the trap-path-down and trap-path-up statements are included. [PR/237464: This issue has been resolved.]
• RSVP packets with the router alert (RA) option that are received from a customer edge (CE) router in a Layer 3 VPN VRF instance are incorrectly forwarded using the forwarding table for the master instance. As a result, Layer 3 VPN customer applications that use RSVP do not work correctly. There is no workaround. [PR/251850: This issue has been resolved.]

Class of Service

• On J-series Services Routers, if you configure a single policy statement that includes both the from community match condition (to match BGP communities) and the then forwarding-class action (to apply a class-of-service forwarding class), the policy might not work and the router might generate the following system log message: “kernel: RT_PFE: RT msg op 12 (Undefined) failed, err 5 (Invalid).” [PR/73885: This issue has been resolved.]
• If you include the scheduler-map statement at the [edit class-of-service interfaces aeX] hierarchy level and a member link of the aggregated Ethernet interface goes down or comes back up, traffic forwarding on the routing platform halts for approximately 400 milliseconds. [PR/102200: This issue has been resolved.]
• When the combination of interface types configured on a channelized IQ PIC requires an amount of memory that exceeds the maximum available, some of the interfaces might not handle traffic correctly. [PR/102932: This issue has been resolved.]
• Some JUNOS processes, including the class-of-service process (cosd), might not correctly release memory that they have allocated. [PR/230771: This issue has been resolved.]

Forwarding and Sampling

• On an M120 router, if the then statement in a firewall filter (at the [edit firewall filter filter-name term term-name] hierarchy level) includes both a policer statement and a count statement, the filter might not handle packets as specified by the configuration. [PR/105465: This issue has been resolved.]

Network Management

• The Management Information Base (MIB) process (mib2d) sometimes generates a core file and logs the message “SNMP_GET_ERROR2: jnxDCUsEntry get-next failed for dcu index/name: index1 <index1> index2 <index2> (Operation timed out).” [PR/228471: This issue has been resolved.]

8.3R2

The following issues have been resolved since JUNOS Release 8.3R1. The identifier following the description is the tracking number in our bug database.

Platform and Infrastructure

• When you issue the show mpls lsp detail command and there is a large amount of data to display, the routing protocol process (rpd) might consume 100 percent of the CPU. [PR/75975: This issue has been resolved.]
• On T-series routing platforms, some MPLS traffic patterns might not load balance correctly. As a workaround, configure the label-2 and label-3 statements in addition to the label-1 statement at the [edit forwarding-options hash-key family mpls] hierarchy level to achieve acceptable load balancing. [PR/76227: This issue has been resolved.]
• When a combination of Compressed Real-Time Transport Protocol (CRTP) and link fragmentation and interleaving (LFI) packets are sent over a MultiServices 100 PIC at high rates (greater than 350 kpps total), forwarding of traffic over that PIC might stop. [PR/97304: This issue has been resolved.]
• The output of the show route forwarding destination command is limited to 16 indexed next hops, instead of 16 unique indexed next hops. [PR/98381: This issue has been resolved.]
• When the chassis process (chassisd) is restarted, an erroneous SNMP alarm for power supply failure is logged. [PR/100753: This issue has been resolved.]
• On J-series Services Routers, the event process (eventd) and DHCP process (dhcpd) do not handle file descriptors correctly in certain circumstances, and the chassis process (chassisd) generates a core file and stops operating. [PR/227855: This issue has been resolved.]

User Interface and Configuration

• If a connection from a client to the router is not established through the CLI (in a JUNOScript session, for example), the router never closes the connection if it becomes idle or closes unexpectedly on the client side. [PR/11689: This issue has been resolved.]
• If you delete and then reconfigure an applied configuration group that does not contain any configuration data, the routing protocol process (rpd) might generate a core file and stop operating. [PR/63677: This issue has been resolved.]
• According to RFC 3986, port numbers can be optional in SCP transfer syntax. The JUNOS CLI accepts the syntax with or without using a colon to separate the hostname from the port number, but the UNIX shell requires a colon. The SCP transfer accepts the syntax only if a colon is not used. This fix enables routers to handle “zero digit” port numbers. [PR/66375: This issue has been resolved.]
• When either or both of the allow-command and deny-command statements are included for a login class at the [edit system login class class-name] hierarchy level, users who belong to the class might experience long delays when trying to connect to the router (for example, to start a CLI, JUNOScript, or NETCONF session). [PR/95042: This issue has been resolved.]
• If you configure a user login class containing deny-commands, and the regular expression that is used to define which commands are denied includes a top-level statement or command (such as configure), the user might still be able to gain access to the statement or command. [PR/228617: This issue has been resolved.]

Interfaces and Chassis

• On MPLS networks, even when you include the atm-l2circuit-mode aal5 statement at the [edit chassis fpc fpc-slot pic pic-slot] hierarchy level in the configuration, the CLP and EFCI bits are not carried across a Layer 2 circuit. [PR/31735: This issue has been resolved.]
• In vlan-ccc mode, the multicast source MAC bit filtering allows packets with the multicast source MAC bit to be set and reset when vlan-ccc mode is disabled. [PR/67401: This issue has been resolved.]
• On J-series Services Routers with multilink-frame-relay-uni-nni (FRF.16) encapsulation, when you issue the show interfaces queue command, the kernel returns only the bundle statistics for FRF.16 and does not return the queue statistics; hence the command fails. [PR/69565: This issue has been resolved.]
• If you modify a time slot on a member link of a redundant link services (rlsq-) interface bundle when the Routing Engine is unusually busy (because of route flaps, for example), that particular member link might stop forwarding traffic. [PR/78591: This issue has been resolved.]
• On Gigabit Ethernet IQ PIC interfaces, the show interface extensive command output displays incorrect values for the Total and Unicast packet counters. [PR/81079: This issue has been resolved.]
• An ISDN PRI dialer interface does not properly handle fragmented packets received from an ISDN BRI interface. As a result, some fragmented packets are dropped. [PR/82060: This issue has been resolved.]
• For interfaces on 6-port, 8-port, or 16-port Gigabit Ethernet uPIMs, when the auto-negotiation statement is set to off, the negotiated speed and duplex mode are not displayed. [PR/82061: This issue has been resolved.]
• On Adaptive Services (AS) PICs, if the PIC receives a large amount of traffic, CPU utilization is high, and there are many memory transactions, some components in the PIC might become stuck and stop processing frames. [PR/94287: This issue has been resolved.]
• On M120 routers, if you remove an active Forwarding Engine Board (FEB) from the chassis without taking it offline, traffic might experience delays after FEB switchover. This issue appears only when the interfaces are installed on a Type 3 FPC or OC192 CFPC. [PR/95491: This issue has been resolved.]
• For interfaces on 6-port Gigabit Ethernet uPIMs that have a 1000Base-T SFP module inserted, the link status is sometimes displayed as up and the LED is lit even when there is an invalid configuration or the cable is not connected. [PR/95658: This issue has been resolved.]
• IPv6 counters keep track of transit IPv6 traffic only and are accessible through SNMP reports. IPv6 packets sent from the Routing Engine are not counted by these counters, and IQ2 PICs do not support IPv6 statistics. [PR/96365: This issue has been resolved.]
• When the configuration for APS unidirectional mode is deactivated or deleted, the system might never switch to bidirectional mode, even if that mode is explicitly configured. As a workaround, deactivate APS on both the working and protect circuits and then reactivate it. [PR/96801: This issue has been resolved.]
• When you issue the show interfaces extensive command for an interface on a 10-Gigabit Ethernet PIC that uses XENPAK small form-factor pluggable modules (SFPs), the byte and packet counts in the traffic statistics and MAC statistics sections of the output are incorrect. [PR/96829: This issue has been resolved.]
• On a J4350 Services Router with a Gigabit Ethernet interface, when you toggle the VRRP mastership state, the interface stops forwarding. [PR/97420: This issue has been resolved.]
• For link services intelligent queuing (LSQ) interfaces configured on AS PICs installed in M40e routers, when a graceful Routing Engine switchover (GRES) event occurs, the AS PIC might reboot, PPP keepalives might be lost, and traffic loss might result. [PR/98391: This issue has been resolved.]
• When you configure the Password Authentication Protocol (PAP) on PPPoE over ATM interfaces on a J-series Services Router, PPP sessions with some other routers do not come up, because when PAP is specified as the authentication protocol in LCP configuration requests, a peer router in PAP passive mode expects the J-series Services Router to initiate PAP requests. [PR/99169: This issue has been resolved.]
• When you configure PAP and CHAP on a router and PAP on the other end of the connection on a PPPoE link, the PPP interface status shows the PAP CHAP state as successful but the IPCP state as down, because of an error during LCP negotiation. [PR/99251: This issue has been resolved.]
• During high congestion, 10-Gigabit Ethernet XENPAK PICs might trigger some very confusing messages as a result of packet loss. The fix replaces the error system log messages with counters that indicate the error count for txxg and rxxg interrupt registers. [PR/100022: This issue has been resolved.]
• Immediately after you boot the system or restart the chassis process (chassisd), buffer pool utilization MIB object jnxOperatingBuffer might be erroneously reported as –1. [PR/100170: This issue has been resolved.]
• For link services intelligent queuing (LSQ) interfaces configured on AS PICs, if you configure an FRF.16 bundle that contains the minimum-links statement and then deactivate and reactivate one of the interfaces that is part of the bundle, the other active interfaces might not rejoin the bundle when the modified interface is reactivated and the bundle comes back up. This issue occurs only if there is an explicit configuration change. [PR/101109: This issue has been resolved.]
• If an LSQ bundle goes down because of minimum-link member settings, the QoS bandwidth for the bundle is not applied correctly after the bundle comes back up again. [PR/101119: This issue has been resolved.]
• When Layer 2 Tunneling Protocol (L2TP) sessions that use schedulers are cleared, inappropriate error messages are logged both in the CLI and on the console of the PIC. [PR/102180: This issue has been resolved.]
• When you delete or deactivate an interface on a channelized IQ PIC, the PIC might stop operating and generate a core file. [PR/102420: This issue has been resolved.]
• In certain circumstances, a channelized IQ PIC might generate a core file and stop operating. [PR/103268: This issue has been resolved.]
• When you issue the show interfaces extensive command for an interface on an M-series router that uses ethernet-ccc encapsulation, the values in the Input rate field of the output might be incorrect. [PR/103527: This issue has been resolved.]
• If you configure an interface to be stacked VLAN initially and then change it to flexible VLAN, the management process (dcd) does not register the new change. As a workaround, deactivate and reactivate the interface. [PR/105626: This issue has been resolved.]
• On Channelized OC-12 intelligent queuing (IQ) interfaces, the output-traffic-control-profile statement at the [edit class-of-service interfaces interface-name] hierarchy level is not supported. [PR/229880: This issue has been resolved.]

Services Applications

• If you include the from instance statement in a policy specification, the policy does not match routes installed by the L2TP process (l2tpd) into routing instances. [PR/57488: This issue has been resolved.]
• Because of interoperability issues or network failures or retries, a router might receive an IPCP CONF-REQ message even after IPCP is up. When this happens, the PPP stack transitions from IPCP up to IPCP down. When the CONF-ACK message is finally received, a second IPCP up event occurs. [PR/73334: This issue has been resolved.]
• On Adaptive Services PICs, when you apply class-of-service (CoS) marking and reclassification for the Session Initiation Protocol (SIP) application, voice and video packets might be marked incorrectly in terms of direction, initiator, and responder. [PR/77249: This issue has been resolved.]
• When you configure twice NAT on a router and issue the dir command from an active FTP session, all NAT flows are terminated on the router. [PR/96920: This issue has been resolved.]
• On M120 routing platforms, version 9 flow aggregation using MPLS and MPLS-IPv4 templates does not work for single-label MPLS packets whose route action is label pop (MPLS to IPv4). [PR/100713: This issue has been resolved.]
• When an AS PIC goes offline or restarts, the Internet Key Exchange (IKE) security associations (SAs) that correspond to tunnels configured on the PIC are not cleared. [PR/104710: This issue has been resolved.]
• A reverse route for a remote proxy network that is shared by multiple dynamic end point tunnels might be deleted if any of the tunnels stops functioning. [PR/105656: This issue has been resolved.]

General Routing

• When you include a policy with a from interface qualifier in a configuration, the routing process might restart unexpectedly. [PR/96752: This issue has been resolved.]

Routing Protocols

• When a Fast Ethernet interface is configured to accept multicast traffic and its associated PIC is taken offline and brought back online, the interface might not accept multicast traffic. The message “Could not enable multicast for INET on interface fe-x/x/x” might be written to the system log in this case. [PR/77351: This issue has been resolved.]
• In rare cases, processing an upstream assert message for an (S,G) node that was previously marked as deleted might cause the routing protocol process (rpd) to reset unexpectedly. [PR/80253: This issue has been resolved.]
• After Routing Engine graceful switchover, the OSPF MD5 crypto sequence number might be lower then the previous one used. If this is the case, the neighbor should reject all packets and adjacency will timeout. A crypto sequence number higher then previously received is allowed; the OSPF neighbor will adapt. [PR/97050: This issue has been resolved.]
• When you include the always-compare-med statement at the [edit protocols bgp path-selection] hierarchy level, the routing protocol process (rpd) might generate a core file (but it continues to run). [PR/99220: This issue has been resolved.]
• If you enable Unicast Reverse Path Forwarding (uRPF) when a next-table next-hop route is present, the routing protocol process (rpd) might restart repeatedly. [PR/99488: This issue has been resolved.]
• When a BGP routing table is removed, the routing protocol process (rpd) might stop operating and generate a core file. [PR/99777: This issue has been resolved.]
• When the interface for reverse path forwarding (RPF) goes down, PIM immediately removes the associated multicast route entry, even if unicast routing has not yet converged. In a configuration in which multicast traffic is always sent on the backup interface, the immediate removal can cause a delay in route installation after unicast routing converges. [PR/102306: This issue has been resolved.]
• When a bootstrap router message (BSM) is received, the Protocol Independent Multicast (PIM) software does not verify that the message came from the appropriate reverse path forwarding (RPF) neighbor. The result is unnecessary forwarding of some BSMs. [PR/103376: This issue has been resolved.]
• JUNOS Release 8.3R1.5 does not support BGP AS4_PATH or AS4_AGGREGATOR; if these attributes are received from a BGP neighbor, the routing protocol process (rpd) might reset unexpectedly. Note that, since these attributes are transitive, they might come from an indirectly peered neighbor. There is no workaround. [PR/104735: This issue has been resolved.]
• When a routing table is updated with information from RIP, the routing protocol process (rpd) might generate a core file and stop operating. [PR/105027: This issue has been resolved.]
• If a policy with a community delete action deletes all communities, the routing process will leak memory. [PR/230207: This issue has been resolved.]

MPLS Applications

• In some cases graceful restart does not work correctly with ingress RSVP LSPs. [PR/80061: This issue has been resolved.]
• When an LDP neighbor’s IP address changes, information about the previous address persists in the newly established LDP session along with the new address. When the previous address times out, the forwarding equivalence class (FEC) for the neighbor’s loopback address might be mistakenly removed. As a workaround, clear the LDP session when the address changes. [PR/103001: This issue has been resolved.]
• An error in the Constrained Shortest Path First (CSPF) software might cause the routing protocol process (rpd) to generate a core file and stop operating. [PR/103777: This issue has been resolved.]
• The router might begin to receive LDP hellos and start to establish an LDP adjacency even if the interface is not fully operational. [PR/228298: This issue has been resolved.]

Class of Service

• Unusually high memory allocation might occur for link services (ls-) interface queues, because the queues' buffer allocation is not based on bundle bandwidth. As a workaround, apply a scheduler map on the multilink bundle, with buffer sizes configured to be a fraction of the original buffer sizes. The maximum buffer size allocated to the multilink bundle interface does not affect other interfaces as long as the sum of buffer sizes of the queues on the multilink interface equals a fraction of the maximum buffer size. [PR/70562: This issue has been resolved.]
• On J-series Services Routers, when you modify the value for the shaping-rate statement at the [edit class-of-service adaptive-shapers adaptive-shaper-name trigger] hierarchy level and then issue the commit command, the change does not take effect on the interface to which the adaptive-shaper adaptive-shaper-name statement is applied. As a workaround, deactivate and then reactivate the interface. Issue the deactivate class-of-service interfaces interface-name unit unit-number adaptive-shaper command, followed by the activate class-of-service interfaces interface-name unit unit-number adaptive-shaper command. [PR/82243: This issue has been resolved.]
• When the policer action involves setting the loss priority or the forwarding class, the policer counter is not incremented. [PR/96341: This issue has been resolved.]
• If you modify the buffer size in a class-of-service scheduler, the FPC might reset. [PR/99780: This issue has been resolved.]
• An error check was introduced for ensuring that the delay-buffer-rate value does not exceed the interface speed for IQ2 PICs. Unfortunately the check was not limited to the IQ2 PICs, with the result that IQ PICs receive this commit failure. [PR/230396; This issue has been resolved.]

Forwarding and Sampling

• On all platforms, certain combinations of load override and rollback operations might cause firewall filters configured for the VPLS, CCC, and TCC families not to work correctly. To restore correct performance, deactivate and reactivate each interface to which the filters are applied. [PR/95140: This issue has been resolved.]
• If you create an input firewall filter chain with multiple filters referencing the same policer (term-specific policer, three-color-policer, or prefix-action template), the firewall filter compiler might stop operating. As a workaround, include the filter-specific statement or apply the policer to a single firewall filter containing multiple terms. [PR/96040: This issue has been resolved.]
• On M10i and MX960 routing platforms, filters are not replicated to the backup Routing Engine, with the result that the filter disappears after a GRES event. As a workaround, issue the commit full synchronized command. [PR/98113: This issue has been resolved.]
• When you configure an interface in a logical router and apply a firewall filter, the software allows you delete the firewall filter from the configuration while the interface still references it. When you commit the configuration, the system returns a warning message: “Referenced filter filter-name of family family-type is not defined,” but allows the commit operation to succeed. [PR/98442: This issue has been resolved.]
• On T-series platforms only, for traffic generated by the Routing Engine, forwarding-class filters do not work properly because the QoS field is not initialized correctly in the kernel. [PR/98943: This issue has been resolved.]
• When you use an MF classifier on a J-series router, if a filter with multiple terms is applied to an interface, the traffic all goes to queue 0 instead of going to separate queues as specified in the filter. [PR/105091: This issue has been resolved.]

Network Management

• If there is a communication failure when the routing protocol process (rpd) is processing an SNMP request from the SNMP process (snmpd), rpd might dump core. [PR/69969: This issue has been resolved.]
• When a multicast route has more than one downstream interface, information about only the first interface is returned in response to SNMP queries. As a result, the MIB table is not populated correctly. [PR/97583: This issue has been resolved.]
• On J4350 and J6350 routers, the engine-id use-mac-address statement at the [edit snmp] hierarchy level is not supported. [PR/98711: This issue has been resolved.]
• When the bcm0 interface flaps on a TX Matrix platform master unit, the SNMP process (snmpd) connection between the T640 routing nodes and the master unit does not reset properly. [PR/100593: This issue has been resolved.]
• When forwarding MPLS LSP traps with a nondefault context (for example, from a nondefault logical router or routing instance), the SNMP process (snmpd) might dump core. [PR/100851: This issue has been resolved.]
• The minimum value for the size statement at the [edit snmp traceoptions file] hierarchy level is 10,000, which is less than the minimum value of 10,240 that applies to the tracing configuration at other hierarchy levels. Attempts to commit a configuration with the value 10,000 wrongly fail, because the verification software applies the standard minimum of 10,240. [PR/101560: This issue has been resolved.]
• If you configure the target address for SNMPv3 traps for both the main router and other logical routers or routing instances (by including multiple target-address statements at the [edit snmp v3] hierarchy level), an attempt to commit the configuration fails and a core file is created. [PR/102890: This issue has been resolved.]

8.3R1

The following issues have been resolved since JUNOS Release 8.2R1. The identifier following the description is the tracking number in our bug database.

Platform and Infrastructure

• Route records for Routing Engine-based sampling are exported to the AS PIC, even when the records are not needed by the AS PIC. This action consumes valuable memory resources on the AS PIC. [PR/75550: This issue has been resolved.]
• The NTP process selects the best source address to reach its peer, overriding the configured source address. [PR/94290: This issue has been resolved.]
• On routing platforms that use IPv6 addresses, duplicate address detection (DAD) fails after some operations (including graceful Routing Engine switchover). As a result, ping requests are sent from an invalid source address and fail. [PR/94946: This issue has been resolved.]
• When an FPC reports a hardware error for a PIC, a FRU failure trap might not be generated. [PR/95006: This issue has been resolved.]
• On M120 Internet routers, large VLAN configurations might cause the router to repeatedly dump core. [PR/95012: This issue has been resolved.]
• When a TCP session is initiated from a local endpoint that is defined in a VPN routing and forwarding (VRF) table, the session can fail when the path maximum transmission unit (MTU) changes to a value small enough to make packet fragmentation necessary. [PR/95379: This issue has been resolved.]
• On M10i routers, when the system is upgraded to the JUNOS 8.2R1 release, memory buffers might become full and cause a core dump. [PR/95671: This issue has been resolved.]

User Interface and Configuration

• When multiple users simultaneously use JUNOScope to perform device interactions on the same device, more than one management (mgd) session might be created on the device. Of the mgd sessions created, one is used by JUNOScope for pooling purpose. The remaining mgd sessions are not automatically closed even after interaction with the device is completed. [PR/72451: This issue has been resolved.]
• RADIUS/TACACS+ authenticated users who are mapped to a local template user might not be able to archive files using the CLI. [PR/96266: This issue has been resolved.]
• When you configure commit script management at the [edit groups group-name system commit] hierarchy level and commit the configuration, the CLI session terminates. As a workaround, configure commit script management at the [edit system commit] hierarchy level. [PR/96917: This issue has been resolved.]

Interfaces and Chassis

• When an M40e router chassis keeps sending a “failed reading voltage” error message, it might indicate that an incorrect power entry module (PEM) is installed. [PR/70868: This issue has been resolved.]
• When you enter an name with more than 80 characters as the interface-name variable used with the show interfaces descriptions interface-name command, the system produces a core dump. [PR/72155: This issue has been resolved.]
• On non-Enhanced FPCs with STM16 PICs on M160 routing platforms, if you configure the MTU size to the maximum value of 9192 bytes, packet forwarding might stop. As a workaround, reset the MTU size to the default of 4474 bytes. [PR/76390: This issue has been resolved.]
• When you configure a local gateway for an IPSec tunnel within a routing instance, and then change the routing instance type from VRF to virtual router and commit the configuration, the IP address of the local gateway might disappear from the interface configuration and the IPSec tunnel might not become established. [PR/76894: This issue has been resolved.]
• In a few cases, when member links of an MLPPP bundle are deactivated and then reactivated, output from the show interfaces interface-name statistics detail command might display unreliable statistics. [PR/78696: This issue has been resolved.]
• You cannot configure the bandwidth on DS, T1, and E1 interfaces. [PR/81827: This issue has been resolved.]
• On a dual-port Channelized T1/E1 PIM with interfaces channelized into DS0 interfaces, all links may not be available after all 24 time slots on one ct1 port are mapped to 24 time slots on another ct1 interface on the same PIM. [PR/81976: This issue has been resolved.]
• When MPLS packets are received on SHDSL (ATM) interfaces on a J-series router, they might be dropped. [PR/94353: This issue has been resolved.]
• When a redundant link services (rlsq-) interface is modified, if an internal query process is being run at the same time as the modification, the kernel might process might stop. [PR/94508]
• When you use MLPPP, the loop-detected device flag remains active for the local interface, even after the remote loop is removed from the end router. [PR/94800: This issue has been resolved.]
• On M320 or T-series routing platforms, logical interfaces on Channelized T3 PICs that are configured with DLCIs of less than 64 in frame-relay-ccc or frame-relay-tcc encapsulations will not pass traffic. [PR/95358: This issue has been resolved.]
• On ATM2 PICs, if you initially configure both the atm-options linear-red-profile statement and the sonet-options aps statement and then change a portion of the linear-red-profile configuration later, the interface associated with the linear-red-profile might flap even if there is no change in the associated linear-red-profile properties. [PR/96621: This issue has been resolved.]
• When you remove a spare Switch Interface Board (SIB) without first taking the SIB offline, the working SIB in slot 1 erroneously changes to Check status in the output from the show chassis sibs command. [PR/96959: This issue has been resolved.]
• The JUNOS software truncates the endpoint discriminator option block received from the peer while sending an LCP config- reject message. This is the case when the endpoint discriminator is an IEEE 802.1 MAC address. [PR/97169: This issue has been resolved.]

Services Applications

• Some probe types require particular options to be configured using specific attributes. For example, the udp-ping-timestamp statement requires a minimum data size of 12. The minimum data size for TCP probe packets is 1. Using a smaller value (or none) for data size results in a commit error. [PR/69765: This issue has been resolved.]
• If traffic is heavy in a tunnel that has numerous concurrent Layer 2 Tunneling Protocol (L2TP) sessions, the AS PIC might discard some Layer Control Protocol (LCP) echo messages. [PR/72334: This issue has been resolved.]
• In active FTP mode on a services PIC, FTP application-level gateways (ALGs) refuse connection attempts that originate at port numbers other than 20. [PR/82232: This issue has been resolved.]
• If you type Ctrl+c to interrupt the request security pki ca-certificate enroll ca-profile ca-profile-name command, the key management process (kmd) might terminate and create a core file. [PR/94713: This issue has been resolved.]
• When the DF bit is set in the IP header, CRTP does not compress the packet. [PR/95396: This issue has been resolved.]

General Routing

• When load balancing is configured, an install-nexthop policy action might not work completely. [PR/72457: This issue has been resolved.]

Routing Protocols

• In certain cases, on multiprotocol BGP sessions configured with a family route-target (AFI/SAFI 1/132), receipt of the very first route-target NLRI might cause the routing process (rpd) to dump core. [PR/78876: This issue has been resolved.]
• If you configure BGP path selection with BGP groups that have no neighbor setting, the routing process (rpd) dumps core. [PR/95558: This issue has been resolved.]
• In IS-IS XML output, when the JUNOS routing software encounters sub-TLV-related XML tags not enclosed within the IS-reachability XML tag, it discards this information. [PR/95711: This issue has been resolved.]
• When you commit only the routing-options section of a configuration, changes in the confederation member list are not forwarded to BGP. [PR/96277: This issue has been resolved.]

VPNs

• On M10i routers configured with VPNs, the MIB variables in vpnRTTable, vpnPwTable, and vpnIfTable might provide incorrect values. [PR/75649: This issue has been resolved.]
• A routing instance can fail to be deleted properly within the routing process if another routing instance is configured with the same VRF target. The workaround is to remove that VRF target from all routing instances. Modifying the route distinguisher in the routing instance configuration can cause prefixes added to the routing table for a particular VRF to not be propagated to the forwarding table. The workaround is to change the name of the routing instance. [PR/80933: This issue has been resolved.]
• A flag mismatch prevented BGP from flashing Layer 2 VPN routes to VPLS instances.[PR/82517: This issue has been resolved.]
• In earlier releases of JUNOS 8.0 and 8.1, when you issued the show snmp mib walk jnxVpnIfTable command, the output provided only the first entry of each instance. [PR/95924: This issue has been resolved.]

Class of Service

• On ATM 2 PICs, when a logical interface is disabled, there is no channel table entry for it. However, the class-of-service process (cosd) still tries to configure a classifier for the channel corresponding to that disabled logical interface and the operation fails because the channel entry does not exist. [PR/71081: This issue has been resolved.]
• Insufficient memory was allocated for forwarding-class configuration data. As a result, trying to access information might have exceeded the allocation and caused the CoS process (cosd) to terminate unexpectedly. [PR/95404: This issue has been resolved.]

Forwarding and Sampling

• When host sampling is configured, some rarely occurring conditions can cause the Packet Forwarding Engine to stop functioning. [PR/74173: This issue has been resolved.]
• When you configure source class usage and change the configuration for a policer, the changes might not take effect. [PR/78754: This issue has been resolved.]
• Flow-route filters that are configured with terms matching TCP fragments might not match the TCP fragments. [PR/81235: This issue has been resolved.]

Network Management

• If you rapidly poll ipCidrRouteNumber OID .1.3.6.1.2.1.4.24.3.0 for multiple virtual routers, you might see incorrect values for all but the first table. [PR/95217: This issue has been resolved.]
• When you set the SNMP engine-id statement to use-mac-address, the engine ID is not visible after you reboot the router. As a workaround, manually restart the SNMP process (snmpd). [PR/97356: This issue has been resolved.]

System Log

• The logged text for the CHASSISD_FASIC_INPUT_DROP system log tag refers to the “Packeting Forwarding Engine” instead of the “Packet Forwarding Engine”. [PR/77189: This issue has been resolved.]