[ Contents] [ Prev] [ Next] [ Report an Error]

Previous Releases

Release 9.1R3

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

Software Installation

When a PIC that is not supported by the JUNOS software is installed in an ISSU-capable router, the PIC is flagged as incompatible for an ISSU and the ISSU process attempts to take the PIC offline. The offline attempt fails and the ISSU process is aborted. [PR/280023: This issue has been resolved.]
On an M320 router, when you perform an in-service software upgrade (ISSU), firewall filter statistics might not be restored properly. [PR/286413: This issue has been resolved.]
When a hard disk is partitioned, the /var/empty directory might not be created. As a result, the router does not accept SSH connections. As a workaround, use the mkdir command to create the /var/empty directory. [PR/290064: This issue has been resolved.]

Platform and Infrastructure

If you incorrectly configure an aggregate interface, a physical interface does not get added into the aggregate bundle even if you have corrected the configuration. [PR/69348: This issue has been resolved.]
The interface and interface-set match criteria in a firewall do not apply correctly for packets with local destinations. [PR/69648: This issue has been resolved.]
When a packet’s outer label is set to explicit null and the S bit is not set, the LSP ping command does not work. The JUNOS software does not comply with RFC 4182, Removing a Restriction on the use of MPLS Explicit NULL. [PR/74963: This issue has been resolved.]
On M7i and M10i routers, when the system log for the CFEB becomes full, additional messages are discarded instead of overwriting the oldest messages in the log. [PR/79128: This issue has been resolved.]
If you configure a policer for BGP traffic and a new BGP neighbor is added, it might cause other established BGP sessions to flap. [PR/80599: This issue has been resolved.]
When IPSec is configured on a logical interface and the protocol family is IPv6, graceful Routing Engine switchover (GRES) might fail if an MTU change is attempted on that interface. [PR/230128: This issue has been resolved.]
When IRB is configured, the MX:ICHIP log error message is generated. [PR/259472: This issue has been resolved.]
If you switch Routing Engines when graceful Routing Engine switchover and IPv6 are enabled, aggregated Ethernet interfaces go offline. [PR/262137: This issue has been resolved.]
When you configure aggregated interfaces as core-facing links, translational cross-connect (TCC) might not work properly. [PR/267867: This issue has been resolved.]
When you configure the mirror-flash-on-disk statement at the [edit system] hierarchy level, the functionality does not work properly. [PR/268474: This issue has been resolved.]
When you partition the hard drive after upgrading the compact flash, the partition sizes in some cases received slightly incorrect values as a result of bsdlabel behavior. This prevents mirror-flash-on-disk from working properly. [PR/270154: This issue has been resolved.]
On M120, M320, and MX960 routers, when you configure override input packet classification, the feature might not work. [PR/271660: This issue has been resolved.]
On MX-series Ethernet Services routers, if a label-switched interface (LSI) is enabled for an xe member link that is part of an aggregated Ethernet (ae) interface, the xe interface statistics are counted twice. [PR/274396: This issue has been resolved.]
On MX-series routers, when unicast RPF is configured on an interface (the rpf-check statement is included at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level), the DPC that houses the interface might generate a core file. [PR/275466: This issue has been resolved.]
In JUNOS Release 9.0 and later, the multicast snooping process (snoopd) leaks memory even if it is not configured. As a workaround, disable the process if it is not required. [PR/279378: This issue has been resolved.]
In JUNOS Release 8.5 and later, on systems with unnecessary traceoptions enabled, or other configurations that cause high levels of hard drive activity, the Routing Engine might reset with a “watchdog timeout” error. No coredump is generated. As a workaround, change the router’s configuration to eliminate unnecessary traceoptions and to minimize other hard disk drive activity. Customers running into this issue are encouraged to upgrade to a JUNOS release containing the fix. For a specific release information, please contact the Juniper Networks Technical Assistance Center (JTAC). [PR/288011: This issue has been resolved.]
By default, Layer 2 address learning process (l2ald) turns on debug tracing without a traceoptions configuration, which might slow down the route update process to the Packet Forwarding Engine. [PR/290540: This issue has been resolved.]
On a Routing Engine of type RE-3.0 (as reported by the show chassis hardware command) with a 1-GB compact flash card, issuing the request system snapshot command might corrupt one or more JUNOS package files in the /altroot/packages directory. [PR/291295: This issue has been resolved.]
When you delete an interface with a firewall filter assigned to it and commit the configuration while filter counters are requested, the router might stop functioning. [PR/292267: This issue has been resolved.]
In an environment with many active multicast routes and one or more aggregated interfaces as downstream interface, when an aggregated interface flaps or an FPC containing an aggregated interface restarts, the kernel might restart unexpectedly. This issue is seen in networks with greater than 1000 multicast routes. The chance of kernel restarts increases as the number of multicast routes increases or the number of downstream aggregated interfaces increases. [PR/292521: This issue has been resolved.]
If you switch Routing Engines when graceful Routing Engine switchover is enabled, and do so multiple times with a thousand of multicast sessions activated over aggregated interfaces, the FPC could reboot with a core dump. [PR/292530: 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/293212: This issue has been resolved.]
When a packet larger than the IP MTU size is transmitted, it is registered as a microcode error rather than an MTU error. [PR/294485: This issue has been resolved.]
When you take offline a T640 routing node that has an aggregated Ethernet member link, multicast traffic does not detour to another link. [PR/294732: This issue has been resolved.]
When a Multilink Point-to-Point Protocol (MLPPP) link is incorrectly added to a Multilink Frame Relay (MLFR) bundle, the kernel resets unexpectedly. [PR/294885: This issue has been resolved.]
When an AS or MS PIC is configured as the tunnel interface, IPv6 multicast does not work over IP. The Tunnel PIC does not have this problem. [PR/296352: This issue has been resolved.]
When an aggregate interface goes down and at the same time there are route updates to the PFE involving the same aggregate interface, the PFE update may fail. These failed route updates are not added back even when the aggregate interface comes up. To recover from this situation, the routes (reported in the syslog) not added into the PFE need to get deleted and added again. [PR/296439: This issue has been resolved.]
On a router configured with multicast next hops, when an aggregated SONET or aggregated Ethernet interface goes down and comes back up, the kernel might generate a core file and restart. [PR/298073: This issue has been resolved.]
An MPLS frame with an explicit NULL label designated for the Routing Engine might be dropped by the Packet Forwarding Engine. [PR/298967: This issue has been resolved.]
For individual T1 links in an MLPPP bundle, the counts of input bytes and input packets are not reported correctly in the "Traffic statistics" section of the output from the monitor interface t1-fpc/pic/port command. [PR/299688: This issue has been resolved.]
On MX-series routers, VLAN mapping over Ethernet CCC interface switching causes IS-IS to drop packets. [PR/300163: This issue has been resolved.]
On M320 and T-series routing platforms, when member links of a Multilink Frame Relay bundle go down and come back up, an FPC in which a Link Services Queuing (LSQ) PIC is installed might stop forwarding traffic and need to be rebooted. As a workaround, install the PICs with the member links and the LSQ PIC in the same FPC. [PR/300331: This issue has been resolved.]
When you configure an unnumbered interface to borrow from a loopback or non-Ethernet interface and also configure unrestricted proxy ARP on the unnumbered interface, the incoming proxy-ARP requests are dropped. As a workaround, configure the unnumbered interface to borrow from any Ethernet interface. [PR/301101: This issue has been resolved.]
Enabling traceoption with certain trace levels for DHCP may cause the DHCP process to core. [PR/301102: This issue has been resolved.]
When you configure a static route on an unnumbered link, the router resets; even rebooting does not help. You must remove the static route configuration to restore stability to the router. [PR/301732: This issue has been resolved.]
When you configure Connectionless Network Service (CLNS) on an lt interface, the source MAC address becomes corrupted. [PR/304323: This issue has been resolved.]
If you configure max-flows for a service set, the other service sets share whatever is left from the system maximum value. The sum of the max-flows values for individual service sets cannot exceed the global maximum value. If the configured total exceeds this value, the max-flows value for the last configured service set is truncated and a warning message is logged. [PR/305350: This issue has been resolved.]
The system reports that it is booted off alternate media when mirror-flash-on-disk is enabled. [PR/311768: This issue has been resolved.]
When two BGP peers are configured to use MD5 authentication and you issue the clear bgp neighbor command on one peer, the following message might be written to the system log on the other peer: “tcp_auth_ok: Packet from <address>:<identifier> missing MD5 digest.” Traffic forwarding is not affected. [PR/312680: This issue has been resolved.]
On MX-series and M120 routers, and M320 routers with an Enhanced III FPC, if the configuration includes the explicit-null statement at the [edit protocols mpls] or [edit protocols ldp] hierarchy level, a DPC or FPC might reboot (but not generate a core file) when an MPLS packet with time-to-live (TTL) equal to 0 (zero) or 1 (one) is processed at the egress of a tunnel. [PR/313319: This issue has been resolved.]
The output from the traceroute command includes both the IP address and DNS hostname of each hop. The hostname information might be incorrect for one or more hops. [PR/389794: This issue has been resolved.]

User Interface and Configuration

TACACS+ accounting start and stop requests are incompatible with Cisco ACS. The fix is to include the no-cmd-attribute-value statement or the exclude-cmd-attribute statement at the [edit system tacplus-options] hierarchy level. When the no-cmd-attribute statement is enabled, the JUNOS software sets the value of the cmd attribute in TACACS+ accounting start and stop requests to a null string. When the exclude-cmd-attribute statement is enabled, the JUNOS software excludes the cmd attribute from the TACACS+ accounting start and stop requests. The statements support the logging of accounting requests correctly in the Accounting log file; otherwise, the requests are logged in the Administration log file. [PR/252472: This issue has been resolved.]
An attempt to log in to a router using SSH might fail with a “Could not chdir to home directory : No such file or directory” error message. This problem might occur when specific user account configuration is in place and the router is configured to use the TACACS+ server for authentication. The issue arises only if the TACACS+ server has been configured with a local-user-name directive that specifies a nonexistent user. [PR/288116: This issue has been resolved.]
When a configuration group containing a wildcard match for a static route and qualified next hop of a broadcast interface is applied, the routing protocol process (rpd) might exit and dump core. [PR/290712: This issue has been resolved.]
In the J-Web chassis view, the 10-port Channelized E1 IQ PIC is shown with an incorrect interface position, although the interface index is correct. [PR/294957: This issue has been resolved.]
Under the following conditions, the commit operation might fail with the syntax error “inactive: group <group-name> { ... }”: (a) you use the configure private command to enter configuration mode, (b) a BGP group is deactivated, and (c) you change another BGP group's name. As a workaround, use the configure command to enter configuration mode. [PR/300917: This issue has been resolved.]
When you invoke a commit or commit check operation for a configuration that includes forwarding-table filters, the firewall process (dfwd) might generate a core file and restart. [PR/301806: This issue has been resolved.]
When TACACS+ authentication is configured and a user tries to log in to the router over an SSH or FTP connection, the JUNOS software does not include the remote user address in the authentication request packet sent to the TACACS+ server. [PR/301927: This issue has been resolved.]
If the set of transient changes specified in a commit script (enclosed by the <transient-change> tag) includes the deactivation of a configuration statement, none of the transient changes take effect. [PR/307352: This issue has been resolved.]

Interfaces and Chassis

On channelized T3 interfaces, the T1 loopback state does not reflect loopbacks set by facilities data link requests using the remote-loopback-respond statement at the [edit interfaces interface-name t1-options] hierarchy level. [PR/45837: This issue has been resolved.]
When you commit firewall and rpf configurations, an erroneous “nh_jtree_fe_prehandler” message might appear on the Packet Forwarding Engine. This message is informational only and does not indicate an error condition. [PR/96146: This issue has been resolved.]
When interchassis Automatic Protection Switching (APS) is configured with channelized OC12 PICs and the working circuit fails, it takes longer than expected to fail over to the protect circuit. [PR/98488: This issue has been resolved.]
On a dual Routing Engine system with graceful Routing Engine switchover (GRES) enabled, when an IPv6 interface is configured with the loopback statement at the [edit interfaces interface-name gigether-options] hierarchy level, the backup Routing Engine might report kernel replication errors in the output of the show system switchover command. [PR/102164: 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.]
When you configure the default-address-selection statement at the [edit system] hierarchy level, Routing Engine graceful-restart may cause GPRS support node (GGSN) services to be unreachable. [PR/232197: This issue has been resolved.]
If there are any configuration changes on an interface when newly committed DLCIs are in the process of coming up, the DLCIs are not active until the interface is reset or until the logical interfaces are deactivated and activated. [PR/261501: This issue has been resolved.]
If you include the compression-device statement at the [edit interfaces at-fpc/pic/port unit logical-unit-number] hierarchy level (that is, on an ATM interface), the JUNOS kernel might generate a core file and restart. [PR/265542: This issue has been resolved.]
Under loaded conditions, the show interfaces rlsq command output might display incorrect statistical information because the statistics replies did not arrive in time. [PR/270467: This issue has been resolved.]
On the M320, a signal integrity issue in old clocking hardware might generate inaccurate alarms and errors when the actual clock is working perfectly. This behavior has no operational impact and has been fixed in later releases. [PR/275308: This issue has been resolved.]
When member links are configured to be part of a redundant LSQ interface MLPPP bundle, while the RLSQ interface is yet to be configured, “error BAD_PAGE_FAULT” is reported by the kernel if monitor interface is executed on a redundant LSQ logical interface. [PR/277689: This issue has been resolved.]
Whenever an LCC or FPC is taken offline, statistics for the aggregate interface become large (negative). This was an issue only for a multichassis system and not single chassis system. [PR/285897: This issue has been resolved.]
When you issue the show interfaces diagnostics optics command and do not specify an interface name, the output is the same as for the show interfaces command, instead of including optic diagnostics. [PR/285978: This issue has been resolved.]
XGE PICs on M120 routers take an unusually long time (up to 1.5 seconds) to send remote-fault messages. [PR/287147: This issue has been resolved.]
On MX-series routing platforms, if you take fabric planes offline and the spare planes become active, you might see high traffic drops or continuous high fabric red drops. To recover from continuous high fabric drops, you must switch the fabric planes again. [PR/291541: This issue has been resolved.]
SONET interfaces that are configured with interface hold up/down timers may remain down after an FPC reset or a PIC reset. To restore the interface, (temporarily) remove the interface hold timers. [PR/291707: This issue has been resolved.]
The interface hold-timer might not work for channelized subinterfaces. [PR/294654: This issue has been resolved.]
On routers running JUNOS Release 9.0R1 or later, if VPLS multihoming is enabled and one instance has two or more sites configured with aggregated interfaces, it might trigger an MPLS loop, because the CCC-down flag for the interface is not applied and the router keeps learning MAC addresses on this aggregated interface. [PR/295634: This issue has been resolved.]
In JUNOS Release 9.0 and later, the monitor interface command output is missing some information. [PR/296131: This issue has been resolved.]
Transit IPSec AH or ESP packets may drop when traversing sp-interface as bypass traffic. [PR/300471: This issue has been resolved.]
When a Routing Engine switchover takes place, the kernel might generate a core file. [PR/301327: This issue has been resolved.]
On a router without redundant Routing Engines (such as the M7i router), if the Routing Engine restarts, the router might stop forwarding packets. As a workaround on the M7i router, issue the request chassis cfeb restart command. [PR/301788: This issue has been resolved.]
When only one Routing Engine is installed in an M120 router, on the craft interface the LEDs for the power supplies never light up. Similarly, in the PS LEDs section of the output from the show chassis craft-interface command, there is a period in all four fields (indicating that no LEDs are lit). [PR/302504: This issue has been resolved.]
On a Gigabit Ethernet IQ2 PIC with SFPs, if a logical interface is configured for VRRP, the values in the Traffic statistics section of the output from the show interfaces ge-fpc/pic/port extensive command might not be accurate. [PR/303151: This issue has been resolved.]
In a Protected System Domain with a large number of LSPs configured (for example, 50,000), an FPC might generate a core file when you issue the show pfe route mpls command repeatedly. [PR/303349: This issue has been resolved.]
When a change in VRRP priority or tracking information occurs, the state machine resets. As a result, VRRP goes through an idle-backup-master transition. With the fix, the reset is avoided and VRRP continues to be the master/backup. [PR/303701: This issue has been resolved.]
When the links of an RLSQ bundle are not configured at the remote site and a Routing Engine switchover is performed followed by taking a primary or secondary LSQ PIC offline, the backup Routing Engine might reset. [PR/306667: This issue has been resolved.]
For SONET/SDH interfaces, when the hold-time statement is included at the [edit interfaces so-fpc/pic/port] hierarchy level and you change the framing type from the default (SONET) to SDH by including the framing sdh statement at the same hierarchy level, the interface does not come up after the commit operation. As a workaround, deactivate the hold-time statement before changing the framing. [PR/306687: This issue has been resolved.]
There is no check to verify if the Other RE is present on the router and RCP is called to copy the snmp index file. [PR/309043: This issue has been resolved.]
An error message, “DCD_RCP_RE_FAILURE” is incorrectly sent when a check is made for redundant Routing Engines and there is only one Routing Engine in the router. [PR/314456: This issue has been resolved.]

Services Applications

When you explicitly configure forward and backward rules for a NAT service set, an ICMP fragmentation-needed message is not sent and the traffic is dropped without notification. If the backward rule is not configured and is left implicit, this problem is not seen. An explicit backward rule causes the ICMP error packet to be handled as a new flow. As a workaround, do not explicitly configure backward rules unless they are absolutely necessary. [PR/238215: This issue has been resolved.]
After a routing instance with an rlsq bundle is deactivated and activated, the primary MS PIC is taken offline and brought back online. In this case, a Routing Engine switchover might result in a kernel database connection error. [PR/292950: This issue has been resolved.]
The Real-Time Streaming Protocol (RTSP) Application Layer Gateway (ALG) implementation was not compatible with some RTSP server implementations. [PR/292961: This issue has been resolved.]
The router handles data paths for Layer 2 Tunneling Protocol (L2TP) tunneled Multilink Point-to-Point Protocol (MLPPP) packets with a payload size of zero bytes incorrectly, which causes the service PIC to reset unexpectedly. [PR/296390: This issue has been resolved.]
If Network Address Port Translation (NAPT) is configured and multiple short-lived flows are established, ports on MS PICs might not be assigned correctly. In some cases, this situation causes the MS PIC to stop functioning. [PR/300553: This issue has been resolved.]
If Network Address Port Translation (NAPT) is configured and multiple short-lived flows are established, ports on MS PICs might not be assigned correctly. In some cases, this situation causes the MS PIC to stop functioning. [PR/304088: This issue has been resolved.]
When a PPP session on a dedicated interface is terminated, associated static routes might remain in the routing table. [PR/309771: This issue has been resolved.]

Routing Protocols

The metric-out statement at the [edit protocols protocol-name group] hierarchy level incorrectly takes precedence over the metric-out statement configured under the neighbor configuration for the same group. [PR/31848: This issue has been resolved.]
BGP traceoptions incorrectly reports Path Attribute flags with the EXT bit always reset. [PR/51953: This issue has been resolved.]
When routes are propagated across IBGP, the show bgp group statistics command output does not display AS numbers correctly. [PR/69098: This issue has been resolved.]
When routes are exported into OSPF and then OSPF is deactivated, the routing protocol process (rpd) might generate a core file and stop operating. [PR/232362: This issue has been resolved.]
When you activate or deactivate an aggregate route filter (represented by the aggregate statement at the [edit routing-options rib routing-table] hierarchy level, its contributing members are not reevaluated and the filter continues to function as before the change. [PR/270115: This issue has been resolved.]
When both of the following conditions apply, a change in interface status (up or down) causes a BGP status change: (a) there are more than 255 unnumbered interfaces without a destination address (the unnumbered-address lo0.0 statement is included at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level for more than 255 logical interfaces), (b) the BGP local address (specified by the local-address statement at the [edit protocols bgp group group-name] hierarchy level) is the last one in the list of addresses included at the [edit interfaces lo0 unit 0 family inet] hierarchy level. As a workaround, either use an unnumbered interface that has a destination address or do not set the BGP local address to an unnumbered interface. [PR/277202: This issue has been resolved.]
When an IPv6 duplicate address is detected, the interface stops forwarding but ISIS and OSPF3 continue to announce the interface as a valid route. However, the address is unreachable and all traffic destined to or through the interface is dropped. [PR/296740]
MVPN type 5 routes may be deleted on MSDP speakers while sources are still active, potentially leading to MVPN traffic disruption. [PR/298338: This issue has been resolved.]
On an AS boundary router or a route reflector for a VPN address family, under the following conditions VPN routes are not imported into the routing instance (VRF instance) tables: (a) the nonstop-routing statement is included at the [edit routing-options] hierarchy level, (b) routing instances are configured for locally attached VPN sites, and (c) you deactivate and reactivate the routing instance configuration. [PR/307770: This issue has been resolved.]
When you configure a policy that causes BGP to advertise static routes that lead to unnumbered interfaces, the routing protocol process (rpd) might generate a core file. [PR/308465: This issue has been resolved.]
If a BGP notification message has an invalid value for the length of the next-hop network address field in the MP_REACH_NLRI attribute, the JUNOS software sends error code 3, subcode 1 (“Malformed Attribute List”), instead of the code specified by RFC 2858, which is code 3, subcode 9 (“Optional Attribute Error”). [PR/308628: This issue has been resolved.]
When you re-add a previously deleted or deactivated address statement for an interface's IPv6 address on a PIM upstream neighbor (at the [edit interfaces interface-name unit logical-unit-number family inet6] hierarchy level), the addition does not register at the downstream neighbor. On the downstream neighbor, the value in the Upstream interface and Upstream neighbor fields remains unknown in the output from the show pim join extensive command. As a workaround, issue the clear pim join command. [PR/309972: This issue has been resolved.]
If unicast routes towards a multicast source are updated via BGP static routing and an IPv6 address on a BGP peer router is deactivated and reactivated, multicast forwarding does not function correctly. [PR/386781: This issue has been resolved.]
If the source address for IPv6 multicast traffic is resolved by a static route, information about an upstream neighbor might not be updated after a graceful Routing Engine switchover event (the value unknown appears in both the Upstream interface and Upstream neighbor fields in the output from the show pim join extensive command). [PR/389856: This issue has been resolved.]

MPLS Applications

After upgrading to JUNOS Release 8.4 or later, LDP neighboring cannot be established with another vendor’s equipment because of a subnet mismatch. The fix adds a new configuration statement, allow-subnet-mismatch, that ignores subnet mismatch for the source address in LDP link hello packets. [PR/285933: This issue has been resolved.]
Other vendor implementations might send status TLV notification messages with the U-bit set to 0 and F-bit set to 1. While such a combination is not recommended according to RFC 5036, the JUNOS software will tear down the LDP session upon receiving such a status TLV message. [PR/290845: This issue has been resolved.]
The autobandwidth adjustment intervals for label-switched paths (LSPs) do not conform to the configured values. [PR/297771: This issue has been resolved.]
Sometimes a traffic engineered label-switched path (LSP) remains up when it should go down. [PR/300919: This issue has been resolved.]
When you configure the traffic-engineering mpls-forwarding statement for a link-protected point-to-multipoint LSP, RSVP creates two link-protection routes, which eventually causes the routing protocol process (rpd) to dump core. [PR/303993: This issue has been resolved.]
If two point-to-multipoint branch LSPs share the same incoming interface, and one of them comes up after the other during a remerge event at a transit router, the in-label for both LSPs is marked “Discard,” as reported by the show route table mpls.0 command. [PR/306312: This issue has been resolved.]
When you issue the traceroute mpls ldp command, the MPLS OAM process (mplsoamd) might generate a core file. [PR/307732: This issue has been resolved.]
If an IP address is configured as both a direct LDP neighbor and a targeted LDP neighbor, and an LDP session with the neighbor repeatedly goes down and comes up again, the routing protocol process (rpd) might generate a core file and stop operating. [PR/308178: This issue has been resolved.]
If there is a single hop to an LDP neighbor and the source address of the received LDP Link Hello address is the same as the LDP Targeted Hello source address, when the LDP link neighbor and target LDP neighbor go down and come back up in a certain sequence, the Layer 2 circuit connection might remain inactive (reported as VC-Dn in the St field of the entry for the neighbor in the output from the show l2circuit connections command). To return the connection to the active state, issue the clear ldp neighbor address command. [PR/312672: This issue has been resolved.]

VPNs

When VPLS nonstop active routing is enabled and you modify the VPLS instance (for example, change the instance type or its route distinguisher), the routing process (rpd) might stop and the system might produce a core dump [PR/231234: This issue has been resolved.]
When a mismatch notification is received in the interval between queuing an mt- interface delete request and the deleting interface, the routing protocol process (rpd) might stop functioning. [PR/294693: This issue has been resolved.]
When the tunnel-services statement is configured at the [edit routing-instance instance protocols vpls] hierarchy level and a VPLS interface is configured with an MTU, a virtual tunnel interface might flap due to unrelated configuration changes. As a workaround, remove the tunnel-services statement in the routing instance configuration. [PR/297141: This issue has been resolved.]
When implementing VPLS in conjunction with point-to-multipoint label-switched paths and provider-tunnel configuration, the VPLS connection(s) will remain in a status of VC-Dn in the following releases of JUNOS: 9.0, 9.1R1, and 9.1R2. As a workaround, downgrade to JUNOS 8.5R3 or earlier. [PR/297650: This issue has been resolved.]

Class of Service

Adding and deleting an interface many times by configuring the scheduler-map-chassis statement at the [edit class-of-service interfaces ge-1/1/*] hierarchy level might cause a memory leak in the class-of-service process (cosd). As a workaround, restart the class-of-service (CoS) process (cosd). [PR/82546: This issue has been resolved.]
On J-series Services Routers, MLPPP bundles with congested member links on which fragmentation is active might interfere with other bundles within the same system and trigger high latency or packet drops. As a possible workaround, configure the shaping rate on the bundle with fragmentation enabled to avoid flow control from the member link. [PR/281985: This issue has been resolved.]
On M120 routers, MX-series routers, and on M320 routers with E3-FPCs, MPLS transit traffic with a label stack that performs a pop operation at the penultimate node is not shaped according to the configured transmit rate exact value, which results in more traffic being sent than should be allowed. [PR/282002: This issue has been resolved.]
When a core-facing interface on a PE router that is acting as an IGP peer is deactivated (for example, by deactivating the interface interface-name statement at the [edit protocols ospf area area-id] hierarchy level), the following message might be written to the system log: “COSMAN: cosman_unbind_update_if_refcount: Failed to find the ifd <interface-name> (<index>) in the ifdtable for ifl <index>.” There is no operational impact. [PR/291630: This issue has been resolved.]
When you delete CoS interface scheduler-map configurations, the allocated IDs are not removed from the Packet Forwarding Engine. As a result, when the new CoS interface configuration is applied, a system log message shows no profile space available. [PR/292223: This issue has been resolved.]
M120 routing platforms configured with class-of-service log “ichip_get_handle” and “ichip_mq_unbind_red_profile_for_queue()” errors when a configuration is committed. These errors are cosmetic. [PR/303006: This issue has been resolved.]
The class-of-service daemon core dumps when a classifier with ”medium-low” or “medium-high” loss priority is assigned to a routing-instance. [PR/311433: This issue has been resolved.]

Forwarding and Sampling

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.]
Policer value does not change dynamically on changing the shaping rate and the policer is still stuck at the initial value. As a work around, deactivate and activate the filter. [PR/286663: This issue has been resolved.]
When you include the route-accounting statement at the [edit forwarding-options family inet6] hierarchy level, the sampling process (sampled) might generate a core file. [PR/291455: This issue has been resolved.]
When you issue show commands to display information for user-configured bridge-domain names containing certain special characters, the CLI returns an error. With the fix, bridge-domain names that contain ":" can be displayed correctly. [PR/299165: This issue has been resolved.]
Under some circumstances, when you add a prefix at the [edit policy-options prefix-list list-name] hierarchy level, the commit operation might fail with one of the following error messages: "Check-out failed for Firewall daemon (/usr/sbin/dfwd) without details" or "configuration check-out failed." [PR/305510: This issue has been resolved.]

Network Management

As a result of a Routing Engine switchover, many processes are restarted. During this transient stage, the SNMP agent process (snmpd) may generate a syslog message: “Header version mismatch: SNMP_SMS_HDR_ERR: problem with hdr size (6) or msg size (0) message in syslog.” This issue is automatically corrected when the switchover process completes, and there is no operational impact afterwards. [PR/77668: This issue has been resolved.]
When some PIC types are taken offline and brought back online, an SNMP linkUp trap is not generated for some of the logical interfaces. [PR/294667: This issue has been resolved.]
The JUNOS software does not generate an SNMP linkDown trap when an interface state (represented by the ifOperStatus object) changes from "up" to "lowerLayerDown." The trap is required by RFC 2863. [PR/297829: This issue has been resolved.]
When you enable firewall counters for IPv4 and IPv6 traffic on an interface (by including the count statement at the [edit firewall family (inet | inet6) filter filter-name term term-name then] hierarchy level and the filter filter-name statement at the [edit interfaces interface-name unit logical-unit-number family (inet | inet6)] hierarchy level), the show snmp mib walk jnxFWCounterByteCount command might not display all of the counters. [PR/313194: This issue has been resolved.]

Release 9.1R2

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

Software Installation and Upgrade

On an M320 router, when you perform an in-service software upgrade (ISSU), destination class accounting statistics might not be restored properly. [PR/284647: This issue has been resolved.]
On an M320 router, when you perform an ISSU, firewall filter statistics might not be restored properly. [PR/286413: This issue has been resolved.]
On an M320 router, when you perform an ISSU, destination class accounting statistics might not be restored properly. [PR/284647: This issue has been resolved.]

Platform and Infrastructure

When graceful Routing Engine switchover (GRES) and multicast are both configured on a router, the master Routing Engine kernel might dump core because of inconsistencies between the multicast forwarding database on the master Routing Engine and the multicast forwarding database on the backup Routing Engine. [PR/100795: This issue has been resolved.]
When using aggregate bundles with FRR, it takes about 10 to 16 seconds of packet loss when one of the member links fail. [PR/101295: This issue has been resolved.]
If Layer 2 encapsulation is larger than 34 bytes, the Packet Forwarding Engine might restart unexpectedly. [PR/240080: This issue has been resolved.]
An MX platform DPC with a 10x1Gigabit Ethernet interface might report the same interface statistics on all ports of the same PIC if the first interface has the MPLS family configured on it. As a workaround, do not configure a family interface on the first port of the PIC slot. [PR/262607: This issue has been resolved.]
On MX-series routers, when unicast RPF is configured on an interface (the rpf-check statement is included at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level), the DPC that houses the interface might generate a core file. [PR/275466: This issue has been resolved.]
With JUNOS Release 8.5R2 or later, when protocol tracing is enabled, I/O writes to the hard drive might get blocked causing daemons to delay sending packets. .[PR/278580: This issue has been resolved.]
On M10i routers that have Channelized DS3 IQ PICs installed, the CFEB might generate a core file, which also interrupts FPC operations. [PR/283943: This issue has been resolved.]
The router reboots when using request system software add command with a filename extension other that the one available for download from the Juniper Networks support site, even though the file is otherwise the same. [PR/283948: This issue has been resolved.]

On a J-series router configured to capture packets, certain conditions might trigger messages similar to the following:

Apr  7 15:00:07  lhotse fwdd[2911]: ipc_msg_write: IPC message type: 13,
subtype: 4 exceeds MTU, mtu 1550, length 1552
Apr  7 15:00:07  lhotse fwdd[2911]: ipc_msg_write: IPC message type: 13,
subtype: 4 exceeds MTU, mtu 1550, length 1556
Apr  7 15:00:09  lhotse fwdd[2911]: ipc_msg_write: IPC message type: 13,
subtype: 4 exceeds MTU, mtu 1550, length 1552

These messages indicate that some packets have not been captured as expected. There is no impact on traffic passing though the router. [PR/285242: This issue has been resolved.]

Under certain circumstances, DHCP discover packets might be leaked to all the configured VRFs. [PR/286139: This issue has been resolved.]

Interfaces and Chassis

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.]
Very rarely when there is a PIC error and the PIC is coming online again, the system might reset unexpectedly. With the fix, the PIC fails to attach if it has a hardware error. It does not cause the FPC to reset as in the previous case. [PR/241092: This issue has been resolved.]
When you configure MLPPP or MLFR UNI NNI (FRF.16) bundles on link services IQ interfaces, a certain mix of traffic might cause a lower-priority queue to be starved when packets expire after not being scheduled for some time. [PR/262901: This issue has been resolved.]
When a Fast Ethernet interface is connected to a Gigabit Ethernet interface that is configured for full duplex without autonegotiation, the information for the Fast Ethernet interface is incorrect in the Autonegotiation information section of the output from the show interfaces extensive command. [PR/263957: This issue has been resolved.]
For a routing node in a routing matrix, when you remove a hardware component from the chassis, alarms are cleared for that component (which is correct), but also for all components of the same type. [PR/278672: This issue has been resolved.]
If you power off and power on a Routing Engine model RE-A-2000 on a T640 routing node (by issuing the request system power-off other-routing-engine and request system power-on other-routing-engine commands), the output of the show chassis hardware command no longer includes an entry for SPMB 1. [PR/281463: This issue has been resolved.]
Prior to JUNOS Releases 9.0R3 and 9.1R2, you could not unplug a 4-port 10-Gigabit Ethernet PIC without taking the PIC offline first. [PR/288077: This issue has been resolved.]
When you insert an OC-192 SONET/SDH PIC that uses XFP optics into an Enhanced Type 3 FPC on a T640 routing node, the FPC might generate a core file. [PR/288884: This issue has been resolved.]
Under the following conditions, a logical interface configured for VRRP (the vrrp-group statement is included at the [edit interfaces interface-name unit logical-unit-number family family address address] hierarchy level) does not initialize properly and the output for it from the show vrrp summary command displays the value bringup in the VR State field:
1. The logical interface is configured with dual VLAN tags (the vlan-tags statement is included at the [edit interfaces interface-name unit logical-unit-number] hierarchy level)
2. The configuration for another logical interface of the same physical interface includes the vlan-id statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level. The problem can occur even though the interfaces do not belong to the same VRRP group.
[PR/288975: This issue has been resolved.]
On an MX-series Ethernet Services router, if you bring fabric planes offline and spare planes are used, you might see high traffic drops or continuous high fabric red drops. To recover from continuous high fabric drops, perform the fabric plane switch again. [PR/291541: This issue has been resolved.]

Services Applications

When you commit a configuration that does not include either the pre-shared-key statement or the local-certificate statement at the [edit security ike policy policy-name] hierarchy level, the key management process (kmd) generates a core file. [PR/267957: This issue has been resolved.]
Services PICs (such as the Adaptive Services and MultiServices PICs) do not record correct information in the SAMPLE-RATE field in the header of the cflowd packets that they export. [PR/276142: This issue has been resolved.]
In a scaling setup with 4000 MLPPP sessions and traffic consisting of 256-byte packets, after traffic flows for more than an hour, the L2TP process does not start when the restart l2tp-service command is issued. [PR/276255: This issue has been resolved.]

Routing Protocols

If more than 1000 communities are attached to a route, the routing process (rpd) might become unresponsive. Removing the communities and restarting the routing process might be necessary to recover. [PR/77001: This issue has been resolved.]
When you activate or deactivate an aggregate route filter (represented by the aggregate statement at the [edit routing-options rib routing-table] hierarchy level, its contributing members are not reevaluated and the filter continues to function as before the change. [PR/270115: This issue has been resolved.]
The show ospf route detail command output displays the optional-capability value for intra-area router routes only. [PR/273809: This issue has been resolved.]
PPMD was not preprogrammed ahead of switchover time. This causes an 8 to 12 second blackout window where no IS-IS Hellos are generated during switchover. [PR/276823: This issue has been resolved.]
With a minimum of two PIM ASM routers and receiver on a LAN segment, if interface mismatch errors occur, an s,g entry will not be created. This is applicable for both native PIM configurations as well as multicast VPN configurations. [PR/281662: This issue has been resolved.]
Using PIM, certain multicast routing topologies might cause delays in multicast route convergence. [PR/282109: This issue has been resolved.]
A BFD v0 session might not be established between a router running a post-JUNOS 8.3 release and a router running a pre-JUNOS 8.3 releases. [PR/286331: This issue has been resolved.]
When BGP multipath is enabled (the multipath statement is included at the [edit protocols bgp group group-name]hierarchy level) and route updates arrive from multipath and nonmultipath peers in a certain order, load balancing across paths might stop working correctly. [PR/288694: This issue has been resolved.]

MPLS Applications

After upgrading to JUNOS Release 8.4 or later, LDP neighborship cannot be established with another vendor's equipment because of a subnet mismatch. The fix adds a new configuration statement, allow-subnet-mismatch, that ignores subnet mismatch for the source address in LDP link hello packets. [PR/285933: This issue has been resolved.]
When the target of the ping mpls rsvp command is another vendor's router, the value in the Local transmit time field is a UNIX timestamp instead of an NTP timestamp as specified by RFC 4379. [PR/289535: This issue has been resolved.]
Packet loss can occur following an RSVP auto-bandwidth adjustment. [PR/289553: This issue has been resolved.]
Other vendors' implementations might send status TLV notification messages with the U-bit set to 0 and F-bit set to 1. While such a combination is not recommended according to RFC 5036, the JUNOS software will tear down the LDP session upon receiving such a status TLV message. [PR/290845: This issue has been resolved.]

Multicast

In JUNOS Release 9.0 and later, the multicast snooping process (snoopd) leaks memory even if it is not configured. As a workaround, disable the process if it is not required. [PR/279378]
When nonstop active routing (NSR) is enabled and you issue the restart routing command on the master Routing Engine, VPLS connections on the backup Routing Engine might not be reestablished quickly. To speed up the synchronization process, issue the restart routing command on the backup Routing Engine. [PR/282095: This issue has been resolved.]

VPNs

The VT tunnel interface is not recreated upon reboot of Tunnel PIC or FPC reboot holding the Tunnel PIC. As a workaround deactivate and activate the vt tunnel interface stanza in the interface configuration. [PR/266170: This issue has been resolved.]
When nonstop active routing (NSR) is enabled and you issue the restart routing command on the master Routing Engine, VPLS connections on the backup Routing Engine might not be reestablished quickly. To speed up the synchronization process, issue the restart routing command on the backup Routing Engine. [PR/282095: This issue has been resolved.]
The delete routing-instances vpls protocols vpls mtu command does not reset the MTU to its default value. As a workaround, deactivate and then reactivate the VPLS instance to set the MTU to the default value of 1500. [PR/288026: This issue has been resolved.]

Class of Service

On the MX960, bandwidth sharing across high priority and strict-high priority schedulers might not be as expected. This issue occurs when the schedulers are configured on logical interfaces. [PR/265603: This issue has been resolved.]
On M120, M320, and MX960 routers, when you configure override input packet classification, the feature might not work. [PR/271660:This issue has been resolved.]
On M120 routers, MX-series routers, and M320 routers with E3-FPCs, MPLS transit traffic with a label stack that performs a pop operation at the penultimate node is not shaped according to the configured transmit rate exact value, which results in more traffic being sent than should be allowed. [PR/282002: This issue has been resolved.]

Forwarding and Sampling

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.]

Network Management

A syntax error in the mib-rfc3811.txt MIB file prevents SNMP from using the MIB. The file is included in the package accessible at https://download.juniper.net/ software/junos-export/release/juniper-mibs-release-signed.tgz, where release is a JUNOS Release number such as 8.2R4.5. [PR/80648: This issue has been resolved.]

JUNOS SDK

Process health monitor (pmond) will not be able to monitor SDK processes that are spawned after it. Heartbeat updates from those applications will be ignored without any error. [PR/287738: This issue has been resolved.]

Release 9.1R1

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

Software Installation and Upgrade

When upgrading from JUNOS Software Release 9.0R1 to JUNOS 9.1B1, the new master Routing Engine is upgraded; however, the old master (new backup) Routing Engine is not upgraded. As a workaround:
- Deactivate the redundancy graceful-switchover statement at the [edit chassis] hierarchy level.
- Deactivate the nonstop-routing statement at the [edit routing-options] hierarchy level.
- Use the request system add command to upgrade the old master Routing Engine to JUNOS Release 9.1B1. [PR/272781: This issue has been resolved.]

Platform and Infrastructure

Packet Forwarding Engine (PFE) notification statistics for the "options or ttl expired (not RE-destined)" counter are increased incorrectly. [PR/64951: This issue has been resolved.]
During a Routing Engine switchover, the Flexible PIC Concentrator (FPC) might reset multiple times. [PR/70857: This issue has been resolved.]
Due to changes in the JUNOS TCP/IP networking stack, the output of the show connections command may be different from JUNOS Release 8.4 and earlier. [PR/103330: This issue has been resolved.]
The PCAP support for Multilink Point-to-Point Protocol (MLPP), Multilink Frame Relay (MLFR), and Multilink Frame Relay (MFR) is not available. [PR/239642: This issue has been resolved.]
On some Routing Engines, the smartd process may display the following error: “atastandbyarmset.” [PR/253775: This issue has been resolved.]
Using the ox option with the smartd process is not recommended on mounted devices because it may result in unexpected behavior. [PR/255473: This issue has been resolved.]
If there are a lot of aggregate next hops and BGP routes pointing at some of them, a quick link flap combined with the BGP route churn might cause the Packet Forwarding Engine to restart unexpectedly. [PR/268204: This issue has been resolved.]
With certain traffic patterns, MX-series and M320 routers with 3.0 forwarding ASICs might experience packet loss. To recover, you must reboot the affected Dense Port Concentrator (DPC). [PR/268274: This issue has been resolved.]
On a J-series router configured with an IPSec tunnel, Ethernet frames smaller than 64 bytes might not pass through. [PR/268965: This issue has been resolved.]
In JUNOS software Release 8.5R1 only, when the router receives an MPLS LSP ping packet, a kernel memory leak is triggered in the network packet buffer and, upon exhaustion, packet transfer is not possible between the Routing Engine and the Packet Forwarding Engine. [PR/273024: This issue has been resolved.]
On a T1600 router, the Link Aggregation Control Protocol (LACP) does not work on the following Ethernet interfaces: 10x1 Gigabit Ethernet, IQ2, or Fast Ethernet. [PR/274586: This issue has been resolved.]
When you delete an interface with a firewall filter assigned to it and commit the configuration while filter counters are requested, the router might stop functioning. [PR/292267: This issue has been resolved.]

User Interface and Configuration

If you use the NETCONF API to modify the configuration database when it has been locked by another NETCONF session, or if you try to delete a configuration statement that does not exist, the NETCONF server returns both the <rpc-error> and <ok/> tag elements as children of the <rpc-reply> tag element. [PR/62664: This issue has been resolved.]
JUNOS devices cannot be managed by Session and Resource Control (SRC) software. [PR/273117: This issue has been resolved.]
When you use the configure private command and then change two static routes at the same time at the [routing-options static] hierarchy level, the commit may fail. As a workaround, configure one static route at a time. [PR/273251: This issue has been resolved.]
When the MX240 DC chassis is in a slightly elevated temperature environment with the fans in high speed, the show chassis environment command might hang. As a workaround, terminate the CLI session by typing CTRL+C to open a new CLI session. [PR/274015: This issue has been resolved.]

Interfaces and Chassis

On M20 routers, when you start the router with Routing Engine 0 and System and Switch Board (SSB) 0 as master components, issue the request chassis routing-engine master switch command, and then log in to Routing Engine 1 and issue the request chassis ssb master switch and request system reboot commands, the ONLINE LED might remain lit on both SSBs. [PR/74283: This issue has been resolved.]
When you configure the default-address-selection statement at the [edit system] hierarchy level, Routing Engine graceful restart may cause gateway GPRS support node (GGSN) services to be unreachable. [PR/232197: This issue has been resolved.]
Input statistics for aggregated Ethernet interfaces incorrectly report zero, regardless of input traffic volume. [PR/266271: This issue has been resolved.]
The chassis LED status returned by the MIB jnxLEDState does not reflect the actual chassis alarm LED. [PR/266326: This issue has been resolved.]
SFPCs cause the warning message “WARNING: Unknown FPC 0x1f4” when checking PIC compatibility. [PR/266854: This issue has been resolved.]
When there is an Address Resolution Protocol (ARP) entry for Virtual IP (VIP), the Virtual Router Redundancy Protocol (VRRP) might not respond to ARP requests for VIP while transitioning to master state. [PR/268627: This issue has been resolved.]
An error in the chassis process (chassisd) causes a small memory leak when the show chassis hardware extensive command is executed. [PR/268925: This issue has been resolved.]
On an MX platform, when a lot of traffic is going to the Routing Engine and the route changes, the Dense Port Concentrator (DPC) might trigger an assertion without producing a core dump. [PR/269699: This issue has been resolved.]
When you configure multiple interfaces with the vlan-id-range statement and cover a large number of VLAN IDs, the Dense Port Concentrator (DPC) might restart unexpectedly. [PR/271456: This issue has been resolved.]
In 9.0R1, you can configure only 4096 Layer 2 Tunneling Protocol (L2TP) sessions with shapers and policers. [PR/273804: This issue has been resolved.]

Routing Protocols

Kernel replication might fail when a pending change on a virtual loopback tunnel (VT) interface is replicated. [PR/69862: This issue has been resolved.]
The redistribution of OSPF point-to-point (P2P) LAN interfaces from a routing instance into the main routing instance can fail, displaying the following log message: “Jan 23 15:24:50 router rpd[6063]: cannot perform nh operation ADDANDGET nhop 0.0.0.0 type unicast index 0 errno 45.” As a workaround, redistribute the interfaces routes within the routing instance into the main routing instance. [PR/271130: This issue has been resolved.]
The routing process can restart unexpectedly if it receives a BGP flow NRLI specification with an undefined subcomponent type. [PR/274421: This issue has been resolved.]

MPLS Applications

The system can leak next-hop resources when RSVP link protection is enabled. [PR/265295: This issue has been resolved.]

VPNs

An interoperability issue exists between NetScreen-specific features (NHTB) and JUNOS Enhanced Services. [PR/274937: This issue has been resolved.]

Class of Service

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.]
On MX960 routers, the class-of-service process does not provide information about SNMP objects whose names begin with "jnxCosQstat." As a result, SNMP queries on those objects fail with an error message. [PR/269419: This issue has been resolved.]

Forwarding and Sampling

If a term in a firewall filter specifies a range of values for a source or destination address or port, the filter might not match packets as expected. As a workaround, define the addresses and ports explicitly. [PR/265023: This issue has been resolved.]

[ Contents] [ Prev] [ Next] [ Report an Error]