Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

17.4R2-S3: Software Release Notification for Junos Software Service Release version 17.4R2-S3



Article ID: TSB17537 TECHNICAL_BULLETINS Last Updated: 08 Mar 2019Version: 1.0
Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, Network Agent
Alert Description:
Junos Software Service Release version is now available for download from the Junos software download site
Download Junos Software Service Release:
  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts

Junos Software service Release version 17.4R2-S3 is now available.

The following are incremental changes in 17.4R2-S3.

PR Number Synopsis Description

The RE-PFE out-of-sync errors might be seen in syslog

When a configuration that moves the Packet Forwarding Engine offline and another configuration that brings the Packet Forwarding Engine back online are committed in quick succession, out-of-synchronization syslog errors might occur. Most of the time these are benign errors, but sometimes these errors might result in Packet Forwarding Engine crash.


BGP might not advertise routes on the existing BGP peer after adding Layer 3 VPN instance

If rib-group is configured under BGP, BGP might not advertise routes on the existing BGP peer after adding Layer 3 VPN instance. The "show bgp neighbor" shows that the neighbor state is stuck in "Send state: not advertising".


MAC addresses might not be learnt on bridge-domains after XE/GE interface flap

The setup with 120 bridge domains among the 1000 bridge domains, with XE/GE links towards downstream switch and LAG bundles as uplinks towards upstream routers. The XE/GE link is part of the physical loop in the topology. Spanning tree protocols such as VSTP/RSTP/MSTP is used for loop avoidance. Some MAC addresses are not learnt on DUT when LAG bundles part of such bridge domains are flapped along with other events such as spanning tree root bridge change.


Unnecessary interface-related log messages might be seen after configuration commit on PTX series routers

Unnecessary interface-related log messages be seen after configuration commit in Junos versions higher than 17.2R2 and 17.3R1. The messages are informational and do not indicate any issue. The PR reclassifies them as trace messages so they will only be seen when further debugging is enabled.


PTX-Series: Invalid programming of interfaces during PFE initialization may lead to traffic null route.

While a PTX-platform performs Packet Forwarding Engine (PFE) initialization, the PFE may not initialize interfaces data structure properly. This causes transit traffic drop while traffic egressing out of those interfaces. The problem is applicable only to PTX1000 ,PTX3000,PTX5000 and PTX10000.


The backup routing engine sends syslog messages to the syslog server with primary fxp0 instead of lo0

The backup routing engine sends syslog messages to the syslog server with primary fxp0 instead of lo0


Traffic loss might be seen on new primary after the interface flaps followed by RE switchover in VRRP scenario

VRRP MAC filter will not be seen in PFE if interfaces flap followed by GRES, before VRRP state settles down after flap. During this time VRRP state is backup in primary-RE and VRRP state is idle in Backup-RE.


The packets might be dropped when they go through MX104 built-in interface

If the packets are destined to specific MAC address (such as last two octets are 0x1101, 0x1102, 0x1103, 0x1104, 0x1106, 0x1108, 0x1109, 0x110a and so on), they might be dropped on the remote-end device when going through MX104 built-in xe(10GE) ports.


The backup VPLS router might still have MAC addresses after the primary router is rebooted and recovered in VPLS environment

In VPLS environment, the l2alm might be out of sync with hardware under some race conditions after extensive negative test (such as node restart, IFL flapping, protocol flapping, rpd restart) are executed. This might cause the issue that some MAC addresses still appear on backup VPLS router after the primary router is rebooted and recovered.


The inline-jflow sampling configuration might cause FPC crash On MX platforms.

On MX-series platforms, if the inline-jflow "nexthop-learning" knob is configured, when the sampling removes one next-hop, the FPC might crash. It is not easily reproducible and it is a rare issue.


small rpd memory leak when configuring EVPN

In EVPN scenarios, rpd migh leak small amount of memory. In the long run, rpd might crash and generate a core file due to a memory allocation problem.


Some harmless log messages are suppressed on the backup SPMB.

Unsuccessful connection attempts will not be logged on the backup SPMB.


SNMP mib walk causes KMD errors.

While performing SNMP mib walk for OID jnxIpSecTunnelEntry, following errors are seen. May 25 00:30:04 labbox_re0 kmd[17150]: KMD_SNMP_PIC_NO_RESPONSE: PIC rsp1 did not respond to SNMP query: No error: 0 May 25 00:30:04 labbox_re0 kmd[17150]: KMD_SNMP_FATAL_ERROR: Fatal SNMP error occurred: libservicesui: ipc_pipe_read() failed - No error: 0


The traffic might not be transmitted correctly in a large scale of VPLS scenario

On MX platforms with MPC cards, if there are large scale numbers of LSI interfaces or pseudowire paths (for example: more than 64K) in virtual private LAN service (VPLS) scenario, the partial traffics might be dropped for the error MAC numbers (which most likely is caused by MAC leak from one instance to the other). Note: In VPLS scenario, LSI logical interface (lsi.x) will be created when the knob of no-tunnel-services is configured.


The IPv6 routed packet may be transmitted through interface whose VRRP state is in non-master

When VRRP is enabled on an interface, if disable and then enable the interface, IPv6 routed packet might be transmitted over VRRP virtual IP address, even its VRRP state is in the non-master state. When this happens, the peer interface may return to normal later than this interface. At this time, the packets sent out through this interface might be dropped.


Debug log message, "expr_nh_flabel_check_overwrite: Caller nh_id params", classified as Error Log when it should be LOG_INFO.

Debug logs are printed as error logs in /var/log/messages. Debug log message, "expr_nh_flabel_check_overwrite: Caller nh_id params", classified as Error Log when it should be LOG_INFO


The traffic traversing an IRB interface might not be tagged with a VLAN if the packets go through an additional routing-instance.

On MX-Series platforms with logical tunnel interface (LT) working in trunk mode, if an IRB interface is referenced by a bridge-domain in a virtual-switch routing-instance and its traffic goes through an l2circuit between two virtual-switch routing-instances, the VLAN insertion might not work for IRB interface, as a result, the traffic could be dropped.


Duplicate IP cannot be configured on both SONET (so-) interface and other interfaces

If configuring duplicate IP on both SONET (so-) interface between other type interface, other type interface might not get the IP address.


After NAT64 router (with MS-MPC) translates an ipv6 fragment to ipv4 fragment, router is not inserting the right value in identification field of IPv4 Header

After NAT64 router (with MS-MPC) translates an ipv6 fragment to ipv4 fragment, router is not inserting the right value in identification field of IPv4 Header


DNS requests with EDNS options might be dropped by DNS ALG

On SRX platforms with DNS ALG enabled, the DNS requests with Extension mechanisms for DNS (EDNS) additional options might be dropped by DNS ALG.


The rpd might crash on the new primary RE when performing GRES

On all Junos platforms with Graceful Routing Engine Switchover (GRES) and Nonstop active Routing (NSR) enabled, if Border Gateway Protocol (BGP) is configured, the rpd process might crash on the new primary Routing Engine (RE) when performing GRES due to this timing issue.


FPC crash might be seen after FPC restarts

If scaling IFLSet members and AE members are configured on the same FPC, the FPC might crash when it restarts.


The MPC6E might crash while fetching PMC device states

PMC device is OTN framer which is sitting on the MIC6-100G-CFP2. While fetching PMC states, CPU might be hogged by the thread more than 2.5 sec. If this occurs, MPC6E might crash.


LACP stuck in Detached/Attached state when interface configured with Native VLAN ID AND VxLAN VLAN.

A QFX may not be able to establish a complete LACP session ("collecting / distributing") depending on the configuration of the QFX interface. If an interface has native-vlan-id configured AND that same 'native-vlan-id' VLAN is in 'vlan members' list AND the VLAN is VxLAN enabled then QFX stops processing received LACP PDUs


Domain name is not reported as part of the LLDP system name in "show lldp neighbor" command

With this fix system name tlv will include configured domain name with host-name.


Adjusting mac-table-size configuration may cause l2ald crash

Sometimes L2ald might crash when try adjusting mac-table-size configuration.


Incorrect user privilege regarding "set vmhost" command

The users can still issue command "set vmhost..." although "permissions system-control" is not configured on system class.


The kmd crashes with core file after bringing up IPSec connection.

On ACX, M, MX and T platforms, after bringing up IPSec tunnels, if issuing show command, kmd crash might be seen.


The IPv6 packet might not be routed when IPv6 packet is encapsulated over IPv4 GRE tunnel on QFX10000..

On QFX10002/QFX10008/QFX10016 platforms, the IPv6 traffic might be dropped if the IPv6 over IPv4 Generic Routing Encapsulation (GRE) tunnel is configured because when an Interface family (IFF) member is removed on the Logical interface (IFL), the property of IFL to learn MAC is getting set to NULL which is causing ARP failure.


IPSec VPN traffic might fail when passing through MS-MPC of MX with CGNAT enabled

While dynamic IP Security (IPSec) virtual private network (VPN) is re-keyed due to lifetime expiration, IPSec internet key exchange (IKE) phase 1 user datagram protocol (UDP) port 500 and phase 2 UDP port 4500 sessions would be translated into two different public internal protocol (IP) addresses while passing through carrier-grade network address translation (CGNAT), which causes IPSec VPN traffic to fail. This behavior does not cause issue for Juniper MX devices with MS-MIC or SRX devices since for such devices identify key is used to authenticate the sessions and it is allowed for private IP address to be translated into two different public IP addresses.


The bypass LSP might pass through unexpected path that includes the same SRLG as the down protected TE link.

Whenever the Point of Local Repair (PLR) router detects that a bypass Label Switched Path (LSP) originating from it has gone down because of the Resource Reservation Protocol (RSVP) ResvTear, it will attempt to re-signal the bypass LSP over the same path. If the bypass LSP came up within a short period, then the configuration of "Link protection re-optimization timer" will determine the further course of action on that bypass LSP. However, if the bypass LSP does not come up along the same path and if the router has not been configured to avoid running Constrained Shortest Path First (CSPF) for the bypass LSP, the router will compute CSPF for the bypass LSP. If the protected Traffic Engineering (TE) link is down when such a CSPF is scheduled for execution, the Shared Risk Link Group (SRLG) information will not be available in Traffic Engineering Database (TED) for the CSPF to determine which SRLGs to avoid for the bypass LSP. Hence that CSPF does not correctly avoid the SRLGs of the protected TE link while computing path. This results in the bypass LSP coming up along a path that will turn out to be incorrect when the protected TE link comes up again.


The bbe-smgd process might crash when two subscribers login with the same framed-route prefix and preference values

In subscriber management scenario, the bbe-smgd process might crash when two subscribers login with the same framed-route prefix and preference values returned from Radius.


Some SFBs might go down when one of the PSMs in the chassis generates a bad output voltage which is out-of-range

On MX2010/MX2020, some Switch Fabric Boards (SFBs) might go down due to one of the Power Supply Modules (PSMs) in the chassis generates a bad output voltage which is out-of-range.


The lsi binding for the IPv6 neighbor is missing

On ACX, EX, MX, QFX and Virtual Chassis Fabric platform, if irb interface is configured under VPLS instance, after switchover the lsi binding for the IPv6 neighbor might be missing.


Certain log messages might be observed on QFX platforms

On QFX platforms, when Power budgeting is executing, log message "PEM power status has changed, run power budget again" might be seen.


MAC learning might stop working on some LAG interfaces.

On QFX10000 platforms, MAC learning does not work on some LAG interfaces after frequent MAC moves


Individual command authorization may cause mgd crash

For a user with allow-commands and deny-commands configured, mgd crash is happening sometimes when the user enters into CLI mode and executes any show commands.


Traffic destined to VRRP VIP gets dropped as filter is not updated to related ifl

On MX platform with enhanced-ip and VRRP configured, if remove/add a child link from AE bundles via "replace pattern" several times, traffic destined to VRRP VIP might be dropped.


The dcd memory leak might be seen when committing configuration change on static route tag

After committing configuration change on static route tag (see below example), the memory consumed by device control daemon (dcd) might increase. The leak rate is slow (200KB for every commit with one tag change). [edit routing-instances TEST routing-options static route xx.xx.xx.xx/25] - tag 10; + tag 11;


The bbe-smgd process might crash after commiting config changes

In enhanced subscriber management environment, the bbe-smgd process might crash after commiting config changes, especially when some parts of the dynamic-profiles are modified.


L2TP subscribers might be stuck in init state in a corner case

On MX platforms enabled with Next Generation Subscriber Management, if Layer 2 Tunneling Protocol (L2TP) is configured, when there is an IP connectivity loss between L2TP Access Concentrator (LAC) and L2TP Network Server (LNS), which will lead to tunnels teardown and re-negotiation, in addition to that, the bbe-smgd process restart at the same time, some affected L2TP subscribers might be stuck in init state and can't login successfully in this corner case.


The ppmd on RE may run with high CPU utilization after RE switchover

In the rare case, ppmd on RE might stay high cpu usage after RE primary switch event. There will be no impact on this problem.


Repackage Juniper MVPN MIB

The Multicast VPN MIB was not being properly compiled into the Juniper MIB package bundle. This PR causes mib-jnx-mvpn.txt to be included as part of the Juniper Enterprise MIB set.


Unable to install licenses automatically on QFX platforms

On QFX Series platforms, it is unable to update licenses automatically with "request system license update" command.


MPC card/afeb/tfeb with Channalized OC MIC can crash with core dump

MPC card/afeb/tfeb with Channelized OC MIC can crash with core dump


Provide user choice whether to drop a core when we'd normally soft core.

The JUNOS RPD daemon has facilities to attempt to trap certain classes of non-fatal bugs by continuing to run, but leaving a "soft" core file. Leaving a soft core is intended to be non-disruptive to routing and forwarding. This PR implements a mechanism by which users may disable soft cores being generated.


EVPN-VxLAN: DCPFE restarted at the _bcm_field_td_counter_last_hw_val_update routine after upgrading spine with latest image.

Within the DCPFE process, it is possible that a deadlock situation between the pfeman thread and the linkscan thread causes the watchdog event to trigger. The DCPFE saving its memory content (core file) as the result.


Downstream interface is not removed from multicast route after getting PIM prune

In NG-MVPN scenario where source and receivers are on the same PE but different routing-instances, if PIM prune (*, g) is received on a downstream interface, Type 7 route might not get updated accordingly, resulting in the interface remaining in multicast route. Thus unwanted multicast traffic keeps being forwarded to that interface.


The rpd soft core might be seen when L2VPN is used

RPD provides a mechanism to validate that route selection has successfully been done. When errors in route selection are detected, a soft core is dropped: RPD remains running, a single core file is dropped, it is rate limited to not do this frequently. When running L2VPN, BGP MED selection may be inappropriately run on the routes. As a result, the route selection sanity code will notice an unexpected result and leave a soft core.


In 13.3R9.13, firewall filter action, "decapsulate gre", decapsulates gre, ip-over-ip and ipv6-over-ip, but in 17.3R3.9, it only decapsulates gre.

The feature fbt based "gre decap" used to decap GRE, IPIP and IPIPV6 traffic till 16.1 . Later PR-1226830 changed this behavior and allowed only the decapsulation of GRE based traffic. This can cause issues in some customer deployment on newer release upgrade where "gre decap" option was used to decap the IPIP and IPIPv6 traffic as no decap support of IPIP/IPv6 The fix in this PR reinstates the older behavior and makes sure GRE decap option decapsulates the additional IPIP and IPIPv6 traffic apart from Gre.


VPN does not recover on the high-end standalone SRX when CLI operation " restart ipsec-key-management " is done

VPN does not recover on the high-end standalone SRX when CLI operation "restart ipsec-key-management" is done.


Only one PFE could be disabled on FPC with multiple PFEs in error/wedge condition

On MX, PTX and QFX platforms with Chassis Manager (CM) error reporting, if Flexible PIC Concentrator (FPC) has multiple Packet Forwarding Engines (PFEs) in which one of PFEs goes into wedge condition, due to this issue, the wedge condition might be reported continuously even after disable_pfe action has been taken for the corresponding PFE. Due to this issue, when CMERROR message queue is saturated and the level report-limit is reached (e.g. 10 major errors), the wedge condition on the other PFE within the same FPC will be ignored and not be able to trigger disable_pfe action any more. This issue might cause some traffic being blackholed.


A single-hop bypass LSP might not be used for traffic when both transit chaining mode and sensor-based-stats are used.

On JunOS platforms with transit chaining mode enabled, if Resource Reservation Protocol (RSVP) link/node protection is enabled and sensor-based-stats is used, a single-hop bypass label-switched path (LSP) nexthop might not be installed in forwarding information base (FIB) even it is in routing information base (RIB). Hence the single-hop bypass LSP will fail to forward traffic when needed.


Dual stacked DHCPv6-PD client connection terminated after commit when RADIUS address assignment is not defined within the range of a local pool

Dual stacked DHCPv6-PD client connection terminated after commit when RADIUS address assignment is not defined within the range of a local pool. At the time of some configuration commit the authd process is checking address-assignments, client connection is terminated suspecting that the address-assignment range had changed when IPv6-PD address does not match range of local pool.


The authd crash might be seen due to a memory corruption issue.

In subscriber scenario, the authd might crash multi-times due to a memory corruption issue.


BGP router on the same broadcast subnet with its neighbors might cause IPv6 routing issue on the neighbor from other vendors

RFC 2545 has limitation on third party next-hops where the next hop is propagated unchanged. Due to this limitation, Border Gateway Protocol (BGP) router attaches its own IPv6 link local address in the next hop and advertise the route to its BGP neighbor. This could introduce the routing issue on the BGP neighbor from other vendor (e.g. Cisco) and put the BGP router itself in the traffic path unexpectedly. This issue will not be seen on Juniper devices because IPv6 link local address is not selected as next hop.


Syslog error messages: [LOG: Err] COS_HALP(cos_halp_get_fabric_stats_per_pfe:3211): pfe_id 0 cchip 0[LOG: Err] COS_HALP(cos_halp_get_fabric_stats_per_pfe:3272): No PFE found for pfe_id_start 0.

On a MX204, when any command under 'show class-of-service fabric <>' hierarchy is executed, you will see "COS_HALP(cos_halp_get_fabric_stats_per_pfe:3211): pfe_id 0 cchip 0" error messages. Since the MX204 is fabric less platform, the COS fabric CLI commands are not available. The error messages have no side effects.


MPLS LSP traffic loss might be seen under rare conditions if CSPF is enabled

When make-before-break (MBB) new instance signaling experiences error and before retry is finished, other triggers such as auto bandwidth adjustment timer expiration have to be blocked until MBB finishes. Once the MBB finishes instance switching, blocked trigger needs to be scheduled, but should only be triggered after optimize-adaptive-teardown timer expires. In the affected releases, the blocked trigger is scheduled immediately after instance switching without taking optimize-adaptive-teardown timer into account, it causes old instance to be torn down before whole system finishes changing routes using the new instance, this leads to traffic loss.


Some error logs might be seen on FPC when reading attempt from Uninitialized memory location

On all MX platforms that support enhanced subscriber management (Next Generation Subscriber Management) with L2TP subscriber scenario, when a packet arrives with size higher than LNS (L2TP network server) IFL (Logical interface) MTU and 'Do-not fragment' bit is set, because the micro kernel generates ICMP error messages and increment 'out-mtu-errors' in IFD (Pysical interface) stream counter, and then the OIF (Outgoing interface) index is wrongly programmed in LNS IFL output feature list. So some error logs would be seen when reading attempt from Uninitialized memory location. This only impacts the traffic from Core to LNS subscriber on PFE which needs to generate ICMP error message like MTU exceeded. It would not impact normal transit traffic.


Log message "JAM HW data base open failed for ptx5kpic_3x400ge-cfp8" during commit.

The following log messages might be seen during configuration commit on PTX series routers with FPC type 3: chassisd[84247]: jam_core_hwdb_open: JAM HW data base open failed for ptx5kpic_3x400ge-cfp8 chassisd[84247]: JAM: jam_pic_plugin_init =1 - fail 4 chassisd[84247]: JAM: Failure Exit jam_pic_plugin_initd chassisd[84247]: jam_plugin_init: JAM:PL: jam_pic_plugin_init failed The messages are cosmetic and can be ignored.


MX-VC VMCORE seen on both VC-MM and VC-BM.

MX-VC VMCORE seen on both VC-MM and VC-BM.


Some files are missing during log archiving

When there are any scripts running on the router cscript.log will be created. It is found that the permission are set wrongly hence when any non-root user tries to archive the /var/log along with cscript, some other files in /var/log go missing in the archived file. So when we untar the file, less files are found. This issue is not seen when root user does the archive. With the fix of the PR non-root user would be able to archive the files.


Traffic impact might be seen if auto-bandwidth is configured for RSVP LSPs

With auto-bandwidth configured for Resource Reservation Protocol (RSVP) Label Switched Path (LSP), when timeout occurs during LSP statistics query, large bandwidth might be wrongly reserved for the LSP. If there is no sufficient resources (e.g. bandwidth, alternative path) in the network, other LSPs might be torn down, or might not go up.


The process rpd crash may be observed once a non-forwarding path is used for re-resolution

The process rpd may crash after a non-forwarding route (i.e., a route to an indirect next-hop association is non-forwarding indirect next-hop) which is received from multiple protocols is resolved again by using the non-forwarding path.


Log messages "dot1xd[]: task_connect: task ESP CLIENT:...: Connection refused" might be reported in Junos 17.4 or later

Messages like the following can appear in log message on devices running Junos 17.4 or later: dot1xd[7683]: task_connect: task ESP CLIENT:33001. addr Connection refused dot1xd[7683]: task_connect: task ESP CLIENT:33001. addr Connection refused .. The message is cosmetic and can be ignored/filtered out.


The non-existent subscribers might appear at 'show system resource-monitor subscribers-limit chassis extensive' output

In subscriber scenario, if the subscribers limit is configured and subscribers flaps, the non-existent subscribers might appear at 'show system resource-monitor subscribers-limit chassis extensive' output. The most important impact is that reaching subscriber-limit for a certain FPC prevents subscribers from other FPC to connect, as a result, subscribers can't come up on another FPC as well.


FPC might crash during next hop change when using MPLS inline-jflow

On MX platforms with MPLS inline-jflow configured, FPC might crash during next hop change due to another FPC reboot or an interface flap, some traffic will be blackholed during the crash.


DMAC problem of IRB interface for traffic over the l2cuircuit

For LT interfaces packets in TX path missing 4 bytes in l2 header


MX10003: Rpd crash with switchover-on-routing-crash doesn't trigger RE switchover and the rpd on primary RE goes into STOP state

If the rpd (routing protocol daemon) crashes with 'switchover-on-routing-crash' knob enabled on MX10003 platform, the RE switchover might not happen and the rpd on primary RE goes into STOP state. All protocols go down and the rpd remains in STOP state until manual recovery is done.


Firewall filters are not getting programmed into PFE

In the subscriber environment, if the client profile has no filters while the service profile has filters, after a subscriber login, the ifstate compression might be seen when deleting the current filters and then adding a different filter. When this occurs, the firewall filter might be corrupted.


The ISIS-SR route sent by the mapping server might be broken for ECMP

On MX/PTX series, in ISIS-SR (segment routing) scenario, the ECMP (equal-cost multi-path) route sent by ISIS-SR mapping server stitched from LDP might not be pushed labels on one of ECMP paths, which results in traffic blackhole on the next-hop with no label.


The L2circuit egress PE might drop the traffic in FAT+CW enabled L2circuit scenario when another FAT+CW enabled L2circuit PW flaps

On PTX1000/PTX10002/PTX10008/PTX10016 platforms, when multiple FAT+CW (FAT->flow-aware transport, CW->control-word) are enabled in L2circuit PWs (pseduo-wires) scenario, the L2circuit egress PE might drop the traffic (the affected PW is unsure/unkown) and also corrupt the PW traffic/packet received from MPLS core when another FAT+CW enabled L2circuit PW flaps (such as, link down, FPC crashes, do enable/disable of flow label on PW, etc).


LDP route missing in inet.3 when enable TI-LFA loose node protection on LDP-SR stitching node

When LDP has a LDP-SR stitching route present because of mapping client,in that scenario, LDP ignores other routes received from the flash in inet.0 table. To solve this problem, we re-flash the inet.0 routes when SR mapping client route is going away. However in case where LDP is deleting the nexthops while deleting theroute, LDP mapping client status is not correctly identified & as a result the re-flash of inet.0 route is missed. Fix is to re-flash the inet.0 route if route is a SR mapping client route & it's nexthops are getting cleaned up.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search