Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Interfaces

  • Support for 400G ZR DWDM optics (MX304)—Starting in Junos OS Release 22.3R1, we support 400G ZR dense wavelength-division multiplexing (DWDM) optics on the MX304 router. When you install the 400G ZR optics, the MX304 supports the following features:

    • Grid spacing of 75 GHz and 100 GHz.

    • Optical loopbacks. To enable optics loopback, use the existing loopback statement at the [edit interfaces optics-options] hierarchy level.

    • One 400GbE and four 100GbE channelization configurations.

    • Performance monitoring and Threshold-Crossing Alarms (TCAs). Use the show interfaces transport pm command to view the current and historical performance-monitoring metrics accumulated into 15-minute and 1-day interval bins . You can thus manage the optical transport link efficiently. TCAs provide the management system an early indication of the deteriorating health of an optical network connection when the performance parameter that you monitor crosses a certain threshold.

    [See optics-options, show chassis hardware, show interfaces, show interfaces diagnostics optics, show chassis pic, and show interfaces transport pm.]

  • Support for IS-IS BFD-enabled sub-TLV (MX2010, MX2020, PTX10000, PTX10008, and PTX10016)—Starting in Junos OS Release 22.3R1, the strict BFD feature allows IS-IS to converge only when BFD is up, and it sends the UP notification to IS-IS. We've introduced a new state in the IS-IS adjacency state machine (InitStrictBFD state) to indicate the agreement between routers to support strict BFD. We've also added a new BFD IS-IS Hello (IIH) PDU TLV in IS-IS hello packets.

    If BFD is unstable, to prevent the traffic from being compromised until the IS-IS adjacency timer expires, configure the hold-down interval (in milliseconds). This configuration delays sending the UP notification to the BFD client. After the BFD is up, the hold-down interval starts, and upon expiration, a BFD UP notification is sent to IS-IS so that IS-IS can start forming an adjacency.

    We've added the following statements for this feature:

    • strict-bfd at the [edit protocols isis interface name level level ] hierarchy level.

    • holddown-interval at the [edit protocols isis interface interface family inet bfd-liveness-detection] hierarchy level.

    [See Configuring BFD, interface (Protocols IS-IS), and bfd-liveness-detection (Protocols IS-IS).]