Previous Releases

8.1R3

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

Platform and Infrastructure

• On M320 and T-series routing platforms, when you configure destination class usage (DCU) and port mirroring, port mirroring might stop working. [PR/51916: This issue has been resolved.]
• If you configure the routing platform as a DHCP relay agent, it might incorrectly broadcast the BootReply message (DHCP offer) to the client, regardless of whether the client's Broadcast flag bit is set or not. [PR/74799: This issue has been resolved.]
• 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.]
• If you telnet to the loopback address of a router configured for graceful Routing Engine switchover and switch mastership to the backup Routing Engine, the route to the telnetted host is cloned to the Backup Routing Engine and points to a reject next hop. When mastership switches back to the primary Routing Engine, this reject next hop remains in the routing table and might affect connectivity to the host. [PR/76996: This issue has been resolved.]
• On IQ or IQ2-based PICs, if you include the per-unit-scheduler statement, the system might leak memory when the interface goes down or is deleted from the configuration and added back. [PR/78000: This issue has been resolved.]
• For ATM interfaces, if you issue a ping command between customer-edge (CE) routers in a virtual private LAN service (VPLS) routing instance, sometimes the ping packets might not reach the remote CE router. [PR/80854: This issue has been resolved.]
• When a label-switched path (LSP) flaps or is rerouted because of LSP optimization, the routing platform might stop forwarding flooded virtual private LAN service (VPLS) traffic such as unknown unicast, multicast, or broadcast traffic. The problem can occur if the LSP egress interface is an aggregated interface, the member links of the aggregated interface are located on different Packet Forwarding Engines, and the LSP is configured with fast reroute, as a secondary LSP in standby mode, or with link protection. As a workaround, configure the LSP without fast reroute, link protection, or standby LSP, or create the LSP egress aggregated interface with all member links located on the same Packet Forwarding Engine. [PR/81164: This issue has been resolved.]
• If you include the source-address statement at the [edit system ntp] hierarchy level, the Network Time Protocol (NTP) process might ignore the configured source address and instead use the address of the interface closest to the NTP peer. [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.]
• On M120 Internet routers, large VLAN configurations can 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 JUNOS Release 8.2R1 software, memory buffers might become full and cause a core dump. [PR/95671: 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.]
• With large numbers of next hops, the Enhanced FPC might overflow its stack, stop operating, and restart. [PR/98562: This issue has been resolved.]

User Interface and Configuration

• If you issue multiple, concurrent show configuration commands, the routing platform might dump core in another CLI session that is attempting to commit a configuration. As a workaround, do not issue the show configuration command in another CLI session when you issue the commit command. [PR/79257: This issue has been resolved.]
• RADIUS/TACACS+ authenticated users who are mapped to a local 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

• On J4300 and J6300 Services Routers with a G.SHDSL PIM, at a line rate of 320 Kbps, a ping command might fail to work with an ADTRAN DSLAM. [PR/62177: This issue has been resolved.]
• On J4300 and J6300 Services Routers with a G.SHDSL PIM, at a line rate of 448 Kbps the line flaps and the ping command fails to work with an ADTRAN DSLAM. [PR/62179: This issue has been resolved.]
• For the 320-Kbps and 256-Kbps line rates only, when the software is bringing up the G.SHDSL line with an ADTRAN DSLAM, the line takes more than a minute to negotiate successfully. [PR/62462: This issue has been resolved.]
• On J2300 Services Routers with a G.SHDSL PIM, at a line rate of 320 kbps, a ping command fails to work with an ADTRAN DSLAM. [PR/64727: This issue has been resolved.]
• On J2300 Services Routers with a G.SHDSL PIM, at a line rate of 448 kbps, the line flaps with an ADTRAN DSLAM. [PR/64729: This issue has been resolved.]
• For Gigabit Ethernet and 4-port Fast Ethernet interfaces installed in J4350 and J6350 Services Routers, MAC address filtering is not supported. [PR/70278: This issue has been resolved.]
• When an M40e router chassis repeatedly sends a “failed reading voltage” error message, it might indicate that an incorrect power supply (for example, an M20 router power supply instead of one for an M40e router) is installed. [PR/70868: This issue has been resolved.]
• When you issue the show interfaces descriptions interface-name command with an interface name containing more than 80 characters, the system might dump core. [PR/72155: This issue has been resolved.]
• On non-Enhanced FPCs with STM16 PICs on M160 routers, 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.]
• For redundant Link Services Intelligent Queuing (LSQ) bundles configured on Adaptive Services II PICs, if you test a local loopback or a remote loopback on one of the links in the bundle, throughput for all bundles terminating on the same PIC might be impacted and packets might be dropped. [PR/76650: 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.]
• For Channelized STM1 Intelligent Queuing (IQ) PICs installed in M320 routers, if you activate or deactivate an E1 channel in a link services intelligent queuing interface (LSQ) or redundant LSQ bundle, and then issue the show interfaces extensive command for other E1 channel bundles on the same PIC, the Missing sequence number field might increment in the output of the command. [PR/77592: This issue has been resolved.]
• For 10-port Channelized E1 PICs, if you include the framing g704-no-crc4 statement at the [edit interfaces ds-fpc/pic/port: channel e1-options] hierarchy level, and then upgrade the router to JUNOS Release 8.1R1, the requested framing value might not be set correctly in the system and the Framing field might be listed as g704 in the output of the show interfaces command. [PR/80841: This issue has been resolved.]
• For Ethernet PIMs on J4350 and J6350 routing platforms, when you take the PIM offline and bring it back online, the router can fail and dump core. [PR/81060: This issue has been resolved.]
• On DS0, T1, and E1 interfaces, you might not be able to configure the bandwidth statement. The fix allows you to configure bandwidth for these interfaces once again, but the routing platform does not use the bandwidth value if the interfaces are included in a Multilink PPP (MLPPP) or Multilink Frame Relay (MLFR) bundle. [PR/81827: This issue has been resolved.]
• For redundant link services intelligent queuing (LSQ) interfaces configured on AS PICs, if you try to modify the existing configuration (for example, delete some of the interfaces) when the interfaces are in the process of coming up after an Automatic Protection Switching (APS) switchover, the routing platform might stop operating. [PR/82125: 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.]
• ATM-over-SHDSL interfaces on J-series Services Routers sometimes discard incoming MPLS packets. [PR/94353: This issue has been resolved.]
• If you modify a redundant link services intelligent queuing (rlsq-) interface bundle and run an internal query process at the same time as the bundle modification, the routing platform might stop operating. [PR/94508: This issue has been resolved.]
• When you configure Multilink PPP (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.]
• For aggregated Ethernet interfaces configured with Link Aggregation Control Protocol (LACP), when you delete a logical interface from the aggregated interface and then reconfigure it (remove a unit statement at the [edit interfaces aex] hierarchy level and add it back), the aggregated interface might not come up. As a workaround, deactivate and reactivate the interfaces assigned to the aggregate and commit the configuration. [PR/95015: This issue has been resolved.]
• For Channelized DS3 Intelligent Queuing (IQ) PICs installed in M320 or T-series routing platforms, if you configure Layer 2 circuits over logical interfaces using frame-relay-ccc or frame-relay-tcc encapsulation and data-link connection identifiers (DLCIs) with values of less than 64, the logical interfaces might not transport the Layer 2 circuit traffic. As a workaround, increase the DLCI values to more than 64. [PR/95358: This issue has been resolved.]
• On M7i routers, when you disable the integrated Gigabit Ethernet interface, you might see a ping round-trip time (RTT) delay of about 50 msec. As a workaround, do not disable the interface, but deactivate the configuration for the integrated interface. [PR/95572: This issue has been resolved.]
• If you include the instant-usage-weight-exponent statement at the [edit chassis fpc fpc-slot pic pic-slot red-buffer-occupancy weighted-averaged] hierarchy level, and then take the PIC offline and bring it back online, the chassis process (chassisd) might leak memory. [PR/95964: This issue has been resolved.]
• If you install a first-generation SONET/SDH PIC into an Enhanced II FPC, the FPC might stop operating. [PR/96309: 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 transition down and up even if there is no change in the associated linear-red-profile properties. [PR/96621: This issue has been resolved.]
• On all routing platforms, 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.]
• 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, Point-to-Point Protocol (PPP) keepalives might be lost, and traffic loss might result. [PR/98391: This issue has been resolved.]
• On Gigabit Ethernet interfaces, when the routing platform processes a configuration containing the reject-the-rest toggle option, the device control process (dcd) might dump core. [PR/98972: 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 only happens 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 class-of-service (CoS) bandwidth for the bundle is not applied correctly after the bundle comes back up again. [PR/101119: This issue has been resolved.]

Services Applications

• When you delete a virtual routing instance that includes a services interface and then roll back the configuration, the forwarding table is marked as deleted. For logical services interfaces in any routing instance and in the service set, the key management process (kmd) adds the corresponding decrypt route in the corresponding forwarding table. When you deactivate the routing instance, the corresponding forwarding table is deleted only if all routes in the table are deleted. However, in this case, since the service set still exists, the decrypt routes are not deleted. As a result, the forwarding table is marked as deleted, but is not actually deleted. [PR/63607: This issue has been resolved.]
• Some probe types require that particular options 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.]
• On Adaptive Services PICs, when you apply class-of-service (CoS) marking and reclassification for the SIP application, voice and video packets might be marked incorrectly in terms of direction, initiator, and responder. [PR/77249: 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.]
• For J-series Services Routers, if the do not fragment (DF) bit is set in the IP header for Multilink Point-to-Point (MLPPP) traffic, Compressed Real-Time Transport Protocol (CRTP) does not compress the packet. [PR/95396: This issue has been resolved.]

General Routing

• Routing policy does not properly handle deleting communities from a list of more than 128 communities. [PR/96557: This issue has been resolved.]

Routing Protocols

• If you configure identical static and backup-router prefixes, the routing platform might incorrectly trigger a warning message. [PR/78615: This issue has been resolved.]
• 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.]
• You cannot include the restrict statement at the [edit ospf area-range range] hierarchy level when the area range is 0/0. [PR/79657: This issue has been resolved.]
• BGP is unable to detect the local AS number change for groups configured in a routing instance, when the routing-options configuration for that instance is deactivated. [PR/80097: This issue has been resolved.]
• If you include the path-selection statement at the [edit protocols bgp] hierarchy level, deactivate all neighbors in the BGP group, and then deactivate and reactivate the entire [edit protocols bgp] hierarchy level, the routing protocol process (rpd) might dump core. [PR/95558: This issue has been resolved.]
• When you commit only the [edit routing-options] section of a configuration, changes in the confederation member list are not forwarded to BGP. [PR/96277: This issue has been resolved.]
• If class-of-service based forwarding is configured and the router fails over to the backup Routing Engine, the routing protocol process (rpd) might restart. [PR/98686: This issue has been resolved.]
• If you enable unicast reverse path forwarding (RPF) when a next-table next-hop route is present, the routing protocol process (rpd) might restart repeatedly. [PR/99488: This issue has been resolved.]

MPLS Applications

• If you issue an MPLS traceroute command and the immediate downstream transit node in the LSP path is an M320 or T-series routing platform with an Enhanced FPC, the traceroute might not work if the transit node uses equal-cost multipath (ECMP). [PR/80089: 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.]
• If more than one VPN routing and forwarding (VRF) routing instance is configured with the same vrf-target statement, a routing instance can fail to be deleted properly from the routing protocol process (rpd). As a workaround, remove the reused vrf-target statement from all routing instances. In addition, if you change the route distinguisher in the routing instance configuration, prefixes added to the routing table for the routing instance might not be propagated to the forwarding table. As a workaround, change the name of the affected routing instance. [PR/80933: This issue has been resolved.]
• If you configure VPLS with an export policy that matches one of two communities, remote provider edge (PE) router prefixes might appear in the bgp.l2vpn.0 table but not in the VPLS instance routing table. Also, the output of the show vpls connections command might indicate that no VPLS connections have been established. [PR/82517: This issue has been resolved.]
• In earlier versions of JUNOS Release 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.]
• If you enable LSI-based VPLS by including the no-tunnel-services statement at the [edit routing-instances instance-name protocols vpls] hierarchy level, you might not be able to use the default class-of-service (CoS) classifier or specify a classifier manually. [PR/80870: This issue has been resolved.]
• Insufficient memory was allocated for forwarding-class configuration data. As a result, trying to access information might exceed the allocation and cause the CoS process (cosd) to terminate unexpectedly. [PR/95404: 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.]

Forwarding and Sampling

• On a T640 routing node, the sampling process (sampled) might write to a sampling output file inconsistently or might fail to export cflowd records as expected. As a workaround, restart the sampling process. [PR/31021: This issue has been resolved.]
• When you configure host sampling, in rare circumstances the Packet Forwarding Engine might 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.]
• 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.]
• 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.]

Network Management

• If there is a communication failure when the routing protocol process (rpd) is processing a Simple Network Management Protocol (SNMP) request from the SNMP process (snmpd), the routing protocol process might dump core. [PR/69969: This issue has been resolved.]
• If the router receives a series of Internet Control Message Protocol (ICMP) port unreachable messages (such as a response to a system log message request when the system log message process is not running) over an MPLS link using RSVP, and you issue the monitor traffic interface extensive command, the tcpdump application might enter an infinite loop, consume large amounts of CPU, and cause the system to hang. [PR/81607: 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.]
• Taking a PIC offline and bringing it back online causes the chassis process (chassisd) to leak memory. [PR/97479: 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.]

8.1R2

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

Platform and Infrastructure

• When you include the explicit-null statement at the [edit protocols mpls], [edit protocols ldp], or [edit protocols bgp group group-name neighbor ip-address family inet labeled-unicast] hierarchy level, the default time-to-live (TTL) value might not be copied correctly from an MPLS null label to an IP packet header. [PR/44814: This issue has been resolved.]
• If you configure the log-out-on-disconnect statement at the [edit system ports] hierarchy level and the console statement at the [edit system syslog] hierarchy level, and you remove and replace the console cable, the console port might lock. [PR/69459: This issue has been resolved.]
• If you configure the routing platform as a DHCP relay agent, it might incorrectly broadcast the BootReply message (DHCP offer) to the client, regardless of whether the client's Broadcast flag bit is set or not. [PR/74799: This issue has been resolved.]
• If you telnet to the loopback address of a router configured for graceful Routing Engine switchover and switch mastership to the backup Routing Engine, the route to the telnetted host is cloned to the Backup Routing Engine and points to a reject next hop. When mastership switches back to the primary Routing Engine, this reject next hop remains in the routing table and might affect connectivity to the host. [PR/76996: This issue has been resolved.]
• When the Self-Monitoring Analysis and Reporting Technology System (SMART) process (smartd) performs an automatic power check every 20 seconds to determine if a disk drive is in standby mode, this check might cause some Routing Engine hard drives to become unresponsive. To resolve this issue, the automatic power checking function has been disabled by default. [PR/77503: This issue has been resolved.]
• For M160 routers, if you configure IS-IS and graceful Routing Engine switchover (GRES), and then take the first Switching and Forwarding Module (SFM) in the chassis offline, IS-IS neighbor adjacencies might transition down and up. [PR/77771: This issue has been resolved.]
• When you configure IPv6 on an interface and the interface comes up late in the duplicate address detection (DAD) retry cycle, the IPv6 address might remain tentative. [PR/78212: This issue has been resolved.]
• M7i and M10i routers containing a Compact Forwarding Engine Board (CFEB) with 256 MB of DRAM might not operate properly with JUNOS Release 8.1R1. [PR/78877: This issue has been resolved.]
• When you configure real-time performance monitoring (RPM) for BGP, the output of the show services rpm probe-results command might not display all of the information for all routing instances. [PR/78888: This issue has been resolved.]
• On J20 GGSN routers, if you delete the instance-type statement at the [edit routing-instances instance-name] hierarchy level and commit the configuration, the routing protocol process (rpd) might dump core. [PR/79264: This issue has been resolved.]
• For Adaptive Services and MultiServices PICs, you might not be able to transport IPv6 packets larger than 1158 bytes through an IPSec tunnel using default values. As a workaround, increase the maximum transmission unit (MTU) of the IPSec tunnel. [PR/79442: This issue has been resolved.]
• In a virtual private LAN service (VPLS) network, if you use an aggregated Ethernet interface to connect a provider edge (PE) router to a provider core (P) router, VPLS traffic might leak between VPLS instances. Additionally, if you add or remove member links from the aggregate bundle, traffic might be forwarded with the wrong VPN label and be placed into the wrong VPLS instance. [PR/79702: This issue has been resolved.]
• After you issue the request chassis routing-engine diagnostics command with the compact-flash, hard-disk or all option, the memory utilization of the Routing Engine increases significantly. The amount of increase depends on the total size of the files located on the compact flash and the hard disk. [PR/80095: This issue has been resolved.]
• The routing platform currently does not support indexed next-hop load balancing for IPv4 to MPLS next hops. [PR/80261: This issue has been resolved.]
• On MultiServices PICs, if you restart the routing platform when link services intelligent queuing (LSQ) interfaces are carrying a heavy traffic load, the PIC might stop functioning. As a workaround, stop the traffic, restart the router, and then resume the traffic. Similarly, if you configure Network Address Translation (NAT) on the MultiServices PIC when there are more than 30,000 flows per second, the PIC might stop operating. [PR/80940: This issue has been resolved.]

User Interface and Configuration

• If the software cannot find a referenced policy, the routing protocol process (rpd) might dump core. [PR/67098: This issue has been resolved.]
• If you issue the load update command and there are duplicate elements in a BGP import or export policy, the system might resequence those elements in the configuration. [PR/76909: This issue has been resolved.]
• When you use JUNOScript to change or access configuration attributes while the JUNOS software is performing an automatic rollback, the management process (mgd) might dump core. [PR/78791: This issue has been resolved.]
• If a comment is present at the end of an XML configuration file, the commit process might fail, in which case the system issues an “internal communication failure” message. [PR/80464: This issue has been resolved.]
• If you issue the replace pattern command to modify a statement that offers a choice of several values (such as a route-filter option in a policy statement) and the new pattern is the same as the old pattern, the management process (mgd) might dump core. [PR/81347: This issue has been resolved.]

Interfaces and Chassis

• When an interface goes down, the resulting system log message might not contain enough information concerning the cause (such as specific alarms for SONET/SDH interfaces). [PR/22776: This issue has been resolved.]
• For link services intelligent queuing (LSQ) interfaces, when you deactivate and reactivate a remote LSQ interface, the show interfaces lsq-fpc/pic/port extensive command might display erroneous counter values for the LSQ bundle. [PR/54855: This issue has been resolved.]
• When a multicast next hop is added and deleted, the packet and byte rate counters are not zeroed out. These counters continue to show the old values. [PR/68074: This issue has been resolved.]
• For Gigabit Ethernet and 4-port Fast Ethernet interfaces installed in J6350 and J4350 Services Routers, MAC address filtering is not supported. [PR/70278: This issue has been resolved.]
• For 2-port Channelized T1/E1 PIMs in J-series Services Routers, BERT is not supported for JUNOS Release 8.1R1. [PR/71435: This issue has been resolved.]
• On M-series and T-series routing platforms, when a link participating in a multilink bundle transitions down and up (for example, when a physical link fails), the multilink bundle might become unresponsive and affect the traffic flowing on all the links in the bundle. [PR/72151: This issue has been resolved.]
• For J4350 and J6350 Services Routers, if you use dynamic end points to establish a large number of IPSec tunnels in a single service set, some tunnels do not become established and some might transition down and up. [PR/76475: This issue has been resolved.]
• On J-series Services Routers, if you modify your configuration to move a manual IPSec tunnel from a routing instance into the main router, traffic might not travel over the tunnel in the main router. [PR/76643: This issue has been resolved.]
• For redundant Link Services Intelligent Queuing (LSQ) bundles configured on Adaptive Services II PICs, if you test a local loopback or a remote loopback on one of the links in the bundle, throughput for all bundles terminating on the same PIC might be impacted and packets might be dropped. [PR/76650: This issue has been resolved.]
• On M120 routers, when an FPC is no longer mapped to a Forwarding Engine Board (FEB) because the FEB was taken offline or removed, the associated interfaces appear to be available, when in fact they are not available and should be marked as unusable. [PR/76846: This issue has been resolved.]
• On Fast Ethernet interfaces installed in J-series Services Routers, if the interface receives traffic with a destination MAC address set to broadcast (ff:ff:ff:ff:ff:ff), it might handle this traffic as keepalive traffic and limit the throughput to ~2500 packets per second. [PR/77376: This issue has been resolved.]
• For intelligent queuing (IQ) interfaces, the output of the show interfaces extensive command incorrectly displays the class-of-service (CoS) queue transmit rates based on the total bandwidth of the interface rather than the shaping rate of the interface. [PR/77483: This issue has been resolved.]
• If you commit a configuration that produces a warning message, the XML display output for that warning might use an <xnm:error> tag instead of the expected <xnm:warning> tag. [PR/78338: This issue has been resolved.]
• Even when you do not configure aggregated Ethernet interfaces, the Link Aggregation Control Protocol process (lacpd) might consume excessive amounts of CPU time and memory. [PR/78739: This issue has been resolved.]
• For AS PICs or MultiServices PICs configured with redundant link services intelligent queuing (LSQ) interfaces, when the redundant PICs are congested with a high traffic volume, the rlsq- interface might enter a “both down” state. As a workaround, take both PICs offline and bring them back online to clear this state. [PR/78742: This issue has been resolved.]
• For link services intelligent queuing (LSQ) interfaces configured on Adaptive Services and MultiServices PICs, when you reboot the PIC, multilink class counters for active classes might not be cleared and the output of the show interfaces lsq-fpc/pic/port command might display incorrect statistics for those counters. [PR/79080: This issue has been resolved.]
• When you configure the routing platform as data terminal equipment (DTE) for a Frame Relay Local Management Interface (LMI) and a circuit goes down and comes back up (flaps), some data-link connection identifiers (DLCIs) configured on the circuit might remain in the DOWN state. As a workaround, disable and reenable these DLCIs. [PR/79208: This issue has been resolved.]
• On a 10-port Gigabit Ethernet PIC, if you configure extended-vlan-vpls encapsulation on multiple logical interfaces for one of the ports and then configure a second port with a different encapsulation type, the VPLS enable port might reconfigure the MAC filter and drop the VPLS connections. As a workaround, deactivate the port containing the VPLS logical interfaces and then reenable it. [PR/81069: This issue has been resolved.]

Services Applications

• When you configure Network Address Translation (NAT) pool addresses with the same prefix as the address for an interface on which a service set has been applied, and you configure NAT in the output direction, the routing protocol process (rpd) might not respond to ARP requests for the NAT addresses. [PR/67901: This issue has been resolved.]
• For link services intelligent queuing (LSQ) interfaces on AS PICs or MultiServices PICs, when you configure an LSQ interface as an independent interface and also as a redundant LSQ primary or secondary interface, the IP Control Protocol process is not enabled. As a workaround, do not configure an LSQ interface individually when the same interface must be part of a redundant LSQ bundle. [PR/73496: This issue has been resolved.]
• For J-series Services Routers, if you configure a real-time performance monitoring (RPM) probe and include the hardware-timestamp statement at the [edit services rpm probe owner-name test test-name] hierarchy level, the round-trip time for a UDP ping does not improve. [PR/75467: This issue has been resolved.]
• When you configure a stateful firewall for an AS PIC or MultiServices PIC and issue the show services stateful-firewall statistics command, the output might display a larger value for the “Reject counters” field than the number of packets actually rejected by the stateful firewall rule. [PR/75593: This issue has been resolved.]
• On Adaptive Services PICs configured with a stateful firewall, a packet with overlapping TCP fragments might cause the PIC to stop operating. [PR/79443: This issue has been resolved.]
• For Adaptive Services PICs configured for Layer 2 Tunneling Protocol (L2TP), when a bundle is deleted and there are outstanding fragments to be transmitted in a Multilink PPP (MLPPP) session, the PIC might stop operating. [PR/80540: This issue has been resolved.]

Routing Protocols

• In a fully meshed BGP network using route reflectors and route target filtering, if there are multiple routes for the same route target or if you configure the advertise-default statement and there is at least one received default route target route, VPN routes might not be sent to all BGP neighbors who requested them. [PR/74517: This issue has been resolved.]
• The output from the show route label-switched-path command might not display all routes that are using an LSP as a next hop. [PR/78875: This issue has been resolved.]
• If there are multiple BGP routes to the same prefix which are received from different neighbor autonomous systems and which differ only in their IGP cost to the next hop, BGP might select the wrong route as the best route. [PR/78975: This issue has been resolved.]
• When you configure Virtual Router Redundancy Protocol (VRRP) on an interface in a routing instance, and you include the accept-data statement at the [edit interfaces interface-name unit logical-unit-number family inet address ip-address vrrp-group group-number] hierarchy level, and if no router ID is configured at the [edit routing-instances instance-name routing-options] hierarchy level in the routing instance, the VRRP virtual IP address might be selected as the router ID for the routing instance. [PR/79825: This issue has been resolved.]

MPLS Applications

• If the traffic rate for an ingress MPLS LSP exceeds 2 Gbps and you issue the monitor label-switched-path command, the “Bits per second (bps)” field in the output might display a negative value. [PR/77924: This issue has been resolved.]
• When you configure the graceful-restart statement at the [edit routing-options] hierarchy level and the routing protocol process (rpd) restarts twice in a short time period, the routing protocol process might dump core. [PR/78539: This issue has been resolved.]
• When an RSVP session goes down and comes back up (flaps), LSP counters might not be reset to zero. [PR/79295: This issue has been resolved.]
• If you issue an MPLS traceroute command and the immediate downstream transit node in the LSP path is an M320 or T-series routing platform with an Enhanced FPC, the traceroute operation might not work if the transit node uses equal cost multipath (ECMP). [PR/80089: This issue has been resolved.]

VPNs

• If you configure two or more MPLS LSPs, create a VPLS instance, and configure a policy to send the VPLS traffic over one of the LSPs, and if the policy contains the from rib mpls.0 match condition and is applied at the [edit routing-options forwarding-table export] hierarchy level, the policy might not match the VPLS routes. [PR/80585: This issue has been resolved.]

Class of Service

• On M320 and T640 routers with Gigabit Ethernet IQ2 PICs, egress class-of-service queue drops might be not be commensurate with transmit rates. As a workaround, configure the delay-buffer-rate statement at the [edit class-of-service traffic-control-profiles profile-name] hierarchy level, or configure the q-pic-large-buffer statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level. [PR/76994: This issue has been resolved.]
• For redundant link services intelligent queuing (LSQ) interfaces configured on AS PICs, if you issue the show interfaces queue command for the multilink PPP (MLPPP) bundles, the output does not show random early detection (RED) drops broken down into individual drop profiles (such as low and high). [PR/77059: This issue has been resolved.]

Forwarding and Sampling

• If you configure Routing Engine-based sampling on a Monitoring Services or Adaptive Services II PIC, the output of a cflowd record might show the destination port field for Internet Control Message Protocol (ICMP) as 0. As a workaround, configure PIC-based sampling. [PR/70906: This issue has been resolved.]
• When port is used with either source-port or destination-port in the same term of a match condition in a firewall filter, the system does not generate an error when you issue a commit command. [PR/76674: This issue has been resolved.]
• When a forwarding next hop is changed from the Ethernet Management interface (fxp0) to a transit interface, an indirect next hop is created for each route that shares the same next hop. As a workaround, do not use the Ethernet Management interface as a forwarding next hop for transit traffic. [PR/80139: This issue has been resolved.]
• On T-series routing platforms, if you include the from traffic-class match condition in an IPv6 firewall filter, the filter might not work as expected. [PR/80359: This issue has been resolved.]

Network Management

• On AS PICs, if you change or rename a service set, the output of the show snmp mib walk jnxSpSvcSet command does not display the correct service set name. As a workaround, issue the restart adpative-services command before reissuing the show snmp mib walk jnxSpSvcSet command. [PR/78130: This issue has been resolved.]
• The values returned for the ifChassisFpc MIB might not match the corresponding index values used in the Juniper Networks enterprise chassis MIB (for example, jnxContentsDescr). [PR/78429: This issue has been resolved.]
• When a large number of trap packets are sent in a short interval and the packets are kept in the trap queue, the SNMP process (snmpd) runs out of memory. [PR/78727: This issue has been resolved.]

8.1R1

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

Platform and Infrastructure

• On M7i and M10i routing platforms, a component of the CFEB is not initialized correctly, which might lead to data corruption. Contributing factors are high CPU load on the PFE or high ambient temperature. [PR/70882: This issue has been resolved.]
• On J20 routers, when successive system log messages are displayed on the console, traffic might stop being forwarded. As a workaround, configure a delay of 2 seconds between successive system log messages. [PR/72851: This issue has been resolved.]
• On a J6300 Services Router with dual power supplies, when one of the power supplies is removed, no log message is generated to record the event. [PR/74261: This issue has been resolved.]
• If a malformed MPLS packet (one in which the MPLS header does not contain a nonzero S-bit to terminate the label stack) is delivered to the Routing Engine, the kernel might reset unexpectedly. [PR/74568: This issue has been resolved.]
• On ATM2 IQ logical interfaces with Layer 2 circuits configured, if you issue a statistics request, the request might not work. In addition, a related memory leak might eventually cause a kernel panic. [PR/74714: This issue has been resolved.]
• On J-series Services Routers, if you configure next-hop sampling, there might be a memory leak in the sample process (sampled). [PR/74718: This issue has been resolved.]
• When a control plane link goes down on an internal interface, the control plane neighbors are not removed immediately, causing the control plane protocol to disconnect. [PR/74840: This issue has been resolved.]
• On a TX matrix routing node, if you request information from the PFE (including interface statistics, class-of-service [CoS] statistics, MPLS statistics, or firewall statistics, as well as using any show pfe command), a memory leak can occur on the LCC. Eventually the LCC is unable to respond to any further requests, and the LCC will reload. [PR/75089: This issue has been resolved.]
• On Gigabit Ethernet interfaces configured with flexible Ethernet services encapsulation, if you configure proxy Address Resolution Protocol (ARP) on a VLAN-based translational cross-connect (TCC) connection and include a MAC address and an IP address for the remote address, the router might not reply to ARP requests. As a workaround, remove the MAC address from the [edit ge-fpc/pic/port unit logical-unit-number family tcc remote] hierarchy level and configure static ARP on the remote device. [PR/76182: This issue has been resolved.]

User Interface and Configuration

• When a configuration change is applied using the J-Web Configuration > View and Edit > Edit Configuration Text and Upload Configuration menu option, an empty red error box appears. However, there are no errors and the commit succeeds. [PR/72601: This issue has been resolved.]
• An error in the commit script handling logic is causing the cscript process to crash with a SIGSEGV error. [PR/75156: This issue has been resolved.]
• If you issue the configure private command and then configure privileges for a user at the [edit system login user] hierarchy level, a user ID (UID) might not be assigned to the user. [PR/75376: This issue has been resolved.]
• The parsing of some JUNOScript elements with a delete flag set is not working. [PR/77878: This issue has been resolved.]

Interfaces and Chassis

• On 10-Gigabit Ethernet PICs, if there are minor problems with the connection, informational messages containing ".pm3392" might be generated continuously and might fill up the system log. [PR/40785: This issue has been resolved.]
• On 1-port 10-Gigabit Ethernet PICs with XENPAK installed in an M320 or T-series routing platform, after the FPC is restarted or the RE is rebooted, the following error message might be logged: "XGE(x/y): runaway interrupt count (1000001)". After this message, the interrupt on this PIC is disabled. As a result, it might take up to one second for the routing platform to detect a LINK fault and bring down the interface on the PIC. As a workaround, take the PIC offline and then bring it back online by issuing the request chassis pic fpc-slot fpc-slot pic-slot pic-slot offline | online command once. [PR/57376: This issue has been resolved.]
• On a Channelized E1 Intelligent Queuing (IQ) PIC, when you configure Frame Relay encapsulation on a point-to-multipoint interface and issue the ping command, the ping operation might fail. As a workaround, reconfigure the interface as a point-to-point interface. [PR/61074: This issue has been resolved.]
• If the chassis process (chassisd) is restarted, the generated hardware database does not contain entries for PICs, because the entry corresponding to the FPCs that hold the PICs has not been created. [PR/68753: This issue has been resolved.]
• On Gigabit Ethernet interfaces installed in J4350 and J6350 Services Routers, autonegotiation needs to be manually disabled for the manual speed and duplex settings to be applied. [PR/69870: This issue has been resolved.]
• For Gigabit Ethernet interfaces installed in J4350 and J6350 Services Routers, the default behavior is to autonegotiate. If autonegotiation is on, the system disregards any manual settings for link mode and speed. When you manually configure the link mode or speed, you must also manually disable autonegotiation. [PR/70133: This issue has been resolved.]
• For link services intelligent queuing (LSQ) interfaces on AS PICs, if there are several missing sequence number drops within the bundles, all bundles on the LSQ interface might stop forwarding traffic for a period of time. As a workaround, configure a drop-timeout of 100 msec on all bundles to reduce the frequency of forwarding interruption. [PR/70798: This issue has been resolved.]
• For Gigabit Ethernet interfaces on J4350 and J6350 Services Routers, the command-line interface (CLI) might indicate you can configure a maximum transmission unit (MTU) of 9192 bytes. The actual maximum configurable MTU value has been changed to 9018 bytes. [PR/71117: This issue has been resolved.]
• When a J4350 or J6350 router receives a frame on one of its built-in Ethernet interfaces (ge-0/0/0 to ge-0/0/3) that is connected to a shared LAN infrastructure, a frame that is not destined for this interface's MAC address is still accepted and might cause erratic ICMP replies. [PR/73928: This issue has been resolved.]
• When you modify the Virtual Router Redundancy Protocol (VRRP) priority setting and commit the configuration, the VRRP process (vrrpd) might dump core. [PR/74180: This issue has been resolved.]
• On J-series routers, you cannot configure clocking on E1 ports using the group configuration. The workaround is to execute a load merge command instead of using the group configuration. This issue is not seen on M-series or T-series routers. [PR/74254: This issue has been resolved.]
• On routers with Gigabit Ethernet interfaces, the router will reply to gratuitous ARP requests if proxy-ARP is enabled, even though the no-gratuitous-arp-request statement is configured at the [edit interfaces] hierarchy level. [PR/74993: This issue has been resolved.]
• On aggregated Ethernet interfaces, if you include the proxy-arp statement at the [edit interfaces ae0 unit logical-unit-number] hierarchy level and the no-gratuitous-arp-request statement at the [edit interfaces ae0] hierarchy level, the routing platform might still reply to gratuitous Address Resolution Protocol (ARP) requests. [PR/74995: This issue has been resolved.]
• Fragmentation maps or class-of-service (CoS) maps are not applied to newly configured redundant link services queuing (rlsq) interfaces. The workaround is to deactivate and then reactivate the entire rlsq bundle. [PR/75986: This issue has been resolved.]
• For link services intelligent queuing (LSQ) interfaces on AS PICs, when you upgrade to JUNOS Release 8.0R1 and later, the throughput for multilink PPP (MLPPP) bundles might be reduced. [PR/76160: This issue has been resolved.]
• On Channelized E1 Intelligent Queuing (IQ) and Channelized STM1 IQ PICs, if you configure E1 channels in unframed mode, a DS1 loss of frame (LOF) alarm appears in the output of the show interfaces extensive command and you might not be able to clear this alarm. [PR/77027: This issue has been resolved.]
• On routing platforms with more than 40 EBGP peers, if each peer has a group with unique import and export policies and you make a configuration change, the route download performance might be reduced. [PR/77968: This issue has been resolved.]

Services Applications

• The Layer 2 Tunneling Protocol (L2TP) process gets into an infinite loop leading to high CPU utilization when IPv6 packets related to RADIUS are processed by the protocol stack. [PR/72588: This issue has been resolved.]
• When you configure an Adaptive Services PIC with stateful firewall rules, Network Address Translation (NAT) services, and the NetShow application layer gateway, the PIC might stop functioning. [PR/73745: This issue has been resolved.]
• On Adaptive Services PICs, if you configure multilink PPP (MLPPP) over multiple Layer 2 Tunneling Protocol (L2TP) tunnels, a maximum of two L2TP links can be established. [PR/74674: This issue has been resolved.]
• On J-series Services Routers, the output from the show services accounting aggregation source-destination-prefix command does not display the inbound and outbound interface of the flow, or the flow count, packet count, and byte count. [PR/75306: This issue has been resolved.]

General Routing

• It is possible to configure a static IPv6 route with a link-local address without also configuring a next-hop interface. You must now include the qualified-next-hop statement at the [edit routing-options static route destination] hierarchy level. [PR/71217: This issue has been resolved.]

Routing Protocols

• In a PIM dense-mode network, the time-to-live (TTL) value for unicast PIM Graft messages might be set to a value of 64 instead of the expected value of 1. [PR/70123: This issue has been resolved.]
• On M-series and T-series routing platforms, when IS-IS adjacencies are present, the routing protocol process (rpd) might stop operating in some cases. [PR/74496: This issue has been resolved.]
• When you configure a multicast distribution tree (MDT) group, the range of 224/4 through 224/32 might not be accepted as a valid MDT group range. [PR/75318: This issue has been resolved.]
• When BGP is configured with prepended AS paths, the routing protocol process (rpd) might stop functioning. [PR/75325: This issue has been resolved.]
• There was no check to see if the MSDP SA received has a valid group or source address. On processing an SA received with group address 0, the routing protocol process (rpd) crashes. [PR/75451: This issue has been resolved.]
• If you configure a multicast distribution tree (MDT) in a multicast over Layer 3 VPN environment, and then a multicast neighbor is lost before a prune message can be resolved, the routing protocol process (rpd) might use a significant amount of CPU processing power and cause the routing platform to become unresponsive and drop all multicast adjacencies. [PR/75460: This issue has been resolved.]
• When you configure IS-IS and include the maximum-routes statement at the [edit routing-options] hierarchy level, the maximum routes value might not be implemented by the JUNOS software. [PR/75897: This issue has been resolved.]
• If a routing platform running IS-IS receives a link-state PDU fragment 0 with a valid IS type, the routing platform might still check the IS type field in the header of all subsequent fragments and drop fragments containing invalid IS types. [PR/76250: This issue has been resolved.]
• Creating a multicast tunnel (mtun) interface for a VRF instance without an IP address on the loopback interface causes the self-NBR's IP address on the mtun interface to be set incorrectly, which causes the PIM asserts to malfunction. [PR/76501: This issue has been resolved.]

MPLS Applications

• If a pathtear message is sent after the Link Management Protocol (LMP) releases the label, the upstream label object is missing from the pathtear message. [PR/68124: This issue has been resolved.]
• When you configure node-link protection and an RSVP authentication key on an interface, and the label-switched path (LSP) traffic switches over to the bypass LSP, the authentication key might prevent the backup LSP from being established. [PR/72776: This issue has been resolved.]
• The RSVP default maximum session limit has been increased from 50,000 to 100,000 sessions. [PR/72854: This issue has been resolved.]
• When you configure an IPv6 static route with a point-to-multipoint label-switched path (LSP) as the next hop, the routing protocol process (rpd) might stop operating. [PR/75284: This issue has been resolved.]
• If you include the include-all and include-any statements at the [edit protocols mpls label-switched-path lsp-name fast-reroute] hierarchy level, Constrained Shortest Path First (CSPF) reoptimization might not work as expected. [PR/75578: This issue has been resolved.]

VPNs

• When you rename the Layer 2 circuit interface that is being used for local switching, the renamed interface is not used and the existing interface is changed to the down state. As a workaround, delete the local-switching interface at the [edit protocols l2circuit local-switching] hierarchy level and reconfigure it with the new interface. [PR/65598: This issue has been resolved.]
• Virtual private LAN service (VPLS) might not work reliably in a logical router. [PR/72753: This issue has been resolved.]
• 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.]

Class of Service

• When you use a tunnel PIC inside a VRF, traffic is incorrectly mapped to four queues on the VRF egress interface because VT interfaces are treated as supporting restricted queues, rather than the configured queue number. [PR/72455: This issue has been resolved.]
• On 1-port OC12, 1-port OC48, 1-port OC192, and 1-port OC768 SONET/SDH PICs installed in M320 and T-series routing platforms, when you configure the no-concatenate statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level, some channels might not forward traffic. As a workaround, restart the FPC after you configure the no-concatenate statement. [PR/75383: This issue has been resolved.]
• When you reload a routing platform that contains a Link Services PIC, the link services interfaces might revert to the default scheduler map instead of the user-configured scheduler map. As a workaround, configure the scheduler map on all interfaces generated by the Link Services PIC (including all associated tunnel interfaces). [PR/76012: This issue has been resolved.]
• If tricolor marking is turned on for M320 and T-series routing platforms and the user has RED profiles configured for some of the queues, the bandwidth and buffer parameters might not get programmed correctly, resulting in unexpected packet loss and delay [PR/77897: This issue has been resolved.]

Routing Policy and Firewall Filters

• On routing platforms with more than 40 EBGP peers, if each peer has a group with unique import and export policies and you make a configuration change, the route download performance might be reduced. [PR/68243: This issue has been resolved.]
• The interface statement at the [edit firewall filter filter-name term term-name from] hierarchy level is not fully supported. If you include the interface statement as a match condition in a firewall filter that has already been compiled, it might not work properly. [PR/77801: This issue has been resolved.]
• The interface statement at the [edit firewall family any filter filter-name term term-name from] hierarchy level is not fully supported. If you include the interface statement as a match condition in a very large firewall filter, apply the filter to a loopback interface, and the associated interfaces transition down and up frequently, these conditions might cause excessive CPU load on the Routing Engine. [PR/72269: This issue has been resolved.]

Network Management

• When a router is configured to simultaneously send SNMPv1, SNMPv2c, and SNMPv3 traps, SNMPv3 and SNMPv2c routing and MPLS traps are not sent. [PR/74181: This issue has been resolved.]