Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Network Management and Monitoring

  • Ephemeral database default commit synchronize model changed to synchronous (PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, and PTX10016)—We've changed the default commit synchronize model for the ephemeral database from the asynchronous model to the synchronous model. The synchronous model ensures better synchronization of ephemeral configurations across Routing Engines or Virtual Chassis members by processing commits synchronously. With this change, only the synchronous model supports synchronizing ephemeral data on devices that have graceful Routing Engine switchover (GRES) or nonstop active routing (NSR) enabled.

    [See Understanding Ephemeral Database Commit Synchronize Models.]

  • Proactive resource monitoring and alarms for data plane stability (PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, and PTX10016)—The Resource Monitoring Infrastructure on Junos OS devices enables proactive and continuous monitoring of critical hardware resources, including Chash, Jencap, Counters, Firewall, and Datapath components. Threshold limits in platform settings ensure real-time detection of abnormal usage without relying on external telemetry collectors. If resource utilization exceeds configured thresholds, the system generates syslog messages, raise alarms through the CMerror module, and forwards events to platform daemons. This infrastructure stabilizes the data plane and reduces traffic loss.

    To view CMerror information, use the show system errors active command.

    [See show system errors active.]

  • Ingress and egress sFlow support for L2 traffic (PTX10002-36QDD)—Use sFlow to monitor ingress or egress data and control traffic forwarded through L2 logical interfaces associated with a bridge domain (BD). This feature supports both enterprise and service provider style L2 configurations.

    [See sFlow Technology Overview.]

  • AES-256 Encryption Algorithm Support for SNMPv3 (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, ACX7024X, PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5700, QFX5700E, QFX5220, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—You can configure Advanced Encryption Standard (AES) 256 algorithm for an SNMPv3 user. To configure AES-256 algorithms for an SNMPv3 user, include the privacy-aes256 statement at the edit snmp v3 usm local-engine user username hierarchy level. AES-256 is a symmetric encryption algorithm that uses a 256-bit key to encrypt or decrypt messages and provides high-level security for protecting sensitive information.

    [See Configure SNMPv3 Authentication Type and Encryption Type, show snmp v3, and usm.]