Previous Releases

8.4R3

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

Platform and Infrastructure

• If you enable logging for the CFEB on an M7i router, the router might generate a core file and stop operating. As a temporary workaround, disable logging on the CFEB serial console by issuing the set syslog tty disable command. [PR/77794: This issue has been resolved.]
• The MultiServices PIC might not work correctly when the PIC is loaded and frequent commands related to the PIC are issued. [PR/81826: This issue has been resolved.]
• If a MultiServices PIC processes more than 250 Kpps, the PPS overload field in the output from the show services accounting errors command is erroneously set to Yes. [PR/95312: 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 a small form-factor pluggable transceiver (SFP) does not respond to a request for diagnostic data, a message is written to the system log. The message is unnecessary because the failure to respond has no operational impact. [PR/97718: 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 T-series routing platforms, high-priority fabric queue 143 is not initialized properly. [PR/228344: This issue has been resolved.]
• On MX-series Ethernet services routers, traffic forwarding is affected under the following conditions: you configure aggregated Ethernet and integrated routing and bridging (IRB) interfaces; and 100,000 next hops are created; and VLAN trunk ports on the remote end transition down and up. The following messages might appear in the system log: "Failed to install flood nexthop" and "Unable to allocate new Flood NH." [PR/230062: 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 so that traffic forwarding is stopped and a core dump occurs. As a workaround, include the router-id statement at the [edit routing-options] hierarchy level on both routers to avoid looping. [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.]
• 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.]
• With JUNOS 8.1 and later, unrestricted proxy Address Resolution Protocol (ARP) does not always work correctly: some requests are ignored, and the proxy requests not proxied counter might increment in the output of the show system statistics arp command. [PR/237985: This issue has been resolved.]
• When you configure an interface to be part of a VPN routing and forwarding (VRF) instance and a class-of-service (CoS) DiffServ code-point rewrite configuration is applied to the interface, the traffic might be sent to an incorrect egress logical interface. [PR/238368]
• In certain rare circumstances, an M-series router might generate a core file and restart when it tries to determine the best match for a specified route prefix. [PR/239837: This issue has been resolved.]
• When you issue the file copy command with an FTP path as the source or destination and include the source-address option, the specified source address is not used for establishing a connection with the peer FTP server. [PR/240580: This issue has been resolved.]
• When SNMP receives a request to create a ping MIB row by using the createAndGo method, the SNMP remote operations (rmopd) process might generate a core file and stop operating. [PR/251555: This issue has been resolved.]
• When the vrf-table-label statement is deactivated at the [edit routing-instances instance-name] hierarchy level, the counts of input bytes and packets for the physical interface in the output of the show interfaces extensive command are twice the actual values. [PR/253946: This issue has been resolved.]
• When aggregate SONET or aggregate Ethernet interfaces are used for multicast traffic, and a link in the aggregate is deleted or goes down, the Packet Forwarding Engine might generate a core file and stop operating. [PR/257691: This issue has been resolved.]
• When an address rename operation is performed on Gigabit Ethernet interfaces, filters are removed and then added back. The operation can sometimes be replicated to the backup Routing Engine as a single change. In this scenario, the backup Routing Engine attempts to delete the filter and add it back using the index specified by the master Routing Engine. However, the entry is not deleted, leading to a mismatch in the index usage between the master and slave Routing Engines, which causes the Routing Engine to produce a core file and stop operating. [PR/258927: This issue has been resolved.]
• The UDP ping server does not respond to probes sent through a routing instance other than the default (inet.0). [PR/260097: This issue has been resolved.]

User Interface and Configuration

• After a Routing Engine switchover, an erroneous EVENTD_POLICY_ENTRY_NOT_FOUND message might be logged. [PR/99561: This issue has been resolved.]
• When you change the value of the time-zone statement at the [edit system] hierarchy level (for example, to change to or from daylight saving time) and commit the configuration, the changed value sometimes does not take effect immediately. [PR/103724: This issue has been resolved.]
• After the following sequence of operations, all parts of a multiword configuration statement might not be deleted: issue the rollback or load update command to change the configuration, commit it, issue the delete command to remove the multiword statement from the new candidate configuration, and commit the configuration. [PR/240983: This issue has been resolved.]
• If a client application that uses the JUNOScript Perl module uses Telnet to connect to the JUNOScript server, the login name or password used by the application cannot include special characters. [PR/241236: This issue has been resolved.]
• If a NETCONF client sends the <commit/> tag to a router on which commit synchronize is the default commit method, the <rpc-reply> tag element generated by the NETCONF server might not be well-formed XML. [PR/241659: This issue has been resolved.]
• When you grant all JUNOS permissions to users in a login class by including the permissions all statement at the [edit system login class class-name] hierarchy level, users in the class might not be granted all permissions. [PR/251722: This issue has been resolved.]
• The comment option of the commit synchronize configuration mode command is no longer available in JUNOS Releases 8.4 and later. [PR/254004: This issue has been resolved.]
• When you issue the request chassis routing-engine master switch command to change Routing Engine mastership, the nxRedundancySwitchover SNMP trap is not generated. (However, the event is recorded in the system log or chassis process log file if logging is appropriately configured.) [PR/254637: This issue has been resolved.]

Interfaces and Chassis

• If a low speed bundle is congested, the jitter for link fragmentation and interleaving (LFI) traffic is high even though fragmentation is configured for Multilink Point-to-Point Protocol traffic. [PR/77862: This issue has been resolved.]
• When you configure point-to-multipoint Frame Relay, the router might generate a core file. [PR/82303: This issue has been resolved.]
• In JUNOS Release 8.0 and later, the default framing method for DS0 interfaces is extended superframe (ESF) instead of the correct, documented superframe (SF) method, which applied in earlier releases. [PR/97277: 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.]
• When a large number of packets traverse a GRE-over-IPSec tunnel that has as one of its endpoints a J4350 Services Router with a Crypto Accelerator Module, the Services Router might stop forwarding traffic. [PR/101337: This issue has been resolved.]
• On M120 routers, MX-series routers, and Enhanced III FPCs on M320 routers, an interface might stop forwarding traffic after it receives an IPv6 packet that has an invalid payload. The interface still accepts traffic, but discards all outgoing packets. To recover, reboot the FEB on M120 routers, the DPC on MX-series routers, or the FPC on M320 routers. There is no workaround. [PR/105266: This issue has been resolved.]
• For Gigabit Ethernet interfaces on J-series Services Routers, the link-mode and speed statements at the [edit interfaces ge-fpc/pic/port] hierarchy level are mutually dependent; that is, if you include one, you must include the other. If you do not, the interface process generates a warning and uses autonegotiated values. For Gigabit Ethernet interfaces on other routing platform types, the speed statement is not available, so including the link-mode statement alone is valid. Nevertheless, the interface process writes the following message to its log and the system log: "Speed and linkmode duplex settings are mutually required." (Note further that the link-mode statement is actually nonoperational on non-J-series routing platforms, because the only valid value for it is the default, full-duplex.) [PR/228857: This issue has been resolved.]
• During initialization of a 10-gigabit small form-factor pluggable transceiver (XFP), error messages similar to the following might appear in the system log for the PIC that houses the XFP: "xfp_mask_alarms: %PFE-index: IQ2(fpc-slot/pic-slot): Link 0 XFP failed set alarm mask addr address err 28." [PR/231624: This issue has been resolved.]
• When you upgrade a J6300 Services Router from JUNOS Release 8.2 to Release 8.4, the upgrade might fail with a validation error even though the configuration includes no elements that are not supported in JUNOS 8.4. The workaround is to include the no-validate option on the upgrade command. [PR/232061: This issue has been resolved.]
• When graceful Routing Engine switchover is enabled and you use the request system reboot command to reboot the master Routing Engine, if an FPC does not establish its connection to the new master Routing Engine before the previous master shuts down, the FPC restarts. [PR/234207: This issue has been resolved.]
• On MX-series Ethernet services routers with dual Routing Engines, when you include the master-only statement at the [edit interfaces fxp0 unit logical-unit-number family (inet|inet6) address address] hierarchy level and issue the commit synchronize command, the following message might be written to the system log on the backup Routing Engine: "DCD_CONFIG_WRITE_FAILED: Interface fxp0, configuration write failed for an IFA ADD: Operation not supported." When you perform a Routing Engine switchover, the following message might be written to the log on both master and backup Routing Engines: "KERN_ARP_DUPLICATE_ADDR: duplicate IP address master-only-address! sent from address: mac-address (error count = count)." There is no operational impact. [PR/235956: 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.]
• When LSQ redundancy is enabled and a PIC in the redundancy group restarts, several FPCs might generate a core file. [PR/236048: This issue has been resolved.]
• It is not valid to include the accept-data statement at the [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-group group-number] address if you also include the virtual-address statement at that level with a value that is the same as in the grandparent address address statement. When you try to commit such a configuration, the following message appears: "WARNING: Can't have accept-data and IP address owner on interface interface-name.xx," where xx is the interface’s logical unit number. When you configure multiple logical interfaces on the same physical interface and include the priority 255 statement at the [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-group group-number] hierarchy level on a logical interface whose unit number is higher than any logical interface that has the invalid configuration described above, the warning message reports as "xx" the logical unit number of that (highest-numbered) logical interface in every case, instead of reporting the unit number of the interfaces that have the incorrect configuration. [PR/236135: This issue has been resolved.]
• On MX-series Ethernet services routers configured with 802.1ag Ethernet Operation, Administration, and Maintenance (OAM), if the direction of a maintenance endpoint (MEP) running on a VPLS customer-edge logical interface is set to DOWN, the commit-check operation fails. [PR/237802: This issue has been resolved.]
• For link services queuing (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.]
• When you issue the show interfaces extensive command on a broadcast interface (Ethernet), you might see discrepancies in the number of input packets reported under the traffic statistics and those reported under the MAC statistics. [PR/238621: This issue has been resolved.]
• When a PIC detachment process takes a long time for an IQ2 PIC (for example, triggered by a large number of route updates when an IQ2 PIC is offlined), the PIC chassis process (pic-chassisd) connection might not be closed properly. [PR/239944: This issue has been resolved.]
• On J4350 and J6350 Services Routers, the show chassis interface extensive command does not display Carrier Transitions and certain other statistics properly. [PR/241086: This issue has been resolved.]
• On a router with graceful Routing Engine switchover enabled and a large number of firewall filters configured, delays in the transfer of the filter information during a Routing Engine mastership switch can cause FPCs to restart. [PR/250686: This issue has been resolved.]
• The JUNOS documentation states that if the configuration is not the same for every port on a multiport ATM DS3 or E3 PIC, the smallest shaping rate configured on a port is used for cell transmission shaping on the PIC. Instead, every time a port’s shaping rate is changed, that value is used for the PIC even if it is not the smallest value. [PR/252837: 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.]
• If an interface (port) on a 4-port Fast Ethernet Enhanced Physical Interface Module (ePIM) on a J-series Services Router is operating in half-duplex mode, it might stop forwarding traffic. As a workaround, include the link-mode full-duplex and speed 100m statements at the [edit interfaces fe-fpc/pic/port] hierarchy level. [PR/253329: This issue has been resolved.]
• If you configure loopback mode on one interface (port) on a 4-port Fast Ethernet Enhanced Physical Interface Module (ePIM) on a J-series Services Router (by including the loopback statement at the [edit interfaces fe-fpc/pic/port fastether-options] hierarchy level), all four ports operate in loopback mode. [PR/253498: This issue has been resolved.]
• When you issue the request chassis routing-engine master switch command to change Routing Engine mastership, the jnxRedundancySwitchover SNMP trap is not generated. (However, the event is recorded in the system log or chassis process log file if logging is appropriately configured.) [PR/254637: This issue has been resolved.]
• When you configure a logical interface with encapsulation ether-vpls-over-atm-llc, the Packet Forwarding Engine does not forward packets destined for the Routing Engine. [PR/255713: This issue has been resolved.]
• After a Routing Engine mastership switch on an M120 router, the show chassis hardware command omits all information about small form-factor pluggable transceivers (SFPs) installed in PICs. [PR/256032: This issue has been resolved.]
• The chassis process on the backup Routing Engine writes the following message to its log every 20 seconds, which causes excessive disk I/O: "mcontrol_idl_ext_handler: rx RE_INFO_IDL_EXT magic 5012." [PR/256840: This issue has been resolved.]
• On M40e routers, SONET/SDH interfaces might experience phase-locked loop (PLL) errors and discard packets. The PLL errors appear in the output of the show interfaces so-fpc/pic/port extensive command as nonzero values in the fields on the line labeled PLL Lock. [PR/256946: This issue has been resolved.]
• On an M40e router, when you configure link services IQ (lsq-) interfaces on MultiServices PICs and pair them with Channelized OC12 PICs for failure recovery, rebooting the router might cause remote defect indication (RDI) or alarm indication signal (AIS) alarms for the OC12 interfaces. In other words, when you include the trigger-link-failure coc12-fpc/pic/port statement at the [edit interfaces lsq-fpc/pic/port lsq-failure-options] hierarchy level and the router reboots, the output of the show interfaces coc12-fpc/pic/port extensive command reports RDI-L or AIS-L in the SONET alarms field. [PR/257419: This issue has been resolved.]
• On a 10-Gigabit Ethernet IQ2 PIC configured for both point-to-point OSPF and PIM, when you disable PIM, OSPF adjacencies might also go down. [PR/257848: This issue has been resolved.]
• On an MX-series routers, asynchronous notification does not work correctly for 4-port Gigabit Ethernet DPCs. [PR/259304: This issue has been resolved.]
• On J2320 and J2350 Services Routers, Gigabit Ethernet interfaces sometimes stop transmitting packets after they are taken down and brought back up. As a workaround, restart PIC 0. [PR/261010: This issue has been resolved.]
• When operating in Layer 3 mode, the Adaptive Services Module in an M7i router might generate a core file and stop operating. [PR/265835: This issue has been resolved.]

Services Applications

• If Network Address Port Translation (NAPT) is configured and multiple short-lived flows are established, ports on AS PICs might not be assigned correctly. In some cases, this situation causes the AS PIC to stop functioning. [PR/95019 and PR/229287: These issues have been resolved.]
• When you configure twice NAT with static source and static destination translation, the destination port for ICMP flows might change (the ports are supposed to remain unchanged). [PR/96701: This issue has been resolved.]
• When a large number of MPLS routes are configured, the MultiServices PIC might write messages like the following to the system log and generate a core file: "meta_db: Route node alloc failed," "meta_db: Failed to allocate from pile," "meta_db: nh-entry to be updated doesn't exist." [PR/235654: This issue has been resolved.]
• On routers that have Layer 2 Tunneling Protocol (L2TP) services configured on Adaptive Services or MultiServices PICs, the final fragment of a fragmented packet might not be forwarded. [PR/251687: This issue has been resolved.]
• On the MultiServices 400 PIC, a memory warning flag might be set even with low traffic rates. [PR/251908: This issue has been resolved.]
• When dynamic flow capture is configured, a Monitoring Services III PIC or MultiServices 400 PIC might repeatedly generate a core file and restart. [PR/257510: This issue has been resolved.]

Layer 2 Ethernet Services

• In the output of the show spanning-tree mstp configuration operational mode command, some columns do not align properly. This does not affect the operation of the Spanning Tree Protocol. [PR/251610: This issue has been resolved.]
• The output for the show spanning-tree mstp configuration operational mode command might display incorrect information about the MSTI identifier. This does not affect the operation of the Spanning Tree Protocol. [PR/251612: This issue has been resolved.]
• On MX-series Ethernet Services routers, if you apply class of service (CoS) to an integrated routing and bridging (IRB) interface within a VPLS domain using virtual loopback tunnel (VT) interfaces, traffic from remote customer edge (CE) routers might not be forwarded during a graceful Routing Engine switchover. As a workaround, modify your VPLS domain to use LSI interfaces by including the no-tunnel-services statement at the [edit routing-instances instance-name protocols vpls] hierarchy level. [PR/252468: This issue has been resolved.]
• If you deactivate the nonstop-bridging statement at the [edit protocols layer2-control] hierarchy level and then a graceful Routing Engine mastership switchover occurs, the bridge ID for a routing instance might be reset to all zeros and the port state for some component interfaces in the routing instance might change to "Blocking." Both conditions are reported by the show spanning-tree bridge routing-instance detail command. [PR/264982: This issue has been resolved.]

General Routing

• If you include the prefix-list list-name statement at the [edit policy-options] hierarchy level and deactivate all addresses in it (so that the prefix list is effectively empty), the commit operation fails with the following message: "Policy error: list-name prefix-list referenced (in term policy-term) but not defined." [PR/237205: This issue has been resolved.]
• When more than one prefix-list statement is included at the [edit policy-options policy-statement statement-name term term-name from] hierarchy level and one of the prefix lists is empty, a commit check operation fails with the message "error: Check-out failed for Routing protocols process (/usr/sbin/rpd) without details." [PR/237457: This issue has been resolved.]

Routing Protocols

• When you disable BGP tracing by removing the traceoptions statement at the [edit protocols bgp] hierarchy level, and then commit the configuration, the previously configured trace file is re-created and tracing continues. [PR/69321: This issue has been resolved.]
• When determining which BGP route to prefer, the JUNOS software does not compare route characteristics in the order specified by RFC 4456, BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP). [PR/70687: This issue has been resolved.]
• 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.]
• When two redundant PE routers send multicast traffic towards their MVPN backbone, the JUNOS software might not perform the actions necessary to prevent traffic duplication. [PR/72447: This issue has been resolved.]
• For the igmpInterfaceIfIndex object in the Internet Group Management Protocol (IGMP) MIB (IGMP-STD-MIB), the routing platform reports the ifIndex value of the logical interface instead of the expected snmpIfIndex value for the index of the table. [PR/98358: This issue has been resolved.]
• The Route Distinguisher field in the output of the show route receive-protocol command reports the value configured on the local router (by the route-distinguisher statement at the [edit routing-instances routing-instance-name] hierarchy level), instead of the route-distinguisher value configured on the remote PE router. [PR/239698: This issue has been resolved.]
• The routing process can restart unexpectedly when nonstop-routing is enabled. [PR/241422: This issue has been resolved.]
• If ATM virtual circuits repeatedly go down and come up, the routing protocol process (rpd) might generate a core file and restart. [PR/252422: This issue has been resolved.]
• In JUNOS Release 8.3 and later, the output from the show pim source command does not include information about nondirect sources. [PR/253629: This issue has been resolved.]
• When you include the family route-target statement at the [edit protocols bgp group group-name] hierarchy level, then deactivate and reactivate a routing instance, the show route table routing-instance command no longer produces output for that routing instance, whereas the show route table bgp.rtarget.0 command does produce output. [PR/257011: This issue has been resolved.]
• When route reflection is enabled for a BGP group, the routing protocol process (rpd) might generate a core file. [PR/258134: This issue has been resolved.]
• When a link goes down briefly (for 50 milliseconds, for example) and comes back up, equal-cost multipath (ECMP) load balancing might stop working correctly. If both links in an ECMP group flap in this way at the same time, IP traffic might not be forwarded to certain destination addresses (MPLS traffic is not affected). [PR/259611: This issue has been resolved.]
• When unicast reverse path forwarding (uRPF) is configured and you unconfigure a routing instance, the routing protocol process (rpd) might generate a core file and restart. [PR/259727: This issue has been resolved.]
• When you deactivate a large number of routing instances (about 335 or more), LDP sessions might go down and the following message might be written to the system log: "RPD_PPM_WRITE_ERROR: ppm_send: write error on pipe to ppmd (Broken pipe)." [PR/260477: This issue has been resolved.]
• If you issue the show route extensive command while the routing protocol process (rpd) is resolving BGP routes, the process might generate a core file and restart. [PR/260527: This issue has been resolved.]
• When a static route is configured in a routing table and then imported into another routing table, it disappears from both routing tables. [PR/262856: This issue has been resolved.]

MPLS Applications

• A router with a point-to-multipoint transmit-switch connection configured might stop functioning if the transmit label-switched path of the connection flaps. [PR/229175: This issue has been resolved.]
• On M120 and MX-series routers and M320 Enhanced III FPCs, when an MPLS-encapsulated IPv4 packet that is padded to meet the minimum Layer-2 frame size (for example, 64 bytes for frames on Ethernet media) exits an LSP, the egress interface might stop forwarding packets. This can happen when the router is configured as a PE router in a VPN or is the penultimate node of an LSP. To recover, reboot the FPC (on MX-series or M320 routers) or the FEB (on M120 platform) that houses the affected interface. [PR/251042: This issue has been resolved.]
• When you add a secondary path to a label-switched path (by including the secondary statement at the [edit protocols mpls label-switched-path] hierarchy level) and commit the configuration, the routing protocol process might generate a core file. [PR/251288: 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.]
• If an MPLS LSP configured with fast reroute is not advertised into the IGP, that LSP might reuse an old unicast list and traffic might not be forwarded. [PR/253352: This issue has been resolved.]
• When you issue the clear mpls lsp statistics name lsp-name command for a transit LSP, the spurious error message "LSP 'lsp-name' not found" might be returned. [PR/253495: This issue has been resolved.]
• The order of addresses returned as the ERO for an LSP by the SNMP mplsPathExplicitRoute object is reversed from the correct order displayed as the Computed ERO in the output of the show mpls lsp extensive command. [PR/263462: This issue has been resolved.]
• When graceful restart is enabled (by the graceful-restart statement at the [edit routing-options] hierarchy level) and an interface is configured as an egress interface in a CCC switch for a point-to-multipoint LSP (the output-interface statement is included at the [edit protocols connection p2mp-receive-switch] hierarchy level), if the LSP flaps repeatedly the interface might stop forwarding traffic. [PR/264930: This issue has been resolved.]

VPNs

• When you include the vlan-tags statement at the [edit routing-instances instance-name bridge-domains domain-name] hierarchy level for VPLS or a virtual switch, the commit operation might fail with the error message "RT Instance: Failed to retrieve vlan-tags." As a workaround, include the vlan-tags statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level instead. [PR/256958: This issue has been resolved.]
• When an interface on a CE router that is part of a CCC virtual circuit repeatedly goes offline and online, the link between the CE router at the other end of the circuit and its PE router might also go down and up repeatedly. [PR/260095: This issue has been resolved.]

Class of Service

• On M320 and T-series routing platforms, if you map multiple forwarding classes to the same queue (specify the same value for the queue-num statement at the [edit class-of-service forwarding-classes class class-name] level for multiple classes) and then include the multiple classes in one scheduler map (by including the forwarding-class statement for each one at the [edit class-of-service scheduler-maps map-name] hierarchy level, the commit operation fails with the message "Total bandwidth allocation exceeds 100 percent for scheduler-map." [PR/103370: This issue has been resolved.]
• The behavior aggregate (BA) classifier is not applied to a logical interface configured to use ether-over-atm-llc encapsulation. [PR/255742: This issue has been resolved.]
• For IQ PICs on M-series and T-series routing platforms and Enhancing Queueing DPCs on MX-series routers, when a scheduler map includes a queue configured with priority strict-high, in certain situations (such as when a PIC to which the scheduler map is applied restarts) the incorrect buffer size might be calculated for the queue. [PR/256263: This issue has been resolved.]
• When the rewrite-rules statement is included at the [edit interfaces interface-name unit logical-unit-number] hierarchy level and the PIC that houses the interface restarts, the configured rewrite rules might not be reapplied to the interface. [PR/256585: This issue has been resolved.]
• When a PIC goes offline and then online, the following message might appear on the Packet Forwarding Engine console: "cosman_compute_mad_state: No ifd for ifd_index interface-device-index." There is no operational effect unless a delay buffer is configured. [PR/257814: This issue has been resolved.]

Forwarding and Sampling

• If you configure a policer with a burst size limit larger than 67 MB, interfaces to which the policer is applied might not forward traffic. On some platforms the limit is higher, and the limit also depends on the available bandwidth. [PR/99758: This issue has been resolved.]
• On MX-series or M120 routers, if you use a tunnel services-based PIC to configure multiple VPLS instances over virtual loopback tunnel (VT) interfaces, and then include the no-tunnel-services statement to direct VPLS traffic over label-switched interface (LSI) logical interfaces instead of the VT interfaces, in some cases, the VPLS traffic might stop even though the VPLS connections remain up. As a workaround, deactivate and reactivate interfaces in the affected VPLS instances. [PR/228411: This issue has been resolved.]
• If you apply the same firewall to both IPv4 and IPv6 traffic on an interface by including the input-list statement at the [edit interfaces interface-name unit logical-unit-number family inet filter] and [edit interfaces interface-name unit logical-unit-number family inet6 filter] hierarchy levels, the clear firewall filter interface-name command clears the counters for IPv4 bytes and packets but not for IPv6 bytes and packets (in the output from the show firewall filter interface-name command). [PR/229016: This issue has been resolved.]
• When you commit a configuration that includes a large number of interfaces, routing instances, and policers, the firewall process (dfwd) might generate a core file. [PR/253440: This issue has been resolved.]
• Firewall filters that include the source-address statement at the [edit firewall filter filter-name term term-name from] hierarchy level might not process traffic correctly. As a workaround, reorder the terms in the filter. [PR/262491: This issue has been resolved.]

Network Management

• When you commit the configuration or the router reboots, SNMP generates the LinkUp trap (and the SNMP_TRAP_LINK_UP message is written to the system log) even for interfaces that are not connected to a cable. [PR/250336: This issue has been resolved.]

8.4R2

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

Platform and Infrastructure

• 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.]
• Under some circumstances, the interface process (ifd) is interfering with the operation of an LSI interface. [PR/102431: 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.]
• 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 (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.]
• On MX-series Ethernet services routers with VPLS, when a core-facing interface that is configured for integrated routing and bridging (IRB) changes to be a regular routing interface, traffic might be discarded. As a workaround, restart the chassis process (chassisd). [PR/237212: 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.]

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.]
• 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.]
• 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 the syslog 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.]
• If the event process (eventd) receives corrupted data from another process, it might generate a core file. [PR/236599: This issue has been resolved.]
• If a NETCONF client sends the <commit/> tag to a router on which ‘commit synchronize’ is the default commit method, the <rpc-reply> tag element generated by the NETCONF server might not be well-formed XML. [PR/241659: This issue has been resolved.]

Interfaces and Chassis

• 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.]
• On M160 and M40e routers, when you commit a configuration change, the router might generate a system log message that erroneously reports the master Packet Forwarding Engine Clock Generator (PCG) status as removed or offline. [PR/58716: 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.]
• With JUNOS Release 8.0 or higher, 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.]
• 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 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.]
• On M320 routers, if the ingress and egress interfaces used for a TCC connection are installed in different types of FPCs (one in a standard FPC, another in an Enhanced III FPC), TCC encapsulation does not work. As a workaround, install the PICs in the same type of FPC. [PR/102997: 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 the kernel database. [PR/105268: 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 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.]
• The link fault management process might fail when you add an interface configuration to a deactivated hierarchy, 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 (the route-accounting statement is included 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.]
• 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 graceful Routing Engine switchover is enabled and the backup Routing Engine is taken offline, a CHASSISD_SNMP_TRAP message might not be generated. [PR/238797: This issue has been resolved.]

Services Applications

• 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 setup 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.]
• If the configuration includes certain features (for example, firewalls), service PICs do not come online if it takes the Packet Forwarding Engine more than 2 minutes to establish communication between PICs and the Routing Engine. [PR/236926: This issue has been resolved.]
• When two or more IQ2 PICs are installed on an M7i, M10i, or M120 router, Layer 2 Tunneling Protocol (L2TP) policer sessions are not established correctly. As a workaround, issue the request chassis pic fpc-slot slot-number pic-slot slot-number command to take all but one of the PICs offline. [PR/237356: This issue has been resolved.]

Routing Protocols

• Label aggregation is not working properly when route reflection is also configured in Layer 3 VPN networks. [PR/228039: This issue has been resolved.]
• When you use the clear bgp damping address command to remove a damped route from a routing table and specify a prefix on the address (for example, clear bgp damping 10.0.0.8/30), the route might not be removed. (Damped routes are listed as hidden in the output of the show route damping suppressed terse command.) [PR/231502: This issue has been resolved.]
• Configuring a PIM bootstrap export policy (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.]
• The Route Distinguisher field in the output of the show route receive-protocol command reports the value configured on the local router (by the route-distinguisher statement at the [edit routing-instances routing-instance-name] hierarchy level), instead of the route-distinguisher value configured on the remote PE router. [PR/239698: This issue has been resolved.]

MPLS Applications

• 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.]
• RSVP PATH messages are not bundled when RSVP aggregation is negotiated on a point-to-point link. [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 at the [edit protocols mpls log-updown] hierarchy level. [PR/237464: This issue has been resolved.]

VPNs

• If you configure a Layer 2 circuit across a logical tunnel interface that uses ethernet-vpls encapsulation, the Layer 2 circuit connection might not come up. As a workaround, use ethernet encapsulation on the logical tunnel interface. [PR/100161: This issue has been resolved.]
• On a provider edge (PE) router configured with Multiprotocol BGP-based multicast VPNs and connected directly to a receiver, if you modify the multicast VPN import target with the import-target statement at the [edit routing-instances routing-instance-name mvpn route-target] hierarchy level, the BGP route reflector might fail to readvertise the multicast VPN routes. As a workaround, issue the clear bgp neighbor soft command on the route reflector to force it to readvertise all the multicast VPN routes without resetting the BGP sessions. [PR/104192: This issue has been resolved.]
• On MX-series Ethernet services routers, if the VPLS configuration includes the no-tunnel-services statement (meaning that an LSI is used instead of a virtual tunnel), customer edge (CE)-facing interfaces sometimes discard traffic. In the output from the show interfaces command, the list in the Flags field for the logical interface might include the CCC-Down or Hardware-Down flag. As a workaround, deactivate and reactivate the CE interface. [PR/234756: This issue has been resolved.]
• For MX-series routers, if you change the route distinguisher used for a VPLS routing instance, VPLS connections might not come up. As a workaround, deactivate and then reactivate the VPLS routing instance. [PR/235048: This issue has been resolved.]

Class of Service

• 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.]
• A class-of-service EXP classifier applied to a VRF routing instance does not work correctly for traffic received by a PIC housed in an Enhanced Scaling FPC (FPC4). [PR/233694: This issue has been resolved.]
• If you configure 600 T1 links and 255 Multilink Frame Relay (FRF.16) bundles on link services queuing (LSQ) interfaces in an AS PIC or MultiServices PIC, then downgrade the routing platform to JUNOS 8.4R1 from a later release, the downgrade might fail the validation process and generate the following error message: “Current configuration not compatible with /var/tmp/jinstall-8.4R1.13-domestic-signed.tgz”. As a workaround, deactivate the class-of-service configuration, downgrade to 8.4R1, and then reactivate the class-of-service configuration. [PR/234031: This issue has been resolved.]
• Over T3 or E3 links on J-series Services Routers, traffic that is assigned strict-high priority might be discarded when large-packet high-priority traffic is sent together with small-packet low-priority traffic and the high-priority queue’s buffer size is much lower than that of the low-priority queue. As a workaround, configure a shaper with its rate set to match line rate. [PR/234626: This issue has been resolved.]
• Deactivating and then activating an interface causes packet loss on other ports of the same PIC. [PR/238314: 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.]
• On MX-series or M120 routers, if you use a tunnel services-based PIC to configure multiple VPLS instances over virtual loopback tunnel (VT) interfaces, and then include the no-tunnel-services statement to direct VPLS traffic over label-switched interface (LSI) logical interfaces instead of the VT interfaces, in some cases, the VPLS traffic might stop even though the VPLS connections remain up. As a workaround, deactivate and reactivate interfaces in the affected VPLS instances. [PR/228411: This issue has been resolved.]
• If you apply the same firewall to both IPv4 and IPv6 traffic on an interface by including the input-list statement at the [edit interfaces interface-name unit logical-unit-number family inet filter] and [edit interfaces interface-name unit logical-unit-number family inet6 filter] hierarchy levels, the clear firewall filter interface-name command clears the counters for IPv4 bytes and packets but not for IPv6 bytes and packets (in the output from the show firewall filter interface-name command). [PR/229016: This issue has been resolved.]
• If the commit full operation is performed repeatedly, some processes (including the firewall process [dfwd]) might fail to release memory that they have allocated while reading the new configuration. [PR/230772: This issue has been resolved.]

Network Management

• Bridge domain instances are not listed in the VacmContextTable table after a Routing Engine switchover or restart of the SNMP process. [PR/233765: 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 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 an 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 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.]

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 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.]
• While using 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.]