Hardware

• The 10x10GbE SFPP and 10x1GbE SFP MIC supports the MPC2E-NG and MPC3E-NG line cards on the MX240, MX480, MX960, MX2010, and MX2020 routers.This MIC has 10 ports that support 1-Gbps small form-factor pluggable (SFP) and 10-Gbps small form-factor pluggable plus (SFP+) transceivers along with PTP and MACsec capabilities.

  [See pic-mode and number-of-ports.]

• We support a new MIC, MIC-3D-10GbE-SFP-E, for the MPC2E-3D-NG, MPC2E-3D-NG-Q, MPC3E-3DNG, and MPC3E-3D-NG-Q line cards.The MIC has ten 10GbE ports that support SFP and SFP+ transceivers. The ports provide MACsec support.

  [See MICs Supported by MX Series Routers.]

High availability and resiliency

• Support for MIC (MIC-3D-10GbE-SFP-E) resiliency in MX Series devices.

• Support for MIC with 1GbE SFP or 10GbE SFP+ ports along with PTP and MACsec capabilities on the line cards.

  [See Port Speed on MX Routers]

• Supported transceivers, optical interfaces, and DAC cables—Select your product in the Hardware Compatibility Tool to view the supported transceivers, optical interfaces, and direct attach copper (DAC) cables for your platform or interface module. We update the HCT and provide the first supported release information when the optic becomes available.

• Oversubscription and preclassification support for MIC MIC-3D-10GbE-SFP-E on MX Series devices.

  [See Oversubscription.]

MACsec

• Support for Media Access Control Security (MACsec) on physical and virtual interfaces with GCM-AES-128, GCM-AES-256, GCM-AES-XPN-128, and GCM-AES-XPN-256 encryption. Both physical and virtual interfaces support static connectivity association key (CAK) mode. Only physical interfaces support dynamic CAK mode, preshared key (PSK) hitless rollover keychain, and aggregated Ethernet.

  [See Configuring MACsec.]

• Precision Time Protocol with Media Access Control Security encryption (MIC-3D-10GbE-SFP-E) enables the simultaneous support of Precision Time Protocol (PTP) and Media Access Control Security (MACsec) encryption on a single port.

  The following limitations apply:

  • The maximum number of MACsec-enabled logical interfaces (IFL) is 200 per system.

  • The maximum number of MACsec-enabled ports with physical interfaces (IFDs) and IFLs where MACsec and PTP are enabled together on different ports is 200 per system.

  • The maximum number of IFLs that can be supported on both 1G and 10G ports is 128.

  • PTP in clear text mode is not supported.

Timing

• Synchronous Ethernet with G.8262 standard support on MIC-3D-10GbE-SFP-E. We support Synchronous Ethernet with G.8262 in compliance with the following International Telecommunication Union Telecommunication Standardization (ITU-T) standard to facilitate the transference of clock signals over the Ethernet physical layer.

  Synchronous Ethernet (G.8262). Timing and synchronization aspects in packet networks. Specifies timing characteristics of synchronous Ethernet equipment clock (EEC).

  [See Synchronous Ethernet.]

• Precision Time Protocol with G.8275.1 standard support on MIC-3D-10GbE-SFP-E. We support Precision Time Protocol with G.8275.1 in compliance with the following International Telecommunication Union Telecommunication Standardization (ITU-T) standards to facilitate distribution of precise time and frequency over packet-switched Ethernet networks.

  • G.8275.1—PTP profile for phase and time (full timing support)

  • G.8275.1—PTP profile for phase and time over link aggregation group (LAG)

  [See Precision Time Protocol.]

Chassis

Support for the following hardware components, platform features, and fabric functionalities for the new MX10K-LC4800 line card in MX10004 and MX10008 routers:

• Power supply modules (PSMs)— JNP10K-PWR-AC2, JNP10K-PWR-AC3, and JNP10K-PWR-DC2

  Use the chassis ambient-temperature (25C|40C|55C) and chassis pfe <pfe Number> power <on | off> commands for power management.

  [See ambient-temperature, and ambient-temperature.]

• Fan trays—JNP10004-FAN2 and JNP10008-FAN2

• Interoperability with MX10K-LC480, MX10K-LC2101, and MX10K-LC9600 line cards on MX10004 and MX10008 routers.

  [See Fabric Plane Management.]

  If compatible components are not present, SFB2 and the line card continue to remain in offline state and an error message is displayed in the show chassis fpc and show chassis sfb command outputs.

  [Seeshow chassis fpc and show chassis sfb.]

• Fabric plane management—SFB2 with 6 Packet Forwarding Engines per slot and 12 fabric planes, with fabric fault handling and fabric hardening.

  [See Fabric Plane Management.]

• Platform resiliency for the following hardware components:

  • CPU

  • Field replaceable units (FRUs)

  • Memory

  • Management Ethernet ports

  • Field-programmable gate array (FPGA) board

  • Optics panel

  • Power supply module (PSM)

  • Fan tray

    If a failure is detected on a hardware component, Junos OS:

    • Logs the message to give clear indication of failure details, including timestamp, module name, and component name.

    • Raises and clears alarms, if applicable.

    • Makes the LED glow to indicate FRU fault, if an LED is present.

    • Performs local action, such as self-healing and taking the component out of service.

    [See Chassis-Level User Guide.]

• Junos environment monitoring (EM) policy extended to include optics temperature sensors. It includes the following features:

  • The Optics EM policy incorporates periodically polled temperature readings of optical modules in the system to automatically manage the fan speed.

  • 100GbE and 400GbE optics firmware automatically triggers optics shutdown when the high-temperature threshold is breached.

  • EM policy is enabled by default on all 100GbE and 400GbE optics interfaces, except for loopback optics and direct attach copper (DAC) cables.

  You can use the set chassis fpc fpc_slot pic pic_slot port port_no no-temperature-monitoring command to explicitly disable the EM policy on specific WAN ports. Use the show chassis environment command to view the optics temperature.

  [See temperature-sensor.]

CoS

• Support for CoS configuration.

  [See CoS Features and Limitations on MX Series Routers and Hierarchical Class of Service for Subscriber Management Overview.]

• Support for CoS on 1GbE ports.

DHCP

• Support for DHCP functionality (DHCPv4/v6 server, relay, and client feature). [See DHCP Relay Agent.]

Hardware

• New MX10K-LC4800 line card (model number: JNP10K-LC4800) on MX10004 and MX10008—We introduce the MX10K-LC4800. MX10K-LC4800 is a fixed-configuration line card that can deliver a bandwidth of up to 4.8 terabit per second (Tbps). The line card has forty 100 Gbps capable SFP56-DD ports and four 400 Gbps capable QSFP56-DD ports. MX10K-LC4800 interoperates with existing MX Series line cards, such as MX10K-LC9600, MX10K-LC2101, and MX10K-LC480 and interfaces with JNP10004-SF2 (in MX10004) and JNP10008-SF2 (in MX10008) SFBs.

High availability (HA)

• Resiliency support for Packet Forwarding Engine and SFB 2. [Seeshow system errors active.]

Interfaces

• Supports transceivers, optical interfaces, and direct attach copper (DAC) cables on MX10004 and MX 10008.

  [SeeHCT and optics-options.]

• Interface support on MX10K-LC4800 line card (MX10004 and MX10008)—We introduce the MX10K-LC4800. MX10K-LC4800 is a fixed-configuration line card that can deliver a bandwidth of up to 4.8 Tbps. The line card has forty 100 Gbps capable SFP56-DD ports and four 400 Gbps capable QSFP56-DD ports. A PIC port in MX10K-LC4800 can support multiple port speeds.

• BER monitoring and PRBS support.

  [See Verifying Link and Transceivers using Pseudo Random Binary Sequence (PRBS) Test and Configuring BERT Testing.]

Junos telemetry interface (JTI)

• Platform Sensors-Junos telemetry interface (JTI) sensors are supported in the following areas:

  • Chassis management error (cmerror) configuration and counters

  • Fabric, optical, and Flexible PIC Concentrator (FPC) environment statistics

  • Platform, interface, and alarm statistics

  • Transceiver statistics

  • Segment routing–traffic engineering (SR-TE) for colored telemetry statistics

  No JTI sensor support is available for these actions:

  • Enabling zero suppression in the Packet Forwarding Engine infra for ULC-based line cards

  • Enabling TARGET-DEFINED support (aft-telemetry library)

  • Configuring INITIAL-SYNC from the Packet Forwarding Infra for AFT-based and ULC-based line cards

• Junos YANG Data Model Explorer--> Telemetry Support. See [https://apps.juniper.net/ydm-explorer/.]

L2 features

• Layer 2 (L2) learning, trunk port, bridging, integrated routing and bridging (IRB), QinQ, VLAN handling, MAC accounting, LACP, LLDP, xSTP, and Ethernet ring protection switching (ERPS).

  [See Understanding Q-in-Q Tunneling and VLAN Translation, Understanding Layer 2 Bridge Domains on MX Series, Understanding Layer 2 Learning and Forwarding, and Introduction to OAM Connectivity Fault Management (CFM).]

• VRRP

  [See Configuring Q-in-Q Tunneling and VLAN Q-in-Q Tunneling and VLAN Translation, Understanding Layer 2 Bridge Domains, Understanding Layer 2 Learning and Forwarding, and Introduction to OAM Connectivity Fault Management (CFM).]

• Support for EVPN–MPLS unicast and multicast forwarding features.

  [See EVPN User Guide.]

• Support for EVPN–VXLAN unicast features.

  [See Understanding Programmable Flexible VXLAN Tunnels.]

• Support for seamless MPLS L2 feature pseudowire headend termination (PWHT).

  [SeeLayer 2 VPNs and VPLS Feature Guide for Routing Devices, and Pseudowire Subscriber Logical Interfaces Overview.]

L3 features

• Support for Layer 3 (L3) features and IGP (OSPF, IS-IS, RIP, and ECMP) for IPv4 and IPv6.

  [See Understanding OSPF Configurations and BGP Overview.]

• Support for forwarding features including IGP, Static Routing, BGP, BGP-PIC, and programmable routing protocol process (rpd). [For OSPF and BGP, see Understanding OSPF Configurations and BGP Overview.]

• Support for Bidirectional Forwarding Detection (BFD). [See Understanding BFD for Static Routes for Faster Network Failure Detection.]

  and Bidirectional Forwarding Detection (BFD).]

• SR-TE statistics for uncolored SR-TE policies on JTI. [For SR-TE telemetry, see Understanding OpenConfig and gRPC on Junos Telemetry Interface and Junos YANG Data Model Explorer.]

• Support for NGMVPN, GTM, Rosen MVPN, P2MP - RSVP-TE/mLDP, and MoFRR inband multicast LDP signaling.

  [See MPLS Overview, Multicast Overview, and Understanding Next-Generation MVPN Control Plane.]

• Support for redundant logical tunnel (RLT) interfaces and pseudowire subscriber interfaces using either a logical tunnel or RLT interfaces as an anchor point.

  [See Redundant Logical Tunnels Overview and Pseudowire Subscriber Logical Interfaces Overview.]

Licensing

• Support for Licensing: Juniper Agile Licensing provides simplified and centralized license administration and deployment. If you exceed the bandwidth capacity license, Junos OS generates periodic alarms indicating that you need bandwidth capacity license. View the bandwidth information of your device using the show system license bandwidth flex-only command. View the features available on your device using the show system license feature-list command.

  See [ System Log Explorer, Software Licenses for MX Series Routers and MPC Service Cards, and Activate Your Licenses.]

MACsec

• Support for Media Access Control Security (MACsec) in static connectivity association key (CAK) mode with GCM-AES-128, GCM-AES-256, GCM-AES-XPN-128, and GCM-AES-XPN-256 encryption. Only physical interfaces support this feature.

  [See Configuring MACsec.]

Network management and monitoring

• Support for port mirroring.

  [See Configuring Port Mirroring on MX, ACX, and PTX Series Routers.]

• Support for sFlow. [See sFlow Technology Overview.]

Platform and infrastructure

• Secure boot and common BIOS implementation based on the UEFI standard.

  See [ Junos OS Overview.]

Routing policy and firewall filters

• Support for distributed denial of service (DDoS).

  See [ Control Plane Distributed Denial-of-Service (DDoS) Protection Overview .]

Services applications

• Inline services support:

  • Inline NAT—NAT44 and NPTv6

  • Inline softwires—Mapping of Address and Port with Encapsulation (MAP-E) and IPv6 rapid deployment (6rd)

  • MAP-T (Mapping of Address and Port using Translation)

  [See [ Inline NAT, Configuring Mapping of Address and Port with Encapsulation (MAP-E), Configuring Mapping of Address and Port with Translation (MAP-T ), and Configuring Inline 6rd.]

• RPM, including all probe types and hardware timestamping of RPM probe messages in the Packet Forwarding Engine using the hardware-timestamp and one-way-hardware-timestamp configuration statements.

  See [ Understanding Using Probes for Real-Time Performance Monitoring on M, T, ACX, MX, and PTX Series Routers, EX and QFX Switches, hardware-timestamp , one-way-hardware-timestamp, and rpm (Services).]

• Two-Way Active Measurement Protocol (TWAMP)

  • Managed control type, for IPv4 traffic

  • Light control type, for IPv4 and IPv6 traffic

  • Configuring the TWAMP client instance to use si-x/y/z as the destination interface, which enables inline services, is not supported if the router has a JNP10K-LC4800 line card installed in the chassis.

    See [ Understand Two-Way Active Measurement Protocol, twamp.]

• Inline monitoring services support, including support for L2 firewall families. [See Inline Monitoring Services Configuration.]

• Juniper Resiliency Interface (JRI): IP Flow Information Export (IPFIX) exception reporting support. [See Juniper Resiliency Interface.]

• Inline active flow monitoring support. [See Understand Inline Active Flow Monitoring.]

• Routing Engine-based traffic sampling support. [See Configuring Traffic Sampling on MX, M and T Series Routers.]

• Inline video monitoring support. [See Inline Video Monitoring.]

• FlowTapLite support. [See Configuring FlowTapLite on MX Series Routers and M320 Routers with FPCs.]

Subscriber management and services

• Support for subscriber services functionalities on LC4800 line card for MX10004 and MX10008 devices, that includes:

  • PPP Subscribers with Unauthenticated Dynamic VLAN

  • PPP Subscribers with Unauthenticated Dynamic S-VLAN

  • PPP Subscribers with Authenticated Dynamic VLAN

  • PPP Subscribers with Authenticated Dynamic S-VLAN

  • DHCP Subscribers with Unauthenticated Dynamic VLAN

  • DHCP Subscribers with Unauthenticated Dynamic S-VLAN

  • DHCP Subscribers with Authenticated Dynamic VLAN

  • DHCP Subscribers with Authenticated Dynamic S-VLAN

  • L2TP Subscribers (LNS)

  • L2TP Subscribers (LAC)

  • Pseudowire

  • CoS Service

  • Firewall Service

  • LTS accounting (Goal for FRS)

  • BFD liveness

  • CoS support for BNG on pseudowire over active/active RLT interface

  • L2 dynamic overhead adjust for accounting

  • Scaling and Performance

• RFC 2544-based benchmarking tests support. [See Understanding RFC2544-Based Benchmarking Tests on MX Series Routers.]