Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Evolved Release Notes for PTX10003 Devices

 

These release notes accompany Junos OS Evolved Release 19.1R2 for PTX10003 devices. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

What’s New

Learn about new features introduced or changed features in the main release and maintenance releases of Junos OS Evolved for PTX10003 devices.

What’s New in Junos OS Evolved Release 19.1R2

Software Installation and Upgrade

  • Component-level upgrade available—The upgrade command provides for restarting applications and nodes in an optimal manner. You use one upgrade command, request system software add, and by default, the upgrade process identifies upgrades only those components that differ in the target release. An option to the upgrade command allows you to perform the equivalent of a cold boot upgrade should it be required. Output specifies whether the software is upgraded using cold boot or by application restart.

What’s New in Junos OS Evolved Release 19.1R1

Authentication, Authorization, and Accounting

  • RADIUS and TACPLUS functionality over IPv6 enabled—RADIUS and TACPLUS over IPv6 functionality is added for the authentication, authorization, and accounting (AAA) system. Additionally, RADIUS and TACPLUS servers are reachable over Packet Forwarding Engine interfaces.

    [See RADIUS Authentication and TACACS+ Authentication.]

Class of Service

General Routing

  • Stateless DHCPv4 and DHCPv6 Relay can be configured to receive packets on a per-interface basis—Stateless Dynamic Host Control Protocol (DHCP) means the feature does not maintain state or records of lease times and bindings. Broadband Edge Subscriber management and subscriber services such as AAA are not supported.

    [See DHCP Relay Proxy Overview.]

Hardware

  • PTX10003-80C and PTX10003-160C Fixed Packet Transport Routers—Junos OS Evolved Release 19.1R1 introduces two fixed-configuration core routers in a compact, 3 U form factor that is easy to deploy in space-constrained Internet exchange locations, remote central offices, and embedded peering points throughout the network, including cloud-hosted services. The PTX10003 builds upon Juniper Networks ExpressPlus™ silicon concepts of low consistent latency and wire-rate packet performance for both IP traffic and MPLS transport, without sacrificing the optimized system power profile. The PTX10003 uniquely addresses power-constrained environments by providing unprecedented power efficiency of 0.2 watts/Gbps. Two models with differing capacities are available. The PTX10003-160C supports 16 Tbps throughput and the PTX10003-80C supports 8 Tbps throughput—each in a compact 3 U footprint.

  • Chassis management support—Using the chassis management software, you can manage and control field replaceable units (FRUs), monitor system health, set chassis alarms, and handle system faults. However, taking an FPC online by using the request chassis fpc slot-number online command is not supported.

    [See Chassis-Level User Guide.]

  • Fabric management support (PTX10003-160C and PTX10003-80C)—Each of these devices supports two Fabric Chips. The PTX10003-160C devices have 32 Packet Forwarding Engines each, while the PTX10003-80C devices have 16 Packet Forwarding Engines each. The fabric supports a link speed of 53.125 Gbps. Both Fabric Chips are always present. The devices support fabric degradation and blackholing detection. The devices do not support fabric redundancy and fabric fault handling per plane. However, fault handling is supported per link error.

    [See Fabric Plane Management.]

  • Power budgeting and management support—The PTX10003-80C devices support two power supply modules (PSMs) each and provide 1+1 redundancy. The PTX10003-160C devices support four PSMs each and provide 2+2 redundancy. Configuration of ambient temperature (25°C and 40°C) and dynamic power management is supported. However, configuration of the ambient temperature value 55°C is not supported.

    [See Managing Power.]

  • Resiliency support (PTX10003-80C and PTX10003-160C)—Each of these devices support platform resiliency. All error conditions are detected and logged. Wherever applicable, alarms are reported, traps are generated, and FRU level actions like reset, offline, or disable are performed.

Interfaces and Chassis

  • Support for 10-Gbps, 40-Gbps, 100-Gbps channelization using QSFP+/QSFP28/QSFP28 DD Optics (PTX10003)—These platforms support the following optics:

    • QSFP+ optics support 4x10 Gbps or 1x40 Gbps

    • QSFP28 optics support 1x100 Gbps

    • QSFP28-DD optics support 2x100 Gbps

    Each optical port can have a configured port speed. Using the appropriate optics, you can channelize the speed of the ports to 10-Gbps, 40-Gbps, or 100-Gbps speeds. If no port speed is configured on a valid optical port, a default port speed of 2x100G is used. Speed can be configured at the PIC or port level. At the port level, channelize the ports by using the number-of-subports configuration statement.

    [See Channelizing Interfaces on PTX10003 Routers]

  • Interfaces and chassis features supported:

    • Digital optical monitoring (DOM)

    • Forwarding features supported on the Packet Forwarding Engine:

      • Forwarding IPv4 and IPv6

      • Firewall filters

      • Load balancing

      • MPLS fast reroute

      • Forwarding IPv6 transit statistics

      • Host path egress peer engineering

      • IPv6 traffic can transport over IPv4 MPLS core network

      [See the BGP User Guide.]

    • J-Insight Device Monitoring feature support (only the fault monitoring functionality is supported in Junos OS Evolved)

    • Management Ethernet interface (re0:mgmt-0) is confined in a non-default virtual routing and forwarding table—Management Interface in a Nondefault Instance

    • Unicast reverse-path-forwarding (RPF) (supported for the IPv4 and IPv6 protocol families, as well as for the virtual private network [VPN] address family)

Junos Telemetry for Interfaces

  • Junos Telemetry Interface (JTI) support—OpenConfig support through gRPC and JTI is available for the following telemetry sensors that were previously only supported in Junos OS:

    • Sensor for Routing Engine internal interfaces (physical interface state and statistics)

    • Sensor for Routing Engine internal Logical interfaces (logical interface state and statistics)

    • Sensors for ARP

    • Sensor for Network Discovery Protocol (NDP)

    • Sensor for operational state of AE with LACP

    • Sensor for operational state of LLDP (neighbors information)

    To provision the sensor to export data through gRPC streaming, use the telemetry Subscribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig and Network Agent packages, both of which are bundled into the Junos OS image in a default package named junos-openconfig.

    [See Configuring a Junos Telemetry Interface Sensor (CLI Procedure).]

  • Fewer external packages—Network Agent (NA) and OpenConfig (OC) packages are provided as part of the Junos OS Evolved image.

  • Packet Forwarding Engine sensors are supported through Junos Telemetry Interface (JTI)—Use the following resource paths to export statistics to an outside collector through gRPC streaming:

    • /interfaces/interface/

    • /interfaces/interface/subinterfaces/

    • /interfaces/interface[name='interface-name']/subinterfaces/

    • /junos/system/linecard/packet/usage/

    • /junos/system/linecard/firewall/

    • /junos/services/label-switched-path/usage/

    From Junos OS Evolved, you must also include the sensor-based-stats statement at the [edit protoclos mpls] hierarchy level to enable sensor-based statistics collection for the MPLS protocol. As was standard for Junos OS, Network Agent (NA) and OC packages are part of the Junos OS Evolved image. Both packages are necessary to support this feature.

Management

Network Management and Monitoring

Routing Protocols

  • Support for 128-way ECMP for MPLS transit case—Equal-cost multi-path routing (ECMP) is a supported routing strategy. The following features do not support 128-way ECMP: multicast, P2MP, MC-LAG, weighted unilist, consistent hashing, link protection (MPLS), adaptive load balancing, and class-based forwarding.

    [See Example: Load Balancing BGP Traffic.]

Security

  • Secure Boot—A significant system security enhancement, Secure Boot, has been introduced in this release of Junos OS Evolved. The Secure Boot implementation is based on the UEFI 2.4 standard. The BIOS has been hardened and serves as a core root of trust. The BIOS updates, the bootloader, and the kernel are cryptographically protected and thus safeguarded from tampering or modification. Secure boot is enabled by default on supported platforms.

    [See Junos OS Overview.]

Software Installation and Upgrade

  • Zero touch provisioning (ZTP) support—ZTP can dramatically reduce the time to provision the network in a data center and decrease the opportunity for introduction of human error into the network. The image and configuration files are placed centrally in a network server. The device is shipped with factory default configuration along with ZTP configuration. Upon booting up, the device downloads the image from the central location, upgrades itself and, upon rebooting, applies the configuration which it fetched from the network server.

    [See Zero Touch Provisioning.]

  • Root password recovery supported—You can reset the root password without doing a reset-to-factory. Through this procedure, only the root password is reset to a known value; all the other functions and state of the device remain unaffected. In a fixed form server, this operation is performed on the serial console of the primary control node.

    [See Recovering the Root Password for Junos OS Evolved.]

  • Snapshot feature is supported—The snapshot feature copies the current running version and its state at the time of the snapshot to a secondary boot device. If the primary boot device fails, you can use the snapshot to boot the system or recover it without the need for an onsite visit. To have a snapshot, you must run the request system snapshot CLI command—it is not automatic. The show system snapshot command shows the snapshot device information and the software versions installed on snapshot device.

System Management

  • Run your own applications in LXC or Docker containers—In Junos OS Evolved, you can run your applications natively or install and run your own applications inside containers. You can run third-party applications in two types of containers: LXC containers and Docker containers.

    [See Running Third-Party Applications in Containers.]

What’s Changed

Learn about what’s different in behavior and syntax in Junos OS Evolved for PTX10003 devices.

Changes in CLI Statements and Commands

  • To see the list of CLI statements and commands changed in Junos OS Evolved, see How Junos OS Evolved Differs from Junos OS in the Introducing Junos Os Evolved Guide.

Authentication, Authorization, and Accounting

  • Passwordless login required for remote connection—Interactive passwords are not supported. For remote connection without authentication issues, you must configure a passwordless login.

General Routing

  • On PTX10003-80C and PTX10003-160C devices, Native Command Queuing (NCQ) is not disabled for SSDs by default. NCQ allows hard disk drives to internally optimize the order in which the read and write commands are executed.

  • The process eventd will not throw any warning message if there are duplicate policies. For example, if event-script and user-configured event policies from the CLI have the same name, eventd accepts the policy on a first-come, first-served basis.

  • The v6 hash-key field is not enabled as default. To enable it, issue the following CLI configuration command: set forwarding-options hash-key family inet6 layer-3. This is different behavior from behavior in Junos OS, in which the v6 hash-key is enabled by default.

Installation and Upgrade

  • TPM upgrade is not supported in this release of Junos OS Evolved.

Interfaces and Chassis

  • On the PTX10003-80C and PTX10003-160C devices, deleting the FPC power off configuration during run time might trigger the FPC to go online and that might result in a system crash. This is because these routers do not support taking FPC online (using the command request chassis fpc slot-number online). We recommend that you delete the power-off configuration when you are ready to reboot the router (that is, delete the configuration just before rebooting the router).

  • On PTX10003-80C and PTX10003-160C devices, the show chassis fpc command does not show any CPU or memory utililzation information because the PTX10003-80C device is a fixed-configuration router and the FPCs in it do not have dedicated CPUs.

Network Management and Monitoring

  • In Junos OS Evolved, snmpd runs as a 64-bit application. When a value of 4294967295678 is passed to counter32, the value returned is read from the lower order 4 bytes, which is 4294966974 (or 4294967295678 and FFFFFFFF).

  • Whereas Junos OS products display a kernel message on console when a USB device is plugged in or unplugged, Junos OS Evolved products do not print this message on the console. The logs can be seen in either the log files or the list of plugged-in USB devices that can be seen by invoking lsusb or lsblk from the shell.

Routing Policies and Firewall Filters

  • Separate filters for management and control traffic—In Junos OS Evolved, you can have two different filters: one for network control traffic (loopback traffic) and one for management traffic. With two filters, you have more flexibility. For example, you can configure a stricter filter on management interface traffic than on network control traffic. Management filtering uses Routing Engine filters based on netfilters, a framework provided by the Linux kernel. This difference results in only certain matches and actions being supported.

    [See Stateless Firewall Filter Overview.]

  • Output filter binding on RtTable is not supported.

Routing Protocols

  • BGP flowspec filters not listed—In Junos OS Evolved, the show firewall terse command only CLI-based firewall filters are listed, not BGP flowspec filters. In Junos OS, both are listed.

System Management

  • For Junos OS Evolved, a core during early bootup is stored in /var/core/re. But a core later in the bootup, for example, after the Routing Engine slot number can be determined, is stored in /var/core/re0 or /var/core/re1. The command show system core-dumps continues to show all cores generated. The location of the core would also be printed in the CLI command output. For Junos OS, all cores are stored at /var/core/re.

User Interface and Configuration

  • FPC, PIC, or SIB commands changed:

    • Taking a FPC, PIC, or SIB online by using the request chassis fpc slot-number online command is not supported.

    • The following CLI command and configuration options have been deprecated:

      • show chassis network-services

      • [edit chassis fpc slot error (fatal | major |minor) action offline-pic]

  • The set option is deprecated in add and delete commands—Starting in Junos OS Evolved Release 19.1R1, the set option is deprecated in both the request system software add and request system software delete commands.

    [See request system software add and request system software delete.]

  • The source-fpc option is deprecated for the show interfaces voq command—For platforms released starting in Junos OS Evolved Release 19.1R1 (PTX10003), there are only logical FPCs. Therefore, the source-fpc option is not required for this show interfaces voq command.

    [See show interfaces voq.]

  • The show system uptime output changed—The output of the show system uptime displays only the System booted and System-wide users information. The output does not display the details such as current time, system booted, protocols started, or last configured parameters.

    [See show system uptime.]

Known Behavior

Learn about known behavior in Junos OS Evolved for PTX10003 devices.

Authentication and Access Control

  • Here template user authorization paramaters are being tests, this functionality is not currently supported. Support for template user authorization is planned as part of RLI-38945 PR1415949

General Routing

  • PTX10003: Fabric stats PFE stats counter is always displayed as zero. No value is populated. PR1389157

  • Platform system reboot design includes different behavior from Junos OS:

    1. System will always boot from a sticky boot device upon reboot (thais, it reboots from the previous successful boot device). The exception to this is that once system has booted up from USB or netboot and the scratch install is successful, the system should boot from the newly scratch-installed disk1 (primary ssd).

    2. If the previous boot device selected did not boot up successfully, the BIOS will cycle through the boot device list as per the order.

    3. After a USB device is hot-plugged in, if you want to boot from the USB, you need to use the request system shurdown reboot usb command or else reboot and select the USB from the BIOS menu.

    4. A power cycle will reset the boot order to the default list which starts from the primary disk (disk1).

    PR1389196

  • Even though the CLI allows an MTU configuration of 9500, the maximum MTU in the forwarding path is restricted to 9416 bytes (including the 4-byte CRC) PR1412018

  • Due to hardware limitation, IFL stats will be displayed only for parent IFL and not for child IFLs. PR1412245

  • In its current form the evo-cda-zx process can consume a relative high amount (more than rpd) cpu in idle state. This is related to period statistics gathering. PR1412651

  • PTX10003-80C/160C: ~0.4% drops are seen at line rate when packet sizes are below 170b PR1415012

  • Customer TPID 0x88a8/0x9100 is not supporting with 19.1R1. PR1415390

  • The "show interfaces extensive" command displays twice the actual packet count under IFL statistics output for traffic destined to the local interfaces on the switch. PR1415487

  • Old severity error statistics for an URI getting updated under new severity, after changing the severity. PR1417191

  • In SR configuration, the nexthop is leaked. On an EVO system, this prohibits the deletion of the IFL,IFD objects from completing. When the interface is deactivated in configuration, its possible that same ifl/ifd index is assigned, because the earlier IFL/IFD objects are not cleared aft-mand assert reason ifl/ifd index exist. PR1418407

  • During frequent route updates or link flaps, the system may not achieve the full scale of 4K ECMP next-hops. PR1419943

  • show interfaces to view traffic statistics doesn't show any traffic statistics for ipv6 PR1421685

  • Restart of certain processes like CDA, AFTMAN, resilD will cause the system to reboot. PR1421993

  • Available Firmware version for all non supported firmware upgrade components will be shown as 0 in system firmware output. Firmware components not supported are TMC FPGA and CPLD components. Also there are redundant values shown under CHASSIS and RE for all the firmware components. PR1422023

  • Host loopback wedge and alarm will be reported, when offline the fpc. PR1422091

  • Restarting ifstats application may cause the hwdre process to restart. PR1426687

Infrastructure

  • FTP cannot be used if accessing the network through WAN interface. PR1407787

Interfaces and Chassis

  • LACP link protection is not supported. If one of the AE links goes down, the AE interface goes down.

  • Setting or removing vlan-tagging on an interface can cause the physical interface to flap. A link flag during this event is not harmful.

  • Output MPLS filters are not supported due to product limitation.

User Interface and Configuration

  • Corner case which has a workaround when hit. As the system will not be clogged with stale users, but merely the messages coming when user enters configure mode will not have any functional impact on the system. The issue will not be seen with the case of graceful reboot or a clean exit. Command "request system logout user regress terminal pts/0 " can be used to remove the stale user as a workaround. PR1409851

  • For large yang file, augmentation may not work PR1416972

  • On doing load override base.conf, management instance is being deleted. When committing this, commit hangs indefinitely. This happens because of VRF switch. It is expected behaviour. PR1421947

  • Junos OS Evolved is not checking invalid configure when commit: "set interfaces ae0 gigether-options 802.3ad ae0" will be commit without error message. Which will be failed to commit in JUNOS. This may cause ifmand core. PR1426018

Open Issues

Learn about open issues in Junos OS Evolved for PTX10003 devices.

Flow-based and Packet-based Processing

  • JFLOW is not supported on the PTX10003. If you configure it the system may generate EvoAftMan-main and/or rpd-agent cores PR1393101

General Routing

  • Observing mgd unable to execute /usr/sbin/mtree for the cli show system audit. PR1420984

  • ICMP mib table is not implemented in Junos OS Evolved and as such SNMP walk/get on this table will not yield any values. PR1378659

  • Packets sent with incorrect IPV6 hop-by-hop type is not dropped. Same issue with IPv4. PR1403686

  • Linkscan status reflects correctly and Interface state gets updated accordingly, but the RxLOS alarm gets set sometimes randomly even after link goes down. Reached out to HW team and working on the root cause. This issue may not get fixed in 19.1R1 timelines. PR1404144

  • When multiple BGP session flaps happen in the system, the memory used for evo-aftmand process is seen to increase gradually and this memory is not released back to the system once the flaps stop happening. PR1409261

  • The messages 'Em: root: route entry del failed, route does not exist prefix:0.0.0/24' and 'Em: root: route entry del failed, route does not exist prefix:0.0.32/24' will be seen after reverting to a baseline configuration. No action needs to be taken, the delete fails because the routes were never installed. This does not cause any issues. PR1414028

  • PTX10003-80C, and PTX10003-160C: fabspoked-pfe app is leaking 0.1% of memory after 70 iterations of both sib offline / online PR1418123

  • evo-cda-zx errors are observed when FPCs are offline: Trigger: user@router> request chassis fpc slot 0 offline Fpc 0 offline initiated! user@router> request chassis fpc slot 1 offline Fpc 1 offline initiated! Result: user@router> show log messages evo-cda-zx[8679]: %USER-3: [Error] CDA :zxchip_dlu_cache_enable(10699): PECHIP[24]: Bad zxchip (nil) or zxchip not initialized! evo-cda-zx[8679]: %USER-3: [Error] CDA: Error flusing/disable bloom filter cache pfeInst:24 status:22 evo-cda-zx[8679]: %USER-3: [Error] CDA :zxchip_dlu_lpm_flush(10749): PECHIP[24]: Bad zxchip (nil) or zxchip not initialized! evo-cda-zx[8679]: %USER-3: [Error] CDA: Error: lpm flush pfeInst:24 status:22 evo-cda-zx[8679]: %USER-3: [Error] CDA: Error write to hash table pfeInst:24 status:22 PR1418294

  • Sometimes "Socket error on client client-1-NA_periodic_subscriber, disconnecting" messages is not seen when sensor is unsubscribed using CTRL+C. Observed that in the log messages, when sensor is unsubscribed using CTRL+C then "Socket error on client client-xx-NA_periodic_subscriber, disconnecting" should come but sometime message is not seen but sensor gets deleted from the system and issue is specific to log messages. PR1419223

  • At the time fpc offline, while offlining is in progress if due to some reason hwdre restarts, picd core is observed. Possibility of seeing this is very remote. PR1419535

  • Following sensor values are not published in current Junos OS Evolved release, /junos/system/linecards/optics and few of the sensor values of /junos/system/linecards/interfaces In errors In discards Out errors Out discards In unicast pkts Out unicast pkts In broadcast pkts Out broadcast pkts In multicast pkts Out multicast pkts In pause pkts Out pause pkts PR1419811

  • CM infra: Reset action programming need to be blocked for Minor error severity. However reset action is not supported, since the fpc does not support restart/reset. PR1420654

  • When the export port flap happens due to pic going offline and there is a collector already connected, then JSD doesn't detect the change in the connection state and hence it doesn't relay the same info to the infra. Due to this, the installed sensors continue to stream data resulting into piling of recv Q and send-Q for na-grpcd and jsd. The issue resolves once the pic is up again and the new connection state is successfully detected by JSD resulting into unsubscriptions. PR1420963

  • The 'show system audit' command will not be supported in 19.1R1-EVO PR1420984

  • Few field will be missing in CLI "show system statistics arp" like , "Current Public ARP nexthops present " in comparison with junos. PR1422197

  • Five errors belonging to same bucket are contributing to the alarm, with bucket level threshold higher than 1 (threshold=3 in this PR) . On doing clear-all, alarm is not getting cleared. PR1422728

  • irp_intr_smp_trap error messages are seen on PTX10003 console while bouncing the IGP protocols and restart routing daemon. PR1422881

  • In some cases, 100G SR4 optics do not link up intermittently during a reboot of the switch. A soft OIR (interface disable/enable via CLI ) recovers the links from this state. PR1422884

  • PTX10003-160C and PTX10003-80C: COS AE Queue stats for the "show interfaces queue ae0" CLI command is displayed as zero for ~3 mins (where as the rate/pps/bps stats are displayed correctly) after the "clear interfaces statistics all" commands and when one AE member link flaps (24x10G ae0) PR1423134

  • GNMI support is not enabled on PTX10003-80C JTI now, configuring a sensor with GNMI support will result in unexpected behavior. PR1423548

  • When multiple BGP session flaps happen in the system, the memory used for fibd process is seen to increase gradually and this memory is not released back to the system once the flaps stop happening. PR1423625

  • If filter with a term of 1514 is applied on full PFEs then full line rate at PFE level can not be achieved from 168-190 packet type. PR1424351

  • When Highly Accelerated Life Test is carried out on PTX10003 FPC Error messages "pgq_intr_miscintr_qsn_skip" will be seen on the console PR1424539

  • addition of new terms in firewall filter as a secondary match can cause traffic issue. PR1424566

  • Sometimes in the presence of multiple triggers like process restarts a hardware crash with a core dump is observed. The system does recover with no functional impact. PR1425242

  • When Highly Accelerated Life Test is carried out on PTX10003 FPC Error messages "egp_intr_pkt_trapcode" seen on the console PR1425508

  • Sflow collector may not received sflow data with ingress or egress sampling. PR1425949

  • Memory leak seen when doing mpls related config/event/trigger, It does not impact the protocol state or traffic flow. PR1425989

  • On USB plugin while the chassis is Up and running, in PTX10003-80C/PTX10003-160C Chassis, CLI "show chassis hardware detail" shows details USB Disk under Hardware inventory Item only after system reboot. PR1426154

  • When physical links were removed and plugged back in immediately under a sec, there is intermittent chance that link might not be UP. PR1426541

Infrastructure

  • The SSH and telnet server are accessible via the management interface in this release, these servers are not available from the WAN interfaces. PR1310556

  • After swapping management and console cable and reverting back, console LED is not functional and is not coming up. PR1417226

  • In Some scenarios immediately after a software upgrade, hostname in IS-IS database shows up as "localhost". Flapping the IS-IS session will clear this. This problem will not be seen in subsequent reboots after the software upgrade. PR1419006

  • During boot installation ntpd.service is failed to start in the scenario when upgrade is done by selecting boot from GRUB menu PR1421946

  • On Junos OS Evolved software, ISIS adjacency will not come up on GR interfaces. PR1425435

Interfaces and Chassis

Multiprotocol Label Switching (MPLS)

  • In a scale scenario of million routes and thousands of LSPs, "show mpls lsp statistics" will be slow due to high volume of route installation and statistics queries. PR1416363

Routing Protocols

  • The command "show pfe route summary" is not supported PR1405448

  • RP and FHR not supported on PTX10003-80C in this release. PR1414780

  • Hidden BGP routes suppressed by Damping feature continue to hold reference on the route's Nexthop, even though the route is uninstalled from FIB. On an EVO system, this prohibits the deletion of the IFL,IFD objects from completing, when the interface is deactivated in configuration. And EVO does not allow an object to be un-deleted or a new-incarnation to be created until old one is really gone. So even if the interface is re-activated in config, ping does not pass. PR1423122

  • On platforms running Junos OS Evolved, issuing show igmp statistics would terminate the CLI shell PR1426181

Software Installation and Upgrade

  • Route add using BGP APIs can be relatively slow if route monitor register happens when bgp routes are already present in the router. Conditions: BGP route add performance is impacted when BGP route monitor is configured PR1389212

  • If the disk is partitioned with non 'dos' partition type, kindly follow below steps, to erase/format and partition with 'msdos' partition type: ------- parted /dev/sdb mklabel msdos Reboot the box Request system snapshot -------- PR1402409

User Interface and Configuration

  • Junos OS Evolved uses the request system shutdown (reboot | power-off | halt) commands. This is different than the Junos commands for same functionality.

  • If the device's configuration is modified when a Software Upgrade operation is in progress, the upgrade may fail. PR1413386

  • IP is not getting assigned to the interface after delete and add interface PR1424442

  • show system core-dumps | display xml output format is different from classis junos

  • show system directory-usage | display xml has variance in the display from classic junos to evo

Resolved Issues

Open PRs resolved in Junos OS Evolved Release 19.1R2 for PTX10003 devices.

General Routing

  • show route summary in AFT won't show the table names properly. PR1407174

  • Below transient alarm set/clear messages may be seen during the system bootup time. No functional impact. Alarm set message: Alarm set: RE color=red, class=CHASSIS, reason=Host 0 Ethernet Interface Link Down Alarm set: PWRZONE color=red, class=CHASSIS, reason=Zone 0 No Redundant Power Alarm set: PWRZONE color=yellow, class=CHASSIS, reason=Zone 0 N+2 Power redundancy missing Alarm cleared messages: Alarm cleared: RE color=red, class=CHASSIS, reason=Host 0 Ethernet Interface Link Down Alarm cleared: PWRZONE color=red, class=CHASSIS, reason=Zone 0 No Redundant Power Alarm cleared: PWRZONE color=yellow, class=CHASSIS, reason=Zone 0 N+2 Power redundancy missing PR1418111

  • When interface-specific filters are configured with telemetry, template filter information is exported along with individual interface specific filters for each interface filter-bind PR1419359

  • SRTE LSP with more than 3 label is not supported PR1419368

  • When Highly Accelerated Life Test is carried out on PTX10003 Error messages "Nexthop: Failed to traverse af, proto will be null for nh_id XXXX " will be seen for evo-aftmand application on the console PR1424296

  • If traffic is more than 85% and terms applied on PFE traffic is more than 1516 then PFE is not able to carry traffic and it drops to 0%. PR1424344

  • An IPv6 address configured on the management ethernet can get deactivated as the result of an interface flap PR1425160

  • On continuous triggers of Deactivate /Activate Member Links of an AE bundle with SFLOW configured, evo-aftmand core may be observed, leading to a router reboot. PR1425914

  • If the SSH session under which 'monitor interface traffic' is being run is killed, the iftop utility will stay at 100% CPU utilization. PR1426069

  • evo-aftmand core at jprds_encap_desc_add and router went for a reboot after continous triggers of MTU change and rollback PR1426270

  • On SIB Offline, Minor Alarm "SIB <> Not Online" will be generated. In this state, restarting hwdre application and then Onlining the SIB, will not clear the Minor Alarm "SIB <> Not Online" PR1426406

  • sflowd core seen when few interface related operations are performed. PR1426902

  • ZTP file transfer will fail when using an FTP server that requires binary transfer mode to be explicitly defined, such as ProFTP. PR1432727

Infrastructure

  • FPC on PTX10003 might go to fault state, if system is rebooted during broadcast storm on mgmt port. PR1423216

Network Management and Monitoring

  • When snmpd is polled continously, snmpd/mib2d may restart due to memory leak. PR1424034

  • Querying for entPhysicalEntryTable may result in an snmp-subagent crash. PR1425253

Routing Policy and Firewall Filters

  • ASAN reported a global buffer overflow while running firewall unit tests. This issue is fixed and verified. PR1430158

User Interface and Configuration

  • Configd core is observed when scaling prefix list for S/A and DA address. PR1421793