Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Serviceability

  • Automated monitoring of continuous fabric drops (MX240, MX480, MX960, MX2010, and MX2020 routers)—Starting in Junos OS Release 24.2R1, we support automated monitoring of continuous fabric drops on MX240, MX480, MX960, MX2010, and MX2020 routers. The platform adds a syslog entry with fabric queue information and raises one of these minor errors in the chassis management module:
    • CM_CMERROR_FABRIC_LO_PRI_Q_DROP
    • CM_CMERROR_FABRIC_LO_PRI_Q_DROP_ALL
    • CM_CMERROR_FABRIC_HI_PRI_Q_DROP
    • CM_CMERROR_FABRIC_HI_PRI_Q_DROP_ALL

    [See Chassis-Level User Guide.]

  • Changes to the show system firmware command to display the versions for the running, primary, and golden firmware for various components on the FRU (MX10004 and MX10008; LC480, LC2101, LC4800, and LC9600 line cards)—Starting in Junos OS Release 24.2R1, we've enabled new options for the show system firmware command. You can use these options to see firmware version information for only a particular component rather than all of the components. You can also display detailed firmware version information for all of the components on the field-replaceable unit (FRU).

    [See show system firmware.]

  • Datapath trace debug (SRX Series Firewalls)—Starting in Junos OS Release 24.2R1, we’ve enhanced the datapath trace debug. With this enhancement, the flow trace provides:

    • Clear and concise information

    • Packet tracking information

    • Information about missing trace logs

    • Ensure to capture a finite number of initial trace messages

    [See Understanding Data Path Debugging for SRX Series Devices.]

  • IDP signature package improvements (SRX Series Firewalls and vSRX3.0)—Starting in Junos OS Release 24.2R1, we’ve made enhancements to improve the reliability of package updates and validation of update installation. The system automatically rolls back the signature package if the security package installation fails.

    In the case of a multi-SPC/PIC device, when a failure occurs in the data plane after a signature pack is installed, the security package is rolled back once the PICs come back online. This action limits potential damage.

    In a high-availability environment, to prevent failovers from occurring in a loop, the integrity validation is conducted during the primary node installation stage. The system installs the security package on the secondary node only after confirming that the package has no integrity issues.

    [See IDP Signature Database Overview.]

  • Support for automatic Junos volume recovery using OAM (EX Series)—Starting in Junos OS Release 24.2R1, we’ve introduced automatic recovery functionality for the Junos volume. To enable this feature, configure the automatic recovery option under the [edit system snapshot] hierarchy level.

    By enabling the automatic recovery option under [edit system snapshot] hierarchy and having a recovery snapshot available, the device automatically recovers the Junos volume when the device can not load the Junos volume. Junos volume recovery happens automatically from the OAM volume and then boots to the Junos volume.

    This feature simplifies the recovery process and ensures that the device boots to the Junos volume without any manual intervention.

    [See recovery and snapshot.]

  • Support for enhanced request support information (MX204, MX240, MX304, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, and MX2020)—Starting in Junos OS Release 24.2R1, we’ve deprecated the CLI option brief from the request support information command and introduced the following CLI options to the existing request support information command:

    • archive
    • with-logs
    • with-components
    • with-options.

    [See request support information.]