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-iporenhanced-ethernet. -
Hyper-mode is the default forwarding mode on the SCBE3-MX. If your deployment does not need hyper-mode, disable hyper-mode using the
set forwarding-options no-hyper-modecli command before installing the Routing Engine into the SCBE3-MX. See also: SCBE3-MX Description
Table 1 displays the values of the current and configured mode based on the hyper mode configuration and system reboot.
|
Action |
Current Mode |
Configured Mode |
|---|---|---|
|
Hyper mode is configured but the device is not rebooted. |
Normal mode |
Hyper mode |
|
Hyper mode is configured and device is rebooted. |
Hyper mode |
Hyper mode |
|
Hyper mode configuration is removed and device is not rebooted. |
Hyper mode |
Normal mode |
|
Hyper mode configuration is removed and device is rebooted. |
Normal mode |
Normal mode |
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 Fusion
-
Junos Node Slicing
-
Padding of Ethernet frames with VLAN is not supported in Junos OS releases prior to 19.2R1.
-
Precision Time Protocol
-
PBB-EVPN.
-
Sending Internet Control Message Protocol (ICMP) redirect messages is not supported in Junos OS releases prior to 19.2R1. In versions prior to 19.2R1, ICMP redirects are disabled by default and cannot be re-enabled in hyper mode.
-
Termination or tunneling of all subscriber-based services.
-
Collecting interface family statistics for IPv4 and IPv6 is not supported in Junos OS releases prior to 19.2R1. The interface family statistics are collected by using the
show interfaces statistics detail interface-namecommand.
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:
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.