Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Resolved Issues: 21.3R1

General Routing

  • VCCV type 1 connectivity verification is not supported. PR1503724

  • The mpls-label does not reap out when configured for SR-sid ingress sensors. PR1516811

  • A set of info level no passwd entry cron logs are displayed in every 1 minute. PR1527266

  • Global port-mirroring applied with deactivation does not display XML correctly for PTX10003 platforms. PR1529413

  • The show chassis alarms command must be redirect to the show system alarm. PR1536020

  • The port mirroring stops working for the FTI interface when the GRE source is changed. PR1536223

  • On PTX10003-80C routers, configuration archival might not work. PR1540843

  • CPU utilization of evo-aftman process goes to 100 percent in a certain scenario on PTX Series devices. PR1562328

  • Layer 2 interface information is not included in DHCPv4 option-82 circuit-id or remote-id and DHCPv6 relay-agent-interface-id or relay-agent-remote-id options when service provider style configuration for switch interfaces is employed. PR1564010

  • Drop counts in the show interfaces voq ae0 command might not match with the show interfaces queue command when the clear interface command is issued while traffic is flowing. PR1567598

  • The request system zeroize command does not delete snapshot images from the backup HDD. PR1569294

  • On PTX10008 platforms, user script output must be logged during the ZTP execution for determining failure in the logs. PR1570167

  • A certain leaf in the /components/component[name='FPC1:CPU']/properties/property/cpu-utilization-total is not available. PR1571502

  • On the PTX10008 platforms, the communication failure with /fpc0/evo-aftmand-bt/ CLI timout error and traffic loss might be observed. PR1574513

  • IPv6 traffic loss might be observed after NSR SWO. PR1576369

  • On PTX10008 platforms, incorrect capacity value is shown on the JNP10K-PWR-AC2 and JNP10K-PWR-DC2 PSM. PR1578682

  • FPC status LEDs are not turning RED during power fault. PR1579466

  • The Packet Forwarding Engine function might break down on all the FPCs after performing Routing Engine switchover on the Junos OS Evolved platforms. PR1579683

  • An FPC is stuck in onlining state and reboots continuously during unified ISSU. PR1580374

  • The l2cpd process might crash on the Junos OS Evolved platforms with dual Routing Engines. PR1580479

  • The Junos Telemetry Interface properties are missing after HwD app restart. PR1580735

  • In certain scenarios, shapers applied on a 10G interface might drop the traffic more than the configured max-rate. PR1580795

  • The timingd process might crash post NSR. PR1581270

  • Streaming over IPv6 fails in the Junos OS Evolved platforms. PR1581341

  • The rpd process might crash on the new primary Routing Engine after performing the graceful switchover. PR1581878

  • The rpd process generates a core file after Routing Engine switchover. PR1582095

  • On PTX10004 platforms, after disabling active path, forcing FRR shows large traffic loss and increased irp.core.trapcode.cfg_err counter. PR1582170

  • On PTX10008 platforms, the show chassis craft-interface command does not show correct PSM LED status. PR1582444

  • Node locked license addition fails. PR1582704

  • There might be a failure of the config-sync service and a major system alarm is raised after upgrade. PR1582717

  • The Junos telemetry interfaces leaves /components/component[name='FPC2:PIC1:PORT0:Xcvr0']/transceiver/state are missing. PR1583076

  • On PTX10008 platforms, grpc core files might be seen on a large number of telemetry subscriptions. PR1583161

  • The system might crash if you configure IPv6 FBF with prefix /88. PR1583374

  • On PTX10008 platforms, the show chassis clocks command must be handled in a graceful way or with a meaningful error. PR1583715

  • The FRR convergence number is high with ALB enabled on the aggregated Ethernet bundle. PR1583866

  • The ospf-hello DDoS statistics pktCnt is listed as 0. PR1584458

  • The vmcore files are generated after performing the switchover. PR1585436

  • After PIC goes offline and then online, the show interfaces queue intf command shows large values for cumulative tail-drop and RED-drop packets and bytes. PR1585552

  • Packet loss might be seen during global repair of FRR. PR1586122

  • On PTX10008 routers, need to add HBM statistics for the network processing unit (NPU) sensor. PR1586148

  • The RPD_KRT_KERNEL_BAD_ROUTE error message is seen in certain scenarios when the rpd process restarts or GRES happens when NSR is enabled. This error has no functional impact. PR1586466

  • Removing SIB without turning offline first might impact traffic. PR1586820

  • The Junos Telemetry Interface leaves such as used-power and allocated-power under /components do not reflect correct values. PR1587184

  • The exported header of the NPU sensor is changed to match Junos OS. PR1588242

  • On PTX10008 platform, error or warning messages are appeared when issuing request chassis cb slot 1 offline command before node goes offline. PR1589433

  • Traffic loss is observed on global repair after disabling the active path forcing FRR. PR1589803

  • Sensor statistics might not be displayed accurately in the show network-agent statistics operational command for the data generated from multiple nodes. PR1590249

  • On PTX10008 platforms, the Packet Forwarding Engine might get stuck in ready state with anomalies type net::juniper::fabric::fabricPfeE. PR1590319

  • VM core files are observed when performing switchover. PR1590372

  • Non-zero values might be displayed against the drop field in the show network-agent statistics CLI command output post switchover scenarios. PR1590432

  • FPC goes offline after switchover if the system has power shortage. PR1592004

  • On PTX10008 platforms, picd log floods when there is the following system alarm: Optics does not support configured speed. PR1592165

  • The aftmand process might crash when an interface is configured with the analyzer. PR1592267

  • The ZTP occasionally fails to apply user configuration after the system upgrade. PR1592281

  • The duplicate Junos Telemetry Interface leaf of oper-status tag for logical interface index 16386 have mismatch value. PR1592468

  • The firewall filter might not take into effect on Junos OS Evolved PTX Series platforms. PR1592500

  • On the PTX10008 and PTX10001-36MR platforms, sFlow sample-rate configuration greater than 16000000 is not supported. PR1592788

  • Port related component sensor does not get exported when subscribed to the /components/component/state/ path. PR1593031

  • After Routing Engine switchover, the following error messages are seen: JexprSlowCntrRead - Unable to get the plct Inst for pfeIdx: 255, User-type: OVFM_OFFCHIP_NEXTHOP_CNTR.PR1593079

  • The rpdagent crashes on the primary Routing Engine after multiple GRES with GR and NSR enabled. PR1593104

  • The port mirroring instance might be down on Junos OS Evolved based platforms. PR1593276

  • Load balance might not take effect for the Layer 2 VPN traffic on the PTX10008 platforms. PR1593548

  • The node name must not be attached to the system hostname under LLDP. PR1593991

  • The evo-pfemand might crash after restarting app evo-pfemand. PR1594331

  • The BFD session for MPLS LSP goes down after enabling ultimate-hop-popping. PR1594621

  • The type leaf value for FPC3:PIC0:PORT0:XcvrX displays XCVR. PR1595103

  • On PTX10008 platform, inconsistent component name for FPC CPU. PR1595109

  • On PTX10008 platforms, application error alarms and trace-writer core files are generated due to defunct rcp zombie. PR1595409

  • Layer 2 VPN stops forwarding when interface encapsulation is changed to vlan-ccc from ethernet-ccc and back. PR1595455

  • Some TCP sessions might not be established after performing the request system snapshot command. PR1595470

  • On PTX10008 platforms, default wavelength for 400G ZR module is incorrect. PR1595498

  • The applications might crash if the publishing parent objects linked child objects are published by different applications. PR1595846

  • On 400G ZR, logical interface creation fails after adding or deleting invalid speed configuration. PR1597022

  • The following error message is observed: cannot find ifToken for counterType:12. PR1597355

  • The aftmand core file might be observed on all Junos Os Evolved platforms. PR1597649

  • Major host 13 Ethernet interface link down false alarm is seen after Routing Engine 1 replacement manually. PR1597763

  • Master-only IP address keeps in old master (new backup) and device becomes inaccessible after Routing Engine switchover. PR1598173

  • Due to issue in AGEOUT notification for inline sessions, sessions remains up till peer sends BFD down packet or BFD client brings it down. PR1599257

  • FTC status LED and SIB power LED are unlit or off on PTX10008 platforms. PR1600178

  • The config interface ip remove command is not working correctly. PR1600932

  • On PTX10008 routers, the set chassis redundancy routing-engine 1 mastercommand does not change the default Routing Engine election priority. PR1601430

  • On PTX10008 routers, AFTMAN core files are seen at jexpr_if_logical_l2d_alloc while powering off or on all the Packet Forwarding Engine across all the FPCs. PR1602035

  • On PTX10003 platform, IRB ping fails post power off or power on underlying Packet Forwarding Engine for aggregated Ethernet child member. PR1602181

  • GRE keepalive packet with recursion control bit set gets dropped on PTX10003 platforms. PR1602353

  • Continuous FPC restart might be observed on Junos OS Evolved platforms with the firewall policer configuration. PR1602446

  • On PTX10008 routers, powering off Packet Forwarding Engines displays the following error message: Jexpr: deleteFdbEntry: Null. PR1602670

  • The following error message is observed: evo-aftmand-bt[18089]: [Error] IfStats:map entry not present for ifl:1039. PR1604334

  • The channel 0 physical interface does not come up after adding the correct speed configuration. PR1604810

  • The host loopback wedge might be detected in the Packet Forwarding Engine when deleting the aggregated Ethernet bundle configuration. PR1605599

  • On PTX10008 platforms, fan tray controller removal or absence alarm is generated. PR1605987

  • The DNS lookup might fail on all Junos OS Evolved platforms. PR1607505

  • On PTX10008 platforms, defunct rcp increases due to transport-alarm-statsd daemon. PR1608776

  • On PTX10008 platforms, the evo-aftmand-bt.fpc_x86_64 core file is seen @ jexpr_pile_malloc with LSR core profile configuration. PR1608999

  • High priority queue might not get the expected bandwidth on the Junos OS Evolved platforms. PR1609823

  • On PTX10001-36MR, PTX10004, and PTX10008 platforms, IS-IS does not come up when network type is P2P for IRB interface. PR1612606

  • Mitigate false wrap of drop statistics when physical interfaces move into or out-of an aggregated Ethernet while physical interface drops excess traffic. PR1613889

Authentication and Access Control

  • Root password might not be accepted under su on the Junos OS Evolved platforms. PR1607861

Class of Service (CoS)

  • The user-defined CoS might not get applied on the interface when you configure class-of-service stanza with interface all. PR1592900

EVPN

  • Sometimes the BUM traffic coming through EVPN MPLS tunnel gets dropped or duplicated when going out of the aggregated Ethernet interface after tunnel termination when the aggregated Ethernet members are spanned across multiple Packet Forwarding Engines. PR1578314

  • On PTX10004 platforms, the EVPN option is missing under routing-instances protocols. PR1581821

Infrastructure

  • The default-address-selection statement might not work on all the Junos OS Evolved platforms. PR1570552

  • The FTP IPv6 server function might fail on all the Junos OS Evolved platforms. PR1591733

  • The detail and the write-file options for the monitor traffic interface CLI command are incompatible with each other when used simultaneously. PR1596188

  • Malformed packets might be sent out on egress interfaces in Junos OS Evolved platforms. PR1603783

Interfaces and Chassis

  • The resiliencyd.re.re0 core files are seen on executing cminfra scripts. PR1578822

  • The Junos Telemetry Interface optics sensor's alarm data type changed from bool_val to str_val. PR1580113

  • On PTX10008 platforms, ifmand core files are seen on configuring master-only on the non-duplicate address. PR1583681

  • When changing the micro BFD session address from IPv4 to IPv6 or vice versa, the BFD session and aggregated Ethernet interface go down. PR1584853

  • The SIB might be stuck at an offlining state after performing offline and online operations. PR1591076

  • Some interface unit descriptions are missing from the output of the show interfaces description command on certain PTX Series platforms. PR1591340

  • The 25G interfaces with FEC91 go down on a few configurations. PR1594740

  • On PTX10003-160C platforms, interface is not programmed in routing-instance. PR1596768

  • On PTX10003 platforms, the show platform object-info anomalies summary CLI command times out. PR1598337

  • The LACP system priority might take a value of 0 and causes an LACP interoperability issue. PR1602724

  • A few links on channelized interface is down after oir_enable and oir_disable in 4X25G. PR1606644

Juniper Extension Toolkit (JET)

  • The gRPC connection stuck on ESTABLISHED state with no active collector. PR1592542

MPLS

  • MBB is not triggered when LSP reverts back to the primary path. PR1587704

Network Management and Monitoring

  • The SNMP query timeout failure might be observed on the Junos OS Evolved platforms. PR1585409

  • The syslog archival transfer might fail if the archive site URL is configured with an IPv6 address. PR1603342

Routing Policy and Firewall Filters

  • The dfwd-junos-relay core file is generated during switchover. PR1597853

  • The dfwd crashes when the no-decrement-ttl filter match condition and action is sent from control plane to the Packet Forwarding Engine. PR1602645

  • The firewalld might crash if you configure fragment-offset out of the range (fragment-offset range: 1-900000000000). PR1605805

Routing Protocols

  • Traffic might be misroute or dropped after the Packet Forwarded Engine restarts or interface flaps. PR1581845

  • On a rare occasion, the rpd process generates a core file on the backup Routing Engine after loading a new image. PR1583630

  • Origin validation replication status shows up in the show task replication command output even when it is not configured. PR1583692

  • The rpd process might crash when the BGP RPKI session record-lifetime is configured less than the hold time. PR1585321

  • The rpd process might crash in a BGP multipath scenario if the interface for a single hop EBGP peer goes down. PR1589141

  • PIM joins might not be synchronized between the primary and backup Routing Engines because of ppmd restart. PR1591685

  • When you enable or disable BGP in a short time interval on a scaled NSR, the router might result in a backup rpd restart. PR1591717

User Interface and Configuration

  • The following error is seen: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory. PR1549479

  • The no-persist-groups-inheritance configration is not supported. PR1575995

  • System logs are not updated when a new user gets added or an old user is deleted after commit. PR1589858

  • Post request system zeroize operation, the sshd service is not enabled by default due to a race condition on PTX10008 platforms. PR1594258

  • The file copy command does not accept HTTPS URls. PR1596881

  • The transfer-on-commit configuration does not commit if you commit through NETCONF. PR1602331

  • The request pfe execute command usage too frequently might cause cmdd to crash. PR1610829