Imaster NCE V100R022C10SPC100 System Overview (System Overview) 01

iMaster NCE V100R022C10SPC100
System Overview (System Overview)
www.huawei.com
Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.
Course Objectives
Upon completion of this course, you will be able to:

n Understand the positioning, architecture, and system capabilities of NCE
V100R022C10SPC100.
Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved. Page 1
Change History
Date Version Description Author
Pan Jiyu, Xie Qing, Gu Xiaogang, Zheng

2023-04-15 V1.0 This is the first official release. Ting, Wang Haiyan, Chen Xian, Wang
Fengmei
Contents
n System Overview
n Questions and Suggestions
Software and
Management Installation and
Positioning Architecture Hardware Migration Expansion HA
Capability Deployment
Configuration
NCE Positioning
NCE is an innovative network cloudification engine
Operator BSS/OSS Mobile terminal
developed by Huawei. Positioned as the brain of future
cloud-based networks, NCE integrates functions such as
Application
network management, service control, and network

package
Portal NBI/Open API Proxy

analysis. It is the core enablement system for network
resource pooling, network connection automation and self-
Commercial applications O&M applications AI
(Premium Broadband, Premium Private Training optimization, and O&M automation.
(Wavelength adding,
Line, IP+Optical...) Center NCE is located at the management and control layer of the
cutover...)
cloud network. It manages and controls IP, transport, and
access devices, and opens capabilities to support
interconnection and integration with OSSs, BSSs, and
service orchestrators to support quick customization of the
Intent engine Intelligence engine application layer.
package
Conversion Verification Decision Forecast Suggestion NCE aims to build an intent-driven network (IDN) that is first
Basic
automated, then self-adapting, and finally autonomous.

n Automation: Autonomous Driving Network (AND) is
enabled to automate network deployment and
Automation engine maintenance throughout the lifecycle.
Analysis engine
n Self-adaptation: Service policies are automatically
Management Control Perception Analysis generated based on big data using the real-time analyzer
to implement proactive maintenance and closed-loop
optimization.
n Autonomy: Artificial intelligence and machine learning are
package
Platform
used to build an intelligent network that can automatically

Basic services NCE Common Product engineering generate dynamic policies.
(Logs, alarms, (Development framework, (Deployment, disaster
security...) southbound framework...) recovery...)
Integrating Traditional Manager, Controller, and Analyzer Capabilities to
Achieve Unified Management and Control
U2000 eSight AC-WAN AC-SDWAN uTraffic NetStar
CloudOpera AC-T
NetOpen Orchestrator SDN
N2510 SecoManager
AC-Campus
AC Super IP Crystal
AC-DCN
Incorporated:
p Most features of U2000, uTraffic, AC-WAN, AC-T, AC-Campus, AC-DCN,
and AC-SDWAN
p NetOpen, an open and enabling platform for home networks, providing
home Wi-Fi network management
p CloudOpera Orchestrator SDN, an SDN orchestrator developed in 2017,
Manager Controller Analyzer focusing on multi-domain private line service provisioning. AC Super, a
super controller developed in 2018, delivered for Multi-Layer Network
Navigator
NCE p Netstar: Visualization and forecast of optical network resources

p SecoManager: Security product management software
p N2510: ODN resource management and diagnosis O&M component
Not incorporated:
p eSight is pending planning.
Software and
Configuration
NCE Characteristics
NCE is a network lifecycle automation platform that integrates management, control, and analysis. It focuses on service automation,
O&M automation, and network autonomy to support carriers' network cloudification and digital operation transformation.
Unified Management and Control Supporting Smooth Cloud Platform Supporting Block-Building
Network Evolution Deployment
n Integrates traditional NMS and SDN controller functions. n Uses a unified cloud platform, user portal, and API gateway,
n Achieves unified management and control of SDN and non- achieves unified installation, deployment, and upgrade, and
SDN networks, leverages SDN network automation, explores consistent data models, and greatly simplifies O&M.
legacy network values, and reduces technical difficulties and n Adopts a microservice architecture, achieves user scenario-
risks of network evolution. specific on-demand deployment.
Product
Open APIs and Programmability Supporting Fast Characteristics Big Data-based Proactive Maintenance
Service Rollout
n Provides standard RESTful APIs to connect to external n Collects network-wide data (using the Telemetry technology),
systems. and based on the big data platform, performs panoramic and
n Provides a DevOps-based tool platform to flexibly customize in-depth analysis on the quality and traffic data of the entire
innovative services based on flexible business scenarios and network to implement intelligent analysis and predictable
network technologies. (not provided in the current version) maintenance.
n Continuously verifies network design and configuration to
ensure that the network accurately implements the users'
intention and achieves stable operation.
Software and
Configuration
Differences Between NCE and U2000/AC/uTraffic
U2000/AC/uTraffic NCE
Portal Northbound Portal Northbound Portal Northbound Portal Northbound Portal NBI
U2000 uTraffic
AC-WAN AC-T
Network management
Network control Network control
Network analysis and Network Network analysis
(FCAPS) assurance Network Control
management and assurance
SBI SBI SBI SBI
SBI
Managed
Network Metro Converged Managed
(Legacy + Network Backbone Metro Converged
network Network Backbone
SDN)
1. Traditional U2000 manages the entire network, including legacy 1. Integrates network management, control, and analysis, manages the
networks. entire network (Legacy+SDN, access/IP/transport) lifecycle, and
2. AC-WAN and AC-T provision and control SDN networks in the IP enables network automation.
and transport domains. 2. Supports the cloud architecture, provides a unified portal,
3. uTraffic performs O&M assurance for the entire network, including northbound and southbound interfaces, and engineering platform,
legacy networks. and supports smooth capacity expansion.
4. Customers need to switch between these systems to implement 3. Opens network capability, provides OpenAPI and designer, and
the required functions, which bring decentralized management supports scenario-specific app development and rollout.
risks in the network.
Software and
Configuration
NCE Architecture (L0)

Tenant Self-Service Service ① Unified cloud platform: Provides public development
Applications AI Training Center
Portal Orchestrator/OSS frameworks and common services (such as alarm
Intent-based API AI-driven Insights management, security management, and inventory).
Components can be flexibly deployed on demand, and
Business scenario application unified engineering capabilities such as installation,
Scenario- (Access Insight, Home Insight, Automated O&M scenario application
specific Private Line provisioning, Private Line
(5G site densification, IP+optical, Unified portal capacity expansion, and HA are provided.
network analysis and optimization...)
apps Analysis and Assurance ...)
② Automation engine: Supports automated network O&M,
6 Open APIs flexible network resource and service orchestration, and
fast device adaptation.
4 Intent engine 5 Intelligence engine
③ Analysis engine: Provides real-time data collection and
Conversion Verification Decision Forecast Suggestion
Functions processing capabilities and flexible analysis framework to
support efficient data processing.
2 Automation engine
3 Analysis engine
④ Intent engine: Converts business logic to network
operations and performs continuous verification to ensure
Management Control Perception analysis sustained business intent.
⑤ Intelligent engine: Implements AI online training and

Cloud Basic framework
Common services Product engineering algorithm debugging, and provides a scenario-based
platform 1 (Engineering, logs, alarms, security...)
(Service framework,
(Deployment, HA, O&M...)
middleware...) development framework (learning library).
Configure Context ⑥ OpenAPI: Provides various OpenAPIs and open and

programmable network capabilities.
Physical & Virtual Network Infrastructure
Software and
Configuration
Cloud Platform Architecture (L1)

Engineering Engineering Common services Domain services
management
Hardware and
Installation/expans Log management Automation Analysis
software ...
configuration ion service service
Upgrade/
planning
patching Alarm monitoring Unified
Certificate
platform
Network planning management Portal
Service development framework
Key management Security
management Southbound
Backup and Management service Control service
collection service
IP address restore development framework framework
Information center framework
planning
HA
Micro-
FEBS service
System monitoring
service
middleware
Distributed Service center DB KAFKA
VM resource
Inspection and transaction
planning
O&M
Middleware Task management Redis ETCD APIGateway
management
OS configuration
planning Running platform Cloud-based
OS: EulerOS (Delivered) deployment
Physics machine FusionCompute
hardware (TaiShan
Communication
200 (Model 2280), Delivered hardware (TaiShan Private cloud (FS) HUAWEI CLOUD
matrix planning
2288X V5, and 200 (Model 2280), 2288X V5,
RS221G1) and RS221G1)
Software and
Configuration
Automation Engine Architecture and Functions (L1)

Portal/User
Orchestrator/OSS Third party applications q Network connection management
Network Network l Receives E2E network connection requests from the
Network
service operation portal or northbound interface and parses the requests
operation
operation into NE configurations.
l Displays information such as network service trails and
Northbound service service SLAs.
CORBA/XML Restconf RESTful SFTP SNMP Websocket SSE JMS q Network control
l Dynamically collects network topologies, detects
topology changes, and automatically computes new
Automated Engine
Service
Network/service management Network monitoring Network control information trails.
l Pre-computes service trails and periodically re-
Analysis engine
Composite service VPN monitoring and IP trail MPLS IP
diagnosis visualization optimization optimization
optimizes the trails.
L3VPN L2VPN Tunnel service Automatic fiber
monitoring
Performance
monitoring
Centralized trail
computing
Route
topology q Network monitoring
OTN/ASON SDH/ASON ETH
l Provides basic O&M assurance for networks and
Packet service fault diagnosis PCEP BGP-LS
services, including basic performance monitoring, test
diagnosis, and fault diagnosis
NE management Inventory management q NE and inventory management
IP NEs Access NEs Optical NEs Resources Topology l Manages IP networks, access NEs, and optical NEs in
a unified manner, including device resource allocation
Third-Party NEs PnP Services Resource pool and southbound connection.
l Manages physical topology, Layer 1, Layer 2, and
Southbound service Service SLA
Layer 3 topology of a physical network.
CLI NetConf PCEP BGP LS OSPF SNMP

Network operation q Southbound and northbound services
l Unified northbound: Provides RESTful, RESTconf,
Kafka APIs, and SFTP NBIs.
Device configuration Device status l Unified southbound: Provides various southbound
Service trails Network topology management protocols, such as CLI, NetConf, PCEP,
and BGP LS.
NE Device alarms and logs
Service SLA status
Close Loop
Currently supported
To be supported
NCE Analyzer Architecture and Functions (L1)
Design APP q Application layer
Studio l Application-oriented model, providing dedicated
Base station analysis Home analysis Enterprise analysis Campus analysis Application analysis
apps based on different usage scenarios.
Feedback
q Service layer
Intelligence engine (on local) l Modeling: Modeling and analysis of service
Model IDE Service layer
Monitoring Rule Inventory Anomaly
...
(PWE3 and EVPN) and network (NE, link, and
management engine management management tunnel) models.
Object AI Jobs
l Model management: Modeling and managing
property Network AI model objects related to services, networks, and devices
Domain
metric model
NE Network Service User App to provide services for monitoring.
Anomaly Traffic Fault
detection forecast forecast
... l Monitoring management: Starting massive
monitoring instances based on app requirements.
Model
Algorithm layer optimization SoftCom AI inference platform q Intelligence engine and algorithm layer
and update l Provides the AI algorithm running framework and
Traditional algorithm AI algorithm Migration Model Model Sample
test management receiving management executes the AI algorithms in task mode; provides
Pipeline
the automatic algorithm optimization capability.
IDE Computing and storage layer l Supports application of various analysis, forecast,
and identification algorithms based on the
DataSet machine learning and deep learning algorithms.
ODAE q Computing and storage layer
Pipeline Mgr AQL TQL Druid
TQL l Data processing: Uses big data engine in the
Script industry to process collected data.
NDP l Data storage: Uses the big data storage platform
AI operator in the industry to query data storage.
Kafka HDFS Spark
q Collection layer
l Provides multiple collection protocols, such as
Collection layer
Telemetry, Syslog, SNMP, and Qx, to collect
Collector SNMP Qx FTP Syslog Telemetry Net Stream massive data from devices in real time.
IDE
Software and
Configuration
NCE Context
U2 U3
U1
Orchestration/OSS
Network Tenant System interfaces:
Designer Operator
I1
n Human-machine interfaces
Design
Studio (not
Portal Northbound interfaces
Basic
platform
① U1: Design UI
provided in
the current
version)
Common ② U2: O&M UI
services
Network management Network control Network analysis

③ U3: Tenant UI
Service
design n External interfaces
Product
engineering
① I1: Northbound interfaces between
Resource inventory
Southbound interfaces
NCE and the carrier's OSS
Third-party Basic
adaptation
design
engineering
② I2: Southbound interfaces between
Southbound-driven
Huawei network Third-party network NCE and NEs
adaptation adaptation
I2
Managed Fabric Metro Converged

network Network Backbone
Software and
Configuration
Interfaces Between NCE and Other Systems

Service provisioning, alarm, performance monitoring
Mobile
OSS/BSS/Orchestrator
app SDK
REST/XML/ REST/Web socket
CORBA/SNMP/Text/TL1/
Syslog
Radius
Authentication, Authorization and
Accounting
Script
AAA OptiX NetStar
NCE Script/XML
IBMS
REST/Qx/SNMP/NetConf/TL1/
TFTP/FTP/SFTP/Telnet/STelnet/ REST
REST OSPF/OSPF-TE/PCEP/BGP-LS/
BGP FlowSpec/BGP
RPD/MQTT/NetStream/Telemetry
Cloud management system

Managed third party controller Managed device
(FusionSphere)
Software and
Configuration
NCE Security Precautions

Office
network
Operator
Operator Trust zone
OSS/BSS App
Public
network
Mobile app 1. A firewall must be deployed for external
1 1 1
access to the NCE server to isolate external
Firewall HTTPS Firewall HTTPS/TLS/SSH
NCE Server
Firewall HTTPS
attacks (as shown in ①).
O&M access
layer
NCE portal
Northbound
access layer
NBI gateway API gateway
2. The NCE server can be divided into the
access layer (including O&M access,
2
Firewall HTTPS
2
Firewall HTTPS northbound access, and southbound access)
Trust zone and core service area. Generally, they can be
deployed in the same trust zone. If high
Service Platform and
Network
management Subsystem
Network control
engineering security is required, firewalls can be deployed
Data storage Security/alarm
Data storage
between each layer (as shown in ②).
and backup /topology/...
and backup
Network analysis
3. By default, NCE opens only secure access
protocols and needs to be customized for
compatibility scenarios that require insecure
2
protocols.
Southbound
NCE southbound-
4. The DCN between NCE nodes for internal
access layer
driven communication is isolated from the DCN for
1 Qx (TLS)/SNMP v3/NetConf 1
external access. The southbound
MQTT
Firewall (SSH)/SFTP/SSH/RESTful/BGP/OSPF/... Firewall communication DCN is isolated from the
Device zone
Infrastructure Transport+IP+Access Third-party Third-party
Service network
Home northbound communication DCN.
NEs NEs controller gateway
network
Software and
Performance Specifications (1)

Configuration
Item Sub-item Indicator Manager Indicator

NCE-T: The Manager + Controller supports 6k, 15k, 30k, 50k and 150k equivalent NEs.
The Manager + Controller + Analyzer supports 6k, 15k, 30k, and 50k equivalent NEs.
NCE-IP: • NCE-FAN (Private Cloud): supports
The Manager + Controller + Analyzer supports 6k, 15k, 30k, and 80k equivalent NEs. 1k (for NCE Lite), and 15k equivalent
NEs.
Note: The Controller supports a maximum of 30k equivalent NEs (30k SR-TE, SR-TP, or RSVP-TE tunnels or 6k SR Policies).
NCE-FAN: • NCE-IP: supports 2k, 6k, 15k and
30k equivalent NEs.
Number of • Manager+Controller (centralized): supports 1k (Lite), 2k (Manager+Controller + Home network co-deployed on TaiShan/2288X servers), 6k (enterprise network), and 30k
equivalent NEs equivalent NEs. • NCE-T: supports 1k (for NCE Lite),
2k, 6k, 15k, and 30k equivalent NEs.
• Manager+Controller (distributed): supports 30k, 100k, and 150k equivalent NEs.
• NCE: supports 1k (for NCE Lite), 2k,
• ODN Visualizer: supports 50k (private cloud) and 1 million subscribers. 6k, 15k, and 30k equivalent NEs.
• FANS: supports 30k equivalent NEs.
• Home network: supports 70k (Manager+Controller + Home network co-deployed on TaiShan/2288X servers), 100k, and 1 million subscribers.
• Premium broadband + Home network: supports 50k, 500k, and 1 million subscribers.
NCE-Super:
NE management • 2B Private Line: supports 15k, 50k, and 100k physical NEs.
capability NCE:
• NCE IP+T Manager+Controller+Analyzer: supports 6k, 15k, and 30k equivalent NEs.
• NCE IP+T Manager+Controller+Analyzer + NCE FAN Manager: supports 15k and 30k equivalent NEs.
IP+optical: NCE-Super supports 1200 physical NEs, mapping to the following controller scenarios:
(1) NCE-IP and NCE-T are deployed separately: Manages 30,000 IP physical NEs and 20,000 transport physical NEs.
(2) NCE-IP and NCE-T are deployed together: Manages 50,000 physical NEs.
Note: The deployment must meet the requirements for the number of physical NEs on NCE-Super and equivalent NEs on the Controller.
6k equivalent NEs: 64 2k equivalent NEs: 32
Number of online 50k equivalent NEs: 200 (only for NCE-T) 30k equivalent NEs: 200
clients 150k equivalent NEs: 600 (only for NCE-T)
NCE-Super: 300
If the number of equivalent NEs is less than or equal to 15k, a maximum of 15k physical NEs can be accessed.
NCE-IP: supports 15k physical nodes when the PTN is managed.
NCE-T: meets the NE equivalent NEs when the transport network is managed.
NCE-FAN:
• Supports 30k MDUs (15k equivalent NEs) when the FTTx network is managed.
Number of Supports 1.2 million ONTs. 12k
physical nodes NCE-Super:
•Priviate line: supports 15k, 50k, and 100k physical NEs.
•Multi-domain private line: supports 50k, and 100k physical NEs.
•Private line + Analyzer: supports 15k and 50k physical NEs.
IP+Optical + private line + Analyzer: supports 6k and 15k physical NEs.
Note: N indicates the number of equivalent NEs.

Note: The preceding data is for reference only. For details about the specifications, see Product Description of the mapping SPC version.
Software and

Configuration

6k equivalent NEs:
• Manager: 90k • 2k/6k equivalent NEs: 90k
• Controller: 24k for the SDH service • 15k equivalent NEs: 220k
15k equivalent NEs: • 30k equivalent NEs: 500k
Maximum number of SDH trails • Manager: 220k • 50k equivalent NEs: 800k
• Controller: 50k
30k equivalent NEs:
• Manager: 500k
• Controller: 100k
50k equivalent NEs:
Service • Manager: 800k
management • Controller: 100k
capability 6k equivalent NEs:
• Manager: 30k • 2k/6k equivalent NEs: 30k
• Controller: 4.5k for the OCh tunnel, 12k for the ODUk tunnel, 12k for the Client service • 15k equivalent NEs: 70k
15k equivalent NEs: • 30k equivalent NEs: 300k
• Manager: 70k WDM trails, less than 15k networkwide electrical-layer links • 50k equivalent NEs: 500k
Maximum number of WDM trails • Controller: 10k for the OCh tunnel, 25k for the ODUk tunnel, 25k for the Client service
30k equivalent NEs:
• Manager: 300k WDM trails, less than 30k networkwide electrical-layer links
• Controller: 20k for the OCh tunnel, 50k for the ODUk tunnel, 50k for the Client service
50k equivalent NEs:
• Manager: 500k WDM trails, less than 50k networkwide electrical-layer links
• Controller: 40k for the OCh tunnel, 100k for the ODUk tunnel, 100k for the Client service
Maximum number of L2 trails 6k equivalent NEs: Same as the Indicator column.
4k for EoS trails, 6k for EoO trails, 3k for MPLS-TP trails
15k equivalent NEs:
10k for EoS trails, 15k for EoO trails, 7.5k for MPLS-TP trails
30k equivalent NEs:
50k equivalent NEs:
Number of IP service access interfaces N x 20 Same as the Indicator column.
Number of tunnels N x 6 (the maximum management capacity of the Controller is 64k) Same as the Indicator column.
Number of 2B private line services M x 10 (M indicates the number of physical NEs managed by NCE-Super). A maximum of 1 million services can be managed. N/A
• Concurrent requests through the CORBA NBI: 4
• Concurrent requests through the XML NBI: 20
• Maximum number of third-party OSSs supported through the SNMP NBI: 10
NBI Number of concurrent • Maximum number of third-party OSSs supported through the text performance NBI: As an FTP client, it can send files to one OSS. As an FTP server, it can access a Same as the Indicator column.
processing requests/maximum number of maximum of three OSSs.
capability connections through the NBI • Maximum number of OSSs supported through the TL1 NBI: 30 per instance
• Maximum number of third-party Kafka Servers supported through the Kafka NBI: 10
Note: For details about the performance indicators, see sections about the NBI in iMaster NCE V100R022C10 Product Description.
Software and
Configuration

Analyzer Number of SNMP/Qx instances N x 30 (applicable to NCE-T and NCE-IP, with a 15-minute collection period) N/A
management
capability Number of SNMP/Qx indicators N x 30 x 50 (applicable to NCE-T and NCE-IP, with a 15-minute collection period) N/A
Telemetry-based data collection N x 20 (with a 15-minute collection period. For the conversion with other periods, N/A
see Product Description.)
Intelligent incident processing < 80k equivalent NEs: 100 alarms per second (IP Analyzer)
N/A
capability 80k equivalent NEs: 200 alarms per second (IP Analyzer)
Software and
Configuration

PMS performance collection indicators (NCE-FAN)
Collection Mode Equivalent NEs Collection Capability (Maximum Equivalent Records/15 Minutes)
SNMP 2000 20,000
SNMP 6000 60,000
SNMP 15000 150,000
SNMP 30000 150,000
SNMP 50000 150,000
SNMP 150000 1,500,000 (supports only northbound performance text files)
BULK 2000 40,000 (supports only northbound performance text files)
BULK 100000 6,000,000 (supports only northbound performance text files; maximum equivalent records/1 hour)
BULK 150000 12,000,000 (supports only northbound performance text files; maximum equivalent records/1 hour)
Software and
Configuration

System start time(70% of the management <=10 minutes Same as the Indicator column.
System startup and capacity consumed)
shutdown
System shutdown time(70% of the <=10 minutes Same as the Indicator column.
management capacity consumed)
Database restoration time <= 60 minutes Same as the Indicator column.
Current alarms 20k to 500k Same as the Indicator column.
Historical alarms 1 to 24 million Same as the Indicator column.
Storage capacity
Logs (operation logs, system logs, and 1 million; database storage duration: 45 days Same as the Indicator column.
security logs)
Links in the current topology 200k Same as the Indicator column.
Topology capacity Subnets The number of created subnets is unlimited. Each subnet can contain a maximum Same as the Indicator column.
of 500 physical NEs at a maximum of six layers. 200 physical NEs are
recommended.
Alarm response speed In normal circumstances, alarms are displayed on NCE within 10 seconds after Same as the Indicator column.
they are generated on NEs.
Normally,
Alarm handling • 100 alarms per second when NCE manages NEs in all domains
Alarm handling capability • 50 to 400 alarms per second when NCE manages only access NEs
capability
• 100 to 300 alarms per second when NCE manages only transport NEs Same as the Indicator column.
• 100 to 200 alarms per second when NCE manages only IP NEs
In peak hours,
No alarm loss within 15 seconds when 1000 alarms are reported per second.
Note: An indicator marked xx to yy indicates that the indicator under the minimum network scale (3k) is xx and under the maximum network scale
(150k) is yy.
Software and
Configuration

Users 200 to 2000 Same as the Indicator column.
User groups 50 to 500 Same as the Indicator column.
System user management Object sets 100 Same as the Indicator column.
capability Operation sets 255 Same as the Indicator column.
Concurrent NE upgrades Maximum: 60 (for NE upgrade task management) Same as the Indicator column.
Maximum: 300 (for NE upgrade wizard)
GNEs <= 3000 <= 2000
Note: A single instance can manage 500 GNEs.
HWECC and IP over DCC
NEs under each GNE It is advisable to connect no more than 50 NEs to Same as the Indicator column.
networking capacity
a single GNE. The maximum number is 128.
Software and
Configuration
A Set of Infrastructure Supporting Flexible Product Combination and On-

Demand Deployment NCE Products
Unified architecture for management, control, and analysis, in on-demand deployment • NCE-IP, NCE-T, NCE-FAN, NCE-
NCE Super, and NCE Manager can be
released as independent
Portal API
products.
Manager Controller Analyzer • The components are deployed on
Multi-layer and multi-domain
demand.
Multi-layer and multi-domain control
management
• NCE-IP, NCE-T and NCE-FAN
perception
Real-time
Intelligent
In-depth
analysis
forecast
management
management
management
Access
Optical
IP Optical Access
can be deployed together.
IP
control control control
CloudSOP
NCE IP+T scenario Multi-domain multi-layer

IP network MAC scenario Optical network MAC scenario Access/Home Network MAC scenario Manager scenario
scenario
NCE IP +T NCE-IP NCE-T NCE-FAN NCE Manager NCE-Super
Portal API Portal API Portal API Portal API
Portal API Portal API
Manager Controller Analyzer Manager Controller Analyzer Manager Controller Analyzer Manager Controller Analyzer
Manager Controller Analyzer
managem
control
ent
Multi-layer and multi-domain

IP
IP
Perception perception Multi- perception

perception
Access network
perception management
Optical control domain
management
management
management
management
private line
control
network
control
network
Access
Home
Optical
Analysis Analysis
management
management
management
Analysis Analysis Analysis
IP
IP
managem
Access
Optical
Optical
control
Optical
IP
ent
IP+optical
Forecast Forecast Forecast
CloudSOP CloudSOP CloudSOP CloudSOP CloudSOP CloudSOP
Software and
Configuration
NCE Networking
To improve network security and balance traffic on service interfaces, NCE uses different ports and links to
transmit data flows on different service planes. For example, NCE isolates management, service, and inter-
node communication data on different planes.
OSS
Network Plane Description Remarks
DCN The VM web client connects to the
DCN 1
client/northboun
NCE server through the management
Firewall
d network ... Management network network to remotely manage the -
hardware and virtualization
Web client environment.
The NCE web client connects to the 1. The service network is divided into
Client or NCE server and OSS through the three types: single network
Primary site Secondary site northbound client or northbound network to (southbound and northbound
DCN DCN network access the management plane and networks are not isolated, that is, the
management management
network Replication line network
O&M plane. southbound network reuses the
client or northbound network), dual
networks (southbound and
...
Server Server
... northbound networks are isolated
Service but Manager and Controller are not
VM Web client DCN VM Web client network isolated), and multiple networks
Southbound Southbound devices connect to the (southbound and northbound
network Southbound
NCE server through the southbound networks are isolated and Manager
network
network. and Controller are isolated).
2. 2. If the product type is NCE-Super,
the southbound device refers to a
Firewall domain controller. If the product type
is not NCE-Super, the southbound
Fiber device refers to an NE.
Standard network cable Nodes of the server communicate with
Southbound devices
each other through the inter-node
Internal communication
communication network. This network -
network
NMS TController NMS
does not need to be connected to
TController
Primary site Common_S Common_S Secondary external systems.
ervice ervice
site It is a data communication network
DB OMP OMP The IP address of the storage network is
DB between blades and disk arrays. This
automatically set to an IP address in the
Storage network (Applicable network does not need to be
192.168.0.x or 192.168.1.x network
to E9000) connected to external systems. (This
segment during installation. You do not
Internal communication/ network is optional, depending on
replication network need to configure it.
whether a disk array is used.)
The DR solution requires high
Management network
bandwidth. A replication link must be
Client login/ The DR network reuses the inter-node
northbound network DR replication network configured between the primary and
communication network.
Southbound network secondary sites for heartbeat
monitoring and data replication.
Software and
Configuration
E2E Installation and Deployment Process

Onsite hardware
implementation Customer
installation
process requirements
Project
Information Automatic planning Installation and deployment

collection HLD output LLD output Commissioning Acceptance
and design of NCE
EasySuite (unified planning and design, and installation and deployment based on the planning information)
Planning and design Installation and deployment

Service Planning and Service Installation and
Version capability
scenarios design scenarios deployment

NCE-FAN ü Infrastructure layer
NCE-FAN ü Deployment scheme planning
installation and
ü Hardware configuration NCE-T
NCE-T configuration
planning
NCE-IP ü Software installation
ü Virtualization platform
NCE-IP ü Software commissioning
configuration planning
NCE-Super ü Service test
NCE-Super ü VM configuration planning
ü High availability
ü OS configuration planning
ü NCE software planning
Infrastructure installation Service node installation Software system commissioning

Scenario Installation Mode Planning Description
Onsite installation
and deployment
Factory installation Plan commissioning.
Import planning parameters.

Install service nodes.
Create VMs and install the

Set planning parameters.
Start system monitoring.

Configure the TaiShan
and design
Power on the server.

On-
management plane.
Install virtualization
Planning
Install the product
commissioning.
Perform NCE
premises Use EasySuite to plan the installation and Install service nodes.
software.
server.
OS.
delivery Onsite installation deployment scheme and plan all hardware and
Parallel installation
software layers.
...
Install service nodes.
Private Plan only the deployment scheme and NCE
Onsite installation
cloud software. Manual operation
30 min 40 min 20 min 25 min 90 min 5 min 120 min
Automatic operation EasySuite-based one-click installation without manual intervention Wizard-based OMP
commissioning
Ø On-premises factory installation: NCE has been installed on the delivered hardware. Only deployment commissioning is required on the live network. The commissioning duration is less than 2 hours.
Ø On-premises onsite installation: EasySuite is used to install the hardware, VM, OS, and NCE. The total installation duration is less than 4 hours. The commissioning duration after the installation is less than 1 hour.
Ø Private cloud scenario (customers provide the infrastructure layer): After customers install the infrastructure layer and OS, Huawei engineers install NCE using EasySuite. The total duration is less than 2.5 hours.
After the installation, Huawei engineers then commission NCE. The commissioning duration is less than 1 hour.
Software and
Configuration
Deployment Scenarios
n Based on whether Huawei provides E2E support for software and hardware, NCE can be deployed in two modes: on-premises and private cloud.
n On-premises deployment refers to software and hardware integration. Huawei provides the required hardware and software and completes the E2E configuration of the
software and hardware.
NCE Deployment Scenarios NCE deployment

scenarios
Application Application Application
Database Database Database On-premises Private cloud
OS OS OS
Virtualization Virtualization Virtualization Physical machine Private cloud Private cloud (product
Virtualized deployment
deployment (OS+product) only)
Server Server Server
Storage Storage Storage

FC KVM OS (EulerOS or CentOS)
Network Network Network Factory installation Onsite installation VHD-based one- provided by customers
click installation OS installed by customers
Private cloud Private cloud (product
On-premises (OS+product) only) FS OpenStack
Manual installation based
Deployed by Huawei Deployed by customers on .qcow2 files
On-premises:
Huawei engineers configure the hardware, virtualization environment (not required for physical machine deployment), OS, database, and NCE software in an E2E manner. Generally, the
installation takes less than 4 hours.
Private cloud (OS+product):
After customers configure the FusionCompute KVM or EMS centralization environment, Huawei engineers create VMs and install the OS, database, and NCE software. Generally, the installation
takes less than 3 hours.
Private cloud (product only):
After customers configure the virtualization environment, Huawei engineers install the database and NCE software. Generally, the installation takes less than 2.5 hours.
Software and
Configuration
Hardware Deployment Baseline

On-premises scenario – stacking virtualization
Physical
Product Service Scenario Network Scale
Machines
6k equivalent NEs 3
15k equivalent NEs 4
Manager+Controller (MPLS network)+Analyzer (basic analysis)
NCE-IP 30k equivalent NEs 5
80k equivalent NEs (PTN) 12
Manager+Controller+Analyzer(Basic)+NIC 6k equivalent NEs (NIC) 4
6k equivalent NEs, 15k equivalent NEs 3
Manager+Controller 30k equivalent NEs 5
NCE-T 2k equivalent NEs (without Local protection) 1
6k equivalent NEs, 15k equivalent NEs 4
Manager+Controller +Analyzer
Manager+Controller 100k equivalent NEs 7
70k subscribers 1
Home network 100k subscribers 1
NCE-FAN
1 million subscribers 4
FANS 30k equivalent NEs 1
50k subscribers 1
Premium broadband + Home network 500k subscribers 4
1 million subscribers 6
Note: The preceding data is for reference only. For details about the specifications, see Release Notes of the mapping SPC version.
Software and
Configuration

On-premises scenario – stacking virtualization
Product Service Scenario Network Scale Physical Machines

NCE-IP+T (Manager+Controller+Analyzer) < 6k equivalent NEs 4
NCE-IP+T (Manager+Controller+Analyzer) 6k–15k equivalent NEs 5
NCE-IP+T (Manager+Controller+Analyzer) 15k–30k equivalent NEs 7
NCE
NCE-IP+T (Manager+Controller+Analyzer)+FAN (Manager) < 6k equivalent NEs 4
NCE-IP+T (Manager+Controller+Analyzer)+FAN (Manager) 6k–15k equivalent NEs 5
NCE-IP+T (Manager+Controller+Analyzer)+FAN (Manager) 15k–30k equivalent NEs 7
< 15k physical NEs 3
Private line 15k–50k physical NEs 3
50k–100k physical NEs 4
Multi-domain optical private line
NCE-Super < 15k physical NEs 3
Private line + Analyzer
< 6k physical NEs 3
IP+Optical + Private line + Analyzer
IP+Optical+Private line
NCE DR with arbitration (automatic active/standby switchover) - 1
Software and
Configuration

On-premises scenario – physical machine
Number of
Product Service Scenario Network Scale physical
machines
NCE-IP Manager 15k equivalent NEs, 30k equivalent NEs 1
NCE-IP Manager+Controller+Analyzer(Physical) 6k equivalent NEs 1
NCE-T Manager 2k equivalent NEs, 6k equivalent NEs, 15k equivalent NEs, 30k 1
equivalent NEs
Manager+Controller 1k equivalent NEs for NCE Lite, 6k equivalent NEs for enterprise 1
networks, or 30k equivalent NEs
NCE-FAN
ODN Visualizer 1 million subscribers 1
NCE Manager 1k equivalent NEs for NCE Lite, or 2k equivalent NEs, 6k equivalent 1
NEs, 15k equivalent NEs, 30k equivalent NEs
NCE Manager+Analyzer 6k equivalent NEs 1
NCE-Super IP+Optical + Private line 6k physical NEs 1
Software and
Configuration
Private Cloud Deployment Baseline Number of Number of Memor

Product Service Scenario Network Scale Storage Space (TB)
VMs vCPUs y (GB)
6k equivalent NEs 23 224 896 9
NCE-IP Manager + Controller (MPLS network) + Analyzer (basic analysis)
80k equivalent NEs (PTN) 73 904 3616 54
Manager
6k equivalent NEs 18 168 672 6.4
Manager + Controller 30k equivalent NEs 25 296 1184 8.9
NCE-T
150k equivalent NEs 92 1264 5256 47.3
Manager + Controller + Analyzer 30k equivalent NEs 36 448 1792 19.1
150k equivalent NEs 114 1616 6464 85.7
Manager 15k equivalent NEs 2 48 192 0.9
Manager + Controller 100k equivalent NEs 46 696 2784 24.5
150k equivalent NEs 60 872 3488 28.9
NCE-FAN 100k subscribers 6 100 400 8.00
Home network
1 million subscribers 27 420 1680 26.4
50k subscribers 1 12 48 0.3
ODN Visualizer
1 million subscribers 7 88 352 4.2
50k subscribers 6 116 464 8
Premium broadband + Home network 500k subscribers 30 452 1808 24.2
1 million subscribers 40 684 2736 43
SaaS(FANS) < 30k equivalent NEs 6 60 240 3.2
Software and
Configuration
Private Cloud Deployment Baseline

Storag
Numbe
Number of Memor e
Product Service Scenario Network Scale r of
VMs y (GB) Space
vCPUs
(TB)
NCE-IP+T Manager
NCE-IP+T+FAN Manager
NCE
NCE-IP+T (Manager+Controller+Analyzer)
30k equivalent NEs 41 528 2112 21.68
NCE-IP+T (Manager+Controller+Analyzer) + NCE-FAN (Manager)
30k equivalent NEs 41 528 2112 21.68
< 15k physical NEs 8 80 320 3.52
Private line 15k–50k physical NEs 10 108 432 4.59
50k–100k physical NEs 14 160 640 6.64
< 50k physical NEs 10 108 432 4.59
Multi-domain optical private line
50k–100k physical NEs 14 160 640 6.64
NCE-Super < 15k physical NEs 13 160 640 8.5
Private line + Analyzer
15k–50k physical NEs 18 236 944 13.96
< 6k physical NEs 13 128 512 6.35
IP+Optical + Private line + Analyzer
6k–15k physical NEs 13 160 640 8.5
< 50k physical NEs 10 108 432 4.59
IP+Optical + Private line
50k–100k physical NEs 14 160 640 6.64
NCE DR with arbitration (automatic active/standby switchover) - 1 4 16 150G
Software and
Configuration
Panorama of Software and Hardware Combination Scenarios

Application Scenarios Virtualization layer+OS
FC8.3.0+EulerOS 2.10 FC8.3.0+EulerOS 2.10 FS22.1/FS8.0.0/6.5/6.5.
Product Deployment Scenario Hardware Others
(ARM) (X86) 1+EulerOS 2.10(X86)
Recommended
TaiShan 200 (Model [EasySuite:
N/A N/A N/A
2280) (delivered) Infrastructure
layer+OS+product]
E9000 CH121 V5 Supported [EasySuite:

N/A Not supported Not supported
(compatible) Infrastructure layer+OS+product]
On-premises
NCE N/A Supported [EasySuite:
2288X V5(delivered) Not supported Not supported
Manager+Controller+A Infrastructure layer+OS+product]
nalyzer 2288H V5 Supported [EasySuite:
N/A Not supported Not supported
(compatible) Infrastructure layer+OS+product]
Supported [EasySuite:
RS221G1 (delivered) N/A Not supported Not supported
Infrastructure layer+OS+product]
Compatible with SUSE12
SP5 prepared by the
Supported [EasySuite: Supported
Private cloud Applicable to all Not supported customer; SUSE 12 SP5
OS+product, product] [EasySuite: Product]
delivered by Huawei
[EasySuite: Product]
Application Scenarios OS
Deployment
Product Hardware EulerOS2.10(ARM) EulerOS 2.10(X86) SUSE 12SP4/SP5
Scenario
Recommended [EasySuite:
TaiShan 200 (Model 2280) N/A Not supported
Infrastructure layer+OS+product]
On-premises 2288X V5(delivered) N/A Supported Not supported
NCE Manager RS221G1 (delivered) N/A Supported Not supported
2288H V5 (compatible) N/A Supported Not supported
Supported Supported Supported
Private cloud Applicable to all
[EasySuite: Product] [EasySuite: Product] [EasySuite: Product]
Software and
Configuration
Hardware and Software Configuration – TaiShan 200 (Model 2280) On-Premises

Delivery
Usage Scenario Hardware Type Hardware Name Requirements Remarks
CPU: 2 x Kunpeng 920 (2.6 GHz, 64 cores)
RAM: 16 x 32 GB DDR4
Hard disk: 12 x 1200 GB SAS HDD
TaiShan 200 (Model RAID controller card: Avago3508 (2 GB cache)
DR arbitration site Rack server 2280) 512 GB, standard
configuration
delivered; compatible with PMC3152 (2 GB cache)
NIC: delivers 2 x 4 GE electrical ports + 2 x 2 10GE

optical ports; compatible with 2 x 4 GE electrical ports +
2 x 2 10/25GE optical ports, 2 x 4 GE electrical ports +
2 x 4 10/25GE optical ports
TaiShan 200 (Model RAID controller card: Avago3508 (2 GB cache)
NCE Manager: with 2k or 6k equivalent NEs, physical machine (supporting remote
clients)
Rack server 2280) 512 GB, standard
configuration
delivered; compatible with PMC3152 (2 GB cache)
NIC: delivers 2 x 4 GE electrical ports + 2 x 2 10GE

TaiShan 200 (Model
NCE Manager: with 15k equivalent NEs, physical machine (supporting remote clients) Rack server RAID controller card: Avago3508 (2 GB cache)
2280) 512 GB, standard
NCE-T Manager+Controller: with 2k equivalent NEs, physical machine virtualized delivered; compatible with PMC3152 (2 GB cache)
configuration
(supporting remote clients) NIC: delivers 2 x 4 GE electrical ports + 2 x 2 10GE
Software and
Configuration
Hardware and Software Configuration – TaiShan 200 (Model 2280) On-Premises

Delivery
NCE Manager: with 30k equivalent NEs, physical machine (supporting remote
CPU: 2 x Kunpeng 920 (2.6 GHz, 64cores)
clients)
NCE-T Manager+Controller: with 6k equivalent NEs, physical machine virtualized
NCE-T or NCE-IP Manager+Controller+Analyzer: with 2k or 6k equivalent NEs,
RAID controller card: Avago3508 (2 GB cache)
physical machine virtualized
TaiShan 200 (Model delivered; compatible with PMC3152 (2 GB
Stack scenario (non-compact deployment):
Rack server 2280) 512 GB, standard cache)
NCE-T: with 15k, 30k, 50k equivalent NEs; NCE-IP: with 6k, 15k, 30k, 80k
configuration NIC: delivers 2 x 4 GE electrical ports + 2 x 2
equivalent NEs
10GE optical ports; compatible with 2 x 4 GE
NCE-Super: with 6k, 15k, 50k, 100k physical NEs
electrical ports + 2 x 2 10/25GE optical ports, 2
Multi-domain solution: Manager+Analyzer based on physical machines (6K),
x 4 GE electrical ports + 2 x 4 10/25GE optical
virtualized distributed system (6K/15K/30K)
ports
CPU: 2 x Kunpeng 920 (2.6 GHz, 64cores)
NCE-FAN:
1) Manager+Controller (physical machine): with 30k equivalent NEs (remote client
deployment is supported)
Rack server TaiShan 200 (Model delivered; compatible with PMC3152 (2 GB
2) Manager+Controller: with 30k, 100k, and 150k equivalent NEs
2280) 512 GB, advanced cache)
3) ODN Visualizer: with 1 million subscribers
configuration NIC: delivers 2 x 4 GE electrical ports + 2 x 2
4) Home network: with 70k, 100k, or 1 million subscribers
10GE optical ports; compatible with 2 x 4 GE
5) Premium broadband + Home network: with 50k, 500k, and 1 million subscribers
electrical ports + 2 x 2 10/25GE optical ports, 2
6) FANS: with 30k equivalent NEs
x 4 GE electrical ports + 2 x 4 10/25GE optical
ports
GE ports: 24 Software version:
General (on-premises physical machine) Switch S5335
10GE ports: 4 V200R019C10
10GE ports: 48 Software version:
General (on-premises virtual machine) Switch CE6863H
100GE ports: 6 V300R022C00
Space: 47 U
General Cabinet A610-22 Size (W x D x H): 600 mm x 1000 mm x 2200
mm

Software and
Configuration
Hardware and Software Configuration – 2288X V5/RS221G1 On-Premises Delivery

CPU: 2 x Xeon Silver 4210 (2.2GHz,10 Core)
RAM: 4 x 32 GB DDR4
2288X V5
Rack server RAID controller card: Avago3508 (2 GB cache) delivered, compatible with PMC3152 (2 GB
128 GB, standard configuration
cache)
NICs: 4 x 2 GE electrical ports + 2 x 2 10GE optical ports delivered, compatible with 2 x 4 GE
DR arbitration site electrical ports + 2 x 2 10GE/25GE optical ports
CPU: 2 x Xeon Silver 4210 (2.2 GHz, 10 cores)
RAM: 4 x 32 GB DDR4
RS221G1 128 GB, standard
Rack server Hard disks: 8 x 600 GB SAS HDD
configuration
NICs: 4 x 2 GE electrical ports + 2 x 2 10GE optical ports
CPU: 2 x Xeon Gold 6238R (2.2GHz,28 Core)
2288X V5
NCE Manager: with 2k, 6k, 15k, or 30k equivalent NEs, Rack server RAID controller card: Avago3508 (2 GB cache) delivered; compatible with PMC3152 (2 GB
512 GB, standard configuration
physical machine (supporting remote clients) cache)
NCE-T or NCE-IP: with 2k, 6k, 15k, 30k, or 80k NICs: delivers 4 x 2 GE electrical ports + 2 x 2 10GE optical ports; compatible with 2 x 4 GE
equivalent NEs electrical ports + 2 x 2 10/25GE optical ports
NCE-Super: with 15k, 50k, 100k physical Nes CPU: 2 x Xeon Gold 6238R (2.2 GHz, 28 cores)
NCE: with 6k, 15k, or 30k equivalent NEs RAM: 16 x 32 GB DDR4
RS221G1 512 GB, standard
configuration
CPU: 2 x Xeon Gold 6238R (2.2 GHz, 28 cores)
NCE-FAN RAM: 16 x 32 GB DDR4
1) Manager+Controller (physical machine): with 30k 2288X V5 Hard disk: 12 x 1800 GB SAS HDD
equivalent NEs (remote client deployment is supported) Rack server 512 GB, advanced RAID controller card: Avago3508 (2 GB cache) delivered; compatible with PMC3152 (2 GB
2) Manager+Controller: with 30k, 100k, and 150k configuration cache)
equivalent NEs NIC: delivers 4 x 2 GE electrical ports + 2 x 2 10GE optical ports; compatible with 2 x 4 GE
3) ODN Visualizer: with 1 million subscribers electrical ports + 2 x 2 10/25GE optical ports
4) Home network: with 70k, 100k, or 1 million
CPU: 2 x Xeon Gold 6238R (2.2 GHz, 28 cores)
subscribers
5) Premium broadband + Home network: with 50k, RS221G1 512 GB, advanced
500k, and 1 million subscribers configuration
6) FANS: with 30k equivalent NEs
Software and
Configuration
Hardware and Software Configuration – 2288X V5/RS221G1 On-Premises Delivery

GE ports: 24 Software version:

General (on-premises physical machine) Switch S5335
10GE ports: 4 V200R019C10

FM6865
100GE ports: 8 V200R019C10
General (on-premises virtual machine) Switch
CE6863H
100GE ports: 6 V300R021C10
Space: 47 U
General Cabinet A610-22
Size (W x D x H): 600 mm x 1000 mm x 2200 mm
General Server TaiShan server 512 GB advanced configuration
General Server 2288X V5 server 512 GB advanced configuration
General Server RS221G1 server 512 GB advanced configuration
Software and
Configuration
Hardware and Software Configuration – E9000 On-Premises

Delivery
Hardware Type Hardware Name Requirements Remarks
Management board: 2 x MM910
Blade chassis E9000 chassis Switch board: 4 x CX320 (8 x 10GE downstream port)
Power supply: 6 x 2000 W (AC)
CPU: 2 x Xeon Gold 6138T (2.0 GHz, 20-core)

Blade E9000 CH121 V5 Hard disk: 2 x 1200 GB SAS (10K RPM)
NIC: 2 x MZ312 (4 x 10GE)
RAID controller card: LSI3108 (2 GB cache)
Controller unit: 2 x SAS controller unit (128 GB cache)

OceanStor 5500 V5 controller
Disk array Hard disk: 25 x 2.4 TB SAS HD hard disk (10000 RPM) Disk array in common scenarios
enclosure
Interface: 8 x 10GE ETH (SFP+)
OceanStor 5500 V5 disk Controller unit: None Expand the disk array in the big data
Disk array
enclosure Hard disk: 24 x 10 TB NLSAS HD hard disk (7200 RPM) analysis scenario.
Switch S5320 10/100/1000Base-T Ethernet ports: 2410GE SFP+ ports:

4
Space: 46 U
Cabinet N610E-22
Size (W x D x H): 600 mm x 1000 mm x 1200 mm
Software and
Configuration
Software and Hardware Configuration – U2000 Hardware Reuse
Strategies:
1. Do not reuse hardware in general.
2. If a site needs to reuse hardware, contact product marketing for

feasibility evaluation.
Software and
Configuration
Software and Hardware Configuration – Compatible U2000 Hardware

Hardware Type Hardware Name Requirements Note
CPU: 4 x E7-4830 V4 (14-core) or 4 x E7-8867 V3 (16-core)
or 2 x E7-8867 V4 (18-core) or 4 x E7-8860 V4 (18-core)
RAM: 192 GB, 256 GB, or 512 GB DDR4 and above To install NCE, supplement hardware resources or add hardware servers
E9000 blade
CH242 V3 DDR4 Hard disk: 2 x 600 GB, 2 x 800 GB, 4 x 1200 GB, or 8 x 600 GB based on the CPU and memory resources required in the deployment
SAS HD hard disk scenario.
NIC: 2 x MZ312 (4 x 10GE) or 1 x MZ512 (4 x 10GE)
In the reuse scenario, the OceanStor 5500 V3 disk array is supported. The
Controller card: 2 x SAS controller unit (48 GB cache) number of hard disks is not limited to the specifications described in the table.
Disk array OceanStor 5500 V3 Hard disk: 24 x 900 GB SAS HD hard disk To install NCE, you need to supplement the hard disk or replace the hard disk
Interface: 2 x 4 10GE ETH (SmartIO card SFP+) with a larger one based on the storage size required in the deployment
scenario.
CPU: 2 x E5-2620 V3 (6-core)

To install NCE, supplement hardware resources or add hardware servers
RAM: 64 GB DDR4 (4 x 16 GB)
Rack server RH2288H V3 based on the CPU and memory resources required in the deployment
Hard disk: 8 x 600 GB SAS HD hard disk
scenario.
CPU: 4 x E7-4820 V4 (10-core)
To install NCE, supplement hardware resources or add hardware servers
RAM: 64 GB DDR4
Rack server RH5885H V3 DDR4 based on the CPU and memory resources required in the deployment
Hard disk: 8 x 600 GB SAS HD hard disk
scenario.
Software and
Configuration
Software and Hardware Configuration – Compatible Software
Software Type Version Note

FusionCompute 8.3.0 applies to onsite installation and factory installation.
FusionCompute 8.3.0 Delivered, used in TaiShan on-premises delivery scenarios.
Virtualization software
Delivered, used in 2288X V5/RS221G1 on-premises delivery scenarios.
FusionSphere OpenStack 22.1.0 Mapping (not delivered), used only in the NMS centralization scenario.
Delivered, used in TaiShan and 2288X V5 on-premises scenarios.
OS EulerOS V2.10
Delivered, used in 2288X V5 on-premises delivery scenarios.
Gauss100 OLTP 1.5.1 Used by Manager/Controller to store Manager data.
Database
Druid 0.21.1 Used by Analyzer to store performance data.
Windows 10 32bit/64bit
Client OS
Google Chrome 90 or later (32-bit/64-bit)
Firefox 89 or later
Client browser Microsoft Edge 90 or later
Firefox 78 ESR or later
Software and
Configuration
Migrating Data from NCE Manager to NCE Manager+Controller+Analyzer

Restrictions:
• Single-server reuse is risky and therefore not supported. Source: DR system; all hardware reused; target: DR system
• Before data migration, a source system needs to be upgraded to NCE V100R022C00.
After data migration, the destination system remains NCE V100R022C00.
Source Systems Destination Systems ③ Migrate data.
Monitoring continues but ⑤ Establish a DR relationship
Single Single services are not NCE at the and perform a switchover.
Server/ Server Server/T provisioned. primary site Monitoring is interrupted for 15
Scenario Two- Memory Scenario wo Server Change Manager at the minutes.
Node Size Node primary site ④ Install the primary site on the
Cluster Cluster existing or new server.
Services are not affected.
192G Added X
NCE NCE at the
NCE Single 384G Manager+ Single Added X ① Remove the DR Manager at the
secondary site
Manager server Controller+ server relationship. secondary site
② Install the secondary site on the
512G Analyzer Added X Services are not existing or new server.
affected. Services are not affected.
192G Added (X*2)+A
NCE
384G Two- Added (X*2)+A
NCE Single Manager+ Source NCE DR system
Manager server Controller+
Node Target NCE DR system
Cluster
512G Analyzer Added (X*2-1)+A
192G Added X
NEs
NCE
Two- 384G Added X
NCE Manager+ Single
Node
Manager Controller+ server Data migration of NCE Manager (either physical machines or private clouds) depends on NMS nodes only.
Cluster
512G Analyzer Added X-1
192G Added (X*2)+A

NCE NMSServer NMSServer Web server
Two- 384G Two- Added (X*2)+A
NCE Manager+ OS OS
Node Node OS
Manager Controller+
Cluster Cluster
512G Analyzer Added (X*2-2)+A Physical machine Private cloud
X indicates the number of destination servers A indicates the number of arbitration servers, which can be 0 or 1. A source server that fails be reused to install
(single-server deployment). NCE Manager+Controller+Analyzer can be used as an arbitration server.
Note: In principle, reusing source servers is recommended. For details about deployment scenarios and specifications, see the Migration Guide for related NCE versions.
Software and
Configuration
Migrating Data from NCE Manager+Controller+Analyzer to NCE Manager+Controller+Analyzer

Restrictions:
• The migration applies to the centralized network management scenario in which the source system is
deployed in on-premises mode and the target system is deployed on FusionSphere private cloud.
• The versions and deployment scenarios of the source and target systems must be the same.
• For the migration scenarios, see Migration Guide. NCE-T does not support this migration solution.
Implementation Principles:
• Back up product data on the management plane of the source system and remotely restore the data on the
management plane of the target system.
Source: DR system; all hardware reused; target: DR system
Step Migrate Manager+Controller Data
③ Migrate data.
Monitoring continues but
1 Back up product data on the management plane of the source system.
services are not provisioned.
2 Transfer the backup files to the target system. Target primary site
Source primary site ⑥ Establish a DR relationship
3 Restore product data on the management plane of the target system. ⑤ Install the primary site on the and perform a switchover.
existing or new server. Monitoring is interrupted for 15
4 Perform other necessary operations on the target system. Services are not affected. minutes.
Source secondary site Target secondary site
① Remove the DR
relationship. ② Install the secondary site on the
Step Migrate Analyzer Data Services are not affected. existing or new server.
Services are not affected.
1 Connect the customer's third-party SFTP server to the source system.
2 Dump performance data on the O&M plane of the source system to the SFTP server. ④ Switch services to
the secondary site.
3 Connect the SFTP server to the target system. Source NCE
NEs Target NCE
4 Restore performance data on the O&M plane of the target system.
5 Perform other necessary operations on the target system.
Note: For details about the scenarios and specifications, see the migration guide released with the product.
Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.
40Page
Software and
Configuration
Capacity Expansion Scenarios

n In capacity expansion, the management scale of NCE or its certain components is increased by adding service instances or adding resources to service instances.
n In incremental deployment (or feature expansion), new features are deployed for NCE to provide new functions. The deployed features remain unchanged.
Management plane Management plane

NCE capacity expansion
Software System DR ... Software System ...

DR
management monitoring management monitoring
and deployment
Application plane Application plane

VM1 VM2 VM3 VM4 VM1 VM2 VM3 VM4 VM5
DB DB APP1 App2 DB DB App1 APP2 APP2
APP3
Management Management Management Management Management Management Management Management Management

plane agent plane agent plane agent plane agent plane agent plane agent plane agent plane agent plane agent
Increase running resources of Increase the number of app2

Incrementally deploy app3.
the app1 instance. instances.
On-premises:
Huawei engineers configure new servers, virtualization environment (not required for physical machines), and OS, and expand the NCE capacity in E2E mode. The expansion takes less than 4 hours.
Private cloud (OS+product):
After customers configure FusionCompute KVM and the EMS centralization environment, Huawei engineers create VMs, install the OS, and expand the NCE capacity. The expansion takes less than
3 hours.
Private cloud (product only):
After customers configure the virtualization environment, Huawei engineers expand the NCE capacity. The expansion takes less than 2.5 hours.
Restrictions:
Currently, the network capacity can be expanded only to a maximum of 30k equivalent NEs.
Software and
Configuration
Capacity Expansion and Deployment Baseline

Source Scenario
Product/Solution Expansion Path
Service Scenario Network scale
NCE-IP Manager+Controller (MPLS network)+Analyzer (basic analysis) 6k/15k 6k -> 15k -> 30k (NIC)
Manager+Controller 6k/15k 6k->15k, 15k->30k, 6k-> 30k
NCE-T
Manager+Controller+Analyzer 6k/15k 6k->15k, 15k->30k
Manager+Controller 100k 100k->150k
NCE-FAN Home network 1/2/3/4 million subscribers 1 million->2 million->3 million->4 million->5 million
Premium broadband + Home network 0.5/1/2 million subscribers 0.5 million->1 million->2 million->3 million
Basic feature expansion of the Analyzer:

NCE-IP Manager+Controller+Analyzer 6k/15k/30k 1. 600k monitoring instances per blade; upper limit: IP RAN: 6k(450k)/15k(900k)/30k(1.5m), PTN 30k/80K (1m)
2. Only one blade can be added.
iFIT feature expansion of the Analyzer:

1. IPRAN 8k base stations (per blade)
NCE-IP Manager+Controller+Analyzer 6k/15k/30k/80k
2. PTN 10k base stations (per blade)
3. Expansion upper limit: 6k/15k (3 blades), 30k (3 blades) , 80k (5 blades)
iFIT feature expansion of the Analyzer:
1. 8k base stations (per blade)
NCE-IP Manager+Controller+Analyzer+Flow collector 6k
2. A maximum of three blades can be added.
3. Flow collection does not support capacity expansion.
PMS expansion:
1. Expansion upper limit: 6k/15k: 1m
NCE-IP Manager+Controller+Analyzer 6k/15k/30k/80k
2. 30k/80k: 2.4m
NCE Analyzer 3. Only one blade can be added.
PMS expansion:
NCE-IP (private cloud) Manager+Controller+Analyzer 30k 1. Expansion upper limit: 2.4m
PMS expansion:
NCE-IP Manager+Controller+Analyzer 6k 1. Expansion upper limit: 1m
PMS expansion:1. Expansion upper limit: 1m or 2.4m
NCE-T Manager or Manager+Controller 15k/50k
PMS expansion:1. Expansion upper limit: 1m
NCE-IP+Super+T Manager+Controller+Analyzer 15k
PMS expansion:
NCE-FAN Manager+Controller 30k 1. Expansion upper limit: 2.4 million
Note: The data provided on this page is for reference only. For the detailed specifications, refer to Project Capacity Expansion Baseline of the required version.
Software and
Configuration
Capacity Expansion and Deployment Baseline

Source Scenario
Product/Solution Incremental Deployment Scenario
Service Scenario Network scale
Manager+Controller 30k Adding Extend Advanced Security Service
Home network 1 million subscribers Adding Extend Advanced Security Service
Premium broadband + Home network 1 million subscribers Adding Extend Advanced Security Service
Premium broadband + Home network 50k subscribers Adding Premium Broadband User Experience
NCE-FAN
Premium broadband + Home network 500k subscribers Adding Premium Broadband User Experience
Premium broadband + Home network 1 million subscribers Adding Premium Broadband User Experience
Manager+Controller 6k/15k/30k/50k/150k Manager+Controller -> Manager+Controller+Analyzer
Manager+Controller 6k/15k/30k/50k/150k Adding Intelligent Incident Management
NCE-T
Manager+Controller+Analyzer 6k/15k/30k/50k/150k Adding Intelligent Incident Management
Manager+Controller 6k/15k/30k Adding Situational Awareness
Manager+Controller (MPLS
NCE-IP 30k Extend Advanced Security Service
network)+Analyzer (basic analysis)
Private line + Analyzer 50k Extend Advanced Security Service
NCE-Super Private line 15K Private line > Private line + Analyzer
Private line 50K Private line > Private line + Analyzer
NCE-IP+T Manager+Controller+Analyzer -> NCE-IP+T
Manager+Controller+Analyzer 30k
Manager+Controller+Analyzer+Situational Awareness
NCE Multi-Domain
Manager+Controller+Analyzer > Manager+Controller+Analyzer + Intelligent
Manager+Controller+Analyzer 6k/15k/30k
Incident Management
Software and
Configuration
HA Capability: Local Protection

Protection TaiShan/2288X + FC E9000 + Disk Array +FC
Component
Layer
Management plane
Protection: microservice-level Protection: microservice-level
management
Manager
Indicators: RPO = 0s, RTO ≤ 3 min Indicators: RPO = 0s, RTO ≤ 3 min
Network
Network
Network
analysis
control
Protection: primary/secondary Protection: primary/secondary
Controller
Indicators: RPO = 0s, RTO ≤ 60s Indicators: RPO = 0s, RTO ≤ 60s
Application
layer Protection: microservice-level Protection: microservice-level
... Analyzer Indicators: RPO = 0s (configuration file), Indicators: RPO = 0s (configuration file),
RTO ≤ 3 min, RPO=45min (big data) RTO ≤ 3 min, RPO=45min (big data)
Protection: Cluster protection Protection: Cluster protection
OS/DB OS/DB OS/DB OS/DB NCE-Super
VM 1 VM 2 VM 3 VM n Protection: Cluster protection Protection: Cluster protection
Basic platform CloudSOP
FusionCompute
Protection: master/slave Protection: master/slave
Database Database
RPO = 60s, RTO ≤ 60s RPO = 60s, RTO ≤ 60s
1: N blade cluster protection, automatic
Virtualization
Private Cloud layer
FusionCompute NA recovery
Indicators: RPO = 0s, RTO ≤ 15 min
E9000 chassis: management module 1+1,
TaiShan: management module 1+1, power
E9000 chassis power supply 1+1, switch board 1+1
Local protection: microservice-level Blade server supply 1+1, switch board 1+1, NIC 1+1,
CH121 V5 blade Blade server: Mezz card 1+1, hard disk
hard disk RAID 1/RAID 10
DR: full-scenario application DR; switchover for RAID 1
all components on a site Hard disk RAID 10, hot-spare policy, disk
Disk array 5500V5 NA
array controller 1+1, power supply 1+1
Recovery point objective (RPO) refers to the data loss duration. Recovery time objective (RTO) refers to the service interruption duration.
Software and
HA Capability: DR
Configuration
1. Implemented by a third-party site

2. Implemented by NE (for NCE-T)
NCE
The DRMgr service is Arbitration The arbitration mechanism is introduced
DRMgr developed by Huawei. to improve decision-making efficiency and
Customers do not need to avoid dual-active states.
Replication purchase third-party HA Status detection and
management management software. automatic switchover
Monitoring Automatic or manual

management switchover
DR RTO <= 15 minutes DR Secondary site
Primary site
Switchover RPO<=60 seconds
management DRMgr Heartbeat DRMgr
NCE DB
Service 1 Service 1
Linux DB
Service 2 DB Service 2
Asynchronous replication RPO <=
.. 60 seconds (service data of ..
. .
VM Manager and Controller)
File File
Service n Service n
Network delay < 50ms, package loss rate < 1%
Hypervisor Services Data Data Services
* It is recommended that a redundant private line connection be
replicated, and the switchover time is less than 1s.
DR based on database
Management Scale (Manager + Controller + Analyzer) 6000 15,000 30,000
replication is located at the
application layer. It is Minimum Bandwidth Requirements Between the Primary
decoupled from the and Secondary Sites 60 Mbit/s 100 Mbit/s 200 Mbit/s
infrastructure layer and (Excluding Analysis Data)
does not depend on
Management Scale (NCE Manager) 2000 6000 15,000 30,000
specific hardware or
virtualization platforms. Minimum Bandwidth Requirements Between the Primary
and Secondary Sites 8 Mbit/s 12 Mbit/s 30 Mbit/s 60 Mbit/s
(with the performance data collection function disabled)
Summary
This chapter describes:

» NCE positioning and service scope
» NCE hardware and software architecture
» NCE installation and deployment
» NCE hardware and software configuration
Contents
n System Overview
n Questions and Suggestions
Q&A Time
Thank you
www.huawei.com
Copyright © 2023 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and
operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments
to differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for reference purpose
only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice.

Imaster NCE V100R022C10SPC100 System Overview (System Overview) 01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Imaster NCE V100R022C10SPC100 System Overview (System Overview) 01

Uploaded by

Copyright:

Available Formats

iMaster NCE V100R022C10SPC100

System Overview (System Overview)

Upon completion of this course, you will be able to:

Date Version Description Author

Pan Jiyu, Xie Qing, Gu Xiaogang, Zheng

n Questions and Suggestions

network management, service control, and network

Portal NBI/Open API Proxy

automated, then self-adapting, and finally autonomous.

used to build an intelligent network that can automatically

NCE p Netstar: Visualization and forecast of optical network resources

Differences Between NCE and U2000/AC/uTraffic

NCE Architecture (L0)

⑤ Intelligent engine: Implements AI online training and

Configure Context ⑥ OpenAPI: Provides various OpenAPIs and open and

Cloud Platform Architecture (L1)

Automation Engine Architecture and Functions (L1)

CLI NetConf PCEP BGP LS OSPF SNMP

Network management Network control Network analysis

Managed Fabric Metro Converged

Interfaces Between NCE and Other Systems

Cloud management system

NCE Security Precautions

Performance Specifications (1)

Item Sub-item Indicator Manager Indicator

Note: N indicates the number of equivalent NEs.

Performance Specifications (2)

Note: N indicates the number of equivalent NEs.

Performance Specifications (3)

Note: N indicates the number of equivalent NEs.

Performance Specifications (4)

Performance Specifications (5)

Performance Specifications (6)

Users 200 to 2000 Same as the Indicator column.

User groups 50 to 500 Same as the Indicator column.

A Set of Infrastructure Supporting Flexible Product Combination and On-

NCE IP+T scenario Multi-domain multi-layer

Multi-layer and multi-domain

Perception perception Multi- perception

CloudSOP CloudSOP CloudSOP CloudSOP CloudSOP CloudSOP

E2E Installation and Deployment Process

Information Automatic planning Installation and deployment

Planning and design Installation and deployment

scenarios design scenarios deployment

Infrastructure installation Service node installation Software system commissioning

Import planning parameters.

Create VMs and install the

Start system monitoring.

Power on the server.

Install the product

NCE Deployment Scenarios NCE deployment

Application Application Application

Database Database Database On-premises Private cloud

Storage Storage Storage

Hardware Deployment Baseline

Hardware Deployment Baseline

Product Service Scenario Network Scale Physical Machines

Hardware Deployment Baseline

NCE-IP Manager+Controller+Analyzer(Physical) 6k equivalent NEs 1

NCE Manager+Analyzer 6k equivalent NEs 1

NCE-Super IP+Optical + Private line 6k physical NEs 1

Private Cloud Deployment Baseline Number of Number of Memor

Private Cloud Deployment Baseline