Knowledge Search


×
 

18.3R1-S5: Software Release Notification for Junos Software Service Release version 18.3R1-S5

  [TSB17624] Show Article Properties


Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, PTX, MX, QFX, vMX, vRR, NFX, SRX, vSRX
Alert Description:
Junos Software Service Release version 18.3R1-S5 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
Solution:

Junos Software service Release version 18.3R1-S5 is now available.

The following are incremental changes in 18.3R1-S5.

 
PR Number Synopsis Description
1307258

With BGP LU FRR in an inter-AS scenario, a very high FRR time is visible once the link is up.

On PTX, EBGP-BGP-LU FRR may produce higher than expected traffic-loss (about 2 seconds) when the inter-AS link with primary-ASBR-peer comes back UP. This is because, in PTX RPD creates Indirect-Nextthops to track an EBGP-peer too. And when the link went down, in problem-scenario - the Indirect-Nexthop of the primary-ASBR-peer is not removed from the Multipath/FRR-formation; which leaves a stale Indirect-Nexthop in the FRR-nexthop-set. This stale Indirect-nexthop becomes Active as soon as link comes back Up, and starts to send traffic with previously-advertised label to the peer-AS. Once the primary-ASBR-peer comes back up and advertises a new label, then the FRR-nexthop-set gets the proper Indirect-Nexthop and traffic is restored.

1343680

i40e NVM upgrade support for PTX platforms

Adding support for i40e NVM upgrade in PTX3000 platforms

1349373

FPCs might reboot continuously until the system is rebooted or RE switchover.

On NG-RE (Next Generation Routing-Engine), a failure of the HWRNG (Hardware Random Number Generator) will leave the system in a state where not enough entropy is available to operate.

1355111

Transit OSPF traffic over Q-in-Q tunneling might be dropped if a firewall filter applied to Lo0 interface

On EX2300 as CE/PE device, transit OSPF traffic over Q-in-Q tunneling might be dropped if a firewall filter applied to Lo0 interface.

1357802

Configuration commit operation after policy change causes rpd crash

The rpd might crash during the policy configuration changes.

1382166

Host bound traffic might be affected and lt interface can go down in ACX

Host bound traffic might be affected and lt interface can go down in ACX

1395098

The best and the second-best routes might have the same weight value if BGP PIC is enabled

In BGP PIC (Prefix Independent Convergence) scenario, next-hop of unequal BGP multipath routes might have the same weight (0x1), resulting in unexpected load balance for traffic.

1398251

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.

1406242

QFX5200/5100 might not be able to send out control plane traffic to the peering device

On all QFX5200/5100 platforms, the router might not be able to send out control plane traffic to the peering device along with "Failed to allocate 16384 DMA memory" messages. All the routing protocols running over the affected interfaces will be down due to this issue, and therefore it impacts the service.

1406691

JDI-RCT: EVPN-VXLAN: Lacp state of few interfaces are in detached state and BGP neighborship state stuck in Active state on Napanook device acting as spine with non collapsed EVPN-VXLAN configurations

In a system when we apply reapply (after deleting) the scale L3 VxLAN configs (4K vlans/vxlan) , LACP states for few interfaces may go to detached state. Workaround is to ReConfigure affected aggregated interfaces.

1423575

vMX RIOT Process Panic with lu_reorder_send_packet_postproc Messages

vMX RIOT Process Panics, results in Riot Core Dump & Impact Data Forwarding.

1423707

Traffic is dropped after FPC reboot with AE member links deactivated by remote device

On JUNOS routers and switches with Link Aggregation Control Protocol (LACP) enabled, deactivating a remote Aggregate Ethernet (AE) member link will make the local member link move to LACP Detached state. The Detached link will be invalidated from the PFE AE-Forwarding table as expected. However, if the device is rebooted with this state, all the member links will be enabled in PFE AE-Forwarding table irrespective of LACP states and result in traffic drop.

1429765

RPD might crash with ospf overload configuration

In MPLS environment, the routing instance connected to the PE-CE of MPLS, RPD might crash then core-dumps is seen in case that [ospf overload as-external] and [ospf overload allow-route-leaking] are configured. It's applicable to common OSPF overload scenario.

1429917

The AE interface does not come up after rebooting the FPC/device though the physical member link is up

When a single FPC carries minimum 10 member links which belong to the same or different AE (Aggregate Ethernet) bundle, if one of the static AE bundle (LACP is not enabled) has disabled member link, this static AE interface does not come up after rebooting the FPC/device though it has physical member link with UP state.

1430115

Interface on QFX does not come up after the transceiver is replaced with one having different speed

On QFX series platforms, interface may not come up when the transceiver is replaced with another transceiver which has different speed.

1431592

"SIB Link Error" detected on a specific PFE may cause complete service impact

On QFX10002-60C/PTX10002-60C platforms, if there is a "SIB Link Error" detected on specific PFE, all the PFEs may not forward traffic between each other. The error may be caused by hardware condition such as any bad optics connected.

1434900

ACX5448 forward small packets(less than 64 bytes including padding) if egress link is 40G/100G causing remote interface drop as runts.

ACX5448 forward small packets(less than 64 bytes including padding) if egress link is 40G/100G causing remote interface drop as runts.

1439518

RIO:ACX5448:DHCP Packets not Transparent over L2CIRCUIT

Transit DHCP packets are not punted to CPU and are transparently passthrough.

1441869

The AE interface might flap whenever a new IFL is added to it

On MX Junos Fusion setup with AE (Aggregated Ethernet) interface configured with link-speed, the AE interface might flap whenever a new IFL (Logical Interface, e.g. subinterface) is added to it and commit. The issue results in service on the AE interface flap.

1442552

Different formats of the B4 addresses may be observed in the SERVICES_PORT_BLOCK_ALLOC/RELEASE/ACTIVE log messages

In DS-lite setup implementation on MS-MPC card different B4(Basic Bridging Broadband) address formats for JSERVICES_NAT_PORT_BLOCK_RELEASE log may be observed when softwire-prefix is configured under the service set, but a unified behaviour is required.

1442901

ACX5448: Pkt buffer error from PFE leading to memory leak when IGMP is sent from NNI AC in L2circuit & VPLS

In an ACX5448 platforms, when the PFE failed to allocate packet buffer, portion of packet memories may not be freed.

1443466

RED drops on all the interfaces on ACX5448

On an ACX5448, traffic might be dropped on interfaces' egress queues and recorded as RED drops. This is due to a software defect which incorrectly configured buffer configurations in the PFE. The trigger events are either COS configuration changes or link flap.

1445508

The 1G interface on MX204 might stay down after the device is rebooted

On MX204 platform, the interface with the parameter "speed 1g" configured might stay down after the device is rebooted. This is a timing issue.

1445979

ACX5448/18.3R1-S4.1 not performing proper dot1p CoS rewrite on interfaces configured with l2circuit/local-switching/family ccc

ACX5448/18.3R1-S4.1 not performing proper dot1p CoS rewrite on interfaces configured with l2circuit/local-switching/family ccc

1446437

On L3VPN, as-external regarding OSPF overload cannot be handled properly.

as-external works fine on inet.0 when overload. However, vpn cases(L3VPN) not handled for external properly.

1446489

Traffic Discarded for only specified VLAN in IPACL_VXLAN filters

When there is only one term containing user-vlan-id match condition and there are no other terms in the IPACL_VXLAN filter except discard, the discard action for non-matching traffic will work for only that VLAN which is specified under user-vlan-id and not for other VxLAN VLANs which are part of that trunk port on which filter is applied. This can be ignored by adding another term to the filter which doesn't contain user-vlan-id match.

1448899

ACX5448 L2circuit stops forwarding traffic after LDP flap.

ACX5448 L2circuit stops forwarding traffic after LDP flap.

Modification History:
First publication 2019-08-22
Related Links: