Knowledge Search


×
 

18.2R2-S5: Software Release Notification for Junos Software Service Release version 18.2R2-S5

  [TSB17622] Show Article Properties


Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, NFS, PTX, QFX, SRX, VMX, VRR, Network Agent
Alert Description:
Junos Software Service Release version 18.2R2-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.2R2-S5 is now available.

The following are incremental changes in 18.2R2-S5.

 
PR Number Synopsis Description
1395685

L3 gateway did not update ARP entries if IP or MAC quickly move from one router to another router in EVPN-VXLAN environment

If IP or MAC quickly move from one router to another router in a highly scaled EVPN-VXLAN environment, such as 1000+ simultaneous VMs mobility events where the VMs move to a new leaf switch and the VM MAC addresses are also changed, L3 gateway did not update ARP entries with new location of the VM and MAC.

1402626

VLAN tagged traffic arriving on VPLS interface might get dropped

VLAN tagged traffic arriving on VPLS interface might get dropped

1408558

The MPC linecards might crash when performing ISSU to 19.1R1 or above release

On MX with MPC1/1E/2/2E/3E/4E linecards installed, the MPC might crash when performing ISSU to 19.1R1 or above release.

1410970

Packets might be dropped if the traffic forward via an LT interface

On all Junos platform, if the traffic forward to IRB via an LT (Logical Tunnel) interface, packets might be dropped.

1414816

The MPC might crash when one MIC is pulled out during this MIC is booting up

On MX platform, the MPC might crash when one MIC is pulled out during this MIC is booting up.

1416032

Services dependent on LDP might be impacted if committing any configuration changes

On all Junos platforms, if there is any protocol running dependent on LDP (e.g., l2circuit/L2VPN), after committing any configuration changes, even only such as changing the description on an interface, unnecessary LDP updates might be seen. Only services dependent on LDP might be impacted during the period.

1420082

Commit error will be seen but the commit is processed if adding more than o

On EX, MX and T platforms, if "automatic-site-id is configured in BGP signalled VPLS scenario, when adding more than one site under "protocols vpls" in the VPLS routing-instances, the wrong configuration commit will be processed.

1420103

Traffic might be dropped due to LDP label corruption after RE switchover

The LDP transit egress route for a BGP route has an indirect nexthop. In NSR and GRES scenario, after RE switchover, in some cases, LDP might fail to receive route flash for a BGP route from inet.0 and would not update the inet.3 route for the BGP route. As a result, the nexthop for LDP transit egress route will become unusable and the LDP transit egress route will get deleted. It could cause BGP sessions to go down and cause traffic drop.

1422354

RSI bloat due to vmhost based log collection

Started from JUNOS 17.3, "request support information" on next-generation routing-engine is dumping vmhost side logs, which will cause RSI bloat. It might lead to the RE switchover on MX10008 as well.

1422645

LDP might not update the LDP ingress route metric when inet.3 route flash happens before inet.0

LDP route metric might not match IGP route metric even with "ldp track-igp-metric" configured.

1427987

The rpd would core dump due to improper handling of Graceful Restart stale routes

In BGP Graceful Restart scenario, including helper mode which is enabled by default, rpd would core dump due to improper handling of BGP Graceful Restart stale routes during the BGP neighbor deleting. The rpd would crash and service/traffic impact would occur.

1430878

With CNH for 6PE, MPLS EXP rewrite rule for non-VPN IPv4 over MPLS traffic might not work

On platforms that use Trio PFE (MX/EX9200/T4000), when Chained Composite Next-Hop for 6PE is configured, Class of Service MPLS EXP rewrite rule for non-VPN IPv4 over MPLS traffic ('protocol mpls-inet-both-non-vpn') may not work when a BGP 6PE route using the same MPLS LSP (same BGP next-hop) exists. This happens after the MPLS LSP next-hop is re-programmed, e.g. due to the network convergence.

1434646

Native vlan is not taking into effect when its done with flexible-vlan tagging on a L3 subinterface

Whenever native vlan config is done along with flexible vlan tagging on a L3 subinterface, untagged packets will be dropped on that L3 subinterface.

1436642

The FPC/pfex crash may be observed due to DMA buffer leaking

On EX2300/EX3400/EX4300/EX4600 platforms, DMA buffer leaking may be hit once the next-hop of received traffics is not resolved and eventually to cause an FPC/pfex crash if the DMA buffer runs exhaustion.

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.

1442078

Clients in isolated vlan might not get IP addresses after completing authentication when both dhcp-security and dot1x are configured

After Junos 18.2R1, on EX-NG platforms which support "DHCP snooping with PVLAN" (e.g. EX4300/EX2300/EX3400), when using PVLAN with dot1x and dhcp-security, and IRB interface is not configured for the PVLAN, due to the DHCP packets getting dropped on the promiscuous port, clients in isolated vlan might not get IP addresses after completing authentication.

1443204

When host bound packet received in MAP-E BR router, service interface statistics counter shows incorrect number of bytes

In MAP-E configured BR router, service interface statistics shows different number from actual packet size when BR received host bound packet from client under CE equipment.

1445637

Lawful Intercept on LAC access interface might not work as expected due to MTU check failure

On MX platforms which is configured as Layer 2 Tunneling Protocol Access Client (LAC), if Lawful Intercept (LI) is enabled on LAC access interface, in the corner case that PPPoE packet size is larger than (PPPOE MTU - 32), but smaller than PPPOE MTU, and DF bit is set for inner PPPOE IP header, the LI mirrored packets might get dropped due to MTU check failure.

1445917

Python op scripts executed as user "nobody" if started from NETCONF session, not as logged in user, resulting in failing PyEZ connection to the device.

When executed over Junos CLI, Python op script is started as a separate process with the same user as the user which started the script.However, when the python op script is started from NETCONF session, the script started as a process from user "nobody". If the script is using PyEZ session to connect to the device and execute RPC commands, it will return the following error from Pyez: ConnectError(host: None, msg: user "nobody" does not have access privileges.). This is fixed by executing with the python op script with the same user as the user from the NETCONF session which invoked op script. This means that the behavior from CLI and NETCONF sessions are the same.

1445926

The OAM CCM messages are sent with single tagged VLAN even when configuring with two VLANs

On MX platform with OAM CFM configured, if scaling number of IFLs are configured with both outer and inner vlan-tag, the outer VLAN header might missing in the OAM continuity check message (CCM) message at some interface units.

Related Links: