Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Network Management and Monitoring

  • Clear LLDP neighbors from an interface with the gRPC Network Operations Interface (gNOI) Layer2 service (ACX710, ACX5448, ACX5448-M, ACX5448-D, EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-48MP, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-48T, EX4100-F-24T, EX4100-F-12P, EX4100-F-12T, EX4300-MP, EX4300VC, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, EX4650-48Y-VC, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016, QFX5110, QFX5110-VC, QFX5110-VCF, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, QFX5120-48YM, QFX5200 and QFX5210)—Starting in Junos OS Release 24.2R1, you can execute supported Layer2 service remote procedure calls (RPCs) to perform the equivalent of the clear lldp neighbors interface interface-name command.

    [See gNOI Layer 2 Service.]

  • CFM CCM support on pseudowire and PWHT service interfaces (MX204, MX240, MX304, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, and MX2020)—Starting in Junos OS Release 24.2R1, we support connectivity fault management (CFM) check messages (CCM) on PS service interface for active/active mode (with or without targeting), which is part of EVPN.

    Pseudowire headend termination (PWHT) allows you to connect an L2 circuit from an access node directly to an L3 service at the service node.

    You can configure CCM for down maintenance association end points (MEPs). The CCM MEPs on the PS service interface monitor the Ethernet networks for connectivity faults with continuity check interval of 1 second (1s), 10 seconds (10s), and 100 milliseconds (100ms).

    CFM sessions distributed or anchored to the active Packet Forwarding Engine.

    The feature support includes:

    • Distributed mode and inline mode of transmissions for CCMs.
    • Ethernet link trace (ETH-LT) and loopback (ETH-LB) for CFM sessions.
    • Interface Status TLV and remote defect indication (RDI) for the CCM frames on the PS service interface.
    • CFM Action profile configuration for events such as adjacency-loss, interface-status-tlv, and RDI on the PS service interface to stop transit traffic.

    [See Ethernet OAM Connectivity Fault Management and Pseudowire Headend Termination (PWHT) Configuration.]

  • CFM support on demux interfaces (MX240, MX480, MX960, MX10004, and MX10008)—Starting in Junos OS Release 24.2R1, we support CFM UP MEP on demux VLAN CCC interface with enhanced CFM mode configuration for both local switching and L2 circuit. This feature enables advanced monitoring and fault detection capabilities for customer VLANs connected through demux VLAN ccc interfaces. It allows for the detection and isolation of faults in the network, ensuring reliable and efficient connectivity.

    Additionally, we also support Ethernet link trace and loopback ping on CFM UP MEP on demux interface with enhanced CFM mode. This feature enhances the fault monitoring, fault verification, and fault isolation capabilities of CFM in Ethernet networks.

    [See Configure Connectivity Fault Management (CFM) and Demultiplexing Interface Overview.]

  • 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.]

  • Support for NETCONF Call Home (MX304, MX960, MX2020, MX10004, MX10008, and MX10016)—Starting in Junos OS Release 24.2R1, Junos devices support the NETCONF Call Home feature for establishing a NETCONF session over SSH. NETCONF Call Home enables the Junos device to initiate a secure connection to a NETCONF client. You can use NETCONF Call Home when the NETCONF client cannot initiate a connection with the server. This situation can occur when a firewall or another security tool restricts management access to the server or implements Network Address Translation (NAT). NETCONF Call Home can also streamline the initial deployment of network devices by enabling a device to register with a management system when it is first powered on.

    [See NETCONF Call Home.]

  • Traffic statistic optimization for PRPD Flex Routes (MX304, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, and MX2020)— Starting in Junos OS Release 24.2R1, you can view detailed traffic statistics for PRPD flex routes with the show programmable-rpd statistics command.

    [See show programmable-rpd and show programmable-rpd statistics.]

  • Support for IPv4 transit statistics on pseudowire and PWHT interfaces (MX240, MX304, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, and MX2020)—Starting in Junos OS Release 24.2R1, you can view IPv4 transit statistitcs for pseudowire and PWHT interfaces using the show interfaces ps-interface extensive command.

    [See show interfaces extensive.]

  • Support for 64-bit nanosecond EPOCH timestamp over port-mirrored packets (MX304, MX10008, and MX10016)—Starting in Junos OS Release 24.2R1, you can specify that the software provide a 64-bit nanosecond EPOCH timestamp over a port-mirrored packet for family any packets mirrored in ingress and egress directions.

    You set the timestamping feature by using the packet-timestamp configuration statement at the [edit forwarding-options port-mirroring] hierarchy level.

    The port-mirroring destination can be a next-hop group. In this case, every mirrored packet, for each member members of the group, carries the same timestamp.

    The timestamp on the mirrored packet is extracted during port-mirror post processing, which executes after the mainline packet is processed. Thus there is a microseconds-worth delay since the mainline packet entered or exited on the corresponding interface. Also, an L2 or L3 feature that depends on the MAC address for forwarding of the mirrored packet might not function as expected, because the MAC header fields are overwritten with the timestamp.

    [See Timestamping of Port-Mirrored Packets .]

  • Support for port mirroring for demux logical interfaces in family CCC (MX240, MX480, MX960,MX10004, and MX10008)—Starting in Junos OS Release 24.2R1, you can add a demux configuration on top of an ae (aggregated Ethernet) interface configuration with family ccc in global-based or instance-based port mirroring. This feature allows you to use demux interfaces in your port-mirroring configuration to substantially reduce the number of logical interfaces that are consumed by child physical interfaces under the AE bundle.

    [See Applying Layer 2 Port Mirroring to Family ccc Traffic with Demux Logical Interfaces Over Aggregated Ethernet .]