NCE-T HCIA Lecture

Introduction to NCE-T
Foreword
⚫ The chapter describes the positioning, features, architecture, and functions

of Network Cloud Engine (NCE), helping you comprehensively understand
the product.
2 Huawei Confidential
Objectives
⚫ On completion of this course, you will be able to:

 Understand the basic knowledge of NCE-T, such as product positioning,
architecture, and deployment solutions.
 Describe the functions of NCE-T, such as network management and optical
service provisioning.
Contents
1. System Architecture of NCE-T

◼ Product Positioning
▫ Solution Architecture
▫ Deployment Solution
2. Basic Functions of NCE-T
3. Key Features of NCE-T
Product Positioning
⚫ Network Cloud Engine (NCE) is an innovative network cloudification engine
provided by Huawei. Positioned as the brain of a cloud-based network, NCE
integrates functions such as network management, service control, and network
analysis. It is a core enabling system for network resource pooling, network
connection automation and self-optimization, and O&M automation.
• NCE Lite is a lightweight version of NCE, which is oriented to enterprises and

provides a low-cost miniaturized solution.
Features
Unified Management and Control Supporting Smooth Cloud Platform Supporting Flexible Deployment
Network Evolution
◼ Uses a unified cloud platform, user portal, and API
◼ Integrates traditional NMS and SDN controller gateway; achieves unified installation, deployment, and
functions. upgrade; and provides consistent data models throughout
◼ Achieves unified management and control of SDN the lifecycle, greatly simplifying O&M.
and non-SDN networks, leverages SDN network ◼ Adopts a cloud-native microservice architecture, and
automation, maximizes the value of live networks, achieves user scenario-specific on-demand deployment.
and reduces technical difficulties and risks of
network evolution.
Features
Open Interfaces Implementing Agile DevOps Network Analysis and Proactive Maintenance Based on
Big Data
◼ Provides open northbound interfaces (NBIs) and ◼ Collects network-wide data, and uses the big data
southbound interfaces (SBIs). The NBIs connect to platform to perform panoramic and in-depth analysis on
external systems through RESTful APIs. the quality and traffic data of the entire network,
◼ Provides a DevOps-based tool platform to quickly achieving intelligent analysis and proactive maintenance.
customize innovative services based on flexible ◼ Continuously verifies network design and configuration to
business scenarios and network technologies. ensure that the network accurately implements the users'
intention and achieves stable operation.
• NCE is a network lifecycle automation platform that integrates management,

control, and analysis. It focuses on service automation, O&M adaptation, and
network autonomy to support carriers' network cloudification and digital
operation transformation.
Highlights of NCE-T
⚫ Network visualization: Unified performance data collection and inventory management enable NCE to detect
network status in real time and support multi-dimensional data visualization and presentation in reports.
⚫ Automatic deployment: NCE supports automatic deployment of CPE NEs and pre-provisioning of service trails.
Therefore, private line services can be provisioned quickly, like home broadband services. The services are available
30 minutes later (most quickly) after CPEs are installed onsite, greatly improving user experience in private lines.
⚫ Automated service provisioning: NCE provides the optical-connection bandwidth on demand (BoD) function.
Therefore, customers can perform agile provisioning of private line services, adjust bandwidth in real time, specify
the bandwidth calendar, multiple Service Level Agreements (SLAs), and application latency policies.
⚫ Intelligent proactive O&M: NCE supports optical network survivability analysis, and allows you to simulate network
faults, analyze service robustness, identify network bottlenecks, and provide guidance on precise network capacity
expansion.
⚫ Scenario-specific interfaces: Based on the three-layer model (infrastructure layer, services layer, and applications
layer), NBIs provide multiple atomic services and a scenario-driven programmable platform, support customized
development of scenario-specific workflows, and implement automatic or semi-automatic intent design, execution,
and optimization processes.
• NCE-T is the core enabler of Huawei's Smart Optical Network. Smart Optical
Network is a transport network solution based on the intent-driven network
(IDN) architecture. It is designed to implement digital optical networks, simplified
and intelligent O&M, optimal user experience, and ultimately realize network
autonomy (autonomous driving of optical networks).
NCE GUI Types
⚫ NCE provides two independent working interfaces on different planes: management plane and O&M
plane. You can log in to each plane through a specific IP address and port number. This helps you focus
on your own task scenarios to ensure efficient system management and network O&M.
Plane Intended User Group Functions Login Mode

Centrally manages NCE resources, applications, and databases to implement
− Installation and
functions such as installation and deployment, system monitoring, system https://IP address of the
Management commissioning
maintenance (user and password management, data backup and restoration, and management
plane engineers
certificate and key management), and system troubleshooting (system health plane:31945
− System administrators
check, fault data collection, fault demarcation and locating, and disaster recovery).
Provides the following features and functions for transport, IP, access, and multi-
layer network planning/deployment, service design/provisioning/analysis, network
− System security monitoring/analysis/adjustment/maintenance/troubleshooting: system settings
administrators (such as license management, interconnection with the southbound systems), https://IP address of the
O&M plane
− Network O&M security management (user management, rights management, security policy, and O&M plane:31943
engineers log management), alarm management, network management, premiumWDM
private line, key service assurance, optical network survivability analysis,OTN
virtual private network, what-if analysis, and network analysis and optimization.
NCE GUI Types (Management Plane)
Home page of the management plane
Logging in to the
1. In the address box of the web browser, enter https://IP address of the management plane:31945 and press Enter.
management
Note: The IP address of the management plane refers to the client login IP address configured on the OMP node. If the
plane
OMP node is deployed in a cluster, the IP address is set to the floating IP address of the cluster.
2. When you log in to the system in local mode, enter the username admin and its password. The initial password for the
admin user is C hangeme_123.
• To ensure system security, change your password upon the first login, update it
periodically, and keep it secure. If you forget the password for the admin user,
you can only reinstall the management plane to restore the initial password.
• For security purposes, do not allow your browser to keep the password.
NCE GUI Types (O&M Plane)
Home page of the O&M plane
the O&M plane
1. In the address box of the web browser, enter https://IP address of the O&M plane:31943 and press Enter.
Logging in to
Note: The IP address of the O&M plane refers to the client login IP address configured on the service node. If the service node is deployed in
a cluster, the IP address is set to the floating IP address of the cluster.
2. NCE provides the default user admin. The initial password for this user is C hangeme_123.
• The GUI screenshots of NCE Manager are used as examples.
• If you have changed the initial password after login, keep the new password
secure. If you forget the password for the admin user, you can reset the password
only by reinstalling the O&M plane.
• For security purposes, do not allow your browser to keep the password.
Contents

▫ Product Positioning
◼ Solution Architecture
▫ Deployment Solution
Architecture of the NCE-enabled Cloud Network Solution
IT/OSS/Application
Multi-tenant Multi-service Multi-industry
Open API catalog & gateway
Scenario-specific apps
Intent engine (innovated planning)
Manager Controller Analyzer
Southbound framework of Multi-vendor device

multi-vendor devices data collection
Cloud platform
Cross-layer Cross-domain Multi-vendor
Network infrastructure
• IT/OSS/Application layer
▫ The IT/OSS/application layer is a platform for carriers to implement digital
operation transformation. In addition to traditional OSSs and BSSs, the
IT/OSS/application layer also includes service orchestrators, policy generators
based on big data analysis and artificial intelligence, and e-commerce portals
that support self-service. The IT/OSS/application layer provides functions such
as network infrastructure resource presentation, service path presentation, and
service policy management to implement end-to-end operation of the entire
network. Carriers provide application services to customers through this layer,
including traditional services such as broadband, video, and B2B enterprise
private line services and emerging services such as cloud computing and
vertical industry IoT. This layer provides ways for carriers to monetize their
network infrastructure.
• NCE provides centralized management, control, and analysis for network
infrastructure.
▫ It also enables resource cloudification, full-lifecycle automation, and
intelligent closed-loop management driven by data analysis. Moreover, it
provides open APIs and IT integration to help carries accelerate service
innovation and realize e-commerce operation.
Logical Architecture of NCE-T
Tenant portal Orchestrator/OSS Application AI training center
Apps Optical Service Optical Network Key Service Private Line SLA
... Unified portal
Provisioning Health Assurance Assurance Analysis
Open APIs ACTN/RESTful SNMP XML CORBA FTP
Manager & Controller Analyzer
Service provisioning Service profile Latency map Centralized policy

SLA analysis
Service Bandwidth
NE configuration CPE PnP
maintenance adjustment
Health prediction
Network Resource
OD/FD Resource prediction
maintenance visualization
Performance
NE upgrade Fault simulation
management
Unified cloud platform Basic services Public services Product engineering
SBIs SNMP QX PCEP OSPF
• Based on the cloud platform, NCE implements three logical modules (network
management, network control, and network analysis) and various application
scenarios as services and components to achieve flexible modular deployment
based on customer requirements.
Scenario-specific Apps Supported by NCE-T
App Name Function Description
System Settings provides functions such as license management, broadcast message, remote notification, and southbound
System Settings
system interconnection.
Security Management involves user management and security policies. Security Management prevents unauthorized users
Security Management
from accessing the system and ensures system data security.
Alarm Monitor enables you to monitor and manage alarms or events reported by the system or managed objects. Alarm
Alarm Monitor Monitor also provides a variety of monitoring and processing rules to meet requirements in different scenarios. In this way,
network faults can be efficiently monitored, located, and rectified.
Network Management enables users to perform basic management, such as security, topology, alarm, performance, and
Network Management
inventory management on networks and NEs.
Optical Service Provisioning is a basic feature for implementing cloud transport networks. It mainly applies to business-to-
business (B2B) scenarios, such as government and enterprise private lines and data center interconnections. Its functions
Optical Service Provisioning
include service profiles, agile provisioning, scheduled reservation, BoD, latency management, service visualization, routing
policies, and route computation.
Optical Network Survivability With this function, users can clearly understand network resource bottlenecks, identify risks in advance, and proactively take
Analysis O&M measures to ensure service reliability and avoid SLA violation, helping build time-saving network O&M capabilities.
With this function, carriers can provide virtual private networks for important enterprise customers. Without the need to
construct their own physical private networks, important enterprise customers can obtain high security achieved by hard pipe
OVPN
isolation and sustainable service development achieved by OVPN resource reservation. In addition, carriers can use the OVPN
function to flexibly sell link bandwidths, improving the resource utilization of carriers' networks.
Key Service Assurance Key Service Assurance enables users to focus on key services.
Optical Network Health Optical Network Health Assurance provides perspective of network resources, displays resource information in multiple
Assurance dimensions such as services, wavelengths, capacity, and sites, and helps discover network resource bottlenecks.
Contents

▫ Product Positioning
▫ Solution Architecture
◼ Deployment Solution
Deployment Solution
⚫ Based on whether Huawei provides E2E support for software and hardware, NCE supports
three deployment modes:
 In on-premises deployment scenarios, Huawei provides both software and hardware. In other
words, Huawei delivers the hardware and software required for NCE deployment and completes
E2E software and hardware configuration.
 Generally, factory installation has been completed for NCE before delivery.
 Deployment on private clouds means that customers prepare the bottom-layer deployment
environment according to the NCE configuration requirements and Huawei installs the OS and NCE
in this environment.
 Deployment using EasySuite: In the on-premises and private cloud scenarios where factory
installation is not performed, EasySuite is used to install and deploy NCE.
On-Premises Deployment
NCE networking (physical machine, single site) NCE networking (physical machine, DR system)
• NCE Manager can be installed and deployed on physical machines and VMs. This
document uses physical machines as an example.
• Based on different system protection expectations, deployment on physical
machines can be divided into two modes: single site and disaster recovery (DR).
▫ Single site: A complete set of NCE is deployed at a single site to protect the
system.
▫ DR system: Two identical sets of NCE are deployed at two sites to form a
DR system. In addition to the internal protection of a single site, the two
sets of NCE protect each other.
Deployment on Private Clouds
NCE networking (single site) NCE networking (DR system)
• Deployment on private clouds means that customers prepare the bottom-layer

deployment environment according to the NCE configuration requirements and
Huawei installs the OS and NCE in this environment.
• Based on different system protection expectations, deployment on physical

machines can be divided into two modes: single site and DR.
▫ Single site: A complete set of NCE is deployed at a single site to protect the
system.
▫ DR system: Two identical sets of NCE are deployed at two sites to form a
DR system. In addition to the internal protection of a single site, the two
sets of NCE protect each other.
Deployment Using EasySuite
Deployment Solution One-Click Installation of EasySuite
1. Configure hardware, including configuring RAID and hardware alarm reporting parameters.
On-premises deployment
2. Install and configure the OS.
on physical machines
3. Install the NCE software (including the database).
Deployment on private 1. (Optional) Install VMs, including installing and configuring the OS.
clouds 2. Install the NCE software (including the database).
• In the on-premises and private cloud scenarios where factory installation is not
performed, EasySuite is used to install and deploy NCE.
• EasySuite is a green web-based engineering tool provided by Huawei. It covers
complex engineering scenarios such as planning, installation, and migration.
Using EasySuite to install NCE greatly simplifies installation and deployment
operations and improves efficiency.
Software Deployment Modes
Server
Business services Browser
Database Browser
On-premises NCE DCN
Windows 10/
OS
deployment on physical Window 7
machines Hardware resources
Server
Business services
Browser
Database
Browser
NCE deployment on OS
DCN
Windows 10/
private clouds VM
Window 7
Private cloud
platform
• NCE uses the browser/server (B/S) architecture for software deployment during
deployment on physical machines or private clouds. Then, users can easily access
NCE through a browser without installing traditional clients.
Server Hardware Configurations (On-Premises)
Hardware Type Model Configuration Requirement
⚫ CPUs: 2 x Kunpeng 920 (2.6 GHz, 48 cores)
⚫
Memory:12 x 32 GB DDR4
384 GB standard- TaiShan 200 ⚫
Hard disks: 12 x 1200 GB HDD
configuration server (model 2280) ⚫ RAID card: Avago3508 (2 GB cache)
⚫
NICs: 2 x 4GE electrical ports + 2 x 4 10GE/25GE optical ports
⚫
CPUs: 2 x Kunpeng 920 (2.6 GHz, 64 cores)
⚫ Memory: 16 x 32 GB DDR4
512 GB standard- TaiShan 200 ⚫ Hard disks: 12 x 1200 GB HDD
configuration server (model 2280) ⚫
RAID card: Avago3508 (2 GB cache)
⚫
NICs: 2 x 4GE electrical ports + 2 x 4 10GE/25GE
⚫ GE ports: 24
GE switch S5331 ⚫
10GE ports: 4
⚫
Version: V200R019C00
Server VM Configurations for Private Cloud Deployment
Service Scenario Network Scale VMs vCPUs Memory Storage
< 2000 equivalent NEs 2 24 96 GB 650 GB
Manager (single domain) < 6000 equivalent NEs 2 40 128 GB 700 GB
< 15000 equivalent NEs 3 64 256 GB 900 GB
Manager+Controller < 6000 equivalent NEs 18 168 672 GB 6 TB
Manager+Controller 6000–15,000 equivalent NEs 19 224 896 GB 7 TB
Manager+Controller 15,000–30,000 equivalent NEs 25 296 1184 GB 8.5 TB
Manager+Controller 30,000–50,000 equivalent NEs 39 528 2112 GB 14 TB
Manager+Controller+Analyzer < 6000 equivalent NEs 25 240 960 GB 10 TB
Manager+Controller+Analyzer 6000–15,000 equivalent NEs 27 328 1312 GB 14 TB
Manager+Controller+Analyzer 15,000–30,000 equivalent NEs 36 448 1792 GB 19 TB
Manager+Controller+Analyzer 30,000–50,000 equivalent NEs 58 792 3168 GB 40 TB
Server Software Configurations
Configuration Item Configuration Type Version Requirement Remarks
Used on TaiShan servers for on-premises
Virtualization software FusionCompute 8.0.0 deployment and deployment on private
clouds.
Used on TaiShan servers for on-premises
OS EulerOS V2.8
deployment.
Delivered software
configurations GaussDB V100R003C20 OMP management node
Manager
Database GaussDB 100 V300R001C00 Analyzer
Controller
Druid 0.13.0 Used by the Analyzer.
Compatible software FushionSphere OpenStack

Virtualization software Used for deployment on private clouds.
configurations 6.5.1
• The following uses NCE Manager+Controller+Analyzer on the ARM server as an

example.
Client Configurations
Configuration Type Configuration Requirement
Minimum configurations: Recommended configurations:

⚫ CPU: 2 cores, 2.6 GHz ⚫ CPU: 4 cores, 3.1 GHz
PC
⚫ Memory: 4 GB ⚫ Memory: 8 GB
⚫ Hard disk: 8 GB ⚫ Hard disk: 8 GB
Minimum configurations:
⚫ CPU: 4 cores, 2.6 GHz
⚫ Memory: 4 GB
⚫ Hard disk: 8 GB
Cloud desktop
Recommended configurations:
⚫ CPU: 6 cores, 3.1 GHz
⚫ Memory: 8 GB
⚫ Hard disk: 8 GB
OS Windows 10 (32-bit or 64-bit)
Language English and simplified Chinese

⚫ Recommended: Google Chrome 70 or later (32-bit or 64-bit), FireFox ESR 61.0.1 or later (32-bit or 64-bit)
Browser
⚫ Compatible: Google Chrome 57 or later (32-bit or 64-bit), FireFox ESR 52 or later (32-bit or 64-bit)
Resolution 1366 x 768 px or higher; recommended resolution: 1920 x 1080 px
• Note:
▫ Zoom ratio of the browser: 100% is recommended and 80% to 200% is

compatible.
▫ If the resolution is within the compatibility scope of the browser, functions

are available but the layout may not be user-friendly. If the resolution is
not within the compatibility scope of the browser, both the functions and
layout are affected.
Quiz
1. (Multiple-answer question) Which of the following are the highlights of NCE-T?

A. Network visualization
B. Deployment automation
C. Automated service provisioning
D. Intelligent proactive O&M
E. Scenario-specific interfaces
• Answer: ABCDE
Contents

◼ Network Management
▫ System Settings
▫ Alarm Monitoring
▫ Security Management
▫ High Availability

Network Management
⚫ Basic functions
 Topology management
 DCN management
 Performance management
 Inventory management
 NE software management
⚫ Transport network management
 Transport NE service management
 Transport network service management
• NCE provides improved NE- and network-level security management, topology

management, alarm management, performance management, inventory
management, and software management. It can manage all NEs on Huawei
transport networks, IP networks, access networks, and obtain third-party device
information over NETCONF, SNMP, and ICMP to manage third-party devices. This
well meets customer requirements for network convergence and service growth.
Topology Management - Physical Topology View
• In topology management, the managed NEs and their connections are displayed
in a topology view. You can learn the network structure and monitor the
operating status of the entire network in real time by browsing the topology
view.
1. Left panel
▫ Resource Tree: displays subnets managed by NCE. Users can quickly locate
subnets.
▫ Legend & Filter: In this area, you can set the display modes of the objects in
a view, and view the descriptions of legends in the view. The filter tree and
legends help you to locate an object quickly.
▫ Toolbox: Provides the functions of creating subnets and setting topology
object layouts.
2. Topology view This area displays all managed NEs, connections between NEs, and
subnets.
▫ In the Main Topology, users can create subnets, NEs, and links, configure
NE data, browse fibers/cables, delete topology objects, browse current
alarms, and synchronize NE configuration data.
▫ Check NE status and communication status using the filter tree and
legends.
▫ Locate NEs. The required NEs can be quickly located by searching for NEs.
Topology Management - Clock View
• In the clock view, you can perform the following operations: set NE clocks, query
the network-wide clock synchronization status, search for clock tracing
relationships, synchronize with the Physical View, view the master clock ID, query
clock attributes, and view the clock locking status. NCE supports physical clocks,
PTP clocks, ACR clocks, and ATR clocks. This feature supports the display of
multiple types of NEs on the entire network, including NEs of the MSTP series,
NG WDM series, and RTN series.
• Discovering the clock topology automatically: NCE searches for clock links
between all NEs on the entire network to obtain the clock tracing relationships of
all NEs.
• Viewing the clock topology: After NCE automatically discovers the clock topology,
you can view the clock tracing relationships on the entire network.
• Configuring clocks: In the NE Explorer, you can configure NE clocks on the GUI
for configuring clocks. They include physical clocks, PTP clocks, ACR clocks, and
ATR clocks. The clock configuration functions vary with NE types.
DCN Management
⚫ NCE communicates with NEs and manages and maintains network nodes through
data communication networks (DCNs).
⚫ The DCN between NCE and the managed network is divided into two parts:
 DCN between the NCE server and NEs
 DCN between different NEs
⚫ Huawei's NEs support DCN networking through the following communication
protocols:
 HWECC
 TCP/IP (IP over DCC)
 OSI (OSI over DCC)
• Usually, a local area network (LAN) or wide area network (WAN) is adopted for
DCN communication between the NCE server and NEs. Inband or outband
networking is established between NEs and NCE. As the DCN between the NCE
server and NEs is external, the DCN between NEs is referred to as an internal
DCN.
• HWECC: Data transmitted in the DCC is encapsulated through HWECC. HWECC is
a private communication protocol developed by Huawei for DCN networking of
optical network NEs. This is supported only by NCE-T.
• TCP/IP (IP over DCC): Data transmitted in the DCC is encapsulated through
Transmission Control Protocol/Internet Protocol (TCP/IP).
• OSI (OSI over DCC). Data transmitted in the DCC is encapsulated through Open
Systems Interconnection (OSI).
Performance Management
OSS
PM TCA/Data
Report to
the OSS.
TCA/ Monitoring
PM data
Data example
Query Configure
data. PM service backend monitoring parameters.
TCA TCA/Data
Export
monitoring example
reports.
PM The alarm threshold
PM data data is exceeded.
PM data collection backend
PM TCA Collect data.

data
TCA/Data
monitoring example
NE Board Port Interface Li nk Service …
• NCE can monitor the key performance indicators of a network in real time, and
provide statistics on the collected performance data. It provides a graphical user
interface (GUI) to facilitate network performance management.
• NCE provides performance monitoring functions at both the NE and network

levels. NCE can manage access NEs, IP NEs, and transport NEs. After performance
monitoring instances are created, NCE collects performance data from NEs at the
specified time.
• NCE-T can monitor the performance of SDH, WDM, RTN, and PTN NEs.
Inventory Management
• Physical resources (such as equipment rooms, NEs, ports, optical/electrical

modules, and passive devices) and logical resources on the entire network can be
managed or maintained in unified and hierarchical mode. You can easily view
and export multi-layer attributes of various types of resources. You can also
customize filter criteria to query data on the live network, which improves
resource maintenance efficiency.
• You can customize categories to collect statistics of physical resources from

multiple aspects, and export inventory reports for equipment rooms, racks,
subracks, NEs, boards, subboards, ports, optical/electrical modules, slot usage,
and passive components. This helps you learn various types of resources on the
entire network, provides reference for E2E O&M, and improves resource usage.
NE Software Management
⚫ NE data management
 Saving
 Backup

Policy management
⚫ NE software upgrade/downgrade

Loading
 Activation
 Restoration
 Task management
 Software library management
• NE Software Management is used to manage NE data and upgrade or

downgrade NE software. NE data management includes NE data saving, backup,
and policy management. NE software upgrade/downgrade includes loading,
activation, restoration, task management, and software library management.
• Saving: After the system is configured, the configuration data is saved in the
memory or hard disks of NEs so that the data will not be lost when the system is
restarted. The following data saving methods are available:
▫ Manually saved
▫ Automatically saved through manually created tasks

▫ Automatically saved through policies
• Backup: Backs up NE data (such as configuration data or databases) to storage
devices other than NEs. The backup data is used for restoring NE data.
• Policy management: Setting policies in advance enables the system to perform
operations on NEs periodically or when trigger conditions are met. This is
applicable to routine NE maintenance.
Transport Network Management - Transport NE Service
Management
⚫ Transport NE support
⚫ Intelligent WDM deployment
⚫ WDM service adjustment
⚫ Intelligent microwave deployment and mobile O&M
⚫ MSTP service adjustment
⚫ Data migration
⚫ Visualized DCN management
• NCE supports SDH, RTN, WDM, submarine optical cable, SDH ASON, and WDM
ASON NEs on transport networks.
• Intelligent WDM deployment: NCE provides the OD optical-layer intelligent
management solution.
• WDM service adjustment: NCE supports optical-layer board replacement and
batch service switching.
• Intelligent microwave deployment and mobile O&M: NCE supports offline

configuration, meter-free testing, hop management, and mobile O&M.
• MSTP service adjustment: NCE supports transport board replacement, transport

NE replacement, and link capacity expansion.
• Data migration: NCE supports script import and export.
• Visualized DCN management: NCE supports DCN management in tables or views,

DCN subnet synchronization, network health evaluation, DCN view snapshot, and
all-gateway management.
Transport Network Management - Transport Network
Service Management
⚫ E2E OTN Service Management and Service-Level Fault Diagnosis
⚫ E2E Management of Transport Packet Services
⚫ Performance Monitoring and Fault Diagnosis of Transport Packet Services
⚫ E2E Microwave Service Management
• NCE supports E2E fast provisioning of OTN network services and troubleshooting
of OTN network faults with just one click.
• It provides E2E service configuration and service path visualization, and supports
visualized E2E provisioning and management of PWE3, VPLS, native Ethernet,
and L3VPN services on transport NEs, improving network O&M efficiency.
• It supports E2E service configuration, one-click connectivity debugging, one-click
performance commissioning, instrument-free tests, performance statistics, one-
click service diagnosis, loopback detection, and service path visualization. E2E
configuration of native Ethernet, PWE3, VPLS, L3VPN, and composite services is
implemented. One-click service diagnosis and visualized service paths greatly
improve the O&M efficiency of transport packet services.
• E2E service provisioning: E2E services are supported, including TDM, EoS, E-Line,
E-LAN, E-Line_E-LAN, and PWE3 services and tunnels. They can be uniformly
created and managed. In addition, E2E service profiles are provided.
Contents

▫ Network Management
◼ System Management
▫ Alarm Management

• NCE interconnects with southbound systems quickly and achieves Single Sign On
(SSO) to O&M interfaces. It supports global configuration in terms of Network
Time Protocol (NTP) time synchronization and license management, software
resource capabilities such as system monitoring and databases, and
troubleshooting such as data backup and restoration, system health check, and
fault locating and data collection. This improves interconnection and
management efficiency, helps carriers forecast and detect potential risks in time,
facilitates fault rectification, and therefore ensures stable and secure system
running.
System Interconnection
⚫ Interconnecting with southbound systems: NCE is integrated with Huawei or third-
party systems to quickly access NEs or virtual resources and obtain NE resources,
alarm and performance data, and virtual resources required for NCE service
provisioning or assurance. This improves interconnection efficiency.
⚫ SSO: an access control policy between NCE and its southbound systems or between
the upper-layer system and NCE. With a single login, users can access all mutually
trusted systems. This implements seamless O&M interface interconnection between
systems and improves O&M efficiency.
System Settings
⚫ NTP time synchronization: NCE nodes are managed and maintained in a unified
mode. Therefore, the Coordinated Universal Time (UTC) on each node must be the
same to ensure that NCE can properly manage services and data on the nodes.
⚫ License management: Updating and maintaining a license allow the system to
properly run based on the features, versions, capacity, and validity period authorized
in a license file.
⚫ Remote notification: When O&M personnel are not on site due to business travel or
off duty and cannot query significant alarms and service reports, remote notification
is used to send SMS messages and emails to the O&M personnel.
• License management includes initial license loading, license update, and routine
license maintenance.
• Initial license loading
▫ After the system is deployed, you need to load the correct license file to
ensure that the system works.
• License update
▫ During O&M, you need to update a license file under any of the following
conditions:
▪ The license is about to expire, has expired, or is invalid.

▪ The resource control items or function control items of the license do
not meet service requirements.
▪ The annual software service fee of the license is about to expire or

has expired.
• Routine license maintenance
▫ You need to check the license expiration date, consumption, and capacity
on a regular basis, so you can identify and resolve problems such as licenses
about to expire or insufficient capacity in a timely manner.
System Monitoring
⚫ Global monitoring capability is supported to monitor NCE resource indicators such
as services, processes, nodes, and databases. This helps conduct predictive analysis
and detect potential risks in time. For key resources, the O&M personnel can set
thresholds to trigger alarms and handle exceptions promptly.
• Service and process monitoring: Monitors the service running status and
indicators such as the CPU usage, memory usage, and number of handles. When
a process in a service stops abnormally or becomes faulty, NCE attempts to
restart the process. If the restart fails for 10 consecutive times, an alarm is
generated, requesting users to handle the exception manually.
• Node monitoring: Monitors node indicators such as the CPU, virtual memory,
physical memory, and disk partitions. If any resource of the node encounters an
exception, the node is displayed as abnormal. If a key resource remains abnormal
within a sampling period, an alarm is generated.
• Database monitoring: Monitors database indicators such as the space, memory,

and disk. If any resource of the database encounters an exception, the database
is displayed as abnormal. If a key resource remains abnormal within a sampling
period, an alarm is generated.
System Maintenance
⚫ System backup and restoration: Backs up and restores the dynamic data, OS, database, management
plane, and application software of NCE. Data is backed up in a timely manner. If any backup object is
abnormal, you can use the corresponding backup file to recover the object to the normal state.
⚫ O&M management: Provides system maintenance and management functions to help O&M personnel
learn the health status of the system and reduce system risks. If a system fault occurs, this function
provides fault location information, which helps to rectify the fault and reduce loss.
⚫ Online help: NCE provides a layered design for the GUI help adapting to user needs in diverse
scenarios. An online help system that supports anytime, anywhere, on-demand learning is established.
A variety of help forms such as tips, panels, question mark windows, and Information Center are
provided. All necessary information is directly displayed on the GUI. Information that is closely related
to the current operation is folded. You can unfold the information if necessary. Systematic learning
information is placed in an independent help system.
• Health check: Checks and evaluates hardware, OSs, databases, networks, and
NCE services to learn the health status, detect abnormal check items, and
determine whether operation or running risks exist in NCE.
• Data collection: Provides data collection profiles based on fault scenarios,

services, and directories. When a system fault occurs, O&M personnel can collect
logs and database tables as required and analyze and locate the fault.
• Quick fault demarcation: Each service operation in the system is implemented by

calling one or more services. During service operations, the system automatically
collects statistics on service operation status, memory usage, and CPU usage for
O&M personnel to quickly demarcate faults and analyze resource consumption.
• Fast fault locating: Provides default locating profiles for O&M personnel to select
profiles based on fault scenarios for automatic fault demarcation and locating.
This helps O&M personnel quickly obtain solutions and shorten the fault locating
time.
Contents

▫ System Management
◼ Alarm Management

• Alarm management enables O&M personnel to centrally monitor NE, system

service, and third-party system alarms and quickly locate and rectify network
faults, ensuring normal network operation.
• Alarms or events are displayed on the page when NEs, services, and
interconnected third-party systems detect their exceptions or significant status
changes.
• Alarm: a type of notification generated when the system or a managed object

(MO) detects a fault.
• Event: a type of notification generated by the system or an MO during normal

running, which needs to be sent to users.
Alarm Severity
Alarm
Default Color Description Handling Policy
Severity
Handle critical alarms immediately. Otherwise,

A service-affecting fault has occurred, and
Critical services may be interrupted or the system may break
measures must be taken immediately.
down.
A service-affecting fault has occurred. If
Handle major alarms in a timely manner. Otherwise,
Major the fault is not rectified, it will lead to a
important services will be affected.
severe result.
Trivial impact has been caused on
Minor services, but corrective measures need to Identify causes and eliminate risks.
be taken to prevent more severe faults.
A potential or imminent fault is detected, Handle warning alarms based on network and NE
Warning
but services are not affected currently. running status.
Alarm Status
Status Alarm Status Description
The initial acknowledgment status is unacknowledged. After users acknowledge an alarm

Acknowledgment Acknowledged or because they plan to handle it, the alarm status changes to acknowledged. After users
status unacknowledged unacknowledge an alarm, the alarm status changes to unacknowledged. Users can configure
rules to automatically acknowledge alarms.
The initial clearance status is uncleared. When the fault that causes an alarm is rectified, a
Cleared or clearance notification is automatically reported to Alarm Management, and the alarm status
Clearance status
uncleared changes to cleared. For some alarms, clearance notifications cannot be automatically
reported. They must be manually cleared. The background color of cleared alarms is green.
The initial maintenance status is normal. Users can set the status of alarms generated during
Maintenance Normal or under
commissioning as under maintenance. When monitoring or querying alarms, O&M personnel
status maintenance
can filter under-maintenance alarms to avoid wasting time on them.
• Current alarms: include alarms that are not acknowledged or cleared,

acknowledged but not cleared, cleared but not acknowledged. Based on current
alarms, users can identify faults, take measures, and notify O&M personnel.
• Historical alarms: include alarms that have been cleared and acknowledged.
Users can analyze historical alarms to optimize system performance.
• Note:
▫ The maintenance status corresponding to Normal is NORMAL.
▫ The maintenance status corresponding to Maintenance is Maintenance and
Invalid status.
Alarm Handling Mechanisms
⚫ Alarm Management provides three alarm handling mechanisms.
 Alarm merging rules improve alarm monitoring efficiency.
 Processing of the full current alarm cache is used to control the number of current
alarms.
 Alarm dump rules are used to control the storage capacity of the database.
• Alarm merging rules: To help you improve the efficiency of monitoring and
handling alarms, alarm management provides alarm merging rules. Alarms with
the same specified fields (such as location information and alarm ID) are merged
into one alarm. This rule is used only for monitoring and viewing alarms on the
Current Alarms page and takes effect only for current alarms.
• The specific implementation scheme is as follows:
▫ If a newly reported alarm does not correspond to any previously reported

alarm that meets the merging rule, the newly reported alarm is displayed
as a merging alarm and the value of Occurrences is 1.
▫ If the newly reported alarm B and the previously reported alarm A meet the
merging rule, alarm B and alarm A are merged into one alarm record and
are sorted by clearance status (uncleared alarms are displayed first) and
occurrence time in descending order.
▪ If alarm A is displayed on top, it is still regarded as a merging alarm,

and the value of Occurrences for the merging alarm increases by 1.
Alarm B is regarded as a merged alarm.
▪ If alarm B is displayed on top, it is regarded as a merging alarm, and

the value of Occurrences for the merging alarm increases by 1. Alarm
A is regarded as a merged alarm.
Contents

◼ Security Management

• Security Management involves user permissions, system security policies, and

logs. Security Management prevents unauthorized users from accessing the
system and ensures system data security.
User Management
User management authorization Region administrator
• User Management ensures user information and system security. Assigns roles to
users and manages user permissions by role, to achieve optimal resource
allocation and permission management and improve O&M efficiency.
▫ Role-based authorization minimizes permissions and optimizes resource

allocation.
▫ The permissions and resources in a region are managed by the region
administrator, ensuring prompt maintenance of user permissions.
▫ Most users use an Authentication, Authorization, Accounting (AAA) system

to implement centralized user management, authentication, and
authorization. After interconnecting with the AAA system through remote
authentication configuration, the system authenticates users on the AAA
system to ensure that only authenticated users can log in to the system.
Log Management
⚫ Log Management is used when you need to perform routine maintenance, locate
and troubleshoot faults, trace historical logs, and query operation logs across
systems.
⚫ Log type:
 Security logs: record user operations performed in the system that affect system security.
 System logs: records automatically triggered system operations or tasks.
 Operation logs: records user operations performed in the system that do not affect system
security.
Contents

◼ High Availability

High Availability
⚫ Local HA
 Hardware HA
 Application Layer HA
⚫ Remote DR HA
• During system running, unexpected faults may occur due to external

environments, misoperations, or system factors. For these unknown risks, NCE
provides hardware, software, and system-level availability protection solutions for
system recovery and damage mitigation.
Hardware HA
Protection Type Protection Solution
TaiShan server: redundancy protection for power supplies and fans, and 1+1 bond protection
for NICs.
Hardware redundancy Switch: redundancy protection. Configure two switches to protect each other. They connect
the server to the customer's network. Hardware redundancy protection enables instant
switchover. The application layer is even unaware of switchover.
If the server has eight hard disks, the first and second hard disks are configured as RAID 1, the
third, fourth, fifth, and sixth hard disks are configured as RAID 10, the seventh hard disk is
RAID
configured as RAID 0, and the eighth hard disk is used for full system backup and restoration.
If the server has 12 hard disks, the hard disks are configured as RAID 10.
• When a fault occurs on the hardware with redundancy protection, the hardware
automatically switches to the normal component to ensure that the NCE OS and
application services run properly.
Application Layer HA
Protection Type Protection Solution Protection Capability
Automatic switchover of application services in the NCE Manager+Controller+Analyzer
scenario:
If virtual nodes are deployed in primary/secondary mode, services are generally
running only on the primary node. When the service processes on the primary node
Switchover time ≤ 5
are faulty, the services on the secondary node are automatically enabled and the
minutes
Application service service instances on the secondary node are started to provide services.
protection If virtual nodes are deployed in cluster mode, all nodes are running in the multi-active
state. If one node is faulty, other nodes share the load of the faulty node and
continue to provide services evenly.
Process restart: Process status is monitored in real time. If a process is stopped or
Process restart time ≤ 5
faulty, NCE will restart the process. If the restart fails for 10 consecutive times, an
minutes
alarm will be generated, requesting users to process the exception manually.
Backup and restoration: The backup and restoration function is provided for data.
Backup and restoration
Data can be backed up periodically or before major changes. If NCE data becomes
time ≤ 60 minutes
abnormal, it can be restored based on the backup files.
Automatic database switchover: Database nodes are deployed in primary/secondary
Data protection mode. In normal situations, the database on the primary node is readable and
writable, and the database on the secondary node is read-only. RPO = 1 minute
When the service processes on the primary node are faulty, NCE automatically RTO = 1 minute
switches to the database on the secondary node to provide services. The
primary/secondary switchover does not affect services.
• Recovery point objective (RPO): a service switchover policy, minimizing data loss
during DR switchover. The data recovery point is used as the objective to ensure
that the data used for DR switchover is the latest backup data.
• Recovery time objective (RTO): a service switchover policy that ensures the
shortest switchover time. It tasks the recovery time point as the objective and
ensures that the redundancy machine can take over services as quickly as
possible.
Remote DR HA
Protection Type Protection Solution Protection Capability
NCE is deployed on primary and secondary sites. Data in each database is
synchronized from the primary site to the secondary site based on the
Primary/Secondary RPO = 1 minute
synchronization policy. If the primary site is faulty, the arbitration service
switchover RTO = 15 minutes
automatically starts the secondary site for NCE service continuity. You can
also manually start the secondary site in this case.
The DR system uses a heartbeat link to monitor
the association between the primary and secondary sites and a data
Primary/Secondary replication link to synchronize data between the two sites. If the heartbeat
status monitoring or data replication link between the primary and secondary sites is
abnormal, NCE will report an alarm. The fault can be either manually
rectified or automatically processed by the arbitration service.
Remote DR Switchover Solution (Manager)
Remote DR Solution Application Scenario
There are two equipment rooms, and the status of the primary and secondary sites is manually
Manual switchover monitored. If a site-level fault occurs, there is no strict requirement on the fault recovery time. In this
case, manual O&M is required.
There are two equipment rooms, and the status of the primary and secondary sites needs to be
Automatic switchover
monitored in real time. After a site-level fault occurs, a primary/secondary switchover needs to be
(without the arbitration
quickly implemented to restore services. In addition, services can bear the risks caused by the dual-active
service)
state.
There are three equipment rooms, and the status of the primary and secondary sites needs to be
Automatic switchover
monitored in real time. After a site-level fault occurs, a primary/secondary switchover needs to be
(with the arbitration service)
quickly implemented to restore services.
Manual Switchover
DR Link IP Address Network Plane

Remote DR network
Data replication link Replication IP address Note: The remote DR network can reuse the inter-node communication
network or northbound network or use an independent network plane.
Remote DR network. The heartbeat IP address and replication IP address must

Heartbeat link Heartbeat IP address
be on the same network plane.
• The DR network can reuse the original network of NCE to reduce the network
configuration of the primary and secondary sites.
• Solution overview:
▫ The primary and secondary sites communicate through the heartbeat link
to detect the status of each other in real time. The primary site
synchronizes data to the secondary site in real time through the data
replication link to ensure data consistency between them.
▫ When a disaster occurs at the primary site, manually perform the takeover
operation at the secondary site. The secondary site becomes the primary
site and provides services. The primary site becomes the secondary site.
• Manual switchover trigger conditions:
▫ A disaster such as an earthquake, fire, or power failure occurs at the

primary site caused the system as a whole to be unable to provide services.
▫ Some key nodes at the primary site are damaged and cannot provide
services. For example, database node (DB) corruption, platform service
node (Common_Service) corruption, management domain service node
(NMS) corruption, and control domain service node (Controller or
TController) corruption.
Automatic Switchover (Without the Arbitration Service)
• Solution overview:
▫ The primary and secondary sites communicate with each other through the
heartbeat link and detect the status of the peer site in real time. The
primary site synchronizes product data to the secondary site in real time
through the data replication link to ensure data consistency between the
primary and secondary sites.
▫ If the primary site encounters a power failure, hardware failure, or system

down event and the fault is not rectified within the specified time, the
secondary site automatically enters the active state and then switches to
the standby state after fault rectification.
▫ If only the heartbeat link between the primary and secondary sites is
interrupted, the secondary site automatically switches to the active state. In
this case, the DR system enters the active-active state and generates related
alarms. However, both the primary and secondary sites run properly.
▪ If the heartbeat link recovers within 2 hours, the system enters active-
active negotiation mode. After the negotiation, the primary site before
the heartbeat link is interrupted remains in the active state, and the
other site switches to the standby state.
Automatic Switchover (with the Arbitration Service)
A three-node remote DR system
• Solution overview: To prevent dual-active split-brain when the network between

sites is abnormal, the arbitration service provides the site private network
monitoring function, periodically checks the connectivity between the primary,
secondary, and third-party sites, and share the check results through the
arbitration site communication link. If the arbitration heartbeat is abnormal due
to a network abnormality or site fault, the arbitration service uses an internal
algorithm to provide the optimal site on the current network to implement
automatic switchover between the primary and secondary sites.
• Automatic switchover trigger conditions:
▫ A disaster such as an earthquake, fire, or power failure occurs at the

primary site, and the fault is not rectified within the specified time.
▫ The heartbeat link between the primary and secondary sites is interrupted,
and the arbitration site communication link between the primary site and
the third-party site is interrupted.
▫ NCE Manager scenario and Manager+Controller+Analyzer compact

scenario:
Quiz
1. (Multiple-answer question) NE Software Management is used to manage NE data and upgrade or
downgrade NE software. Which of the following operations are performed on NEs to manage NE
data?
A. Save
B. Back up
C. Load
D. Policy management
2. (True or false) The remote DR switchover solution includes automatic switchover and manual
switchover. Manual switchover can be classified into manual switchover without the arbitration
service and manual switchover with the arbitration service based on whether there are two or three
equipment rooms.
A. True
B. False
• Answers: 1. ABD 2. B
Contents

◼ Optical Service Provisioning
▫ Optical Network Survivability Analysis
▫ OVPN
Optical Service Provisioning
⚫ Functions:
 Automatic service provisioning
 Scheduled service provisioning
 Reserved service bandwidth adjustment
 Real-time service bandwidth adjustment
 Optimal latency policy
Automatic Service Provisioning
1. Service
Prerequisite Resource discovery and
configuration
updates
➢ Automatic discovery of TE link
resources
➢ Automatic discovery of 2. Service Topology display
topologies adaptation
➢ Visualized topology and easy
management 3. Route
computation NCE
Resource discovery and
1 Service configuration
updates
➢ Meets diversified service
4. Delivery and
requirements. IDC /
route setup
DC
2 Service adaptation
➢ Converts service parameters into

internal commands.
Video Video
3 Route computation
➢ Computes a service route based Cloud office Cloud office

on the service request and IDC/DC IDC/DC
available resources.
Data backup Data backup
4 Delivery and route setup
Service Provisioning Process (1)
Resource discovery and Service Service Route Delivery and route
updates configuration adaptation computation setup
Visualized network resources,

topology, and bottlenecks
NBI RESTCONF RESTful CORBA MTOSI XML
Visualized use status of resources:
Network Cloud Engine
• NEs & Ports

Optical Service Key Service Optical Network • Inter-site layered resources
Apps OVPN
Provisioning Assurance Survivability Analysis • Remaining bandwidth between
two sites
NCE automatically discovers TE link resources, node

Manager C ontroller Analyzer resources, pipe resources, and cross-connection resources
through PCEP/OSPF.
Based on different services, the Controller abstracts link
SBIs PCEP OSPF-TE Qx SNMP SFTP resources at different layers (including layer-1 links,
layer-2 links, and SDH links) and cross-connection
resources at different layers (including common cross-
connections, SDH cross-connections, and packet cross-
IDC IDC connections).
Enterprises Metro Backbone Enterprises In addition to common node resources and pipe
resources, services are also dependent on different link
resources and cross-connection resources.
Resource discovery Service Route Delivery and
Service configuration
and updates adaptation computation route setup
Client service
Parameter Description
Rate Signal type of a client service
Network topology • Point-to-point (P2P): transmits data from one source to one destination.
Latency requirements There is no latency constraint or user-defined latency constraint.
• Permanent 1+1: If the working or protection path becomes faulty, rerouting will be triggered. Ensure that there is always
one working path and one protection path.
• Rerouting 1+1: If the working path becomes faulty, protection switching will be triggered. If the working and protection
paths are both faulty, rerouting will be triggered.
Protection level
• Static 1+1: If the working path becomes faulty, protection switching will be triggered. This mode does not provide
rerouting.
• Rerouting: If the working path becomes faulty, rerouting will be triggered. This mode does not provide a protection path.
• None: There is no protection mechanism, rerouting, or protection path.
• Explicit node constraints can be set for electrical-layer networks.
Route constraints
• Explicit node constraints and optical-layer server layers can be set for optical-layer networks.
Packet service
Bandwidth Service bandwidth
• None: After an EPL service is created, the port transparently transmits all the received packets.
Ethernet encapsulation protocol
• 802.1Q: After an EVPL service is created, the port identifies and transmits only standard 802.1Q packets.
type
• QinQ: After an EVPL service is created, the port identifies and transmits only standard QinQ packets.
Routing policy No latency constraint/Minimum latency
• Permanent 1+1: If the working or protection path becomes faulty, rerouting will be triggered. Ensure that there is always
one working path and one protection path.
• Rerouting 1+1: If the working path becomes faulty, protection switching will be triggered. If the working and protection
paths are both faulty, rerouting will be triggered.
Protection level
• Static 1+1: If the working path becomes faulty, protection switching will be triggered. This mode does not provide
rerouting.
• Rerouting: If the working path becomes faulty, rerouting will be triggered. This mode does not provide a protection path.
SDH service
SDH bearer mode SDH self-networking and MS-OTN carrying SDH services
Routing policy No latency constraint/Minimum latency
• Static 1+1: If the working path becomes faulty, protection switching will be triggered. This mode does
Protection level not provide rerouting.
• VC12: 2 Mbit/s
• VC4: 155 Mbit/s
Signal type • VC4-4C: 622 Mbit/s
• VC4-16C: 2480 Mbit/s
• VC4-64C: 9920 Mbit/s
Client service
1. A user starts the Optical Service Provisioning app, selects the client service
type, and specifies service parameters such as the source, sink, SLA, and
policy.
2. The NCE Controller computes service routes and checks whether server trails
can be reused (server trails with the same route exist and the bandwidth
meets requirements.).
3. The NCE Controller delivers trail and service configuration information to the
NE through PCEP.
(a) If no server trail is available, the NCE Controller drives the NE to create a
trail through GMPLS.
⚫ For electrical-layer GMPLS networks, if static OCh trails have been configured on
the networks, the NCE Controller can drive the creation of dynamic ODUk trails.
⚫ For optical-layer GMPLS networks, the NCE Controller can drive the creation of
dynamic OCh trails and static ODUk trails.
(b) The NCE Controller drives the source and sink NEs to configure the port
service mode and create cross-connections from ports to ODUk trails to
complete client service configuration.
E-Line service 1. A user starts the Optical Service Provisioning app, selects the E-Line service type, and
specifies service parameters such as the source, sink, encapsulation type, bandwidth,
port protection mode, SLA, and policy.
2. The NCE Controller computes service routes and checks whether server trails can be
reused (server trails with the same route exist and the bandwidth meets
requirements.).
3. The NCE Controller delivers trail and service configuration information to the NE
through PCEP.
(a) If no server trail is available, the NCE Controller drives the NE to create a trail
through GMPLS.
⚫ For electrical-layer GMPLS networks, if static OCh trails have been configured on the networks,
the NCE Controller can drive the creation of dynamic ODUk trails.
⚫ For optical-layer GMPLS networks, the NCE Controller can drive the creation of dynamic OCh
trails and static ODUk trails.
(b) If MPLS tunnels exist and the remaining bandwidth meets requirements, the MPLS
tunnels are reused. Otherwise, MPLS tunnels are created along the ODUk trail.
(c) The NCE Controller drives the source and sink nodes to configure the port working
mode, create PWs, configure ETH OAM, and set QoS parameters to complete E-line
service configuration.
SDH service
1. A user starts the Optical Service Provisioning app, selects the SDH service type,
and specifies service parameters such as the source, sink, rate level, SLA, and
policy. The SDH service parameters are transmitted to NCE through the NBI.
2. The NCE Controller computes service routes and checks whether VC-4 tunnels can
be reused.
3. The NCE Controller delivers trail and service configuration information to the NE
through PCEP.
(a) If no VC-4 tunnel is available, the NCE Controller drives the NE to create a VC-4 tunnel
through GMPLS.
(b) The NCE Controller drives the source and sink NEs to configure cross-connections from
ports to the VC tunnel to complete SDH service configuration. If there is an aggregation
node in the middle, cross-connections of the aggregation node also need to be created.
Resource discovery Route Delivery and route
Service configuration Service adaptation
and updates computation setup
1. The service module sends a route setup request to the

trail service module.
Service
2. The trail service module sends a route computation
NCE Controller
module request to the routing algorithm module.
1 5 3. The routing algorithm module computes routes based

on the routing policy expected by the service module.
Trail (1) The routing algorithm module synchronizes data
service
to obtain information of network-side links by
2 4
using southbound PCEP/OSPF link resources.
(2) The route computation contains three key steps:
Routing Node resources
3 1. Link availability check
algorithm
Pipe resources 2. Link cost computation
Network Network Link resources 3. Optimal route computation
resources topologies
Cross-connection 4. The routing algorithm module sends the route
resources computation result to the trail service module.
SBI (PCEP/OSPF)
5. The trail service module sends the route computation
response to the service module.
Centralized route computation

After a service alarm is received, the first node of the service sends a
Service restoration NCE route computation request to the NCE Controller. The NCE
failed Controller returns the route computation result, and the first node
sets up trails based on routes.
H G F H 1. The NCE Controller is used to provision services, and centralized
G F
A E D C A E
route computation is used for trail setup.
D C 2. When a link is faulty, the NCE Controller can be used for
B B centralized rerouting.
ASON metro SDN metro Advantages of centralized route computation
1. The services of different first nodes can be considered to avoid
Success rate (%) resource conflicts and ensure optimal processing of global services.
100% 2. The optical-layer batch algorithm is used to improve the batch
99.9999% 10+% rerouting success rate.
98%
3. The route availability and performance of optical parameter
reachability diagram algorithm of the NCE Controller are better
90%
88.9% than those of the NE-side optical parameter algorithm.
4. The upper-layer service requirements can be considered during
route computation.
Distributed Centralized 5. The Controller works with the NEs for service recovery to ensure
more reliable services.
Strategy
R outing profile
Traffic Minimum Minimum Minimum User-defined
...
engineering (TE) latency hops distance cost
TE Minimum latency Minimum hops

20 ms
500 km 606 km
400 km 10 km
100 km 300 km
100 km 920 km
80 km 100 km
100 km 200 km
300 km
10 ms
Minimum distance User-defined cost
500 km 606 km
400 km 10 km
100 km 300 km
100 km 920 km
80 km 100 km
100 km 200 km
300 km
L1 L2 SDH
Strategy Name ODUk Trail OCh Trail
Service Service Service
TE policy ● ● ● ● ●
Minimum-latency
● ● ● ● ●
policy
Minimum-hop
- - - ● ●
policy
Minimum-distance
- - - ● ●
policy
User-defined cost - - - ● ●
Note: ●: Supported; -: Not supported

NCE (active 1. The service module obtains the route information

and standby) computed by the algorithm module and delivers the
configuration data to the first node for service
(1) (3) configuration over PCEP-based SBI.
2. After the NE-side ASON software receives the

request, it delivers a trail setup request to the first
node.
(2)
3. After a trail is set up, the first node sends a response
to the NCE Controller through PCEP.
Scheduled Service Provisioning (1)
⚫ What
 For L1 services (client services), users can set the time when services are provisioned and deleted as required.
When the specified time arrives, the system automatically triggers an operation so that the bandwidth setting
takes effect.
⚫ Why
 Scheduled provisioning aims to meet the requirements of scheduled provisioning and withdraw of client
services, achieving staggered sharing of link, port, and trail resources.
• Staggered sharing of trails: Different customers or departments have their

diversified bandwidth requirements in different time segments. Duration-based
bandwidth scheduling enables staggered sharing of trail bandwidth resources.
Load Load
Transmission bandwidth reservation
reduces the load of the core IDC.
Common Common IDC

IDC 00:00–08:00
Super IDC Super IDC

16:00–24:00
08:00–16:00
Common IDC
Data center OSN optical subrack

Switch OSN electrical subrack
The bandwidth reservation mechanism is used to meet customers' planned

service requirements and implement staggered sharing of trails.
Bandwidth
Without NCE Bandwidth cannot be shared,
Video-on-demand and fixed bandwidth must be
Video-on-demand reserved for each service type in
each time segment.
Video traffic
Cloud office
Cloud office IDC/DC IDC/DC Cloud office
Data backup
Data backup Data backup

00:00–08:00 08:00–16:00 16:00–24:00 Time
Scheduled provisioning enables staggered bandwidth sharing and

With NCE ensures optimal use of OTN line resources.
Video-on-demand Bandwidth
Video-on-demand
Peak Video traffic
Peak Cloud office
Peak
Cloud office
IDC/DC IDC/DC Cloud office Data backup
Data backup Data backup 00:00–08:00 08:00–16:00 16:00–24:00 Time
Scheduled service provisioning enables staggered bandwidth sharing.
NE-side resources
Scheduled service process are not occupied.
A user requests for Reserve port, When a user requests for

provisioning of a reserved
reservation
provisioning of a link, and other

Resource
reserved service. resources. service, the NCE Controller

uses reserved port, link, and
NCE other resources instead of the
Port and link resources on resources on the NEs.
the NE are occupied.
The scheduled service When the scheduled service
Scheduled
activation
start time arrives.

start time approaches, the
NCE Controller automatically
NCE creates the service based on
the reserved resources,
which occupies the resources
The scheduled Release the resources Release the occupied port and
service end time reserved for the NCE link resources on the NE.
on the NE.
deactivation
arrives. Controller.
Scheduled
When the scheduled service

end time approaches, the
NCE NCE Controller automatically
releases the occupied
resources on the NE.
Reserved Service Bandwidth Adjustment (1)
⚫ On-demand bandwidth reservation flexibly meets planned or sudden requirements.
Bandwidth
↑ 300 Mbit/s ↓ 400 Mbit/s
400 Mbit/s
↑ 200 Mbit/s
Leased-line
200 Mbit/s
VIP
Actual traffic flow

0 Mbit/s
July Aug Sep. Oct. Nov. Dec. Time
• When the allocated bandwidth cannot meet requirements of data services, a user
can increase the bandwidth. When the allocated bandwidth is excessive, a user
can decrease the bandwidth to save costs.
• Bandwidth can be adjusted daily or temporarily on a specified date.

Reserved Service Bandwidth Adjustment (2)
① Policy profile:
➢ Profile name
⚫ Function implementation: ➢ Bandwidth
➢ Type: temporary or routine
App ➢ Adjustment time
1 2
Policy
Policy Policy ② Policy application:
profile application Bind the created E-Line service to the policy profile and deliver the
request for resource verification and reservation.
The time at which 4 EVPL service 3 ③ Resource verification and reservation:
the policy takes
effect starts.
Check whether the port bandwidth resources are sufficient for
EVPL services. If the ODUk resources are insufficient, create an
Adjust bandwidth Verify and reserve ODUk, switch services to the new ODUk, and reserve the
in real time. bandwidth resources.
resources to ensure that the bandwidth can be adjusted to the
expected value when the policy expires.
④ Real-time bandwidth adjustment:
Adjust bandwidth at the time specified in the policy profile.
Real-Time Service Bandwidth Adjustment (1)
⚫ Provide bandwidth for customers on demand, improving network resource usage.
A user can adjust service bandwidths in real time.

The NCE Controller issues latest bandwidths to
NEs, modifies the CIR and PIR of service PWs, and
adjusts MPLS-TP tunnel bandwidths accordingly.
⚫ If ODUk resources are sufficient for bandwidth
adjustment, PW shaping can be directly
adjusted, and services will not be interrupted.
⚫ When ODUk resources are insufficient, an
extra ODUk/MPLS-TP tunnel needs to be
created and the original PW needs to be
switched to the new trail. In this case, services
will be interrupted for about 10 seconds.
Optical Service
⚫ Function implementation (decreasing Provisioning app
the bandwidth):
MPLS-TP
 Decrease the PW bandwidth, and deliver 1
2
the bandwidth to the source node and TP tunnel PW
then the sink node.

 Decrease the TP tunnel bandwidth.
 The minimum bandwidth unit is 1 Mbit/s. SBI
NEs
⚫ Function implementation (increasing the Optical Service
Provisioning app
bandwidth and reusing the TP tunnel):
MPLS-TP
 Increase the TP tunnel bandwidth. 1
2
 Increase the PW bandwidth. TP tunnel PW
 The maximum bandwidth varies depending

on the board type.
SBI
NEs
• Note: The sequence is the reverse of that for decreasing the bandwidth.
⚫ Function implementation (increasing the
Optical Service
bandwidth and not reusing the TP tunnel): Provisioning app
 Create a TP tunnel.
MPLS-TP

Rebind the PW to the new TP tunnel. 1
2
TP tunnel PW
 Switch to the new ODUk tunnel and delete the old
TP tunnel.
PW
PW TP tunnel (old) PW
PW
ODUk (old)
SBI
TP tunnel (new)
ODUk (new)
• Note: The sequence is the reverse of that for decreasing the bandwidth.
Minimum Latency Policy
Select the route with the ⚫ The NCE Controller centralized

minimum latency based on algorithm calculates the service route
the latency measurement based on the latency information,
582 μs 473 μs
results. obtains the minimum-latency route,
and delivers the route to the NE to
Source: site E 102 μs complete service creation.
339 μs 326 μs
Sink: site C 198 μs 227 μs
⚫ The NCE Controller obtains the latency
Bandwidth: 10 Gbit/s 196 μs 401 μs information of each board and link from the
SLA: 1+1 NE and realizes real-time visualization of
latency on the entire network.
Latency: minimum ⚫ For the service boards that do not support
latency
the latency policy, the NCE Controller
automatically calculates the latency (5
µs/km) based on the fiber distance.
⚫ Latency information is carried on each board (tributary

board, line board, cross-connect board, and tributary-
line integrated board).
⚫ In the electrical-layer networking scenario, the NE
automatically triggers the link latency calculation. (The
prerequisite is that the OCh trail is established in
advance and the board supports latency
measurement.)
Contents

▫ Optical Service Provisioning
◼ Optical Network Survivability Analysis
▫ OVPN
Overview of Optical Network Survivability Analysis
⚫ Optical network survivability analysis is
a process of simulating a fault on a
network resource to check whether the
remaining resources meet service
protection requirements and identify
the services that will be interrupted or
downgraded.
This function helps users assess

whether SLA violation risks are present
in service quality and take
countermeasures in advance.
• NCE supports resource warning, immediate analysis, and fault simulation.

Application Scenarios of Survivability Analysis
Fault Fault
Description
Immediate analysis Resource warning Type Occurrences
All links on each node are considered a fault
Node
NCE group. During optical network survivability
NCE fault analysis, NCE checks all nodes on a network.
Each link is considered a fault group. During
Link
optical network survivability analysis, NCE
fault 1 checks all links.
All links in a shared risk link group (SRLG) are
SRLG considered a fault group. During optical
Traverses network-wide site and fiber faults (Triggered as scheduled or upon network survivability analysis, NCE covers all
fault
to analyze faults once or twice. resource changes) Traverses SRLGs.
network-wide faults to analyze Two nodes are considered a fault group. During
Fault simulation faults once and identify all Node survivability analysis, NCE checks all nodes.
resource risks. If a network has N nodes, the number of fault
fault
groups equals to N x (N – 1).
Two links are considered a fault group. During
Link survivability analysis, NCE checks all links.
2 If a network has N links, the number of fault
fault
Two SRLGs are considered a fault group. During
Analyze faults once on the specified fault points (10 at SRLG survivability analysis, NCE checks all SRLGs.
most), improving efficiency by 90%. If a network has N SRLGs, the number of fault
fault
Survivability Analysis Principles
⚫ Survivability analysis process:
Apply for analysis Generate fault points

Obtain analysis
Initial state resources (network- based on analysis
Analysis is configurations.
wide topology) configurations.
triggered.
Summarize and Analyze the service Identify the services

generate analysis restoration status when that are affected by a
results. the fault occurs. fault point.
Analyze fault points one by one.
• The NCE Controller supports centralized rerouting. When the working or

protection route of one or more GMPLS services that have rerouting resources is
interrupted, the NE control plane automatically sends route calculation requests
to the NCE Controller. The NCE Controller calculates an optimal route for the
GMPLS service based on the network-wide topology and sends the route to the
NE of each GMPLS service. The NE then creates a restoration route based on the
optimal route.
• The NCE Controller implement survivability analysis using the centralized

rerouting computation capability. By simulating a network resource fault (fault
point) and analyzing services affected by the fault, the NCE Controller calculates
the service restoration status and restoration route based on the network-wide
topology. By analyzing and collecting statistics on faults on the entire network or
a single fault point, you can evaluate the network resources on the entire
network or a single fault point.
Contents

▫ Optical Service Provisioning
▫ Optical Network Survivability Analysis
◼ OVPN
OVPN Overview (1)
⚫ Optical virtual private network (OVPN): Link resources on software-defined
networking (SDN) networks are sliced and specified link bandwidth is reserved for
users so that a logically independent private network can be formed.
⚫ With the OVPN function, carriers can provide virtual private networks for important
enterprise customers. Without the need to construct their own physical private
networks, important enterprise customers can obtain high security achieved by hard
pipe isolation and sustainable service development achieved by OVPN resource
reservation. In addition, carriers can use the OVPN function to flexibly sell link
bandwidths, improving the resource utilization of carriers' networks.
OVPN Overview (2)
Tenant 1 Tenant 2 Tenant 3 Tenant 4
Virtual network
NCE
Transport network
Basic Concepts of OVPN
⚫ Resource slicing
 Resource slicing is resource division. Carriers allocate network-side resources to different OVPN users based on
OVPN user applications. The line-side resources allocated by carriers are ODUk resources, and the minimum
granularity is ODU0.
 The line-side resources allocated to OVPN users are OVPN resources and can be used only by the corresponding
OVPN users. The line-side resources that are not allocated are shared resources (also referred to as public
network resources), and carriers can allocate these resources to other OVPN users or services that do not use
the OVPN function.
⚫ Resource adjustment
 OVPN users apply for resources as required. If the resources that are applied for do not match the actual
resources, the resources can be dynamically adjusted.
 When network resources of an OVPN user need to be expanded, the shared resources are allocated to the
OVPN user. When network resources of an OVPN user need to be reduced, the resources allocated to this OVPN
user are recycled as shared resources.

Application Scenarios of OVPN
⚫ The OVPN function can virtualize transport networks to provide diversified bandwidth services,
improving user experience and bringing a new business mode for carriers.
⚫ OVPN implementation: A carrier divides a network into several virtual subnets and provides them for
specific tenants.
2 2
Tenant 1 Application 1 3 1
4 5 4
layer 6 7 6 7
The tenants request the
carrier to adjust bandwidth. Client 2 Client 1
Tenant 2 Carrier Tenant 2 Tenant 1

Management & NCE
The carrier adjusts Control layer
bandwidth as required but
the tenants do not receive Physical layer
2
real-time response. 1 3
5 4 8
6 7
Transport network
No OVPN OVPN solution

OVPN Principles
Creating an OVPN
1. A carrier starts the OVPN app and allocates link resources to an OVPN user
according to the requirements of the OVPN user.
2. NCE delivers line-side resources planned by the carrier to a WDM device using
PCEP protocol messages.
3. The WDM device adds an OVPN ID for the corresponding link and floods the
OVPN ID to the entire network using the OSPF protocol.
4. After the carrier receives the resource adjustment request of the OVPN user,
steps 1 to 3 are repeated to adjust the network resources of the OVPN user.
Provisioning services on the OVPN

1. A user starts the Optical Service Provisioning app and provisions services on the
specified OVPN.
2. NCE computes service routes based on the OVPN link resources and delivers the
computation result to the WDM device.
3. The WDM device generates the corresponding OVPN service.
Provisioning services on the OVPN
• Note: When a fault occurs on the network, the OVPN service is rerouted to
matching resources (not other OVPN resources or shared resources) based on the
used OVPN, regardless of whether route computation is performed on the device
or NCE. Services deployed on public resources cannot be rerouted using OVPN
resources.
Quiz
1. (True or false) An OVPN is the virtual private network of an optical network. Link
resources on software-defined networking (SDN) networks are sliced and
specified link bandwidth is reserved for users so that a logically independent
private network can be formed.
A. True
B. False
• Answer: A
Summary
⚫ The chapter describes the product positioning, solution architecture, and

deployment solutions as well as the functions and features of NCE-T.

Thank you. 把数字世界带入每个人、每个家庭、
每个组织，构建万物互联的智能世界。
Bring digital to every person, home, and
organization for a fully connected,
intelligent world.
Co pyright© 2021 Huawei Technologies Co., Ltd.

A l l 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.

NCE-T HCIA Lecture

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

NCE-T HCIA Lecture

Uploaded by

Copyright:

Available Formats

Introduction to NCE-T

⚫ The chapter describes the positioning, features, architecture, and functions

⚫ On completion of this course, you will be able to:

1. System Architecture of NCE-T

2. Basic Functions of NCE-T

3. Key Features of NCE-T

• NCE Lite is a lightweight version of NCE, which is oriented to enterprises and

• NCE is a network lifecycle automation platform that integrates management,

Plane Intended User Group Functions Login Mode

• The GUI screenshots of NCE Manager are used as examples.

1. System Architecture of NCE-T

2. Basic Functions of NCE-T

3. Key Features of NCE-T

Multi-tenant Multi-service Multi-industry

Open API catalog & gateway

Intent engine (innovated planning)

Manager Controller Analyzer

Southbound framework of Multi-vendor device

Cross-layer Cross-domain Multi-vendor

Open APIs ACTN/RESTful SNMP XML CORBA FTP

Manager & Controller Analyzer

Service provisioning Service profile Latency map Centralized policy

Unified cloud platform Basic services Public services Product engineering

SBIs SNMP QX PCEP OSPF

1. System Architecture of NCE-T

2. Basic Functions of NCE-T

3. Key Features of NCE-T

• Deployment on private clouds means that customers prepare the bottom-layer

• Based on different system protection expectations, deployment on physical

Manager (single domain) < 6000 equivalent NEs 2 40 128 GB 700 GB

< 15000 equivalent NEs 3 64 256 GB 900 GB

Manager+Controller < 6000 equivalent NEs 18 168 672 GB 6 TB

Manager+Controller 6000–15,000 equivalent NEs 19 224 896 GB 7 TB

Manager+Controller 15,000–30,000 equivalent NEs 25 296 1184 GB 8.5 TB

Manager+Controller 30,000–50,000 equivalent NEs 39 528 2112 GB 14 TB

Manager+Controller+Analyzer < 6000 equivalent NEs 25 240 960 GB 10 TB

Manager+Controller+Analyzer 6000–15,000 equivalent NEs 27 328 1312 GB 14 TB

Manager+Controller+Analyzer 15,000–30,000 equivalent NEs 36 448 1792 GB 19 TB

Manager+Controller+Analyzer 30,000–50,000 equivalent NEs 58 792 3168 GB 40 TB

Druid 0.13.0 Used by the Analyzer.

Compatible software FushionSphere OpenStack

• The following uses NCE Manager+Controller+Analyzer on the ARM server as an

Minimum configurations: Recommended configurations:

⚫ Hard disk: 8 GB ⚫ Hard disk: 8 GB

OS Windows 10 (32-bit or 64-bit)

Language English and simplified Chinese

▫ Zoom ratio of the browser: 100% is recommended and 80% to 200% is

▫ If the resolution is within the compatibility scope of the browser, functions

1. (Multiple-answer question) Which of the following are the highlights of NCE-T?

C. Automated service provisioning

D. Intelligent proactive O&M

1. System Architecture of NCE-T

2. Basic Functions of NCE-T

3. Key Features of NCE-T

• NCE provides improved NE- and network-level security management, topology

PM data collection backend

PM TCA Collect data.

• NCE provides performance monitoring functions at both the NE and network

• Physical resources (such as equipment rooms, NEs, ports, optical/electrical

• You can customize categories to collect statistics of physical resources from

• NE Software Management is used to manage NE data and upgrade or

▫ Automatically saved through manually created tasks

• Intelligent microwave deployment and mobile O&M: NCE supports offline