Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX, PTX, and QFX Series running Junos Evolved Software

Alert Description

Junos Software Service Release version 21.4R1-S1-EVO 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 21.4R1-S1-EVO is now available.

21.4R1-S1-EVO - List of Fixed issues

PR Number Synopsis Category: "agentd" software daemon
1638262 JTI UDP export support for /junos/system/cmerror/configuration and /junos/system/cmerror/counters is not working supported on chassis based systems like PTX10008/PTX10016.
Product-Group=evo 		UDP export from FPC is not working for /junos/system/cmerror/counters/ and /junos/system/cmerror/configuration/ sensors. UDP export of these sensors is working fine on fixed-form-factor systems like PTX10001/PTX10003 but is not working on chassis-based (modular) systems like PTX10008/PTX10016/PTX10004. GRPC and GNMI export of these sensors is not affected.
1641483 The 'show network-agent statistics gnmi detail' cli command is reporting packet drops for some gnmi target-defined mode sensors.
Product-Group=evo 		When a collector installs one or more gnmi target-defined mode sensors, the 'show network-agent statistics gnmi detail' cli command might incorrectly show drops accumulating for some of the gnmi target-defined mode sensors.
1641936 GNMI Capabilities() RPC returns yang module's 'latest-revision' value instead of "semantic-version"(or oc-ext:openconfig-version) for OpenConfig yang modules
Product-Group=evo 		GNMI Capabilities() RPC returns yang module's 'latest-revision' value instead of "semantic-version"(or oc-ext:openconfig-version) for OpenConfig yang modules
PR Number Synopsis Category: Border Gateway Protocol
1620463 The rpd may crash and restart when NSR is enabled
Product-Group=evo 		On all Junos with NSR (nonstop routing) enabled the rpd crash and restart may occur when RPKI (Resource Public Key Infrastructure) records are being replicated between the primary and backup RE (Routing Engine) and some of the records are withdrawn over the RPKI session.
PR Number Synopsis Category: PFE COS features on BT based platforms
1633850 evo-cda-bt core dump if "show cda qpoll" or get-state used while a PFE is offlined/faulted, then also after PFE restarted
Product-Group=evo 		On EVO PTX10001-36MR or PTX10008/-04/-16, using cli-pfe "show cda qpoll ..." or get-state while a PFE is Offlining or Off sets up evo-cda-bt to crash later, if those commands or get-state is used again when that PFE has restarted.
PR Number Synopsis Category: PFE L2 forwarding features on BT based platforms
1632255 PTX10008 EVO CFM: Transit Loopback(LB) ping / LinkTrace(LT) PDUs not forwarded transparently
Product-Group=evo 		On PTX10008 EVO, transit CCM sessions come UP, but transit Loopback(LB) ping / LinkTrace(LT) PDUs do not go through.
PR Number Synopsis Category: Express BT PFE L3 Features
1621037 Incorrect sensor modeling/mapping in the Telemetry streaming scenario
Product-Group=evo 		On PTX platforms running Junos OS Evolved, the interface sensor will export UDP data with either sensor ID 158 or 58 in the Telemetry streaming scenario. This is the incorrect sensor modeling/mapping.
1629097 PTX EVO ddos-protection protocols group arp counters not showing correct values
Product-Group=evo 		On PTX EVO platforms, ddos-protection protocols group arp counters are not showing correct values because protocol group arp arp is not supported by PTX EVO.
1632385 P2MP LSP ping and traceroute from bud-node fails when the branch is on another PFE
Product-Group=evo 		On PTX10001-36MR or PTX10004/PTX10008/PTX10016 which uses line cards PTX10K-LC1202/JNP10K-LC1202, when Point-to-Multi-point (P2MP) label-switched path (LSP) ping is initiated on a bud-node, ping fails if the brach is on another PFE. LSP ping packets will always have IP TTL as 1 on a bud-node/PHP node hence ping fails when the branch interfaces are on different PFEs.
1635130 [platform_evo] [generic] : ptx10004 :: PDT:BOWMORE:evo-aftmand-bt[20778]: [Error] Jexpr: Error reading counter|JexprStatsOverflowMgrInst|Overflow Manager: Read: Failed to read to counter pfeInst:1 and transit ngmvpn /l2vpn/l3vpn traffic dropped - post offline pfe-instance - 21.4R1.11-EVO.
Product-Group=evo 		When PFE reset triggered, there is MPLS LSP transit traffic gets wrong encapsulation and traffic getting dropped down stream. This issue will not be fixed for evo-rel-21.4R1 release. Issue applicable for PTX10K EXPR BT based platforms.
1636271 'request node halt ' may cause cm-errors.
Product-Group=evo 		The 'request node halt ' command is not fully supported by evo-aftmand-bt. The command can cause cm-errors on other FPCs as the fabric links are not gracefully shudown. Use 'request chassis fpc slot offline' to shutdown an FPC, instead
PR Number Synopsis Category: Express BX PFE L3 Features
1648156 EVO adding config "hash-key family inet layer-4" disables inet Hash-key Protocol.
Product-Group=evo 		EVO adding config "hash-key family inet layer-4" disables inet Hash-key Protocol.
PR Number Synopsis Category: Ethernet OAM (LFM)
1634721 CFM sessions are not up after evo-pfemand restart or gets crashed
Product-Group=evo 		On ACX7509/ACX7100-48L/ACX7100-32C, when a large number of CFM sessions with 10ms or 3.3ms continuity-check interval are configured and evo-pfemand process is restarted or gets crashed, then the CFM sessions may not come up even after evo-pfemand is up.
PR Number Synopsis Category: EVO cfmd RE related PRs
1623443 ethtraceroute core generated on PTX EVO
Product-Group=evo 		ethtraceroute core is generated on PTX EVO
PR Number Synopsis Category: EVO Netstack FIB Service Daemon
1612208 Egress TCP RST may not have correctly populated DSCP field
Product-Group=evo 		Egress TCP RST may not have correctly populated DSCP field
PR Number Synopsis Category: Issues related to EVO interface statistics.
1618587 PTX EVO : 'Output bytes' and 'Output packets' counter values under Transit statistics on 'show interfaces extensive' CLI decrease along with sending protocol control packets
Product-Group=evo 		On all PTX running EVO, 'Output bytes' and 'Output packets' counter values under Transit statistics on 'show interfaces extensive' CLI decrease along with sending protocol control packets. PFE can not count for a few types of Control packets under IFL statistics. When PFE reports Total count, RE displays the Transit count as Total (from the PFE) - local (all control packets count from RE).
PR Number Synopsis Category: Issues related to evo operations - libevo infra, typeinfo ..
1616114 Master RE0 reloaded unexpectedly and new-master RE1 doesn't bring up ISIS/LDP adjacencies
Product-Group=evo 		On Junos Evolved platforms with dual RE, in very rare cases, while on bootup, the rpd on backup RE might not start up due to a software defect. If later any RE switchover happens, because of no rpd running on the new master RE, complete service impact will be seen.
PR Number Synopsis Category: System Management daemon and related issues
1625834 The mastership transfer may not be triggered on each rpd crashes if switchover-on-routing-crash is configured
Product-Group=evo 		On all EVO platform with nonstop active routing (NSR) is enabled, if with switchover-on-routing-crash knob configured, issuing the CLI command "request system core-dump routing fatal" or rpd crashes occur automatically on RE0 (RE switchover occurs and RE1 becomes master), repeat this step on master RE, rpd crashes on RE1 and RE0 becomes master. Now, repeat this step on master RE again, rpd crashes on RE0 and RE switchover will fail.
PR Number Synopsis Category: Lacp related problems and issues.
1636093 Some daemons might get stuck when snmpd is at 100% CPU utilization
Product-Group=evo 		On all Junos and EVO platforms, when snmpd is at 100% CPU utilization and some daemons are trying to raise an SNMP trap, these daemons might get stuck which results in unbaling to handle any incoming corresponding packets and unbaling to response to any CLI commands.
PR Number Synopsis Category: SNMP, mib2d issues
1635958 False traffic spikes seen SNMP graphs when ifHCOutOctets or ifHCInOctets are used .
Product-Group=evo 		False traffic spikes seen SNMP graphs when ifHCOutOctets or ifHCInOctets are used .
PR Number Synopsis Category: Express PFE CoS Features
1620284 [cos] [scheduler] Scapa : scapa:10g wrong TX rate for queues configured "mix of high-low tx rates without excess bandwidth", 100GE works fine
Product-Group=evo 		Scapa : scapa:10g wrong TX rate for queues configured "mix of high-low tx rates without excess bandwidth" due to Low amount of OutPut Queue Buffer on BT chips, 100GE works fine.
PR Number Synopsis Category: Express PFE FW Features
1595788 Filter with forwarding-class and destination-class combined may not work
Product-Group=evo 		On Junos OS Evolved platforms, if a firewall filter has both SCU(Source Class Usage)/DCU(Destination Class Usage) matches and forwarding-class/loss-priority matches used on the same term in the 'from' action, the traffic supposed to be subjected to the firewall filter may not get subjected to it.
PR Number Synopsis Category: Label Distribution Protocol
1620262 LDP protections paths might not be established when "auto-targeted-session" knob is deactivated and activated
Product-Group=evo 		On all Junos and EVO platforms, MPLS (Multiprotocol Label Switching) backup paths might not be established when LDP (Label Distribution Protocol) "auto-targeted session" knob is enabled after establishing IGP (Interior Gateway protocol) paths and traffic fails until a new path is computed.
PR Number Synopsis Category: Issues related to Junos licensing infrastructure
1628733 PTX10008 EVO : license installation fails with "validation hook evaluation failed" commit error
Product-Group=evo 		On PTX10008 EVO, license installation succeeds with "request system license add terminal" CLI command, but installing the same license fails with "validation hook evaluation failed" error while performing commit.
PR Number Synopsis Category: KRT Queue issues within RPD
1638745 CCL:NGPR: RPD_KRT_RESPOSE_ERROR: krt change failed for prefix <> error from kernel is "EINVAL -- Bad parameter in request
Product-Group=evo 		EINVAL Issue is observed in EVO while installing a route with indirect next-hop ( having no-forward type ).In this scenario, after "deactivate routing-options forwarding-table export" configuration , route is flashed to KRT layer which is referring to an indirect next-hop with no-forwarding(0x2). KRT installs such route to rpd-agent with discard next-hop and it causes EINVAL error. But same trigger in Junos, kernel is treating the same event as success(#AT-43). Such issue is transient which is observed while changing configuration "deactivate routing-options forwarding-table export". Due to configuration change, all routes are flashed in KRT and its download next-hop as "discard" type.Indirect next-hop with valid forwarding next-hop is calculated later due to change in forwarding export policy and corresponding route change is flashed again in KRT for installation in kernel/rpd-agent.
PR Number Synopsis Category: PTX10K Line Card specific interface PRs
1638603 There is a mismatch between user-configured wavelength and actually transmitted wavelength on 400G-ZR wavelength setting with 75GHz spacing
Product-Group=evo 		For the 75GHz grid spacing on 400G-ZR Optics, there is a mismatch between user-configured wavelength and actually transmitted wavelength. This will lead to interface down with other vendors' devices.
PR Number Synopsis Category: PTX10K specific platform PRs
1638768 PTX10008 EVO : SNMP mib get on jnxLEDxxx generates General error with core dump
Product-Group=evo 		On PTX10008 EVO, snmp mib walk on jnxLEDxxx completes without errors, but snmp mib get on jnxLEDxxx generates General error with core dump.
1641515 FPC start time is incorrect under "show chassis fpc details" CLI command
Product-Group=evo 		FPC line card time clock might not be initialized correctly.
PR Number Synopsis Category: PTX10K Timing/Sync-E issues tracking
1635771 PTX10008 EVO Scapa : Frequent syslog "zephyr_clock_get_tod_ext_sync_sample(xxx): READ BT-X tod_sec: xxxxxxxxxx, tod_ns: xxxxxxxxx"
Product-Group=evo 		PTX10008 EVO Scapa FPC JNP10K-LC1201 frequently generates "zephyr_clock_get_tod_ext_sync_sample(xxx): READ BT-X tod_sec: xxxxxxxxxx, tod_ns: xxxxxxxxx" message
PR Number Synopsis Category: DDL/ODL infrastructure and CLI/Op commands
1632645 MXVC: Summit MX chassis communication does not work after VC member-id set/delete
Product-Group=evo 		MXVC: Summit MX chassis communication does not work after VC member-id set/delete This problem seen because host missed to reboot. Rebooting vmhost in resolves this problem.
 

21.4R1-S1-EVO - List of Known issues

PR Number Synopsis Category: "agentd" software daemon
1621347 On scaling system, load override and commit of baseline cfg can cause RPD sensors uninstallation to fail
Product-Group=evo 		On scaling system, load override and commit of baseline cfg causes RPD to spin high on CPU. As GRPC config is removed aswell, sensors needs to be uninstalled. But RPD is not responding to these telemetry sensors uninstallation requests. So sensors uninstallation fails. Later when GRPC is enabled back on box and same sensor profile( cfg .json file used with jtimon) is requested from collector, RPD is sending pkts with higher sequence numbers(Because sensor was not removed from RPD earlier) and this is considered as drops by collectors which rely on sequence-numbers.
PR Number Synopsis Category: Bi Directional Forwarding Detection (BFD)
1585644 On restart ppmd bfd flap seen with "NbrSignal Remote diag: CtlExpire Reason: Received DOWN from PEER"
Product-Group=evo 		With ISIS/BFD and RSVP on a link with link protection enabled, on PPMD restart multiple BFD sessions flaps are seen
PR Number Synopsis Category: PTX10003 Interface related issues
1615000 PTX10003 Evo-aftmand process sees memory increasing linerally over days
Product-Group=evo 		PTX10003 Evo-aftmand process sees memory increasing linearly over days
PR Number Synopsis Category: PTX10003 Platform Resiliency
1610764 Brackla: Noticing error message "evo-aftmand[27321]: [Error] Jexpr: JexprHandleDdos faile to update plct pfe:1f proto:0x8400"
Product-Group=evo 		on FPC log, when the system is up, the PFE error msg Jexpr: JexprHandleDdos faile to update plct pfe:1f proto:0x8400 will be seen. This error msg is just a debugging error msg, there is no functional impact with this log error messages.
PR Number Synopsis Category: Express BT PFE L3 Features
1628889 PTX EVO : DDoS filter does not classify OSPF packets as OSPF-Hello and OSPF-Data packet
Product-Group=evo 		OSPFv2 and OSPFv3 packets are not classified as OSPF-Hello and OSPF-Data packet by DDoS filter on PTX EVO.
PR Number Synopsis Category: CFM
1642948 CFM traceoptions writes on every other line on PTX10008 EVO
Product-Group=evo 		CFM traceoptions writes on every other line on PTX10008 EVO.
PR Number Synopsis Category: Firewall Filter
1599075 MX: SNMP WALK ON FIREWALL COUNTERS BREAKS WITH "REQUEST FAILED: GENERAL ERROR"
Product-Group=evo 		Generic error while walking through the firewall MIBs in case of list filters both on init and inet6 families (Dual Stack scenario) on same IFL. The validations were added to avoid a low probability core. And to avoid generic error, the list filters naming convention was changed to appear as different filter names for list filters when applied in Dual stack case. But, this will be a CVBC change which may not be agreed from the service releases point of view. In the mainline future releases this generic error issue will be addressed by changing the list filter names applied for init and inet6 families on same interface.
PR Number Synopsis Category: Layer 3 forwarding, both v4+v6
1604034 Some route entries are missing in HW after interface flap, when the route table scale is almost full.
Product-Group=evo 		In case of scaled scenario's with route table scale reaching upto their full limit(close to 1M), few triggers which reprograms the routing table might result in route entries getting missed in Hardware. This happens in a worst-case scenarios of prefix distribution, in real-time scenario this issue should not be seen. In real use-case scenario the internet route scale is around 800K which should be holding good.
1624365 ACX7509 :: More than 50% degradation is observed in Fib learning rate on IPv6 host routes (/128) as compared to ACX7100, only when scale exceeds 375K routes
Product-Group=evo 		The learning rate of ACX7509 is same as ACX7100 when the host routes /128 routes are within the limit of ACX7100 scale (375K) or LEM table size limit. The PR is reporting an issue only when the scale goes beyond 375K , the learning rate degrades compared to ACX7100
PR Number Synopsis Category: OAM support on DNX
1595861 acx7509 : :: pfemand as well as picd core is observed when we restart FPC on scaled config
Product-Group=evo 		If fpc is offlined/restarted with scale config or routes or mac entries, then PICD might core. PICD will come back up automatically and user intervention is not required.
PR Number Synopsis Category: EVO L2 Control Protocols Support
1628032 On Restarting l2cpd app below logs can be seen "Task l2cpd solic client: Sync with kernel taking too long, timeout" and "task_module_config: excessive runtime %.3#s during configuration of LLDP", which does not have any functionality impact.
Product-Group=evo 		On Restarting l2cpd app below logs can be seen "Task l2cpd solic client: Sync with kernel taking too long, timeout" and "task_module_config: excessive runtime %.3#s during configuration of LLDP", which does not have any functionality impact. The above logs are added to triage the issue when app is up and running. If seen during the app restart, these logs will not have any functional impact.
PR Number Synopsis Category: EVO RPD agent PRs
1623601 PTX10008 routing subsystem not running with warm-standby option enabled
Product-Group=evo 		After configuring the warm-standby option, please wait for 3 minutes before performing a RE switchover.
PR Number Synopsis Category: Junos Evolved socket replication
1627625 Transient JSR replication errors 113 / 115 seen on disable/enable OSPF
Product-Group=evo 		No functionality impact as NSR gets enabled again quickly on all protocols after the error messages. Also errors are mostly seen when rpd-agent crashes
PR Number Synopsis Category: Configd, ffp issues
1617667 [interface] [ardbeg_ifl] PTX10001-36MR :: configd publish deleted anomalies seen while running p2mp rsvp eoam test
Product-Group=evo 		In a rare event after configuring and deleting below DDL knobs, the config object correctly gets out of scope however is not released due to a shared reference: set chassis aggregated-devices set interface ae1 aggregated-ether-options There is no functional impact of the above and the situation can be cleared by restarting config daemon from CLI--> configd > restart configd
1619974 EVO: Addition/deletion of gRPC configuration can cause memory leak in EDO app
Product-Group=evo 		On EVO platforms, addition and deletion of gRPC related configuration might lead to memory leak in EDO Application, which will not impact any service/traffic.
PR Number Synopsis Category: mgd, ddl, odl infra issues
1642743 Ignore the syslog - UI_MOTD_PROPAGATE_ERROR: Unable to propagate login announcement (motd) to /var/etc/motd.junos
Product-Group=evo 		An unharmful syslog error message [UI_MOTD_PROPAGATE_ERROR: Unable to propagate login announcement (motd) to /var/etc/motd.junos] is seen in EVO in case someone configures "system login announcement". There is no functional impact and the error message can be ignored.
PR Number Synopsis Category: EVPN control plane issues
1639204 X-men Failed to forward some of the VXLAN encapsulated traffic to remote
Product-Group=evo 		For certain VXLAN encapsulated traffic streams, the X-men failed to perform L3 forward and cause traffic lost.
PR Number Synopsis Category: Express PFE FW Features
1589296 Addition/Removal of Nested Firewall filter in lo0 might result in error messages with some packet drop for short duration
Product-Group=evo 		On all PTX platforms running EVO, addition/deletion of the filter configuration in loopback interface might result in error messages with some packet drop for short duration ,which would be self-recovered.
1648037 [firewall] [generic_evo] EVO-Brackla : :: is-fragment match condition is not hitting when we send packets with more-fragment flag bit enabled
Product-Group=evo 		For Brackla/Scapa platforms, expected behavior for is-fragment match it packets would match only on fragment-offset != 0. It wouldn''t match on MF = 1 and fragment-offset = 0. If customer wants to match on first-fragment too, customers need to configure two different terms. One term matching first-fragment and second term matching is-fragment.
PR Number Synopsis Category: All Guardian (ACX7509) Linecard (FPC) related issues
1592388 ACX7509: some of the interfaces from 16x100G and 20XSFP56 will not go down after evo-pfemand restart
Product-Group=evo 		ACX7509: some of the interfaces from 16x100G and 20XSFP56 will not go down after evo-pfemand restart.
1608223 [interface] [ACX7509] Interfaces mapped to same phy flapping when any one of the interfaces speed modified
Product-Group=evo 		The momentarily link flaps are observed when different ports of variant speeds are combined within a SERDES group due to PLL shifts, so for the slot-1 and 5, the flaps are observed in groups of 8 (et-x/0/0-et-x/0/7, et-x/0/8-et-x/0/15, et-x/0/16-et-x/0/19) and other slots flaps are observed in groups of 4 (et-x/0/0 - et-x/0/3, et-x/0/4 - et-x/0/7, et-x/0/8 - et-x/0/11, et-x/0/12 - et-x/0/15, et-x/0/16 - et-x/0/19).
1614286 ACX7509: 1GE copper SFP-1GE-T optic link is not coming up with any other platforms
Product-Group=evo 		in ACX7509, 1GE interface doesnot comes up with copper 1G SFP-T optics and this issue is specific to copper 1G cables
1625165 ACX7509: 400G DAC is not coming up on restarting the FPC
Product-Group=evo 		in ACX7509, 400G DAC link doesn't comes up on FPC restart and this issue is specific to interop with QFX5220 boxes
1631193 [interface] [Guardian] 4x100g channels not coming up after multiple iterations Tx lase disabled alarm on
Product-Group=evo 		issue is not specific to guardian and issue is common to EVO platform. We need more time to analyse this issue with optic vendor and fixing in 21.4 is risky now And we have below work around for this issue and will fix this issue in next release 22.1 Work around: Port disable/Enable will bringup the link.
1635115 ACX7509: interfaces in 4x400g linecard are flapping when unrelated FPC is offlined in multiple fpc offline/online test
Product-Group=evo 		interfaces in 4x400g linecard are flapping when unrelated FPC is offlined in multiple fpc offline/online test
PR Number Synopsis Category: PFE infra to support jvision for EVO
1653129 fibtd is not sending updates to one of the gaft collectors under certain conditions
Product-Group=evo 		When using the fidtd process to update multiple collectors, the fibtd process may stop sending updates if one of the collectors is restarted.
PR Number Synopsis Category: KRT Queue issues within RPD
1612487 On backup RE during GRES, you may see "RPD_KRT_KERNEL_BAD_ROUTE: krt unsolic client.128.0.0.5+62000: lost ifl 0 for route" warning messages
Product-Group=evo 		Several warning messages show up while the RPD process restarts during performing GRES on a system running Junos EVO.
PR Number Synopsis Category: RPD Next-hop issues including indirect, CNH, and MCNH
1619229 Traffic loss observed on BGP-LU paths after restoring primary paths in setup with IGP/LDP RLFA enabled
Product-Group=evo 		Traffic loss observed on BGP-LU paths after restoring primary paths in setup with IGP/LDP RLFA enabled
PR Number Synopsis Category: PTX10K specific platform PRs
1633552 [aft] [generic_evo] : Scapa : PDT - SCAPA - FPC1 show empty, seeing ERROR on multiple applications pointing to fpc1 as Producer ID
Product-Group=evo 		Due to limitation in CBC FPGA, No interrupt is generated if Routing Engine mastership daemon stalls and a HW timer-expiry mastership switchover is initiated. Post switchover, a reboot is required on backup routing-engine before another switchover.
PR Number Synopsis Category: PTX10K Timing/Sync-E issues tracking
1649358 PTX10008 EVO scapa : SyncE clock 'hold-off-time' configuration not working due to incorrectly computed timer value
Product-Group=evo 		On PTX10008 EVO scapa, SyncE clock 'hold-off-time' configuration does not work due to incorrectly computed timer value. Only default Hold-off 1000 ms works correctly.
PR Number Synopsis Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1638489 Interoperability issue between legacy line cards and MPC10E/11E may cause incorrect load balancing over aggregate ethernet links
Product-Group=evo 		On MX platforms, due to a software defect seen in interoperability scenarios on newer AFT-based MX cards (MPC10E and MPC11E), packets entering through legacy(non-AFT) card interfaces and exiting through AE interfaces via IRB may get incorrectly load balanced.
PR Number Synopsis Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1624562 The core files can not be deleted using CLI "file delete /var/core/*/vmcore*"
Product-Group=evo 		File delete with regex may fail, if using filename without regex it works.
PR Number Synopsis Category: VNID L2-forwarding on Trio
1630163 Scenario where within a VRF multiple VXLAN type-5 tunnels with same decap prefix are not handled on MPC10/11
Product-Group=evo 		On MPC10/11 line cards, EVPN/VXLAN scenario where within a VRF multiple VXLAN type-5 tunnels with same decap prefix are created is not well handled, which might lead to traffic drop.
 

Modification History

First publication 2022-03-09