Alert Type

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

Product Affected

ACX PTX QFX platforms running Junos Evolved software

Alert Description

Junos Software Service Release version 24.4R2-S2-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

NOTE: Starting on August 30th, 2024, we include PR's severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

 

Junos Selective Update (JSU) feasible

Not applicable

Call to Action

For your review.

Solution

Junos Software service Release version 24.4R2-S2-EVO is now available.

24.4R2-S2-EVO - List of Fixed issues

PR NumberSynopsisCategory: Border Gateway Protocol
1887911
Major		The rpd process crashes after BGP configuration commits involving group-split-size and RIB-sharding
Product-Group=evo
Severity=Major		On Junos and Junos OS Evolved platforms, configuring "group-split-size" with BGP RIB-sharding(Border Gateway Protocol Routing Information Base Sharding) can lead to a crash in the routing protocol daemon (rpd) when a route update for a non-negotiated NLRI(Network Layer Reachability Information) is received in the update thread. This occurs if the NLRI is targeted at other BGP peers within the group that have negotiated it.
1907391
Major		Routes are hidden when accept-own feature is enabled with rib-sharding
Product-Group=evo
Severity=Major		On MX480 and MX960 platforms, routes become hidden when the "accept-own" feature is enabled in environments configured with rib-sharding. This issue arises when the "vrf-table-label" is configured within a routing instance and route sharding is enabled, potentially leading to routing failures.
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
1895937
Minor		IPv4 and IPv6 traffic is dropped over VXLAN tunnel on PTX router
Product-Group=evo
Severity=Minor		On Junos OS Evolved PTX platforms, when eBGP (External Border Gateway Protocol) multihop and EVPN-VXLAN (Ethernet Virtual Private Network - Virtual eXtensible Local Area Network) are configured along with the "preserve-nexthop-hierarchy" knob, traffic is being dropped over the VXLAN tunnel due to a failure in the PFE (Packet Forwarding Engine).
PR NumberSynopsisCategory: DNX L2 related features
1855369
Major		Storm Control stops working on all LAG members after deactivating one or more interfaces on Junos OS Evolved ACX7K platforms
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7K platforms, when storm control is configured on a LAG (Link Aggregation Group) interface and one or more LAG member interfaces are deactivated, storm control stops working on all remaining active members. This results in an immediate increase in BUM (Broadcast, Unknown Unicast, and Multicast) traffic on the egress interface.
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1880571
Major		Interfaces are not created after system reboot on Junos OS Evolved ACX platforms
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX platforms, there is a timing issue during system reboot involving the FPC (Flexible PIC Concentrator) and the FruE (Flexible Routing Update Engine) process calls, which causes a deadlock, preventing interfaces from being created after reboot. As a result, interfaces remain down until the Packet Forwarding Engine daemon (evo-pfemand) is manually restarted, after which the interfaces come up normally.
PR NumberSynopsisCategory: ACX LAG infrastructure
1875544
Major		Traffic impact due to shared Broadcom resource among multiple ifd
Product-Group=evo
Severity=Major		On Junos Evolved ACX7K series platforms, repeated configuration changes of LAGs (Link Aggregation Groups) cause overlap in hardware resource allocation of Broadcom (BRCM) leading to traffic impact.
PR NumberSynopsisCategory: DNX VPLS
1896785
Major		Stale ARP details after RE switchover leading to traffic loss observed on ACX7K
Product-Group=evo
Severity=Major		On all Junos OS Evolved ACX7K Platforms, Layer 3 traffic loss can occur after an RE reboot due to a race condition between ARP and VPLS programming.
PR NumberSynopsisCategory: Binding Queue
1885455
Major		application rpd-agent may restart with a coredump after interface related event changes.
Product-Group=evo
Severity=Major		The rpd-agen application may restart either immediately or latently - after interface are activate, deactivated, created, or removed.via.
PR NumberSynopsisCategory: System Management daemon and related issues
1852221
Minor		The l2cpd-agent crashes due to its state cleaned up during shutdown
Product-Group=evo
Severity=Minor		On all Junos Evolved platforms, due to a timing issue, it is observed that the l2cpd agent crashes when the app's state is being cleaned by external garbage collection as app is about to shutdown. But there is no traffic impact due to this issue.
1905807
Minor		System stops responding to "show system applications app ndp detail" command or prevents applications from start/stop/restart
Product-Group=evo
Severity=Minor		On all Junos OS Evolved platforms with release >=24.1R1, a failure in internal process communication will cause the system to stop responding to the "show system applications app ndp detail" CLI command or prevent applications from start/stop/restart. This issue occurs when systemd becomes unresponsive to requests initiated by sysman. There is no impact to traffic forwarding.
PR NumberSynopsisCategory: EVO Services Jflow PRs for defect & enhancement requests
1874737
Minor		[ptx-10008-evo] ingress mpls IPFIX flows have TopLabelAddr V6: ::
Product-Group=evo
Severity=Minor		Root Cause: In this issue, there can be two routes published for the same MPLS label (one each for BOS=0 and BOS=1). So, in JFLOW, it learns both of them as a single route, resulting in overwriting the routes based on the sequence of updates. Fix Details: On route update in the onModify routine, if the route is present, then update the Prefix & fec PrefixLen only if the FEC prefix is not NULL. No workaround is available.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1899530
Major		MAC learning failure when moving the AE interface from one VLAN to another VLAN in a single commit
Product-Group=evo
Severity=Major		On Junos OS Evolved platforms, when an Aggregated Ethernet (AE) logical interface (IFL) is moved from one Virtual LAN (VLAN) to another VLAN in a single commit, Layer 2 forwarding tables fail to update correctly. This causes Media Access Control (MAC) learning failure and traffic disruption.
PR NumberSynopsisCategory: EVO-AFT Infrastructure PFE related issues
1869773
Critical		Applying a Layer2 filter on interface on results in protocol flaps and traffic disruption on other interfaces on the same PFE
Product-Group=evo
Severity=Critical		Applying a Layer2 filter on and interface on Junos OS Evolved PTX platforms results in protocol flaps and traffic disruption on other interfaces on the same PFE. Please refer TSB96988 [juniper.net] for more details.
PR NumberSynopsisCategory: N/A:sw-evo-re-firewall:
1896496
Minor		Traffic drop observed for two policer with same initial name and term names
Product-Group=evo
Severity=Minor		On all Junos OS Evolved platforms, when two policers with the same initial name(First 15 characters of rate estimator name) and term names are configured, since the rate estimator name (combination of filter term name and policer name) which gets truncated to 15 characters, the two policers start using the same rate estimator and it can lead to possible early drops by the policer, based on the current traffic rate of the two policers.
PR NumberSynopsisCategory: Configd, ffp issues
1900883
Major		Traffic loss occurs due to missing apply-path handling during reboot or configd restart
Product-Group=evo
Severity=Major		On platforms running Junos OS Evolved 20.2R1-EVO and later releases, apply-path configurations with wildcards after leaf nodes are not evaluated correctly during reboot or configd restart. This is due to missing special handling required for evaluating such configurations during reboot and configd restart, this causes failure of routing and forwarding functions that rely on apply-paths, leading to traffic loss post reboot or configd restart.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1883530
Critical		FPC crash is seen on certain Junos platforms when firewall filter is configured for subscribers
Product-Group=evo
Severity=Critical		On MX platforms with MPC10E, MPC11E, LC9600 line-cards and MX304 with subscriber-management enabled, Flexible PIC Concentrator (FPC) crashes in a rare scenario and crash files are generated when filters are configured for subscribers . This will lead to traffic impact since the line-card reboots and subscribers are re-logged.
PR NumberSynopsisCategory: ACX7332 & ACX7348 Platform Software
1809091
Minor		ACX7024 sees a vmcore and restarts or potentially hangs on reboot
Product-Group=evo
Severity=Minor		ACX7024 sees a vmcore and restarts or potentially hangs on reboot
PR NumberSynopsisCategory: ACX7509 Linecard (FPC) related issues
1898908
Major		The other port in a port group goes down after an RE switchover if one of the port in the port group is already down on an ACX7509
Product-Group=evo
Severity=Major		On Junos OS Evolved ACX7509 platforms, when one port in a channelized group (like ports 0 in a port group consisting of port 0 and port 1) is already in 'down' state in a ACX7509-FPC-16C with 16x100G-QSFP, performing a Routing Engine (RE) switchover or restarting the picd process can cause the other port in the port group to go down. This will lead to disruption of services running on the port.
PR NumberSynopsisCategory: ACX7509 Platform related issues
1907310
Major		After RE switchover on the device, the capacity of DC PSM is observed to be zero after toggling the input power
Product-Group=evo
Severity=Major		On all Junos OS Evolved platforms, whenever a Routing Engine (RE) switchover occurs and the DC input supply to one of the Power Supply Modules (PSMs) is toggled or flapped, the output capacity of that PSM becomes zero. If the remaining PSMs are unable to provide sufficient power to the chassis, all Flexible PIC Concentrators (FPCs) go offline, resulting in traffic impact.
PR NumberSynopsisCategory: ISIS routing protocol
1906578
Minor		IS-IS FA configuration in IPv4 or IPv6 Multicast topology may cause inconsistency in routing table leading to routing loop
Product-Group=evo
Severity=Minor		On Junos and Junos OS Evolved platforms, when IS-IS IPv4 or IPv6 Multicast topology (set protocols isis topologies [ipv4-multicast | ipv6-multicast]) is configured along with IS-IS Forwarding Adjacency (FA), a separate TLV-222 is added in IS-IS LSP for each FA. This causes incorrect next-hop resolution in the routing table, potentially leading to routing loops.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1889546
Major		MPLS ping/trace not working for direct peers via routing-instance over MPLS protocols
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, when a routing instance is configured at the destination device, an echo request packet is received over this routing instance interface. This routing instance should have a valid route to reach the source device. But the default routing instance should not have a valid route to reach the source device. This issue is not specific to MPLS ping over SR alone. This issue is applicable for all the protocols MPLS ping.
PR NumberSynopsisCategory: Issues related to krt-async routing infrastructure
1866522
Major		VPLS session stays down after interface flaps
Product-Group=evo
Severity=Major		An LSI IFL remains in RPD even after being deleted by the interface manager daemon. It is visible in show interface routing but not in show interfaces, indicating that RPD still holds the IFL despite its removal elsewhere. rpd-agent does not send a delete message to RPD due to a reference count issue. Another daemon?likely l2ald?still holds a reference to the IFL. rpd-agent only sends the delete once all references are cleared, which doesn't happen in this case. The fix is to send a "delete pending" message from rpd-agent to RPD. RPD will treat this as a delete and remove the IFL, ensuring consistency across the system.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1815837
Minor		Configure low file size in traceoptions while logging volume is high will lead to high CPU and RPD scheduler slips causing operational impact
Product-Group=evo
Severity=Minor		If the file size is too small and the amount of traceoptions volume is too high it can cause scheduler slips and operational impact.
PR NumberSynopsisCategory: ACX724 platform issues
1895749
Critical		System crashes due to a CPU glitch
Product-Group=evo
Severity=Critical		On Junos Evolved ACX7024 and ACX7024X platforms, the system crashes and kernel core is generated due to a random CPU error.
PR NumberSynopsisCategory: ACX7000 platform software related issues.
1885345
Minor		Fan Tray X Incompatible alarm was raised when the fan unit was removed
Product-Group=evo
Severity=Minor		On all ACX7100-32C, when the fan unit was removed, the "Fan Tray X Incompatible" alarm was raised upon removal of the fan unit. This issue has no impact on traffic.

 

 

24.4R2-S2-EVO - List of Known issues

PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1896239
Major		Host-bound packet drops when using decapsulate filter action in non-default routing-instances
Product-Group=evo		On all Junos OS Evolved QFX5K platforms, host-bound packets on L3 interfaces associated with non-default routing-instances are consistently dropped when a filter with the decapsulate action is applied sequentially on one interface and then on its counterpart.

Resolved In: evo:23.4R2-S3-J14-EVO evo:23.4R2-S6-EVO evo:25.2R2-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: Express BT PFE L3 Features
1893165
Minor		Micro BFD packets egress through incorrect queue on PTX platforms
Product-Group=evo		On PTX platforms that support inline micro BFD ( Bidirectional Forwarding Detection), the BFD packets are sent through Q3 ( network-control queue) instead of Q5 (protocol queue). This can cause packet drops due to wrong queue selection.

Resolved In: evo:25.4R1-EVO evo:26.1R1-EVO junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: Express BX PFE L3 Features
1901035
Major		IPv6 Tunneling in RSVP LSP's, streams dropped on transit penultimate node
Product-Group=evo		After configuring all the nodes in the network with the explicit null config, the issue is not seen.

Resolved In:
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1908282
Major		Next hop is missing when ECMP uses an IRB interface in an EVPN-VXLAN scenario
Product-Group=evo		On all Junos OS Evolved ACX7K Series platforms, the Next hop is wrongly programed when Equal Cost Multi Path (ECMP) is configured, and IRB (Integrated Routing and Bridging) interface is used as a Next hop. Since the Next hope is not being programed properly, routes are unable to have a next hop causing service disruption.

Resolved In: evo:23.4R2-S6-J3-EVO evo:23.4R2-S7-EVO evo:24.2R2-S4-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO
PR NumberSynopsisCategory: System Management daemon and related issues
1866988
Critical		System stops responding to "show system applications app ndp detail" command or prevents applications from start/stop/restart
Product-Group=evo		On all Junos OS Evolved platforms, a failure in internal process communication will cause the system to stop responding to the "show system applications app ndp detail" CLI command or prevent applications from start/stop/restart. This issue occurs when systemd becomes unresponsive to requests initiated by sysman. There is no impact to traffic forwarding.

Resolved In: evo:23.4R2-S6-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: EVO MACSEC Platform Independent Implementation
1908196
Major		All Marvell(MX, ACX): LLDP protocol goes down when 'exclude protocol LLDP' is deleted from MACsec policy attached to IFD
Product-Group=evo		With IFD MACsec configured with exclude-protocol LLDP and LLDP protocol enabled, LLDP protocol goes down when 'exclude-protocol LLDP' is deleted from MACsec connectivity association.

Resolved In: evo:25.4R1-EVO evo:26.1R1-EVO junos:25.2R2 junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: Paragon Active Assurance
1886928
Major		PAA installation failure on reboot due to "Not found default vrf" error
Product-Group=evo		When a device is rebooted with PAA installed in 25.2R1 , PAA installation on reboot may fail due to "Not found default vrf" error. This can be resolved by deactivating and activating or freshly installing the PAA configuration

Resolved In: evo:25.4R1-EVO junos:25.4R1
PR NumberSynopsisCategory: PRs related to software Agentd daemon on EVO
1783844
Major		ACX7300 evo-pfemand cored at JBcmDispatch:: jsh_process_command during SWtest
Product-Group=evo		ACX7300 platforms are system with dual REs, with a single FEB system. The forwarding asic on the FEB is managed by the master RE. Per design the PFE process needs to run only on the master RE. However because of an know bug in the USB upgrade, the PFE process runs on the backup and since can not access the ASIC it exits with core dump. This does not impact the functionality of the box and can be ignored.

Resolved In: evo:23.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO
PR NumberSynopsisCategory: Express ptx-evo PFE L3 Features
1883158
Major		Issue while connecting boot server with 1st iteration while in 2nd iteration it will go fine.
Product-Group=evo		In JUNOS evolved, ARP resolution requests are throttled on FPC per logical interface level i.e if resolution request on a logical interface expires then a throttle timer is started on that logical interface and no other resolution request could be generated on that logical interface when throttle timer is running. In this issue RE netstack is sending packets to FPC with hint to resolution request for already resolved IP address and triggering throttle timer. So resolution request for second IP address on same logical interface could not be generated for some time which is triggering phone-home application 10 seconds time out.

Resolved In:
PR NumberSynopsisCategory: Express PFE CFM
PR NumberSynopsisCategory: ACX7332 ACX7348 Interfaces software
1870528
Major		Interface down is observed while configuring 1G speed on ACX7332/ACX7348/ACX7509 platforms
Product-Group=evo		On Junos OS Evolved ACX7332/ACX7348/ACX7509 platforms, physical interface goes down on configuring 1G speed after the first boot with or without auto-negotiation.

Resolved In: evo:23.2R2-S4-EVO evo:23.4R2-S2-J15-EVO evo:23.4R2-S5-J15-EVO evo:23.4R2-S6-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO junos:24.4R2 junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: ACX7332 & ACX7348 Platform Software
1894824
Minor		ACX 7348 - Continuous log messages seen on backup routing engine after RE switchover
Product-Group=evo		OnJunos Evolved ACX 7348 platforms, continuous log messages are flooded in the backup routing engine during switchover of routing engine. This does not have any functional impact.

Resolved In: evo:24.2R2-S4-EVO evo:25.4R1-EVO junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: ACX7509 platform, FEB, RCB and linecaard resi
1891967
Major		The fetched firmware version results an incorrect value on ACX7509
Product-Group=evo		On Junos OS Evolved ACX7509 platforms, firmware version mismatch alarm is observed. This occurs in rare scenarios and results in incorrect display issue.

Resolved In: evo:23.2R2-S4-J6-EVO evo:23.2R2-S5-EVO evo:24.2R2-S2-EVO evo:24.4R2-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO
PR NumberSynopsisCategory: ACX7509 Linecard (FPC) related issues
1870204
Major		1G port not getting full bandwidth when ACX7509 device connecting to other vendor platforms
Product-Group=evo		When ACX7509 is used with 1G optics, due to IPG(Inter-Packet-Gap) setting mismatch on Marvell PHY chip, 1G port may corrupt transmitting packets when the rate is close to 1G wire or having micro burst to cause service impact Traffic loss can be seen when connecting to vendor platforms, eg Intel NIC card. ACX7509 sends out packet with tight IGP, and if peer has low tolerance on IGP, they could drop it. Firewall filter or wire capture on can confirm if IPG setting is causing the issue. Please contact JTAC to determine the issue

Resolved In: evo:23.2R2-S1-J10-EVO evo:23.2R2-S4-EVO evo:23.4R2-S2-J15-EVO evo:23.4R2-S5-EVO evo:24.2R2-S1-EVO evo:24.4R2-EVO evo:25.2R1-EVO evo:25.3R1-EVO
PR NumberSynopsisCategory: ACX7509 Platform related issues
PR NumberSynopsisCategory: N/A:sw-hamilton-timing:
1874475
Minor		PTP LAG interface GRES issue
Product-Group=evo		PTP on one particular LAG interface stops working on the ULC - MX10004, MX10008 Line Card - in the below scenarios: - Load override existing LAG+PTP config with some baseline config - Replace baseline config with the previous LAG+PTP config - Perform GRES and then on the new master we see that one of the slave LAG interfaces do not receive PTP packets. Issue is only seen in above scenarios. Other GRES scenarios work correctly wrt PTP

Resolved In: evo:25.2R1-EVO evo:25.3R1-EVO junos:25.2R1 junos:25.3R1
PR NumberSynopsisCategory: SW PRs for MPC10E PlatformD
1909455
Major		RADIUS interim accounting will not work for subscribers after GRES on MX platforms with MPC10 line card
Product-Group=evo		On MX platforms with MPC10, RADIUS (Remote Authentication Dial-In User Service) interim accounting will not be working for subscribers after GRES (Graceful Routing Engine Switchover).

Resolved In: evo:24.2R2-S4-EVO evo:25.2R2-EVO evo:25.4R1-EVO evo:26.1R1-EVO junos:25.2R2 junos:25.4R1 junos:26.1R1
PR NumberSynopsisCategory: MPC11 ULC platform software related issues.
1881499
Minor		On MPC11E linecards, Periodic error messages are logged as "Temp sensor DDR4 A failed"
Product-Group=evo		DDR temp sensor is designed to be used periodically to get temps to send to chassisd. The temp sensors reside may have an intermittent contention that can cause these read failures resulting in DDR4 Temp Sensor Fail" logs on MPC11E linecards.

Resolved In: evo:24.2R2-S2-EVO evo:25.2R1-S1-EVO evo:25.2R2-EVO evo:25.3R1-EVO evo:25.4R1-EVO junos:24.2R2-S1-J6 junos:24.2R2-S2 junos:25.2R1-S1 junos:25.2R2 junos:25.4R1
PR NumberSynopsisCategory: Protocol Independant Multicast
1880262
Major		PIM neighbors timeout on backup RE due to inconsistent state with master
Product-Group=evo		On all Junos and Junos Evolved platforms with dual Routing Engines (REs), Protocol Independent Multicast (PIM) neighborship is not be maintained on the backup Routing Engine after a ppmd-agent restart. This can lead to loss of PIM neighbor state on the backup RE.

Resolved In: evo:23.4R2-S6-EVO evo:24.2R2-S2-EVO evo:25.2R2-EVO evo:25.3R1-EVO junos:22.4R3-S8 junos:23.2R2-S5 junos:23.4R2-S6 junos:24.2R2-S2 junos:25.2R2 junos:25.3R1
PR NumberSynopsisCategory: KRT Queue issues within RPD
1830588
Critical		The rpd process crashes on all Junos and Junos OS Evolved platforms when recursively resolved routes are changed or deleted
Product-Group=evo		On all Junos and Junos OS Evolved platforms when recursively resolved routes are changed or deleted, route churn will potentially lead to the rpd process crash.

Resolved In: evo:22.2R3-S7-EVO evo:22.3X50-EVO evo:22.3X80-D45-EVO evo:22.3X80-D46-EVO evo:23.2R2-S3-EVO evo:23.2R2-S4-EVO evo:23.4R2-S4-EVO evo:23.4R2-S5-EVO evo:24.2R2-EVO evo:24.4R2-S1-J1-EVO evo:25.1R1-EVO junos:22.2R3-S7 junos:22.3X60 junos:23.2R2-S3 junos:23.4R2-S4 junos:24.2R2 junos:24.4R2-S2 junos:25.1R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1881609
Minor		RSVP hello messages uses secondary address when primary/preferred address are present for same interface
Product-Group=evo		On all Junos and Junos OS Evolved platforms where RSVP (Resource Reservation Protocol) configuration is present and a RSVP enabled interface has 2 IP address of which one is configured as primary/preferred in that case the RSVP Hello message uses the secondary IP address to form neighborship.

Resolved In: evo:25.3R1-EVO junos:25.3R1
PR NumberSynopsisCategory: Issues related to control plane security
1860970
Minor		SIB HA wait timeout error upon graceful RE switchover
Product-Group=evo		SSH issue from the Routing Engine to the FPC causes SIB HA timeout error upon RE switchover. All the SIBs will be reset as a result of that.

Resolved In:
PR NumberSynopsisCategory: ACX7000 PTP timing related issues.
PR NumberSynopsisCategory: ZT pfe l3 forwarding issues
1474146
Major		For the MPC10E line card, the IS-IS and micro-BFD sessions do not come up during baseline.
Product-Group=evo		For the MPC10E card line, the IS-IS and micro-BFD sessions do not come up during baseline.

Resolved In:

 

 

Modification History

First publication 2025-12-01