Professional Documents
Culture Documents
NetEngine 8000 M14, M8 and M4 V800R023C10SPC500 Product Description
NetEngine 8000 M14, M8 and M4 V800R023C10SPC500 Product Description
Product Description
Issue 01
Date 2024-03-31
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: support@huawei.com
Contents
3 Product Architecture.............................................................................................................15
3.1 Physical Architecture............................................................................................................................................................ 15
3.2 Logical Architecture............................................................................................................................................................. 16
3.3 Software Architecture.......................................................................................................................................................... 17
3.4 Forwarding Process.............................................................................................................................................................. 20
4 Application Scenarios........................................................................................................... 23
5 NMS.......................................................................................................................................... 24
6 Product Specifications.......................................................................................................... 25
Figures
Tables
Purpose
This document describes the HUAWEI NetEngine 8100 M14/M8, NetEngine 8000
M14K/M14/M8K/M8/M4 & NetEngine 8000E M14/M8 series in terms of its
product positioning and features, architecture, technical specifications, link
features, service features, usage scenarios, and operation and maintenance.
Related Versions
The following table lists the product versions related to this document.
Intended Audience
This document is intended for:
Security Declaration
● Notice on Limited Command Permission
The documentation describes commands when you use Huawei devices and
make network deployment and maintenance. The interfaces and commands
for production, manufacturing, repair for returned products are not described
here.
If some advanced commands and compatible commands for engineering or
fault location are incorrectly used, exceptions may occur or services may be
interrupted. It is recommended that the advanced commands be used by
engineers with high rights. If necessary, you can apply to Huawei for the
permissions to use advanced commands.
● Encryption algorithm declaration
The encryption algorithms DES/3DES/RSA (with a key length of less than
3072 bits)/MD5 (in digital signature scenarios and password encryption)/
SHA1 (in digital signature scenarios) have a low security, which may bring
security risks. If protocols allowed, using more secure encryption algorithms,
such as AES/RSA (with a key length of at least 3072 bits)/SHA2/HMAC-SHA2
is recommended.
For security purposes, insecure protocols Telnet, FTP, and TFTP as well as
weak security algorithms in BGP, LDP, PCEP, MSDP, DCN, TCP-AO, MSTP, VRRP,
E-Trunk, AAA, IPsec, BFD, QX, port extension, SSH, SNMP, IS-IS, RIP, SSL, NTP,
OSPF, and keychain features are not recommended. To use such weak security
algorithms, run the undo crypto weak-algorithm disable command to enable
the weak security algorithm function. For details, see the Configuration Guide.
For security purposes, you are advised not to use weak security algorithms in
this feature. If the weak security algorithm function has been disabled in the
current system, an error message will be displayed when you configure a
weak security algorithm. If a weak security algorithm is required, run the
undo crypto weak-algorithm disable command to enable the weak security
algorithm function first.
● Password configuration declaration
– When the password encryption mode is cipher, avoid setting both the
start and end characters of a password to "%^%#". This causes the
password to be displayed directly in the configuration file.
– To further improve device security, periodically change the password.
● MAC addresses and Public IP addresses Declaration
– For purposes of introducing features and giving configuration examples,
the MAC addresses and public IP addresses of real devices are used in the
product documentation. Unless otherwise specified, these addressees are
used as examples only.
– Open-source and third-party software may contain public addresses
(including public IP addresses, public URLs/domain names, and email
addresses), but this product does not use these public addresses. This
complies with industry practices and open-source software usage
specifications.
– For purposes of implementing functions and features, the device uses the
following public IP addresses:
Network planning and site design must comply with reliability design
principles and provide device- and solution-level protection. Device-level
protection includes planning principles of dual-network and inter-board dual-
link to avoid single point or single link of failure. Solution-level protection
refers to a fast convergence mechanism, such as FRR and VRRP. If solution-
level protection is used, ensure that the primary and backup paths do not
share links or transmission devices. Otherwise, solution-level protection may
fail to take effect.
Special Declaration
● This document package contains information about the NetEngine 8100 M,
NetEngine 8000E M, NetEngine 8000 M. For details about hardware, such as
devices or boards sold in a specific country/region, see Hardware Description.
● This document serves only as a guide. The content is written based on device
information gathered under lab conditions. The content provided by this
document is intended to be taken as general guidance, and does not cover all
scenarios. The content provided by this document may be different from the
information on user device interfaces due to factors such as version upgrades
and differences in device models, board restrictions, and configuration files.
The actual user device information takes precedence over the content
provided by this document. The preceding differences are beyond the scope of
this document.
● The maximum values provided in this document are obtained in specific lab
environments (for example, only a certain type of board or protocol is
configured on a tested device). The actually obtained maximum values may
be different from the maximum values provided in this document due to
factors such as differences in hardware configurations and carried services.
● Interface numbers used in this document are examples. Use the existing
interface numbers on devices for configuration.
● The pictures of hardware in this document are for reference only.
● The supported boards are described in the document. Whether a
customization requirement can be met is subject to the information provided
at the pre-sales interface.
● In this document, public IP addresses may be used in feature introduction and
configuration examples and are for reference only unless otherwise specified.
● The configuration precautions described in this document may not accurately
reflect all scenarios.
● Log Reference and Alarm Reference respectively describe the logs and alarms
for which a trigger mechanism is available. The actual logs and alarms that
the product can generate depend on the types of services it supports.
● All device dimensions described in this document are designed dimensions
and do not include dimension tolerances. In the process of component
manufacturing, the actual size is deviated due to factors such as processing or
measurement.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
V800R023C10SPC500 01 2024-03-30
2.2 Appearance
Appearance of the NetEngine 8000 M4
Figure 2-6 Appearance of the NetEngine 8000 M14 (AC Including 4*AC Power)
Figure 2-7 Appearance of the NetEngine 8000 M14 (AC Including 2*AC Power)
● Powerful routing capabilities: The device supports super large routing tables
and provides Routing Information Protocol (RIP), Open Shortest Path First
(OSPF), Intermediate System-to-Intermediate System (IS-IS), Border Gateway
Protocol 4 (BGP-4), and multicast routing protocols. It also supports simple
and ciphertext authentication, as well as fast route convergence. These
features ensure network stability and security in complicated routing
environments.
● Strong service transport capabilities: IP, MPLS, and SRv6 networking can be
deployed depending on networking requirements, L2VPN, L3VPN, MVPN, and
EVPN services are supported, and functions such as traffic engineering (TE),
selective 802.1Q-in-802.1Q (QinQ), and Generic Routing Encapsulation (GRE)
can be deployed. Because the device can provide access for both traditional
and emerging services, it satisfies the needs of multiple service environments.
● Powerful and expandable multicast capabilities: The device supports IPv4/IPv6
multicast protocols, such as Protocol Independent Multicast - Sparse Mode
(PIM-SM), PIM - Source Specific Multicast (PIM-SSM), Multicast Listener
Discovery Version 1 (MLDv1)/Multicast Listener Discovery Version 2 (MLDv2),
Internet Group Membership Protocol Version 3 (IGMPv3), IGMP snooping,
MLD snooping, and Bit Index Explicit Replication IPv6 Encapsulation (BIERv6).
The device has the flexibility to carry video services, such as Internet Protocol
Television (IPTV) services, and satisfies the requirements for multicast services
on networks of any scale.
Full-Lifecycle Automation
iMaster NCE-IP enables full-lifecycle automation and network-wide real-time
visualization. Precise in-band flow measurement based on the controller and IFIT
enables real-time visualization of service quality and fault locating within minutes.
Energy-Conserving Design
The environmentally friendly design of the device conserves energy and reduces
emissions.
● The device has a cooling and energy-conserving system adopting an advanced
ventilation and heat dissipation design and intelligent fans. This allows the
device to automatically detect and adjust the temperature, greatly improving
power utilization.
● The device supports intelligent fan speed adjustment, greatly reducing power
consumption and providing more obvious advantages in energy saving.
Feature Description
Energy ● Separate hot air ducts from cold air ducts in the
conservation equipment room of the NetEngine 8100 M, NetEngine
suggestions for 8000E M, NetEngine 8000 M, place an air intake vent
the NetEngine besides a cold air duct, and prevent hot air from entering
8100 M, the air intake vent.
NetEngine ● Select the best suited AC power modules to prevent high
8000E M, power consumption resulted from AC power light load
NetEngine 8000 (load ratio is less than 30%).
M
● Cover vacant slots with filler panels and cap unused ports
with rubber plugs to help ensure efficient heat dissipation
of the NetEngine 8100 M, NetEngine 8000E M, NetEngine
8000 M.
● Power off boards and shut down ports if they are not
currently used.
● It is recommended that the NetEngine 8100 M, NetEngine
8000E M, NetEngine 8000 M work in basic energy
conservation mode.
3 Product Architecture
NOTE
The preceding figure shows the functional host subsystem of the NetEngine 8000 M14
(DC).
As shown in Figure 3-4Figure 3-5, the Packet Forwarding Engine (PFE) uses the
Network Processor (NP) to implement high-speed packet forwarding through
table lookup. External memory types include the Static Random Access Memory
(SRAM), Dynamic Random Access Memory (DRAM), and Net Search Engine
(NSE). The SRAM stores forwarding entries; the DRAM stores packets; the NSE
performs non-linear searching.
Data forwarding is processed on the NetEngine 8000 M14 in both the upstream
and downstream directions.
● Upstream process: The Physical Interface Card (PIC) encapsulates packets into
frames and sends them to the PFE. The inbound interface processing module
on the PFE decapsulates the link-layer protocol information and identifies the
packet types. Then the upstream traffic classification module classifies traffic
based on the QoS configurations on the inbound interface. After traffic
classification, the PFE searches for forwarding entries to determine where to
forward the packets. For example, to forward IPv4 unicast packets, the PFE
searches the Forwarding Information Base (FIB) for the outbound interfaces
and next hops of the packets based on the packets' destination IP addresses.
Finally, the PFE sends the packets and the scheduling priority and forwarding
information to the Traffic Management (TM) module.
● Downstream process: The PFE encapsulates link-layer information in the
packets based on the packet type and outbound interface type. For example,
for an IPv4 packet destined for an Ethernet interface, the PFE obtains the
MAC address of the next hop. Then the downstream traffic classification
module classifies traffic based on the QoS configurations on the outbound
interface. The outbound interface processing module encapsulates the packets
with new Layer 2 headers and sends them to the PIC.
Data forwarding is processed on the NetEngine 8000 M8/NetEngine 8000 M4 in
both the upstream and downstream directions.
● Upstream process: The Physical Interface Card (PIC) encapsulates packets into
frames and sends them to the PFE. The processing module on the inbound
interface parses the link-layer protocol information and identifies the packet
type. Then the upstream traffic classification module classifies traffic based on
the QoS configurations on the inbound interface. After traffic classification,
the PFE searches for forwarding entries to determine where to forward the
packets. For example, to forward IPv4 unicast packets, the PFE searches the
Forwarding Information Base (FIB) for the outbound interfaces and next hops
of the packets based on the packets' destination IP addresses.
● Downstream process: The PFE encapsulates link-layer information in the
packets based on the packet type and outbound interface type. For example,
for an IPv4 packet destined for an Ethernet interface, the PFE obtains the
MAC address of the next hop. Then the downstream traffic classification
module classifies traffic based on the QoS configurations on the outbound
interface. The outbound interface processing module encapsulates the packets
with new Layer 2 headers and sends them to the PIC.
4 Application Scenarios
5 NMS
6 Product Specifications