Open Issues

In Provider Backbone Bridging - Ethernet VPN (PBB-EVPN) environment, ARP suppression feature which is not supported by PBB might be enabled unexpectedly. This could cause MAC addresses of remote CEs not to be learned and hence traffic loss. PR1529940

On all Junos OS and Junos OS Evolved platforms that support Type-2 (T-2) Integrated Routing and Bridging (IRB) symmetric routing, EVPN virtual extensible LAN symmetric type-2 route needs to be imported in L2 mac-vrf instance for IP host route to be added in Layer 3 vrf. Layer3 inter-subnet routing will fail if there is no reachability for the remote IP-host route.PR1669585

On all platforms, MAC-IP route deletion and addition are triggered when Address Resolution Protocol (ARP) on multihoming device fails in the EVPN-MPLS multihoming scenario resulting in traffic drop. PR1691132

On all Junos OS dual-Routing Engine platforms, when activating and deactivating GRES multiple times, you will observe synchronization issues between the primary and backup dfwd process. PR1697959

If a vmhost snapshot is taken on an alternate disk and there is no further vmhost software image upgrade, the expectation is that if the current vmhost image gets corrupted, the system boots with the alternate disk so the user can recover the primary disk to restore the state. However, the host root file system and the node boots with the previous vmhost software instead of the alternate disk. PR1281554

When VLAN is added as an action for changing the VLAN in both ingress and egress filters, the filter is not installed. PR1362609

FPC crash on MX240 and MX2020 routers or Packet Forwarding Engine crash on MX104 routers might happen when the MIC-3D-8OC3-2OC12-ATM is installed and ATM interface is configured. PR1453893

VXLAN VNI (multicast learning) scaling on QFX5110 traffic issue is seen from VXLAN tunnel to Layer 2 interface. PR1462548

When there are HW link errors occurred on all 32 links on an FPC 11. Because of these link errors, all FPCs reported destination errors towards FPC 11 and FPC 11 was taken offline with reason "offlined due to unreachable destinations". PR1483529

runt, fragment and jabber counters are not incrementing on EX4300-MPsPR1492605

After backup Routing Engine halt, CB1 goes offline and comes back online; this leads to the backup Routing Engine booting up, and it shows the reboot reason as "0x1:power cycle/failure." This issue is only for the RE reboot reason, and there is no other functional impact of this. PR1497592

* When an AMS ifd is configured for the first time or any member of the AMS bundle is removed or added, the PICs on which the members of AMS bundle are present go for a reboot. * There is a timer running in the AMS kernel which is used as a delay for the PIC reboot to complete and once that timer expires AMS assumes that the PICs might have been rebooted and it moves into next step of AMS fsm. * In scaled scenarios, this rebooting of the PIC is delayed due to DCD. This is because when a PIC goes down, DCD is supposed to delete the IFDs on that PIC and then the PIC reboot happens. * But DCD is busy processing the scaled config and the IFD deletion is delayed. This delay is much greater than the timer running in AMS kernel. * When the above timer expires, the FSM in AMS kernel wrongly assumes the PIC reboot would be completed by then, but the reboot is still pending. * By the time DCD deletes this IFD the AMS bundles are already UP. Because of this, there is a momentary flap of the bundles. PR1521929

In Mac-OS platforms when Juniper Secure Connect client connects successfully, the client is not getting minimized to tray icon and needs to be minimized manually.PR1525889

IPSec rekey fails when SRX is configured with kilobyte based lifetime in remote access solution. PR1527384

Due to BRCM KBP issue route lookup may fail. Need to upgrade KBP to address this issue, Due to high risk KBP SDK upgrade planned for 21.1. PR1533513

In scaled mx2020 router, with vrf localisation enabled, 4 million nexthop scale, 800k route scale. FPCs may go offline on GRES. Post GRES, router continues to report many fabric related CM_ALARMs. FPC may continue to reboot and not come online. Rebooting master and backup RE will help recover and get router back into stable state. PR1539305

Unsupported config is being attempted by the script that then hits the maximum threshold for the given platform PTX5000PR1555159

5M DAC that connects QFX10002-60C and MX2010 doesn't link up. But with 1M and 3M DAC this interoperability works as expected. Also, on QFX10002-60C and ACX Series devices or on traffic generator, the same 5M DAC works seamlessly. Need to debug certain SI or link level configuration on both QFX10002-60C and MX2010 with the help from the hardware and SI teams and resolved. PR1555955

With IPsec PMI or fat-core enabled, the CLI show services sessions utilization do not display the appropriate CPU utilization. PR1557751

The Sync-E to PTP transient simulated by Calnex Paragon Test equipment is not real network scenario. In real network deployment model typically there will be two Sync-E sources (primary and secondary) and switchover occurs from one source to another source. MPCE7 would pass real network SyncE switchover and associated transient mask. PR1557999

VE and CE mesh groups are default mesh groups created for a given routing instance. On vlan/bridge-domain add, flood tokens and routes are created for both VE and CE mesh-group/flood-group. Ideally, VE mesh-group does not require on a CE router where IGMP is enabled on CE interfaces. Trinity based CE boxes have unlimited capacity of tokens, so this would not be a major issue. PR1560588

This is a feature enhancement and work is in progress to provide this support. This will have impact only when routing daemon crashes and will not have impact on rest of the NSR support. PR1561059

Due to a race condition, the 'show multicast route extensive instance instance-name" output can display the session status as Invalid. Such an output is a cosmetic defect and not indicative of a functional issue. PR1562387

To avoid the additional interface flap , interface hold time needs to be configured . PR1562857

Service MIC does not work on ACX500 running Junos 20.4 or higher. PR1569103

On PTX platforms, when Inline Jflow is configured and high sampling rate (more than 4000 per second) is set, high CPU utilization may be observed and this might result in relevant impacts on traffic analysis and billing. This issue is fixed from 21.3R1 via RLI 49464.PR1569229

On QFX5100, Media type for SFP+-10G-CU1M and SFP-T cables are shown as Fiber. This is only a display issue and no functionality impact is observed.PR1570555

This issue is caused by /8 pool with block size as 1, when the config is committed the block creation utilizes more memory causing NAT pool memory shortage which is currently being notified to customer with syslog tagged RT_NAT_POOL_MEMORY_SHORTAGE. PR1579627

On MX platforms the JDM (Juniper Device Manager) server could not be created in in-chassis mode of junos node slicing, which results in mgd process crash and affects GNF's (Guest Network Function) provisioning. PR1583324

When the active slave interface is deactivated, the PTP lock status is set to 'INITIALIZING' state in 'show ptp lock-status' output for few seconds before BMCA chooses the next best slave interface. This is the day-1 behavior and there is no functional impact. PR1585529

On all devices running Junos 19.1R3-S5-J3, the subscriber IFL(logical interface) may be in a stuck state after the ESSM (Extensible Subscriber Services Manager) deletion. PR1591603

On QFX5110 VC, FPC may gets disconnected with 24K DHCPv6 relay scaling, after the traffic is stopped. "pfe_listener_disconnect" error messages may be seen.PR1594748

Pim Vxlan not working on TD3 chipsets enabling VxLAN flexflow after release 21.3R1. Customers Pim Vxlan or data plane VxLAN can use the Junos OS Release 21.3R1. PR1597276

MX2010, MX2020: MPC11E: ISSU is not supported for software upgrades from 21.2 to 21.3 and 21.4 releases due to a flag day change PR1597728

During RE switchover, if there is a burst of ICMP/BFD/SSH/FTP/TELNET/RSVP packets (~18K pps) you might see new backup RE restarting. PR1604299

On MX-VC (Virtual Chassis) platforms with MS-MPC or SPC3 service cards and AMS(Aggregated Multi-Service), traffic on the line card in the backup chassis may not be load-balanced properly due to timing conditions. This works well on the line card in the master chassis. There might be traffic loss when interfaces are not properly balanced.PR1605284

On all MX Series platforms, in a subscriber management environment, new subscribers might not connect if Class of service (CoS) CR-features (Classifier Rewrite) are used by the VBF (Variable Based Flow) service. The reference count mismatching between RE (Routing Engine) and VBF is caused by VBF flow VAR CHANGE failure. PR1607056

When user tries to disable AMS ifd using config knob, the ipsec tunnels are not deleted. Deactivating the services will provide the desired result. PR1613432

In some NAPT44 and NAT64 scenarios, Duplicate SESSION_CLOSE Syslog will be seen. PR1614358

On all Junos platforms the MAC address of the 17th ae interface might be changed after the upgrade from 18.4+ to 20.4+ releases. It will lead to mac based service interruption.PR1629050

For a topology with VSTP and VRRP configured and IPV6 traffic, if VSTP bridge priority is changed a couple of times (to trigger toggling of root bridge), it is possible that V6 traffic drop is seen on some of the streams. PR1629345

For ACX5448, MX204 and MX2008 "VM Host-based" platforms, starting with Junos 21.4R1 or later, ssh and root login is required for copying line card image (chspmb.elf for MX2008) from Junos VM to Linux host during installation. The ssh and root login are required during installation. Use "deny-password" instead of "deny" as default root-login option under ssh config to allow internal trusted communication. Ref https://kb.juniper.net/TSB18224 PR1629943

On MX platform with enhanced subscriber management enabled, when "host-prefix-only" is configured on the underlying-interface for subscribers, it might not work in FPC. PR1631646

The fabric statistics counters are not displayed in the output of "show snmp mib walk ascii jnxFabricMib". PR1634372

On all devices running Junos OS or Junos OS Evolved, where this is a high BGP scale with flapping route and the BGP Monitoring Protocol (BMP) collector/station is very slow, the rpd process might crash due to memory pressure.PR1635143

Source MAC should nt be configured on the underlying static interface on the UP for PPPoE login to work correctly.PR1641495

WIth PTPoIPv6 on MPC2E 3D EQ, PTP slave stays in acquiring state.PR1642890

When CFP2-DCO is used, operator need to configure otn-option - that is the only mode supported PR1643815

On MX10004, MX10008, and MX10016 platforms, oamd process do not start and GRE keepalives adjacency goes down. PR1644480

Committing configuration changes during the Packet Forwarding Engine reset pause window (when Packet Forwarding Engine is disabled, yet the Packet Forwarding Engine reset proper has not started yet) has the potential of causing errors and traffic loss. In particular, config changes that result in re-allocating policers (which are HMC-based) might lead to traffic being entirely policed out (i.e. not flowing). Once the Packet Forwarding Engine reset procedure has started config changes ought to be avoided until the procedure is completely done.PR1644661

bb device has to be manually enabled in configuration for DHCP and PPP access models for BNG CUPS. Configuration to enable bb device is as follows:: #set system subscriber-management mode force-broadband-devicePR1645075

When per-interface egress and per-sid egress SR sensor stats are configured using the CLI commands below, the (pushed) MPLS label length does not get included in the output/Tx octets field that gets exported from the sensor. set protocols isis source-packet-routing sensor-based-stats per-interface-per-member-link egress set protocols isis source-packet-routing sensor-based-stats per-sid egress This is a day-1 behavior on all Trio ASIC based FPCs on the MX platform.PR1646799

With overlapping NAT pool configured with different NAT rules under different service sets, when service outside interface is moved between different routing instances (EX: from vr1 to default, and from default to vr1), NAT routes corresponding to the service-set in default routing instance are getting deleted, resulting in reverse path traffic failure for NAT sessions. PR1646822

In the IPv6 segment routing deployment, packets are sent out with the wrong ethernet type. PR1647622

Core file is generated intermittently where random grpc stack crashes. The license service will auto restart and recover. PR1656975

ZTP: DHCPACK is not received at ztp-server after zeroizing the client device. PR1658287

On Junos OS platforms, in the VPLS environment configuring the CLI routing-options resolution preserve-nexthop-hierarchy results in the packet drop at the egress PE device for multiple MPLS stack labels.PR1658406

The OpenSSL project has published security advisories for multiple vulnerabilities resolved in OpenSSL. Please Refer to JSA70186 for more information. PR1661450

The version details for certain daemons will appear in the command output after the device has been rebooted after the completion of the USB installation of Junos OS.PR1662691

Not all MAC addresses are learnt for some VPLS instances after clear vpls mac-table command is executed. PR1664694

Egress PE device rpd core file at ctx_module_config (ctx=0x2dbb914 < task_args>, errmsg=0xffffc764 "Module 0x2d753e0 Name BGP Failed in Config Pass 2, LSYS=default", elen=2048) at ../../../../../../../../src/layer3/usr.sbin/rpd/lib/ctx/app_ctx_module.c:115.PR1667320

On MX Series platforms with MIC-MACsec-20GE, Forwarding Engine Board (FEB) might go down while activating and deactivating GRES configuration.PR1668983

License-check core file is generated upon reloading the system after applying specific set of configurations. No issues will be seen when the system comes up. PR1671419

In the case of an active-active lease query stale-timer configuration is mandatory. This is required to optimize the synchronization time, as both peers get the solicit packets at the same time. As a workaround, the set forwarding-options dhcp-relay stale-timer 20 configuration statement can be used. PR1671589

Sometimes core file is generated on the backup Routing Engine during init after a reboot. When the backup Rounting Engine initializes and the system is busy, some commands executed in context of spmbpfe takes more time to complete due to the initial heavy lifting by the kernel. In this stage, if in case the commands from spmbpfe process do not complete in 2.5 seconds, then there are chances of generating spmbpfe core files. This is a temporary issue seen on the backup Routing Engine during init time. This might not impact because if in case spmbpfe process crashes due to this, it might restart by itself and continue to init and run once the initial high CPU condition has passed. It should not cause any functionality or performance impact; especially since it is reported only on the backup Routing Engine. PR1675268

On SyncE over LAG interfaces, if the end points have different ESMC QL configured, on one of configured syncE interface, ESMC QL is toggling between PRC and DNU and sync-E does not lock and moves to holdover state. PR1677131

The physical interface remaining statistics flag is not set properly in chassid in today's code. It should be set to TRUE only if HCOS is configured on an interface. Else, it should not be SET. Not setting this rightly, results in statistics not being displayed OR the command output not being displayed at all. The impacted command is run show interfaces extensive intf-name and the impact is seen in GNF environment with no explicit CoS configuration on the interfaces. Not using "extensive" will ensure there is no issue as well. This is specific to MPC11 with sub LC (GNF) setup.PR1678071

There will be drop of syslog packets seen for RT_FLOW: RT_FLOW_SESSION_CREATE_USF logs until this is fixed. This will not impact the functionality.PR1678453

Observing FPC MQSS WAN reorder timeout errors after the device reboots. PR1681763

If MVRP is enabled on an MSTP enabled interface, the interface will be made part of all the existing instances on the switch. PR1686596

On Junos OS platforms, error messages are seen with traffic drops on the labelled route present in mpls.0 resolving over an IPv6 prefix. PR1698516

On MX Series platforms, traffic egressing on the integrated routing and bridging (IRB) interface with the underlying Layer 2 access port that has VLAN tags imposed incorrectly.PR1700321

Identify and report fabric link errors caused due to connector related issues.PR1700983

When subscribing to sensor paths "/junos/system/linecard/packet/usage/", "/junos/services/label-switched-path/usage/" or other line card (PFE) sensor paths in gNMI subscription mode, packet drops may be seen in the CLI command "show network-agent statistics gnmi detail" output. The collector output may also contain missing sequence numbers. For example, the sequence number output may be 0, 3, 6, 9, 12, etc. instead of 0, 1, 2, 3, 4, etc. PR1703418

In Chassisd, Jvision thread takes more time in streaming of jvision packets because of volume of data and number of sensors involved with this daemon. Jvision thread engaged for more time to process streaming events caused Chassisd master thread to lose receive/send keepalive messages to/from other RE, which eventually was causing automatic RE switchover in most of the cases. To avoid this, fix done for exporting small payload jvision packets (formation of which takes less time) and deferring jvision thread more in an interval, to allow chassisd master thread to process high-priority hello/keep-alive messages. This means now, more number of packets is sent in one reporting interval and with larger spread (earlier same amount of data was sent with 2 or 3 packets of higher payload size, and 100ms of deferring time for jvision thread. This behaviour is increasing KPI-2 but lowering KPI-1 (payload size). It is not possible to back out changes done to solve keep-alive message loss issue. Hence we will have to keep Chassisd as an exception, when we measure/report KPI-2 values. Jvision in Chassisd has to give more priority/time to process keep-alive messages than sending of jvision packets. Hence delay between jvision packets are more.PR1706300

When "routing-service" is enabled for a PPPoE Subscriber over AE, the subscriber will not have network access due to traffic drops.PR1706446

In a Virtual-chassis (VC) scenario on Junos MX platforms installed with MPC7E Flexible PIC Concentrators (FPC), if the inline-jflow Sampling is enabled, the Inline Flow Monitoring is not working as data is not getting exported to the collector.PR1708485

When you upgrade to new Junos OS release and apply the configuration, the rpd might create parallel MBBs due to this number of nexthops might increase and on-chip memory exhaustion might happen at FPC. This can lead to FPC crash. Issue should not be seen once system settles down. PR1710362

When subscribing to sensor paths "/junos/system/linecard/packet/usage/" in gNMI subscription mode, packet drops ((gNMI translator lookup failures)) may be seen in the CLI command "show network-agent statistics gnmi detail" output for empty dummy packets (packets which do not have a prefix or key-value data). The collector output may also contain missing sequence numbers. For example, the sequence number output may be 0, 3, 6, 9, 12, etc. instead of 0, 1, 2, 3, 4, etc.PR1711779

The packets are being dropped when they come from the VC (Virtual Chassis) link into member in the MX Virtual Chassis with MPC10 line card.PR1712790

After GRES with disabled em0 (or fxp0), the subnet assigned to em0 (or fxp0) remains down on the new backup, even after the interface is re-enabled. PR1372087

Logical interface packet counters are not implemented for AMS interface. It is a new change. Changes are planned for next release 22.4R2PR1673337

When the MPC10 and MPC11 FPCs restart, error logs related to invalid anchor next hops are seen with distributed aggregated Ethernet IRB VRRP sessions. The aggregated Ethernet interfaces must span multiple FPCs. PR1674069

With IXIA connection, we do not receive an ARP response in the DUT port to store the destination MAC address. Unable to determine the ARP response if the issue is with the MX Series port or medium or IXIA port. PR1677624

On MX Series platforms, in a rare scenario, Flexible PIC Concentrator or Sub Line Card (FPC/SLC) might get stuck in the ready state after restarting. You will observe a syslog error message 'Device busy'. PR1682271

This issue is specific to MX Series Virtual Chassis and the issue is not seen during manual execution of the test case. Issue is seen only with the test script that too rarely and hence the exact trigger of the issue. is not clear.PR1686425

On all Junos platforms, while performing an upgrade from prior to Junos OS Release 20.4 and later with an incorrect configuration may fail. This issue may lead to traffic loss or network outages.PR1692404

On Junos OS MX Series Virtual Chassis, Chassis Control Link (CCL), and Cyclic Redundancy Check (CRC) errors can be seen after Flexible PIC Concentrator (FPC) detach during the sequential operating system upgrade of MX-VC system. The CCL and CRC errors are expected after the FPC detaches and eventually, the FPC is marked offline by the MX-VC and there is an unexpected chassisd process restart. The chassisd restarted because of the connection failure between Linecard Chassis Control (LCC) chassisd and Switch Chassis Control (SCC) chassisd which is triggered by the sequence of messages exchanged between the LCC and SCC after the FPC detach event. There will be a traffic impact as the FPC will be offline, and the system recovers to a working state by itself. PR1706268

MPC7E firmware upgrade in MX Series Virtual Chassis cannot be completed.PR1713502

L2TP LAC functionality do not work in this release. PR1642991

In case of the access-side interfaces used as SP-style interfaces, when a new logical interface is added and if there is already a logical interface on the physical interface, there is 20-50 ms traffic drop on the existing logical interface. PR1367488

In MVPN case, if the nexthop index of a group is not same between master and backup after a nsr switchover, we might see a packet loss of 250 to 400 ms. PR1561287

Ingress will retry after LSP stay down for extended period of time or customer can clear LSP to speed up the retry. PR1631774

On all Junos OS and Junos OS Evolved platforms, if Circuit Cross-Connect (CCC) is configured to use a label-switched path such as IGP routed, that is, no-cspf and no strict explicit route object (ERO) configuration, then restarting egress CCC node or restarting FPC on the egress CCC node containing remote-interface-switch configuration multiple times might cause CCC to remain stuck in remote-if-down state, resulting in loss of traffic. The statement remote-interface-switch is configured on the egress LER of the Resource Reservation Protocol-Traffic Engineering label-switched path (RSVP-TE LSP) which binds the LSP terminating on the node to a local interface. PR1694777

When an LSR acts as a Point of Local Repair (PLR) as well as a Merge Point (MP) for an LSP during a double failure scenario, the LSR incorrectly originates one or two PathErr messages with RoutingProblem (code=24/2) instead of originating PathErr with NotifyError (code/subcode=25/3). This will not cause any service impact if the ingress LER would not react adversely to RoutingProblem error (code=24/2).PR1713392

When maximum-password-length is configured and user tries to configure password whose length exceeds configured maximum-password-length, error is thrown, along with error 'ok' tag is also emitted. The configuration do not get committed. PR1585855

On all Junos OS and Junos OS Evolved platforms, while using source-address NTP configuration parameter and issue the command set ntp date from the CLI, packets will be sent with the source address of the outgoing interface rather than the manually configured IP address. Typically, the manually configured IP address will be a loopback address. The problem does not apply to automatically generate the NTP poll packets. PR1545022

When the deactivate services rpm and deactivate routing-options rpm-tracking configuration statement are applied together and then committed, some of the rpm tracked added routes are not deleted from the routing table. Issue cannot be seen using the following steps.

1. deactivate routing-options rpm-tracking

2. commit the configuration then all the rpm tracked routes will be deleted. If the RPM service needs to be deactivated,

3. deactivate services rpm

4. commit

PR1597190

With given multi dimensional scale, if configuration is removed and restored continuously for more than 24 times, MX Series FPC might crash and restart. During the reboot, there can be traffic impact if backup paths are not configured. PR1636758

On all platforms, the issue is when the first time when ESIS is coming up sometimes the ESIS route might not get installed. PR1559005

When l2cpd (in the context of xSTP) clears the entries that it has programmed on ppmd, that is, when you delete xSTP configurations from the box, there is a possibility of generating a ppmd core file. If ppmd is in distributed mode then there will be no service impact, else there can be a service impact as packet transmission for various protocols will happen via if ppmd is in centralized mode.PR1660299

On all Junos OS and Junos OS Evolved platforms, whenever there is high percentage of background CPU usage that causes the rpd to run at average CPU load. BGP convergence will be slow, which results in traffic loss. PR1663883

Any platforms with micro BFD configured on member links of the LAG and aggregated Ethernet interface, BFD Session state in Routing Engine remains as UP always even though PEER device has ceased. PR1675921

On all Junos OS and Junos OS Evolved platforms, the rpd crashes when protocol independent multicast (PIM), multicast only fast reroute (MoFRR) configuration is present and some network churn event such as continuous interface cost changes, resulting in a change of active and backup paths for ECMP occurs. There will be service impact because of the rpd crash but the system self-recovers until the next crash. PR1676154

Junos OS Release 22.3 and later, IS-IS yang is uplifted to 1.0.0 version which has major change in existing OC path that was supported earlier. Since OC path has change, same need to be reflected in translation script which is not done. As part of D27 release for cloud, translation script will be modified with newer OC path. Until then, older OC configuration is broken. eventually D27 code will come back to DCB and things will work fine after that.PR1686751

On all Junos OS and Junos OS Evolved platforms BGP Labeled-Unicast (BGP-LU) advertisements fail with the message "BGP label allocation failure: Need a gateway" based on timing conditions involving route resolution and installation.PR1689904

On Junos OS platforms, if a BGP peer is going down and stays down and the system might take an extremely long time to complete removing the BGP routes. The issue observed when a BGP peer sends many routes, only a small amount of routes are selected as the active routes in the RIB (Routing Information Base), and if the BGP delete job gets only a small part of the CPU time as the CPU shards with other work in the routing process.PR1695062

This issue is seen with only evo and not seen Junos. Its seen in a combination of Rsvp and ISIS. Stats is getting incremented PR1700063

On all Junos OS and Junos OS Evolved platforms, when an IPv4 prefix advertisement received by an IS-IS/OSPF router in the Extended IP reachability TLV and SR mapping server (SRMS) advertisement for the same prefix received through the segment identifier (SID) label Binding TLV, then SRMS advertised label preferred over IS-IS/OSPF SID label advertised via opaque-AS extended-prefix. Traffic will be sent via wrong path due to this issue.PR1702456

On all Junos OS and Junos OS Evolved platforms, the mcsnoopd process crashes. This issue is seen when the devices support the VLAN (Virtual Local Area Network) style of internet group messaging protocol (IGMP) igmp-snooping configuration set protocols igmp-snooping vlan vlan_name and the VLAN name begins with the word all and has certain other characters. The workaround is not to enable the snooping for such VLANs.PR1711153

When routing information base (RIB) contains IPv4 routes with IPv6 next-hops, these routes do not get re-advertised by IPv4 EBGP sessions unless export policy is configured to change it to IPv4 next-hop.PR1712406

When a configured tunnel interface is changed to another one, flow-tap-lite functionality stops working that is, packets do not get mirrored to content destination. But, this problem isn't consistently seen. PR1660588

Tunnel debugging configuration is not synchronized to the backup node. It needs to be configured again after RG0 failover. PR1450393

Change here is basically reverting to old enum value used for ATM VPN, and using a new value for BGP multicast address family, and although these is no visible behavior change due to this, there may be impact on ISSU for ATMVPN and BGP multicast address family if enabled.PR1590331

When using group VPN, in certain cases, the PUSH ACK message from the group member to the group key server may be lost. The group member can still send rekey requests for the TEK SAs before the hard lifetime expiry. Only if the key server sends any new PUSH messages to the group members, those updates would not be received by the group member since the key server would have removed the member from registered members list.PR1608290