Knowledge Search


×
 

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

  [TSB17519] Show Article Properties


Alert Type:
SRN - Software Release Notification
Product Affected:
MX, PTX, VMX, VRR
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
Solution:

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

The following are incremental changes in 18.3R1-S2.

PR Number Synopsis Description
1341720

The VRF static route might not be exported when route-distinguisher-id is used on RR in BGP L3VPN scenario.

In Border Gateway Protocol (BGP) Layer 3 Virtual Private Network (L3VPN) scenario, on the Route Reflector (RR) with Virtual Routing and Forwarding (VRF) instance deployed, the VRF static route might not be exported to bgp.l3vpn.0 table correctly. Hence the static route could not be advertised to remote device.

1355953

PTX10001 platform: FRR link-protection convergence time

Traffic loss duration during FRR link-protection is between the range 25m.sec to 150m.sec.

1363935

Packet drop in EVPN stitching with IRB configured.

In Ethernet VPN (EVPN) interconnecting scenario where EVPN-VXLAN or EVPN-MPLS instances are stitched, if one routing instance has an IRB interface configured and the other one does not have IRB, traffic loss might be observed because packets with the IRB MAC as source MAC (for example, ARP requests) are discarded.

1367477

The FPC might go down on some vmhost based PTX/QFX platforms

On PTX1000/PTX10001-20C/PTX10002-60C/QFX10002-60C, the Flexible PIC Concentrator (FPC) might reboot which might result in the FPC not coming up or the system becoming unresponsive.

1369705

The rpd might crash in EVPN scenarios when configuring EVPN

In EVPN scenarios, rpd might crash and generate a core file due to a memory allocation problem.

1377500

Packets might be dropped on data plane in the inline Jflow scenario

On MX series with MPC, in the inline Jflow scenario, due to a software defect, the data structure associated with inline Jflow feature may not be initialized correctly. This leads to not being able to forward traffic correctly on the affected MPC.

1378392

Traffic might be dropped on third-generation FPCs on PTX.

On PTX with third-generation FPCs, if optics not certified by Juniper Networks (NON-JNPR) are used and there is specific traffic pattern with congestion, traffic might be dropped.

1379016

The SRX device acting as DHCP relay may not forward the DHCP OFFER/ACK packet to the DHCP client

On SRX-Series platforms, if 'Cross routing instance dhcp-relay forward-only' is applied, when the DHCP client requests IP address from DHCP server through the SRX device, the DHCP OFFER/ACK packet would not be forwarded into the DHCP client on the DHCP relay, which causes the DHCP clients could not get IP address. And it would affect the traffic and service.

1379138

ARP request packets might be sent out with 802.1Q VLAN tag

ARP request packets might be sent out with 802.1Q VLAN tag even though the outgoing interface is access port.

1384898

QFX5120/EX4650: Occasionally two of Channelized 25G ports using 4x25G breakout cable will not come up after JUNOS reboot

Intermittently after JUNOS reboot two of channelized 25G ports using 4x25G breakout cable may not come up.

1387746

Penultimate-hop router does not install BGP LU label causing traffic blackhole.

On the penultimate-hop router in BGP LU (labeled unicast) scenario using PHP (penultimate-hop popping), when a link flap causes the next-hop of a label received from the egress router to change, once the link comes back, the penultimate-hop router might fail to install the clone route (S=0) entry for that label and result in traffic blackhole.

1388888

With IGMP snooping enabled on the LEAF switches, multicast traffic is forwarded to VLAN/VNI which doesn't have active receiver

In 18.1R3-S3, IGMP snooping is supported only on network port. i.e. Traffic coming on access interface will be flooded to other access interface and network interface, it won't use IGMP joins to send multicast traffic only to required receiver. But when traffic is coming on network port (VTEP encapsulated), it will not flood traffic but will forward only if there are receivers on LEAF box. This behavior is same as 18.1R1.

1391535

[vSRX 18.3R1] flow traceoptions does not work on vsrx 18.3R1

on vSRX configured with one dataplane CPU, the flow trace-options debug does not display useful information.

1398398

High jsd or na-grpcd CPU usage might be seen even JET or JTI is not used.

Even Juniper Extension Toolkit (JET) or Junos Telemetry Interface (JTI) is not used, due to a bug in the grpc stack which is used by jsd and na-grpcd daemons, the CPU usage might go up after 24 days of device uptime on JunOS starting 18.3 or 18.2X75-D10 releases, if there are no clients connected to these daemons.

1398685

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.

1399726

EVPN Type 2 MAC+IP route is stuck when the route Advertisement has 2 MPLS labels and Withdrawal has 1 label

In EVPN (Ethernet VPN) scenario, if the router receives a Type 2 MAC+IP route Advertisement having 2 MPLS labels, and then Withdrawal of the same route with only 1 label, the Withdrawal will not be processed and that route will be stuck.

1404895

ARP/ND will not be resolved in case of native VLAN ID configured for LAG access interface

When native VLAN ID is configured for LAG access interface for L2 gateway case, ARP/ND will not be resolved and hence traffic will be dropped for that VLAN. No issue with native VLAN ID configured on normal xe / et interfaces (without LAG).

1405182

Routes with multiple communities being rejected in inter-AS NG-MVPN scenario.

In segmented inter-AS NG-MVPN scenario, when the PE router receives a C-multicast (or leaf AD) route with more than one communities from a remote AS, the route might be rejected due to incorrect route-target community matching.

1406282

Vxlan Transit Traffic over Tagged underlay L3 Interface gets dropped due to HW Limitation.

Vxlan Transit Traffic over Tagged underlay L3 Interface gets dropped due to HW Limitation.

1408749

RPD core dump after NSR switchover

New master RE RPD may core if there's a churn specifically with EVPN routes just before NSR switchover.

1410687

Connections using 100G long range JNPR optics between QFX5120 & QFX10008 are not stable and go down randomly.

When using PSM4 optics on QFX5120, there is a possibility that due to timing fault on FPGA hardware, link may go down due to tx laser being disabled and require administratively toggling the link to enable it back. This issue is addressed with this PR changes.

Modification History:
First publication 2019-02-07
Related Links: