Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Network Management and Monitoring

  • Support for SRv6 traceroute (MX240, MX480, MX960, MX2008, MX10003, MX10008, and vMX)—Starting in Junos OS Release 22.3R1, we support the traceroute mechanism for Segment Routing for IPv6 (SRv6) segment identifiers. You can use traceroute for both UDP and ICMP probes. By default, traceroute uses UDP probe. For ICMP-probe, use the traceroute command with probe-icmp option.

    [See .]How to Enable SRv6 Network Programming in IS-IS Networks

  • HMC fatal error SNMP trap (QFX10002-36Q, QFX10002-60C, QFX10002-72Q, QFX10008, QFX10016, PTX1000, PTX10002-60C, PTX10008, and PTX10016)—Starting in Junos OS Release 22.3R1, the listed devices send SNMP trap messages from the SNMP agent to the SNMP manager whenever a Hybrid Memory Cube (HMC) fatal error occurs and gets cleared.

    We've added the following traps to detect the HMC fatal errors:

    • jnxASICExternalMemTraps and jnxASICExternalMemOKTraps at the jnxTraps hierarchy level. The jnxASICExternalMemTraps and jnxASICExternalMemOKTraps traps get triggered when there is an ASIC external memory error.

    • jnxHmcFatal at the jnxASICExternalMemTraps hierarchy. The jnxHmcFatal trap triggers when it detects that the specified HMC on a specific FPC has failed.

    • jnxHmcOK at the jnxASICExternalMemOKTraps hierarchy level. The jnxHmcOK trap triggers when the specified HMC on a specific FPC has recovered from the failure.

    The HMC SNMP traps are raised for fatal HMC errors only. The jnxHmcOK trap is triggered only once for each FPC, although several fatal HMC errors are triggered and then cleared.

    [See SNMP MIBs and Traps Supported by Junos OS.]

  • IPv6 and IPv4 multicast and unicast traffic statistics (MX240, MX480, MX960, MX2010, MX2020, MX10003, MX10008, and MX10016)

    —Starting in Junos OS Release 22.3R1, we support input and output packets, bytes counters, and rate counters for IPv6 and IPv4 multicast and unicast traffic. This feature helps enhance the traffic statistics collection process. To enable this feature, use detailed-transit-interface-stats enable at the [edit accounting-options] hierarchy level. Use show interfaces ge-1/2/9.0 extensive to display the Layer 3 transit statistics.

    [See show interfaces extensive and accounting-options.]