Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

High Availability

  • Multihop BFD support in inline mode (MX304, MX10003, MX10004, MX10008, and MX10016)—Starting in Junos OS Release 23.4R1, multihop BFD sessions will operate using inline mode by default instead of distributed mode. Inline mode allows for a higher number of programmable RPD (PRPD) programmed multihop BFD sessions. We support multihop sessions only in inline mode when you configure enhanced IP mode.

    You can globally disable multihop BFD using inline mode with the set protocols bfd mhop-inline-disable configuration statement.

    To disable multihop BFD using inline mode on a per BFD session basis, use the set protocols bgp group group bfd-liveness-detection inline-disable configuration statement.

    [See Understanding How BFD Detects Network Failures.]

  • BFD Session Dampening for LACP Interfaces (MX240, MX480, MX960, MX10003)—Starting in Junos OS Release 23.4R1, you can use BFD session damping on LACP interfaces to suppress BFD session state change notifications for a configured time period when thresholds for session flapping are exceeded. Session damping helps reduce potential instability from excessive BFD notifications.

    Use the set bfd-liveness-detection damping configuration statement at the [edit dynamic-profiles name interfaces name aggregated-ether-option] hierarchy level to configure BFD session damping.

    [See BFD Session Damping Overview.]

  • Support for running unified ISSU on MPC10 line cards on MX240, MX480, and MX960 routers—Starting in Junos OS Release 23.4R1, we support in-service software upgrade (ISSU) for subscriber services functionality on MPC10 line cards on MX240, MX480, and MX960.

    [See request system software in-service-upgrade and Unified ISSU System Requirements]

  • Configure BFD size to support large packets on AFT-enabled devices (MX304, MX10003, MX10004, MX10008, MX10016, MX2010, and MX2020)—Starting in Junos OS Release 23.4R1, on AFT-enabled devices, you can adjust the size of the BFD protocol data units (PDUs) with the pdu-size configuration statement at the [edit protocols ospf area area interface interface bfd-liveness-detection] hierarchy level. You can configure the BFD PDU size from the default of 24 bytes up to a maximum of 9000 bytes.

    [See Understanding How BFD Detects Network Failures.]