Understanding the Hyper Mode Feature on Enhanced MPCs for MX Series Routers and EX9200 Switches
Starting with Junos OS Release 15.1, enhanced MPCs can be configured to support increased packet processing rates. Enhanced MPCs include these models: MPC3E, MPC4E, MPC5E, MPC6E, MPC7E-MRATE, MPC7E-10G, MX2K-MPC8E, and MX2K-MPC9E.
Starting with Junos OS Release 18.2R1, MPC JNP10K-LC2101 can be configured to support increased packet processing rates. A higher rate of processing of data packets results in the optimization of the lifetime of a data packet. Optimization of the data packet lifetime enables the network device (a router or a switch) to provide better performance and throughput.
To enable the device to support increased packet processing rates, you must configure the hyper mode feature. After configuring the hyper mode feature, you must reboot the device for the changes to take effect.
When you configure the hyper mode feature on the device, the configured mode changes from normal mode to hyper mode. However, because the configuration does not take effect until you reboot the device the current mode of the device remains as normal mode. The current mode changes from normal mode to hyper mode after you reboot the device. If the hyper mode feature is not configured, thedevice processes data packets in normal mode.
You can enable the hyper mode feature only if the network-service mode on the device is configured as either enhanced-ip or enhanced-ethernet.
Table 1 displays the values of the current and configured mode based on the hyper mode configuration and system reboot.
Table 1: Current Mode and Configured Mode Values Based on Hyper mode Configuration
Hyper mode is configured but the device is not rebooted.
Hyper mode is configured and device is rebooted.
Hyper mode configuration is removed and device is not rebooted.
Hyper mode configuration is removed and device is rebooted.
Starting in Junos OS Release 19.2R1, MPC10E-10C and MPC10E-15C line cards support the following features in hyper-mode:
Configuring ICMP redirect and generating ICMP redirect messages.
Padding VLAN packets to a minimum frame size of 68 bytes, by using the command set interfaces interface-name gigether-options pad-to-minimum-frame-size.
Collecting interface family statistics for IPv4 and IPv6, by using the command show interfaces statistics detail interface-name.
When you configure hyper mode, the following features are not supported:
Creation of Virtual Chassis
Forwarding class accounting (enhanced mode)
Interoperability with legacy DPCs, including MS-DPCs. The MPC in hyper mode accepts and transmits data packets only from other existing MPCs.
Interoperability with non-Ethernet MICs and non-Ethernet Interfaces such as channelized interfaces, multilink interfaces, and SONET interfaces.
Junos Node Slicing
Padding of Ethernet frames with VLAN.
Precision Time Protocol
Provider Backbone Bridging (PBB) and Ethernet VPN (EVPN)
Sending Internet Control Message Protocol (ICMP) redirect messages. ICMP redirects are disabled by default and cannot be re-enabled in hyper mode.
Termination or tunneling of all subscriber-based services.
After you configure the hyper mode feature and reboot the device, existing MPCs that do not support the hyper mode feature, such as MPC1, MPC2, and MPC3, power on in normal mode. Also, when you have installed MICs and PICs on MPCs that are in normal mode when the hyper mode feature is enabled, those MICs and PICs do not power on. Following is a list of the MICs and PICs that do not power on: