Imaster NCE-IP V100R022C10 Product Description (x86) 03-E

iMaster NCE-IP
V100R022C10
Product Description
(x86,enterprise)
Issue 03
Date 2023-08-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. i

iMaster NCE-IP
Product Description (x86,enterprise) About This Document
About This Document
Purpose
This document describes the positioning, features, architecture, configuration,
functions, and application scenarios of iMaster NCE, helping you comprehensively
understand the product.
NOTE
The unified network management and control feature depends on the NCE components
that you have deployed. If only Manager components are deployed (NCE Manager for
short), only management capabilities can be implemented.
Intended Audience
This document is intended for:
● Network planning engineers
● Data configuration engineers
● System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium level of risk which, if not

avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not

avoided, could result in minor or moderate injury.
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. ii

iMaster NCE-IP
Symbol Description
Indicates a potentially hazardous situation which, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Supplements the important information in the main text.

NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
GUI Element Reference Conventions

The GUI conventions that may be found in this document are defined as follows:
Convention Description
Boldface Buttons, menus, parameters, tabs, windows, and dialog

titles are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Command Conventions
The command conventions that may be found in this document are defined as
follows:
Boldface Command keywords are in boldface.
Italic Command arguments are in Italic.
[] Items (keywords or arguments) in brackets ([ ]) are

optional.
{x | y |...} Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item or no item is selected.
{ x | y | ... } * Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. iii

iMaster NCE-IP
[ x | y | ... ] * Optional items are grouped in brackets and separated by

vertical bars. A minimum of none or a maximum of all can
be selected.
Change History
Issue Date Description
03 2023-08-15 This issue is the third official release.
02 2023-04-15 This issue is the second official release.
01 2023-01-10 This issue is the first official release.
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. iv

iMaster NCE-IP
Product Description (x86,enterprise) Contents
Contents
About This Document................................................................................................................ ii

1 Product Positioning................................................................................................................. 1
2 Product Features...................................................................................................................... 4
2.1 Network Digital Map............................................................................................................................................................. 4
2.2 Network Open Programmability Platform (AOC)....................................................................................................... 5
2.3 Incident View............................................................................................................................................................................ 5
2.4 Energy View............................................................................................................................................................................... 6
3 New Features............................................................................................................................7
4 Architecture.............................................................................................................................. 9
4.1 Solution Architecture..............................................................................................................................................................9
4.2 Software Architecture.......................................................................................................................................................... 12
4.3 External Interfaces................................................................................................................................................................ 13
4.3.1 NBIs........................................................................................................................................................................................ 14
4.3.1.1 XML NBIs...........................................................................................................................................................................15
4.3.1.2 CORBA NBIs..................................................................................................................................................................... 18
4.3.1.3 SNMP NBI......................................................................................................................................................................... 19
4.3.1.4 Performance Text NBI (FTP/SFTP)........................................................................................................................... 20
4.3.1.5 REST.................................................................................................................................................................................... 20
4.3.1.6 Kafka.................................................................................................................................................................................. 22
4.3.2 SBIs......................................................................................................................................................................................... 26
4.4 Southbound DCN Networking......................................................................................................................................... 28
5 Deployment Schemes........................................................................................................... 31
5.1 On-Premises Deployment.................................................................................................................................................. 31
5.1.1 Deployment on Physical Machines..............................................................................................................................31
5.1.2 Deployment on VMs......................................................................................................................................................... 35
5.2 Deployment on Private Clouds.........................................................................................................................................40
5.3 EasySuite Deployment Tool............................................................................................................................................... 44
6 Configuration Requirements.............................................................................................. 46
6.1 Server Hardware Configurations for On-Premises Deployment ......................................................................... 46
6.2 Server VM Configurations for Private Cloud Deployment...................................................................................... 46
6.3 Server Resource Configurations (SUSE, Product Only)............................................................................................ 50
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. v

iMaster NCE-IP
6.4 Server Software Configurations....................................................................................................................................... 51

6.5 Client Configurations........................................................................................................................................................... 53
6.6 Bandwidth Configurations................................................................................................................................................. 54
7 Functions and Features........................................................................................................ 58

7.1 App List..................................................................................................................................................................................... 58
7.2 System and Common Functions...................................................................................................................................... 61
7.2.1 System Settings.................................................................................................................................................................. 61
7.2.2 Alarm Management......................................................................................................................................................... 65
7.2.3 Security Management...................................................................................................................................................... 78
7.2.3.1 User Management......................................................................................................................................................... 78
7.2.3.2 Log Management........................................................................................................................................................... 85
7.2.3.3 Security Situation........................................................................................................................................................... 91
7.2.3.3.1 Security Situation Awareness................................................................................................................................. 91
7.2.3.3.2 Remote Attestation.................................................................................................................................................... 94
7.2.3.3.3 Dynamic Trust Assessment......................................................................................................................................95
7.2.3.3.4 Dynamic Policy Management................................................................................................................................ 95
7.2.3.4 Security Configuration Check.................................................................................................................................... 96
7.2.3.4.1 Application Security................................................................................................................................................... 97
7.2.3.4.2 NE Security....................................................................................................................................................................97
7.2.3.4.3 Security Configuration Check Management..................................................................................................... 98
7.2.4 Data Collector..................................................................................................................................................................... 99
7.2.4.1 Feature Description..................................................................................................................................................... 100
7.2.4.2 Application Scenarios................................................................................................................................................. 100
7.3 Network Management..................................................................................................................................................... 101
7.3.1 Basic Functions................................................................................................................................................................ 101
7.3.1.1 Topology Management..............................................................................................................................................103
7.3.1.2 DCN Management...................................................................................................................................................... 109
7.3.1.3 Performance Management...................................................................................................................................... 110
7.3.1.4 Inventory Management............................................................................................................................................. 116
7.3.1.5 NE Software Management....................................................................................................................................... 123
7.3.2 IP Network Management............................................................................................................................................. 125
7.3.2.1 IP NE Management..................................................................................................................................................... 125
7.3.2.2 IP Service Management.............................................................................................................................................127
7.3.3 Third-Party NE Deployment........................................................................................................................................ 129
7.4 Service Provisioning........................................................................................................................................................... 132
7.4.1 Network Slicing................................................................................................................................................................132
7.4.1.1 Background.................................................................................................................................................................... 132
7.4.1.2 Feature Introduction................................................................................................................................................... 132
7.5 Analysis and Assurance.................................................................................................................................................... 134
7.5.1 Network Performance Analysis.................................................................................................................................. 134
7.5.1.1 Telemetry Collection................................................................................................................................................... 134
7.5.1.2 Performance Overview.............................................................................................................................................. 136
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. vi

iMaster NCE-IP
7.5.1.2.1 Introduction to Performance Overview............................................................................................................ 136

7.5.1.3 Performance Reports.................................................................................................................................................. 144
7.5.1.3.1 Introduction to IP Reports..................................................................................................................................... 145
7.5.1.3.2 Introduction to PTN Reports................................................................................................................................ 159
7.5.1.4 Report Management.................................................................................................................................................. 175
7.5.1.5 Performance Regional Map..................................................................................................................................... 175
7.5.1.6 Performance Topology............................................................................................................................................... 177
7.5.1.7 Service Bandwidth Analysis...................................................................................................................................... 177
7.5.1.8 Scheduled Report Task Management................................................................................................................... 178
7.5.1.9 Object Management...................................................................................................................................................178
7.5.1.9.1 IP RAN/PTN Object Management...................................................................................................................... 178
7.5.1.10 TWAMP Quality Monitoring.................................................................................................................................. 179
7.5.1.11 ICMP Quality Monitoring....................................................................................................................................... 192
7.5.1.12 Trace Test..................................................................................................................................................................... 195
7.5.1.13 Network Path Restoration and Auxiliary Fault Demarcation.................................................................... 196
7.5.1.13.1 ATN+CX Network Path Restoration and Auxiliary Fault Demarcation............................................... 196
7.5.1.13.2 IP Network Path Restoration and Auxiliary Fault Demarcation............................................................ 205
7.5.1.13.3 PTN Network Path Restoration and Auxiliary Fault Demarcation....................................................... 206
7.5.2 Network Path Optimization........................................................................................................................................ 209
7.5.2.1 Background.................................................................................................................................................................... 209
7.5.2.2 Feature Introduction................................................................................................................................................... 209
7.5.3 VPN Service Assurance.................................................................................................................................................. 212
7.5.3.1 Trends and Status Quo.............................................................................................................................................. 212
7.5.3.2 Solution Overview....................................................................................................................................................... 212
7.5.3.3 Usage Scenario............................................................................................................................................................. 217
7.5.3.4 Technical Principles..................................................................................................................................................... 219
7.5.3.4.1 IFIT................................................................................................................................................................................. 219
7.5.3.4.1.1 Measurement Mechanisms............................................................................................................................... 219
7.5.3.4.1.2 Measurement Modes........................................................................................................................................... 224
1. E2E Measurement Mode.................................................................................................................................................... 224
2. Hop-by-Hop (Trace) Measurement Mode....................................................................................................................225
7.5.3.4.1.3 Mass Fault Aggregation Algorithm................................................................................................................ 227
7.5.3.4.2 TWAMP........................................................................................................................................................................ 227
7.5.3.4.3 Y.1731........................................................................................................................................................................... 229
7.5.3.5 VPN Monitoring Specifications............................................................................................................................... 230
7.6 Agile Open Container........................................................................................................................................................240
7.6.1 Challenges in Network O&M...................................................................................................................................... 240
7.6.2 Introduction to AOC....................................................................................................................................................... 241
7.6.2.1 Application Scenarios................................................................................................................................................. 243
7.6.2.2 Customer Benefits....................................................................................................................................................... 244
7.6.2.3 Specifications and Restrictions................................................................................................................................ 245
7.7 Northbound Integration................................................................................................................................................... 247
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. vii

iMaster NCE-IP
7.7.1 Open API & Tool.............................................................................................................................................................. 247
8 Usage Scenarios ..................................................................................................................249

8.1 CloudWAN............................................................................................................................................................................ 249
9 High Availability..................................................................................................................254
9.1 Local HA................................................................................................................................................................................ 255
9.2 Disaster Recovery Solutions............................................................................................................................................ 259
10 Security................................................................................................................................275
10.1 Security Architecture....................................................................................................................................................... 275
10.2 Security Functions............................................................................................................................................................ 276
11 Personal Data and Privacy Protection......................................................................... 280

11.1 Personal Data Description............................................................................................................................................ 280
11.2 Principles and Key Technologies................................................................................................................................. 281
11.3 Lifecycle Management................................................................................................................................................... 282
11.4 Privacy Protection Roles.................................................................................................................................................283
12 Specifications..................................................................................................................... 284
12.1 System Performance Indicators...................................................................................................................................284
12.2 NE Management Capabilities and Maximum Concurrent Client Connections...........................................299
12.3 Service Management Capabilities.............................................................................................................................. 300
12.4 Equivalent Coefficient..................................................................................................................................................... 302
12.4.1 Equivalent Coefficients for NEs on NCE-IP.......................................................................................................... 302
13 Version Requirements...................................................................................................... 383

13.1 PTN Series........................................................................................................................................................................... 383
13.2 NE/ATN/CX/Multi-service gateways Series............................................................................................................. 407
13.3 R/AR Series......................................................................................................................................................................... 484
13.4 RM9000 Series.................................................................................................................................................................. 509
13.5 Switch Series...................................................................................................................................................................... 509
13.6 Security Series................................................................................................................................................................... 628
13.7 iCache Series...................................................................................................................................................................... 658
A Standards Compliance....................................................................................................... 659

B Glossary and Abbreviations.............................................................................................. 668
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. viii

iMaster NCE-IP
Product Description (x86,enterprise) 1 Product Positioning
1 Product Positioning
Trends and Challenges

With the rapid development of 5G and the advent of the cloud era, all-new
business models are continuously emerging, and enterprises have begun to move
towards cloudification and digitalization. As an enabler of digital and cloud
transformation in various industries, the telecom industry faces many new
opportunities and challenges presented by massive connections, all-cloud, and
intelligence of everything.
● Increasingly complex networks: A large number of sites need to be built or

reconstructed on 5G networks, and 5G will double to triple base station
density with comparison to 4G. Complex cross-domain and cross-network
service scenarios lead to high planning and deployment costs.
● High O&M costs: Site visit costs remain stubbornly high. Analysis and
decision-making rely on manual efforts and other tools, which are not only
costly but also error-prone.
● Difficulty in business monetization: Differentiated products and service
capabilities are insufficient for the cloudification of millions of enterprises,
and SLAs cannot be monetized. In addition, service provisioning takes too
long due to a low level of automation.
To cope with these challenges, carriers must fundamentally change the way they
operate networks and solve network O&M issues through architectural innovation
rather than just tinkering with the traditional architecture.
Industry Direction
At the beginning of 2020, Huawei released ADN Solution White Paper. The ADN
solution aims to research the impact of AI technologies on future network
architectures, O&M modes, and business models by integrating multiple intelligent
technologies, such as SDN, NFV, cloud, big data, AI, and knowledge graph. It
solves structural TCO problems on telecom networks and drives the intelligent
upgrade of the telecom industry through architectural innovation. It enables
Huawei to proactively participate in and promote the development of intelligent
society, and share the dividends of service innovations in intelligent society. This
will revitalize the telecom industry, attract more talent, and promote healthy and
sustainable development of the industry.
Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 1

iMaster NCE-IP
ADN consists of three layers: smart devices, management and control platform,
and cloud-based applications. ADN transforms the existing network architecture in
the following aspects:
● Replaces inefficient repetitive work with automated processes to cope with
the heavy O&M pressure caused by massive connections and large network
scale, greatly shortening the network construction and service provisioning
time.
● Shifts from complaint-driven O&M to proactive O&M (proactively identifying
and resolving problems and then notifying customers), and achieves
predictive O&M through in-depth analysis of massive data.
● Explores the advantages of AI machine learning and massive data to provide
assistance or even make decisions under human supervision, significantly
improving response speed, resource efficiency, and energy efficiency for
network services.
● Shares data throughout network planning, construction, maintenance, and
optimization to achieve closed-loop autonomy.
IP networks have evolved from manually executing command lines to an SDN
+Automation era, and then an ADN <Autonomous> era.
Product Positioning
In the three-layer ADN architecture, iMaster NCE-IP is located at the management
and control platform layer. It uses network as a service (NaaS) interfaces to
intelligently translate upper-layer services and application intents into network
behaviors. The compliance with 70+ standard protocols enables it to dynamically
detect IP network status and implement intent-driven automation.

iMaster NCE-IP

iMaster NCE-IP
Product Description (x86,enterprise) 2 Product Features
2 Product Features
NCE-IP leverages the intelligent cloud-map algorithm to associate network

resources, services, and status data and build a complete digital map of the IP
network. It integrates network data collection, network awareness, network
decision-making, and network control to help enterprises transform their IP
network O&M.
● Automation: SR/SRv6 control-plane capabilities are integrated to
automatically discover network topologies and optimize paths.
● Intelligence: Telemetry and IFIT are used to collect network data in real time.
Then through intelligent data analysis, proactive O&M becomes a reality.
● Open programmability: YANG models are used to implement the intent-
driven APIs needed for cloud-network convergence. The workflow engine
enables onsite programming.
2.1 Network Digital Map
2.2 Network Open Programmability Platform (AOC)
2.3 Incident View
2.4 Energy View
2.1 Network Digital Map

Network Digital Map in iMaster NCE-IP is an innovative solution that manages the
physical network world through a digital world. It operates similar to a
transportation navigation map and is capable of multidimensional visualization
and path navigation from networks to applications.
Network Digital Map possesses the following five features:
● Multidimensional visualization: Network Digital Map provides views —
physical, slicing, and network. Interconnected through standard protocols such
as TWAMP, BGP-LS, and telemetry, Network Digital Map collects link protocol
status, delay, packet loss, bandwidth utilization, and more information in real
time in order to draw multidimensional views including real-time delay,
bandwidth utilization, and packet loss views. The big data engine processes
massive data in seconds, including multidimensional indicators (such as real-
time delay, bandwidth, and packet loss) of 100,000 links on 30,000 NEs, truly

iMaster NCE-IP
achieving "one map for the entire network". Network-wide status changes,
originally invisible, can now be perceived in milliseconds, helping customers
identify network problems like service detours and accurately plan network
paths.
● Navigation-like path computation: Network Digital Map is integrated with GIS
so that devices can be accurately located based on GIS information. It also
supports path precomputation and multiple path selection policies, such as
bandwidth balancing and minimum delay. When automatically planning
network paths for services, it computes the optimal paths that best match
customers' service intents.
● Differentiated path bearer: The adoption of the self-developed cloud-map
algorithm enables Network Digital Map to compute paths based on
combinations of 20+ factors, including bandwidth, delay, traffic, and
availability. All the factors can be combined flexibly to compute the optimal
paths according to service intents. This also helps carriers with refined
classification of services and opens up more possibilities for provisioning
diversified network products.
● Automatic traffic scheduling: Network Digital Map monitors network quality
indicators, including delay, packet loss, and bandwidth utilization, and detects
network congestion and delay/packet loss deterioration in real time. Based on
this information, paths are automatically adjusted — which takes mere
minutes — to provide continuous service SLA assurance.
● Management of millions of tunnels: Network Digital Map supports millions of
tunnels and takes mere minutes to compute paths network-wide, even
meeting future requirements of large-scale network management. E2E
network management is truly achieved through just one map.
2.2 Network Open Programmability Platform (AOC)

Service-oriented network operation is one of the goals pursued by carriers and
large enterprises during network evolution. It involves full-lifecycle management
of network services, spanning design, provisioning, adjustment, and O&M. iMaster
NCE-IP provides flexible model-driven full-lifecycle management of network
services, supports drag-and-drop service design, and opens service models for
flexible extension of custom parameters, shortening the service rollout time to
weeks. In terms of service provisioning, the automation engine of NCE-IP supports
atomic service orchestration in various single-domain and cross-domain scenarios,
one-click service provisioning in minutes, and bandwidth on demand (BoD) and
bandwidth calendaring (BC) capabilities. Moreover, NCE-IP abstracts services at
three levels (NE, network, and service). Its intent-oriented NBIs significantly
simplify OSS integration and accelerate service innovation.
2.3 Incident View

Network O&M is synonymous with high cost and low efficiency, which is largely
due to the fact that O&M activities (such as alarm monitoring, and fault locating,
analysis, and handling) rely heavily on manual work.
Incident View offers intelligent incident management and network risk analysis to
forecast risks, detect faults within 1 minute, and diagnose faults within 3 minutes,

iMaster NCE-IP
reducing the cost of handling invalid and correlative events and improving
troubleshooting efficiency.
● Intelligent incident management: builds a fault propagation model based on
O&M big data and expert knowledge, conducts continuous online self-
learning, aggregates correlative alarms into network incidents, and outputs a
fault propagation diagram to accurately locate root events, reducing the cost
of handling invalid and correlative events, improving troubleshooting
efficiency, and reducing dependency on experts.
● Network risk analysis: builds a two-layer AI architecture (AI in the network
management and control system and embedded AI in devices) to detect
anomalies in massive device KPIs, forecast device resources, and analyze and
train network-wide KPI data, configuration data, and performance data
online, implementing proactive detection and analysis of network risks.
2.4 Energy View

As the global energy price surges, energy saving becomes urgent and people are
accelerating their journey to carbon neutrality. Currently, IP transport devices
consume about 20% of energy on the communications network, second only to
base stations.
Energy View provides a way to visually manage and optimize the network energy
consumption from multiple dimensions. The energy consumption of devices on the
transport network is no longer a "black-box;" instead, it is visualized at the device,
network, and carrier levels with the help of industry-leading energy-saving
technologies. The multidimensional energy consumption visualization provides the
energy-saving trend and overview, which show the energy consumption
distributions and trends in real time. The ability to dynamically identify idle
resources and forecast service trends enables Energy View to hibernate or wake up
resources as needed. Through what is described above, it makes carriers closer to
their energy conservation and emission reduction targets and the goal of "green
site, green network, and green operation."

iMaster NCE-IP
Product Description (x86,enterprise) 3 New Features
3 New Features
This section describes the changes in key features compared with the previous
NCE version.
Table 3-1 New features of NCE-IP

Function/ Type Description
Feature
Name
Network Enhan Offer security or physical isolation for power differential

Managem ced protection services, security & stability control services,
ent and power monitoring services.
Applicatio Enhan For devices at both ends of a private line, provide data
n ced compression/decompression to reduce the private line
Optimizati bandwidth and leasing costs.
on ● Application definition: specifies the application access
locations (NEs), application characteristics (such as 3-
tuples and APN IDs), and application attributes (such
as source/sink areas, application types, and levels).
● Application policy (compression): defines a
compression policy, data compression algorithm, and
applications associated with the policy.
● Policy benefit: presents NE-level statistics (product
implementation restrictions), traffic before
compression, traffic after compression, and
compression rate.
● Comparison: compares the compression effects of the
same NE in different time segments or different NEs in
the same time segment.

iMaster NCE-IP
Product Description (x86,enterprise) 3 New Features
Function/ Type Description

Feature
Name
Network Enhan BSID as a service enables cross-domain connections and

Path ced one-hop transmission of cloud-network services across
Optimizat provinces and cities. Specifically, it supports:
ion ● Traffic statistics visualization
● SR MPLS Policy cascading
● On-demand obtainment of SLA values of cross-
province private lines
Pure protocol interconnection enables nodes and links to
be displayed in the Layer 3 topology, even though related
NEs are not managed by NCE.
DR Enhan No DR site needs to be deployed, reducing deployment

ced costs and improving DR reliability.

iMaster NCE-IP
Product Description (x86,enterprise) 4 Architecture
4 Architecture
4.1 Solution Architecture

4.2 Software Architecture
4.3 External Interfaces
4.4 Southbound DCN Networking
4.1 Solution Architecture

The following figure shows the architecture of the NCE enabling cloud-based
network solution.

iMaster NCE-IP
Figure 4-1 Architecture of the NCE enabling cloud-based network solution
The functions of each layer are as follows:
● IT/OSS/application layer
The IT/OSS/application layer is a platform that helps carriers transform to
digital operations. In addition to traditional OSSs and BSSs, the IT/OSS/
application layer 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 that allow for
end-to-end operation of the network, including network infrastructure
resource presentation, service path presentation, and service policy
management. 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 implements centralized management, control, and analysis of network
infrastructure, cloudifies resources, and automates the entire network lifecycle
based on business and service intents. Moreover, it provides intelligent closed-
loop management driven by data analysis. It also provides open network APIs

iMaster NCE-IP
and quick IT integration to help carriers accelerate service innovation and

implement e-commerce operations.
From top to bottom, NCE consists of the following layers:
– Open API catalog & gateway
The unified API gateway provides a secure and reliable entry point for
access.
It provides open NBIs to integrate with external systems such as the
traditional OSS, orchestrator, and third-party applications. It supports
backward compatibility of traditional interfaces such as CORBA/MTOSI
and SNMP, and new interfaces such as REST/RESTCONF to adapt to
future solutions and development.
– Scenario-based apps
Provides application packages for automating business scenarios. Users
can simply define service requirements based on their business intentions
without worrying about how the network implements them or what
resources are utilized. NCE converts these service requirements into
network configurations and delivers them. It provides application
packages for network operation and maintenance automation, which
covers the full E2E lifecycle for automated management.
– Intent engine (innovated planning)
Provides lifecycle management and driving capabilities based on
networks, services, and business intentions, supports intent planning,
design, conversion, verification, activation, decision-making, and
optimization, and implements flexible service innovation through model
driving and open model and policy assembling.
– NCE Manager
Provides traditional management capabilities (FCAPS) for device
configuration, alarms, performance, links, and QoS, and provides E2E
automated service provisioning capabilities for traditional networks.
– Controller
Provides capabilities for single- and multi-domain control (including IP
cross-domain, optical cross-domain, and IP+optical cross-layer control) of
SDN networks. Optimizes routes, delivering related configurations
through multi-factor global route computation.
– NCE Analyzer
Provides real-time data collection, status awareness, in-depth analysis,
and intelligent prediction capabilities for network traffic and
performance. Proactively identifies faults and potential risks via big data
analysis and generates warnings.
– Southbound Collection Framework
The southbound collection architecture is decoupled layer by layer.
Plugins can be injected to quickly extend capabilities such as adding new
protocols for data collection, adding device types, and defining new data
outputs.
– Southbound collection
Provides model-driven device data collection capabilities, shields the
application layer from differences in protocols used for collection (such as
telemetry, SNMP, and Qx) and device version differences, and filters

iMaster NCE-IP
duplicate collection tasks from multiple apps. In this way, data can be
collected once and used for multiple purposes.
– Cloud platform
NCE's unified cloud platform provides a unified user portal, network
planning and IP address planning tool, installation, deployment, upgrade,
system monitoring, and common services such as alarms, security,
topology, and inventory. With its cloud microservice architecture, NCE can
be deployed independently and adapt to any user scenario. As it utilizes
virtualization, NCE supports cloud-based deployment, reducing CAPEX.
● Network infrastructure
The network infrastructure layer (physical layer) is the layer that belongs
mostly to carriers, and includes devices on the transport, IP, and access
networks. It implements the most fundamental of communication and
connection services. Consisting of traditional networks and new SDN
networks, an NCE-enhanced infrastructure layer provides connections
everywhere, and is constantly evolving. It provides high-bandwidth and low-
delay communication services, and abstracts devices at the connection layer
into a shared model to form a network resource pool that can achieve a given
business intent.
4.2 Software Architecture

NCE is a cloud-based system that uses a service-oriented software architecture. It
is deployed on the virtualization platform and can be scaled flexibly. NCE
implements three logical modules (network management, network control, and
network analysis) and various application scenarios as services and components
that allow for flexible, modular deployment to meet customer requirements.
Logical Architecture of NCE-IP
Figure 4-2 Logical architecture of NCE

iMaster NCE-IP
NCE-IP adopts a service-oriented modular design on top of its cloud architecture

and supports distributed deployment on virtual machines. It consists of the
following modules: common service, Manager+Controller+Analyzer, scenario-
specific app, and southbound & northbound openness.
● Common service module: provides basic network services such as alarms and
logs and product engineering capabilities such as disaster recovery (DR) and
backup.
● Manager+Controller+Analyzer module: provides the network topology,
L2/L3 VPN, path computation and optimization, diagnosis, and prediction
capabilities.
● Scenario-specific app module: provides E2E service capabilities (such as agile
private lines) for different business scenarios.
● Southbound & northbound openness module: provides NBIs and SBIs for
quick interconnection and integration with third-party applications, other
management & control systems, and devices.
4.3 External Interfaces

NCE provides multiple northbound interfaces (NBIs) to quickly interconnect with
the OSS. It is also compatible with multiple southbound interfaces (SBIs) to
implement unified management and control of transport, IP, and access devices.

iMaster NCE-IP
Figure 4-3 Functions and features of external interfaces
4.3.1 NBIs
NCE offers network monitoring information, such as the alarm, performance, and
inventory information, for OSSs through NBIs. The NBIs support network
management, control, and analysis functions, such as service configuration and
diagnostic tests. Through the NCE NBIs, NCE can integrate with different OSSs
flexibly.
Table 4-1 NBI functions supported by NCE-IP
Interf Featu NE CX Switc BRAS ATN PTN Securi

ace re Series Series h ty
Series
XML[ Alarm √ √ √ √ √ √ √
MTOS
I] Perfor √ √ × × √ √ ×
manc
e
Invent √ √ √ √ √ √ ×
ory
Config √ √ √ √ √ × ×
uratio
n

iMaster NCE-IP
Interf Featu NE CX Switc BRAS ATN PTN Securi

ace re Series Series h ty
Series
CORB Alarm √ √ √ √ √ √ ×
A
SNMP Alarm √ √ √ √ √ √ √
Perfor Perfor √ √ √ √ √ √ ×
manc manc
e text e
NBI (Histo
(FTP/ rical
SFTP) Perfor
manc
e)
REST Alarm √ √ √ √ √ √ √
Perfor √ √ √ √ √ √ ×
manc
e
Invent √ √ √ √ √ √ √
ory
Config √ √ × × √ √ ×
uratio
n
Kafka Alarm √ √ √ √ √ √ √
Perfor × × × × × × ×
manc
e
Invent √ √ √ √ √ √ √
ory
4.3.1.1 XML NBIs

The XML NBI is developed for NCE by referring to the Multi-Technology
Operations System Interface (MTOSI) series. The XML NBI functions as a bridge
between NCE and OSSs. The XML NBI can adapt itself to the integration and
cross-domain trends. The XML NBI provides alarm management, service
provisioning, inventory management, and performance management and can be
integrated with the OSS easily.

iMaster NCE-IP
Performance Indicators
Table 4-2 Performance indicators of the XML NBI

Indicator Specifications
Number of concurrent A total of 20 XML interfaces can be called concurrently.

interface requests If more than 20 interfaces are called, the excess
interfaces will be put into a queue and may time out
eventually, depending on the timeout periods set on
OSSs and interfaces. The following interfaces maintain
their own concurrency limits, which, once exceeded,
will also trigger errors no matter whether the
preceding total limit (that is, 20 interfaces) is
exceeded:
● The concurrency of the following interfaces is 1:
getInventory, executeCLI, getAllInventoryData
getAllManagedElements, getAllManagedElement-
Names, getAllTopologicalLinks, getAllSubnetwork-
Connections, getAllSubnetworkConnectionNames,
getAllProtectionSubnetworks, getAllFlowDomain-
Fragments, getAllFlowDomainFragmentNames,
getActiveAlarms, getHistoryAlarms,
getHistoryPerformanceMonitoringData,
getAllCurrentPerformanceMonitoringData,
getAllTopoViewNodesInfo
setManagedElementParam, deleteManagedEle-
mentParam, doProcess
Delay in response to When querying a large quantity of alarms, the XML

XML requests NBI handles at least 100 alarms per second, depending
on the network and NE status.
Number of 10
notification
connections
Alarm notification ≥ 60 alarms/s (3 OSSs)

processing capability
Alarm notification < 10s (3 OSSs)

transmission delay
Size of an SOAP 500,000 characters

request packet

iMaster NCE-IP
NCE-IP Functions
Complying with the TMF MTOSI 2.0 series standards, the XML NBI enables NCE to
provide alarm, performance, inventory, configuration, diagnosis, and protection
group management on IP devices for OSSs.
The NCE XML NBI supports the following functions:
● Alarm management
– Alarm reporting
– Synchronization of active alarms
– Alarm acknowledgment
– Alarm clearance
– Alarm unacknowledgment
– Collection of alarm statistics
● Performance management
– Query of historical performance data
– Query of performance threshold-crossing events
– Performance instance management, including creating, deleting,
suspending, enabling, and querying performance instances
● Inventory management
– Query of physical inventory, such as NEs, subracks, slots, boards, and
physical ports
– Query of logical inventory, such as logical ports, fibers or cables, tunnels,
and services
– Export of inventory data and report of changes in inventory
– QoS management, including query, creation, deletion, applying, and
unapplying
● Configuration management
– Provisioning of tunnel resources, such as TE tunnels, static CR tunnels,
and static tunnels
– Provisioning of service resources, such as ATM PWE3, CES PWE3, Ethernet
PWE3, VPLS, L3VPN, and PWSwitch
● Diagnosis management
– Management of MDs, MAs, MEPs, MIPs, and RMEPs based on 802.1ag,
802.3ah, and Y.1731 standards
– CC, LB, and LT tests
– Management of test suites and test cases
– BFD session management, including creating, deleting, binding, and
unbinding BFD sessions
– OAM statistics management, including query, creation, and execution
● Protection group management
– E-trunk management, including creating, deleting, and querying E-trunks
– E-APS management, including creating, deleting, and querying E-APS
protection groups

iMaster NCE-IP
4.3.1.2 CORBA NBIs

This section describes the NCE CORBA NBI functions.
Table 4-3 Performance indicators of the CORBA NBI

Number of 4
concurrent The maximum invocation concurrency of the CORBA NBI is
interface 4. If the number of invocations exceeds 4, the invocations
requests are queued.
For interfaces that involve a large amount of data, such as
getAllEquipment and getHistoryPMData, it takes a long
time for the NCE server to process the interface invocations.
A small number of concurrent interface invocations are
supported. Therefore, single-thread serial invocation is
recommended. Otherwise, an error indicating a fully loaded
task may be reported.
Alarm ≤ 100 notifications/s

notification
processing
capability
Alarm sending < 10s (3 OSSs)

delay
NOTICE
● The alarm handling capability of the CORBA NBI depends on many factors,
such as the alarm quantity on the live network, and CPU performance and
memory size of the server. At the same time, the CORBA NBI sends alarms
synchronously, that is, another alarm will not be sent until the OSS receives the
previous alarm and responds to the CORBA NBI. Therefore, the network
stability between NCE and the OSS and the handling capability of the OSS will
affect the alarm handling capability of NCE.
● If an alarm storm occurs, the CORBA NBI will possibly reach its handling limit.
The CORBA NBI can report a maximum of 1,000,000 alarms within 1 hour. For
system stability purposes, the CORBA NBI will discard some alarms if the alarm
quantity exceeds 1,000,000. You are recommended to handle network faults
instantly if an alarm storm occurs. In addition, the OSS is suggested to
synchronize alarms actively at proper time, for example, when the system is
idle.

iMaster NCE-IP
NCE-IP Functions
Complying with the TMF MTNM V3.5 series standards, the CORBA NBI enables
NCE to provide unified alarm and inventory management for IP devices.
The NCE CORBA NBI supports the following functions:
● Alarm management
– Alarm reporting
– Synchronization of active alarms
– Alarm acknowledgment
– Alarm unacknowledgment
– Alarm clearance
● Inventory management
– Query of physical inventory such as NEs and boards
● Configuration management
– Configuration of E2E services for tunnels (only for PTN devices) (static-CR
tunnel)
– Configuration of E2E services (only for PTN devices) (CES PWE3 and
Ethernet PWE3)
4.3.1.3 SNMP NBI

Complying with the SNMP v1/v2c/v3 standard, the SNMP NBI enables NCE to
provide unified alarm management for OSSs.
Table 4-4 Performance indicators of the SNMP NBI
Maximum number of concurrent OSS 10

connections
Alarm reporting efficiency More than 60 alarms per second when

three OSSs are connected
Alarm reporting delay Shorter than 10 seconds when three

OSSs are connected
Functions
The SNMP NBI supports the following functions:
● Alarm reporting
● Synchronization of active alarms
● Alarm acknowledgment

iMaster NCE-IP
● Alarm unacknowledgment
● Alarm clearance
● Heartbeat alarm reporting
● Setting of alarm filter criteria
● Alarm maintenance status reporting
4.3.1.4 Performance Text NBI (FTP/SFTP)

Through the performance text NBI, NCE can export performance data to a
specified FTP/SFTP server for the OSS to analyze.
Table 4-5 Performance indicators of the performance text NBI

Maximum number of ● As the FTP/SFTP client, NCE transmits files to one

connected OSSs OSS only.
● As the FTP/SFTP server, NCE can be accessed by a
maximum of 3 OSSs.
Functions
The NCE performance text NBI supports the following functions:
● Generates the performance text file in a unified format (*.csv).
● Exports the performance text file based on the collection period (the period
can be 5, 10, 15, 30, 60, 360, or 1440 minutes).
● Exports the performance text file at the scheduled time (5, 10, 15, 30, 60, 360,
or 1440 minutes; the time must be longer than the collection period).
● Specifies the start time to export the performance text file.
● Checks data integrity of the performance text file. If the performance text file
fails to be generated, the data will be saved to the performance text file that
will be generated in the next period.
● Transmits the performance text file to the specified FTP or SFTP server.
● Exports the performance text file by indicator.
● Specifies the start time to delete the performance text file.
● Clears earlier performance text files periodically.
● Specifies the number of data records in a single file.
4.3.1.5 REST
Complying with the IETF standard, the REST NBI of NCE provides service
management, resource management, network O&M APIs for the OSS.
REST is a software architecture style rather than a standard. It provides a set of
guidelines and constraints for designing client-server interaction software.

iMaster NCE-IP
Software in this style is more hierarchical and simpler, facilitating the

implementation of caching and other mechanisms.
Table 4-6 Performance indicators of the REST NBI
Request response 5 minutes

timeout interval
Request packet size 2 MB

limit
Response packet size 10 MB

limit
Notification reporting ≤ 500 per second

capability
Notification and alarm < 10 seconds

reporting delay
Number of ≤ 100
notification
(WebSocket&SSE)
connections
Alarm reporting Continuous reporting: ≤ 500 alarms per second; peak:

capability 1000 alarms per second (without loss in 15 seconds)
Persistence: When the number of persistent data
(alarm notifications) reaches 500,000 or the
persistence duration reaches 7 days, data will be
wrapped.
NCE-IP Functions
● Resource management
– Query of subnets, NEs, subracks (or chassis), boards, slots, ports, optical
modules, equipment rooms, racks, fiber links, customers, IGP route
processes, IGP links, tunnel protection groups, L3VPN services, VRFs, VPLS
services, PWE3 services, PW trails, PWs, service access points, tunnel
paths, tunnel interfaces, L2VPN and L3VPN bridging groups, and slices
– Reporting of resource change notifications for subnets, NEs, subracks (or
chassis), boards, slots, ports, optical modules, equipment rooms, racks,
fiber links, customers, IGP route processes, IGP links, tunnel protection
groups, L3VPN services, VRFs, VPLS services, PWE3 services, PW trails,
PWs, service access points, tunnel paths, tunnel interfaces, L2VPN and
L3VPN bridging groups, and slices
● Service management

iMaster NCE-IP
– EVPN-over-VXLAN, SR-TE, SR-MPLS TE Policy, SRv6 Policy, inter-AS SRv6

Policy, RSVP-TE, and L3VPN service provisioning
– Query of L3VPN and EVPN services as well as tunnels
– Service path computation
– Service deletion
● Network optimization
– IP traffic optimization
– MPLS traffic optimization
● Fault management
– Alarm subscription
– Alarm reporting
– Alarm synchronization
– Alarm acknowledgment/unacknowledgment
– Query of static alarm information
– Incident reporting
● Network performance analysis
– Historical performance query
Constraints:
The REST interface IDs and models are unified, including the interfaces for
provisioning L2 EVPN and L3VPN services, querying NE, board, and port inventory,
L3VPN and EVPN services, and tunnels. Other capabilities will be gradually
planned based on market requirements.
The historical performance query is limited to board and interface resources. Other
types of resources will be gradually planned based on market requirements.
4.3.1.6 Kafka
NCE Kafka is a northbound interface implemented based on the open-source
Apache Kafka. As a producer, NCE pushes data (such as inventory, alarm, event,
and performance data) to the Kafka server deployed by the customer or a third
party, through a Kafka channel. The OSS then consumes the data by subscribing
to corresponding topics on the Kafka server.
Table 4-7 Performance indicators of the Kafka NBI
Kafka instances ≤ 10
Server addresses ≤ 50 per Kafka instance
Topic subscription ≤ 20 per Kafka instance

iMaster NCE-IP
Scheduled inventory ≤ 5000 pieces/s

reporting Persistence: not supported. Because data is reported
periodically, you can wait for data in the next period if
errors occur in a period.
Inventory notification When the data push mode is asynchronous, ≤ 1000

notifications/s
When the data push mode is synchronous, ≤ 250
notifications/s (network latency is under 1 ms)
Persistence: When the size of persistent data reaches 5
GB or the persistence duration reaches 7 days, data
will be wrapped.
Alarm reporting When the data push mode is asynchronous, ≤ 1000

alarms/s
alarms/s (network latency is under 1 ms)
will be wrapped.
Event reporting When the data push mode is asynchronous, ≤ 1000

events/s
events/s (network latency is under 1 ms)
will be wrapped.
Incident reporting When the data push mode is asynchronous, ≤ 1000

incidents/s
incidents/s (network latency is under 1 ms)
will be wrapped.
Delay in inventory < 10 seconds

notification, alarm
reporting, event
reporting, and incident
reporting
Performance reporting ≤ 500 pieces/s

Persistence: not supported. Because data is reported
periodically, you can wait for data in the next period if
errors occur in a period.

iMaster NCE-IP
Functions
The OSS can receive the following messages through the Kafka NBI:
● Inventory: reports notifications upon inventory changes; reports network-wide
inventory data periodically. For details, see Table 4-8.
● Alarm: reports alarms. For details, see Table 4-9.
● Event: reports events. For details, see Table 4-10.
● Performance: reports performance data. For details, see Table 4-11.
● Incident: reports incidents. For details, see Table 4-12.
Table 4-8 Inventory reporting functions supported by the Kafka NBI

Category Content Reported Domain
Inventory Reports inventory change notifications NCE

notification based on resource types.
Inventory Periodically reports inventory data based NCE

scheduled task on resource types.
Table 4-9 Alarm reporting functions supported by the Kafka NBI

Category Function Domain
Alarm Filters current alarms based on the NCE

following:
● Service-affecting change alarms
● Severity change alarms
● Correlative alarms
● Engineering alarms
● Alarm priorities
● Resource types
● Alarm source types
● Alarm sources
● Specific alarms
● Advanced conditions ( For example:
Location information, affected services,
IP addresses and other information)

iMaster NCE-IP
Alarm Filters acknowledged and NCE

acknowledgment unacknowledged alarms based on the
/ following:
unacknowledgm ● Correlative alarms
ent
● Engineering alarms
● Alarm priorities
● Resource types
● Alarm source types
● Alarm sources
● Specific alarms
Table 4-10 Event reporting functions supported by the Kafka NBI

Event Filters events based on the following: NCE

● Resource types
● Event source types
● Event sources
● Specific events
Table 4-11 Performance reporting functions supported by the Kafka NBI

IP Analyzer Reports IP Analyzer performance data. NCE-IP

performance data NOTE
Only the
Manager
+Controller
+Analyzer
scenario is
supported.

iMaster NCE-IP
Table 4-12 Incident reporting functions supported by the Kafka NBI

Incident Filters incidents based on the following: NCE

● Incident priority
● Resource types
4.3.2 SBIs
Using southbound interfaces (SBIs), NCE can interconnect with physical-layer
network devices to implement management and control functions.
The IP NEs that NCE-IP can manage include NE series routers, CX series routers,
Ethernet switches, BRASs, ATN devices, and security devices.
Table 4-13 SBI functions supported by NCE-IP

SBI Type Description Supported IP NEs
SNMP SNMP is a TCP/IP-based network management protocol All IP NEs

at the application layer. SNMP uses the UDP protocol at
the transmission layer. Through the SNMP SBI, NCE can
manage network devices that support agent processes.
NCE supports the SNMP SBI that complies with
SNMPv1, SNMPv2c, and SNMPv3. Through the SNMP
SBI, NCE can connect to devices. The SNMP SBI
supports basic management functions such as discovery
of network devices, service configuration data
synchronization, fault management, and performance
management.
Telnet/STelnet The Telnet and STelnet SBIs are a basic type of interface All IP NEs
used for remote login to and management of NEs. The
Telnet and STelnet SBIs address the disadvantages of
the SNMP SBI and allow NCE to provide more
management functions.
● Through the Telnet SBI, users can log in to an NE in
the CLI and run commands directly in the CLI to
maintain and configure the NE. Telnet is a TCP/IP-
based network management protocol at the
application layer. Telnet uses the TCP protocol at the
transmission layer and provides services for network
communication. Telnet transmits communication
data in plain text, which is not secure.
● STelnet provides secure Telnet services based on SSH
connections. Providing encryption and
authentication, SSH protects NEs against attacks of
IP address spoofing.

iMaster NCE-IP
TFTP/FTP/SFTP TFTP, FTP, and SFTP are TCP/IP-based network All IP NEs
management protocols at the application layer and are
dependent on the UDP protocol.
● TFTP is a simple and low-overhead protocol (as
compared with FTP and SFTP) used to upload and
download files. TFTP does not support password
configuration and transfers file contents in plain
text.
● FTP is a set of standard protocols used for
transferring files on networks. FTP transfers
passwords and file content in plain text.
● SFTP uses the SSH protocol to provide secure file
transfer and processing. For data backup using SFTP,
passwords and data are encrypted during
transmission.
Routers and switches whose VRP version is 5.7 or later
use the TFTP, FTP, or SFTP SBI to synchronize data with
NCE. IP NEs use NE Software Management to
implement functions such as NE upgrades, backup, and
patch installation.
Syslog The Syslog SBI serves as an interface for NCE to receive All IP NEs
system logs from NEs. With the Syslog SBI, NCE can
manage NE logs. IP NEs support Syslog running logs.
ICMP ICMP is a network-layer protocol. It provides error All IP NEs

reports and IP packet processing messages that will be
sent back to the source. ICMP is usually used as an IP-
layer or higher-layer protocol and ICMP packets are
usually encapsulated in IP packets for transmission.
Some ICMP packets carry error packets that will be sent
back to NEs.
NETCONF ● NETCONF is used to manage network data device VRPv8-based routers

configurations. This protocol is designed to (NE, NetEngine, and
supplement the SNMP and Telnet protocols for CX series)
network configuration.
● NETCONF defines a simple mechanism for installing,
manipulating, and deleting the configurations of
network devices. NETCONF uses XML-based data
encoding for the configuration data and protocol
messages. In an automatic network configuration
system, NETCONF plays a crucial role.
NetStream NetStream is a network traffic collection protocol based ATN, CX, ETN, ME,
on UDP transmission, which reports network traffic NE, NetEngine, and
collection results to Analyzer. By using this protocol, PTN series NEs
Analyzer can be aware of the volume, source, and
destination of network traffic.

iMaster NCE-IP
Telemetry Telemetry is an efficient performance data collection ATN, CX, ETN, MA,
technology. It uses efficient data formats and ME, NE, NetEngine,
transmission modes such as Google Protocol Buffer PTN, and VNE series
(GPB) and gRPC Remote Procedure Calls (gRPC), NEs
collects data by means of subscription and push, and
supports seconds-level data sampling.
PCEP PCEP is used by the controller to control tunnel paths NE, NetEngine, CX,
on forwarders in MPLS network optimization scenarios. ATN, and PTN series
NEs
BGP-LS BGP-LS is used by the SDN controller to collect network
topology information from forwarders. The router
collects information such as network topology,
bandwidth, and packet loss using IGP (such as OSPF
and IS-IS), and then sends the information to the SDN
controller using BGP-LS. Then the SDN controller
computes service paths based on the information.
BGP FlowSpec BGP FlowSpec routes are new BGP routes and carry
traffic matching rules and actions. The SDN controller
delivers BGP FlowSpec routes to forwarders to
implement traffic optimization.
BGP RPD BGP-Route Policy Distribute (RPD) is used by the SDN

controller to send traffic optimization policy routes to
forwarders in inbound traffic optimization scenarios.
4.4 Southbound DCN Networking

NCE and each managed device communicate with each other through the internal
data communication network (DCN) or external DCN. The two modes can also be
used together for DCN networking.
NOTE
For details about the bandwidth requirements of the southbound DCN, see 6.6 Bandwidth
Configurations.
Internal DCN Networking

In internal DCN networking, NCE uses the communication channels provided by
managed devices to transmit management and control information and
implement network management and control.
In this mode, the managed network is generally divided into multiple DCN
subnets. NCE directly communicates with one NE in each subnet called the
gateway NE (GNE). The communication between NCE and the other NEs in the
subnet is forwarded by the GNE. If NCE and the GNE are in the same equipment
room, they can be connected through LAN; otherwise, they need to be connected
through private lines.

iMaster NCE-IP
Figure 4-4 Internal DCN networking
Internal DCN networking has the following characteristics:

● Advantages: Internal DCN networking is flexible, device-independent, and
cost-effective.
● Disadvantages: When a network fault occurs and the communication channel
between NCE and the managed network is interrupted, NCE cannot maintain
the related devices.
External DCN Networking

In external DCN networking, NCE uses the communication channels provided by
intermediate devices on an external DCN network to transmit management and
control information to managed devices and implement network management
and control. Generally, the managed devices connect to the external DCN through
the management ports on their system control boards.
In this mode, the NCE is connected to the devices on the managed network
through the DCN consisting of other devices. Generally, the managed devices
connect to the external DCN through the management ports on their system
control boards.

iMaster NCE-IP
Figure 4-5 External DCN networking
External DCN networking has the following characteristics:

● Advantages: External DCN networking allows NCE to connect to the managed
network through other devices. When a managed device is faulty, the device
will not be unreachable from NCE due to the fault of the managed device.
● Disadvantages: External DCN networking requires the construction of an
independent maintenance network that provides no service channels, which
makes network deployment expensive.

iMaster NCE-IP
Product Description (x86,enterprise) 5 Deployment Schemes
5 Deployment Schemes
Based on whether Huawei provides E2E support for software and hardware, NCE
supports two deployment modes: on-premises and private cloud.
5.1 On-Premises Deployment

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.
Depending on whether a virtualization platform is required, on-premises
deployment can be further classified into physical machine deployment and VM
deployment. Generally, factory installation has been completed for NCE before
delivery.
5.2 Deployment on Private Clouds
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.
5.3 EasySuite Deployment Tool
In the on-premises and private cloud scenarios where factory installation is not
performed, EasySuite is used to install and deploy NCE.
5.1 On-Premises Deployment

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.
Depending on whether a virtualization platform is required, on-premises
deployment can be further classified into physical machine deployment and VM
deployment. Generally, factory installation has been completed for NCE before
delivery.
5.1.1 Deployment on Physical Machines

NCE Manager or NCE Manager+Controller+Analyzer (centralized) can be directly
installed and deployed on physical machines (bare metal).

iMaster NCE-IP
System Networking
Based on different system protection expectations, deployment on physical
machines can be divided to two modes: single site and disaster recovery (DR).
● Single site: A complete set of NCE is deployed in a place with internal
protection enabled.
CAUTION
Table 5-1 lists the comparison of the protection solutions between the single-
site system and the DR system. The DR system is recommended to ensure the
reliability and continuity of NCE.
The table contains the following columns:
● Local Hardware Protection: implements hard disk RAID and hardware
redundancy, such as power supply and fan redundancy, NIC 1+1 bond, and
switch redundancy.
● Local Application Protection: deploys VM nodes in active/standby or cluster
mode.
● Site Protection: implements the DR solution.
Table 5-1 Comparison of the protection solutions between the single-site

system and the DR system
Scenario Local Local Site Fault Scenario and Risk
Hardw Applic Protec
are ation tion
Protect Protec Soluti
ion tion on
Single-site Yes No No ● When a server fault,

system, software fault, or site fault
Manager, occurs, NCE may fail to
centralized recover promptly.
Manager ● During the software and
+Controller hardware upgrade, NCE
+Analyzer, or services need to be stopped
compact and network monitoring is
Manager interrupted.
+Controller
+Analyzer

iMaster NCE-IP

Hardw Applic Protec
are ation tion
ion tion on
Single-site Yes Yes No ● When multiple servers are

system, faulty, the software is faulty
distributed on multiple nodes, or a site
Manager fault occurs, NCE may fail to
+Controller recover promptly.
+Analyzer ● During the software and
hardware upgrade, NCE
services need to be stopped
and network monitoring is
interrupted.
DR system Yes Yes Yes ● When the primary site is

(recommend faulty, the secondary site
ed) takes over services to ensure
the normal running of the
system.
● During the software and
hardware upgrade, you can
upgrade the primary and
secondary sites in different
periods of time to ensure
that the system is running
properly.
● 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.

iMaster NCE-IP
Figure 5-1 NCE system networking (physical machine, single site)

iMaster NCE-IP
Figure 5-2 NCE system networking (physical machine, DR)
Software Deployment Mode

NCE uses the Browser/Server (B/S) architecture for software deployment during
deployment on physical machines. You can easily access NCE through a browser
without installing traditional clients.
In the NAT scenario, the clients can communicate with the NCE server properly.
Figure 5-3 NCE software deployment mode on physical machines
5.1.2 Deployment on VMs

In the distributed Manager+Controller+Analyzer and compact Manager+Controller
+Analyzer scenarios, NCE can be installed and deployed on the VM platform
virtualized from physical machines.

iMaster NCE-IP
Single Site and DR System

Based on different system protection expectations, deployment on virtual
machines can be divided to two modes: single site and disaster recovery (DR).
protection enabled.
CAUTION
switch redundancy.
mode.

Hardw Applic Protec
are ation tion
ion tion on

+Controller
+Analyzer

iMaster NCE-IP

Hardw Applic Protec
are ation tion
ion tion on

interrupted.

system.
properly.

iMaster NCE-IP
Figure 5-4 NCE system networking (VM, single-server)

iMaster NCE-IP
Figure 5-5 NCE system networking (VM, DR)
NOTE
● The management DCNs of the primary and secondary sites can be isolated from each
other or not.
● The DR system requires high bandwidth. A replication link must be configured between
the primary and secondary sites.

NCE uses the B/S architecture for software deployment during deployment on
VMs. Users can easily access NCE through a browser without installing traditional
clients.
Figure 5-6 NCE software deployment mode on VMs

iMaster NCE-IP
5.2 Deployment on Private Clouds

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.
Single Site or DR System

Depending on system protection requirements, NCE can be deployed either at a
single site or as a DR system in private cloud deployment scenarios.

protection enabled.
CAUTION
switch redundancy.
mode.


Hardw Applic Protec
are ation tion
ion tion on

+Controller
+Analyzer

iMaster NCE-IP

Hardw Applic Protec
are ation tion
ion tion on

interrupted.

system.
properly.

iMaster NCE-IP
Figure 5-7 NCE system networking (private cloud, single-server)

iMaster NCE-IP
Figure 5-8 NCE system networking (private cloud, DR)
NOTE
The DR system requires high bandwidth. A replication link must be configured between the
primary and secondary sites.

NCE uses the B/S architecture for software deployment during deployment on
private clouds. Users can easily access NCE through a browser without installing
traditional clients.

iMaster NCE-IP
Figure 5-9 NCE software deployment in private cloud mode
5.3 EasySuite Deployment Tool

In the on-premises and private cloud scenarios where factory installation is not
performed, EasySuite is used to install and deploy NCE.
Basic Concept
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 create an NCE installation project simplifies installation and
deployment operations and improves efficiency.
Operations in Each Installation Scenario
Table 5-4 Deployment operations on EasySuite
Deployment Solution EasySuite One-Click Installation
On-premises deployment on physical 1. Configure hardware, including

machines configuring RAID and hardware
alarm reporting parameters.
2. Install and configure the OS.
3. Install NCE, including installing the
database.
On-premises deployment on virtual 1. Configure hardware, including

machines configuring RAID and hardware
alarm reporting parameters.
2. Set up the virtualization layer,
including installing CNA and VRM
and configuring CNA hosts and
networks (including configuring
virtual switches and port groups).
3. Install VMs, including installing and
configuring the OS.
database.

iMaster NCE-IP
Deployment Solution EasySuite One-Click Installation
Deployment on private clouds 1. (Optional) Install VMs, including

installing and configuring the OS.
database.

iMaster NCE-IP
Product Description (x86,enterprise) 6 Configuration Requirements
6 Configuration Requirements
NCE has specific requirements on the hardware, software, client, and bandwidth to
ensure the stable running of the system.
6.1 Server Hardware Configurations for On-Premises Deployment
6.2 Server VM Configurations for Private Cloud Deployment
6.3 Server Resource Configurations (SUSE, Product Only)
6.4 Server Software Configurations
6.5 Client Configurations
6.6 Bandwidth Configurations
6.1 Server Hardware Configurations for On-Premises

Deployment
For detailed specifications, see Server Hardware Specifications.
Product For Enterprises
NCE-IP x86: Obtain the document from the following link: iMaster NCE-IP
Server Hardware Specifications
6.2 Server VM Configurations for Private Cloud

Deployment
In private cloud scenarios, customers need to prepare resources based on the
network type, functional unit combination, and network scale difference.
Configuration Constraints
● Do not configure CPU, memory, or storage overcommitment. Otherwise, NCE
performance will deteriorate.

iMaster NCE-IP
NOTE
Overcommitment is a virtualization technology that allocates more virtual resources

than physical resources to VMs. For example, if the physical memory size is 32 GB,
more than 32 GB memory can be allocated to VMs through overcommitment.
● VM resources must be exclusively occupied. NCE VMs cannot share resources
with other applications.
● Reliability protection must be configured for storage resources. For example,
RAID is configured for disks.
● The management network must be isolated from the service network to
improve network security. For example, VLANs are used to isolate networks.
● NCE has high requirements on input/output operations per second (IOPS) and
I/O delay of storage devices. You are advised to use high-performance storage
for database nodes, for example, centralized SSD all-flash storage. Do not use
distributed storage solutions (such as FusionStorage) or SATA HDDs.
● If HDDs are used, the rotational speed must be greater than or equal to
10000 revolutions per second, and the distributed storage solution is not
recommended.
Table 6-1 VM resources required for NCE-IP
Service Network VMs vCPU Mem Stora I Re W I/O Rea

Scenario Scale s ory ge O ad rit Blo d/
(GB) (GB) P D e ck Wri
S el De Siz te
ay la e Rat
( y (K io
m (m B)
s) s)
Manager < 2000 2 24 96 650 1 5 5 16 2:8

(single equivalent 5
domain) NEs 0
0
< 6000 2 40 160 700 2 5 5 16 2:8

equivalent 0
NEs 0
0
< 15,000 3 64 256 1050 3 5 5 16 2:8

equivalent 0
NEs 0
0
< 30,000 4 104 416 1350 4 5 5 16 2:8

equivalent 5
NEs 0
0

iMaster NCE-IP
VM Resource Configurations for NCE Manager+Controller+Analyzer
Table 6-2 VM resources required for NCE-IP

Service Networ VMs vCP Mem Stora IO Re W I/O Re
Scenario k Scale Us ory ge PS ad rit Blo ad/
(GB) (TB) De e ck Wri
lay De Siz te
(m la e Rat
s) y (K io
( B)
m
s)
Manager < 6000 23 224 896 9 10 5 5 16 2:8

+Controller equival 46
(MPLS ent NEs 0
network)
+Analyzer
(basic
analysis)
Manager 6000– 26 292 1168 14 12 5 5 16 2:8

+Controller 15,000 48
(MPLS equival 0
network) ent NEs
+Analyzer
(basic
analysis)
Manager 15,000– 35 400 1600 19 16 5 5 16 2:8

(MPLS equival 0
network) ent NEs
+Analyzer
(basic
analysis)
Manager 30,000– 73 912 3648 55 32 5 5 16 2:8

(MPLS equival 0
network) ent NEs
+Analyzer
(basic
analysis)
Manager < 6000 23+ 224+ 896+ 13.45 10 5 5 16 2:8

+Controller equival 6*n 80*n 320* +8.52 46
+Analyzer( ent NEs n *n 0+
Basic+IFIT) 30
00*
n

iMaster NCE-IP
Service Networ VMs vCP Mem Stora IO Re W I/O Re

Scenario k Scale Us ory ge PS ad rit Blo ad/
(GB) (TB) De e ck Wri
lay De Siz te
(m la e Rat
s) y (K io
( B)
m
s)
Manager 6000– 26+ 292+ 1168 16.95 12 5 5 16 2:8

+Controller 15,000 6*n 80*n +320 +8.52 48
+Analyzer( equival *n *n 0+
Basic+IFIT) ent NEs 30
00*
n
Manager 15,000– 35+ 400+ 1600 23.5+ 32 5 5 16 2:8

+Controller 30,000 6*n 80*n +320 8.52* 56
+Analyzer( equival *n n 0+
Basic+IFIT) ent NEs 30
00*
n
Manager < 6000 28 304 1216 12.55 13 5 5 16 2:8

+Controller equival 00
+Analyzer( ent NEs 0
Basic)+NIC
NOTE
1. The IOPS of each VM must meet the single-node planning requirements in each
deployment scenario. For details, see the VM planning in the HLD on EasySuite.
2. The recommended IOPS is the overall IOPS requirement for the running of NCE. If the
system does not meet this requirement, exceptions such as slow system response and
slow backup may occur, affecting the running of NCE.
3. In the Manager+Controller+Analyzer(Basic+IFIT) scenario, n is an integer from 1 to 5,
and the corresponding IFIT specifications are as follows:
● Mobile transport service assurance (IFIT): IP RAN IFIT (8000 x n base stations) or
PTN IFIT (10,000 x n base stations)
● VPN service assurance: 240,000 x n flows
VM Resource Configurations for the NCE DR Arbitration Site
Table 6-3 VM resources required for the NCE DR arbitration site

Service Scenario Network VMs vCPUs Memory Storage
Scale (GB) (GB)
DR arbitration - 1 4 16 150

iMaster NCE-IP
6.3 Server Resource Configurations (SUSE, Product

Only)
VM Configuration Constraints
● Do not configure CPU, memory, or storage overcommitment. Otherwise, NCE
performance will deteriorate.
NOTE
Overcommitment is a virtualization technology that allocates more virtual resources

than physical resources to VMs. For example, if the physical memory size is 32 GB,
more than 32 GB memory can be allocated to VMs through overcommitment.
● VM resources must be exclusively occupied. NCE VMs cannot share resources
with other applications.
● Reliability protection must be configured for storage resources. For example,
RAID is configured for disks.
● The management network must be isolated from the service network to
improve network security. For example, VLANs are used to isolate networks.
Resource Configurations
Table 6-4 Hardware resources required for physical machine deployment of NCE-
IP Manager in the product only scenario
Service Network CPU Memory Storage NIC IOP
Scenari Scale Size (GB) S
o (GB)
Manag < 2000 2.0 GHz, 24 128 650 1 x 4 GE 150

er equivalent cores 0
NEs

iMaster NCE-IP
Table 6-5 VM resources required for private cloud deployment of NCE-IP Manager
in the product only scenario
Servi Networ V vCPUs Memor Storage I Re W I/O Rea
ce k Scale M y (GB) (GB) O ad rit Blo d/
Scen s P D e ck Wri
ario S el De Siz te
ay la e Rat
( y (K io
m (m B)
s) s)
Mana < 2000 2 24 96 Custome 1 5 5 16 2:8

ger equivale r- 5
nt NEs provided 0
SUSE OS: 0
650
Huawei-
delivered
SUSE OS:
712
6.4 Server Software Configurations

Table 6-6 Server configurations (x86)
Item Type Version Remarks
Deliv Virtuali FusionCompute 8.3.0 Used on x86 servers in

ered zation the on-premises scenario.
softw softwar
are e
confi
gurati OS EulerOS V200R010C00 Used on x86 servers in
ons the on-premises and
private cloud scenarios.
Databa Druid 0.21.1 NCE Analyzer

se
GaussDB T V3 (also called OMP node
Gauss100 OLTP 1.5.1) NCE Manager
NCE Analyzer
Controller

iMaster NCE-IP
Comp Virtuali ● FusionSphere OpenStack Used only in the private

atible zation 22.1.0 cloud scenario.
softw softwar ● FusionSphere OpenStack 8.0.0
are e
NOTE
confi You need to confirm the following
gurati key information with the
ons customer in advance:
1. If IPv6 is required for NCE
deployment, check whether
the customer's private cloud
supports IPv6.
2. Check whether the customer's
private cloud meets the
requirements in 6.2 Server
VM Configurations for
Private Cloud Deployment.
FusionCompute 8.2.0 -
FusionCube 8.0.0 or later Used only in the private

cloud scenario.
OS EulerOS V200R007 (EulerOS 2.5), -

EulerOS V200R008 (EulerOS 2.8),
and EulerOS V200R009 (EulerOS
2.9)
Table 6-7 Server software configurations (SUSE) (for enterprises)

Comp OS ● Customer provided: SUSE Used in the scenario

atible Linux Enterprise Server 12 SP5 where the SUSE OS is
softw ● Huawei delivered: SUSE Linux compatible.
are Enterprise Server 12 SP5
confi
gurati Databa GaussDB T V3 (also called Used to store NCE
ons se Gauss100 OLTP 1.5.1) product data.

iMaster NCE-IP
6.5 Client Configurations

Table 6-8 Client configurations
Type Requirements
PC Minimum configuration:
● CPU: 2 cores, 2.6 GHz
● RAM: 4 GB
● Hard disk: 8 GB
NOTE
When you access NCE in an environment with the minimum configuration,
frame freezing may occur. You are advised to use the recommended
configuration.
Recommended configuration:
● RAM: 8 GB
● Hard disk: 8 GB
Cloud Minimum configuration:

desktop ● CPU: 4 cores, 2.6 GHz
● RAM: 4 GB
● Hard disk: 8 GB
NOTE
When you access NCE in an environment with the minimum configuration,
frame freezing may occur. You are advised to use the recommended
configuration.
Recommended configuration:
● RAM: 8 GB
● Hard disk: 8 GB
OS Windows 10 (32-bit or 64-bit)
Browse ● Google Chrome 90 or later (32-bit or 64-bit)

r ● Firefox 89 or later (32-bit or 64-bit)
● Firefox 78 ESR or later (32-bit or 64-bit)
● Microsoft Edge 90 or later (64-bit)
NOTE
● You are advised not to configure the browser proxy. If you need to configure
the proxy, either of the following conditions must be met to ensure normal
access to NCE:
● The configured proxy supports HTTPS and WebSocket.
● Add "IP address of the O&M plane" to the proxy server address whitelist
so that NCE can be accessed without using the proxy.

iMaster NCE-IP
Type Requirements
Resoluti 1366 x 768 px or higher; recommended resolution: 1920 x 1080 px

on 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.
6.6 Bandwidth Configurations

Table 6-9 Bandwidth requirements
Type Requirements
Network delay ● Between NCE and external systems (client, NE, and third-
party arbitration site): < 50 ms
● Between NCE and the OSS: < 20 ms
● Between NCE VM nodes: < 1 ms
● Between the primary and secondary sites of the NCE DR
system: < 50 ms (< 20 ms if the Controller is contained)
Packet loss rate ● Between NCE and external systems (client, NE, and third-
party arbitration site): < 1%
● Between NCE and the OSS: < 1%
● Between NCE VM nodes: < 0.2%
● Between the primary and secondary sites of the NCE DR
system: < 1% (< 0.1% if the Controller is contained)
Bandwidth ≥ 1000 Mbit/s

between VMs
Bandwidth Bandwidth recommended for a client: ≥ 10 Mbit/s

between the Bandwidth between the server and clients = Bandwidth for a
server and client x Number of clients
clients
Bandwidth Bandwidth for each OSS: ≥ 10 Mbit/s

between the Bandwidth between the server and OSSs = Bandwidth for
server and OSSs each OSS × Number of OSSs. For example, if three OSSs
interconnect with the same NCE through REST interfaces, the
minimum bandwidth is 30 Mbit/s (3 x 10 Mbit/s). If there
are two OSSs, with one interconnecting with NCE through
the REST interface and the other interconnecting with NCE
through the SNMP interface, the minimum bandwidth is 20
Mbit/s (10 Mbit/s + 10 Mbit/s).

iMaster NCE-IP
Type Requirements
Bandwidth The Manager, Analyzer, and Controller have different

between the bandwidth requirements. The required minimum bandwidth
server and NEs is the sum of bandwidths for deploying the Manager,
Analyzer, and Controller.
● Controller Committed Information Rate (CIR): N x 2 kbit/s
(at least 4 Mbit/s)
Peak Information Rate (PIR): N x 10 kbit/s (at least 10
Mbit/s)
● Manager CIR: N x 0. 5 kbit/s (at least 2 Mbit/s); PIR: N x 5
kbit/s (at least 10 Mbit/s) (In different networks, the 2
Mbit/s bandwidth may not meet the bandwidth
requirement of the live network.) In this case, you can use
formulas to determine the CIR and PIR. Network-wide
data synchronization, performance data collection, and
batch upgrade require high bandwidth. Therefore, it is
recommended that the live network bandwidth meet the
PIR requirement.
● Analyzer bandwidth
– (1) Basic performance collection: CIR = N x 0.002
Mbit/s (minimum: 4 Mbit/s), PIR = N x 0.01 Mbit/s
(minimum: 20 Mbit/s)
– (2) SNMP+Telemetry performance collection in NCE-IP
Manager+Controller+Analyzer (excluding PTN): CIR =
N x 0.015 Mbit/s, PIR = N x 0.15 Mbit/s
– (3) Basic performance collection in mobile transport
service assurance of NCE-IP Manager+Controller
+Analyzer:
The IP RAN uses the management plane: CIR = M x
0.008 Mbit/s, PIR = M x 0.08 Mbit/s
The PTN uses the control plane: CIR = M x 0.0112
Mbit/s, PIR = M x 0.336 Mbit/s
– (4) NetStream collection in NCE-IP Manager
+Controller+Analyzer (excluding PTN): If the sampling
ratio is 1000:1 and the live-network traffic is 1 Tbit/s,
the CIR needs to be 200 Mbit/s.
– In the hybrid collection scenario, the bandwidth of the
used collection protocols needs to be accumulated. For
example, in the IP RAN with the mobile transport
service assurance feature of Analyzer, SNMP+Telemetry
performance collection of Analyzer and basic
performance collection of mobile transport service
assurance are used, and therefore the total bandwidth
is (2)+(3). In the PTN with the mobile transport service
assurance feature of Analyzer, the basic performance
collection of Analyzer and that of mobile transport
service assurance are used, and therefore the total
bandwidth is (1)+(3).

iMaster NCE-IP
Type Requirements
NOTE
M indicates the number of base stations, and N indicates the
number of equivalent NEs.
Bandwidth In a DR system, a replication private line is established

between the between the primary and secondary sites for real-time data
primary and synchronization.
secondary sites CIRs of the replication link bandwidth are as follows:
of the DR system
(Manager ● If N is 6000, the CIR is 60 Mbit/s.
+Controller, ● If N is 15,000, the CIR is 100 Mbit/s.
Manager ● If N is 30,000, the CIR is 200 Mbit/s.
+Controller
+Analyzer) ● If N is 50,000, the CIR is 300 Mbit/s.
● If N is 80,000, the CIR is 500 Mbit/s.
● If N is 150,000, the CIR is 1 Gbit/s.
NOTE
N indicates the number of equivalent NEs.
Bandwidth In a DR system, a replication private line is established

between the between the primary and secondary sites for real-time data
primary and synchronization. The bandwidth requirements vary according
secondary sites to scenarios.
of the NCE ● Bandwidth for NCE Manager without performance data
Manager DR collection: Table 6-10
system
● Bandwidth for NCE Manager with SNMP performance
data collection: Table 6-11
● Bandwidth for NCE Manager with transport NE
performance data collection: Table 6-12
Bandwidth ≥ 2 Mbit/s
between the DR
system and the
third-party
arbitration site
Table 6-10 Bandwidth between the primary and secondary sites of the NCE
Manager DR system (without performance data collection)
Network Scale Minimum Bandwidth Recommended

Bandwidth
< 2000 equivalent NEs 8 Mbit/s 12 Mbit/s
2000–6000 equivalent NEs 12 Mbit/s 30 Mbit/s
6000–15,000 equivalent NEs 30 Mbit/s 60 Mbit/s
15,000–30,000 equivalent NEs 60 Mbit/s 100 Mbit/s

iMaster NCE-IP
Manager DR system (with SNMP performance data collection)
Network Scale Performance Minimum Recommen
Collection Capability Bandwidth ded
Without Max/Min Bandwidth
Data Aggregation
(Unit: Max Equivalent
Records/15 Minutes)
< 2000 equivalent NEs 20000 12 Mbit/s 20 Mbit/s
2000–6000 equivalent 60000 24 Mbit/s 60 Mbit/s

NEs
6000–15,000 150000 56 Mbit/s 100 Mbit/s

equivalent NEs
15,000–30,000 150000 88 Mbit/s 200 Mbit/s

equivalent NEs
Manager DR system (with transport NE performance data collection)
Network Scale Minimum Recommended
Bandwidth Bandwidth
< 2000 equivalent NEs (number 12 Mbit/s 20 Mbit/s

of performance monitoring
instances: 20,000)
2000–6000 equivalent NEs 18 Mbit/s 60 Mbit/s

(number of performance
monitoring instances: 40,000)
6000–15,000 equivalent NEs 40 Mbit/s 100 Mbit/s

15,000–30,000 equivalent NEs 72 Mbit/s 200 Mbit/s


iMaster NCE-IP
Product Description (x86,enterprise) 7 Functions and Features
7 Functions and Features
NCE user-facing scenarios provide cloud-based network management, control, and

analysis optimization.
7.1 App List
7.2 System and Common Functions
7.3 Network Management
7.4 Service Provisioning
7.5 Analysis and Assurance
7.6 Agile Open Container
7.7 Northbound Integration
7.1 App List

The supported capabilities vary depending on the deployment scenarios. The
following table lists the involved apps.
Table 7-1 NCE-IP app list

Deployment Available Apps
Scenario
Manager (physical Network Management, Alarm Monitor, Security

machine) Management, System Settings, Agile Open Container,
and Data Collector
Manager (private Network Management, Alarm Monitor, Security

cloud) Management, System Settings, and Data Collector

iMaster NCE-IP
Deployment Available Apps

Scenario
Manager+Controller Network Management, Alarm Monitor, Security

(MPLS network) Management, System Settings, Data Collector, Agile
+Analyzer (basic Open Container, Open API & Tool, Network Path
analysis) Optimization, Network Slicing, Network Performance
Analysis, VPN Service Assurance, and Intelligent
Incident Management

+Analyzer (basic Management, System Settings, Data Collector, Agile
analysis+IFIT) Open Container, Open API & Tool, Network Path
Optimization, Network Slicing, Network Performance
Incident Management

+Analyzer (basic Management, System Settings, Data Collector, Agile
analysis)+NIC Open Container, Open API & Tool, Network Path
Incident Management
NOTE
Compared with Manager+Controller (MPLS network)
+Analyzer (basic analysis), the Application Optimization
feature in this scenario supports NetStream collection.

+Analyzer (physical Management, System Settings, Data Collector, Agile
machine) Open Container, Open API & Tool, Network Path
Incident Management
Table 7-2 Scenario-specific apps supported by NCE-IP
App Name Description
System Settings This app provides functions such as license management,

message broadcast, remote notification, and southbound
system interconnection.
Security This app provides functions such as user management

Management and security policies to effectively prevent unauthorized
users from intruding into the system, thereby keeping
system data secure.
Alarm Monitor This app monitors and manages the alarms and events
reported by the system itself or managed objects (MOs).
It provides a rich set of rules to help users efficiently
monitor, locate, and handle network faults in different
scenarios.

iMaster NCE-IP
Network ● This app provides basic management functions, such as

Management security management, topology management, fault
management, performance management, and
inventory management.
● It implements service deployment for multiple types of
tunnels (such as static tunnels, dynamic tunnels, SR-
MPLS TE Policies, and SRv6 Policies) and VPNs (such as
MBGP L3VPN and L2EVPN) and manages these
services.
NOTE
Path computation and optimization for dynamic tunnels and
SR Policies depend on controllers. Select a deployment
scenario that contains a controller.
● This app also provides maintenance functions such as
network adjustment, service cutover, and fault
diagnosis.
Data Collector This app can collect data about network inspection,
network faults, network evaluation, topologies, and
network designs.
Network Path This app computes the optimal E2E forwarding paths and
Optimization optimizes the paths as required. It centrally configures
and manages network topology information to leverage
the full potential of network resources.
Agile Open Based on YANG models, Agile Open Container (AOC)

Container provides E2E open programmability capabilities, including
device driver programmability, network service
programmability, open NBIs regarding devices and
services, as well as secure and reliable assurance
mechanisms.
Open API & Tool This app presents NCE NBI capabilities through open APIs
and provides tool suites to meet API customization
requirements.
VPN Service This app presents VPN service quality and traffic
Assurance information in multiple dimensions, such as overview,
topology, and report, helping users quickly learn the
running status of the VPN network. IFIT, TWAMP, and Y.
1731 technologies are used to visualize the SLAs of VPN
services. IFIT technology possesses VPN path restoration,
segment-by-segment detection, and SLA analysis
capabilities, enable real-time accurate fault demarcation
and locating.
Network As a network experience awareness, decision making, and

Performance big data analysis center, this app provides a user-friendly
Analysis visualized approach to help users monitor network traffic
and quality in real time, detect network changes, and
improve O&M efficiency at lower OPEX.

iMaster NCE-IP
Intelligent Incident For the intelligent metro networks (IP RAN) that are more
Management complex and have wider connections and higher O&M
requirements, a two-layer AI architecture is constructed
between NEs and NCE, and online NCE training and real-
time inference are adopted to provide E2E intelligent
O&M capabilities, such as incident management,
transforming traditional passive O&M based on
complaints into proactive O&M for prevention.
7.2 System and Common Functions
7.2.1 System Settings

NCE connects to southbound systems and O&M interfaces of different systems,
and supports functions such as license management and remote notification.
Interconnection With Southbound Systems

NCE is integrated with Huawei or third-party systems to quickly access NEs and
obtain the NE resources, alarm and performance data, and virtual resources
required for NCE service provisioning or assurance, which improves interconnection
efficiency.
● Configuring and managing a southbound driver: Before interconnecting NCE
with a southbound system, users can import external drivers by means of
management and configure SNMP drivers to quickly adapt to NEs and service
models (resources, alarms, and performance) of the peer system. This
achieves quick driver development and access and improves interconnection
efficiency. Users can also query driver types and monitor and delete driver
instances to achieve unified driver management.
● Interconnecting with a southbound system: Users can interconnect NCE with a
Huawei or third-party system and update certificates to manage NEs or
virtual resources. After login, users can obtain basic information of the NEs,
such as NE and port resources, alarms, and performance data, and collect VM
images, networks, and firewalls.
License Management
Updating and maintaining a license allows the system to properly run based on
the features, versions, capacity, and validity period authorized in a license file.
License management allows users to initially load, update, and routinely maintain
licenses.
● Initially loading a license
After the system is deployed, users need to load a license by importing license
files so that they can use the system properly.
● Updating a license

iMaster NCE-IP
During O&M, users need to update a license file under any of the following
conditions:
– The license is about to expire.
– The license has expired.
– The license is invalid.
● Routine license maintenance
Users need to query license information in the system from time to time, such
as the expiration time, consumption, and capacity, so that they can quickly
identify and resolve problems (for example, a license is about to expire or its
capacity on resource control items or sales information items is insufficient).
Remote Notification
The notifications feature applies to scenarios where network O&M personnel
cannot view alarms or events in a timely manner during non-working time or
business trips, and where O&M personnel need to send notifications to relevant
personnel.
● If network O&M personnel cannot view alarms or events onsite in a timely
manner during non-working time or business trips, the alarms and events are
sent to them in the form of emails or SMS messages.
After setting notification parameters, O&M personnel set the message content
and message sending rules. Then, the system automatically sends alarms and
events to relevant personnel in the form of SMS messages or emails through
its interconnected SMSGW or mail server.
● O&M personnel need to send some notifications to relevant personnel.
O&M personnel can manually edit message contents to be sent or use set
notification templates after setting notification parameters. O&M personnel
can manually enable the system to send SMS messages and emails to
relevant personnel so that they can obtain information about the alarms and
events.
Figure 7-1 shows the principles of the notifications feature.

iMaster NCE-IP
Figure 7-1 Principles of the notifications feature
● Automatic and manual modes are supported.

– Automatic mode: O&M personnel set the message content and message
sending rules. Then, NCE automatically sends alarms and events to
relevant personnel in SMS messages or emails through the SMSGW or
mail server connected to NCE.
– Manual mode: O&M personnel manually edit message contents to be
sent or use preset notification templates, and trigger NCE to send SMS
messages and emails to relevant personnel so that they can obtain
information about the alarms and events.
● The notifications can be sent by SMS message or email.
Table 7-3 Notification sending modes
Form Sending Description

Mode
SMS SMS Third-party SMS gateway, which is maintained by

gateway O&M personnel from the user network.
The notifications feature allows O&M personnel to
set a default SMSGW and its parameters, ensuring
successful interconnection between the SMSGW and
the system.
SMS SMS gateway settings will not take effect after the
modem SMS modem is set. Sending SMS messages by the
SMS modem is slower than by the SMS server. You
are advised to use the SMS server.

iMaster NCE-IP
Form Sending Description

Mode
Emails Mail server Third-party email server, which is maintained by

O&M personnel from the user network.
The notifications feature allows O&M personnel to
set parameters for mail servers to establish
communication between mail servers and the
system.
Broadcast Messages
Broadcast messages are the foreground notifications of the system. Broadcast
messages provide the event and message channel between the client and server
applications.
● Event: data processed by application code.
● Message: text visible to users.
Certificate Management
Certificate management involves service certificate management, CA
interconnection configuration, and certificate application. Service certificates can
be managed (including preconfiguration, import, deletion, and periodic validity
check) in a centralized manner, and you can quickly apply for and use the
certificates.
CA Service
The CA service provides functions such as configuring and managing CAs,
certificate templates, and CRLs, and supports the standard certificate management
protocol (CMP) and privacy CA protocol. Through the CA service, users can quickly
apply for and use certificates, which reduce the cost of certificate application.
CA Proxy Service
The CA proxy service is used to connect NCE with the CA or CRL server.
The CA proxy service provides functions such as CA server connection and CRL
server connection.
Table 7-4 Functions of the CA proxy service
Function Description
CA server Used for connection with a CA server. After the connection is

connection successful, users can apply for certificates from the CA server.
CRL server Used for connection with a CRL server. After the connection is
connection successful, users can obtain CRL files from the CRL server.

iMaster NCE-IP
Lifecycle Information Management

Lifecycle information refers to the service life of NCE and its managed NEs, such
as Manufacture Date, Starting Point Date, Session (Month), and Status.
In the current version, the lifecycle information about NEs, boards, and local hosts
can be managed. The local devices refer to the NCE software or hardware.
Online Help
NCE provides a layered design for the GUI help adapting to user needs in diverse
scenarios. An online help system is established supporting on-demand learning
anytime and anywhere. A variety of help forms such as tips, panels, F1 or 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 expand the information if necessary. Systematic
learning information is placed in an independent help system.
7.2.2 Alarm Management

Alarm Management enables O&M personnel to centrally monitor NE, system
services, and third-party system alarms and quickly locate and handle network
faults, ensuring normal network operation.
Alarm Severity
The alarm severity indicates the importance and urgency of a fault. It helps O&M
personnel quickly identify the importance of an alarm, take corresponding
handling policies, and change the severity of an alarm as required.
Alarm severities can also be redefined, as shown in Table 7-5.
Table 7-5 Alarm severity
Alarm Color Description Handling Policy

Severit
y
Critical Services are affected. Critical alarms need to be

Corrective measures must be handled immediately.
taken immediately. Otherwise, services may be
interrupted or the system
may break down.
Major Services are affected. If the Major alarms need to be

fault is not rectified in a timely handled promptly.
manner, serious consequences Otherwise, important
may occur. services will be affected.
Minor Minor impact on services. Minor alarms need to be

Problems of this severity may handled by locating the
result in serious faults, and causes to eliminate potential
therefore corrective actions faults.
are required.

iMaster NCE-IP
Alarm Color Description Handling Policy

Severit
y
Warnin Potential or imminent fault Warning alarms are handled

g that affects services is based on network and NE
detected, but services are not running status.
yet affected.
Different handling policies apply to different alarm severities. You can change the
severity of a specific alarm as required in NCE.
NOTE
The severity of an alarm needs to be adjusted when the impact of the alarm becomes
larger or smaller.
Alarm Status
Table 7-6 lists the alarm statuses. Figure 7-2 lists the alarm status relationship.
Table 7-6 Alarm status

Status Alarm Description
Name Status
Acknowl Acknowledg The initial acknowledgment status is

edgment ed and Unacknowledged. A user who views an
status unacknowle unacknowledged alarm and plans to handle it can
dged acknowledge the alarm, at which point its status
changes to Acknowledged. An acknowledged alarm
can also be unacknowledged, at which point its status
is restored to Unacknowledged. You can also
configure auto acknowledgment rules to
automatically acknowledge alarms.
Clearanc Cleared and The initial clearance status is Uncleared. When a

e status uncleared fault that causes an alarm is rectified, a clearance
notification is automatically reported to Alarm
Management and the clearance status changes to
Cleared. For some alarms, clearance notifications
cannot be automatically reported, and users need to
manually clear these alarms after the corresponding
faults are rectified. The background color of cleared
alarms is green.

iMaster NCE-IP
Status Alarm Description

Name Status
Mainten Normal and The initial maintenance status is Normal. If the

ance maintenanc alarms are generated during commissioning and are
status e not triggered by faults, you can set filter criteria to
filter out maintenance alarms when monitoring or
querying alarms.
NOTE
● The maintenance status corresponding to Normal is
NORMAL.
● The maintenance status corresponding to Maintenance
is Maintenance, or Invalid status.
Figure 7-2 Alarm status relationship
Acknowledged and cleared alarms are moved to the historical alarm list, and a
non-historical alarm is called a current alarm. Table 7-7 shows the definition of
an alarm.
Table 7-7 Current alarms and historical alarms
Name Description
Current alarms Current alarms include uncleared and unacknowledged

alarms, acknowledged but uncleared alarms, and
unacknowledged but cleared alarms. When monitoring
current alarms, you can quickly identify faults, operate
accordingly, and notify maintenance personnel of these faults.
Historical Acknowledged and cleared alarms are historical alarms. You

alarms can analyze historical alarms to optimize system performance.
Alarm and Event

If the system or MOs detect an exception or a significant status change, an alarm
or event will be displayed on the alarm management GUI. MOs refer to the
objects or NEs connected to alarm management. Table 7-8 describes the
definitions of the alarm and event.

iMaster NCE-IP
Table 7-8 Alarm and event
Na Description Differences Between Alarms and Similarities

me Events
Ala Notification ● An alarm indicates that an Alarms and

rm generated exception or fault occurs in the events are
when the system or MO. An event is a presented to users
system or notification generated when the as notifications.
an MO is system or MO is running properly.
faulty. ● Alarms must be handled to avoid
Eve Notification abnormal services as a result of
nt of status exceptions or faults. Events do not
changes need to be handled and are used
generated for analyzing and locating
when the problems.
system or ● Users can acknowledge and clear
an MO is alarms on the GUI but cannot
running acknowledge or clear events.
properly.
Alarms or events are displayed on the page when NEs, services, and
interconnected third-party systems detect exceptions or significant status changes.
Table 7-9 describes the types of the alarm and event.
Table 7-9 Alarm and event types
Type Description
Communication Alarms caused by failures of the communications in an NE,

between NEs, between an NE and a management system,
or between management systems. For example, device
communication interruption alarms.
Service Alarms caused by service quality deterioration. For

example, device congestion alarms.
Process Alarms caused by software or processing errors. For

example, version mismatch alarms.
Equipment Alarms caused by physical resource faults. For example,

board fault alarms.
Environment Alarms generated when the environment where the device

resides is faulty. For example, temperature alarms
generated when the hardware temperature is too high.
Security Alarms generated when security issues are detected by a

security service or mechanism. For example, alarms caused
by authentication failures, confidential disclosures, and
unauthorized accesses.

iMaster NCE-IP
Alarm Handling Mechanism

Alarm management provides three alarm handling mechanisms. For details, see
Table 7-10.
Table 7-10 Alarm handling mechanisms

Mechanism Description
Alarm merging To help users improve the efficiency of monitoring and

rule 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
previous reported alarm that meets the merging rule, the
newly reported alarm is displayed as a merged alarm and
the value of Occurrences is 1.
● If the newly reported alarm B and the previous 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
merged alarm, and the Occurrences value of the merged
alarm increases by one. Alarm B is regarded as an original
alarm.
In the alarm list, click Occurrences of an alarm, you can
view the detailed information about the merged alarm and
original alarm.
● If a merged alarm is cleared, it will be converted into an
original alarm. The previous original alarms will be sorted
by clearance status (uncleared alarms are displayed first)
and occurrence time in descending order.
● If a merged alarm or original alarm is cleared and
acknowledged, the alarm will be converted to a historical
alarm and the value of Occurrences decreases by one.

iMaster NCE-IP
Processing of To prevent excessive current alarms from deteriorating system

the full current performance, alarm management provides a full-alarm
alarm cache processing rule. When the number of current alarms in the
database reaches the upper threshold, alarm management
applies the following rules to move some alarms to the
historical alarm list. When the number of alarms falls to 90%
of the upper threshold, alarm management stops the
processing of the full current alarm cache.
1. Alarms are moved to the historical alarm list in the
following sequence: original alarms in the maintenance
state, alarms that do not match any merging rules and are
in the maintenance state, original alarms in the normal
state, and alarms that do not match any merging rules and
are in the normal state.
2. Alarms in the same maintenance state and merging state
are moved to the historical alarm list in the following
sequence: cleared and acknowledged alarms, cleared and
unacknowledged alarms, and acknowledged and uncleared
ADMC alarms.
3. Alarms of the same type are moved to the historical alarm
list in ascending order of alarm severity.
4. Unacknowledged and uncleared alarms are moved to the
historical alarm list in sequence based on the preceding
rules.
5. For the alarms that meet the preceding conditions, the
earlier alarms are moved to the historical alarm list first.
6. In a distributed system, when the NE alarms are reported to
different nodes and the processing of the full current alarm
cache is triggered, the alarms are moved to the historical
alarm list in descending order of the node alarm quantity.
The more alarms are reported to a node, the higher the
priority of the node is. For example, if an NE is connected to
node A and node B, and the alarm quantity on node A is
more than node B, the processing of the full current alarm
cache is performed only on node A.

iMaster NCE-IP
Alarm dump To avoid excessive alarm database data, the system dumps
rule events, masked alarms, and historical alarms every 2 minutes
according to the following rules. The dumped alarms or events
cannot be queried in the alarm or event list.
● If the database space usage reaches 80%, alarm
management dumps the data in the database to files
according to the sequence of occurrence time and data
table type (event, masked alarm, or historical alarm). When
the space usage after dumping reaches 80% of the usage
before dumping, the dumping is stopped.
● If alarm management detects that the data in the database
table is generated 90 days ago, it dumps the database
table.
Dumped files that meet any of the following rules will be
deleted:
● The dumped file will be deleted after 180 days.
● If the total size of the dumped files exceeds 1 GB or the
total number of files exceeds 1000, the system deletes the
earliest files.
Alarm Management Function

Alarm management provides a variety of monitoring and processing rules. You can
configure alarms or events to reduce the number of alarms, implement real-time
alarm notification, and meet personalized monitoring requirements. Multiple
monitoring pages provide users with various and convenient monitoring and
processing methods. For routine maintenance of alarm data, a configurable
assurance mechanism is provided to prevent the reporting of new alarms from
being affected when the database is full.
For details about the alarm or event rules that can be configured, see Table 7-11.

iMaster NCE-IP
Table 7-11 Configuring alarm or event rules

Configuring Alarm management provides visualized pages for managing

alarms or alarm rules and settings. In a DR scenario, alarm rules are
events synchronized between the active site and standby site every
hour. After a DR switchover, the synchronization of all alarm
rules is complete within 5 minutes.
● Masking rule
During maintenance, test, or deployment, the system or MO
generates predictable alarms or events that require no
attention or handling. You can set rules to mask these
alarms or events so that they are not displayed on the
Current Alarms, Historical Alarms, or Event Logs page.
When setting a masking rule, you can choose to discard
masked alarms or events, that is, these alarms or events are
not saved to the alarm database, or display the masked
alarms on the Masked Alarms page.
● Severity and type redefinition rule
To ensure the smooth running of network devices or key
devices in a region, you can set redefinition rules to change
the severity and type of alarms or events. For example, if an
alarm is considered important, its severity can be set to a
higher one, so that O&M personnel can handle it
preferentially to provide high-quality network assurance
services.
● Name redefinition rule
Some alarm or event names are professional, which do not
conform to user habits or are too technical to understand.
You can redefine alarm or event names as required.
● Correlation rule
A correlation rule defines correlative relationships between
alarms. Correlated alarms are the alarms with related
causes. Among correlated alarms, one alarm is the root
alarm of the others, and other alarms are correlative alarms
of the alarm. You can customize correlation rules, and
enable and disable default correlation rules as required.
When monitoring or viewing alarms, you can filter out
correlative alarms and focus on only the root alarms that
you need to handle.
● Intermittent/Toggling rule
When the interval between generation and clearance of an
alarm is less than a specific period, the alarm is considered
as an intermittent alarm.
If the number of times an alarm (with the same ID) is
reported by the same alarm source in a specified period
reaches the trigger condition, toggling handling is started.
After an intermittent/toggling alarm handling rule is set, the
intermittent alarms or alarms that are generated during the

iMaster NCE-IP
toggling can be discarded or masked to reduce interference

caused by repeated alarms.
● Aggregation rule
Repeated alarms or events are the alarms or events (with
the same ID) reported by the same alarm or event source for
multiple times. After an aggregation rule is set, the system
automatically aggregates the repeated alarms or events
reported within the specified period into one alarm or event.
O&M personnel can view the aggregated alarms on the
alarm details page.
● Setting events as ADMC alarms
If events require more attention, you can set them to auto
detected manually cleared (ADMC) alarms. This type of
alarms cannot be automatically cleared.
● Auto acknowledgement rule
After an auto acknowledgment rule is set, alarm
management automatically acknowledges the current
alarms in the cleared state according to the specified rule
and moves the acknowledged alarms to the historical alarm
list.
● Northbound filtering rule
On the live network, the upper-layer NMS often receives a
large number of alarms. Network congestion and breakdown
may occur due to overload, and you cannot quickly locate
concerned alarms. To resolve this problem, you can set alarm
northbound filtering rules to determine whether to report
the alarms that meet the rules to the upper-layer NMS.
Alarm By using the alarm notification function, alarm management

notification can send the alarm or event information to users in real time
by SMS message or email. In this way, the users can learn
about the alarm or event information in real time and handle
important alarms or events in a timely manner.

iMaster NCE-IP
Personalized Alarm management provides multiple display modes or sound

monitoring prompt rules for alarms and events. You can modify the rules of
display mode and sound prompt as required to obtain the latest
alarm or event information in different ways.
● Color settings: You can set colors for different alarm or event
severities and colors for selected alarms or events to easily
identify alarms or events.
● Alarm sounds: You can set sounds for alarms at different
severities so that you can identify the importance of alarms.
● Font colors: You can set font colors for read and unread
alarms to distinguish alarms.
● Highlight: If alarms at a severity are not handled, that is, the
alarm status remains unchanged, within the specified period
of time, the alarms are highlighted in the alarm list
according to the highlight settings.
● Alarm display mode: You can set alarm display modes for
alarms at different severities and in different states so that
you can quickly identify concerned alarms.
● Global alarm indicators: You can enable global alarm
indicators so that you can learn about the overall situation
of alarms in real time on different web client pages.
● Alarm box: The alarm box can use indicators in different
colors and play different sounds based on NE alarm
severities. You can set filter criteria for the alarm box. Alarms
that match the criteria are sent to the alarm box and you
are notified of the alarms by indicators and sounds.
● Emergency maintenance notification: By setting the
emergency maintenance notification function, you can
determine whether to display the Emergency Maintenance
Notification panel to remind O&M personnel to handle
alarms in a timely manner.
For details about how to monitor alarms or events and handle alarms, see Table
7-12.

iMaster NCE-IP
Table 7-12 Monitoring alarms or events and handling alarms

Monitoring and O&M personnel can monitor alarms and view alarm or event
viewing alarms information in alarm management in real time.
or events ● Alarm or event lists
– A current-alarm list is provided. The system pushes
alarms to the Current Alarms page. O&M personnel
can monitor and handle alarms in real time using the
list.
– An alarm log list is provided. You can view current and
historical alarms. By default, 20,000 alarms can be
displayed.
– An event log list is provided, which presents the event
messages sent by devices to the system. By default,
20,000 events can be displayed.
● Statistics panel
On the Current Alarms page, the statistics panel is
provided to display the following statistics:
– Top 10 Alarms: Displays the 10 most frequently
reported alarms.
– Duration: Displays the statistics on the number of
current alarms by duration.
– Top 10 Alarm Sources: Displays the 10 alarm sources
that report the most alarms.
– Severity: Displays the statistics on the total number of
current alarms and the number of current alarms at
each alarm severity.
– Status: Displays the statistics on the number of alarms
by acknowledgement and clearance status.
● Alarm or event name group
You can add multiple alarm or event names to a name
group to perform operations on them at a time.
● Object group
You can add multiple alarm or event sources to an object
group to perform operations on them at a time.
● Alarm sounds and indicators
When a new alarm is reported, alarm management plays
a sound. The alarm indicator that corresponds to the
severity of the alarm blinks to remind you to handle
alarms in a timely manner.
● Filter
You can set criteria to filter alarms that require special
attention.
● Filter templates
You can save the set filter criteria as a filter template to
customize filter templates for different scenarios. You can
also use the default filter template to quickly filter alarms.

iMaster NCE-IP
● Browsing alarms by status or severity

A page is divided into four areas to display current alarms
by status or severity.
Handling You can use alarm management to handle alarms to

alarms facilitate troubleshooting. For example, you can specify alarm
handlers and acknowledge or clear alarms. Alarm handling
functions are as follows:
● Viewing alarm details
Obtains key alarm information, including alarm names,
repair recommendations, and location information, to
facilitate fault diagnosis and troubleshooting.
● Manually acknowledging alarms
Acknowledging an alarm indicates that the alarm is traced
by a user, and other users can ignore it. If you want other
users to focus on the alarm again, you can unacknowledge
the alarm. Manual alarm acknowledgement and
unacknowledgement, and automatic acknowledgement by
severity are supported in alarm management.
● Recording maintenance experience
After handling an alarm, the O&M personnel can record
the handling experience in a timely manner for future
reference.
● Manually clearing alarms
If an alarm cannot be automatically cleared or the fault is
rectified but the alarm is still uncleared, you can manually
clear the alarm.
Table 7-13 describes routine maintenance functions, such as alarm data

management.

iMaster NCE-IP
Table 7-13 Routine maintenance functions

Performance By analyzing historical alarms and masked alarms and

optimization collecting statistics on alarm data, you can learn about the
and statistics running status of devices and determine whether rules are
properly set, and can also further analyze potential issues of
running devices based on the statistics.
● You can view historical alarms and masked alarms.
In this manner, you can understand device running
statuses and determine whether rules are appropriate.
– A historical alarm list is provided, which displays 20,000
acknowledged and cleared alarms by default.
– A masked alarm list is provided, which allows O&M
personnel to view masked alarms and determine
whether masking rules are appropriate. By default,
20,000 masked alarms can be displayed.
● You can collect statistics on alarm or event logs.
Statistics on alarm or event data can be collected based
on specified criteria and displayed in the table and charts
for system fault analysis.
Alarm or event ● Current alarm threshold warning

data When the number of current alarms reaches the upper
management limit, the system processes the full current alarm cache
and moves current alarms to the historical-alarm list. To
prevent important alarms from being moved to the
historical-alarm list, you can set a threshold for current
alarms. When the number of current alarms reaches a
specified threshold, an alarm is reported to prompt users
to handle the current alarms.
● Manually synchronizing alarms
After a peer system is disconnected from the current
system, alarms of the peer system cannot be reported to
the current system. After the connection is restored, the
alarms need to be synchronized to the current system for
monitoring.
● Current alarm lifecycle
You can set the period for saving cleared and
acknowledged alarms in the current alarm list to facilitate
alarm monitoring.
Handling After handling an alarm, record the handling information to

experience the experience database for future reference or guidance. You
management can import or export experience records.

iMaster NCE-IP
7.2.3 Security Management

Security management involves management of user permissions, user policies, and
logs, as well as security situation analysis of products. Security management helps
protect NCE against unauthorized user logins, ensuring system data security.
7.2.3.1 User Management

User Management ensures the security of user information and the system. By
attaching users to roles and managing the permissions of each role, resource
allocation is optimized and permission management is simplified, improving 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 the Authentication, Authorization, Accounting (AAA) system
to implement centralized user management, authentication, and
authorization. After interconnecting with the AAA system though remote
authentication configuration, the system authenticates users to ensure that
only those authorized can log in.
User Management
● User
A user refers to a person who uses the system. Information about a user
includes their username, password, and permissions.
Users can be classified into the following types:
– Local users: users who are authenticated and log in to the O&M plane
– Third-party users: users (machine-machine accounts) that interconnect
the O&M plane with third-party systems
– Remote users: users that interconnect with Lightweight Directory Access
Protocol (LDAP) or Remote Authentication Dial In User Service (RADIUS)
servers
A system administrator can be configured during the system installation. The
system administrator has all permissions on all managed objects, and is
attached to both the Administrators and SMManagers roles.
NOTICE
● The system administrator has the highest permission for the system and all
managed objects. Exercise caution when performing operations as this
user, and avoid any actions that might affect system security. For example,
do not share or distribute the username and password of the system
administrator.
● The system administrator user can be renamed. For details, see "Disabling,
Enabling, or Renaming Default Web Users" in Administrator Guide.
The system defines two types of special users:

iMaster NCE-IP
– Security administrator: a user attached to the SMManagers role

– Administrator: a user attached to the Administrators role
● Role
Users attached to a role have all the permissions granted to that role. You can
quickly authorize a user by attaching the user to a role, facilitating permission
management. Figure 7-3 shows role information.
Figure 7-3 Role information
Users attached to a role have all the permissions granted to that role and can
manage all the resources managed by the role. A user can also be attached to
multiple roles, whereby the user has all the permissions granted to those roles
and can manage all the resources managed by the roles.
Default roles cannot be deleted and their permissions cannot be modified as
these permissions are granted by the system. The system provides the
following default roles:

iMaster NCE-IP
NOTICE
Users attached to the Administrators or SMManagers roles have operation

rights for all resources in the system. As such, exercise caution when
performing operations with these user accounts, and do not take any action
that might affect system security. For example, do not share or distribute
these user names and passwords.
Role Name Description
Administrators Has all the permissions except User Management, Query

Security Log, and View Online Users.
SMManagers Has the User Management, License Management, View

Online Users, Query Security Log, and Update ACL
Policy permissions.
NBI User The user group has permission to configure northbound

Group interfaces such as SNMP, RESTful, CORBA, XML, OMC, and
TEXT NBIs.
Guest The domain of this user group is All Objects, and it has
operation rights for default monitor operation sets. They
can perform query operations, such as querying statistics,
but cannot create or configure objects.
Maintenance The domain of this user group is All Objects, and it has
Group operation rights for default maintenance operation sets. In
addition to the rights of the Guests and Operator Group
groups, users in this group have the rights to create
services and perform configurations that affect the
running of NCE and NEs. For example, they can search for
protection subnets and trails, delete composite services,
and reset boards.
Operator The domain of this user group is All Objects, and it has
Group operation rights for default operator operation sets. In
addition to the rights of the Guests group, users in this
group have the rights to modify on NCE (rights to perform
potentially service-affecting operations are not involved).
For example, they can change alarm severities.
Analyzer User Analyzer user group.

Group
HOFS Group Has the File Management Operation Set permission.
● Operation rights and operation set

Operation sets are used to assign a set of operation rights to roles. Users
attached to a role have the operation set of that role.
User Management provides two types of operation sets:
– Application operation set: a collection of operation rights for system
functions, such as querying system logs and creating users.

iMaster NCE-IP
The system provides the default application operation set All Application
Operations. For security purposes, this operation set contains the
operation rights for all system functions except User Management,
Auditlog Manager, and License Manager.
– Device operation set: a collection of operation rights for devices, such as
starting and stopping switches.
The system provides the default device operation set All Device
Operations, which contains the operation rights for all devices.
Permission Management
A permission defines what operations a user can perform on what objects.
Permission elements include an operator, operation objects, and operations as
shown in Figure 7-4.
Figure 7-4 User Management permission
● Permission
– Users act as operators.
– Operation objects include the system and resources (physical and virtual
resources, such as servers, network devices, and VMs) where users
perform operations.
– Operations include application operations and device operations.
Application operations are performed on the system. Device operations
are performed on resources.
● Authorization mechanism
Authorization is the process of granting permissions on certain objects to
users. The authorization mechanism of User Management is as follows:
– To authorize a user with an object on which this user needs to perform
operations, add this object to the managed objects of the role that this
user is attached to.
– To authorize a user with an operation that they are required to perform,
add it to the operations for which the user's current role has operation
rights.
Figure 7-5 shows the authorization principles of User Management.

iMaster NCE-IP
Figure 7-5 User authorization principles of User Management
NOTE
● Users can perform application operations and device operations. If only managed
objects are configured for a role but no device operation is configured, users of this
role can view the managed objects after logging in to the system but do not have
the operation rights for the managed objects.
● If Assign rights to users directly is selected, permissions can be directly granted to
users.
● Authorization method
The authorization method of user management grants permissions by
attaching a user to a role. After the security administrator sets role
permissions (including managed objects and operation rights), they attach the
user to a role in order to grant them access to the role's permissions. If Assign
rights to users directly is selected, permissions can be granted to users
directly.
User authorization allows security administrators to implement authorization
for all users in a post at the same time. When employee posts are changed,
security administrators can delete the original user from the role and add the
new user to authorize them.
● Secondary authorization
Secondary authorization policies are required to ensure that users can
cautiously perform dangerous operations or those that will have a major
impact. After a secondary authorization policy is enabled, users are not
allowed (prohibition or suspension occurs) to perform these operations when
the criteria set in the secondary authorization policy are met, even if they
have operation rights for these operations. If an operation is suspended, users

iMaster NCE-IP
can only proceed with the operation after they are authenticated by a user
that has the operation rights for Secondary Authorization Authentication.
Region Management
Regions can be classified by geographic location or resource usage, and users can
be authorized based on regions.
Security administrators can create different regions based on service requirements
to implement regional rights-based management. After a region is created, the
system automatically creates a region administrator role Region
name_SMManager for the new region. Security administrators need to set
parameters on the Mandate-Operation Rights and Mandate-Managed Objects
tab pages for the region administrator to enable them to manage the users, roles,
objects, and operation sets in this region based on the settings.
Figure 7-6 Region administrator
● Security administrator permissions and region administrator permissions

Security administrators have all the permissions in the system. Region
administrator permissions are set by security administrators based on service
requirements.
● Region administrator permissions and permissions of roles in the region
The permissions and managed objects set for a region administrator on the
Mandate-Operation Rights and Mandate-Managed Objects tab pages can
be assigned by the region administrator to roles in the region.

iMaster NCE-IP
User Maintenance and Monitoring

During user permission maintenance, you can view and modify user, role, and
operation set information, and monitor user sessions and operations in real time,
ensuring system security.
● Common operations for user information maintenance include viewing,
exporting, and modifying user information, as well as deleting users.
● Common operations for role information maintenance include viewing,
exporting, and modifying role information, as well as deleting roles.
● Common operations for operation set information maintenance include
viewing and modifying operation set information, as well as deleting
operation sets.
● You can modify user information (such as Max. online sessions and Login
time policy) in batches to improve system security.
● Personal settings involve periodically changing personal data such as the user
password, telephone number, and email address, to ensure optimal user
security.
NOTE
● When modifying your personal information (for example, mobile number or email
address), you are obligated to take appropriate measures in compliance with the
laws of the countries concerned and the user privacy policies of your company to
ensure that your personal data is fully protected.
● To ensure the security of personal data such as mobile numbers and email
addresses, such data is anonymized on the GUI, and HTTPS encryption
transmission channels are used.
● Resetting a user password: If a user forgets their password or is unable to
change it, they must contact security administrators to reset it. If a security
administrator forgets their password, they must contact the system
administrator to reset it.
NOTICE
● If the admin user forgets the password, the password must be reset by
referring to "Resetting the Password for the admin User of the
Management Plane or O&M Plane" in Administrator Guide.
● For account security purposes, it is recommended that third-party system
access users contact the security administrator to periodically reset their
passwords.
● User monitoring: This refers to the monitoring of users' resource access

behaviors, including session monitoring (online status) and operation
monitoring. If a user performs an unauthorized or dangerous operation, the
system allows security administrators to forcibly log out the user. This
function allows security administrators to prevent user access and ensure
system security.
User Policies
User Policies allow you to set access control rules for users. During the initial
installation of the system, you must plan and configure user policies and adjust

iMaster NCE-IP
the configurations based on management requirements. This prevents

unauthorized users from intruding into the system, ensuring system security. User
policies involve account policies, password policies, client IP address policies, and
login time policies.
● Account policies: These include the minimum username length and user login
policies. Appropriate setting of an account policy improves system access
security. The account policy is set by security administrators and takes effect
for all users.
● Password policies: A password policy includes the password complexity,
change interval, and character limitation. Appropriate setting of a password
policy prevents users from setting weak passwords or using the same
password for extended periods, improving system access security. The
password policy is set by security administrators and takes effect for all users.
A new password policy does not affect the configured password.
● Client IP address policies: A client IP address policy provides a control
mechanism for checking the accessibility of the IP address used by an external
access request during system operation. After a client IP address policy is set
and applied, users are only allowed to log in to the system using IP addresses
within the specified IP address range.
● Login time policies: A login time policy provides a control mechanism for
checking the validity time of an external access request during system
operation. After a login time policy is set and applied, users are only allowed
to log in to the system within the specified period. The system administrator
is not restricted by the login time policy.
7.2.3.2 Log Management

Log management records logs and allows user to query and export logs, as well as
create, export, and import operation log templates. In this way, users can obtain
information about operations they perform in the system and the system running
status in real time. Log forwarding settings report audit logs as well as logs
reported by other applications to the Syslog server for users to query and analyze.
Usage Scenario
Log management is used when you need to perform routine maintenance, locate
and troubleshoot faults, trace historical logs, and query operation logs across
systems.
● Routine maintenance
It is necessary to view logs during routine maintenance. If logs exist recording
failed, partially successful, or unknown operations, or logs in the risk level,
analyze the exception causes and troubleshoot the faults.
● Fault locating and troubleshooting
To locate and troubleshoot faults occurring during system running, you can
analyze logs to detect whether risk-level operations or operations that affect
system security are performed.
● Historical log tracing
Logs are stored in the database after being generated. The system periodically
dumps logs from the database to a hard disk to ensure sufficient database

iMaster NCE-IP
space. To ensure the integrity and traceability of logs, you can forward these
logs to the Syslog server.
● Cross-system operation log query
If you need to query operation logs meeting the same criteria on different
systems, you can set filter criteria on one of the systems, save these criteria as
a template, and import the template to other systems.
Log Types
Log management allows the system to automatically record information regarding
the system's running status and operations performed by users.
Table 7-14 describes the log types recorded in log management.
Table 7-14 Log types

Type Definition Triggered By Purpose Level
Securit Records user Operations Detects security ● Risk

y log operations performed by issues and risks. ● Minor
performed in users
the system (including ● Warning
that affect third-party
system system access
security. users)
attached to
the
SMManagers
role, such as:
● Creating a
user.
● Changing a
password.
System Records system System Analyzes the system ● Risk

log operations or operations, running status and ● Minor
tasks. such as: rectify faults.
● Warning
● Unlocking
a user.
● Starting a
scheduled
task.

iMaster NCE-IP
Type Definition Triggered By Purpose Level
Operati Records user User Traces and analyzes ● Risk

on log operations (including user operations. ● Minor
performed in third-party
the system system access ● Warning
that do not users)
affect system operations,
security. such as:
● Exporting
current
alarms.
● Creating a
subnet.
NE Syslog run logs System You can view the NE Warning,

Syslog record operations. Syslog operation logs Error
run log operation logs on NCE, rather than
about viewing them on
managed NEs. each NE.
NOTE
This function applies
only to NCE-IP.
Log Management
When user operations, system operations, or system tasks are performed, log
management records logs and saves the logs to the log management database. To
prevent logs from exhausting the database space, the system automatically dumps
logs meeting the requirements from the database to the hard disk of a server. The
dumped logs are automatically deleted from the database.
Logs can be dumped by means of integrated task management and log
management. Logs that have been dumped to the hard disk are automatically
deleted from the database. To prevent log files from exhausting the hard disk
space, the system periodically checks log files on the hard disk and deletes log
files meeting the requirements from the hard disk. For details, see Table 7-15.

iMaster NCE-IP
Table 7-15 Dump scheme details

Dump Ch Default Dump Path Default
Scheme ec Condition for Condition for
k Dumping Logs Deleting
Int from Database Dumped Log
er Files from the
val Hard Disk
Log Ev ● Percentage of Logs meeting the ● Days for which

manage ery the used log conditions are log files have
ment ho database automatically saved to been stored ≥
ur space ≥ 80% a .csv or .zip file and 45
● Quantity of dumped to ● Total size of
logs of a type the /opt/oss/ all log files ≥
≥ 1 million share/NCE/ 1024 MB
SMLogLicService/
● Days for which dump directory on the ● Log file
logs of a type hard disk of the server. quantity ≥
have been 1000
NOTE
stored ≥ 45
If the system is
deployed in cluster
mode, you need to log
in to all nodes where
SMLogLicService resides
and go to the file dump
or export paths on the
nodes to find dumped
or exported files.
Integrate Ev Overflow Dump: Task management ● Days for which

d task ery Maximum dumps logs logs have been
manage da storage capacity to /opt/oss/ stored ≥ 15
ment y of a log type ≥ share/NCE/ ● Total size of
100,000 SMLogLicService/var/ all log files ≥
Database ThresholdExport/Log 1024 MB
Capacity on the server.
● Log file
Management: quantity ≥
Days for which 1000
logs of a type
have been stored
in the database ≥
90

iMaster NCE-IP
NOTE
● You can obtain complete dumped log files in two dump paths. If the system is deployed
in cluster mode, you need to log in to all the nodes where SMLogLicService resides and
go to the file dump paths on the nodes to find dumped files.
● For the log management dump scheme, you can run the auditTool.sh command script
to modify the conditions for dumping logs and deleting dumped log files. For details,
see "Setting Log Dump (the O&M Plane)" in Administrator Guide.
● For log dump by means of integrated task management, the conditions for dumping
logs and deleting dumped log files can be set on the GUI for each task type (for
example Security Log Dump and Operation Log Dump).
● If integrated task management is deployed, only the number of days for storing logs set
in integrated task management is effective, and the corresponding condition of log
management does not take effect.
Figure 7-7 shows the log dump principles.
NOTE
● All values in the figure are default values.

● To trace user operations, system operations, and system tasks, you can forward
concerned logs to the Syslog server by opening the System Settings app and choosing
System Settings > Log Forwarding Settings from the main menu. You can view the
forwarded logs as required on the Syslog server.

iMaster NCE-IP
Figure 7-7 Log dump principles
Log Forwarding
Log forwarding settings are used when users need to trace the logs recorded by
log management, or query and analyze the logs recorded by log management as
well as the logs of other functions (such as NE Syslog run logs and NE Syslog
operation logs) in real time.
● Users need to permanently store the NCE system logs recorded by log
management so that they can trace the logs to locate problems or rectify
faults.
● For the logs of other functions (such as NE Syslog run logs and NE Syslog
operation logs), log forwarding settings allow users to centrally query and
analyze these logs on Syslog servers.
Figure 7-8 shows the principles of log forwarding settings.

iMaster NCE-IP
Figure 7-8 Principles of log forwarding settings
7.2.3.3 Security Situation
7.2.3.3.1 Security Situation Awareness

Situational awareness provides visualized threat detection and analysis. It classifies
and aggregates the detected attack events, threat alarms, and attack sources, and
displays visualized reports and attack situation for users, providing a basis for
decision-making on security event handling.
Related Concepts
● Assets: objects on which Security Situational Awareness performs security
detection and analysis. You can set detection rules to detect real-time or
historical events on an asset. The internal assets of Security Situational
Awareness are in a two-layer model. The first layer consists of NEs and the
NMS, and the second layer consists of NE VMs, NMS VMs, and FusionSphere
physical machines.
– Business assets: OSS and NEs.
– Hosts: NE VMs, NMS VMs, and FusionSphere physical machines.
● Security events: events that may pose threats to asset security. Security
Situational Awareness allows you to view and handle security events.
● Security Situational Awareness provides two detection modes: offline
detection and real-time detection.

iMaster NCE-IP
Prope Offline Detection Real-time Detection

rty
Detec SSADetectionService microservice SSAAgentService

tion microservice
meth
od
Detec EMS and NE EMS and NE

tion
object
Detec Events that have posed threats to asset Events that pose
tion security real-time threats to
scope asset security
Detec According to the position where an event System: detects

tion occurs, offline detection can be performed exceptions and
domai in the following domains: attacks related to the
n ● O&M: detects exceptions on the O&M OS of the EMS or NE,
entry of the EMS or NE, such as brute- such as OS malware
force cracking of O&M accounts and attacks and file
abnormal login. exceptions. Here, the
system refers to the
● System: detects exceptions and attacks position where
related to the OS of the EMS or NE, attacks occur, which
such as brute-force cracking of OS is different from the
accounts and user privilege escalation. meaning of "system"
Here, the system refers to the position (an organized whole
where attacks occur, which is different consisting of similar
from the meaning of "system" (an things, such as a
organized whole consisting of similar database system and
things, such as a database system and a a network system) in
network system) in a broad sense. a broad sense.
Detec Brute-force cracking, login behavior Privilege escalation,

tion analysis, data theft, and account behavior file anomaly analysis,
scenar analysis. malware analysis,
io abnormal account
analysis, and process
anomaly analysis.
Security Situation Awareness Functions

Security Situational Awareness can detect events on assets and display details
about those events in real time, including affected assets, event types, and event
severities. Security Situational Awareness allows you to set detection rules,
applicable to various assets and scenarios. In addition, you can query the trend
analysis over the past 30 days and the event processing status. Such data helps
you locate risks and develop follow-up policies.

iMaster NCE-IP
Table 7-16 Function description
Functio Description
n
Situatio Provides a global situation analysis report.

n ● Displays Risk Overview, Real-Time High-Risk Event, Security
analysis Event Trend, Security Event Level Distribution, Security Event
Domain Distribution, Security Event Type Top 5, Asset Risk Top
5, and Configuration Check Risk.
● Supports log forwarding, which can be used to report threat
information to a third-party log management system or log
analysis system. The third-party log management system or log
analysis system retains key logs, and queries and analyzes events.
When configuring the log forwarding function, enter
eventCategory in Required string; otherwise, the threat
information of security situational awareness cannot be queried by
a third-party system.
Security Provides the following detection modes:

detecti ● Offline detection: provided by SSADetectionService microservice to
on detect events that have posed threats to asset security.
● Real-time detection: provided by SSAAgentService microservice to
detect events that pose real-time threats to asset security.
Configu Provides configuration check analysis reports, containing the rule risk
ration distribution by level, rule distribution by category, check category
check distribution, top 5 asset configuration risks, top 5 improper
configurations, and configuration check analysis list.
Rule Supports detection rule settings.

manag ● Offline detection rule: You can view all offline detection rules, edit
ement a detection rule, and deliver a detection rule.
● Real-time detection rule: You can view all real-time detection rules,
associate the detection object with a detection rule, and deliver a
detection rule.
Detection Principles
● Offline Detection
The offline detection principles are the same for EMSs and NEs.

iMaster NCE-IP
● Real-Time Detection
– When the detection object is an EMS:
– When the detection object is an NE:
7.2.3.3.2 Remote Attestation

Remote attestation is one of the key technologies in the trusted computing
solution and is used to verify the trust relationship of devices. Remote attestation
obtains relevant measurement data (including the measurement values and
measurement logs of PCRs) from a device, compares the data with baseline
values, and displays the trust relationship of the device based on the comparison
result.
Description
Remote attestation verifies the trust status of the device, including the integrity of
the device in the boot phase and running phase. During verification by remote
attestation, the boot phase needs to be used together with the measurement boot
phase, and the running phase needs to be used together with the IMA
measurement phase.
In the measurement boot process, the measurement values of software running

on the device in each boot phase are extended to the platform configuration
register (PCR) of the HTM or TPM. After the device is booted successfully, remote
attestation initiates a challenge to the device to be verified, obtains the
measurement value, measurement logs, and other information of the PCR, and
compares the measurement value with the baseline value to verify whether the
device is trusted. The device is trusted only when the integrity of all software
meets expectations.
Remote attestation provides the following functions:
● Allows users to manually verify the trust relationship of a device, or enables

the system to automatically do so at a scheduled time.
● Verifies the integrity of files loaded during device boot and running.

iMaster NCE-IP
● Displays the overall device trust relationship and the trust relationship of the
board.
● Reports an alarm when a device is untrusted.
Usage Scenario
During device boot and operation, attackers may exploit vulnerabilities to tamper
with programs and implant Trojan horses. Remote attestation obtains integrity
measurement data during device boot or operation, provides device identity and
integrity verification reports, generates alarms when a device is untrusted, and
prompts you to handle file tampering attacks.
7.2.3.3.3 Dynamic Trust Assessment

Dynamic Trust Assessment assesses the security status of users based on security
detection events. O&M personnel can adjust dynamic policies in real time based
on assessment results to improve network security.
Basic Concepts
● Trust score: dynamic trust assessment result. A higher score indicates higher
security. The default initial score of a user is 100.
● Security detection event: basis for trust assessment by Dynamic Trust
Assessment. Dynamic Trust Assessment scores the security status of each user
based on the impact values of all security detection events.
● Risk event impact period: Events that occurred during this period are used as
the basis for trust assessment.
● Risk event storage period: Events whose risk event impact period expires but
risk event storage period does not expire are not used as the basis for trust
assessment.
Function

Assessment Allows you to view dynamic trust assessment results, view

dynamics evidence information, ignore risk events, and reset user scores.
Evaluation Allows you to view security detection events, configure the

Policy impact, and set the impact period and storage period of risk
events.
Dynamic Allows you to dynamically adjust user access policies.

Policy
Management
7.2.3.3.4 Dynamic Policy Management

Dynamic policy management executes policies based on the user trust score. If a
user performs a risky operation, the trust score of the user decreases. If the trust

iMaster NCE-IP
score of the user is less than or equal to the trust score required by a policy, the
policy will be implemented to improve the system security.
Related Concepts
Understanding related concepts such as the policy trust score helps you
implement the functions of dynamic policy management.
The trust score is the result of dynamic trust assessment. A higher score indicates
higher security. The default score of a user is 100.
Policy: A policy controls measures taken on users based on their trust scores,
including reporting an alarm, enabling two-factor authentication, restricting high-
risk operations, logging out sessions, and warning.
Usage Scenario
If a user performs a risky operation, the trust score of the user decreases. For
security purposes, if the trust score of the user is less than or equal to the trust
score required a policy, the policy will be implemented to take measures, such as
logging out the user session and reporting an alarm.
Dynamic Policy Management

The dynamic trust assessment service gives a trust score for the reported security
logs and operation logs, and then delivers the trust score to dynamic policy
management. Dynamic policy management matches a policy based on the trust
score and implements the matched policy.
Figure 7-9 shows the principles of dynamic policy management.
Figure 7-9 Principles of dynamic policy management
7.2.3.4 Security Configuration Check

iMaster NCE-IP
7.2.3.4.1 Application Security

Application security monitors service configuration items in a centralized manner
and provides risk check and baseline management for these items.
Usage Scenario
Security administrators can use application security to check whether the
protocols, keys, algorithms, and policies (for example, the policy of forcible
password change after expiration) used by services meet the baselines, ensuring
service security.
Functions
Application security provides risk check on service configuration items and
baseline management. Each service needs to register service configuration items
with application security. Security administrators determine whether to modify the
baselines as required. Application security performs risk checks on service
configuration items based on the check baselines, warns of risks, and provides
handling suggestions, helping security administrators detect and handle service
security risks in a timely manner.
Figure 7-10 shows the principles of application security.
Figure 7-10 Principles of the application security function
7.2.3.4.2 NE Security
NE security monitors NE service configuration items, performs security
configuration check, and manages check baselines.
Usage Scenario
You can check baseline compliance of the protocols, algorithms, and
configurations to learn NE service risks and ensure NE service security.
Functions
NE security allows you to check NE service configurations and manage check
baselines.

iMaster NCE-IP
NE security performs risk checks on NE service configuration items based on the

check baselines, warns of risks, and provides handling suggestions, helping
administrators detect and handle NE service security risks.
Figure 7-11 shows the principles of NE security check.
Figure 7-11 NE security check
7.2.3.4.3 Security Configuration Check Management

Security configuration check management compares the asset configuration status
with the security baseline to detect the differences.
Usage Scenario
Security configuration check management can check the application layer, service
layer, and system layer of NCE and NEs, covering multiple types of middleware
such as the operating system, database, and Tomcat. It also covers more than 50
security types, such as software file system security, identity authentication,
account and password management, kernel security, and log audit. This function
provides user-defined check templates based on user scenarios to implement
flexible check capabilities and meet different check requirements. It evaluates the
security configuration check results of NCE and NEs from the asset and rule views,
analyzes and displays the impact of weak configurations, and quantifies asset risks
through professional evaluation models.
Security Configuration Check Management

Security configuration check management provides full-stack security
configuration check capabilities for the application layer, service layer, and system
layer, and builds integrated security capabilities of risk identification, risk
quantification, and risk resolution guidance. Through automatic check, the
duration for identifying weak configuration risks is within hours, improving
automatic O&M efficiency and reducing security risks. Risks are quantified through
multi-dimensional visualization, improving user's risk evaluation capabilities.
The following table lists the functions provided by security configuration check
management.

iMaster NCE-IP

Functio Description
n
Overvie Collects statistics on the check results of multiple tasks on the entire
w network from the asset and rule dimensions, helping users learn asset
details from a global perspective.
Check Associates check templates with assets and checks all rules contained
Task in the check templates on the corresponding assets.
Repairi Provides repair task management for some rules that support
ng automatic repair.
Script
Task
Rule Collects and aggregates check results of multiple tasks on the entire
View network from the rule dimension.
Asset Collects and aggregates the check results of multiple tasks on the
View entire network from the asset dimension to warn assets with
configuration risks.
Check Checks whether the configuration rule items have security risks based
Baselin on the baseline configuration. You can search, modify, and view
e baselines as well as restore the default value of the baseline.
Manag
ement
Check Selects required rule items from the check baseline based on the
Templa application scenario and configure the check template.
te
Manag
ement
Figure 7-12 shows the principles of security configuration check management.
Figure 7-12 Technical principles of security configuration check management
7.2.4 Data Collector

iMaster NCE-IP
7.2.4.1 Feature Description

As a visualized platform, the Data Collector app can collect data such as version
information and running configuration information of NEs in one-click mode.
After data collection is complete, the collection result can be uploaded to the
corresponding cloud analysis platform for subsequent analysis and report
generation.
Oriented to frontline engineers, the Data Collector app adopts an E2E operation
process, focuses on intelligent data collection, and builds three key capabilities:
● Synchronizes and manages NE information in one-click mode, allowing users
to perform quick and convenient operations.
● Collects data such as version information and running configuration
information of NEs in one-click mode based on collection templates, and
generates collection result files.
● Provides built-in standard collection templates to meet common user
requirements, and supports custom templates to meet personalized
requirements.
Figure 7-13 E2E operation process
7.2.4.2 Application Scenarios

Engineers usually use the data collection tool to collect data during routine
maintenance, and network evaluation.
Main application scenarios:
● During network maintenance, technical support engineers collect inspection
information about devices on the live network and evaluate the network
health status.
● When a fault occurs on the network, technical support engineers can collect
NE fault information to locate the fault and help rectify the fault.
● During network optimization, sales engineers collect the version information,
running configurations, and port usage of the devices on the existing network
to evaluate the customer network. In this way, sales engineers can find the
network bottlenecks and security risks in time and provide network
optimization suggestions for customers.

iMaster NCE-IP
NOTE
Engineers must obtain the customer's authorization before collecting data and can
perform only operations within the scope approved by the customer. After the
collection is complete, the collection result can be transferred out of the customer
network only after being authorized by the customer.
7.3 Network 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
meets customer requirements for network convergence and service growth.
7.3.1 Basic Functions

This section presents an overview of the basic functions and features of NCE.
Table 7-19 Overview of the functions and features of NCE

Functio Description
n or
Feature
Security This function secures NCE through user management, login

manage management, rights- and domain-based management, along with
ment other security policies. As a comprehensive solution, security
management also includes managing logs about logins, user
operations, and NCE running.
For details, see 7.2.3 Security Management.
NE NCE can only successfully communicate with managed NEs after the
commu connection parameters are correctly set.
nication Users can query or set the said parameters on NCE as follows:
paramet
er ● Query and set the SNMP parameters.
manage ● Manage the default SNMP parameter template.
ment ● Query and set the NE Telnet/STelnet parameters.
● Set the Telnet/STelnet parameters in batches.
● Manage the Telnet/STelnet parameter template.
● Manage the FTP/TFTP/SFTP parameter template.
● Manage the NETCONF parameter template.
● Query and set the NE NETCONF parameters.
● Set CloudOpera CSM communication parameters.

iMaster NCE-IP
Functio Description
n or
Feature
Topolog In topology management, the managed NEs and their connections

y are displayed in a topology view. Users can learn the network
manage structure and monitor the operating status of the entire network in
ment real time by browsing the topology view.
For details, see 7.3.1.1 Topology Management.
DCN NCE communicates with NEs and manages and maintains network
manage nodes through a data communication network (DCN).
ment For details, see 7.3.1.2 DCN Management.
Alarm Alarm management enables O&M personnel to centrally monitor the

manage NE, system service, and third-party system alarms and quickly locate
ment and handle network faults, ensuring normal network operation. For
details, see 7.2.2 Alarm Management.
Perform Network performance may deteriorate because of internal or external

ance factors and faults may occur. To achieve good network performance
manage while controlling costs, network planning and monitoring are
ment necessary. In addition, network efficiency needs to be measured in
terms of the throughput rate, resource usage, and error rate.
Performance management enables users to detect the deteriorating
trends in advance and solve the potential threats so that faults can
be prevented. In addition, high-precision (10-6) performance
measurement based on service packets is implemented to collect
performance indicators, including the packet loss rate, delay, and
jitter.
For details, see 7.3.1.3 Performance Management.
Inventor NCE collects, queries, prints, and exports network-wide physical

y resources and service resources in a unified manner. This helps users
manage obtain resource information on the entire network in a convenient,
ment quick, and accurate manner to support service planning, routine
maintenance, NE warranty, and network reconstruction.
For details, see 7.3.1.4 Inventory Management.
NE NE software management manages NE data and upgrade or

softwar downgrade NE software, including data saving and backup as well as
e policy management. Upgrading or downgrading NE software includes
manage loading, activation, restoration, task management, and software
ment library management.
For details, see 7.3.1.5 NE Software Management.
Centrali Centralized task management manages and coordinates all scheduled

zed task tasks in a unified management GUI. Two types of tasks are managed
manage in the centralized task management mode: system scheduled tasks
ment (periodic) and custom scheduled tasks (one-off). The two types of
tasks can be scheduled to run automatically. Users can set
parameters and browse the task status, progress, and results.

iMaster NCE-IP
Functio Description
n or
Feature
NE NE template management allows users to bulk configure NEs by

templat using configuration templates. This makes NE configuration faster
e and easier. Repetitive and labor-intensive data entry can be avoided
manage by using templates that automatically fill in the parameter values of
ment the NEs.
NE data The batch configuration of NE services is supported by using

configur configuration templates, importing data sheets, and loading
ation configuration files. NCE also supports the backup, restoration, and
and synchronization of NCE and NE data. With this function, services can
manage be provisioned quickly on the GUI.
ment
7.3.1.1 Topology Management

In topology management, managed NEs and their connections are displayed in a
topology view. Users can learn the network structure and monitor the running
status of the entire network in real time by browsing the topology view.
NCE provides a physical topology view, clock view, and custom view. By browsing
these views from different perspectives, users can monitor and learn the running
status of the entire network.
NCE provides service topologies for various E2E services, including VPLS, PWE3,
L3VPN and aggregation services, and tunnels. By using the service topology
function, users can easily view and configure related services.
Physical Topology View

The physical topology view consists of a tree on the left and a view on the right.
The tree shows a layered network structure, and the view displays managed
objects (MOs) in different places (coordinates).
Users can set the background image of the topology view. NCE supports multiple
image formats. Figure 7-14 shows the NCE topology view and its functions.

iMaster NCE-IP
Figure 7-14 Topology view and its functions
1. Left panel 2. Topology view 3. Toolbar

● Resources: Displays Displays all managed Allows you to save
all subnets managed NEs, connections topology locations, lock or
by NCE. Users can between NEs, and unlock views, refresh views,
quickly locate subnets on NCE. set topology display,
specific subnets. ● In the topology view, display or hide link
● Legend & Filter: Sets users can create bandwidth, and zoom in or
the display modes of subnets, NEs, and out views.
the objects in the links, configure NE
view, views the data, browse fibers/
description of each cables, delete
legend, and quickly topology objects,
locates objects. browse current
● Toolbox: Creates alarms, and
subnets and sets synchronize NE
topology object configuration data.
layouts. ● The filter tree and
legends are provided
to check the NE
status and
communication
status.
● The search function
is provided to quickly
locate NEs.

iMaster NCE-IP
4. Search & information 5. Displays the client 6. Displays the NCE login
panel time. username.
On the information
panel, users can search
for topology objects,
view NEs, subnets, and
connections, and add
common operations.
7. Displays the name 8. Overview 9. NE statistics

(specified on the Helps users locate the Double-clicking a subnet
current NCE client) and area displayed in the displays the NE type and
IP address of the topology view. number of NEs in this
current NCE server. subnet.
By default, the NE
information in the root
node of the physical
topology is displayed.
Alarm Display in the Topology View

Alarms in NCE topology can be displayed with different colors or icons to identify
the subnet and NE statuses. Icon colors or state icons are provided to display
alarms in the topology view. Icon colors are used by default.
Figure 7-15 Alarm display in the topology view
In the physical topology tree, users can select nodes at different levels, such as a
subnet or an NE, to browse current alarms. Alarm indication of NCE works as
follows:
● The color of a topology node indicates the running status (such as normal,
unknown, or offline) and alarm status of a monitored NE.
● If an NE reports alarms of different severities, the color or icon that indicates
the highest severity of the alarm is displayed for the NE in the topology view.
● If multiple nodes on a subnet report alarms, the color or icon that indicates
the highest severity of the alarm is displayed for the subnet in the topology
view.
● Users can switch to the current alarm page of an NE using the shortcut menu
of the NE node or query the details of current alarms on the NE panel.

iMaster NCE-IP
Automatic Topology Discovery

NCE provides automatic topology discovery to automatically add NEs to topology
views. This function helps reduce manual operations and operating expense
(OPEX).
Figure 7-16 Illustration of automatic topology discovery
1. NCE provides a wizard that instructs users to configure the parameters

required for automatic discovery, such as the task type, SNMP parameters,
and IP address range.
2. Based on the configuration, NCE searches for the required NEs in the specified
network segments, displays them, and uploads their basic information. This
simplifies basic settings of the NEs.
3. Automatic discovery can stop at any time. After the automatic discovery is
complete, users can view Discovery Failure Cause and Handling
Suggestions.
Automatic topology discovery of NCE works as follows:
● Creating NEs in batches

– Creating SNMP NEs: When NCE communicates with SNMP NEs properly,
NCE can search out all the NEs by IP address or network segment and
create the NEs in batches.
The following NEs are included:
▪ Router series
▪ Switch series
▪ Security NE series
– Creating transport or PTN NEs in batches: Based on the IP address of a
GNE, network segment where a GNE resides, or the NSAP address of a
GNE, NCE searches out all the NEs that communicate with the GNE and
creates the NEs in batches.

iMaster NCE-IP
– Importing NEs: Users can import the IP addresses and communication

parameters of NEs to NCE to create the NEs in batches.
● Automatic NE discovery: NCE automatically discovers NEs it can manage,
creates NEs, and uploads NE data.
● Automatically creating fibers/cables/microwave links and links: NCE
automatically discovers fibers/cables/microwave links and links and creates
them in batches.
Clock View
The clock view provides a visualized platform for setting NE clocks, querying the
network-wide clock synchronization status, tracing and searching for clocks,
synchronizing with physical views, displaying master clock IDs, querying clock
attributes, and displaying the clock locking status. It supports physical-layer clocks,
PTP clocks, ACR clocks, and ATR clocks. The clock view displays multiple types of
NEs on the entire network, including:
● PTN series, NE40E routers, ATN series, and CX600
Figure 7-17 Clock view and its functions
Automatically Viewing the clock Configuring clocks:

discovering the network topology: Users can configure the
topology After NCE automatically following NE clocks on
NCE searches for clock discovers the clock the clock configuration
links between all NEs in topology, users can view page of the NE Explorer:
the entire network to the clock trace physical-layer, PTP, ACR,
obtain the clock tracing relationships on the and ATR clocks. The
relationships of all the entire network. To adjust clock configurations vary
NEs. The search can be the clock topology, users with NE types.
performed by NE or by can manually create and
clock link type. When the delete topological nodes
clock source of an NE and links.
has changed, another
clock trace relationship
search is required.

iMaster NCE-IP
Monitoring clock Switching clocks Synchronizing with the

changes: manually: physical view:
When an NE or a link By switching between Users can synchronize
fails or clock sources clock links, users can the coordinates of NEs
switch on a network, change the current clock and subnets in the clock
NCE automatically trace relationships view with the
updates the clock trace between NEs. corresponding
relationships and the coordinates in the
clock synchronization physical view. The
status. The clock alarms subnets that have clock
generated on the NE NEs are also
where a clock change synchronized from the
occurs help users locate physical view to the
the fault. clock view. Empty
subnets in the clock view
are deleted.
Querying clock Viewing the clock status: Checking clock loops:

attributes: Users can query the Users can check the
Users can query the type, specific configurations of network-wide clock trace
hops, and port name for a clock NE to diagnose relationships for clock
clocks traced by the and troubleshoot loops. If any clock loop is
current NE, and view the possible clock NE faults. contained in the check
compensation value for result, users can double-
clocks traced by the port. click the loop to locate it
on the NEs in the clock
view and correct the NE
configurations.
Redirecting to the Redirecting to the clock Viewing the master clock

physical view: view: ID:
Users can be redirected Users can be redirected For an NE that has clock
from the clock view to to the corresponding trace relationships, when
the corresponding subnet in the clock view. users move the pointer
subnet in the physical If the subnet does not over a clock NE, a tooltip
view. If the subnet does exist in the clock view, will pop up, displaying
not exist in the physical the root node will be the clock mode, master
view, the root node will displayed. clock ID, and port status
be displayed. of the NE.
Viewing the cable Querying clock- Browsing real-time or

transmission warp unsynchronized/unlocked historical clock
report: NEs: performance:
NCE allows users to Users can search for Users can query the
query cable transmission clock NEs in the clock performance status
warp values for PTP unsynchronized or on the performance
clock links between NEs. unlocked state. In this monitoring page.
Users can easily find the list, users can select
sites with large warp desired NEs and export
values and perform their data.
measurement only for
these sites.

iMaster NCE-IP
The clock view can Querying clock tracing Exporting NE clock

display NEs copied in the trails: information:
physical root view and NCE highlights the Users can export the
their clock trace current clock tracing clock information about
relationships. Copied NEs paths of a clock NE. one or all NEs to a
have the same clock When a fault occurs, specified directory.
trace relationships as users do not need to
their source NE. draw the clock tracing
path between NEs
manually. This improves
fault diagnosis efficiency.
Custom View
The custom view is a subset of the main topology view. Network entities can be
NEs, NCE, and subnets. Typically, network management personnel need to
customize views, and choose network entities within their management scope
from the main topology view.
Figure 7-18 Custom view
7.3.1.2 DCN Management

NCE communicates with NEs and manages and maintains network nodes through
DCNs.
On the DCNs, NCE and NEs are considered as nodes. These nodes are connected
through Ethernet or DCCs. The DCN between NCE and the managed network is
divided into two parts:
● DCN between the NCE server and NEs: The NCE server communicates with
NEs through a local area network (LAN) or wide area network (WAN). In
practice, NCE and NEs may be located on different floors, in different
buildings, or even in different cities. Therefore, NCE and NEs are usually
connected through an external DCN with switches and routers.

iMaster NCE-IP
● DCN between different 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.
Huawei's NEs support DCN networking through the following communication
protocols:
● TCP/IP (IP over DCC). Data transmitted in the DCC is encapsulated through
the Transmission Control Protocol/Internet Protocol (TCP/IP).
● OSI (OSI over DCC). Data transmitted in the DCC is encapsulated through
Open Systems Interconnection (OSI).
NOTE
● IP and OSI are standard communication protocols, which can function in networks using
devices from different vendors. In addition, these two standard protocols can be
adopted on networks consisting of only Huawei devices. In the case of a hybrid network
consisting of optical network NEs from different vendors that do not support IP or OSI,
Huawei provides solutions such as transparent transmission of DCC bytes and Ethernet
service channels' transparent transmission of management information.
DCN Functions Supported by NCE-IP

The following DCN management functions are provided for ATN and CX series
NEs:
● Automatically add non-gateway NEs to NCE in batches. Users do not need to
plan data before ATN series NEs are powered on and added to NCE for
management.
● Show the running status and connection status of NEs in the DCN view.
7.3.1.3 Performance Management

When the network is running properly, internal and external factors may affect
network performance and cause network faults. To ensure sufficient network
performance at low costs and to prepare for future performance requirements,
users need to plan, monitor, and measure aspects of network efficiency, such as
throughput, usage, and error rate. Through performance management, tendency
towards deterioration can be noticed early and solved before a fault occurs. In
addition, high-precision (10-6) performance measurement based on service
packets is implemented to collect performance indicators, including the packet
loss rate, delay, and jitter.
NCE provides a GUI for monitoring network KPIs and displaying statistics about
collected performance data.

iMaster NCE-IP
Figure 7-19 Performance management process
Huawei NCE provides the performance monitoring function, which supports NE-
level and network-level performance management. This function is applicable to
access NEs, IP NEs and transport NEs. When a performance instance is created,
NCE can collect performance data from NEs at specified intervals.
● Monitoring NE performance. This function supports the following NE-level
performance indicators:
– CPU usage
– Memory usage
– Hard disk usage
● Monitoring network traffic. This function is used to collect the traffic statistics
of network ports, including:
– Inbound traffic
– Outbound traffic
– Packet error rate
● Monitoring SLA data. This function supports multiple types of SLA data,
including:
– Delay, jitter, and loss rate of ICMP, TCP, and UDP packets
– Connection delay and download speed of Internet services such as HTTP
and FTP
● Collecting interface-based traffic and performance indicators. This function
supports interface-based traffic in BGP/MPLS VPN, VPLS, and PWE3 services,
and performance indicators such as delay, packet loss rate, and jitter in BGP/
MPLS VPN SLA service. Performance indicators vary depending on the NE
type.

iMaster NCE-IP
● Setting performance thresholds. This function allows users to set thresholds

for specific performance indicators. NCE also provides default global settings
for batch configuration. The following thresholds can be set: The following
thresholds can be set:
– Upper and lower threshold
– Alarm thresholds
● Maintaining data. With this function, users can:
– Save performance data
– Age performance data
Performance Data Collection Capability

NCE supports the following performance collection modes:
● Collection based on SNMP

NOTE
● NEs must respond in 0.05s to collection requests sent from NCE. Otherwise, the actual
performance collection capability is compromised.
● The preceding collection capabilities are applicable only to SNMPv1 and SNMPv2c. For
SNMPv3, only 2/3 of the data collection capabilities are reached. For example, on a
large-scale network, the performance collection capability for SNMPv1 and SNMPv2c is
150,000 equivalent NEs, and the performance collection capability for SNMPv3 is
100,000 equivalent NEs when max/min data aggregation is disabled. SNMPv1 and
SNMPv2c are insecure protocols. A more secure SNMPv3 protocol is recommended.
● Bulk collection based on a file transfer protocol, which is usually used for
large-capacity performance management.
● Collection based on Qx, a protocol developed by Huawei, which can be used
for MSTP, WDM, RTN, PTN, and OTN equipment.
Performance Monitoring Policy

● Customize the performance threshold template. Specifically, users can
customize a maximum of 16 performance threshold templates in addition to
the default template.
● Select the performance threshold template for an NE and set the performance
thresholds.
● Customize the RMON performance attribute template.
● Set the performance thresholds for a specified board.
● Set the NE performance monitoring time.
● Set whether to prompt unavailable time and threshold-crossing events in a
timely manner.
● Set the start and end time for monitoring Ethernet performance.
● Set the monitoring status of Ethernet performance events.
● Set the ATM performance monitoring time.
● Set the ATM performance monitoring period.
● Set the monitoring status of ATM performance events.
● Set real-time ATM performance monitoring.

iMaster NCE-IP
● Set performance thresholds by ports or channels.
Performance Data Aging

The storage duration of performance data varies depending on the collection
period. If the collection period is 5 minutes, 10 minutes, 15 minutes, or 30
minutes, performance data generated only in the last day is saved by default. If
the collection period is 1 hour or 1 day, performance data generated only in the
last 8 days or 30 days is saved by default.
Performance data can be aged in the database in either of the following ways:
● Automatic aging: Performance data is deleted automatically based on the
preset lifecycle values, such as the number of days for different granularities
and the database usage.
● Manual aging: Performance data is aged based on the user-defined
conditions, according to the aging type within the end date.
Performance Monitoring Template Management

Each performance monitoring template is a collection of performance indicators in
different indicator groups. Users can manage a performance monitoring task
easily by setting such a template.
There are different types of performance monitoring templates. Some may contain
indicators and indicator groups of network resources, while others may contain
both indicators and indicator thresholds.
SLA Template
This function enables users to configure SLA parameters in a template. This saves
operation time for configuring SLA parameters when creating an instance.
Monitoring Instance Management

Instance: Resource + Template = Instance. An instance collects data on some
indicators of a specific performance resource. A template can contain multiple
indicator groups.

iMaster NCE-IP
NOTE
● Resource: A resource is a telecommunication resource model, for example, NEs, boards,

ports, or links in a performance management domain. A resource can be either a
physical or logical entity. Logical resources contain physical resources. A resource has
specific performance indicators. A performance monitoring system collects indicator
values for resources.
● Profile: A profile is a set of performance data collection indicators. Indicators are
presented in indicator groups. Users can configure templates to manage performance
monitoring tasks easily.
● Indicator group: An indicator group is a set of statistics indicators of performance
measurement. Each indicator group contains one or multiple indicators with similar
properties.
● Indicator: Indicators are related with resources. It indicates an aspect of the performance
of a monitored resource, for example, CPU usage and memory usage. Performance
indicator values are calculated based on the performance data collected from the
monitored resource. A performance indicator has properties, such as the data type,
precision value (only for float), maximum value, and minimum value.
By creating a monitoring instance, users can collect resource performance data of

a specified device based on the pre-configured templates and scheduled policies.
One monitoring instance collects data for only one resource.
Users can perform the following operations about monitoring instances:
● Create a monitoring instance for the IP SLA from resources such as NEs,
boards, ports, and links to PTN and third-party equipment.
● Modify a monitoring instance.
● View a monitoring instance.
● Delete monitoring instances.
● Suspend a monitoring instance.
● Resume monitoring instances.
● Synchronize instance resources.
● Query and rectify monitoring instance exceptions.
● Query the threshold.
● Query the VPN SLA test result.
● Export instance information.
● Collect statistics about instances.
● View KPI values in the Performance Monitoring Management window.
Scheduled Policy Management

For performance instances using the SNMP collection protocol, a scheduled policy
specifies the time segments and interval at which the data needs to be collected.
Users can apply scheduled policies to the resources while creating or modifying a
monitoring instance.
Historical Performance Data Query

Users can collect network performance data within a specified period and save the
data in multiple formats. This provides reference for predicting changes in network
performance.

iMaster NCE-IP
NCE can query performance data by parameters such as the NE name, time, and
performance data type. Currently, 5-minute, 10-minute, 15-minute, 30-minute, 1-
hour and 1-day historical performance data can be queried. Users can view the
historical performance data of a network in a line chart or table. Line charts allow
the query result to be saved in .csv format, while tables allow the query result to
be saved in .csv, .html, .pdf, .txt, and .xml formats. For example, if performance
data is saved in .csv format, the result will be similar to Figure 7-20.
Figure 7-20 Saving the result
In addition, users can compare performance data in different periods in a line

chart or bar chart or compare the indicators of different resources in a chart.
Users can choose whether to view the historical performance of a resource in one
chart or multiple charts.
Real-Time Performance Data Query

Users can view real-time performance data in a table, line chart, or bar chart, and
save performance data in .csv, .html, .pdf, .txt, and .xml file format.
Users can also set the default display mode to line chart, bar chart, or table.
Network Performance Monitoring

Users can view the performance data of NEs, interfaces, IP links, Layer 2 links,
static tunnels, dynamic tunnels, and test cases on the same network by network
group. In addition, users can perform various tests on a network, such as a UDP
jitter test and FTP ping test, to evaluate the quality of networks and services and
analyze the correlation between the two.
● Create a network group.
Users can group the monitoring instances of resources of different types on
the same network according to customized rules, such as an area-based rule
or service-based rule. This facilitates performance data browsing and
comparison.

iMaster NCE-IP
● Analyze interface performance trends.

When network interface indicators are set, a performance trend graph of the
current time or of the past 12 hours can be generated for analysis.
● View the results of network monitoring instances.
Users can view the results of network monitoring instances to obtain
information about network-related indicators, evaluate network performance,
and analyze the correlation between indicators and network performance.
TCA Threshold Setting

NCE allows users to set thresholds for performance indicators using a threshold
crossing alert (TCA) monitoring template. When creating a performance statistics
task, users can use a data monitoring template to collect performance data, use a
TCA monitoring template to set the upper and lower thresholds, and use a
scheduled policy to collect performance data in a specified period or based on a
repetition period. NCE generates a TCA when the performance indicator value
exceeds a defined threshold in the TCA monitoring template, informing users of
network performance deterioration.
Database Size Calculator

NCE can calculate the required database space based on the number of collection
instances (number of interface resources), collection period, lifecycle, and the
number of indicators of each instance. In addition, NCE can calculate the
performance data lifecycle based on the number of collection instances (number
of interface resources), collection period, number of indicators of each instance,
and available database space.
7.3.1.4 Inventory Management

NCE provides the functions to collect, query, and export network-wide physical
resources (including virtual NEs and third-party NEs) and service resources. The
resources can be exported to XLS, XLSX, TXT, HTML, or CSV files. This helps users
obtain resource information on the entire network in a convenient, quick, and
accurate manner to support service planning, routine maintenance, NE warranty,
and network reconstruction.
● 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. Users can easily
view and export multi-layer attributes of various types of resources. Users can
also customize filter criteria to query data on the live network, improving
resource maintenance efficiency.

iMaster NCE-IP
● Users can customize categories to make statistics of physical resources from

multiple aspects, and export inventory reports for equipment rooms, racks,
subrack, NEs, boards, subboards, ports, optical/electrical modules, slot usage,
and passive components. This helps learn various types of resources on the
entire network, provides reference for E2E operation and maintenance, and
improves resource usage.
Users can customize categories to query network-wide resources from

multiple aspects in unified mode and make statistics for the resources. This
provides reference for E2E operation and maintenance.
– Service planning: Users can make statistics for the NEs, used slots, ports,
and optical modules to learn about online NEs, slot usage, idle ports,
optical splitting, and remaining bandwidth.
– Routine maintenance: Users can query racks, NEs, boards, and ports to
learn the running status of the rack power supply and NEs, software
version of NEs and boards, service configurations, and port rate.
– NE warranty: Users can query NEs and boards to learn about NEs created
in the specified time, or the hardware and software versions of boards.
– Network reconstruction: Users can make statistics for NEs by customizing
categories to learn about NE types, quantities, and positions.
The following table provides the functions of each type of physical or logical
resource, inventory query result, and the default categories of the inventory report.

iMaster NCE-IP
Table 7-20 Inventory function, resource query, and report statistics

Ty Res Function Queried or Exported Default
pe our Inventory Statistics
ce Categories
of the
Inventory
Report
Ph Equi Creates, modifies, or Equipment Room Name, Site, Country/

ysi pm deletes an equipment Site, Country/Region, Region&State
cal ent room, and queries, State/Province, City, /Province/
res roo exports, or collects Location, Room Number, City, Country/
our ms statistics on equipment Cabling Mode, Antistatic Region&State
ces rooms. Floor, Thickness of /
Antistatic Floor (mm), and Province&Cit
Remarks. y/Room
Number,
Cabling
Mode, and
Custom
Statistics
Rac Creates, modifies, or Rack Name, Equipment Rack Type,

ks deletes a rack, and Room Name, Rack Type, Height,
queries, exports, or Rack Height (mm), Rack Width,
makes statistics on Width (mm), Rack Depth Depth,
racks. (mm), Power Box Type, Height&Widt
Voltage (V), Number of h&Depth,
Batteries, Internal Battery, Power Box
Internal Power Supply, Type,
Internal MDF, Internal Voltage, and
Transmission, Number of Custom
Shelves, and Remarks. Statistics.
NEs Queries and exports NE Name, NE Type (MPU NE Type

NE information, Type), NE IP Address, (MPU Type),
collects statistics of Software Version, NE MAC Software
NEs by NE or subnet, Address, NE ID, Fibers/ Version, NE
and collects statistics Cables, Subnet, Subnet Type (MPU
on equivalent NEs. Path, Subrack Type, NE Type) &
Subtype, Communication Software
Status, Administrative Version,
Status, Physical Location, Equivalent
Created On, NE Alias, NE, and
Remarks, Patch Version Custom
list, LSR ID, Gateway Type, Statistics.
Gateway, Gateway IP,
Optical NE, and Life Cycle
Status.

iMaster NCE-IP

ce Categories
of the
Inventory
Report
Sub Queries, exports, and NE Name, Subrack Name, Subrack

rack collects statistics on Subrack Type, NE ID, NE Type,
subracks by NE or IP Address, Software Equipment
subnet. Version, SN (Bar Code), Room, Rack,
Subnet, Subnet Path, NE
Subrack ID, Subrack Type(MPU
Status, Subrack Alias, PN Type), and
(BOM Code), Description, Custom
Manufactured on, Statistics.
Equipment Room Name,
Rack Name, Subrack
Number, and Remarks.
Boa Queries, exports, and NE Name, Board Full Board Type,

rds collects statistics on Name, Board Name, Board
boards by NE or Board Type, NE ID, NE IP Type&Hardw
subnet. Address, NE Type (MPU are Version,
Type), Subrack Type, Board
Subrack ID, Slot ID, Type&Softwa
Hardware Version, re Version,
Software Version, SN (Bar and Custom
Code), Board Alias, Statistics.
Remarks, Model, Rev
(Issue Number), FPGA
Version, BIOS Version,
Board Status, Protection
Role, PSTQ, PN (BOM
Code), Administrative
Status, Description,
Manufacture On, and
Create On.
Sub Queries, exports, and NE Name, NE Type (MPU Subboard

boa collects statistics on Type), Subboard Full Type,
rds subboards. Name, Subboard Name, Subboard
Subboard Type, Subrack Type&Hardw
ID, Slot Number, Subslot are Version,
Number, Hardware Subboard
Version, Software Version, Type&Softwa
SN (Bar Code), Subboard re Version,
Status, Subrack Alias, and Custom
Description, Remarks, PN Statistics.
(BOM Code), Manufacture
On, Model, and Rev (Issue
Number).

iMaster NCE-IP

ce Categories
of the
Inventory
Report
Port Queries, exports, and NE Name, NE Type (MPU Port Type

s collects statistics on Type), Shelf Number, Slot
ports. Number, SubSlot Number,
Port Number, Phone
Number, Port Full Name,
Port Name, Port Type,
Port Rate (kbit/s), Port
Level, Administrative
Status, Operational Status,
Port Alias, Remarks, and
Port Description.

iMaster NCE-IP

ce Categories
of the
Inventory
Report
Opti Sets user labels for the ● SFP Information: Port, Router and
cal/ optical/electrical SFP Type, Fiber/Cable Switch
Elec module, and queries, Type, Logical Type, Optical/
tric exports, or collects Physical Type, SN(Bar Electrical
al statistics on optical/ Code), CLEI Code, Module:
mo electrical modules. PN(BOM Code/Item), Wave Length
dule Model, Rev(Issue (nm), NE
s Number), Name+Wave
Manufacturer, Date of Length (nm)
Manufacture, User
Label, Description,
User-defined Info
● Router and Switch
Optical/Electrical
Module: Serial No.,
Optical/Electrical Type,
NE Name, Port Name,
Port Description, Port
Type, Receive Optical
Power (dBm),
Reference Receive
Optical Power (dBm),
Reference Receive
Time, Receive Status,
Upper Threshold for
Receive Optical Power
(dBm), Lower
Threshold for Receive
Transmit Optical Power
(dBm), Reference
(dBm), Reference
Transmit Time,
Transmit Status, Upper
Threshold for Transmit
Lower Threshold for
(dBm), SingleMode/
MultiMode, Speed
(Mbit/s), Wave Length
(nm), Transmission
Distance (m), Fiber
Type, Manufacturer,

iMaster NCE-IP

ce Categories
of the
Inventory
Report
Optical Mode
Authentication, Port
Remark, Port Custom
Column,
OpticalDirection Type,
Vender PN, Model, Rev
(Issue Number)
Slot Collects statistics on NEs, NE Type, NE Name, NE Type

usa the total slots and Total Slot Count, Used (MPU Type),
ge used slots by NE type Slot Count, Vacant Slot NE
stati and NE, so that users Count, Slot Usage %
stics can determine the
board capacity and
future expansion.
Pass Collects statistics on NE, Serial Number, DCM -

ive dispersion Name, BOM, Barcode,
com compensation modules Compensation
pon (DCMs) to manage Distance(km), IN Port,
ents DCM passive devices. OUT Port, Location,
Only NCE-T supports Vendor, Description,
this function. Remark
Lo Fibe Adds multiple fibers Pipe Name, Pipe Memo, -

gic r/ and cables to a pipe Creation Time, Creator,
al Cab for management. Fiber Count
res le Fiber/cable pipe
our pipe management is
ces s supported when the
platinum service is
used. Pipe
management involves
creating, deleting, or
querying a fiber/cable
pipe, and adding or
removing fibers and
cables to or from a
fiber/cable pipe.

iMaster NCE-IP

ce Categories
of the
Inventory
Report
Link Manages and Alarm Severity, Link -

s maintains virtual links, Name, Link Type, Network
layer 2 links, and IP Protocol Type, Source NE,
links, involving creating Source IP, Source Port,
a link, adding a link to Source Port IP, Source Port
a link group, and Alias, Sink NE, Sink IP,
viewing links and link Sink Port, Sink Port IP,
alarms. Sink Port Alias, Link Level,
Link Rate (bit/s),
Remaining Upstream
Bandwidth (Kbit/s),
Remaining Downstream
Bandwidth (Kbit/s), Build
Time, Remarks, User
Label, Owner, Weight
Elec NCE exports electronic - -

tron labels of devices that
ic comply with the new
labe IBMS script
ls specifications and
saves the data in XML
files. This helps
maintenance personnel
view and manage
network inventory
resources in the IBMS.
7.3.1.5 NE Software Management

NE Software Management is used to manage NE data and upgrade or downgrade
NE software. Managing NE data includes data saving and backup as well as policy
management. Upgrading or downgrading NE software includes loading, activation,
restoration, task management, and software library management. To ensure
security, use SFTP for data transmission between NCE and NEs.
The main functions are listed as follows:
● Saving: After the configuration is complete, the configuration data is saved in

the flash drive or hard disks of NEs so that the data will not be lost once the
system is restarted. The following saving methods are supported:
– Manual
– Automatic (by creating a task)
– Automatic (by creating a policy)

iMaster NCE-IP
● 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. If NCE has permission to manage the NE and no loading, backup, or
restoration operation is being performed on the NE, the NE accepts the
backup request and transfers the contents to be backed up to the backup
path on the NCE server through the file transfer protocol. The contents can
also be transferred to the client or to the third-party server. The number of
backup files depends on available space in the backup path. The following
backup methods are supported:
– Manual
– Automatic (by creating a task)
– Automatic (by creating a policy)
● Policy management: Backup policies enable automatic NE backup (periodic or
triggered) for routine NE maintenance. The policy method is used periodically,
and is mainly used for frequent operations, such as data saving and backup.
Users can select a policy based on the scenarios at the sites.
● Loading: Software is loaded for NE upgrade. If NCE has permission to manage
NE upgrade and no other loading, backup, or restoration operations are being
performed on an NE, the NE will accept the loading request. NCE then
transmits the contents to be loaded to the NE by using the transfer protocol.
The following loading methods are supported:
– Creating a task for automatic loading
– Creating an automatic upgrade task for automatic loading
● Activating: New NE software needs to be activated by restarting NEs. If NCE
has permission to manage NE upgrade and no other loading, backup, or
restoration operations are being performed on an NE, the NE will accept the
activation request. The following activation methods are supported:
– Creating an automatic upgrade task for automatic activation
● Restoration: An NE can be restored using the backup NE data. If NCE has
permission to manage NE upgrade and no other loading, backup, or
restoration operations are being performed on an NE, the NE will accept the
restoration request. NCE then transmits the contents to be restored to the NE
by using the transfer protocol. The following restoration methods are
supported:
– Manually restoring the data
– Creating a task for automatic restoration
● Task management: NCE encapsulates all operations into tasks. By creating an
upgrade task or a downgrade task for software or a patch, users can upgrade
or downgrade the software or patch in one-click mode or at the scheduled
time. The task method is not periodic. It is mainly used for non-frequent
operations, such as upgrade. Users can select a task based on the scenarios at
the sites.
● Software repository management: NE software is managed in a repository. For
example, users can upload NE software from the NCE client or NCE server to
the software repository for centralized management and efficient loading.
● NE license management: allows users to query, apply for, install, and adjust
NE licenses (in case of capacity or a server change). The license controls the
validity period or functions of an NE. Therefore, users need to view the license
status and change the expired license. Otherwise, services will be affected.

iMaster NCE-IP
● NE upgrade wizard: During the upgrade preparation, the wizard provides

guidance through the process of creating an upgrade project and upgrade
tasks. During the upgrade, functions such as filtering and search, status
statistics, and batch operations are optimized to provide more user-friendly
upgrade operations.
7.3.2 IP Network Management
7.3.2.1 IP NE Management
Basic Capabilities
NCE is able to manage the following series of IP NEs: PTN, NE, ATN, CX, service
gateway, R/AR router, switch, voice gateway, security, and iCache, covering VRPv5-
based, VRPv8-based, and YANG NEs.
NOTE
If users need to configure and manage BGP private network instances in the YANG NE
management process, enable the YANG management mode (bgp yang-mode enable) on
devices first. For details, see the command description provided by devices.
PnP
PnP helps engineers remotely commission and deliver basic configurations to a
large number of NEs at the same time, freeing engineers from going to sites and
greatly improving the deployment efficiency.
Usage Scenarios
PnP is used for making scripts and bringing NEs online during deployment. It
provides a rich set of predefined templates, where users need to set only a few
parameters for generating basic NE configuration scripts. Remote DCN
commissioning eliminates the need for planning before NE power-on, and NEs are
automatically added to NCE for management.
During deployment, PnP is mainly used for remotely commissioning newly added
NEs and bringing them online so that NCE can manage these NEs. PnP delivers
basic configurations to NEs in different networking scenarios to complete batch
NE deployment.
Automatically Available DCN
● PnP based on network planning/design (tools): Automatically available DCN

is leveraged to automatically establish connections between NCE and NEs and
generate scripts based on plans.
● Tool-free PnP: Network planning is performed after devices go online, and
scenario-specific custom templates are offered to facilitate planning.
a. Custom templates are offered for the L2+L3 and HVPN service scenarios.
b. Management IP addresses, NNI IP addresses, and IGP parameters are
automatically allocated to online devices.
Custom Deployment Solutions

iMaster NCE-IP
Users can flexibly customize a group of deployment templates (including

parameter IDs and expressions) based on the site scenarios and typical
configurations.
● Based on deployment templates, users export and fill in a service planning
table. They can import planned NE configurations (such as NE addresses and
interface IP addresses) in batches and adjust the sequence of parameters in
the planning table.
● Users can also customize scenario-specific deployment templates by
importing device command scripts and correlating parameters across device
role templates.
● Basic and service configuration scripts are generated at the same time. With
the DCN online function, configurations are delivered instantly when devices
go online.
IP Network Assurance
NCE provides various network assurance functions, such as health check,
intelligent troubleshooting based on path visualization, automatic locating of top
N typical alarms, and network-level alarm correlation. This greatly reduces skill
requirements for fault locating, shortening the average fault locating time from
more than 1 hour to 10 minutes.
IP NE health check: This check is performed automatically so that it takes only
seconds to check a single NE (including its optical power and IP address).
Engineers no longer need to check configurations manually, resulting in a
significant increase in the check efficiency while also reducing the potential faults
linked with inappropriate basic configurations.
PTN network health check: Network running indicators are centralized on one
page where users can compare the current and historical PTN network statuses
during routine maintenance to find and rectify exceptions in advance.
Intelligent troubleshooting based on path visualization: NCE supports
protection path discovery, covering five protection schemes (primary/secondary
PW, VPN FRR, VRRP, E-APS, and TE HSB) on the live network. It can also discover
and display primary and backup paths to facilitate the locating of faults related to
service path switching. In addition, NCE clearly shows specific fault locations in
hierarchical paths (at the service, tunnel, route, and link layers). It is also able to
discover paths in the VPLS and HVPLS scenarios and visualize path
troubleshooting. The diagnosis process is automatically determined based on MBB
scenarios and fault types (such as interruption, deterioration, and clock switching).
The 300 check items cover key MBB features, improving accuracy and efficiency.
Automatic locating of top N typical alarms: For top N alarms, NCE
automatically packages detection means, thereby providing one-click diagnosis
and handling suggestions.
Network-level alarm correlation: By analyzing the alarms reported by IP NEs
within a period, NCE identifies root and correlative alarms based on rules and
displays them to maintenance personnel.

iMaster NCE-IP
7.3.2.2 IP Service Management

NCE supports unified management of services, including tunnels and L3VPN,
EVPN, VPLS, PWE3, composite, and CBR services. Specific functions include service
provisioning, monitoring, and diagnosis.
Service Provisioning
All service configurations can be complete on one neat UI. Service templates can
be used to automatically generate parameters for multiple NEs at a time. Users
can preview the configuration results in the topology view before delivering
configurations.
● FlexE channel functions:
– Configure FlexE channels.
– Configure FlexE channel protection groups.
● MTN FG channel functions:
– Configure MTN FG channels, restore services, and manage discrete
services.
● Dynamic tunnel functions:
– Provision SR-TE, SR-TP, and RSVP-TE tunnels.
– Configure disjoint groups.
● SR Policy functions:
– Provision SR Policies.
– Set color for SR Policies.
– Configure candidate paths.
● Static tunnel functions:
– Deploy static LSPs or static CR LSPs to support MPLS access.
– Set link bandwidth thresholds.
When computing paths for static CR LSPs, NCE generates link weights
based on remaining link bandwidths and thresholds, thereby achieving
traffic balance.
● MBGP L3VPN service functions:
– Provision unicast and multicast MBGP L3VPN services.
– Provision services by using a template.
– Automatically create tunnels during service creation.
● EVPN service functions:
– Set the connection type to P2P or MP2MP.
– Provision services by using a template.
– Automatically create tunnels during service creation.
● Static L3VPN service functions:
– Set the networking mode to full mesh or custom.
– Configure VPN fast reroute (FRR) and IP FRR, and bind L3VPN services to
TE tunnels.
– Configure static routes.

iMaster NCE-IP
● VPLS service functions:

– Support VPLS services in LDP or static signaling (Martini) mode.
– Support VPLS services in BGP signaling (Kompella) mode.
– Support VPLS services in multi-VSI mode.
● PWE3 service functions:
– Configure static and dynamic PWE3 services.
– Manage the following types of PWE3 services: CES, ATM, Ethernet, IP
over PW, ATM interworking function (IWF), and heterogeneous
interworking.
– Configure management PWs.
– Configure backup PWs.
– Configure PW FRR.
– Configure CES fast protection switching (FPS).
● Composite service functions:
Composite services fall into three categories: custom, H-VPLS, and
PWE3+MBGP L3VPN. Their creation methods are different.
– Custom: Custom services include VPLS+PWE3, VPLS+L3VPN,
PWE3+L3VPN, Option A VPLS, Option A PWE3, Option A L3VPN, and
PWE3+PWE3. Users need to manually create or select individual services,
and add connection points to combine them into a composite service.
– H-VPLS: Users only need to add related nodes (such as VPLS, PWE3, or
PW switching nodes). NCE then automatically creates an H-VPLS
composite service.
– PWE3+MBGP L3VPN: Users only need to set a gateway IP address, select
an MBGP L3VPN service, and add a PWE3 service. NCE then
automatically creates a PWE3+L3VPN composite service.
● CBR service functions:
– Configure CBR services.
Service Discovery
The E2E service or tunnel data deployed on the network can be restored to NCE
through service discovery so that these services can be managed in an E2E
manner. This not only saves time but also avoids the impact of misoperation on
the original services.
● Static tunnels as well as static L3VPN, VPLS, PWE3, aggregation, and

composite services can be automatically discovered based on preset policies.
● Dynamic tunnels, EVPN services, and MBGP L3VPN services can be
automatically discovered based on service templates.
360-Degree Service View

This view makes service status and service object relationships clear and visible to
users. Specifically, it associates services with tunnels, and tunnels with routes. It
also clearly presents the hierarchical object and bearing relationships, which
facilitates fault locating and troubleshooting.

iMaster NCE-IP
Service Diagnosis
Diagnostic tools are used to check network connectivity and locate faults. Users
can generate diagnosis tasks based on selected services, perform operations in the
topology view, and check the diagnosis results.
Service Check and Test

● Configuration check: NCE checks the consistency of VPN service
configurations at different sites and informs users of where errors have been
made.
● Connectivity check: Ping and traceroute are provided for checking service
connectivity and locating faulty NEs.
● Protocol status check: NCE checks service protocol status and forwarding
tables. If errors are found, it directly shows the errors to help users locate
faults.
7.3.3 Third-Party NE Deployment

NCE provides basic NE management capabilities, including NE topology
visualization, specified alarms, and performance indicators.
The supported third-party NEs are listed below.
Table 7-21 Supported third-party NEs
Vend Product Hardwar Software SysOid Equiv

or Series e Version alent
Version Coeff
icient
Cisco ASR9000 ASR 6.3.26.4.2 1.3.6.1.4.1.9.1.1640 7

series 9922
ASR 6.4.2 1.3.6.1.4.1.9.1.1762 1

9904
ASR 6.1.36.3.2 1.3.6.1.4.1.9.1.1017 2.5

9010 6.3.36.7.3
ASR 6.3.26.3.3 1.3.6.1.4.1.9.1.1018 1.25

9006 6.4.26.7.3
ASR 6.3.26.3.3 1.3.6.1.4.1.9.1.1639 0.5

9001 6.4.26.7.3
NCS5500 NCS5504 6.5.37.3.2 1.3.6.1.4.1.9.1.2413 1.25

series
NCS5508 6.5.37.3.2 1.3.6.1.4.1.9.1.2349 2.5
NCS5516 6.5.37.3.2 1.3.6.1.4.1.9.1.2412 5
NCS6000 NCS6008 6.3.3 1.3.6.1.4.1.9.1.1851 10

series

iMaster NCE-IP

Version Coeff
icient
CRS CRS16SB 6.1.4 1.3.6.1.4.1.9.1.1331 10

series
CRS16S 6.1.4 1.3.6.1.4.1.9.1.613 10
Nokia 7750 SR-12 15.*19.* 1.3.6.1.4.1.6527.1.3.3 3

series
SR-7 15.*19.* 1.3.6.1.4.1.6527.1.3.4 1.5
SR-12e 15.*19.*2 1.3.6.1.4.1.6527.1.3.8 3

1.*
SR-a4 15.*19.* 1.3.6.1.4.1.6527.1.3.9 0.5
SR-1e 21.* 1.3.6.1.4.1.6527.1.3.11 0.5
SR-7s 15.*19.* 1.3.6.1.4.1.6527.1.3.17 0.5
Junip MX MX204 19.4.* 1.3.6.1.4.1.2636.1.1.1.2.10000 2

er series
MX480 18.2.*20.4 1.3.6.1.4.1.2636.1.1.1.2.25 2.5
R2.7
MX960 20.4R2.7 1.3.6.1.4.1.2636.1.1.1.2.21 3.5
MX2020 20.4R2.7 1.3.6.1.4.1.2636.1.1.1.2.93 5
MX10003 21.2.* 1.3.6.1.4.1.2636.1.1.1.2.139 1.25
T series T1600 20.4R2.7 1.3.6.1.4.1.2636.1.1.1.2.27 10
T640 20.4R2.7 1.3.6.1.4.1.2636.1.1.1.2.6 10
ZTE M6000-S 18S V5.00.10 1.3.6.1.4.1.3902.3.100.6008.6 10
8S Plus V5.00.10 1.3.6.1.4.1.3902.3.100.6008.7 2.5
3S Plus V5.00.10 1.3.6.1.4.1.3902.3.100.6008.1 1.25

4
3S V5.00.10 1.3.6.1.4.1.3902.3.100.6008.1 1.25

4
9000 9000-18E V5.00.10 1.3.6.1.4.1.3902.3.100.6010.1 5

A 3
6180H 6180H-A V5.00.*V5 1.3.6.1.4.1.3902.3.100.8000.2 1

.10.* 7
6120H 6120H-S V5.10.* 1.3.6.1.4.1.3902.3.100.6006.0 1
H3C CR16000 CR16010 7.* 1.3.6.1.4.1.25506.1.2024 2

-F

iMaster NCE-IP

Version Coeff
icient
CR16010 7.* 1.3.6.1.4.1.25506.1.2022 2.5

H-F
CR16018 7.* 1.3.6.1.4.1.25506.1.18 5

H
CR16010 7.* 1.3.6.1.4.1.25506.1.2310 5

H-FA
CR19000 CR19000 7.* 1.3.6.1.4.1.25506.1.1641 10

-20
RX8800 RX8800- 7.* 1.3.6.1.4.1.25506.1.2043 10

16
Through protocols such as SNMP, NETCONF, STelnet, BGP-LS, and PCEP, NCE
directly interacts with third-party routers to obtain device information and
implement the functions listed below.
Table 7-22 Third-party NE management functions

Feature Function Protocol Description
Topology Searching SNMP You can search for third-party NEs by

managem for NEs NE IP address. The discovered NEs are
ent then displayed in the topology view.
Discoverin LLDP Layer 2 links between third-party NEs

g links can be automatically discovered by
searching for third-party NEs.
BGP-LS Layer 3 links between third-party NEs

can be automatically discovered by
synchronizing NE configuration data.
Alarm Viewing SNMP You can view all standard alarms and
managem alarms some proprietary alarms of third-party
ent NEs.
Performan Creating SNMP You can create some performance

ce performan instances for third-party NEs.
managem ce
ent instances

iMaster NCE-IP
NOTE
● Currently, E2E features have not been adapted to third-party NEs. Therefore, the third-
party NE Explorer may not support the service parameters present in E2E features.
● The current version does not dim third-party NEs or report errors when delivering data
to them.
7.4 Service Provisioning
7.4.1 Network Slicing
7.4.1.1 Background
Driven by ever-increasing mobile and fixed network service requirements, carriers
may run different services on the same network. To prevent services from taking
bandwidth from others, carriers want to isolate service bandwidth. The transport
network carries various services with distinct traffic characteristics. For example, it
is difficult to assess the bandwidth of individuals' fixed broadband services; bursty
Internet traffic, in particular, requires high bandwidth and is insensitive to latency
(up to 50 ms). Enterprise services — some are latency-sensitive, some are not —
generally have clear Service Level Agreements (SLAs) regarding bandwidth and
latency. For latency-sensitive and latency-insensitive services on the mobile
transport network, one distinct difference is convergence ratio.
To address this issue, Network Slicing uses FlexE or channelized interfaces to

divide one physical network into multiple slices. These slices achieve hard
bandwidth isolation and deploy services independently, enabling customers to use
one network for multiple purposes.
7.4.1.2 Feature Introduction

Network slicing needs to streamline adaptation interfaces among usage scenarios,
network functions, and network resources, and support on-demand customization
and provisioning. For each type of service, resources are exclusive, but they
actually share the same physical infrastructure. This ensures the economies of
scale, improves the utilization of physical resources, reduces CAPEX and OPEX, and
enriches network operating models.
Network slicing provides tailored network functions and performance assurance

for specific scenarios, achieving on-demand networking. Network slicing has the
following highlights:
● Secure: Network resources are isolated among slices. Overload, congestion,

and configuration adjustment in one slice will not affect other slices. This
improves network security, reliability, and robustness.
● Dynamic: Network slices can dynamically allocate resources to meet
spontaneous service requirements.
● Elastic: Network slices may be elastically and flexibly scaled (for example,
through convergence and reconstruction) to adapt to dynamic changes in
user quantities and service requirements.

iMaster NCE-IP
● Optimal: Network functions can be tailored and flexibly deployed based on

service scenarios to achieve optimal service processes and data routes.
The network slicing solution of NCE uses FlexE or channel subinterface technology
to slice the bearer network in an E2E manner. NCE can uniformly orchestrate and
manage network resources and support visualized slice creation, management,
query, and cancellation. Simplified slice creation and one-click scale-up/down
further improve network O&M efficiency and experience.
Table 7-23 Slice features

Feature Description
Slice deployment FlexE interfaces are supported.

MTN channels (that is, FlexE channels) and
MTN FG channels are supported.
Slices can be deployed over channel
subinterfaces embedded in FlexE (including
FlexE Client interfaces) (routers).
Slices can be deployed over channel/
channelized subinterfaces (including Eth-Trunk
channel subinterfaces) (PTN devices and
routers).
On-demand slices are supported (flexible sub-
channels on routers).
The entire network or any subnet can be
sliced based on bandwidth values, bandwidth
percentages, exclusive links, or the shared
mode.
Slice management View resources in the slice topology view.

Adjust slice link bandwidth.
Delete links from slices.
Take the source and sink ports of slice links
online and offline.
Slice activation Activate slice links.
Slice-based service deployment Deploy SR-TE and SR-TP tunnels in slices by

setting affinity.
Bind VPN services to tunnels in a slice.
Create on-demand slices in a service-driven
manner (L2 EVPN or MBGP L3VPN services).
Switch to the network optimization view and
dynamic tunnel, SR Policy, and L2 EVPN
service management pages.
Slice restoration Supported

iMaster NCE-IP
NOTE
● In the single-IGP scenario (slices 1 to N share an IGP process with slice 0), all the
preceding functions are supported.
● In the multi-IGP scenario (slices 1 to N have their own IGP processes), the slice
deployment, slice management, and slice restoration features are supported. If the slice
activation and slice-based service deployment functions are needed, use the Network
Setup Automation app in PTN scenarios.
7.5 Analysis and Assurance
7.5.1 Network Performance Analysis

This section describes the features provided by Network Performance Analysis.
7.5.1.1 Telemetry Collection

Telemetry is a technology developed to fast collect data from physical or virtual
devices remotely. Devices periodically send information such as interface traffic
statistics, CPU data, and memory data to the collector in push mode. Compared
with the traditional pull mode (question-answer interaction), the push mode
provides more real-time and high-speed data collection.
Compared with other collection methods, Telemetry collection can be used on

larger networks and completed in a shorter period.
Report Specifications
Table 7-24 provides the specifications of Telemetry analysis reports.
Table 7-24 Specifications of Telemetry analysis reports
Report Resour Report and Function

Type ce
Basic Board Board Health Report:

Traffic Collects the performance indicators (such as the CPU usage
Report and memory usage) of boards based on subnets, helping
users quickly identify the boards with the heaviest load.
NE NE Health Report:
Collects the performance indicators (such as CPU usage
and memory usage) of NEs based on subnets, helping
users quickly locate NEs with the heaviest load.
Port Universal Interface Traffic Report:

Collects the performance indicators (such as the traffic rate
and bandwidth usage) of IP ports, helping users quickly
identify the interfaces with the heaviest load.

iMaster NCE-IP

Type ce
CBQos Interface CAR Traffic Report:

By configuring CAR, the traffic is restricted. This report
displays the number of bytes, packets, discarded bytes, and
discarded packets that pass through the interface.
Flex-Channel Slice Traffic Report:

Collects performance indicators of Flex-Channel slices, such
as the packet passing rate, packet discarding rate, and
bandwidth usage, to learn the traffic load of slices.
Flow TWAMP Quality Report:

By viewing the TWAMP quality report, you can clearly
learn the information and quality situation of each service
and find services to be focused on.
Link IGP Link Traffic Report:

Collects performance indicators of IGP links, such as the
traffic rate and bandwidth utilization, helping users quickly
locate interfaces with heavy loads.
IGP Link Queue Traffic Report:

Collects performance indicators of the IGP link queue, such
as the traffic rate and bandwidth utilization, helping you
quickly locate interfaces with heavy loads.
IGP Link Quality Report:

Collects the delay, jitter, and packet loss rate of IGP links to
quickly locate interfaces with heavy loads.
IGP Link Queue Quality Report:

Collects the delay, jitter, and packet loss rate of the IGP link
queue to quickly locate interfaces with heavy loads.
Service QoS Template Traffic Report:

Collects indicators (such as the number of discarded
packets and the packet rate) in the basic HQoS queue
(based on QoS profiles) and the packet rate in the total
traffic queue (based on QoS profiles), helping users
analyze the network congestion condition.
TE Tunnel Traffic Report:

Collects traffic data of TE tunnel services, such as the
maximum, minimum, and average traffic rate, as well as
the maximum, minimum, and average packet rate.
SR Policy Traffic Report:

Displays the traffic of SRPolicy services, such as maximum
traffic, minimum traffic, maximum package rate, and
minimum package rate.

iMaster NCE-IP

Type ce
Port Default Queue Traffic Report:

Collects indicators such as the number of discarded packets
and the packet rate in the port default queue, as well as
the total traffic packet rate to analyze the network
congestion condition.
7.5.1.2 Performance Overview

Network Performance Analysis of NCE provides performance overviews to clearly
display device status, which helps users monitor key device status and detect and
repair abnormal devices in time.
7.5.1.2.1 Introduction to Performance Overview

NCE provides the performance overview function, which allows you to view multi-
dimensional analysis on network performance data and quickly learn about the
network running status.
● You can quickly design overview charts using the dashboard.
● Various network analysis visualization capabilities are supported.
● The dashboard can be shared.
Performance Overview Management

You can manage performance overviews.
Table 7-25 Viewing charts
Operation Description
Viewing In the upper right corner of a chart, the time and period for
performance generating the current data are displayed.
data of a device
Refreshing a
Click in the upper right corner of a performance
performance
overview to refresh its data.
overview
Going to a Click in the upper right corner of a performance overview

report to go to the report page.
Exporting a
report Click to export the .png image.

iMaster NCE-IP
Table 7-26 Managing tabs

Adding a tab You can create multiple tab pages for multi-dimensional
page analysis visualization in various scenarios.
1. Click in the upper left corner. The Dashboard
Designer page is displayed.
2. Enter the name of the tab page in the Name text box.
3. Drag the chart to be displayed from the left pane to the
designer.
4. Set parameters for the new chart.
5. Click Commit and Publish.
Pinning a tab You can display a tab page that you concern on the top. This
page on top allows you to quickly locate the tab page.
Move the pointer to the name of the target tab page, click
, and choose Top from the drop-down menu.
Displaying an Display an overview tab page in full screen on the product

overview tab page.
page in full
screen ● Click and choose Full Screen from the drop-down
menu to display the overview tab page in full screen.
NOTE
Here, an overview tab page displayed in full screen does not
mean that the browser is displayed in full screen. If the browser
is set to display in full screen, the overview tab page can be
displayed in full screen over your monitor.
● Click in the upper right corner to exit the full screen

mode.
Editing a tab You can modify the tab page name to re-identify the tab
page. This allows you to quickly locate the tab page.
Click and choose Edit from the drop-down menu to

rename the tab.
Copying a tab You can copy an existing tab page and edit it to create
another tab page.
● Click and choose Copy from the drop-down menu. In

the dialog box that is displayed, rename the tab, and then
you can edit the chart and publish a new chart on a new
tab page.
● Click to go to the dashboard list and view the

successfully copied tab pages.

iMaster NCE-IP
Table 7-27 Managing the dashboard list

Viewing the View all dashboards (published or drafted) in the list.

dashboard list
Editing a Modify the dashboard name and chart parameters as

dashboard required.
Click to go to the dashboard list and click in the

Operation column of the dashboard to be edited.
NOTE
The built-in service charts are described in Built-in Charts.
Copying a Copy an existing dashboard.

dashboard
Click to go to the dashboard list and click to copy a
dashboard.
Favoriting/ Add a dashboard to favorites.

Unfavoriting a For example, you can add excellent dashboards created by
tab other users to favorites, edit them as required, and publish
them on the performance overview page.
1. Click to go to the dashboard list.
2. Click in the Operation column and choose Favorite

or Unfavorite.
NOTE
One can view the dashboards created by others but cannot edit
the dashboards.
Deleting a tab Delete redundant dashboards.
1. Click to go to the dashboard list.
2. Click in the Operation column and choose Delete.

iMaster NCE-IP
Table 7-28 Dashboard design areas

Area Description
Left ● Chart
panel Only line charts are supported.
(Compone Compared with Analysis component, Chart is
nts) stronger in dashboard customization. You can
customize a chart's title attributes, units,
background, border margins, and data sources, and
display or hide tool menus. Interaction between
charts is not supported.
● Analysis component: 15 chart types are supported.
Classifies services in charts.

You are allowed to add, edit, and delete service
(Service categories.
Card)
● Click on the right of Template Settings to add a
service category.
● Click on the right of a service name to rename

the service. In the editing state of the dashboard,
select a chart and click in the upper left corner of
the chart to manage the chart by category.
● Click on the right of a service name to delete a
service category.
NOTE
● The prerequisite for deleting a service category is that
the service category does not contain any charts.
● To remove a chart from a service category, click in

the upper right corner of the chart, as shown in the
following figure.
Middle Compositio Allows you to drag one or more charts or services to

panel n area in start analysis.
the middle
Right Basic/Data Allows you to set the chart title, chart type, and chart
panel data.

iMaster NCE-IP
Area Description
Upper- Canvas Adjusts the canvas scale, for example, reduces the scale
right Scale to view all charts on the dashboard or increases the
corner scale to view some charts on the dashboard.
Preview Previews the designed dashboard, avoiding rework after

the dashboard is published.
Click in the upper right corner to exit the preview.
Commit Verifies the integrity and validity of a dashboard and

submits the verified dashboard to the database.
Publish Publishes the dashboard.

By default, a published dashboard is added to favorites
and therefore displayed on the performance overview
page ( ). If you do not want to display the

dashboard on the performance overview page, go to
the dashboard list ( ) and remove the dashboard

from favorites.
Built-in Charts
Navigation path: Open the Network Performance Analysis app. On the homepage,
click to open the Dashboard Designer page.
Table 7-29 Performance Overview

Resource Performance Overview Name and Function
Type
IP RAN built- NE CPU Utilization Top 10:

in chart Displays the peak CPU usage of network-wide NEs, helping
users quickly locate the NEs with the heaviest load.
IPLink Peak RX Bandwidth Utilization Top10:

Helps users quickly identify the network-wide IP links with the
heaviest load and view the peak usage and other performance
indicators of the IP links.
UNI Interface Traffic Utilization Receive Max Top10:

Helps users quickly identify the network-wide UNI ports with
the heaviest load in the receiving direction and view the
bandwidth utilization and other performance of the UNI ports.

iMaster NCE-IP

Type
UNI Interface Traffic Utilization Receive Average Top10:

Helps users quickly identify the network-wide UNIs with the
heaviest average load in the receiving direction and view the
bandwidth usage and other performance indicators of the UNIs.
UNI Interface Traffic Utilization Send Max Top10:

Helps users quickly identify the network-wide UNI ports with
the heaviest load in the sending direction and view the
bandwidth utilization and other performance of the UNI ports.
UNI Interface Traffic Utilization Send Average Top10:

Helps users quickly identify the network-wide UNIs with the
heaviest average load in the sending direction and view the
bandwidth usage and other performance indicators of the UNIs.
NNI Interface Traffic Utilization Receive Max Top10:

Helps users quickly identify the network-wide NNI ports with
bandwidth utilization and other performance of the NNI ports.
NNI Interface Traffic Utilization Receive Average Top10:

Helps users quickly identify the network-wide NNIs with the
heaviest average load in the receiving direction and view the
bandwidth usage and other performance indicators of the NNI.
NNI Interface Traffic Utilization Send Max Top10:

Helps users quickly identify the network-wide NNI ports with
bandwidth utilization and other performance of the NNI ports.
NNI Interface Traffic Utilization Send Average Top10:

Helps users quickly identify the network-wide NNIs with the
heaviest average load in the sending direction and view the
bandwidth usage and other performance indicators of the
NNIs.
IPLink Top10 by Average Delay:

Collects statistics on IP link service quality and displays the
delay of the corresponding IP link.
IPLink Top10 by Average Packet Loss Ratio:

packet loss rate of the corresponding IP link.
QoS Top10 by Saturation:

Quickly identifies network-wide QoS services with the highest
saturation and compares the assured bandwidth and actual
traffic rate.

iMaster NCE-IP

Type
L3VPNService Top10 by Standard Rate:

Collects statistics on the L3VPN service fulfillment rate and
allows users to view performance data such as the delay, jitter,
and packet loss rate of L3VPN services.
IPLink Top10 by Average Jitter:

jitter of the corresponding IP link.
SR Policy Traffic Top10:

Collects statistics on SR Policy traffic rates to quickly locate SR
Policies with heavy loads.
IPLink Peak TX Bandwidth Utilization Top10:

heaviest load and view the peak TX bandwidth usage and other
performance indicators of the IP links.
Top 10 Layer 2 Link Peak RX Bandwidth Usage:

Helps users quickly identify the network-wide Layer 2 links with
bandwidth utilization and other performance of the Layer 2
links.
Top 10 Layer 2 Link Peak TX Bandwidth Usage:

links.
L2Link Traffic Utilization Receive Average Top10:

the heaviest average load in the receiving direction and view
the bandwidth usage and other performance indicators of the
Layer 2 links.
L2Link Traffic Utilization Send Average Top10:

the heaviest average load in the sending direction and view the
bandwidth usage and other performance indicators of the Layer
2 links.
NE Threshold-crossing Rate Top 10:

Helps users quickly identify NEs with the highest threshold-
crossing rate and learn NE load status based on the threshold-
crossing status of average CPU usage and average memory
usage.

iMaster NCE-IP

Type
Minimum IP Link Availability Top 10:

lowest availability and view link availability to learn link quality.
TWAMP PacketLossRate Top10:

Helps users quickly identify the services with the poorest
network quality and view the average two-way packet loss rate
of the services.
TWAMP Delay Top10:

network quality and view the average two-way delay of the
services.
TWAMP Jitter Top10:

network quality and view the average two-way jitter of the
services.
NE Threshold-crossing Rate Distribution:

Classifies NEs based on the threshold-crossing rate of average
NE CPU usage and average memory usage and collects
statistics on the distribution of NE threshold-crossing rates
within the recent one hour to help users quickly learn NE
threshold-crossing status.
Interface Threshold-crossing Rate Distribution:

Classifies universal interfaces based on the threshold-crossing
rate of interface transmit/receive bandwidth utilization and
collects statistics on the distribution of interface threshold-
crossing rates within the recent one hour to help users quickly
learn interface threshold-crossing status and adjust interface
traffic.
PTN built-in PTN Board temperature Top10:

chart Helps users quickly identify the network-wide boards with the
heaviest load and view the temperature and other performance
indicators of the boards.
Port Bandwidth Utilization Top10:

Helps users quickly identify the network-wide ports with the
heaviest load and view the bandwidth usage and other
performance indicators of the ports.
L2VPN-PW CIR Bandwidth Utilization Top10:

Helps users quickly identify the network-wide PWs with the
heaviest load and view the bandwidth usage and other
performance indicators of the PWs.

iMaster NCE-IP

Type
Top 10 Layer 2 Link RX Bandwidth Utilization:

links.
Top 10 Layer 2 Link TX Bandwidth Utilization:

links.
Top 10 Ring Bandwidth Utilization:

Collects bandwidth utilization based on rings to quickly identify
the ring with the heaviest load for precise adjustment or
expansion.
L2Link Traffic Utilization Receive Average Top10:

the heaviest average load in the receiving direction and view
the bandwidth usage and other performance indicators of the
Layer 2 links.
L2Link Traffic Utilization Send Average Top10:

the heaviest average load in the sending direction and view the
bandwidth usage and other performance indicators of the Layer
2 links.
TWAMP PacketLossRate Top10:

network quality and view the average two-way packet loss rate
of the services.
7.5.1.3 Performance Reports

The NCE solution provides various types of reports. By viewing reports, you can
evaluate the current network status and provide effective support for O&M,
capacity expansion, and optimization.
Functions
● Report query method
– Some reports, such as the IGP Link Traffic Report, can be queried in real
time. The supported collection periods include 5-second, 10-second, and
15-second.
– The supported query periods include 5-minute (partially), 15-minute,
hourly, daily, weekly, monthly, yearly, and user-defined time range.

iMaster NCE-IP
– Customizing the table heading and column width of a report is

supported.
– Sorting data in ascending or descending order is supported.
– Filtering data is supported.
– Querying data by group is supported.
● Report data analysis
Various data analysis methods are provided to analyze report data from
different dimensions, including comparison analysis, top N analysis, group
analysis, and indicator analysis.
● Report export methods
– Manual report export: Reports can be exported in XLS, XLSX, CSV, or PDF
format or in a user-defined format.
– Automatic report export: You can export specified report data in a
specified period using scheduled tasks. You can save the report data
locally or upload the report data using SFTP or SMTP.
7.5.1.3.1 Introduction to IP Reports

This section describes the basic traffic reports that can be viewed in IP reports.
These reports help users learn the network-wide resources and performance data
such as port, link, and ring traffic.
Panorama of IP Basic Reports

● Navigation path:
Open the Network Performance Analysis app and choose Analysis > Basic
Analysis > Performance Reports from the main menu. Choose IP from the
navigation tree.
● Reports and functions:
Resource Report and Function Key Parameter and Key
Operation
Board Board Health Report: -

Collects performance indicators
of boards such as CPU usage and
memory usage based on subnets,
helping users quickly locate
boards with the heaviest loads.
NE NE Health Report: -
of NEs such as CPU usage and
memory usage based on subnets,
helping users quickly locate NEs
with the heaviest loads.

iMaster NCE-IP

Operation
Subrack Resource Usage Key operations:

Report: Click Board Resource
Collects the rated power Report on the Subrack
distribution and utilization of Resource Usage Report
subracks, preventing subrack page to open the Board
physical resources from being Resource Report.
overloaded and providing
support for physical-layer
expansion.
NE Resource Usage Report: Key operations:

Collects the number of physical Click Card Resource Usage
ports and the slot utilization of Report on the NE Resource
NEs, preventing NE physical Usage Report page to open
resources from being overloaded the Board Resource Usage
and providing support for Report.
physical-layer expansion.
Port Universal Interface Traffic Key operations:

Report: Click Traffic Feature on the
Predicts the trend of the traffic Universal Interface Traffic
bandwidth utilization of the Report page to open the
main device interface in the Port 15-Minute Raw Data
future three months based on Display, Port Historical
the historical data, providing Data TOP N and Traffic
reference for interface traffic Percentage, Port Busy-
adjustment. hour, and Idle Feature
Display at Workday-
Weekend.
Ethernet Port Optical Report: -

of ports such as transmit or
receive optical power based on
subnets, helping users master
the optical power status of
network-wide ports.
Multi-channel Ethernet Port -

Optical Power Report:
Displays transmit or receive
optical power performance data
of multi-channel optical ports,
helping users learn the optical
power status of network-wide
ports.

iMaster NCE-IP

Operation
Interface Traffic Report: -

of IP ports, such as the traffic
rate and bandwidth utilization,
interfaces with heavy loads.
CBQos Interface CAR Traffic -

Report:
By configuring CAR, the traffic is
restricted. This report displays
the number of bytes, packets,
discarded bytes, and discarded
packets that pass through the
interface.
Flex-Channel Slice Traffic -

Report:
of Flex-Channel slices, such as
the packet passing rate, packet
discarding rate, and bandwidth
usage, to learn the traffic load of
slices.
Flow TWAMP Quality Report: -

By viewing the TWAMP quality
report, you can clearly learn the
information and quality situation
of each service and find services
to be focused on.
ICMP Quality Report: -

By viewing the ICMP quality
report, you can clearly learn the
information and quality situation
of each service and find services
to be focused on.
Link Layer 2 Link Traffic Report: -

of layer 2 links, such as the
traffic rate and bandwidth
utilization, helping users quickly
locate interfaces with heavy
loads.

iMaster NCE-IP

Operation
IP Link Traffic Report: -

of IP links, such as the traffic rate
and bandwidth utilization,
IP Link Quality Report: -

of IP link bi-directional services,
such as the packet loss rate,
delay, and jitter, helping users
learn the link quality.
IP Link DS Service Quality NOTE

Report: Users are advised to create
performance instances on the
Collects performance indicators hour of the collection period.
of IP link sink-to-source services, For example, if the collection
such as the packet loss rate, period is 15 minutes, users are
delay, and jitter, helping users advised to create performance
instances on the hour of the
collection period like 11:15 or
11:30.
IP Link SD Service Quality
Report:
of IP link source-to-sink services,
such as the packet loss rate,
delay, and jitter, helping users
10G IP Link Service Quality -

Report:
Collects the performance
indicators (such as the packet
loss rate, delay, and jitter) of
bidirectional services on 10
Gbit/s links, helping users learn
the quality of 10 Gbit/s links.
10G IP Link DS Service Quality -

Report:
sink-to-source services on 10

iMaster NCE-IP

Operation
10G IP Link SD Service Quality -

Report:
source-to-sink services on 10
IGP Link Traffic Report: -

of IGP links, such as the traffic
rate and bandwidth utilization,
IGP Link Quality Report: -

Collects the delay, jitter, and
packet loss rate of IGP links to
quickly locate interfaces with
heavy loads.
IGP Link SD Service Quality -

Report:
of IGP link source-to-sink
services, such as the packet loss
rate, delay, and jitter, helping
users learn the link quality.
IGP Link Queue Traffic Report: -

of the IGP link queue, such as
the traffic rate and bandwidth
utilization, helping users quickly
loads.
IGP Link Queue Quality Report: -

Collects the delay, jitter, and
packet loss rate of the IGP link
queue to quickly locate

iMaster NCE-IP

Operation
Service L3VPN Interface Traffic Detail -

Report:
of L3VPN services, such as the
traffic rate, helping users quickly
loads.
L3VPN Service E2E Quality -

Report:
packet loss rate, delay, and jitter,
helping users learn the E2E
quality of L3VPN services.
L3VPN Service E2E Quality -

Report(TWAMP):
helping users learn the E2E
quality of L3VPN services.
Users can click Path
Optimization to go to the
network optimization page and
perform manual optimization on
demand or automatic
optimization based on policies.
PWE3 Service Traffic Report: -

of PWE3 services, such as the
utilization, helping you quickly
loads.
PWE3 Service Quality Report: -

of PWE3 services, such as the
helping users learn the quality of
PWE3 services.

iMaster NCE-IP

Operation
QoS Template Traffic Report: -

Collects indicators such as the
number of discarded packets and
the packet rate in the basic
HQoS queue (based on the QoS
profile) and the packet rate in
the total traffic queue (based on
the QoS profile) to analyze the
network congestion condition.
Port Queue Traffic Report: -

the packet rate in the basic XQoS
queue (based on the default
interface queue), as well as the
total traffic packet rate to
analyze the network congestion
condition.
VRF Traffic Report: -

Collects VRF traffic of L3VPN
services, including the byte
receive/transmit rate, packet
receive/transmit rate, and
numbers of received/transmitted
packets.
Location Service Type Detail -

Report:
Collects the traffic percentages
of services (such as 3G and LTE
services) by region, helping users
quickly learn the service traffic
composition of each region.
City Service Type Detail Report: -

Collects the traffic percentages
of services (such as 3G and LTE
services) by city, helping users
quickly learn the overall service
traffic composition of the city.
TE Tunnel Quality Report: -

Collects performance data of TE
tunnel services, such as the
to learn the tunnel service
quality.

iMaster NCE-IP

Operation
TE Tunnel Traffic Report: -

Collects traffic data of TE tunnel
services, such as the maximum,
minimum, and average traffic
rate, as well as the maximum,
minimum, and average packet
rate.
TE Tunnel Convergence Traffic -

Report:
Collects the average traffic rate
of the TE tunnel from the source
to the destination.
EVPN Interface Traffic Detail -

Report:
of EVPN services, such as the
traffic rate, helping users quickly
loads.
VPLS Service Report NQA: -

of VPLS E2E services, such as the
saturation, VC usage rate, packet
loss rate, and delay, helping
users learn the quality of VPLS
services.
SR Policy Traffic Report: -

Displays the traffic of SR Policy
services, such as maximum
traffic, minimum traffic,
maximum package rate, and
minimum package rate.
Port Default Queue Traffic -

Report:
the packet rate in the port
default queue, as well as the
total traffic packet rate to
analyze the network congestion
condition.

iMaster NCE-IP

Operation
Ring Ring Convergence Ratio For details about the

Report: parameters and operations
Collects the descending in the Ring Convergence
convergence ratio of the ring and Ratio Report, see
displays ring traffic aggregation, Aggregation Ring
helping users quickly locate a Convergence Ratio Report
traffic bottleneck of the ring and and Access Ring
take corrective measures Convergence Ratio Report.
(capacity expansion or network
optimization).
Network Second-Level Peak The data in this report is

Report: calculated based on the
Collects second-level peak load data in the Universal
rates of inter-ring ports, helping Interface Traffic Report.
users learn the load rate change When creating the
trends on rings and providing Universal Interface Traffic
guidance for ring expansion on Report, users are advised to
networks. select the Outbound Peak
indicator in the Traffic Peak
Indicators indicator group
and the Outbound Rate
indicator in the Basic
Traffic Statistics Indicators
indicator group.
NOTE
The Peak TX Rate(b/s) is
calculated based on the
Outbound Peak indicator in
the Traffic Peak Indicators
indicator group of the
Universal Interface Traffic
Report. If the device does not
support second-level peak
collection, the system uses the
Outbound Rate indicator in
the Basic Traffic Statistics
Indicators indicator group of
the Universal Interface
Traffic Report for calculation.
Key operations:
In the report in the lower
part of the page, you can
click HistoryPerf in the
Operation column to view
the historical performance
of a single ring.

iMaster NCE-IP

Operation
Ring Report: Key operations:

Collects performance indicators ● In the Ring Traffic
of rings such as inter-ring port Report area in the lower
rates and bandwidth utilization, part of the page, users
helping users quickly locate can click L2Link Traffic
heavily loaded ports on access Report in the Operation
rings. column to view the
traffic status of layer 2
links related to a single
ring.
● In the Ring Traffic
Report area in the lower
part of the page, users
can click IPLink Traffic
Report in the Operation
column to view the
traffic status of IP links
related to a single ring.
Operation column to
view the historical
performance of a single
ring.

iMaster NCE-IP

Operation
Ring Load Deterioration ● Key parameters:

Statistics Report: – QueryPeriod: Only
Collects the top N second-level the Daily option is
peak load rates of inter-ring provided.
ports, helping users identify rings – TOPn: After it is set,
with the highest load rate the report only
networkwide. displays the top n
rings whose load rate
exceeds the alarm
threshold within the
QueryPeriod.
– Alarm severity: After
it is selected, the
report only collects
the alarms on the
rings at the selected
alarm severity.
● Key operations:
– After a bar in the bar
chart in the upper
part is clicked, the
report in the lower
part displays the load
rates and bandwidth
values of the ring
represented by the bar
at all data collection
time points within a
day.
– In the report in the
lower part of the
page, you can click
HistoryPerf in the
Operation column to
view the historical
performance of a
single ring.

iMaster NCE-IP

Operation
Ring Convergence Ratio ● Key parameters:

Distribution Statistics Report: – Step: After it is set,
Collects the convergence ratio the sectors in the
distribution status of access and convergence ratio
aggregation rings. statistics chart are
divided by Step.
– Minimum: indicates
the minimum
convergence ratio to
be collected. After it is
set, the chart only
collects the data that
is greater than the
convergence ratio.
– Maximum: indicates
the maximum
convergence ratio to
be collected. After it is
set, the chart only
collects the data that
is less than the
convergence ratio.
● Key operations:
In the report in the lower
can click Ring
Convergence Ratio
Distribution Statistics
column to analyze the
convergence ratio of a
single ring on a daily or
weekly basis.
Core Ring Report: -

of core rings such as port rates
and bandwidth utilization,
heavily loaded ports on core
rings.

iMaster NCE-IP

Operation
Aggregation Ring Convergence Key operations:

Ratio Report: In the report in the lower
Collects the descending part of the page, you can
convergence ratio of the click HistoryPerf in the
aggregation ring, and displays Operation column to view
ring traffic aggregation, helping the historical performance
users quickly locate a traffic of a single ring.
bottleneck of the ring and take
corrective measures (capacity
expansion or network
optimization).
Aggregation Ring Report: -

indicators (such as the traffic
rate and bandwidth usage) of
ports on aggregation rings,
helping users quickly identify the
ports with the heaviest load on
aggregation rings.
Aggregation Ring Service Type Key operations:

Traffic Analysis Report: In the report in the lower
Collects the traffic percentages part of the page, you can
of services (such as 3G and LTE click HistoryPerf in the
services) by aggregation ring, Operation column to view
helping users quickly learn the the historical performance
service traffic composition of the of a single ring.
aggregation ring.
Access Ring Convergence Ratio -

Report:
Collects the descending
convergence ratio of the access
ring, and displays ring traffic
aggregation, helping users
quickly locate a traffic bottleneck
of the ring and take corrective
measures (capacity expansion or
network optimization).

iMaster NCE-IP

Operation
Access Ring Report: Key operations:

Collects performance indicators ● In the Ring Traffic
of access rings such as port rates Report area in the lower
and bandwidth utilization, part of the page, users
helping users quickly locate can click L2Link Traffic
heavily loaded ports on access Report in the Operation
rings. column to view the
traffic status of layer 2
links related to a single
access ring.
can click IPLink Traffic
column to view the
traffic status of IP links
related to a single access
ring.
Operation column to
view the historical
performance of a single
access ring.
Access Ring Service Type Key operations:

Traffic Analysis Report: In the report in the lower
Collects the traffic percentages part of the page, you can
of services (such as 3G and LTE click HistoryPerf in the
services) by access ring, helping Operation column to view
users quickly learn the service the historical performance
traffic composition of the access of a single ring.
ring.

iMaster NCE-IP

Operation
Y1731 PWE3 Service Y1731 PriAll -

Report
PWE3 Service Y1731 Pri0
Report
Report
Report
Report
Report
Report
Report
Report
The PWE3 Y.1731 quality report
displays the PWE3 Y.1731
detection results, helping users
quickly view the quality of PWE3
services.
NOTE
The priority refers to the priority of
detection packets.
EVPN Service Y1731 Report -

The EVPN Y.1731 quality report
displays the EVPN Y.1731
detection results, helping users
quickly view the quality of EVPN
services.
7.5.1.3.2 Introduction to PTN Reports

This section describes the basic traffic reports that can be viewed in PTN reports.
These reports help you learn the network-wide resources and performance data
such as port, link, and ring traffic.
Panorama of PTN Basic Reports

● Navigation path:
Open the Network Performance Analysis app and choose Analysis > Basic
Analysis > Performance Reports from the main menu. Choose PTN from the
navigation tree.

iMaster NCE-IP
● Reports and functions:

NOTE
The report panorama includes the mainstream PTN device reports and PTN 6900 reports.
● Except Ethernet Port Optical Report and Eth-Trunk Traffic Statistics Report in the
report panorama, all other reports support the mainstream PTN devices.
● In the report panorama, Channelization Subinterface Traffic Report and FLexETH
Interface Traffic Report support PTN 7900s only.
● In the "Supporting PTN 6900 or Not" column of the report panorama, "Not support"
indicates that the report does not support PTN 6900s, "Support" indicates that the
report supports PTN 6900s, and "Support PTN 6900s only" indicates that the report
supports PTN 6900s only.
Resource Report and Function Supporting PTN 6900

or Not
Board Board Performance Report: Support

Collects NE temperature based on
subnets to learn NE health status.
Port Port Bandwidth Utilization Support

Report:
indicators (such as the bandwidth
and bandwidth usage) of ports
based on subnets, helping users
quickly identify traffic bottlenecks
and optimize the network as
required. This report can be drilled
down to PW Trail Traffic Report.
Ethernet Port Optical Power Support PTN 6900s

Report: only
Collects performance indicators of
ports such as transmit or receive
optical power based on subnets,
helping users master the optical
power status of network-wide
ports.
NNI Port CIR Percentage Report: Support

Collects the sum of assured
bandwidth on ports. For ports
whose assured bandwidth usage is
high and remaining bandwidth is
insufficient, users need to adjust
the network or expand capacity in
a timely manner.

iMaster NCE-IP

or Not
NNI Port Bandwidth Utilization Support

Report:
Collects bandwidth utilization
performances of NNI ports,
including CIR, peak traffic and CIR
bandwidth utilization. This report
can be drilled up to PW Trail
Traffic Report and horizontally to
Link Bandwidth Utilization
Report.
NNI Port Bandwidth Utilization Support

Segmented Statistics Report:
Collects the distribution of NNI
port bandwidth usage at different
levels, helping users evaluate the
overall network load.
UNI Port Bandwidth Utilization Support

Report:
Collects bandwidth utilization
performances of UNI ports,
including CIR, PIR, peak traffic and
CIR bandwidth utilization. This
report can be drilled down to PW
Trail Traffic Report.
UNI Service Type Assured Support

Bandwidth Proportion Report:
Collects the percentage of sum of
assured bandwidth of PW trails of
a certain service type to sum of
assured bandwidth of PW trails of
all service types based on different
UNI service types (such as 3G, LTE
and WLAN).
UNI Service Type Proportion Support

Report:
Provides a traffic pie chart to
display the proportion of network-
wide UNI traffic in different types
of pipes more clearly.

iMaster NCE-IP

or Not
Eth-Trunk Traffic Statistics Support PTN 6900s

Report: only
indicators (such as the traffic rate
and bandwidth usage) of Eth-
Trunk interfaces based on subnets,
Eth-Trunk interfaces with the
heaviest load.
Port Bit Error Report: Support

Collects statistics on the bit error
performance of Ethernet ports
based on subnets to learn the
transmission quality of services
over the Ethernet ports.
Ethernet Port Error Packet Support

Report:
Collects statistics on the bit error
performance of Ethernet ports
based on subnets to learn the
transmission quality of services
over the Ethernet ports.
PTN6900 Interface Queue Support

Report:
Collects statistics on packet loss
performance of port queues of
PTN 6900s based on subnets,
including the rate of packets
discarded by queues and the rate
of packets passing through queues.
This helps users learn packet loss
on ports and provides guidance for
network O&M.
PTN Interface Queue Report: Not support

Collects statistics on packet loss
performance of port queues of
PTN NEs (excluding PTN 6900s)
based on subnets, including the
rate of packets discarded by
queues and the rate of packets
passing through queues. This helps
users learn packet loss on ports
and provides guidance for network
O&M.

iMaster NCE-IP

or Not
Laser Laser Optical Power Report: Not support

Collects the optical power of
network-wide lasers based on
subnets to learn the laser status
for network O&M.
Laser Bias Current Report: Not support

Collects the bias current of
network-wide lasers based on
subnets to learn the laser status
for network O&M.
Link Link Bandwidth Utilization Support

Segmented Statistics Report:
Collects the distribution of link
bandwidth utilization at each level
for users to evaluate the overall
network load.
Link Bandwidth Utilization Support

Report:
Collects statistics on link
bandwidths, bandwidth utilization,
and other performance on a
subnet basis, helping users quickly
learn about the link traffic
bottlenecks for further network
optimization. This report can be
drilled up to PW Trail Traffic
Report and horizontally to Port
Bandwidth Utilization Report.
Service Group Customer Traffic Analysis Support

Report:
Analyzes and ranks traffic of group
customers and displays the top N
group customers that use the
highest traffic. This function
ensures QoS of group customer
networks and facilitates precise
marketing and proactive expansion
for group customers with high
traffic loads. This report can be
drilled down to PW Trail Traffic
Report.

iMaster NCE-IP

or Not
Area Traffic Analysis Report: Not support

Helps learn traffic usage in
different areas and determine
whether to perform regional
network expansion based on the
analysis results. This report can be
Report.
Area Total Traffic Analysis Support

Report:
Collects statistics on traffic in the
current month and last month
based on areas, helping users learn
monthly traffic changes.
Service Type Assured Bandwidth Not support

Proportion Report:
Collects statistics about the
proportion of total assured
bandwidths of a certain type of
PW trail to those of all types of
PW trails based on different
service types (such as 3G, LTE and
WLAN).
Service Traffic Trend Report: Not support

Shows the network-wide service
traffic trend, traffic of all service
types, and traffic proportions.
Service Traffic Analysis Report: Not support

Helps users learn which type of
service (for example, 3G, LTE and
WLAN) uses the highest traffic and
perform precise network planning
and deployment. This report can
be drilled down to PW Trail
Traffic Report.
Service Type Traffic Proportion Not support

Report:
Provides a traffic pie chart to
display the proportion of network-
wide traffic in different types of
pipes more clearly.

iMaster NCE-IP

or Not
Tunnel Traffic Report: Support

Facilitates users to view the
difference between the current
traffic rate and the PIR to provide
guidance for timely network
adjustment or expansion. This
report can be drilled down to Link
Tunnel Quality Report: Support

Collects performance data of
tunnel, such as the packet loss
rate, delay, and jitter, to learn the
tunnel quality.
PW Trail Traffic Report: Not support

adjustment or expansion. This
report can be drilled up to UNI
Port Bandwidth Utilization
Report and down to Ring Traffic
Analysis Report and Link
Channelization Subinterface Not support

Traffic Report:
Deploy channelization
subinterfaces on a physical port to
carry different types of services
(such as home broadband, group
customer private line, and mobile
backhual services), configure
bandwidths based on the
channelization subinterfaces, and
use the HQoS scheduling of the
TM chip to implement bandwidth
isolation among different
channelization subinterfaces on
the same physical port. This report
helps users query the performance
statistics of the channelization
subinterface, including the traffic
rate and bandwidth utilization.

iMaster NCE-IP

or Not
FLexETH Interface Traffic Report: Not support

Deploy FLexETH interfaces on
physical ports and bind different
timeslots to the interfaces to
divide into different bandwidths.
Different services (such as home
broadband, group customer
private line, and mobile backhual
services) are homed to different
FLexETH interfaces. Each FLexETH
interface is scheduled
independently to implement
complete isolation among
different services. Each FLexETH
interface is scheduled
independently to implement
complete isolation among
different services.
VPLS Service Traffic Report: Not support

adjustment or expansion.
PWE3 Service Traffic Report: Not support

Is used to view the traffic status of
PWE3 services to instruct timely
network adjustment or expansion.
This report can be drilled down to
PW Trail Traffic Report.
PWE3 Service Quality Report: Support

Helps learn quality of PWE3
services on a network, including
the delay and packet loss rate.
Queue Loss Report: Support

the packet rate in the basic HQoS
queue (based on the QoS profile)
and the packet rate in the total
traffic queue (based on the QoS
profile) to analyze the network
congestion condition.

iMaster NCE-IP

or Not
Site PWE3 Traffic Report: Support

Collects service traffic information,
including traffic rate and
bandwidth utilization, of a base
station (for example, LTE base
station with dual IP addresses),
helping adjustment networks or
expand capacity in a timely
manner. This report can be drilled
down to PW Trail Traffic Report.
L3VPN Interface Traffic Detail Support

Report:
indicators (such as the traffic rate)
of L3VPN services, helping users
quickly identify the ports with the
heaviest load.
PW Path Quality Report: Not support

Collects the quality data (such as NOTE
the delay, jitter, and packet loss ● PTN 3900, PTN
rate) of PW services. 3900-8 and PTN 1900
are supported only
when the matched
TN81AIE interface
board is available.
Other products of
this series have no
requirements on the
interface board.
● If the source or sink
of the group
customer service is
PTN 3900, users need
to configure the PTN
3900 as AIE
centralized (OAM
dual-stack, cross-
connect dual-stack or
AIE dual-stack). Note
that intermittent
disconnection may
occur during the
transit from
distributed to
centralized.

iMaster NCE-IP

or Not
L2L3 Traffic Report: Support

Helps users better observe the
total traffic of Layer 2 and Layer 3
services and the traffic change of
each monitoring point.
Tunnel Trail Statistics Report: Support

Helps users learn the gap between
current tunnel trail traffic and PIR,
which provides support for timely
network adjustment or expansion,
and collects performance
indicators such as the packet loss
rate, delay, and jitter of services for
users to learn about the tunnel
trail quality.
PW Trail Statistics Report: Support

Helps users learn the gap between
current PW trail traffic and PIR,
which provides support for timely
network adjustment or expansion,
and collects performance
indicators such as the packet loss
rate, delay, and jitter of PW
services for users to learn about
the PW trail quality.
PTN Leasedline: Support

Displays quality of all VIPs' private
lines and allow users to view
performance indicator data of all
VIP private lines, including Leased
Line Name, VIP Customer Name,
Source NE Name, Sink NE Name,
Remote Avg PLR, Local Avg PLR,
Avg Bidirectional Jitter and so on.
FlexE-Group Performance Report: Not support

Helps you monitor the overall
traffic of a FlexE group and
identify the interfaces with the
highest usage, helping you
determine whether a capacity
expansion is required.

iMaster NCE-IP

or Not
FgClient Interface Traffic Report: Not support

An FgClient interface is a sub-
interface of a FLexETH interface. It
can be divided into 10 Mbit/s
timeslots. A FLexETH interface can
be divided into multiple FgClient
interfaces, which greatly improves
configuration flexibility. FgClient
interfaces are deployed on physical
ports and bound with different
timeslots to allocate different
bandwidths. Different services
(such as smart grid, smart port,
smart healthcare, and smart
railway) are homed to different
FgClient interfaces. Each FgClient
interface is independently
scheduled to implement complete
isolation between different
services. This report helps you
query the performance statistics of
the FgClient interface, including
the traffic rate and bandwidth
utilization.
Ring Ring Bandwidth Utilization Support

Trend Report:
Provides the development trend of
site or ring traffic and supports
warnings (the peak rate will be
exceeded XX days later) to provide
support for network planning.
PTN Ring Traffic Statistics Support

Report:
Collects and analyzes statistics on
ring traffic, helping users quickly
identify traffic bottlenecks and
conduct timely expansion or
optimization.

iMaster NCE-IP

or Not
Ring Traffic Balance Report: Support

Shows whether traffic
configurations are appropriate and
egress traffic is balanced on rings.
This report can be drilled up to
High Level Ring Traffic Balance
Report, horizontally to PTN Ring
Traffic Statistics Report, The
Same Level Ring Traffic Balance
Report, and down to PW Trail
Traffic Report and Link
Ring Traffic Monthly Growth Support

Report:
Shows ring traffic growth through
the absolute indicator of monthly
growth volume and the relative
indicator of monthly growth rate,
which facilitates network
adjustment or expansion.
Service Type Bandwidth Not support

Utilization Report Based On
Ring:
Provides traffic, traffic rate,
bandwidth utilization and traffic
proportion of each type of service
(3G, LTE and WLAN) on the ring to
assess the service distribution. This
report can be drilled down to PW
Network Traffic Change Trend Support

Report:
Includes Traffic Change Trend
Report and Growth Rate Change
Trend Report, helping users can
view and learn the traffic in recent
a month and growth rate
respectively in a bar chart or a line
chart.

iMaster NCE-IP

or Not
Core Ring Traffic Analysis Support

Report:
Collects performance data such as
utilization of ports on core rings,
helping users quickly locate heavily
loaded ports on core rings. This
report can be drilled up to High
Level Ring Traffic Analysis
Report, horizontally to Link
Bandwidth Utilization Report,
and down to Low Level Ring
Traffic Analysis Report and PW
Core Ring LTE Traffic Analysis Support

Report:
Collects traffic information of core
rings that carry LTE services,
helping users quickly find hot rings
and prevent packet loss. This
Level Ring LTE Traffic Analysis
and down to Low Level Ring LTE
Traffic Analysis Report.
Aggregation Ring Traffic Support

Analysis Report:
utilization of ports on aggregation
rings, helping users quickly locate
heavily loaded ports on
aggregation rings. This report can
be drilled up to High Level Ring
Traffic Analysis Report,
horizontally to Link Bandwidth
Utilization Report, and down to
Low Level Ring Traffic Analysis
Report and PW Trail Traffic
Report.

iMaster NCE-IP

or Not
Aggregation Ring LTE Traffic Support

Analysis Report:
Collects traffic information of
aggregation rings that carry LTE
services, helping users quickly find
hot rings and prevent packet loss.
This report can be drilled up to
High Level Ring LTE Traffic
Analysis Report, horizontally to
Report, and down to Low Level
Ring LTE Traffic Analysis Report.
Access Ring Traffic Analysis Support

Report:
utilization of ports on access rings,
helping users quickly locate heavily
loaded ports on access rings. This
Level Ring Traffic Analysis
and down to Low Level Ring
Traffic Analysis Report and PW
Access Ring LTE Traffic Analysis Support

Report:
Collects the traffic information of
access rings that carry LTE services,
helping users quickly identify hot
rings and prevent packet loss. This
Level Ring LTE Traffic Analysis
and down to Low Level Ring LTE

iMaster NCE-IP

or Not
Access Chain Traffic Analysis Support

Report:
access links, helping users quickly
find hot links and prevent packet
loss. This report can be drilled up
to Upper-Layer Ring Traffic
Analysis Report, horizontally to
Report, and down to Lower-Layer
Ring Traffic Analysis Report and
PW Trail Traffic Report.
Access Chain LTE Traffic Analysis Support

Report:
access links that carry LTE services,
helping users quickly find hot links
and prevent packet loss. This
Level Link LTE Traffic Analysis
and down to Low Level Link LTE
PTN Port Bandwidth Utilization Support

Report Based On Ring:
Collects bandwidth usage and
other performance data of rings,
rings with the heaviest load and
conduct adjustment or expansion
as required. This report can be
Report.
Peak Bandwidth Utilization of Support

Core-Ring Port:
Classifies ports on a core ring
based on the peak bandwidth
utilization and helps learn which
ports on the core ring have the
abnormally high peak bandwidth
utilization.

iMaster NCE-IP

or Not

Aggregation-Ring Port:
Classifies ports on an aggregation
ring based on the peak bandwidth
utilization and helps learn which
ports on the aggregation ring have
the abnormally high peak
bandwidth utilization.

Access-Ring Port:
Classifies ports on an access ring
utilization and helps users learn
which ports on the access-ring
have the abnormally high peak

Access-Chain Port:
Classifies ports on an access chain
utilization and helps users learn
which ports on the access-chain
have the abnormally high peak
Busy Average Bandwidth Support

Utilization of Core-Ring Port:
Classifies ports on a core ring
based on the busy average
bandwidth usage and helps users
learn which ports on the core ring
have abnormally high bandwidth
usage.

Utilization of Aggregation-Ring
Port:
Classifies ports on an aggregation
ring based on the busy average
bandwidth usage and helps users
learn which ports on the
aggregation ring have abnormally
high bandwidth usage.

iMaster NCE-IP

or Not

Utilization of Access-Ring Port:
Classifies ports on an access ring
bandwidth utilization and helps
users learn which ports on the
access-ring have the abnormally
high bandwidth utilization.

Utilization of Access-Chain Port:
Classifies ports on an access chain
bandwidth utilization and helps
users learn which ports on the
access-chain have the abnormally
high bandwidth utilization.
7.5.1.4 Report Management

NCE provides different patterns of reports to help users create charts with certain
data sources.
From the reports, users can conveniently, quickly, and intuitively gain accurate
resource statistics on the entire network for network monitoring, service planning,
and expansion planning.
● Managing reports: Users can flexibly customize reports and data sources, set
the sequence of report fields, and select different patterns of charts for
presentation.
● Creating basic reports: Users can create custom reports and view the created
reports by choosing Settings > Application > Report Management > Report
Management.
● Setting the presented reports: Users can choose the basic reports to be
presented on the client.
● Creating composite reports: NCE allows users to combine associated user-
defined basic reports of various styles into one, helping users quickly,
intuitively, and accurately learn about the running status of concerned
resources.
7.5.1.5 Performance Regional Map

NCE provides the regional map function, which visualizes traffic and quality
condition in different regions and enables users to quickly identify the regions that
require special attention.

iMaster NCE-IP
Functions
● The PTN and IP traffic monitoring solutions provide regional traffic maps that
clearly display the traffic condition and ranking of each region.
● The TWAMP and ICMP quality monitoring solutions provide regional quality
maps that clearly display the quality condition and ranking of each area. The
displayed indicators include packet loss rate, delay, and jitter.
Specifications
Regional traffic map
● Colored alarms on the map
Regions on the map are displayed in different colors depending on whether
the regional traffic exceeds the preset threshold.
– Green indicates that the regional traffic is less than the Minor Alarm
threshold.
– Yellow indicates that the regional traffic is less than the Critical Alarm
threshold but greater than or equal to the Major Alarm threshold.
– Red indicates that the regional traffic is greater than or equal to the
Critical Alarm threshold.
– Gray indicates that the region is not monitored.
● Map drilldown
The regional PTN traffic monitoring map supports two-level drilldown and
traffic data display.
● Region rankings
Regions are ranked by total traffic or bandwidth usage in descending order,
and the rankings are refreshed every hour.
● Visibility into traffic
– The regional PTN traffic monitoring map clearly displays the total traffic,
RX traffic, TX traffic, and service traffic of different regions, helping users
identify key regions in a timely manner.
– The regional IP traffic monitoring map clearly displays the RX bandwidth
usage, TX bandwidth usage, peak RX bandwidth usage, and peak TX
bandwidth usage of different regions, helping users identify key regions
in a timely manner.
Regional quality map
● Colored alarms on the map
Regions on the map are displayed in different colors depending on whether
an indicator of the regional service exceeds the preset threshold.
– Green indicates that the regional service quality is Good.
– Yellow indicates that the regional service quality is Medium.
– Red indicates that the regional service quality is Bad.
– Gray indicates that the region is not monitored.
● Region rankings
Regions are ranked by service quality in the order from bad to good.

iMaster NCE-IP
● Indicator visualization
The regional map clearly displays quality indicators, which helps users quickly
identify the regions with poor quality.
7.5.1.6 Performance Topology

Performance topology is a view that displays managed NEs and their connections.
This view helps users understand the structure and running status of the entire
network in real time.
Functions
● The physical topology consists of a navigation pane on the left and a view on
the right. The navigation tree shows the layered network structure, and the
view displays managed objects in different places (coordinates).
● The physical topology integrates NE performance indicators and alarms,
helping users learn the NE condition and running status of the entire network.
● The physical topology integrates link performance indicators and alarms,
helping users learn the structure and running status of the entire network.
● Some NCE resources, such as PW trails, Layer 2 links, rings, and Ethernet
ports, support warning settings.
7.5.1.7 Service Bandwidth Analysis

NCE can analyze the bandwidth usage of PTN PWE3 services. By analyzing the
average busy bandwidth usage of CIR and PIR, peak bandwidth usage of CIR and
PIR, and threshold policies, NCE provides bandwidth adjustment suggestions and
policies for PWE3 services.
Functions
● Policy configuration
Users can select different service types to set the upper and lower thresholds
for the average busy and peak bandwidth usage of CIR and PIR as well as the
threshold-crossing days. These settings help NCE learn the threshold-crossing
condition and determine whether adjustment is needed.
● Service adjustment analysis
Users can modify, delete, and refresh periodic report tasks.
– If the average busy or peak bandwidth usage of CIR is above its upper
threshold for the specified number of days, increase the CIR.
– If the average busy or peak bandwidth usage of CIR is below its lower
threshold for the specified number of days, decrease the CIR.
– If the average busy or peak bandwidth usage of PIR is above its upper
threshold for the specified number of days, increase the PIR.
– If the average busy or peak bandwidth usage of PIR is below its lower
threshold for the specified number of days, decrease the PIR.

iMaster NCE-IP
7.5.1.8 Scheduled Report Task Management

With scheduled report task management, reports can be automatically exported
and uploaded within a specified period.
Functions
● Creating tasks
You can create tasks to automatically export hourly, daily, weekly, and
monthly reports as XLS, XLSX, CSV, or PDF files within a specified period. They
can save the exported reports to the local computer or upload them to a
server through SFTP or SMTP.
● Managing the task list
Users can modify, delete, and refresh periodic report tasks.
Specifications
● A maximum of 24 tasks can be created at the same time and a maximum of
48 reports can be created.
● Hourly, daily, weekly, and monthly reports are exported at every hour, 05:00
every day, 09:00 every Monday, and 13:00 on the first day of every month,
respectively.
● All data can be exported if the report format is XLS, XLSX, or CSV. However, if
the report format is PDF, only the first 100 records can be exported.
● If Sending mode is set to Save to local, report files are saved in the specified
directory on the NCE server by default. Files of each task are periodically
deleted to retain only the files generated within three days. If the report data
is too large and the storage space usage of report files reaches 50% of the
remaining storage space of the /opt directory (Remaining storage space =
Total storage space – Space occupied by other files), the report files that are
stored earlier are automatically deleted. If Sending mode is set to SMTP,
reports are sent through emails. Multiple email addresses are supported.
7.5.1.9 Object Management
7.5.1.9.1 IP RAN/PTN Object Management

With the object management function of NCE, users can select multiple objects of
the same type to collect and analyze their performance indicators within a period.
Benefits
● NCE provides the object management function, which allows users to select
performance indicators of multiple resource objects of the same type within a
specified period for statistics collection and analysis.
● Maintenance Suite is provided for users to manage multiple objects and view
performance data or even the performance aggregation results of objects. The
aggregation results can be exported as a report. Maintenance Suite
aggregates performance data by area, service type, or device. For example, it
can aggregate performance data for multiple ports of the same device or in
the same area. In addition, Maintenance Suite allows users to flexibly set
object layers for easily collecting and querying performance data by layer.

iMaster NCE-IP
Functions
● Users can select multiple objects of the same resource type for group creation
and specify the period, time segment, performance indicators, and
aggregation type (average, maximum, minimum, and sum) to obtain
aggregated values.
● Users can view and export the results.
Specifications
● Groups can be queried, created, or deleted, and objects in the same group
must be of the same type.
● Users can modify group names but cannot modify resource types. Users can
add or delete objects as required. During the modification, all objects in the
group are listed.
● The performance data of groups can be browsed and exported to reports, but
cannot be saved to the database.
Table 7-30 Resource types for query

Solution Resource Type
PTN solution PTN_NE
PTN_CP
L2Link
PTN_Ethernetport
PWTrail
IP solution NE
CP
IpOpticalPort
IPLink
IGPLink
IPInterface
L2Link
7.5.1.10 TWAMP Quality Monitoring

NCE supports TWAMP tests, facilitating real-time mobile bearer network quality
monitoring and fault demarcation and locating. A TWAMP test is preferentially
used for quality monitoring. If this test is not supported, use an ICMP test.

iMaster NCE-IP
Typical IP RAN Networking

TWAMP tests can be used to monitor network quality in real time and assist in
fault demarcation and locating.
Real-time network quality monitoring and assistance in fault demarcation
and locating: A TWAMP test can be conducted between a device with TWAMP
test cases deployed and a base station to collect network performance data.
Carriers can deploy NCE to detect service quality change trends in a visualized
manner to facilitate fault demarcation and locating.
Figure 7-21 shows the typical networking schemes.
Figure 7-21 Real-time monitoring and fault demarcation and locating

iMaster NCE-IP
Table 7-31 Probe deployment suggestions and service benefits

Applicati Probe Deployment Suggestion and Service Benefit
on
Scenario
Real- ● ATN + CX solution: A CX device with the SNC board installed can
time serve as the TWAMP test source. An ATN device connected to an
monitori L3 access device as the test destination. Then a TWAMP test is
ng and proactively initiated to the ATN device to evaluate network
fault quality between the base stations and their controllers in real
demarcat time.
ion and This solution brings the following benefits to carriers:
locating
● Provides service assurance in the case of important events or
festivals: With increase in social activities in recent years, carriers
concern more about service continuity in the case of important
events or festivals. Carriers require key targets to be monitored in
real time and faults to be detected and rectified quickly.
● Monitors interfaces of the base station peer devices in real
time: Deploy the TWAMP test on the interface connecting a core-
layer device and a base station peer device to monitor the
network in real time. Once a service quality problem occurs on
the transmission side, it can be detected in real time and
demarcated preliminarily.
● Monitors interfaces on L2-to-L3 devices in real time: Deploy
the TWAMP test on the interface connecting a core-layer device
and an L2-to-L3 device to monitor the network in real time. Once
a service quality problem occurs on an L3 device, it can be
detected in real time and demarcated preliminarily.
Typical PTN Networking

TWAMP tests can be used to monitor network quality in real time and assist in
fault demarcation and locating.
Real-time network quality monitoring and assistance in fault demarcation
and locating: A TWAMP test can be conducted between a device with TWAMP
test cases deployed and a base station to collect network performance data.
Carriers can deploy NCE to detect service quality change trends in a visualized
manner to facilitate fault demarcation and locating.

iMaster NCE-IP

iMaster NCE-IP

on
Scenario
Real- ● PTN TWAMP monitoring solution: Enable the TWAMP

time monitoring function on a PTN 7900 on the RNC/EPC side. Then
monitori initiate a TWAMP test from the PTN 7900 to an L2/L3, L2, or L3
ng and PTN device to evaluate network quality between the RNC/EPC
fault side and base stations in real time as well as quality between
demarcat different network layers.
ion and ● PTN embedded heavy traffic test: Configure a PTN 7900 to
locating initiate a TWAMP test for evaluating network quality between
base stations and their controllers in real time. A heavy traffic
test is recommended when services are not provisioned on a
deployed network. This test can be used to evaluate the quality
of services, such as packet loss, when the network is heavily
loaded.
This solution brings the following benefits to carriers:
● Provides service assurance in the case of important events or
festivals: With increase in social activities in recent years, carriers
concern more about service continuity in the case of important
events or festivals. Carriers require key targets to be monitored in
real time and faults to be detected and rectified quickly.
time: Deploy the TWAMP test on the interface connecting a core-
layer device and a base station peer device to monitor the
the TWAMP test on the interface connecting a core-layer device
and an L2-to-L3 device to monitor the network in real time. Once
a service quality problem occurs on an L3 device, it can be
detected in real time and demarcated preliminarily.
TWAMP Test Description

Basic Concepts
TWAMP: Two-Way Active Measurement Protocol, used to test the network quality
indicators such as jitter, packet loss rate, and delay from the source to the
destination.
Principles
The TWAMP test process on NCE is as follows:
● An SNC-capable Huawei NE or PTN NE can function as the TWAMP test client

and controller to start a test and collect statistics.

iMaster NCE-IP
● A TWAMP-capable device can function as the TWAMP server, which responds

to test packets only.
Table 7-33 Indicator description
Indicator Description
Two way Rate of the number of discarded packets to the total number of
Packet packets transmitted within a period.
Loss Ratio
Two way Time used by a packet to be transmitted from the source end to
Delay the sink end.
Two way Difference between two consecutive delays for packets to reach
Jitter the same sink end.
One-way Rate of lost packets to transmitted packets on a link from the

Packet source end to the sink end or from the sink end to the source end
Loss Ratio within a period.
One-way Time required from sending a packet by the source end to

Delay receiving the packet by the sink end or from sending an
acknowledgment packet by the sink end to receiving the
acknowledgment packet by the source end.
One-way Delay change from the source end to the sink end or from the sink
Jitter end to the source end.
MOS A test to obtain users' view of the network quality. The MOS
provides a numerical indication of the perceived quality from the
users' perspective of received media and is expressed as a single
number in the range of 0 to 5, where 0 indicates the lowest
perceived quality, and 5 indicates the highest perceived quality.
The voice quality is determined based on E-Model calculation.
R-Value A 100-score system to measure the voice quality based on E-Model

calculation, considering the network impairment factors. The R-
Value is a number ranging from 0 to 100, where 0 indicates the
lowest voice quality, and 100 indicates the highest voice quality.
Error Number of error packets detected during data transmission.

Packets
Table 7-34 Requirements on TWAMP test source and sink ends
Device Type Function as TWAMP Source Function as

TWAMP Sink
Device with an SNC Y N

board installed
Destination device IP N Y
(TWAMP-capable device)

iMaster NCE-IP
Device Type Function as TWAMP Source Function as

TWAMP Sink
TWAMP-capable base N Y
station
PTN device (PTN device Y Y

which TWAMP test cases
deployed)
IP device (that is, the Y Y

NE40E, CX600 or ATN
device in the V8 version)
Table 7-35 Applicable versions between NCE and PTN devices

Device Type Device Reflector Supported or Not Sender
Type Support
ed or
Not
V100R010C10 PTN960 Supported by all serial boards No

160G

iMaster NCE-IP

Type Support
ed or
Not
V100R008C00, PTN 7900 Supported by all serial boards Yes

V100R011CX0 NOTE NOTE
0, When a PTN 7900 works as the reflector, a When a
V100R011C00 maximum of 128 TWAMP test cases are PTN
SPC500T, supported. 7900
works
V100R011C00
as the
SPC600T, sender,
V100R012C00 a
SPC100, maximu
V100R012C00 m of
SPC200, and 2048
TWAMP
V100R012C00
test
SPC300 cases
are
support
ed.
Each
board
support
sa
maximu
m of
1024
TWAMP
test
cases
(the
maximu
m of
TWAMP
test
cases
support
ed by a
PTN
7900–
12 is
decreas
ed by
half).

iMaster NCE-IP

Type Support
ed or
Not
V100R011C00, PTN7900E Supported by all serial boards Yes

V100R011C00
SPC500T,
V100R011C00
SPC600T,
V100R012C00
SPC100,
V100R012C00
SPC200, and
V100R012C00
SPC300
V100R011C00 PTN990E Supported by all serial boards Yes

SPC500T,
V100R011C00
SPC600T,
V100R012C00
SPC100,
V100R012C00
SPC200, and
V100R012C00
SPC300
V100R008C00, PTN990 Supported by all serial boards Yes

V100R011C00,
V100R011C00
SPC500T,
V100R011C00
SPC600T,
V100R012C00
SPC100,
V100R012C00
SPC200, and
V100R012C00
SPC300

iMaster NCE-IP

Type Support
ed or
Not

V100R011C00
SPC100T,
V100R011C00
SPC200,
V100R011C00
SPC500T,
V100R011C00
SPC600T,
V100R012C00
SPC100,
V100R012C00
SPC200, and
V100R012C00
SPC300

V100R011C00,
V100R011C00
SPC100T,
V100R011C00
SPC200,
V100R011C00
SPC500T,
V100R011C00
SPC600T,
V100R012C00
SPC100,
V100R012C00
SPC200, and
V100R012C00
SPC300
V100R007C00 PTN960 Supported by all serial boards No

& (TND3CXPA/B and TND5CXPA/B)
V100R007C10
V100R007C00 PTN950 Unsupported by the old board No

& (TND1CXP PL317) and supported by
V100R007C10 new boards (TND2CXP and
TND2CXPC/D)
V100R007C00 PTN910 Unsupported by old boards No

& (TNC1CXPA/B/G/H/I PL317) and
V100R007C10 supported by new boards
(TNC2CXPI/N)

iMaster NCE-IP

Type Support
ed or
Not
V100R007C00 PTN910-F Supported by the TNE1CXPA/B boards No

&
V100R007C10
V100R011C00 PTN910E- Supported by all serial boards No

F
V100R007C00 PTN906A Supported by the TPH1CXPA board No

&
V100R007C10
V100R007C00 PTN905A Supported by the TNP2CXPA board No

&
V100R007C10
V100R007C00 PTN905B Supported by the TNP2CXPB board No

&
V100R007C10
V100R007C00 PTN3900/ Supported by the TN81EXL1, TN86EX4, No

3900-8 TN83EX2, and TN86EX2 boards without
distinguishing single-stack and dual-
stack
V100R007C10 PTN3900/ Distributed OAM (single-stack): No

3900-8 supported by the TN81EXL1, TN86EX4,
TN83EX2, and TN86EX2 boards
Centralized OAM (dual-stack):
supported by all series of Ethernet
boards and not supported by the low-
speed board MP1 or X11 series boards
such as TN81EG16, TN82EG16, and
TN81EX2
V100R007C00 PTN1900 Unsupported by all boards No
V100R007C10 PTN1900 Supported by the TN73CXP board only No

in dual-stack mode
V100R007C10 PTN1900 Unsupported by TN71CXP/TN72CXP No

boards
Versions later PTN6900 Supported by new 588x boards No

than
V600R007C00
V800R007C00 PTN6900- Supported by new 588x boards No

M

iMaster NCE-IP

Type Support
ed or
Not
V800R011C10 PTN Yes Yes

6900-2-
M8C
V800R011C10 PTN6900- Yes Yes

2-M8A

2-M16A
V800R012C00 PTN Yes Yes

6900-2-
M14

8

16

8A(V8)

16A(V8)

M2K

M2K-B
NOTE
● For an L2VPN, an L2VPN name and an L2VPN interface have to be configured on the
PTN reflector.
● For an L3VPN, an L3VPN interface has to be configured on the PTN reflector if the PTN
device works in dual-stack mode and an L3VPN name and an L3VPN interface have to
be configured if the PTN device works in single-stack mode.

iMaster NCE-IP
Table 7-36 Huawei ATN support for TWAMP
NCE Device Type Boa Single- Dual- Reflect Sende

Version rd Stack Stack or r
Typ Mode Mode Suppor Suppo
e Support Suppor ted or rted or
ed or ted or Not Not
Not Not
NCE All ATNs N/A N/A N/A Y N

V100R01
9C00
Specifications
The following lists the specifications supported by TWAMP-based IP RAN or PTN
quality monitoring:
● Viewing real-time performance data
The real-time performance data obtained from a TWAMP test can be
displayed in a line chart to help users learn the current service quality.
● Viewing historical performance data
Users can specify a time range to view the historical performance data of a
TWAMP test, helping users obtain the historical service quality, as well as
indicators when the quality is abnormal.
● Generating and exporting a TWAMP quality report
Statistics are collected for TWAMP test indicators, such as the delay, jitter, and
packet loss rate. A quality report can be generated or exported every 15
minutes, hour, day, week, month, or year.
● Generating a regional quality map
Statistics about TWAMP test indicators such as the delay, jitter, and packet
loss rate can be collected by region, helping you obtain the indicator quality
distribution and detect regions that require special attentions.
● Generating regional reports
In the hierarchical deployment solution, TWAMP test indicators, such as the
delay, jitter, and packet loss rate, can be collected by region, helping you
collect statistics on and analyze quality of different regions.
● Supporting three quality reports
– Network alarm statistics report: Collects statistics about base station
service quality alarms (delay, jitter, and packet loss rate) to help users
know base stations with deteriorated service quality and the deterioration
duration.
– Base station IP address usage report: Collects statistics about whether a
base station is reachable to help users know IP address usage of base
stations in difference regions.
– Network performance statistics report: Collects statistics about regional
network KPIs to provide a clear view of region ranks, which helps users
detect service bottlenecks.

iMaster NCE-IP
● Supporting one-time test, continuous test, and large buffer test

– One-time test only supports real-time collection and viewing of
performance data. If a probe functions as the test source, TWAMP test
results are collected at an interval of 30s by default. If an NE functions as
the test source, TWAMP test results are collected at an interval of 15s by
default.
– Continuous test supports test period configuration as well as collection
and viewing of historical performance data.
– Large buffer test is a high-precision TWAMP test initiated by a PTN 7900
to test performance (packet loss rate and number of lost packets) of a
device transmitting heavy traffic. A PTN 7900 supports only one large
buffer test at a time, with the packet sending interval of 0.1 ms and
sending period of less than 3 minutes. Loop detection can be enabled
only when the destination is a Huawei PTN device.
● Supporting TWAMP payload check parameter configuration for PTN 7900
V100R007C10
If a PTN 7900 V100R007C10 serves as the source of a TWAMP test, four types
of payloads (0x00, 0xff, 0x55, and 0xaa) can be configured. In this case, the
test result will contain the number of error packets.
● Supporting unified alarm management
For various indicators, users can set thresholds for different severities of
alarms. If the values of network or service indicators exceed the preset
thresholds during the TWAMP test, alarms are generated.
● Exporting TWAMP performance data through the performance text NBI
The data dictionary is provided, allowing TWAMP performance data to be
exported through the performance text NBI for interconnection with a third-
party system.
7.5.1.11 ICMP Quality Monitoring

NCE can proactively send packets to simulate an ICMP jitter test, which helps
users obtain network quality in real time and demarcate faults. A TWAMP test is
preferentially used for quality monitoring. If this test is not supported, use an
ICMP test.
Typical Networking
ICMP tests apply to various scenarios and feature easy deployment. NCE brings
the following benefits to carriers by working with NEU200s to perform ICMP jitter
tests:
● Monitors base station quality in an E2E and real-time manner to obtain base
station E2E quality as well as quality on the wireless and transmission sides.
● Monitors the link quality of important base stations in real time to obtain
network quality of important sites.
● Assists network fault demarcation and locating, including demarcation of
faults to the wireless side or transmission side.

iMaster NCE-IP

on
Scenario
Real- 1. Deploy core-layer devices interconnected with the EPC as the

time source, and configure multiple base stations as the destination.
monitori Deploy an ICMP jitter test to monitor the quality of links on both
ng and wireless and transmission sides in real time.
fault 2. Deploy core-layer devices interconnected with the EPC as the
demarcat source, and configure PTN devices interconnected with base
ion and stations as the destination. Deploy an ICMP jitter test to monitor
locating the quality of links on the transmission side in real time.
3. Based on the preceding link quality information, users can easily
monitor the quality of the wireless and transmission sides in real
time, facilitating fault demarcation.
This solution brings the following benefits to carriers:
time: Deploy the ICMP jitter test on the interface connecting a
core-layer device and a base station peer device to monitor the
the ICMP jitter test on the interface connecting a core-layer
device and an L2-to-L3 device to monitor the network in real
time. Once a service quality problem occurs on an L3 device, it
can be detected in real time and demarcated preliminarily.
ICMP Jitter Test

The following tables describe the related indicators, source and destination ends,
and version mapping of ICMP jitter tests.

iMaster NCE-IP
Table 7-38 ICMP jitter indicators
Packet loss Rate of the number of discarded packets to the total number of
rate packets transmitted within a period.
Delay Time used by a packet to be transmitted from the source end to

the sink end.
Jitter Difference between two consecutive delays for packets to reach

the same sink end.
Table 7-39 Requirements on ICMP test source and sink ends
Device Type Function as ICMP Function as ICMP

Source Destination
Base station N Y
(ICMP-capable device)
NE N Y
Specifications
The following lists the specifications supported by network quality monitoring
based on ICMP jitter tests:
● Viewing real-time performance data

The real-time performance data obtained from an ICMP jitter test can be
displayed in a line chart to help users learn the current service quality.
Users can specify a time range to view the historical performance data of an
ICMP jitter test, helping users obtain the historical service quality, as well as
indicators when the quality is abnormal.
● Generating and exporting an ICMP jitter quality report
Statistics are collected on indicators of the ICMP jitter test, such as the delay,
jitter, and packet loss rate. A quality report can be generated or exported
every 15 minutes, hour, day, week, month, or year.
● Generating a regional quality map
Statistics about ICMP test indicators such as the delay, jitter, and packet loss
rate can be collected by region, helping you obtain the indicator quality
distribution and detect regions that require special attentions.
● Supporting three quality reports
– Network alarm statistics report: Collects statistics about base station
service quality alarms (delay, jitter, and packet loss rate) to help users

iMaster NCE-IP
know base stations with deteriorated service quality and the deterioration
duration.
– Base station IP address usage report: Collects statistics about whether a
base station is reachable to help users know IP address usage of base
stations in difference regions.
– Network performance statistics report: Collects statistics about regional
network KPIs to provide a clear view of region ranks, which helps users
detect service bottlenecks.
● Supporting one-time test and continuous test.
– One-time test only supports real-time collection and viewing of
performance data. If a probe functions as the test source, ICMP jitter test
results are collected at an interval of 30s by default.
– Continuous test supports test period configuration as well as collection
and viewing of historical performance data.
● Supporting unified alarm management
For various indicators, users can set thresholds for different severities of
alarms. If the values of network or service indicators exceed the preset
thresholds during the ICMP jitter test, alarms are generated.
7.5.1.12 Trace Test

NCE supports a trace test, during which the hop-by-hop path from the source to
the destination can be detected on a specific network, helping users detect or
restore a service path.
Function Overview
During a trace test, packets with different time to live (TTL) are sent to the
destination to determine the IP address, packet loss rate, and delay of each hop
on the path.
The following tables describe the related indicators, source and destination ends,
and version mapping of trace tests.
Table 7-40 Trace test indicators

Packet loss Ratio of the number of lost packets on each hop to the total
rate number of packets transmitted on the forwarding path from the
source to the destination within a period of time.
Delay Time required for each intermediate device to respond when a

packet is sent along the forwarding path from the source device to
the destination device.

iMaster NCE-IP
Trace Test Description
Table 7-41 Requirements on trace test source and sink ends
Device Type Function as Trace Function as Trace Test

Test Source Sink
IP address (IP address of N Y

a device, an interface, or
a BTS)
SNC Y N
Specifications
The following lists the specifications supported by network quality evaluation
based on trace tests:

To learn the quality of a service path, users can view the historical
performance data and check the IP address, packet loss rate, and average
two-way delay of each hop.
● Supporting periodical testing
The test period can be set to 5min, 10min, 15min, 20min, or 30min to
facilitate periodical tests of a service path.
7.5.1.13 Network Path Restoration and Auxiliary Fault Demarcation
7.5.1.13.1 ATN+CX Network Path Restoration and Auxiliary Fault Demarcation

In ATN+CX networking mode, alarms displayed in the physical topology trigger
path restoration from the source interface to the destination interface. After hop-
by-hop diagnosis is performed for the restored paths, the TWAMP/ICMP indicators
(delay, jitter, and packet loss rate) of devices are obtained for auxiliary fault
demarcation, helping O&M personnel learn the alarm conditions and locate faults.
Function Overview
NCE utilizes the path restoration function triggered by TWAMP tests and ICMP
jitter tests to help carriers achieve the following:
● Discover and restore hop-by-hop service paths from the alarm source to the
alarm destination.
● Based on the restored service paths, read indicators of existing or on-demand
TWAMP tests or ICMP jitter tests hop by hop; implement hop-by-hop fault
diagnosis based on the test results.
Figure 7-24 shows the typical networking scheme.

iMaster NCE-IP
Figure 7-24 Typical networking scheme

iMaster NCE-IP
Table 7-42 Path restoration and auxiliary fault demarcation

Scenario Category Description
Path restoration Proactive path Use the TWAMP test

NOTE restoration (initiated case as an example:
Path restoration supports from the probe) 1. The proactive NEU200
hierarchy VPN (H-VPN) NOTE associated with the
and mixed VPN In the probe-initiated
networking scenarios. RNC/EPC interface
proactive path restoration
Hierarchical design is initiates a proactive
scenario, the indicator
adopted from CSG to RSG alarms that trigger path TWAMP test case, and
and applies to large-scale restoration support the base station
networks. TWAMP and ICMP reports indicator
● In the H-VPN scheme, a proactive testing alarms to NCE.
hierarchical L3VPN indicators.
needs to be established 2. TWAMP indicator
to completely isolate all alarms trigger path
access rings and restoration, and the
aggregation rings at associated RNC/EPC
the protocol layer. interface is found
Intra-ring links or node
based on the source
faults are synchronized
to the NMS only inside NEU200 in the test
the area where the ring case.
resides instead of 3. The RSG interface
devices outside the
connected to the
ring. The protocol layer
can support 100,000 or RNC/EPC is used as
more rings. the source interface,
● The mixed VPN scheme and the CSG interface
applies to mobile connected to the base
bearer projects where station is used as the
independent O&M is destination interface.
performed for access The interface
rings and aggregation
information is
rings. The characteristic
is that the access reported to the
Ethernet and low-speed Manager for IP RAN
service bearer modes path restoration.
are consistent. NOTE
● If the test case
destination is a base
station, select the
CSG router interface
connected to the
base station as the
destination
interface.
destination is an
ATN NE, select the
ATN NE interface at
the TWAMP test
case destination as
the destination
interface.

iMaster NCE-IP
4. NCE obtains H-VPN

paths for restoration
from the Manager
and displays them to
users in the physical
topology.
Proactive path 1. The SNC initiates a

restoration (initiated proactive TWAMP test
from the SNC) case, and the SNC
interface at the test
case source end works
as the source
interface for path
restoration.
2. The CSG destination
interface is found
based on the
destination device
type of the TWAMP
test case.
NOTE
destination is a base
station, select the
CSG router interface
connected to the
base station as the
destination
interface.
destination is an
ATN NE, select the
ATN NE interface at
the TWAMP test
case destination as
the destination
interface.
3. The interface
information is
reported to the
Manager for IP RAN
path restoration.
4. NCE obtains H-VPN
paths for restoration
from the Manager
and displays them to
users in the physical
topology.

iMaster NCE-IP
Auxiliary fault Proactive path TWAMP test indicators

demarcation restoration (initiated Check whether the hop-
from the probe) by-hop destination
NOTE device in the H-VPN path
TWAMP/ICMP test obtained through path
indicators are supported.
restoration has an IP
address.
● If the hop-by-hop
destination device has
an IP address, search
for the existing
TWAMP test case
based on the source
probe interface IP
address, VRF, source
device ID, and
destination device IP
address, and obtain
the latest result data
in the recent 15
minutes for
accumulation.
destination device
does not have an IP
address, search for
the existing TWAMP
test case based on the
source probe device
ID and destination
device ID, and obtain
in the recent 2 hours
for accumulation.
NOTE
The hop-by-hop
destination device
indicates the ingress
interface of the NE in the
H-VPN path restored by
the Manager.
In the H-VPN path restored
by the Manager, the device
from RSG to CSG is the P
device. Except the RSG
ingress interface and the
CSG egress interface, the
ingress interface of the P
device has no IP address.
ICMP test indicators

iMaster NCE-IP
1. Check whether the

hop-by-hop
destination device in
the H-VPN path
obtained through
path restoration has
an IP address.
2. If the hop-by-hop
for the existing ICMP
source probe interface
IP address, VRF,
source device ID, and
address, and obtain
for accumulation.
3. If the hop-by-hop
destination device
does not have an IP
address, search for
the existing ICMP test
case based on the
source probe device
ID and destination
in the recent 15
minutes for
accumulation.
NOTE
The hop-by-hop
destination device
interface of the NE in
the H-VPN path
restored by the
Manager.
In the H-VPN path
restored by the
Manager, the device
from RSG to CSG is the
P device. Except the
RSG ingress interface
and the CSG egress
interface, the ingress
interface of the P
device has no IP
address.

iMaster NCE-IP
4. If the destination
device has an IP
address but does not
have data of the
existing ICMP test
case, apply a real-
time ICMP test case
to the destination
device IP address.
NOTE
● If the destination
device is an ATN NE,
the device in this hop
has no IP address; if the
existing ICMP test case
is not found, the real-
time ICMP test case is
not deployed.
● In the H-VPN path
restored by the
Manager, the device
from RSG to CSG is the
P device. Except the
RSG ingress interface
and the CSG egress
interface, the ingress
interface of the P
device has no IP
address. A real-time
ICMP test case is
deployed.

iMaster NCE-IP
Proactive path Check whether the hop-

restoration (initiated by-hop destination
from the SNC) device in the H-VPN path
NOTE obtained through path
Only TWAMP test restoration has an IP
indicators are supported. address.
for the existing
TWAMP test case
based on the source
probe interface IP
address, VRF, source
device ID, and
address, and obtain
in the recent 15
minutes for
accumulation.
destination device
does not have an IP
address, search for
the existing TWAMP
source probe device
ID and destination
for accumulation.
NOTE
The hop-by-hop
destination device
interface of the NE in the
H-VPN path restored by
the Manager.
In the H-VPN path restored
by the Manager, the device
from RSG to CSG is the P
device. Except the RSG
ingress interface and the
CSG egress interface, the
ingress interface of the P
device has no IP address.

iMaster NCE-IP
Diagnosis Test Indicator Description

ATN+CX quality diagnosis supports ICMP jitter and TWAMP tests. The following
tables describe the related indicators, source and destination ends, and version
mapping.
Table 7-43 ICMP jitter and TWAMP indicators


the sink end.

the same sink end.
Table 7-44 Requirements on ICMP jitter test source and sink ends
Device Type Function as ICMP Function as ICMP Jitter
Jitter Source Sink
NEU200 Y N
Base station N Y
Device/Interface IP N Y
address
IP device N Y

Device Type Function as TWAMP Function as TWAMP
Source Sink
IP device (TWAMP- Y Y
capable device)
station
Specifications
The following describes the specifications supported by ATN+CX quality path
restoration and auxiliary fault demarcation:

iMaster NCE-IP
● A TWAMP test case alarm can trigger path restoration and auxiliary fault
demarcation.
If a TWAMP test case, whose source is a Huawei IP device, PTN, or probe,
generates an alarm, click the alarm device in the performance topology. In the
quality alarm panel displayed in the right pane, manually trigger path
restoration and auxiliary fault demarcation to help fault analysis.
● An ICMP jitter test case alarm can trigger path restoration and auxiliary
fault demarcation.
If an ICMP jitter test case with the source of an NEU200 generates an alarm,
click the alarm device in the performance topology. In the quality alarm panel
displayed in the right pane, manually trigger path restoration and auxiliary
fault demarcation to help fault analysis.
● Hop-by-hop fault information collection is supported.
Auxiliary fault demarcation is implemented based on the restored path, and
performance indicator values are accumulated. The fault information is
displayed on each hop of the path, including the link traffic, optical power,
and queue packet loss rate. The lower pane of each hop of the path provides
a report tab page to display detailed indicators.
7.5.1.13.2 IP Network Path Restoration and Auxiliary Fault Demarcation

In case of an alarm generated in a TWAMP test initiated by an NE with an SNC
board installed, NCE supports manual triggering of a trace test for service path
restoration as well as hop-by-hop fault diagnosis through a TWAMP test, helping
fault demarcating and locating.
Function Overview
Path restoration brings the following benefits to carriers:
Based on the restored service paths, read indicators of existing or on-demand
TWAMP tests hop by hop; implement hop-by-hop fault diagnosis based on the
test results.
Table 7-46 Auxiliary fault demarcation rules
Applicati Rule Description

on
Scenario
Auxiliary After path restoration is complete, a hop-by-hop diagnosis test can

fault be performed only on a Layer 3 network.
demarcat Hop-by-hop diagnosis rule for Layer 3 devices: Check whether any
ion TWAMP test cases use a Layer 3 device as the destination. If yes,
obtain the latest result reported in the last 15 minutes.

IP network quality diagnosis supports TWAMP tests. The following tables describe
the related indicators, source and destination ends, and version mapping.

iMaster NCE-IP
Table 7-47 TWAMP indicators

the sink end.

the same sink end.

Source Sink

board installed
Destination device IP Y Y
station
Specifications
The following describes the specifications supported by IP network quality path
restoration and auxiliary fault demarcation:
A TWAMP test case alarm can trigger path restoration and auxiliary fault
demarcation.
If a TWAMP test case with the source of an NE generates an alarm, click the
alarm device in the performance topology. In the quality alarm panel displayed in
the right pane, manually trigger path restoration and auxiliary fault demarcation
to help fault analysis.
7.5.1.13.3 PTN Network Path Restoration and Auxiliary Fault Demarcation

In case of an alarm generated in a TWAMP or an ICMP jitter test, NCE supports
manual triggering of a trace test for service path restoration, helping fault
demarcating and locating.
Function Overview
NCE utilizes the path restoration function triggered by TWAMP tests and ICMP
jitter tests to help carriers achieve the following:

iMaster NCE-IP
Based on the restored service paths, read indicators of existing or on-demand

TWAMP tests or ICMP jitter tests hop by hop; implement hop-by-hop fault
diagnosis based on the test results.
Table 7-49 Auxiliary fault demarcation rules

Applicati Rule Description
on
Scenario
Auxiliary NCE determines a device model based on the trace test result. If a
fault device has an IP address, it is a Layer 3 device; otherwise, it is a
demarcat Layer 2 device.
ion After TWAMP test cases generate an alarm and path restoration is
complete, the hop-by-hop diagnosis rules are as follows:
● Hop-by-hop diagnosis rules for Layer 2 devices:
If the destination device is a single-stack L2VPN or L3VPN device
or a dual-stack PTN device, check whether TWAMP test cases to
the device exist.
– If such TWAMP test cases exist, report the results in the last 15
minutes.
– If no such TWAMP test cases exist, no data is reported and no
indicator data is accumulated in the path restoration view.
● Hop-by-hop diagnosis rules for Layer 3 devices:
– When the test protocol type is TWAMP:
Check whether TWAMP test cases to the destination IP
address exist.
– If such TWAMP test cases exist, report the results in the last 15
minutes.
– If no such TWAMP test cases exist, no data is reported and no
indicator data is accumulated in the path restoration view.
– When the test protocol type is ICMP:
Check whether ICMP jitter test cases to the destination IP
address exist.
– If such ICMP jitter test cases exist, report the results in the last
15 minutes.
– If no such ICMP jitter test cases exist, create an on-demand
ICMP jitter test case and report the test results.

PTN quality diagnosis supports ICMP jitter and TWAMP tests. The following tables
describe the related indicators, source and destination ends, and version mapping.

iMaster NCE-IP
Table 7-50 ICMP jitter and TWAMP indicators


the sink end.

the same sink end.
Table 7-51 Requirements on ICMP jitter test source and sink ends
Device Type Function as ICMP Function as ICMP Jitter
Jitter Source Sink
Base station N Y
Device/Interface IP N Y
address
NE N Y

Source Sink

board installed
station
PTN device with an Y Y

internal PTN probe
IP device (that is, the Y Y

NE40E, CX600, or ATN
device in the V8 version)
RTN device N Y
Specifications
The following describes the specifications supported by PTN path restoration and
auxiliary fault demarcation:

iMaster NCE-IP
● A TWAMP test case alarm can trigger path restoration and auxiliary fault
demarcation.
If a TWAMP test case, whose source is a Huawei IP device, PTN, or probe,
generates an alarm, click the alarm device in the performance topology. In the
quality alarm panel displayed in the right pane, manually trigger path
restoration and auxiliary fault demarcation to help fault analysis.
● An ICMP jitter test case alarm can trigger path restoration and auxiliary
fault demarcation.
If an ICMP jitter test case with the source of an NEU200 generates an alarm,
click the alarm device in the performance topology. In the quality alarm panel
displayed in the right pane, manually trigger path restoration and auxiliary
fault demarcation to help fault analysis.
● Hop-by-hop fault information collection is supported.
Auxiliary fault demarcation is implemented based on the restored path, and
performance indicator values are accumulated. The fault information is
displayed on each hop of the path, including the link traffic, optical power, bit
error, and queue packet loss rate. The lower pane of each hop of the path
provides a report tab page to display detailed indicators.
7.5.2 Network Path Optimization
7.5.2.1 Background
With the development of networks, services occupy more and more network
resources, and the network becomes increasingly complex and large. The
traditional MPLS TE technology cannot meet the requirements of the live network.
MPLS TE enables the establishment of label switched path (LSP) tunnels with
specified paths based on reserved resources and preempts bandwidth resources of
LSPs with lower priorities to control traffic paths when resources are insufficient.
Although MPLS TE substantially improves bandwidth resource efficiency, it is
difficult to plan paths in a large topology. In addition, MPLS TE path computation
depends on Interior Gateway Protocol Traffic Engineering (IGP TE) topology
information, but IGP TE floods only the topology information of IGP domains and
consequently cannot compute or establish end-to-end (E2E) TE tunnels across IGP
domains or even autonomous systems (ASs).
In addition, the constrained shortest path first (CSPF) algorithm used for MPLS TE
path computation can only be determined by the source nodes of tunnels, and this
distributed computation and management approach cannot coordinate bandwidth
resources, leading to problems such as bandwidth resource waste and even tunnel
establishment failure.
Network Path Optimization computes the optimal E2E forwarding paths and
optimizes the paths as required. It centrally configures and manages network
topology information to leverage the full potential of network resources.
7.5.2.2 Feature Introduction

Network Path Optimization is a technology dedicated to service path optimization
and therefore plays an important role in network service quality assurance.

iMaster NCE-IP
Network Path Optimization has the following technical advantages:

● Visualized global tunnel topology
Network Path Optimization enables visualized monitoring of the entire
network topology and monitors network-wide link bandwidth utilization
based on the collected traffic statistics. This topology allows administrators to
detect traffic path changes in real time and optimize traffic accordingly to
prevent network faults.
● Centralized global multi-domain path computation
The controller establishes BGP peers with routers to collect the topologies of
multiple ASs. After combining and processing these topologies, it computes
inter-AS tunnel paths based on one uniform topology. It can also interconnect
with other AS controllers to collect the topologies of multiple ASs in order to
establish inter-AS service paths. Centralized path computation enables
collaborative management of network resources, maximizes network
bandwidth utilization, and reduces the bandwidth resource conflicts caused by
distributed computing.
● Intelligent maintenance during a fixed period of time
During a maintenance window, traffic automatically bypasses maintained
nodes or links. After the maintenance is complete, traffic switches back to the
original paths. If faulty nodes or links exist, traffic can also automatically
bypass these nodes or links.
● Multiconstraint-based path computation for various tunnels
– Path computation is available for both traditional services (RSVP-TE) and
other types of tunnels, including SR-TE (SR-MPLS TE), SR Policy (SR-MPLS
TE Policy and SRv6 Policy), and service paths (inter-AS tunnel over SR
Policy). For the new technology SRv6 Policy, Network Path Optimization
supports both unequal cost multipath (UCMP) load balancing based on
multiple segments and DSCP-based traffic steering to provide
differentiated SLA assurance for applications. The segments that UCMP
depends on are dynamically computed by the path computation unit and
can be split based on service requirements to ensure service quality.
– Multiconstraint-based path computation refers to the act of setting
primary/backup path, availability, and disjoint tunnel constraints to
maintain high network reliability; (2) setting explicit/excluded paths, co-
routing, path pinning, switchback, and other constraints to maintain high
network controllability; or (3) setting reserved bandwidth, real-time
bandwidth, delay, and other constraints to satisfy SLAs.
– Network Path Optimization also supports SRv6 Policy group deployment.
Bandwidth is reserved so that the planned SRv6 Policies can be quickly
deployed upon network changes.
● Higher packet processing efficiency thanks to generalized SRv6
Generalized SRv6 (G-SRv6) is an SRv6-compatible SRH compression solution.
SRH compression helps reduce the overheads of SRv6 packet headers. In
addition, G-SRv6 SIDs and conventional SRv6 SIDs can be programmed in the
same SRH, enabling SRv6 to smoothly evolve from non-compression solutions
to a compression solution.
A complete SID is 128 bits long and consists of three parts: Locator, Function,
and Arguments (optional). Locator can be divided into B (prefix) and N (node
ID). B is redundant because it is a common prefix of SIDs on an SRv6 network.

iMaster NCE-IP
If B is placed in a shared location, N and Function constitute shorter

generalized SIDs (G-SIDs) for forwarding packets, thereby enhancing SRv6
packet processing performance and facilitating large-scale SRv6 deployment.
● Slice-centric optimization
During optimization, you can specify a slice to optimize paths for tunnels
within the slice. The paths of tunnels in other slices will remain unchanged.
● Multiple optimization mechanisms
Network Path Optimization provides different trigger mechanisms for
different usage scenarios to ensure optimal service paths. The automatic
optimization mechanism provides the automatic approval function. You can
determine whether to directly deliver path computation results by enabling or
disabling automatic approval. Manual approval is required if automatic
optimization is disabled, automatic approval is disabled, or manual
optimization is used.
Table 7-53 Optimization mechanisms

Optimization Description
Mechanism
Automatic Automatic optimization and automatic approval

optimization If a network is too large for manual optimization, use
automatic optimization (triggered periodically or upon link
threshold crossing) and automatic approval. The path
computation results are directly delivered, reducing
manual intervention and OPEX. However, this mechanism
is risky. Exercise caution when using this mechanism.
Automatic optimization and manual approval

Path computation results can be delivered only after being
manually approved. This mechanism allows you to have
more control over the network.
Manual Local optimization

optimization When a link is congested, you can optimize the specified
tunnel or link.
Global optimization
If traffic imbalance exists on a large number of tunnels,
you can perform global optimization to optimize network-
wide service paths.
● Flexible selection of optimization policies

Optimization aims to maximize network throughput and minimize path costs,
that is, to make more services run in shorter and lower-weight paths. In
practice, however, some services are sensitive to delay. Therefore, the delay
attribute is provided for such services. Considering that some links may
become faulty frequently, link availability is also introduced to ensure that
services are running over the links with the minimum fault rate.

iMaster NCE-IP
Table 7-54 Optimization policies

Optimization Policy Description
Least TE metric Among all the paths that meet the specified
constraints, the one with the least TE metric will be
selected.
Minimum delay Among all the paths that meet the specified
constraints, the one with the minimum delay will be
selected.
Maximum availability Among all the paths that meet the specified
NOTE constraints, the one with the maximum availability
Link availability is the will be selected.
ratio of up time to
down time.
Bandwidth balancing Among all the paths that meet the specified
constraints, the one with the smallest sum of
reciprocals of remaining link bandwidths will be
selected.
7.5.3 VPN Service Assurance
7.5.3.1 Trends and Status Quo

This section describes the trend and O&M status quo of VPN services.
Service Trend
New technologies, such as SRv6, are ready for commercial use. Agile provisioning
of VPN services requires intelligent diagnosis and in-line monitoring in VPN
scenarios to implement SLA quality visualization.
O&M Status
VPN services cannot be measured hop by hop, and the service status in the fault
occurrence period cannot be played back. As a result, it is difficult to accurately
demarcate faults. The fault locating period is as long as several days or even
weeks, and the efficiency is low.
7.5.3.2 Solution Overview

Based on technologies such as In-situ Flow Information Telemetry (IFIT), Two-Way
Active Measurement Protocol (TWAMP), and Y.1731, NCE meets the service level
agreement (SLA) assurance and O&M requirements of VPN services, implements
proactive and visualized SLA awareness of services, and proactively and quickly
demarcates and locates faults, ensuring good user experiences.
Measurement Technology
From the perspective of technologies, the existing network performance
measurement technologies in the industry each have defects, so none of them can

iMaster NCE-IP
meet the requirements of VPN networks on measurement precision, hop-by-hop

measurement, service scenario, and performance. Based on the advantages and
disadvantages of the existing performance measurement technologies, Huawei
launches IFIT. IFIT is an extension to in-band OAM (iOAM) while integrating the IP
flow performance measurement (IP FPM) and RFC 8321 coloring technologies to
directly measure packets. IFIT cooperates with Telemetry as well as unified
management, control, computation, and visualization to enable real-time
visualization and proactive monitoring of network quality SLAs and rapidly
demarcate and locate faults. It is an important O&M technique for VPN networks.
Figure 7-25 Traditional out-of-band measurement
Figure 7-26 Hybrid measurement

iMaster NCE-IP
Figure 7-27 IFIT in-band flow measurement

iMaster NCE-IP
Table 7-55 Comparison of measurement technologies in the IP RAN scenario

Mea Principle Usage Advanta Disadvantage
sure Scenario ge
men
t
Tech
nolo
gy
TWA TWAMP constructs L3VPN and When ● The service to be

MP packets to measure L3EVPN over the measured is not a
the SLA such as the SRv6 L3VPN real service, so
delay and packet loss or that hop-by-hop
rate to learn about L3EVPN measurement is
the network quality. service not supported.
flow is ● The measurement
interrupt precision is low
ed and and deviates from
no the actual
packet network.
exists on
the ● The sent test
path, packets consume
the network
TWAMP resources.
measure
ment
technolo
gy is
used.
Y. Located between out- L2VPN and When Y.1731 (Eth OAM):

1731 of-band measurement L2EVPN the This technology
and in-band VPWS L2EVPN applies only to Layer
measurement, Y.1731 service 2 services and
constructs a small flow is cannot traverse a
number of auxiliary interrupt Layer 3 network.
packets to perform ed and
SLA measurement on no
actual service flows. packet
Some measurements exists on
have high precision the
because they are path,
performed based on the Y.
actual service flows. 1731
measure
ment
technolo
gy is
used.

iMaster NCE-IP
Mea Principle Usage Advanta Disadvantage

sure Scenario ge
men
t
Tech
nolo
gy
IFIT By integrating the L3VPN V4/ ● High When the service

coloring technology L3EVPN V4 scala flow is interrupted
and in-situ over SRv6, bility, and no packet exists
measurement L3VPN V6/ vario on the path, the IFIT
technology, IFIT L3EVPN V6 us measurement
performs per-packet over SRv6, usage technology cannot
measurement, L2EVPN scena be used.
providing accurate VPWS over rios,
measurement results. SRv6, custom and
flow, and easy
auto- to
identified deplo
flow y
● Accur
ate
meas
urem
ent of
the
delay
and
packe
t loss
rate
based
on
actua
l
servic
e
paths
IFIT Process
This part uses the IP RAN scenario as an example to describe the IFIT process. The
IFIT process in the SPN scenario is similar. Users need to start the IFIT E2E
measurement on the first node of a VPN (for example, PE1 in the path PE1 ->
PE2). PE1 inserts the IFIT E2E measurement header into the flow from VRF100 to
PE2. PE1 and PE2 report the measurement results separately, and NCE calculates
and displays the E2E SLA of the service. For services that deteriorate in quality, the
system automatically triggers the IFIT trace hop-by-hop measurement mode on
the first node (for example, PE1) of the service. PE1 inserts the IFIT trace hop-by-
hop measurement header into the flow from VRF100 to PE2, and then hop-by-hop

iMaster NCE-IP
devices report measurement results. NCE calculates and displays the nodes and
links that cause poor quality hop by hop.
Figure 7-28 IFIT monitoring the traffic from PE1 to PE2
7.5.3.3 Usage Scenario

The VPN service assurance feature is oriented to IP RAN and SPN networks. It
builds the SLA assurance capability for private line services in Analyzer based on
performance measurement protocols.
When the VPN service assurance feature is deployed on NCE-IP, it supports the IP
RAN solution; when deployed on NCE-Super, it supports the IP RAN solution. For
details about the networking scenarios and measurement protocols, see Table
7-56.
Table 7-56 Networking scenarios and measurement protocols
Solutio Networking Scenario Measurem Deployment

n ent Mode
Technolog
y
IP RAN IP private network, IP cloud private line, IFIT, NCE-IP

site-to-site private line, and cloud TWAMP, Y.
backbone. The service types can be 1731
L3VPN, L3 EVPN, and L2 EVPN VPWS/
VPLS. This version mainly covers
L3VPNv4/L3 EVPNv4 over SRv6,
L3VPNv6/L3 EVPNv6 over SRv6, L2
EVPN VPWS over SRv6, L2 EVPN VPLS
over SRv6, and L3VPNv4/L3 EVPNv4/
L3VPNv6/L3 EVPNv6 over SE-TE/SR-
BE/SR-TE Policy.

iMaster NCE-IP
Solutio Networking Scenario Measurem Deployment

n ent Mode
Technolog
y
SPN Intra-metro enterprise site-to-site IFIT

private line, inter-metro enterprise site-
to-site private line, and enterprise site-
to-cloud private line. The service type
can be L2 EVPN (EVPN VLL) or L3VPN.
This version mainly covers the L2 EVPN
VLL and L3VPN service types, which are
dynamically or statically configured
based on VPN services, and supports
long-term real-time monitoring and on-
demand hop-by-hop measurement.
Figure 7-29 Scenario diagram (IP RAN)
Typical Networking
Based on the SLA assurance and O&M requirements of VPN service assurance,
NCE provides real-time SLA visualization and intelligent fault demarcation and
locating for IP RAN networking scenario.

iMaster NCE-IP
Figure 7-30 IP RAN networking scenario
NOTE
● Hybrid networking of VRPv5- and VRPv8-based devices is not supported.

● Hybrid networking of third-party and VRPv8-based devices is not supported.
● The IFIT, Y.1731, and TWAMP measurement technologies are supported.
7.5.3.4 Technical Principles

This section describes the technical principles of performance measurement
technologies (IFIT, TWAMP, and Y.1731) and the congestion view solution.
7.5.3.4.1 IFIT
As IP services pose increasingly strict requirements on committed and
differentiated SLAs, Huawei proposes the innovative IFIT solution by integrating
the advantages of all existing performance measurement technologies. For
example, it combines telemetry (a seconds-level data collection protocol), a data
analysis platform, and AI algorithms (for mass faults) to visualize service SLAs in
real time (precision improved from the link level to the service level), aggregate
mass poor-QoS faults (quantities reduced from thousands to tens), and fast
demarcate and locate faults (time shortened from hours to minutes). In addition,
this solution allows on-demand fault playback. These effectively improve IP service
O&M efficiency.
7.5.3.4.1.1 Measurement Mechanisms

This section describes how the Congestion View app uses IFIT to measure packet
loss and delay, and detect base station interruption.
IFIT Packet Header

The IFIT packet header encapsulates the packet loss and delay measurement flags
and a measurement mode flag (specifying the E2E or trace mode) to measure the
packet loss and delay of service packets in E2E or hop-by-hop mode.
Figure 7-31 IFIT encapsulation format

iMaster NCE-IP
Figure 7-32 IFIT encapsulation format for packet-by-packet delay measurement

iMaster NCE-IP
Table 7-57 Components in the IFIT packet header

Component Description
Flow ● Flow ID (20 bits): uniquely identifies a service flow. This ID

instruction must be unique across the measurement domain. NEs
header (FIH) identify flows based on flow IDs.
● L flag: packet loss measurement flag. It can be set to 0 or 1.
If it is set to 0 for packets in a measurement period, it will
be set to 1 for packets in the next period. For example, if the
number of L flags collected at the previous hop is 10 but
drops to 9 at the next hop in a measurement period, it is
considered that one packet is lost.
● D flag: delay measurement flag. The value 1 indicates that
delay measurement is required, whereas the value 0
indicates that delay measurement is not required.
● R: reserved
● R/S flag: If the FII label is not the last in the stack, the S
(bottom-of-stack) flag is carried. If the FII label is the last in
the stack, the R (reserved) flag is carried, and the default
value is 1.
● Header type indicator (HTI): an 8-bit FIH. The 8 bits are
described as follows:
– 0: reserved
– 1: basic E2E FIH
– 2: basic hop-by-hop FIH
– 3: extended E2E FIH (for FIEH)
– 4: extended hop-by-hop FIH (for FIEH)
– 5: packet-by-packet delay FIH (E2E), supported by SPN
V100R012C00SPC700 and later versions
– 6: packet-by-packet delay FIH (hop by hop), supported by
SPN V100R012C00SPC700 and later versions
– 7: reserved
Mechanism of Packet Loss Measurement

Packet loss measurement refers to the act of calculating the difference between
the number of packets entering a network and the number of packets leaving the
network within a measurement period.
1. The ingress sets the L flag to 0 or 1 by period (the two values are used
alternatively between consecutive periods). The forwarding chip at each hop
counts packets within a period.
The measurement period on the receive end is T – 1/3T to T + 2/3T, which is
2/3T later than that on the transmit end. This prevents out-of-order packets
from affecting packet measurement and ensures that the number of packets
in each period is correctly collected. For example, in the following figure, a
green packet is missing at T[0] but received at T[0] + 1/3T. The delay (1/3T) is

iMaster NCE-IP
within the designed range (2/3T); therefore, the packet, though out of order,
can still be counted at T[0].
2. Each node sends their counting results to NCE through telemetry.
3. NCE compares the packet counts of hops. If the count decreases at a point, it
determines that packet loss occurs.
Mechanism of Delay Measurement (Sampling)

In IFIT, delay measurement refers to the act of sampling packets on NEs and
recording the times when the packets are sent and received.
1. The ingress sets the D flag to 1 in only one packet in each period. The
forwarding chip of each node records the arrival and departure timestamps of
the sampled packets.
2. Each node sends their recorded results to NCE through telemetry.
3. NCE calculates the delay of each hop based on the received data.
Mechanism of Delay Measurement (Packet-by-Packet)

Packet-by-packet delay measurement efficiently measures the delay of each
service.

iMaster NCE-IP
1. The ingress does not report time. Other nodes use telemetry to report the
time of each packet to NCE based on the measurement period.
2. NCE calculates the delay of each node and aggregates the result at an
interval of 1 minute. For example, if the measurement period is 10 seconds,
the maximum value of the six maximum delays and the average value of six
average delays are used for the corresponding minute.
Mechanism of Base Station Flow Interruption Detection

A base station flow is a set of packets with the same source IP address, source
mask, sink IP address, sink mask, and flow ID.
Base station flow interruption is detected based on the number of lost packets
and the changes of flow rates. If the maximum packet loss rate of a flow is 100%
and the flow rate drops below the configured threshold (20% by default) after
several suppression periods, the flow is considered interrupted.
Mechanism of Base Station Interruption Detection

A base station is considered interrupted if all flows using the base station as the
source or sink are interrupted.
Base station flow interruption detection depends on complete IFIT measurement

results from devices. It applies to individual base station flows. If all flows of a
base station are interrupted, that is, the base station is interrupted, IFIT alone
cannot determine whether the base station is interrupted. To address this, the
Congestion View app combines IFIT with OAM. It initiates OAM detection from the
NPE to the base station to locate the fault point.
Taking the SPN scenario as an example, the detailed process is as follows:
1. IFIT is used to collect base station inventory data and automatically identify
potentially interrupted base stations based on the following criteria:
a. The maximum flow rate is 0.
b. There is no flow.
c. There is only a signaling flow, and its packet loss rate is 100% or invalid.

iMaster NCE-IP
2. Potentially interrupted base stations are clustered by UPE, SPE, and NPE to
generate a potential mass interruption fault.
3. NPEs and base station IP addresses are selected from the potential mass fault.
Each of the selected NPEs initiates OAM detection to base stations. If the
detection fails, the mass interruption fault exists in the base stations.
4. Initiate segment-by-segment OAM detection from the NPEs to the base
stations to demarcate the fault.
7.5.3.4.1.2 Measurement Modes

IFIT is a technology that measures the packet loss and delay of service flows. It
aims to obtain the packet loss rate and delay when the service flows pass through
a transport network. That is, it measures the packet loss rate and delay at the
ingress and egress of the transport network and then calculates the target
performance indicators. Performance indicators can be directly measured on each
NE to obtain the per-hop performance indicators of service packets. However, such
process is at a performance cost. If only E2E network indicators are needed,
network indicators do not need to be measured hop by hop, reducing performance
consumption. To sum up, IFIT has two measurement modes: E2E and hop-by-hop
measurement.
?.1. E2E Measurement Mode

The E2E measurement mode of IFIT applies to routine proactive O&M, which
measures performance at the ingress and egress of service flows. NCE aggregates
and analyzes the measurement results to calculate E2E service SLAs, and displays
the SLAs in reports or visual charts.

iMaster NCE-IP
Implementation Details
1. To achieve accurate measurement, high-precision time synchronization within
microseconds is deployed at both the ingress and egress to ensure that the
packet loss measurement periods of the ingress and egress of the E2E flow
match and the delay measurement periods are synchronous.
2. Global IFIT monitoring, telemetry subscription, and base station flow
monitoring are configured on NCE.
3. NEs identify service flows, record the number of packets and timestamps at
the ingress and egress based on packet or measurement flag, and measure
packet loss, delay, and real-time traffic to obtain E2E SLAs.
4. NEs periodically report packet loss and delay statistics to NCE through
telemetry.
5. NCE periodically calculates the packet loss and delay at the ingress and egress
of service flows. In addition, it displays the packet loss, delay, and real-time
traffic in the base station flow, data flow, and signaling flow reports based on
different periods.
– One-way link delay = Time of packet receiving on the egress – Time of
packet sending by the ingress
– Number of lost packets = Number of packets received by the ingress –
Number of packets sent by the egress
– Visualization through network-wide E2E base station flow, data flow, and
signaling flow reports
?.2. Hop-by-Hop (Trace) Measurement Mode

When any E2E indicator exceeds the threshold, NCE automatically enables IFIT
hop-by-hop measurement for fault diagnosis. (You can also enable this mode
manually.) When a service flow passes an NE, the NE uses telemetry to collect and
report data of each hop in seconds. NCE calculates indicators such as the delay
and packet loss rate of each hop of the service flow. If any indicator of a hop
exceeds the specified threshold, the hop is considered faulty. In this way, the faulty
NE or link can be located.

iMaster NCE-IP
Implementation Details
1. To achieve accurate measurement, high-precision time synchronization is
deployed on all nodes to ensure that the packet loss measurement periods of
all nodes through which a service flow passes match and the delay
measurement periods are synchronous.
2. For base station flows, to reduce the impact on performance, a hop-by-hop
monitoring policy is configured on NCE to identify threshold-crossing flows
and start hop-by-hop monitoring for them. An IFIT packet header is added to
threshold-crossing flows to enable NCE to learn the hop-by-hop path of each
real-time service flow and enable hop-by-hop diagnosis. For PTN static flows,
you can specify the IP 5-tuple (source IP address, sink IP address, source port,
sink port, and protocol) to create a PTN static flow monitoring instance and
enable hop-by-hop measurement.
3. At the ingress and egress of each NE through which a service flow passes, the
numbers of packets and timestamps are recorded based on packet or
measurement flag, and packet loss, delay, and real-time traffic are measured
to obtain the real-time SLAs of each NE and link on the service path.
4. NEs periodically report the packet loss and delay statistics of each NE, port,
and link to NCE through the Telemetry protocol.
5. NCE periodically calculates the packet loss and delay of each NE port based
on the hop-by-hop path of the threshold-crossing flow. In addition, it displays
the hop-by-hop path, packet loss, and delay information of base station flows
by period.
– One-way link delay = Time of packet receiving on the local node – Time
of packet sending by the previous node
– Number of lost packets = Number of received packets on the local node –
Number of packets sent by the previous node
– E2E path restoration and quality visualization for network-wide IP
services
▪ SR-BE and RSVP-TE: Restore the E2E flow paths and SLA indicators
based on the TTL result of IFIT hop-by-hop tracing.

iMaster NCE-IP
NOTE
SR-BE and RSVP-TE support only the (private IPv4) hop-by-hop restoration
solution, including tunnel path restoration, TTL restoration, and link
restoration.
▪ SR-TE and SR-TP: Restore the E2E flow paths and SLA indicators
based on the tunnel inventory data synchronized from NCE Manager
and Controller.
▪ L3VPN over SRv6 Policy/BE: Restore the E2E flow paths and SLA
indicators based on the Layer 2 link, IP link, dummy link, or virtual
link synchronized from NCE Manager and Controller.
Based on IFIT hop-by-hop measurement results, KPI analysis, and
diagnosis rules, fault locations and possible causes can be quickly located.
In addition, the transport network can prove its innocence and the 24-
hour SLA data of the last 7 days can be played back.
7.5.3.4.1.3 Mass Fault Aggregation Algorithm

When a node on the network is faulty, all service flows passing through the node
become poor-QoS. In this case, performing hop-by-hop diagnosis on all poor-QoS
service flows will consume a large number of performance resources, which is,
however, unnecessary. As such, the Congestion View app uses the mass fault
aggregation algorithm to calculate the similarity among poor-QoS flow paths and
among poor-QoS parameter features in a period. Higher similarities indicate a
higher probability that the faults are caused by the same root cause. If the
algorithm threshold is reached, the faults are aggregated into one incident.
7.5.3.4.2 TWAMP
TWAMP is a standard measurement protocol defined in RFC 6038. It is compatible
with most routers and base stations on live networks. TWAMP measures IP

iMaster NCE-IP
performance indicators such as the packet loss, delay, and jitter of links to monitor
network service quality in real time and facilitate fault demarcation.
Measurement Mechanism
1. NCE selects two TWAMP-capable devices (device A as the sender and device B
as the reflector) to create a TWAMP test case and initiates IP performance
test.
a. Sender: initiates a test, collects data, and collects statistics. The TWAMP
sender can be an NEU200, IP device, or PTN device.
b. Reflector: only replies test packets to the sender. The TWAMP reflector
can be an NEU200, base station, IP device, PTN device, or destination
device IP address.
2. Device A initiates a test session to device B.
3. Device B reflects the test session to device A.
4. NCE collects indicators in processes 2 and 3 from device A and calculates two-
way performance indicators.
Fault Demarcation and Locating Principles

1. Test case creation: A probe is deployed on the core network as the TWAMP
sender to send test packets and collect data. A base station and a CSG work
as the TWAMP reflector and respond to test packets.
2. Indicator collection: The probe collects performance indicators between the
core-side GW and CSG and between the core-side GW and base station in real
time, measures the packet loss rate, delay, and jitter of links on the transport
network and transport network to wireless segment, and reports the
indicators to NCE.
– Two-way packet loss rate: ratio of lost packets on a link to the total
number of transmitted packets over a period of time.
– Two-way delay: time used by a packet to be transmitted from the source
end to the sink end.
– Two-way jitter: difference between two consecutive delays for packets to
reach the same sink end.
3. Fault demarcation: NCE periodically calculates the average two-way packet
loss rate, two-way delay, and two-way jitter. Based on the configured alarm

iMaster NCE-IP
thresholds, the threshold-crossing indicators and related links are colored red.
This helps determine the quality of links between the core network and CSG
and between the core network and base station, quickly identify faulty links,
and determine whether the fault occurs on the core network or transport
network. For example, if the link between the core-side GW and CSG is
displayed in green and the link between the core-side GW and base station is
displayed in red, the link quality of the transport network is normal and
congestion occurs on the RAN.
7.5.3.4.3 Y.1731
Y.1731 is an OAM protocol proposed by ITU-T. It is used for performance
monitoring and fault management on Ethernet networks. This section describes
only the performance measurement functions of Y.1731, including single-ended
packet loss measurement, dual-ended packet loss measurement, one-way delay
measurement, two-way delay measurement, and single-ended synthetic packet
loss measurement in VLAN networks.
Table 7-58 Performance measurement functions of Y.1731
Function Description Usage Scenario
Single-ended Sends packet loss To measure packet loss, select

packet loss measurement information either single-ended or dual-
measurement between MEPs to assess ended packet loss
link quality. It is measurement.
independent of CC. ● Dual-ended packet loss
measurement delivers higher
accuracy than the single-
ended method. The interval
between dual-ended packet
loss measurements varies
with the interval between
CCM transmissions. The
CCM transmission interval is
shorter than the interval
between single-ended
packet loss measurements.
As such, the dual-ended

iMaster NCE-IP
Function Description Usage Scenario
Dual-ended Measures packet loss to method allows for a short

packet loss assess the quality of the interval and thus higher
measurement link between two MEPs accuracy.
with CFM CC enabled. ● Single-ended packet loss
measurement can be used
to minimize the impact of
many CCMs on the network.
One-way delay Measures the network To measure the link delay,

measurement delay on a unidirectional select one- or two-way delay
link between MEPs. measurement as needed.
Two-way delay Measures the network ● One-way delay

measurement delay on a bidirectional measurement is used to
link between MEPs. measure the delay on a
unidirectional link between
two MEPs with synchronous
time.
● Two-way delay
measurement is used to
measure the delay on a
bidirectional link between
two MEPs with
asynchronous time.
Single-ended Measures packet loss on a Single-ended synthetic packet

synthetic packet point-to-multipoint link to loss measurement is used to
loss monitor the link quality. measure accurate packet loss
measurement on point-to-multipoint links.
7.5.3.5 VPN Monitoring Specifications
VPN Performance Specifications

Item Specifications
Mea Performance IFIT: one-way delay, one-way packet loss, one-way jitter
sure indicator Y.1731: two-way delay, two-way packet loss, two-way
men jitter
t
item TWAMP: two-way delay, two-way packet loss, two-way
jitter
Delay Sampling, packet-by-packet

measuremen
t
Packet loss Packet-by-packet

measuremen
t

iMaster NCE-IP
Item Specifications
Measuremen IFIT: E2E measurement, hop-by-hop measurement

t capability TWAMP and Y.1731: E2E measurement, association
analysis
Mea Delay IFIT: microseconds-level

sure Y.1731: high
men
t TWAMP: low
preci Jitter IFIT: microseconds-level
sion
Y.1731: high
TWAMP: low
Packet loss IFIT: 10-6

rate Y.1731: high
TWAMP: low
E2E flow and hop- See VPN E2E Flow and Hop-by-Hop Flow
by-hop flow Specifications.
Perfo Query period IFIT: 1-minute, hourly, daily, weekly, monthly, yearly
rma Y.1731 and TWAMP: 5-minute, hourly, daily, weekly,
nce monthly, yearly
repo
rt Data lifecycle ● 1-minute data: 1 week
● 5-minute data: 1 week
● Hourly data: 30 days
● Daily data: 365 days
● Weekly data: 52 weeks
● Monthly data: 24 months
● Yearly data: 5 years
NBI Text NBI ● Collects traffic, delay, and packet loss rate data.
● Collection period:
IFIT: 1-minute, 5-minute
TWAMP and Y.1731: 5-minute, 15-minute
REST NBI Returns data in JSON or text format.

iMaster NCE-IP
Baseline Specifications of VPN Deployment Scenarios

Prod Scen Deployme M Baseline Expa Description
uct/ ario nt an Capability nsio
Solu Capability ag n
tion e Supp
m orte
en d
t
Sc
ale
NCE- Singl Manager 60 800 E2E No APN is a flow

IP e- +Controller 00 flows (200 identification
site +Analyzer( eq equivalent technology, which
Man Physical uiv nodes x 4) involves flow collection
ager machine) ale and 250 and reporting. Flow
+Con nt hop-by- collection consumes a
trolle NE hop flows large number of
r s resources. As such, APN
+Ana is not supported in this
lyzer scenario.
IP Manager 60 A Yes 1. Maximum number of

RAN +Controller 00 maximum IFIT hop-by-hop flows
+Analyzer( eq of 48,000 (collection period: 1-
Basic) uiv E2E flows minute): When the
ale (license- number of E2E flows is
nt controlled) less than or equal to
NE and 1000 100,000, the maximum
s hop-by- number of hop-by-hop
hop flows flows is 1000; when the
with one number of E2E flows is
server greater than 100,000,
added the number of hop-by-
hop flows equals the
15, 1000 E2E number of E2E flows
00 flows and divided by 100.
0 250 hop-
eq by-hop
uiv flows by
ale default. A
nt maximum
NE of 120,000
s flows
(license-
controlled)
and 1200
hop-by-
hop flows
with one
server
added.

iMaster NCE-IP

tion e Supp
m orte
en d
t
Sc
ale
30, 1000 E2E

00 flows and
0 250 hop-
eq by-hop
uiv flows by
ale default. A
nt maximum
NE of 240,000
s flows
(license-
controlled)
and 2400
hop-by-
hop flows
with one
server
added.
SPN Manager 60 Not Yes 1. Maximum number of

+Controller 00 supported IFIT hop-by-hop flows
+Analyzer( eq by default. (collection period: 1-
Basic) uiv Capacity minute): When the
ale expansion number of E2E flows is
nt is required less than or equal to
NE (160,000 100,000, the maximum
s unidirectio number of hop-by-hop
nal flows flows is 1000; when the
per number of E2E flows is
server). greater than 100,000,
the number of hop-by-
30, 2000 E2E hop flows equals the
00 flows and number of E2E flows
0 1000 hop- divided by 100.
eq by-hop
uiv flows by
ale default.
nt 160,000
NE unidirectio
s nal flows
with one
server
added.

iMaster NCE-IP

tion e Supp
m orte
en d
t
Sc
ale
80, 2000 E2E

00 flows and
0 1000 hop-
eq by-hop
uiv flows by
ale default.
nt 160,000
NE unidirectio
s nal flows
with one
server
added.
NCE Man Manager 60 A Yes 1. You are advised not to

ager +Controller 00 maximum use the following
+Con +Analyzer( eq of 48,000 advanced features on
trolle Basic) uiv flows after NCE-T:
r ale capacity 1) Private line SLA
+Ana nt expansion, analysis
lyzer NE license-
(IP s controlled. 2) Microwave network
+T, insight
IP+T 15, 1000 flows If these advanced
+FA 00 by default. features have been used,
N, 0 A capacity expansion is
and eq maximum required to use VPN
IP uiv of 120,000 service assurance.
+FA ale flows with
nt one blade 2. Maximum number of
N IFIT hop-by-hop flows
[exp NE added,
s license- (collection period: 1-
ansi minute): When the
on controlled.
number of E2E flows is
not 30, 1000 flows less than or equal to
supp 00 by default. 100,000, the maximum
orte 0 A number of hop-by-hop
d]) eq maximum flows is 1000; when the
uiv of 240,000 number of E2E flows is
ale flows after greater than 100,000,
nt capacity the number of hop-by-
NE expansion, hop flows equals the
s license- number of E2E flows
controlled. divided by 100.

iMaster NCE-IP

tion e Supp
m orte
en d
t
Sc
ale
NCE Supe - 15, 1000 flows No You are advised not to

r+IP 00 use the following
+T 0 advanced features on
(IP eq NCE-T:
+opti uiv 1) Private line SLA
cal ale analysis
scen nt
ario) NE 2) Microwave network
s insight
1. In
this If these advanced
scen features have been used,
ario, capacity expansion is
NCE- required to use VPN
Supe service assurance.
r
does
not
provi
de
the
priva
te
line
funct
ion
and
it
proc
esses
and
then
displ
ays
the
basic
perfo
rma
nce
data
obtai
ned
from

iMaster NCE-IP

tion e Supp
m orte
en d
t
Sc
ale
NCE-
IP
and
NCE-
T.
2. A
co-
depl
oyed
syste
m is
a
cross
-
dom
ain
scen
ario
for
Anal
yzer.
3. A
distri
bute
d
syste
m is
a
singl
e-
dom
ain
scen
ario
for
Anal
yzer.
For
detai
ls
abou
t the

iMaster NCE-IP

tion e Supp
m orte
en d
t
Sc
ale
capa
biliti
es,
see
the
specif
icati
ons
of
each
dom
ain.
NCE- Priva - 15, 5000 IFIT - Private line SLA analysis

Supe te 00 flows and VPN service
r line 0 assurance share
provi eq resources. The maximum
sioni uiv of 15,000 private lines
ng ale and 5000 IFIT flows
+Ana nt cannot be supported at
lyzer NE the same time.
(priv s
ate
line - 50, 30,000 IFIT - -
assur 00 flows
ance 0
) eq
uiv
ale
nt
NE
s

iMaster NCE-IP
VPN E2E Flow and Hop-by-Hop Flow Specifications

Scen Deploym Equi Fresh Compon Description
ario ent vale Installation ent
Capabilit nt Expansio
y NEs n
IP Single- 6000 800 E2E flows Not ● If the number of E2E

RAN site and 250 hop- supporte flows is less than or
Analyzer by-hop flows d equal to 100,000, the
(Basic) number of hop-by-
hop flows cannot
IP Analyzer 6000 Not supported Every exceed 1000.
RAN (Basic) time a
15,00 1000 E2E ● In capacity expansion
server is
0 flows and 250 scenarios, the
added,
hop-by-hop maximum number of
the
flows VPN flows is limited
specificati
by the license. The
on
maximum number is
increases
the licensed number
by
of equivalent NEs
240,000
multiplied by eight,
VPN
and the number of
flows
hop-by-hop flows is
(flowing
the number of E2E
in and
flows divided by 100.
out
In IP scenarios, a
through
maximum of three
single
servers can be added.
ports).
● For tunnel-level IFIT
measurement, the
number of E2E flows
is the number of E2E
flows divided by the
number of boards.
● In VPN Monitoring >
IFIT Monitoring
Configuration, the
number of locators
equals the number of
flows.
● In Application
Monitoring >
Custom Flow
Monitoring
Configuration or
Auto-Identified
Flow Monitoring
Configuration, the
number of custom or
auto-identified flows

iMaster NCE-IP

y NEs n
30,00 1000 E2E equals the number of

0 flows and 250 created monitored
hop-by-hop objects.
flows
SPN Analyzer 6000 Not supported Every ● If the number of E2E

(Basic) time a flows is less than or
30,00 2000 E2E server is equal to 100,000, the
0 flows and added, number of hop-by-
1000 hop-by- the hop flows cannot
hop flows specificati exceed 1000.
80,00 2000 E2E on ● In capacity expansion
0 flows and increases scenarios, the
1000 hop-by- by maximum number of
hop flows 160,000 VPN flows is limited
VPN by the license. The
flows maximum number is
(flowing the licensed number
in and of equivalent NEs
out multiplied by four,
through and the number of
single hop-by-hop flows is
ports). the number of E2E
flows divided by 100.
In the SPN scenario,
a maximum of five
servers can be added.
● In VPN Monitoring,
one VLL private line
equals four flows
(bidirectional +
working +
protection)
● In Application
Monitoring >
Custom Flow
Monitoring
Configuration or
Auto-Identified
Flow Monitoring
Configuration, the
number of custom or
auto-identified flows
equals the number of
created monitored
objects.

iMaster NCE-IP

y NEs n
NCE NCE- 15,00 5000 E2E Not -

- Super 0 flows and supporte
Supe 1000 hop-by- d
r hop flows
inter
conn 50,00 30,000 E2E Not -
ectin 0 flows and supporte
g 1000 hop-by- d
with hop flows
NCE
-IP
NOTE
● IFIT hop-by-hop data granularity: 1 minute

● TWAMP and Y.1731 do not involve hop-by-hop data.
● Numbers of E2E flows and hop-by-hop flows: Refer to the data or formulas described in
the preceding table.
● Custom flows and auto-identified flows belong to IFIT flows and have the same
specifications as IFIT.
7.6 Agile Open Container
7.6.1 Challenges in Network O&M

This section describes the challenges in network O&M.
Industry Trends
In the 5G era, network O&M is facing growing challenges. Network O&M is more
like traffic operations as its value objectives are changing from lowering costs to
generating benefits. Traditional network O&M uses a typical manual mode
requiring both human efforts and process assistance. It is semi-manual and semi-
automatic, and is evolving towards full automation. Network O&M evolution first
requires a change in the traditional thinking pattern, that is, from separation of
development and O&M to integration of them. To achieve this, the carriers' O&M
department must have Development and Operations (DevOps) capabilities that
can transform network O&M from traditional CT O&M into diversified ICT O&M.
In the era featuring rapid development of cloud computing, the design concept of
using the cloud-native architecture to ensure cloud service experience as adopted
for OTT services has a profound impact on the network construction mode of
carriers. Regardless of whether to follow carriers' bottom-up practice of "network
first, cloud later" or OTT service providers' top-down concept of "one network

iMaster NCE-IP
above cloud", the common factor driving the selection is that enterprises' digital
transformation is accelerating the requirements for cloud-network synergy. Cloud-
based network resource migration and cloud-network integration require both
carriers and enterprises to offer on-demand customization, so as to support future
service scenarios.
Customer Pain Points

In the traditional manual O&M model featuring "people + process", carriers or
enterprises have the following pain points:
● Carrier or enterprise networks are in the dilemma of multi-vendor device
management. Using devices from multiple vendors is a long-term strategy for
carriers and enterprises to avoid vendor lock-in. However, controllers of a
single vendor can only manage its own network devices, and there is no
unified interface standard for integration with the OSS system. The efficiency
in adapting to a new device depends on the vendor's capability and response
speed, which restricts the evolution in automatic provisioning of end-to-end
network services. The adaptation efficiency remains low for a long time and
has become an industry-recognized bottleneck.
● It takes a long time — usually half a year, or even one to two years — to roll
out a new service, which obviously cannot be able to meet the requirements
of the new era. Among the numerous reasons for low rollout speeds, the
typical one is that the development and O&M of new services are separated.
That is, based on the new service requirements raised by carriers or
enterprises, device vendors develop and release versions, which will then be
accepted and used by carriers or enterprises. This means a long process.
● To complete tasks such as network device adaptation and network cutover, an
engineer needs to manually execute a large number of command scripts,
which is error-prone. As the scripts increase in scale, their maintainability
keeps decreasing, making network O&M a high-risk task.
Obviously, this network management and control model that centers on single-
vendor configurations and baselines cannot meet increasingly flexible and agile
O&M requirements of carriers and enterprises. This is where multi-vendor-oriented
open and programmable network management and control solutions can help.
7.6.2 Introduction to AOC

Facing severe challenges in network O&M, Agile Open Container (AOC) provides a
multi-domain and multi-vendor open programmability platform for network
automation, on the basis of YANG models.
YANG Model
AOC is a network automation platform based on the YANG model. This means it
can better interconnect with the southbound and northbound YANG protocol
standard ecosystem, building a low-code platform for network automation.
NETCONF/YANG has become a mainstream network management protocol, ideal
for replacing traditional methods such as CLI and SNMP. It has the following
advantages over traditional methods:
● Machine-machine interfaces: NETCONF provides structured machine-
machine interfaces, enabling network automation.

iMaster NCE-IP
● Simplified network management: NETCONF defines a transaction

mechanism for devices, simplifying network management.
● Efficient management: NETCONF defines standards such as YANG Push and
Get Schemas, making network O&M more efficient.
● Standardization: Standards organizations and vendors have defined YANG
standards, and carriers and enterprises have helped promote YANG
standardization.
AOC can quickly manage NETCONF/YANG devices that are based on the YANG
model and manage CLI-based devices that are not based on the YANG model.
Multi-Domain and Multi-Vendor

Multi-domain: AOC supports multiple domains, such as carriers' data center
networks, metro networks, backbone networks, and mobile backhaul networks as
well as enterprises' data center networks, campus networks, and WANs. It also
manages diverse network devices. These devices include physical and virtual
network devices from the physical form perspective and include firewalls, switches,
and routers from the device type perspective.
Multi-vendor: AOC supports network devices from mainstream vendors, including
Huawei, Cisco, and Juniper, and supports fast integration of devices from other
vendors.
Network Automation
AOC is a network automation platform, which can combine device-level APIs into
abstract network service APIs for cross-device automatic orchestration.
By automating cumbersome, repetitive manual tasks, AOC frees up network
administrators and engineers for more in high-value tasks. It not only improves
employee satisfaction, but also improves productivity and reduces manual
configuration errors.

iMaster NCE-IP
Unlike traditional automation tools, such as Ansible, AOC is a dedicated network

automation tool that provides out-of-the-box network automation capabilities.
This is implemented through the YANG model, EasyMap mechanism, and
transaction mechanism of AOC. With AOC, you only need to focus on service code,
letting you quickly roll out services.
Open Programmability
AOC provides network open programmability capabilities, which allow you to
quickly define and deliver both multi-vendor management and network service
application development capabilities.
Figure 7-33 Open programmability
Similar to drivers and applications on Windows, AOC provides application and

driver openness capabilities.
Driver: AOC provides fast device driver programming capabilities to quickly
manage new devices.
Application: AOC supports the quick programming of service applications to
rapidly develop new applications.
By opening these capabilities and leveraging plug-and-play capabilities, you can
quickly roll out new services.
7.6.2.1 Application Scenarios

This section describes the main application scenarios of AOC.
Quick Adaptation to Multi-vendor Devices

Carrier and enterprise networks usually have devices from multiple vendors,
typically in scenarios such as automatic 5G site densification and multi-vendor CPE
configuration. However, these devices cannot be centrally managed. In addition,
slow integration of new devices, low automation, and long service provisioning
periods have become bottlenecks in end-to-end service delivery. AOC is a perfect
choice for improving device adaptation efficiency. It can automatically identify and
read YANG model files of devices through YANG interfaces, generate specific NE
driver (SND) packages, and load the packages to the system. In this way, a new

iMaster NCE-IP
device can get managed within one day, improving the adaptation efficiency by
90%.
Rapid Service Rollout

New service rollout depends on the OSS system and controller version update. It
takes a long time to roll out a new service due to problems such as insufficient
API integration and high customization costs. Such a service rollout speed cannot
support flexible service scenario changes. AOC allows users to customize service
YANG models and service logic, and can automatically generate northbound APIs
to quickly integrate with the OSS system, so that users can add, delete, modify,
and query devices and network services. The version development time is
shortened from 6-9 months to only 1 month (agile and on-demand release), and
the service rollout period is reduced by 80%.
Reliable Network Change Mechanisms

Legacy network O&M involves migration and modification of a large number of
services. These changes are achieved by manual operations or command scripts,
which are error-prone. It is difficult to maintain massive numbers of scripts,
leading to high risks in network changes. To resolve these difficulties, AOC
provides secure and reliable mechanisms such as dry run, rollback, transaction,
and concurrency, improving the network change accuracy to 99.9%.
Full-Stack Programmability for Management, Control, and Analysis

In the 5G network slicing and intelligent O&M scenarios, AOC not only
implements programmable service provisioning, but also provides path
computation and intelligent analysis programmability based on user-defined
network service models, maximizing the support for future network evolution of
carrier and enterprise services.
7.6.2.2 Customer Benefits

AOC can meet the following requirements of carriers and enterprises:
● Agile automation: New service rollout depends on the OSS and controller
version update. It takes a long time to roll out a new service due to problems
such as insufficient API integration and high customization costs. Such a
service rollout speed cannot support flexible service scenario changes. AOC
accelerates service rollout and provides on-demand service customization
capabilities, enabling enterprises to quickly launch 5G and cloud applications
to meet ever-changing requirements.
● Open programmability: AOC provides end-to-end network open
programmability capabilities to enable DevOps and digital transformation for
enterprises.
● Full-lifecycle network automation: AOC provides cross-device network
automation from the service perspective, enabling automated deployment.
This simplifies network operations and achieves quick and reliable execution
of service change requests.
● Network configuration consistency assurance: AOC provides device- and
service-level configuration consistency assurance capabilities to reduce the

iMaster NCE-IP
Mean Time to Repair (MTTR) and quickly detect and rectify faults for
enterprises.
● Network infrastructure as code: AOC supports code-based automated
network management as well as template, service package, and parameter
management, minimizing errors caused by manual operations.
● Low-code platform: AOC supports YANG models, EasyMap algorithm, and
codeless driver generation, maximizing operational efficiency.
7.6.2.3 Specifications and Restrictions

This section describes the specifications and restrictions that you need to
understand before using service programming.
Specifications
Table 7-59 Package management specifications
Activation package A maximum of 800 activation packages can be loaded,

management regardless of the package types. In practice, the number
of the activation packages depends on configurations.
Table 7-60 Transaction concurrency
Maximum number of 32
concurrent
transactions on a
single node
Table 7-61 Configuration consistency test specifications
Device
Interconnect with devices through the specified protocol and collect data in the
specified mode (test object: a single device; test feature: static route).
Time of southbound It takes 10 seconds to configure 1000 leaf nodes, and

difference discovery the time increases by 1 second for each additional 1000
(SFTP) leaf nodes.
Southbound It takes 10 seconds to configure 1000 leaf nodes, and

synchronization time the time increases by 2 seconds for each additional
(SFTP) 1000 leaf nodes.

iMaster NCE-IP

reconciliation time the time increases by 25 seconds for each additional
(SFTP) 1000 leaf nodes.

difference discovery the time increases by 2 seconds for each additional
time (NETCONF) 1000 leaf nodes.

synchronization time the time increases by 10 seconds for each additional
(NETCONF) 1000 leaf nodes.

reconciliation time the time increases by 15 seconds for each additional
(NETCONF) 1000 leaf nodes.
Service
View the service instance list when 1000 leaf nodes are configured for a single
southbound device.
Difference discovery 30 seconds per southbound device

time (NETCONF)
Deep difference 35 seconds per southbound device

discovery time
(NETCONF)
NOTE
Each controller can perform difference discovery, synchronization, and reconciliation on a
maximum of 20 devices at the same time.
Table 7-62 SSH server specifications

Maximum number of 100 TCP connections per server

connections
Maximum connection 5 TCP connections per second

rate
Table 7-63 NETCONF client specifications

Timeout period of The default timeout period is 45 seconds, which is

packet sending configurable.

iMaster NCE-IP
Call home device go- 40 devices per second per node. That is, each node can
online rate establish TCP connections with a maximum of 40
devices per second.
Maximum number of 15,000 connections per node. That is, each node can
proactive go-online accept TCP connection requests from a maximum of
connections 15,000 devices at the same time.
Maximum number of 30,000 connections per node. That is, each node can
call home device accept TCP connection requests from a maximum of
connections 30,000 devices at the same time.
Table 7-64 Datastore read and write specifications

Read and write Read: 250 list instances per second

performance without Create: 650 list instances per second
data sources
Replace: 650 list instances per second
Merge: 650 list instances per second
Delete: 5000 list instances per second
Read and write Read: 100 list instances per second

performance with data Create: 50 list instances per second
sources
Replace: 50 list instances per second
Merge: 50 list instances per second
Delete: 30 list instances per second
Restrictions
The SSP and SND packages released with this version are intended for testing
purposes only. Contact Huawei if you want to use them for production purposes.
An explicit range of device versions has been declared for the SND packages
released with this version. Due to possible incompatible YANG model changes
between device versions, do not use the SND packages beyond the declared
version range. If you need to customize SND packages for a device version, contact
Huawei R&D engineers.
7.7 Northbound Integration
7.7.1 Open API & Tool

API Catalog displays the northbound APIs provided by NCE, making it convenient
to find and use APIs during OSS integration.

iMaster NCE-IP
● Quick API search: Compliant with the open API standards defined by TMF, API
Catalog categorizes the northbound APIs of NCE and allows users to search
for APIs by catalog or name (keyword).
● API details: To help users quickly understand APIs, API Catalog provides
details about each API, including their functions and request parameters.
● Try it out: The Try it out function in API Catalog allows users to try out the
entire process, including calling APIs and receiving responses.

iMaster NCE-IP
Product Description (x86,enterprise) 8 Usage Scenarios
8 Usage Scenarios
8.1 CloudWAN
8.1 CloudWAN
Background and Challenges
A wide area network (WAN) is an interconnection network used for long-distance
communication between enterprises or organizations. With coverage ranging from
tens to thousands of kilometers, WANs enable information and resource sharing
over vast distances. Typically, enterprises lease links from carriers or build their
own links for long-distance communication. WANs connect enterprise factories,
branches, cloud platforms, intelligent products, and users. At the same time, they
break data silos, support quick implementation of innovative services and
applications, and enable efficient collaboration between various fields. While
enterprise digital transformation improves production efficiency, it also brings the
following challenges to WANs:
● Segment-based O&M of traditional WANs results in inefficient network
provisioning and non-agile enterprise cloudification.
Traditional enterprise applications are mostly deployed on local servers in the
headquarters. In this case, WANs only need to implement communication
between branches and the headquarters, typically adopting the point-to-point
(P2P) connection mode. As enterprise applications are deployed on clouds,
WANs are used to connect branches and the headquarters to these clouds in
point-to-multipoint (P2MP) or multipoint-to-multipoint (MP2MP) mode.
Traditional WANs typically use MPLS technology, and their maintenance is
conducted by multiple departments. Service deployment is based on manual
segment-by-segment configuration, which is time-consuming and cannot
match the cloud deployment speed.
Due to the lack of a unified WAN backbone network, an enterprise needs to
lease multiple site-to-cloud private lines based on the deployment locations
of different clouds. Building a new cloud data center means that all network
and cloud connections need to be established from scratch. This results in
complex connections, difficulty in segment-based deployment, and long time
for service monetization.

iMaster NCE-IP
● The adoption of IP on production networks makes it difficult to guarantee

network SLAs.
As core production systems are migrated to the cloud, carrying various
services on one IP WAN will become an inevitable trend for enterprise digital
transformation, especially when we factor in construction cost, O&M, and
rapid service expansion. Different services have distinct requirements on
network latency and bandwidth. How to carry various services on a single
network while meeting their SLA requirements is also a key challenge facing
WANs.
● Cloud and network resource utilizations are unbalanced, and capacity
expansion is mostly carried out passively.
Traditional WANs forward packets through the shortest path, leading to an
imbalance between cloud and network resource utilizations. Specifically, on
some nodes, resources are exhausted, but on others, most or even all of
resources are left idle. As the overall network traffic increases year by year,
enterprises passively invest in capacity expansion of some nodes or links,
leading to waste. Furthermore, cloud data center construction leads to a
sharp increase in traffic between enterprises and cloud data centers and
between cloud data centers, exacerbating this problem.
● In the cloud era, the number of network connections increases by hundreds of
times. Complex connections create difficulties in O&M.
Traditional O&M lacks E2E automation capabilities and instead responds
passively to customer complaints. Manual fault locating, segment-by-segment
troubleshooting, and path adjustment are time-consuming and labor-
intensive, resulting in low O&M efficiency. Massive terminal connections make
services more diversified and network connections more complex, posing
severe challenges to the traditional O&M mode. How to improve O&M
efficiency and implement intelligent O&M is a must for WANs.
Solution
The CloudWAN solution is a next-generation agile, intelligent, and secure WAN
solution developed based on an intelligent foundation — the IPv6 Enhanced
digital infrastructure. The CloudWAN solution uses key technologies such as SRv6,
network slicing, intelligent cloud-map algorithm, and In-situ Flow Information
Telemetry (IFIT) to meet the requirements of enterprise cloudification and IP-
based production networks. It helps build future-oriented intelligent WANs,
accelerating enterprise digital transformation. This solution solves the following
problems faced by enterprise WANs:
● Non-agile cloud connection

The CloudWAN solution builds a unified WAN cloud backbone network to
which various cloud resources are preconnected through cloud PEs and
enterprise campus egresses are preconnected through network PEs, that is,
cloud-network connections are predeployed. As part of this solution, iMaster
NCE-IP, under the support of the seamless cross-domain technology SRv6,
takes just minutes to generate cloud paths with different QoS, latency, and
bandwidth based on customers' business requirements. That, coupled with
self-services such as cloud path and SLA assurance, truly achieves agile cloud
connection and multi-cloud access upon network access.
● Deterministic SLAs non-guaranteed

iMaster NCE-IP
The CloudWAN solution uses the industry's first hierarchical slicing technology
to implement one fiber for multiple purposes. To prevent mutual impact,
different services are carried on different slices that are hard isolated from
each other. This solution not only implements converged transport on a single
network, but also meets the SLA requirements of different services. As such,
the solution eliminates the need to construct multiple networks, thereby
significantly reducing costs.
● Heavy investment in passive capacity expansion
In the CloudWAN solution, network-wide traffic is reported to iMaster NCE-IP
in a unified manner. iMaster NCE-IP uses algorithms, such as the intelligent
cloud-map algorithm, to perform cloud-network optimization based on both
network factors (bandwidth and latency) and cloud factors (cost and
computing power), maximizing the utilization of cloud-network resources.
● Low O&M efficiency
The CloudWAN solution uses IFIT to collect KPIs such as network latency and
packet loss rate in real time. The KPIs are then reported to iMaster NCE-IP,
making service experience visible and manageable. Huawei's proprietary
knowledge graph algorithm is used to quickly locate the root causes of faults
and automatically rectify faults.
Solution Scenarios
Huawei's CloudWAN solution deploys key technologies (such as SRv6, network
slicing, intelligent cloud-map algorithm, and IFIT) on the network, and uses
iMaster NCE-IP for unified control to implement automatic deployment of
enterprise cloud services, SLA assurance for key services, intelligent optimization of
network traffic, service visualization, fast O&M, and more. The CloudWAN solution
is mainly applied on the backbone networks between enterprise campuses and
clouds, between enterprise campuses, and between clouds. Its applications are
divided into three scenarios:
● Scenario 1: enterprise services agilely carried on the cloud
● Scenario 2: industrial interconnection between enterprise campuses
● Scenario 3: inter-cloud interconnection

iMaster NCE-IP
Key Features
The CloudWAN solution has the following key features:
● SRv6, enabling network automation
Based on native IPv6, SRv6 integrates the network programming capability of
segment routing. SRv6-TE Policy leverages the source routing mechanism of
segment routing to guide packet forwarding based on an ordered list of
segments encapsulated by the headend. Thanks to iMaster NCE-IP and SRv6-
TE Policy, provisioning end-to-end services in enterprise cloudification
scenarios does not require any manual intervention. Consequently, the
configuration process can be based entirely on the cloud and SDN. According
to enterprises' business requirements, iMaster NCE-IP can generate cloud
paths with different QoS, latency, and bandwidth in mere minutes, thereby
implementing quick deployment of cloud services.
● Network slicing, providing deterministic SLA assurance
Using hierarchical slicing, the CloudWAN solution enables multiple logical
networks to be created over one physical network for multi-service transport
and deterministic SLA assurance. Network SLAs mainly involve latency and
bandwidth, which network slicing can control and guarantee, respectively, to
safeguard mission-critical services.
● Intelligent cloud-map algorithm, improving resource utilization
The intelligent cloud-map algorithm is a vital part of the CloudWAN solution.
In this solution, iMaster NCE-IP is used to collect network-wide information
(such as path latency and bandwidth), compute E2E optimal forwarding paths
based on the collected information, and steer traffic to these paths. In

iMaster NCE-IP
addition to network factors such as bandwidth and latency, the intelligent

cloud-map algorithm considers cloud pool load factors. Based on SRv6 and
SDN technologies, the algorithm can quickly match and schedule services to
the most appropriate cloud pool. The intelligent cloud-map algorithm
implements cloud-network load balancing and efficient resource utilization,
helping enterprises effectively reduce TCO.
● IFIT, building a closed-loop intelligent O&M system
IFIT directly measures network performance indicators such as the latency,
packet loss rate, and jitter by adding IFIT headers to real service packets. It
uses telemetry to report measurement data in real time to iMaster NCE-IP,
which then displays network performance indicators through its GUI. After
IFIT is deployed on a network, the actual forwarding path of packets can be
restored. Thanks to telemetry enabling the collection of data within seconds,
network SLAs can be visualized in real time and faults can be quickly
demarcated and automatically rectified, building a closed-loop intelligent
O&M system.

iMaster NCE-IP
Product Description (x86,enterprise) 9 High Availability
9 High Availability
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,
which recover the system from faults to minimize the damage to the system.
Figure 9-1 shows the NCE availability protection solutions.
Figure 9-1 Availability protection solutions (on-premises VM deployment on

TaiShan servers is used as an example)
9.1 Local HA
In the on-premises scenario, NCE provides detailed HA protection solutions for the
hardware, virtualization layer, and application layer of a single site. These
solutions can prevent unknown risks caused by hardware or software faults and
ensure secure and stable running of NCE.
9.2 Disaster Recovery Solutions
NCE provides disaster recovery solutions to prevent unknown risks on the entire
system and ensure secure and stable running of NCE.

iMaster NCE-IP
9.1 Local HA
In the on-premises scenario, NCE provides detailed HA protection solutions for the
hardware, virtualization layer, and application layer of a single site. These
solutions can prevent unknown risks caused by hardware or software faults and
ensure secure and stable running of NCE.
Hardware HA
If hardware under redundancy protection becomes faulty, services are
automatically switched to a normal counterpart to ensure non-stop work of the
NCE OS and applications.
Table 9-1 HA protection solutions for hardware (x86 servers delivered with the
version)
Protection Protection Solution
Type
Hardware ● Server: Power modules and fans work in redundancy mode,

redundancy and NICs work in 1+1 bond protection mode.
● Switch: redundancy protection. Configure two switches that
protect each other to connect the server to the customer's
network.
Hardware redundancy provides instant protection switchover
without impact on the application layer.

iMaster NCE-IP

Type
RAID Physical machine (using HDDs)

● 2-disk server: Configure disk 0 and disk 1 as RAID 1.
● 8-disk server: Configure disk 0 and disk 1 as RAID 1 to store
OS software and data. Configure disk 2, disk 3, disk 4, and
disk 5 as RAID 10 to store service data and software.
Configure disk 6 as RAID 0, which is reserved. Configure
disk 7 as RAID 0, which is reserved.
● 12-disk server: Configure disk 0 and disk 1 as RAID 1 to
store OS software and data. Configure disk 2, disk 3, disk 4,
disk 5, disk 6, disk 7, disk 8, and disk 9 as RAID 10 to store
service data and software. Configure disk 10 as RAID 0,
which is reserved. Configure disk 11 as RAID 0, which is
reserved.
Physical machine (using SSDs)
● 2-disk server: Configure disk 0 and disk 1 as RAID 1.
● 6-disk server: Configure disk 0 and disk 1 as RAID 1 to store
OS software and data. Configure disk 2 and disk 3 as RAID
1 to store service data and software. Configure disk 4 as
RAID 0, which is reserved. Configure disk 5 as RAID 0, which
is reserved.
● 10-disk server: Configure disk 0 and disk 1 as RAID 1 to
store OS software and data. Configure disk 2, disk 3, disk 4,
disk 5, disk 6, and disk 7 as RAID 10 to store service data
and software. Configure disk 8 as RAID 0, which is reserved.
Configure disk 9 as RAID 0, which is reserved.
VM (using HDDs)
● Each server has 12 hard disks, which are configured as RAID
10. If NCE Analyzer is deployed, the hard disk used by each
Network Data Processor node is configured as RAID 0 and
other hard disks are configured as RAID 10.
VM (using SSDs)
● Each server has 10 hard disks, which are configured as RAID
50.

iMaster NCE-IP
Table 9-2 HA protection solutions for hardware (E9000 servers)

Type
Hardware ● E9000 chassis: The management modules, power modules,

redundancy and switch boards work in 1+1 redundancy mode, and the
fans work in redundancy mode.
● Disk array: The disk array controllers, power modules, and
SmartIO cards work in 1+1 redundancy mode.
Hardware redundancy provides instant protection switchover
without impact on the application layer.
RAID ● E9000: Configure two hard disks of each blade as RAID 1.

● Disk array: A total of 25 hard disks are configured as a disk
domain that adopts hot backup policies. In addition, a
storage pool is configured as RAID 10. If an extended disk
enclosure is deployed, all disks in the enclosure are
configured as RAID 6/10.
MZ312 Return probability: Extremely low

network card ● Return probability in the early stage (0–6 months): 0.033%
availability
● Return probability in the middle stage (7–18 months):
0.011%
● Return probability in the late stage (18 months or above):
0.000%
NOTE
● Mezz1: connected to the storage. If Mezz1 is faulty, the E9000
cannot connect to the disk array.
● Mezz2: connected to services. If Mezz2 is faulty, the E9000
cannot connect to the service network.

iMaster NCE-IP
Application Layer HA
Table 9-3 HA protection solutions for the application layer
Protectio Protection Solution Protection Capability

n Type
App Automatic switchover of application Switchover duration ≤ 3

service services in the NCE Manager+Controller minutes
protection +Analyzer scenario:
● If virtual nodes are deployed in
primary/secondary mode, services are
generally running only on primary
nodes. When the service processes on
the primary node are faulty, NCE
automatically starts the services on
the secondary node and the service
instances on the secondary node are
started to provide services.
● If virtual nodes are deployed in cluster
mode, all nodes are running at the
same time. If one node fails, other
nodes share the load capability of the
faulty node to provide services for
external systems in a balanced
manner.
Process restart: Process status is Process restart duration

monitored in real time. If a process is ≤ 5 minutes
stopped or faulty, NCE restarts the
process. If the restart fails for 10
consecutive times, an alarm is generated,
requiring users to handle the failure
manually.
Data Backup and restoration: The backup and Backup and restoration
protection restoration function is provided for data. duration ≤ 60 minutes
Data can be backed up periodically or
before major changes. If NCE data is
abnormal, users can use the backup files
to quickly restore the data to the normal
state.
Automatic database switchover: ● RPO = 1 minute

Database nodes are deployed in master/ ● RTO= 1 minute
slave mode. In normal situations, the
database on the master node is readable
and writable, while the database on the
slave node is read-only. If a service
process on the master node fails, NCE
automatically switches to the database
on the slave node to provide services.
The switchover does not affect services.

iMaster NCE-IP
Protectio Protection Solution Protection Capability

n Type
Recovery point objective (RPO): a service switchover policy that minimizes data
loss during DR switchover. It takes the data recovery point as the objective to
ensure that the data used for DR switchover is the latest backup data.
Recovery time objective (RTO): The maximum acceptable amount of time for
restoring a network or application and regaining access to data after an
unexpected interruption.
9.2 Disaster Recovery Solutions

NCE provides disaster recovery solutions to prevent unknown risks on the entire
system and ensure secure and stable running of NCE.
Table 9-4 HA solutions at the DR system
Protectio Description Protection Capability

n
Solution
Active/ NCE is deployed on primary and ● RPO = 1 minute

standby secondary sites. Data in each database is ● RTO = 15 minutes
switchove synchronized from the primary site to the (The RTO of the
r secondary site based on the NCE-IP and NCE-FAN
synchronization policy. If the primary site alarm monitoring
fails, users can immediately manually service is 1 minute.)
start the secondary site or the arbitration
service automatically starts the
secondary site to quickly restore NCE
services.
Active/ The DR system uses a heartbeat link to -

standby monitor the association between the
monitorin primary and secondary sites and a
g replication link to synchronize data
between the two sites. If the heartbeat
and replication links between the
primary and secondary sites become
abnormal, NCE will report an alarm to
inform users of manual troubleshooting
or automatic troubleshooting by the
arbitration service.
Recovery point objective (RPO): a service switchover policy that minimizes data
loss during DR switchover. It takes the data recovery point as the objective to
ensure that the data used for the service switchover is the latest backup data.
Recovery time objective (RTO): the maximum acceptable amount of time for
restoring a network or application and regaining access to data after an
unplanned disruption.

iMaster NCE-IP
Table 9-5 DR switchover solution of NCE (distributed Manager+Controller

+Analyzer, centralized Manager+Controller+Analyzer, and compact Manager
+Controller+Analyzer scenarios)
DR Solution Scenario
Automatic This solution applies to NCE-IP, NCE-T, and cross-domain

switchover (with NE scenarios. There are two equipment rooms, and the
arbitration, originally status of the primary site and secondary site are
with non-third-party monitored by southbound arbitration NEs in real time. If
arbitration) a site- or application-level fault occurs, a switchover
must be quickly carried out to restore services and avoid
the dual-active exception.
Automatic There are three equipment rooms, and the status of the
switchover (with primary site and secondary site needs to be monitored
third-party in real time. If a site- or application-level fault occurs, a
arbitration) switchover must be quickly carried out to restore
services.
Manual switchover There are two equipment rooms, and the status of the
primary site and secondary site is manually monitored. If
a site-level fault occurs, manual operations are
performed as the system is not sensitive to fault
recovery time.
Table 9-6 Remote DR switchover solution of NCE (Manager scenario)

Automatic This solution applies to NCE-IP, NCE-T, and cross-domain

switchover (with NE scenarios. There are two equipment rooms, and the
arbitration, originally status of the primary site and secondary site are
with non-third-party monitored by southbound arbitration NEs in real time. If
arbitration) a site- or application-level fault occurs, a switchover
must be quickly carried out to restore services and avoid
the dual-active exception.
Automatic There are three equipment rooms, and the status of the
switchover (with primary site and secondary site need to be monitored in
third-party real time. If a site- or application-level fault occurs, a
arbitration) switchover must be quickly carried out to restore
services.
Automatic There are two equipment rooms, and the status of the
switchover (without primary site and secondary site needs to be monitored
arbitration) in real time. If a site- or application-level fault occurs, a
switchover must be quickly carried out to restore
services, and services must be resistant against the
exception that both sites are active.

iMaster NCE-IP
Manual switchover There are two equipment rooms, and the status of the
primary site and secondary site is manually monitored.
If a site-level fault occurs, manual operations are
performed as the system is not sensitive to fault
recovery time.
NOTE
In Manager, centralized Manager+Controller+Analyzer, and distributed Manager+Controller

+Analyzer IP address convergence scenarios, if the northbound networks of the primary site
and secondary site of the DR system are on the same network segment, you can configure
a floating IP address for northbound interconnection for the primary site and secondary
site. This IP address is used to automatically interconnect with the OSS after the primary
site and secondary site are switched over.
In other scenarios, the floating IP address for interconnection between sites cannot be
configured.
Manual Switchover
Solution Introduction
The primary site and secondary site communicate with each other through
heartbeat links and detect the status of the peer site in real time. The active site
synchronizes product data to the standby site in real time through the data
replication link to ensure product data consistency between the primary site and
secondary site.
When a disaster occurs at the primary site, perform the takeover operation at the
secondary site. The secondary site becomes the active site and provides services
externally. The primary site becomes the standby 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.
● The primary site is faulty, causing some key nodes to be damaged and unable
to provide services. For example, database node (DB) corruption, platform
service node (Common_Service) corruption, management domain service
node (NMS) corruption, or control domain service node (Controller or
TController) corruption.
Solution Schematic Diagram

iMaster NCE-IP
Figure 9-2 Working principle of manual switchover in the DR system
The DR network can reuse the original network of NCE to reduce the network
configuration of site A (primary site) and site B (secondary site).
Table 9-7 DR network configuration

DR Link IP Address Network Plane
Data replication link Replication IP DR network

address NOTE
The DR network can reuse the inter-
node communication network or
northbound network, or use an
independent network.
Heartbeat link Heartbeat IP DR network. The heartbeat IP

address address and replication IP address
must be on the same network
plane.
Automatic Switchover (No Arbitration)

Solution introduction:
The primary and secondary sites use heartbeat links to detect the status of the
peer site 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 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 the primary site switches to the standby
state after fault rectification.
If only the heartbeat link between the primary and secondary sites is interrupted
and the heartbeat interruption duration exceeds the configured threshold (5
minutes by default), service takeover occurs, causing dual active and generating
dual active alarms. When the heartbeat recovers, the dual active state changes to
active/standby 3 minutes later.
● If the heartbeat recovers within two hours, the active site before the
heartbeat link is interrupted remains active, and the other site switches to

iMaster NCE-IP
standby. After the heartbeat link is normal and the active/standby state is
stable, the system automatically synchronizes full data of the product at the
active site to the standby site to restore the product. In addition, the product
data at the primary site is consistent with that at the secondary site.
● If the heartbeat recovers two hours later, considering both sites may have
been operated, the system does not automatically change the dual active
state to active/standby. Instead, users determine the active and standby sites
based on site requirements and perform manual switchover to prevent data
loss.
Trigger conditions of automatic switchover:
site, and the fault is not rectified within the specified time.
● In NCE Manager and other specific scenarios:
– If local protection is not configured for microservices, when any of the
default key microservices of the system is faulty, an automatic switchover
is triggered to ensure proper service running. For the key microservice list,
see the Pivotal Microservice column in the Processes and Services sheet
of NCE Process and Service List.
– If local protection is not configured for service nodes, when a southbound
or northbound network interface on a service node is faulty, which causes
the southbound or northbound network to be faulty, an automatic
switchover is triggered.
– If local protection is not configured for databases, when a default key
relational or Redis database instance on a service node is faulty, an
automatic switchover is triggered.

iMaster NCE-IP
NOTE
● Perform the following operations to check whether a database instance is a

key relational database instance:
1. Log in to the management plane.
2. On the management plane, choose Maintenance > Operation and
Maintenance Management > Panoramic Monitoring from the main
menu.
3. In the navigation pane, choose Middleware Monitoring.
4. In the upper left corner of the Middleware Monitoring page, select a
product or NCE-OMP.
5. On the Relational Databases tab page, click the name of the database
instance to be checked.
6. On the Database Instance Diagnosis page, scroll down the page to the
Relational Database tab page, and obtain values in the Service Name
column in the Database Details area. If any service is a key microservice,
the database instance is a key relational database instance. If all services
are non-key microservices, the database instance is a non-key relational
database instance. For the key microservice list, see the Pivotal
Microservice column in the Processes and Services sheet of NCE Process
and Service List.
● In the current scenarios, all Redis database instances are non-key Redis
database instances by default.
● The priorities of triggering an automatic switchover are as follows: Key
database instances are faulty > Southbound or northbound network is faulty
> Key microservices are faulty. If a database instance at the secondary site is
faulty, an automatic switchover is not triggered even if a key microservice at
the primary site is faulty.
Solution schematic diagram:
Figure 9-3 Working principle of automatic switchover in the DR system (without

arbitration)
The DR network can reuse the existing network of NCE to reduce the network

iMaster NCE-IP

Data replication link Replication IP DR network.

address NOTE
northbound network or use an

plane.
Automatic Switchover (with Third-Party Site Arbitration)

Solution introduction:
The arbitration service periodically checks the connectivity between the primary,
secondary, and third-party sites, and shares the check results through the
arbitration node communication link. If the arbitration heartbeat is abnormal due
to a network exception 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 site and secondary site.
Trigger conditions of automatic switchover:
● The heartbeat link between the primary and secondary sites is interrupted,
and the communication link between the arbitration nodes on the active and
third-party sites is interrupted.
● In the NCE Manager, centralized Manager+Controller+Analyzer, or compact
Manager+Controller+Analyzer scenario:
– If local protection is not configured for microservices, when any of the
is triggered to ensure proper service running. For the key microservice list,
see the Pivotal Microservice column in the Processes and Services sheet
of NCE Process and Service List.
– If local protection is not configured for service nodes, when a southbound
– If local protection is not configured for databases, when a default key
automatic switchover is triggered.

iMaster NCE-IP
NOTE

menu.
product or NCE-OMP.
and Service List.
● In the NCE distributed Manager+Controller+Analyzer scenario:
– By default, microservices are deployed in active/standby or cluster mode,
and local protection is configured. If a default key microservice in the
system is faulty, a local active/standby switchover or cluster isolation is
preferentially performed. If the fault persists, an automatic switchover is
triggered to ensure normal service running.
For the key microservice list, see the Pivotal Microservice column in the
Processes and Services sheet of NCE Process and Service List.
– Service nodes are deployed in active/standby or cluster mode, and local
protection is configured. When the southbound or northbound network is
faulty due to a network interface fault on a group of service nodes of the
same type, for example, when the northbound network of the
Common_Service cluster is faulty due to a northbound network interface
fault on the Common_Service_01, Common_Service_02, and
Common_Service_03 nodes, an automatic switchover is triggered.
– Databases are deployed in active/standby mode, and local protection is
configured. When a default key relational or Redis database instance on a
service node is faulty, a local active/standby switchover is preferentially
performed. If the fault persists, an automatic switchover is triggered.

iMaster NCE-IP
NOTE

menu.
product or NCE-OMP.
and Service List.
Arbitration service deployment:
● The CPU architectures of the primary site, secondary site, and third-party site
must be the same. For example, if the primary and secondary sites use Arm
servers, the third-party site must use Arm servers.
NOTE
If the CPU architectures of the primary and secondary sites are different, contact
Huawei R&D engineers to determine whether the DR system can be created.
● If the third-party site is provided by the customer, it must be exclusively used
for the arbitration service but cannot be shared with other services.
● One NCE DR system corresponds to one arbitration service at the third-party
site. If multiple NCE DR systems exist on the live network, the corresponding
arbitration services can be deployed at the same third-party site to reduce
costs. A maximum of 10 arbitration services, for different software versions,
can be co-deployed at a third-party site. If the third-party site is faulty, all
arbitration services at it will fail to run and must be reinstalled.
NOTE
The OS of a third-party site can trace only one external clock source. When multiple
arbitration services are deployed at a third-party site, the clocks of their corresponding
DR systems must be the same to ensure that the time of the third-party site is
consistent with that of all the primary and secondary sites.
● In the NCE distributed Manager+Controller+Analyzer scenario, the arbitration
service is deployed in 2+2+1 mode on five nodes of the three sites.

iMaster NCE-IP
– Two arbitration nodes (Common_Service) are deployed at each of site A

(the primary site) and site B (the secondary site) for mutual protection.
One arbitration node is deployed at the third-party site.
– ArbiterRaft is deployed on the five arbitration nodes to form an
ArbiterRaft cluster. Monitor is deployed on the four arbitration nodes at
site A (the primary site) and site B (the secondary site) to monitor the
network connectivity between the two sites and save the results in the
ArbiterRaft cluster.
NOTE
The arbitration service consists of the ArbiterRaft and Monitor processes.

● ArbiterRaft is a self-developed distributed key-value storage system. It
provides data consistency read and write capabilities when no more than half
of the nodes are faulty. In the NCE DR system with third-party arbitration, it
stores key switchover decision-making data and configuration parameters to
ensure automatic application-level DR switchover.
● Monitor checks the network connectivity between sites and saves the check
results in the ArbiterRaft cluster.
Figure 9-4 Five-node DR system
● In the NCE Manager, centralized Manager+Controller+Analyzer, and compact

Manager+Controller+Analyzer scenarios, the arbitration services are deployed
in 1+1+1 mode on three nodes of the three sites.

iMaster NCE-IP
– One arbitration node is deployed at each of site A (the primary site) and
site B (the secondary site) for mutual protection. In the compact
Manager+Controller+Analyzer scenario, Common_Service serves as the
arbitration node. In the Manager and centralized Manager+Controller
+Analyzer scenarios, NMS_Server serves as the arbitration node. One
arbitration node is deployed at the third-party site.
– ArbiterRaft is deployed on the three arbitration nodes to form an
ArbiterRaft cluster. Monitor is deployed on the two arbitration nodes at
site A (the primary site) and site B (the secondary site) to monitor the
network connectivity between the two sites and save the results in the
ArbiterRaft cluster.
Figure 9-5 Three-node DR system
The DR network can reuse the existing network of NCE to reduce the network
Data replication Replication IP DR network.

link address NOTE
The DR network can reuse the inter-node
communication network or northbound
network or use an independent network.
Heartbeat link Heartbeat IP DR network. The heartbeat IP address

address and replication IP address must be on the
same network plane.

iMaster NCE-IP
Arbitration Arbitration node DR network.

node communication NOTE
communication IP address ● The DR network can reuse the inter-node
link communication network or northbound
network or use an independent network.
● It is not recommended that the arbitration
node communication link reuse the
northbound network. If the arbitration
node communication link reuses the
northbound network and both of them
break down, the arbitration service cannot
run properly, causing an exception during
automatic switchover. In this case, the NCE
management plane that is connected
through the northbound network is
inaccessible and manual switchover cannot
be performed. As a result, the DR system
cannot be restored in time.
Automatic Switchover (with NE Arbitration)

Solution Introduction
To prevent the dual-active state when the network between sites is abnormal, the
DR service periodically initiates a request for querying the southbound arbitration
NE status and determines the status of the primary site and secondary site based
on the query results. When the DR heartbeat is abnormal due to a network
exception or site fault and the connection between the active site and southbound
arbitration NE is abnormal, the primary site and secondary site are automatically
switched over.
CAUTION
● NAT is not supported between NCE and the southbound arbitration NE.
● The number of arbitration NEs must be an odd number and ranges from 3 to
11.
● To ensure system reliability:
● Separate the southbound network from the DR network to reduce the
probability that both networks are faulty at the same time.
● Select arbitration NEs from different subnets to reduce the probability of
multiple points of failure during NE upgrade.
Automatic Switchover Trigger Conditions

● The heartbeat link between the primary site and secondary site is interrupted,
and the connection between the active site and southbound arbitration NE is
abnormal.

iMaster NCE-IP
● In Manager, centralized Manager+Controller+Analyzer, and compact Manager

+Controller+Analyzer scenarios of NCE:
– If no local protection is configured for microservices, when any of the
is triggered in the DR system to ensure that services run properly. For
details about the key microservice list, see the Pivotal Microservice
column in the Processes and Services sheet of NCE Process and Service
List.
NOTE
You can contact Huawei technical support to obtain the required NCE Process
and Service List. Huawei technical support can obtain the NCE Process and
Service List as follows:
● For enterprises, log in to https://support.huawei.com/enterprise. Search for
"iMaster NCE-domain" on the homepage. On the iMaster NCE-domain page,
search for "Common Documents". Process and Service List is contained in
Common Documents.
The process and service list lists all key microservices of iMaster NCE-domain. The
listed key microservices may be different from those on the live network based
on the deployment scenario (such as Manager and distributed Manager
+Controller+Analyzer).
– If no local protection is configured for service nodes, when a southbound
switchover is triggered in the DR system.
– If no local protection is configured for databases, when a default key
automatic switchover is triggered in the DR system.

iMaster NCE-IP
NOTE

menu.
4. In the upper left corner of the Middleware Monitoring page, select the
product or NCE-OMP.
database instance. For details about the key microservice list, see the
Pivotal Microservice column in the Processes and Services sheet of NCE
Process and Service List.
● In the current scenario, all Redis database instances are non-key Redis
> Key microservices are faulty. If at least one database instance at the
secondary site is faulty, an automatic switchover is not triggered even if a key
microservice at the primary site is faulty.
● In the NCE distributed Manager+Controller+Analyzer scenario:
– By default, microservices are deployed in active/standby or cluster mode,
and local protection is configured. If a default key microservice in the
system is faulty, a local active/standby switchover or cluster isolation is
preferentially performed. If the key microservice is still faulty after the
local active/standby switchover or cluster isolation, the DR system
triggers an automatic switchover to ensure normal service running.
For details about the key microservice list, see the Pivotal Microservice
column in the Processes and Services sheet of NCE Process and Service
List.
NOTE
● You can contact Huawei technical support to obtain the required NCE Process
and Service List. Huawei technical support can obtain the NCE Process and
Service List as follows:
● For enterprises, log in to https://support.huawei.com/enterprise.
Search for iMaster NCE-domain on the homepage. On the iMaster
NCE-domain page, search for "Common Documents". Process and
Service List is contained in Common Documents.
● The process and service list lists all key microservices of iMaster NCE-domain.
The listed key microservices may be different from those on the live network
based on the deployment scenario (such as Manager and distributed
Manager+Controller+Analyzer).
– Service nodes are deployed in active/standby or cluster mode, and local
protection is configured. When the southbound or northbound network is
faulty due to a network interface fault on a group of service nodes of the

iMaster NCE-IP
same type, the system triggers an automatic switchover. For example, if

the northbound network of the Common_Service cluster is faulty due to a
northbound network interface fault on the Common_Service_01,
Common_Service_02, and Common_Service_03 nodes, an automatic
– Databases are deployed in active/standby mode, and local protection is
configured. When a default key relational or Redis database instance on
the service node is faulty, a local active/standby switchover is
preferentially performed. If the key database instance is still faulty after
the local active/standby switchover, the DR system triggers an automatic
switchover.
NOTE

menu.
4. In the upper left corner of the Middleware Monitoring page, select the
product or NCE-OMP.
database instance. For details about the key microservice list, see the
Pivotal Microservice column in the Processes and Services sheet of NCE
Process and Service List.
● In the current scenario, all Redis database instances are non-key Redis
> Key microservices are faulty. If at least one database instance at the
secondary site is faulty, an automatic switchover is not triggered even if a key
microservice at the primary site is faulty.
Solution Schematic Diagram

iMaster NCE-IP
Figure 9-6 Working principle of automatic switchover (with NE arbitration) in the

DR system
It is recommended that the DR network reuse the original network of NCE to

reduce the network configuration of site A (primary site) and site B (secondary
site).

Data replication link Replication IP DR network

address NOTE
northbound network, or use an
The DR network and southbound
network cannot be on the same
network plane.

plane.

iMaster NCE-IP
Product Description (x86,enterprise) 10 Security
10 Security
NCE uses the security architecture design that complies with industry standards
and practices to ensure system, network, and application security from multiple
layers.
10.1 Security Architecture
10.2 Security Functions
10.1 Security Architecture

NCE security architecture consists of the network layer, virtualization platform,
system layer, application layer, and secure O&M. Figure 10-1 shows the features
at each layer.
An in-depth defense system is established to provide powerful defense and build a
multi-layer and multi-dimension security protection network.
Network layer: Firewalls are used to isolate the external network from the system
to prevent attackers from accessing the system.
Virtualization platform: VMs and virtual networks are isolated to prevent viruses
from spreading in the system.
System layer: OS, database, and web container hardening helps eliminate or
reduce system security risks, and protect the system against damages from
attackers.
Application layer: Measures such as access control, secure transmission, secure
storage, and personal data protection are taken to reduce and control risks of
application and data loss or damage and prevent data leakage or theft.
Secure O&M: Identity and permission management, digital certificate
management, and key management are used to prevent spoofing attacks and
ensure data integrity and security.

iMaster NCE-IP
Figure 10-1 NCE security architecture
10.2 Security Functions

NCE security management aims to protect the confidentiality, integrity, and
availability of products, services, and user data carried by the products and
services and to ensure traceability and anti-attack capabilities in compliance with
applicable laws. NCE provides multiple security functions to achieve these goals.
CAUTION
● Designated computer principle: Using a designated server to install and run

NCE is recommended. This server must be separated from other office servers.
Using an NCE server to act as an email server or handle emails from a public
network is not recommended.
● Minimum installation principle: Installation of mandatory system applications
and auxiliary tools only on the server that runs NCE is recommended. Do not
install software downloaded from unauthorized websites, unofficial software
releases, software for testing, or any unnecessary applications of any kind.

iMaster NCE-IP
Table 10-1 NCE security functions

Security Description
Function
Area isolation ● Internal communication and external communication are

isolated and are controlled by different buses.
● The management plane and O&M plane are isolated, and
access control is implemented through different
interfaces and users.
NOTE
● The management plane refers to the plane that manages the
software and hardware resources of NCE.
● The O&M plane refers to the plane that uses NCE to perform
O&M operations on networks and devices.
User NCE can manage the roles, permissions, and access policies
management of system users.
Log NCE can manage operation logs, system logs, security logs,
management NE logs, and northbound logs and, dump Syslog logs.
Authentication ● The user passwords of the management plane and O&M

and plane are encrypted and stored using the PBKDF2
authorization irreversible algorithms.
management ● NCE can interconnect with authentication, authorization,
and accounting (AAA) systems such as the RADIUS or
LDAP system, and manage and authenticate O&M users
in a unified manner.
● NCE provides SSO authentication services based on CAS
and SAML and supports northbound interconnection and
integration authentication.
● Digital certificates are used for identity authentication.
Different certificates are used for northbound
communication, southbound communication, internal
communication, and interconnection with third-party
systems, and the interconnections are isolated from each
other. Certificate replacement and certificate lifecycle
management are supported.
Transmission Both internal and external transmission channels use

security security protocols such as HTTPS, TLS, SSH, SNMPv3, and
SFTP.
OS security SELinux is used to harden OS security, system service

restrictions are minimized, and insecure services are
disabled.
Database A dedicated low-permission system account is used to run

security the database, and database access permissions are
restricted.

iMaster NCE-IP
Security Description
Function
Sensitive data ● The PBKDF2 algorithm is used to securely store user

security passwords.
● The AES128 or AES256 algorithm is used to encrypted
and stored sensitive data.
● In SSH communication, the Diffie-Hellman or ECDH (≥
256 bits) algorithm is used to exchange keys, and
AES128-CTR, AES192-CTR, or AES256-CTR is used to
encrypt data.
Software NCE uses a software integrity protection solution equipped

integrity with CMS and OpenPGP. CMS is automatically called during
protection software package installation and upgrade. OpenPGP is used
when software package integrity needs to be manually
verified.
Communication ● NCE supports the web application firewall (WAF).

security ● NCE supports load balancing, traffic control, and access
control.
● NCE supports anti-DoS.
Network security Network isolation and firewall deployment are used to

ensure network security, as shown in Figure 10-2.

iMaster NCE-IP
Figure 10-2 NCE networking security (on-premises deployment where southbound

and northbound networks are isolated)
NOTE
If only NCE Manager is deployed, no disk array is involved.

iMaster NCE-IP
Product Description (x86,enterprise) 11 Personal Data and Privacy Protection
11 Personal Data and Privacy

Protection
Privacy is a fundamental human right recognized in the Universal Declaration of

Human Rights, the International Covenant on Civil and Political Rights and many
other international and regional laws and treaties. Privacy protection is a part of
Huawei's fulfillment of social responsibilities. Huawei fully understands the
importance of privacy protection and uses privacy protection as one of the
company's highest guidelines, and complies with applicable privacy protection and
personal data protection laws and regulations in all operating countries. Privacy
includes space, psychology, and personal data. Privacy protection in Huawei
products involves personal data.
11.1 Personal Data Description
11.2 Principles and Key Technologies
11.3 Lifecycle Management
11.4 Privacy Protection Roles
11.1 Personal Data Description

Definition of Subscriber Personal Data
Subscriber personal data is the information that can be used alone or together
with other information to identify a person. Personal data includes user names,
accounts, numbers of calling and called parties, communication records, CDRs,
communication time, and location data.
Declaration on Use of Subscriber Personal Data

NCE will inevitably use subscriber personal data, such as user names, IP addresses,
MAC addresses, email addresses, and passwords. You are obligated to obey the
applicable laws and privacy policies of your country or region and take sufficient
measures to fully protect the personal data.

iMaster NCE-IP
Subscriber Personal Data Used by NCE

NCE may collect or require subscribers to set certain subscriber personal data to
provide support for problem analysis. The data will not be transferred to third
parties. Different functions require different data that will be processed in
different ways. For details about the personal data scope and protection measures,
see NCE Personal Data Description.
NOTE
Methods to obtain NCE Personal Data Description:

For enterprises, log in to https://support.huawei.com/enterprise/en/index.html. On the
homepage, enter a product name iMaster NCE-domain (such as iMaster NCE-IP) in the
search box. On the Documentation tab page of the iMaster NCE-domain (such as iMaster
NCE-IP) page, click iMaster NCE-domain Product Documentation under Product
Documentation Set and find Personal Data Description under Security.
11.2 Principles and Key Technologies

Figure 11-1 Key technologies of NCE privacy protection
NCE complies with the following principles when processing personal data:
● Lawfulness, fairness and transparency: Personal data shall be processed
lawfully, fairly and in a transparent manner in relation to the data subject.
● Purpose limitation: Personal data shall be collected for specified, explicit and
legitimate purposes and not further processed in a manner that is
incompatible with those purposes.
● Data minimization: Personal data shall be adequate, relevant and limited to
what is necessary in relation to the purposes for which they are processed.
Huawei shall apply anonymization or pseudonymization to personal data if
possible to reduce the risks to the data subjects concerned.
● Storage limitation: Personal data shall be kept for no longer than is
necessary for the purposes for which the personal data is processed.
● Integrity and confidentiality: Personal data shall be processed in a manner
that ensures appropriate security of the personal data, including protection

iMaster NCE-IP
against unauthorized or unlawful processing and against accidental loss,

destruction or damage, using appropriate technical or organizational
measures.
● Accuracy: Personal data shall be accurate and, where necessary, kept up to
date; Proper measures must be taken to promptly delete or correct inaccurate
personal data based on the purpose of data processing.
● Accountability: The data controller must be responsible for and demonstrate
compliance with the preceding principles.
11.3 Lifecycle Management

Based on the lifecycle of personal data in Generally Accepted Privacy Principles
(GAPP), the roles (data controller, data processor, or device supplier) in different
scenarios can be identified to meet compliance requirements in each phase.
Lifecycle Compliance Requirement
Notification ● Inform data subjects of the types of the data to be collected,

to data processing purposes, methods, data subject rights, and
subjects security measures.
Data ● Personal data collection should be based on the consent of

subjects' the data subject, written authorization from the customer, or
choice and other legal reasons.
consent ● Grant the data subject the right to choose and ensure that
the "consent" can be revoked.
Collection ● Collect the least amount of personal data as possible based

on purpose relevancy and necessity.
● If the data is collected from a third party, make sure that it is
collected in a legal manner.
Use, ● Ensure that the purpose, methods and storage duration of

retention, personal data are consistent with of which the data subject is
and disposal informed and with the scope authorized by the customer.
● Ensure the accuracy, integrity, and relevance of personal data
based on personal data processing purposes.
● Provide a security protection mechanism for personal data to
prevent unauthorized or improper use, abuse, and disclosure
of personal data.

iMaster NCE-IP
Disclosure to ● Suppliers and partners (third parties) that process personal

third parties data shall be properly certified based on risks to ensure that
they can provide security measures for personal data
processing. In addition, third parties shall be required on the
contract to provide the same level of data protection as
Huawei.
● Third parties shall not handle personal data beyond contract
and instructions.
● When Huawei jointly handles personal data with a third
party, the responsibilities of each party shall be specified in
the contract.
Legal ● Before transferring personal data across borders, consult with

transfer of the corresponding data protection officer (DPO) or legal
user data affairs department.
● Before personal data is transferred out of the European
Economic Area (EEA), a data transfer agreement required by
the EU shall be signed or customer's explicit consent shall be
obtained. The entity that receives personal data shall comply
with the basic principles of personal data processing to
provide sufficient privacy protection.
Data subject ● As a data controller, provide a reasonable access mechanism

access for data subjects and allow them to update, destroy, or
transfer personal data if necessary.
11.4 Privacy Protection Roles

In on-premises scenarios, carriers/enterprises are responsible for O&M and
operation of products and determine the purposes and methods of personal data
processing. They are data controllers. Huawei is responsible for product delivery
and is an equipment provider.
In SaaS scenarios, enterprise tenants are responsible for product operation and
determine the purposes and methods of personal data processing. They are data
controllers. Huawei is responsible for product delivery and O&M and is a data
processor. Huawei needs to process personal data as requested by the data
controllers.

iMaster NCE-IP
Product Description (x86,enterprise) 12 Specifications
12 Specifications
NCE specifications include performance specifications, NE management

capabilities, and service management capabilities.
12.1 System Performance Indicators
12.2 NE Management Capabilities and Maximum Concurrent Client Connections
12.3 Service Management Capabilities
12.4 Equivalent Coefficient
12.1 System Performance Indicators

Basic Capabilities
Table 12-1 System performance indicators

Category Indicator Value
System startup System startup time ≤ 10 minutes

and shutdown (70% of the
management capacity)
System shutdown time ≤ 10 minutes

(70% of the
management capacity)
System Database restoration ≤ 60 minutes

database time
Protection Application layer ● RPO = 0 seconds

performance protection ● RTO ≤ 3 minutes
Database protection ● RPO = 60 seconds

● RTO ≤ 60 seconds

iMaster NCE-IP
Category Indicator Value
1:N blade cluster ● RPO = 0 seconds

● RTO ≤ 15 minutes
Disaster recovery ● RPO = 60 seconds

● RTO ≤ 15 minutes
Log capacity Operation logs, system ● Default conditions for dumping logs from
logs and security log database:
– Quantity of logs of a type ≥ 1 million
– Retention days of logs of a type ≥ 45
When any of the conditions is met, the earliest
logs will be saved as a log file and dumped to
the hard disk.
● Default conditions for deleting dumped log files
from the hard disk:
– Retention days of the log files ≥ 45
– Total size of all log files ≥ 1024 MB
NE upgrade Concurrent NE upgrade ≤ 60 (NE upgrade task management)

≤ N x 300 (wizard-based NE upgrade)
NOTE
● If the network management scale is less than 80,000
equivalent NEs, N is 1.
● If the network management scale is equal to 80,000
equivalent NEs, N is 3.
Alarm Management Capabilities

NOTE
The alarm management indicators involve alarms and events. Alarms are classified into
uncleared alarms and cleared alarms, which are measured separately.
Table 12-2 Alarm management indicators

Indicator Value
Alarm response speed In normal circumstances, alarms are displayed on NCE within
10 seconds after they are generated on NEs.

iMaster NCE-IP
Indicator Value
Alarm handling capability Normally:

● When NCE manages only IP NEs, the alarm processing
capabilities for different network scales are as follows:
– 2000/6000 equivalent NEs: 100 alarms per second
– 15,000/30,000 equivalent NEs: 100 alarms per second
– 80,000 equivalent NEs: 200 alarms per second
In peak hours:
● No alarm loss within 15 seconds when not more than 1000
alarms are reported per second
Historical alarm storage 180 days

duration in database
Table 12-3 Relationship between the alarm capacity and the NE management scale
NE Management Scale Maximum Current Alarms Maximum Historical Alarms
(Unit: 10,000) (Unit: 10,000)
2000 2 100
6000 5 200
NOTE
The value is 10 in the NCE-IP
Manager+Controller+Analyzer
scenario, and 5 in other scenarios.
15,000 10 400
30,000 10 400
NOTE
The value is 30 in the NCE-IP
Manager+Controller+Analyzer
scenario, and 10 in other scenarios.
80,000 30 1200
NOTE
For details about the NE management scale of NCE, see 12.2 NE Management
Capabilities and Maximum Concurrent Client Connections.
Topology Capabilities
Indicator Value
Links in the current topology ≤ 200,000

iMaster NCE-IP
Indicator Value
Subnets The number of subnets is not limited. Each subnet can contain a
maximum of 500 physical NEs at a maximum of six layers. 200
physical NEs are recommended.
HWECC and IP over DCC ● GNEs: ≤ 3000

networking capability NOTE
A single instance can manage 500 GNEs.
● NEs managed by each GNE: ≤ 128 (50 is recommended)
User Management Capabilities

Indicator Value
Users ≤ 2000
User groups ≤ 500
Object sets ≤ 100
Operation sets ≤ 255

iMaster NCE-IP
Southbound Performance Collection Capabilities

NOTE
● An equivalent instance is a basic unit to describe the performance collection capability

of the PMS.
● Number of equivalent instances = Total number of indicators of each instance (15-
minute period)/50. If the number of equivalent instances is less than one, it is
regarded as one. If the period is not 15 minutes, the value is calculated based on
the proportion of the period to 15 minutes. For example, the number of equivalent
instances of a one-hour period can be 0.25. Note that the total number of
instances cannot exceed the maximum capability of Manager+Controller+Analyzer.
● The preceding collection capabilities are applicable only to SNMPv1 and SNMPv2c.
For SNMPv3, only 2/3 of the data collection capabilities are reached. For example,
the collection capability based on SNMPv1 and SNMPv2c is 150,000, and that
based on SNMPv3 is 100,000. SNMPv1 and SNMPv2c are insecure protocols. A
more secure SNMPv3 protocol is recommended.
● NEs must respond in 0.05s to collection requests sent from NCE. Otherwise, the
actual performance collection capability is compromised.
● Bulk (Access) collection generates only NBI data and does not support PMS
instance creation.
● The equivalent instances of different collection protocols are as follows: 1
equivalent instance = 50 indicators of 1 instance (15-minute period)
Protocol Equivalent Instance
SNMP 1
QX 1
Bulk (IP) 1
Bulk (Access) 0.5
BULKOverQX 2
SNMP-EX 5
SNMPV3 1.5
● If multiple collection methods are used, conversion is required. For example, if SNMP
+Bulk is used for collection and X records are collected in SNMP mode, the number of
records Y collected in Bulk mode can be calculated as follows:
Y = Maximum collection capability – X
● The BulkOverQx collection mode applies to the following NEs: ATN905(V8),
ETN500(V8), OptiX PTN 930, OptiX PTN 905D, OptiX PTN 7900E-32, OptiX PTN 910E-F,
OptiX PTN 905G, OptiX PTN 905E, OptiX PTN 7900E-24, OptiX PTN 7900E-12, OptiX
PTN 960 (160G), OptiX PTN 980, OptiX PTN 990E, OptiX PTN 970C, OptiX PTN 916-F,
OptiX PTN 970, OptiX PTN 990, OptiX PTN 7900-32, OptiX PTN 7900-24, and OptiX PTN
7900-12
Table 12-4 PMS performance collection indicators (NCE-IP)
Collection Equivalent Collection Capability (Maximum Equivalent Records/15

Mode NEs Minutes)
SNMP/BULK 2000 20,000
SNMP/BULK 6000 60,000
SNMP/BULK 15,000 150,000
SNMP/BULK 30,000 150,000

iMaster NCE-IP
Collection Equivalent Collection Capability (Maximum Equivalent Records/15

Mode NEs Minutes)
SNMP-EX 2000 4,000
SNMP-EX 6000 12,000
SNMP-EX 15,000 30,000
SNMP-EX 30,000 30,000
BulkOverQx 2000 10,000
BulkOverQx 6000 30,000
BulkOverQx 15,000 75,000
BulkOverQx 30,000 75,000
Qx 2000 20,000
Qx 6000 40,000
Qx 15,000 80,000
Qx 30,000 100,000
Table 12-5 Analyzer performance collection capabilities

Protocol Real-Time Historical Performance Data Collection
Performance
Data
Collection
Collection Collection Capability Description

Capability
Qx Not ● Number of performance instances: N N indicates the number of

(indepen supported × 30 (15-minute collection period) equivalent NEs. For details
dent ● Number of performance indicators: about how to calculate the
collectio N × 30 × 50 (15-minute collection number of equivalent NEs,
n) period) see 12.4 Equivalent
Coefficient.
Qx Not ● Number of performance instances: This capacity is not affected

(proxy supported 150,000 (15-minute collection by the number of equivalent
collectio period) NEs.
n) ● Number of performance indicators:
150,000 × 50 (15-minute collection
period)

iMaster NCE-IP

Performance
Data
Collection

Capability
SNMP ● Compact ● Number of performance instances: N ● N indicates the number

scenario × 30 (15-minute collection period) of equivalent NEs. For
with 2000 ● Number of performance indicators: details about how to
equivalent N × 30 × 50 (15-minute collection calculate the number of
NEs: 50 period) equivalent NEs, see 12.4
performan Equivalent Coefficient.
ce ● The 15-minute collection
instances period is used as an
● Other example to describe the
scenarios: collection capability. For
200 other collection periods,
performan the collection capability
ce is calculated by
instances proportion. The
calculation formula is as
follows: number of 15-
minute instances:number
of 5-minute instances =
3:1.
● A maximum of 1000 and
3000 performance
instances can be created
for an NE within a
collection period of 5
minutes and 15 minutes,
respectively.
SNMP- ● Compact ● Number of performance instances: N N indicates the number of

EX scenario × 3 (15-minute collection period) equivalent NEs. For details
with 2000 ● Number of performance indicators: about how to calculate the
equivalent N × 3 × 50 (15-minute collection number of equivalent NEs,
NEs: 5 period) see 12.4 Equivalent
performan Coefficient.
ce
instances
● Other
scenarios:
20
performan
ce
instances

iMaster NCE-IP

Performance
Data
Collection

Capability
BulkOve ● Compact ● Number of performance instances: N N indicates the number of

rQx scenario × 6 (15-minute collection period) equivalent NEs. For details
with 2000 ● Number of performance indicators: about how to calculate the
equivalent N × 6 × 50 (15-minute collection number of equivalent NEs,
NEs: 10 period) see 12.4 Equivalent
performan Coefficient.
ce
instances
● Other
scenarios:
40
performan
ce
instances
Bulk Not Number of performance instances: N × N indicates the number of

supported 30 (15-minute collection period) equivalent NEs. For details
about how to calculate the
number of equivalent NEs,
see 12.4 Equivalent
Coefficient.
Twamp 10 Number of performance instances: N × N indicates the number of

performance 5 (15-minute collection period) equivalent NEs. For details
instances about how to calculate the
number of equivalent NEs,
see 12.4 Equivalent
Coefficient.
Netstrea Not A maximum of 1,000,000 flows per 5 ● For details about how to
m supported minutes calculate the number of
NOTE equivalent NEs, see 12.4
NCE can process a maximum of 1 million Equivalent Coefficient.
flows within 5 minutes.
● Only Analyzer (basic
analysis+flow collection)
with 6000 equivalent NEs
is supported.
● Netstream collection
applies only to the
servers added to the
Analyzer (basic analysis)
hardware resources.
Analyzer (basic analysis)
can also use other
collection modes.

iMaster NCE-IP

Performance
Data
Collection

Capability
Hybrid ● Compact ● Number of performance instances: N ● N indicates the number

of scenario × 20 (15-minute collection period) of equivalent NEs. For
Telemetr with 2000 ● Number of performance indicators: details about how to
y and equivalent N × 20 × 50 (15-minute collection calculate the number of
SNMP NEs: 50 period) equivalent NEs, see 12.4
performan Equivalent Coefficient.
ce ● The 15-minute collection
instances period is used as an
● Other example to describe the
scenarios: collection capability. For
200 other periods, the
performan collection capability is
ce calculated by proportion.
instances The calculation formula
is as follows: number of
15-minute
instances:number of 5-
minute instances:number
of 1-minute
second instances:number
of 10-second
second instances =
900:300:60:30:10:1.
● Only one type of
Telemetry or SNMP
monitoring instance can
be created for a resource.
That is, a Telemetry
monitoring instance
cannot be created for a
resource when an SNMP
monitoring instance is
created for the same
resource.
● Only monitoring
instances using the same
collection protocol can be
created for resources that
have aggregation
relationships (such as
interfaces to links, boards
to NEs, and interfaces

iMaster NCE-IP

Performance
Data
Collection

Capability
and QoS profiles). For

example, if an SNMP
monitoring instance is
created for an interface,
only an SNMP
monitoring instance can
be created for the
associated link. Telemetry
monitoring instances
cannot be created.
SNMP Not ● IP RAN analysis (basic data + None

and IFIT supported second-level data) on 6,000
hybrid equivalent NEs: The SNMP collection
collectio capability is 120,000, and the IFIT
n flow collection capability is 30,000
unidirectional flows.
Table 12-6 SNMP-EX collection (Instances need to be created based on the

indicator groups listed in the following table.)
Navigation Path Resource Sub-resource Indicator Group
Router/ 40/100G Ethernet -- BIP8 Statistics

Switch/MA/ME NE Port Profile
> Port
Link Dynamic Tunnel Dynamic Tunnel LSP TE Jitter

Router&Switch Delay and Delay
Tunnel Jitter and Packet
Loss
LSP TE Ping Path

Delay and Packet
Loss
Dynamic Tunnel LSP TE Ping Path

PTN6900 Tunnel Delay and Packet
Loss
LSP TE Jitter
Delay and Delay
Jitter and Packet
Loss

iMaster NCE-IP
Static Tunnel Static Tunnel LSP IP Ping Delay

Router&Switch and Packet Loss
Tunnel
LSP IP Jitter Path
Delay and Packet
Loss
Static Tunnel LSP IP Jitter Path

PTN6900 Tunnel Delay and Packet
Loss
LSP IP Ping Delay

and Packet Loss
IP Link -- UDP Ping Delay

and Packet Loss
UDP Jitter Delay

and Delay Jitter
and Packet
Loss(IPV4)
ICMP Delay and

Packet Loss(IPv4)
ICMP Delay and

Packet Loss(IPv6)
ICMP Jitter Delay

and Delay Jitter
and Packet Loss
IGP Link -- UDP Ping Delay

and Packet Loss
UDP Jitter Delay

and Delay Jitter
and Packet
Loss(IPV4)
ICMP Delay and

Packet Loss(IPv4)
ICMP Delay and

Packet Loss(IPv6)
ICMP Jitter Delay

and Delay Jitter
and Packet Loss
L2 Link -- Ethernet Service

OAM MAC Ping
Delay and Delay
Jitter and Packet
Loss

iMaster NCE-IP
Service > VPN L3VPN VRF L3VPN basic

Statistics
Indicators
PE Link UDP Jitter Delay

and Delay Jitter
and Packet
Loss(IPV4)
ICMP Ping Delay

and Packet Loss
Ratio
SNMP Ping Delay

and Packet Loss
TCP Ping Delay

and Packet Loss
UDP Ping Delay

and Packet Loss
CE Link ICMP Delay and

Packet Loss(IPv4)
UDP Ping Delay

and Packet Loss
ICMP Jitter Delay

and Delay Jitter
and Packet Loss
ICMP Delay and

Packet Loss(IPv6)
UDP Jitter Delay

and Delay Jitter
and Packet
Loss(IPV4)
PTN 6900 VRF L3VPN basic

Statistics
Indicators
PTN6900 PE Link SNMP Ping Delay

and Packet Loss
ICMP Ping Delay

and Packet Loss
Ratio
UDP Jitter Delay

and Delay Jitter
and Packet
Loss(IPV4)

iMaster NCE-IP
TCP Ping Delay

and Packet Loss
UDP Ping Delay

and Packet Loss
PTN 6900 CE Link ICMP Delay and

Packet Loss(IPv4)
UDP Jitter Delay

and Delay Jitter
and Packet
Loss(IPV4)
UDP Ping Delay

and Packet Loss
ICMP Jitter Delay

and Delay Jitter
and Packet Loss
VPLS VC Delay and Packet

Loss
PTN 6900 VC Delay and Packet

Loss
Service > VPN > PWE3 ATM PW Delay and Packet

PWE3 Loss
PTN 6900 PW Delay and Packet

Loss
PWE3 CES PW Delay and Packet

Loss
PTN 6900 PW Delay and Packet

Loss
PWE3 ETH PTN 6900 PW Delay and Packet

Loss
PW Delay and Packet

Loss
PWE3 IP PTN 6900 PW Delay and Packet

Loss
PW Delay and Packet

Loss
PWE3 ATM IWF PTN 6900 PW Delay and Packet

Loss
PTN 6900 VC Delay and Packet

Loss

iMaster NCE-IP
Test Path > UDP Path -- UDP Delay and

Network Path Packet Loss
TCP Path -- TCP Delay and

Packet Loss
ICMP Path -- ICMP Delay and

Packet Loss(IPv4)
UDP Jitter -- UDP Jitter Delay

Path(IPv4) and Delay Jitter
and Packet
Loss(IPV4)
ICMP Path(IPv6) -- ICMP Delay and

Packet Loss(IPv6)
ICMP Jitter Path -- ICMP Jitter Delay

and Delay Jitter
and Packet Loss
UDP Jitter -- UDP Jitter Delay

Path(IPv6) and Delay Jitter
and Packet
Loss(IPv6)
Ethernet Service -- Ethernet Service

OAM MAC Path OAM MAC Ping
Delay and Delay
Jitter and Packet
Loss
Test Path > SNMP Path -- SNMP Delay and

Application Path Packet Loss
FTP Path -- FTP Delay and

Packet Loss
DNS Path -- DNS Parsing

Delay and Parsing
Error and Packet
Loss
HTTP Path -- HTTP Delay and

Packet Loss
DHCP Path -- DHCP Delay
Test Path > LSP LSP IP Ping Path -- Delay and Packet
Path Loss
LSP TE Ping Path -- Delay and Packet

Loss

iMaster NCE-IP
LSP IP Jitter Path -- Delay and Packet

Loss
LSP TE Jitter Path -- Delay and Packet

Loss
Test Path > PWE3 PWE3 Path -- PWE3 Delay and

Path Packet Loss
Test Path > VPLS VPLS MAC Path -- Delay and Packet
Path Loss
OAM TWAMP OAM -- Packet Loss

Performance Statistics
-- Delay and Delay

Jitter Statistics
NOTE
The collection node of NCE Analyzer does not support dynamic load balancing of existing
tasks.
NBI Capabilities
Table 12-7 NBI concurrency indicators

Protocol Maximum Concurrent Requests
CORBA 4
XML 20
REST 6000
NOTE
The total number of concurrent controls for all REST APIs is 6000.
For details about the concurrent controls of each REST API, see the
API constraints.
NOTE
For CORBA, XML, and REST, the number of concurrent requests refers to the maximum
number of interfaces that OSSs can invoke. The number is collected among all OSSs and
interfaces. For example, if the number is 4, it is probable that one OSS invokes four
interfaces (a, b, c, d) at the same time, or four OSSs invoke one interface (a) at the same
time.

iMaster NCE-IP
Table 12-8 OSS connection indicators
Protocol Maximum OSS Connections
SNMP A maximum of 10 OSSs can be connected to NCE.
TEXT ● As the FTP/SFTP client, NCE transmits files to only one

OSS.
● As the FTP/SFTP server, NCE can be accessed by a
maximum of three OSSs.
NOTE
For SNMP and TEXT, the number of NCE connections is collected by OSS.
12.2 NE Management Capabilities and Maximum

Concurrent Client Connections
The number of clients, number of equivalent NEs, and number of physical NEs are
key indicators for measuring the NE management capability of NCE.
The maximum management capabilities are described based on specific hardware

configurations. The management capabilities of NCE vary with hardware
configurations.
NOTE
For simplicity purpose, this table uses short names for NCE components. The meanings of
the short names are as follows:
● Manager indicates that only the Manager component is deployed.
● Analyzer indicates that the Analyzer component is deployed.
● Manager+Controller indicates that the Manager and Controller components are
deployed.
● Manager+Controller+Analyzer indicates that Manager, Controller, and Analyzer are
deployed.
Table 12-9 Maximum NE management capability and client connection indicators (NCE-IP)
Component Maximum Physical NEs Maximum Equivalent Maximum

NEs Concurrent Client
Connections
Manager N/A 2,000 32

(Manager
+Analyzer)

iMaster NCE-IP
Component Maximum Physical NEs Maximum Equivalent Maximum

NEs Concurrent Client
Connections

+Controller
+Analyzer

+Controller
+Analyzer

+Controller
+Analyzer

+Controller
+Analyzer
NOTE
● The cross-domain scenario is a combination of IP, T, and FAN domains, including IP+T
+FAN, IP+T, T+FAN, and IP+FAN scenarios.
● For simplicity purpose, this table uses short names for NCE components. The meanings
of the short names are as follows:
● Manager indicates that the Manager component is deployed.
● Manager+Controller+Analyzer indicates that Manager, Controller, and Analyzer
components are deployed.
12.3 Service Management Capabilities

Tunnel and Service Access Interface Capabilities
Category Indicator (Manager+Controller Indicator (Management)
+Analyzer)
Number of tunnels Number of tunnels = N x 6 Number of tunnels = N x 6

(undelegated RSVP-TE and static (undelegated RSVP-TE and static
tunnels) tunnels)
N indicates the maximum number N indicates the maximum number
of equivalent NEs. of equivalent NEs.

iMaster NCE-IP

+Analyzer)
Number of LSPs 6000 equivalent NEs: N/A

● NCE can manage a maximum of
32,000 dynamic tunnels in cases
where only RSVP-TE or SR-TE
tunnels are involved, as well as
64,000 LSPs if hot standby is
enabled for each tunnel.
where only SR Policies are
involved, as well as 128,000 LSPs
if hot standby is enabled for
each tunnel.
64,000 dynamic tunnels
(including 32,000 RSVP-TE and
SR-TE tunnels at most) and
128,000 LSPs in cases where
RSVP-TE tunnels, SR-TE tunnels,
and SR Policies co-exist.
15,000 or 30,000 equivalent NEs:
where only RSVP-TE or SR-TE
tunnels are involved, as well as
128,000 LSPs if hot standby is
enabled for each tunnel.
128,000 dynamic tunnels in
cases where only SR Policies are
involved, as well as 256,000 LSPs
if hot standby is enabled for
each tunnel.
128,000 dynamic tunnels
(including 64,000 RSVP-TE and
SR-TE tunnels at most) and
256,000 LSPs in cases where
RSVP-TE tunnels, SR-TE tunnels,
and SR Policies co-exist.

iMaster NCE-IP

+Analyzer)
Number of IP service IP service interfaces include access IP service interfaces include access
access interfaces service interfaces and network service interfaces and network
service interfaces. The total number service interfaces. The total
of IP service interfaces is calculated number of IP service interfaces is
as follows: calculated as follows:
Total number of IP service Total number of IP service
interfaces = N × 20 interfaces = N × 20
N indicates the maximum number N indicates the maximum number
of equivalent NEs. of equivalent NEs.
12.4 Equivalent Coefficient

Equivalent coefficients are the ratios of the resources occupied by physical NEs or
ports to the resources occupied by equivalent NEs.
Definition
● Equivalent NE: a uniform criterion used to describe and calculate the
management capabilities of NCE. This criterion is needed because different
types of NEs occupy different system resources to support different functions,
features, cross-connect capacities, and numbers of boards, ports, and
channels. Therefore, different types of NEs and ports must be converted to
equivalent NEs based on the number of system resources they occupy. An
equivalent NE occupies as many system resources as an STM-1 transport NE.
● Equivalent coefficient: Resources occupied by physical NEs or ports/Resources
occupied by equivalent NEs
Calculation
The number of equivalent NEs that NCE can manage is calculated according to
the following rules:
● Basic unit of equivalent NEs: OptiX OSN 1800 I
● The equivalent coefficient of third-party NEs is 1. The equivalent coefficient of
OEM devices is the same as that of Huawei devices.
● Number of equivalent NEs = Number of NEs of type 1 x Equivalent coefficient
of type 1 + ... + Number of NEs of type n x Equivalent coefficient of type n
12.4.1 Equivalent Coefficients for NEs on NCE-IP

Rules for defining the equivalent coefficients of NEs:

iMaster NCE-IP
Device Type Rule Equivalent Coefficient
Fixed- Small device <=1U 1~2.5

configuratio
n device Midrange >1U 2.5~5
device
Modular Large device <=20U 5~10

device
Ultra-large >20U >=10
device
Number of equivalent NEs on NCE-IP = Number of NEs of type 1 x Equivalent

coefficient of type 1 + ... + Number of NEs of type n x Equivalent coefficient of type
n
NOTE
For example, if there are 5 NE5000Es (equivalent coefficient: 10), 200 S5300 series
(equivalent coefficient: 1.25), and 1000 CX200 series (equivalent coefficient: 0.625), then:
Number of equivalent NEs on NCE-IP = 5×10 + 200×1.25 + 1000×0.625 = 925
The following table lists the equivalent coefficients for NEs on NCE-IP.
Table 12-10 Equivalent coefficients for NEs on NCE-IP

NE Type Equivalent Coefficient
Alcatel-Lucent7750 0
AntiDDos1825 0.75
AntiDDoS1820-N 0.75
AntiDDos1880 0.75
AntiDDos1820 0.75
AntiDDoS1520 0.75
AntiDDoS1500-D 0.75
AntiDDoS1680-DC 0.75
AntiDDoS1650-AC 0.75
AntiDDoS1550 0.75
AntiDDoS12016 10
AntiDDoS12008F 5
AntiDDoS12004F 5

iMaster NCE-IP
AntiDDoS12008-DC 4
AntiDDoS12008-AC 4
AntiDDoS12004-DC 1.5
AntiDDoS1905-N 1
AntiDDoS1905-K 1
AntiDDoS1908 1
AntiDDoS1908-K 1
AntiDDoS1905 0.25
AntiDDoS8080 4.0
AntiDDoS8160 8.0
AntiDDoS8030 1.5
AR631I-LTE4CN 0.125
AR631I-LTE4EA 0.125
RU-5G-101 1.0
AR10 0.125
SRG1340E 0.25
SRG1311 0.125
AR6140E-S 0.25
AR6121E-S 0.125
AR6121EC-S 0.125
AR730 0.125
AR720 0.125
AR6121E 0.125
AR6140E-9G-2AC 0.25
AR651W-8P 0.125
SRG1340-16G4XG 0.25
AR6121-S 0.125
AR6121K 0.125
AR6121C-S 0.125

iMaster NCE-IP
AR6140K-9G-2AC 0.25
AR6140H-S 0.25
AR6140-9G-R-2AC 0.25
AR651K 0.125
SRG1321 0.125
AR6140-16G4XG 0.25
AR6140-9G-2AC 0.25
AR6121 0.125
AR6120-S 0.25
AR651U-A4-LTE4EA 0.125
AR651U-A4-LTE6EA 0.125
AR651 0.125
AR651-LTE6EA 0.125
AR651W 0.125
AR6120-VW 0.25
AR6140-S 0.25
AR6120 0.25
AR1220-S2 0.25
AR1220-8GE 0.25
AR1220W 0.25
AR1220VW 0.25
AR1220-S 0.25
AR1220-D 0.25
AR1220L-S 0.25
AR1220EV 0.25
AR1220E-S 0.25
AR1220F-S 0.25
AR1220EVW 0.25
AR1220E 0.25
AR1220F 0.25

iMaster NCE-IP
AR1220W-S 0.25
AR1220L 0.25
AR1220V 0.25
AR1220 0.25
AR1000V 0.25
AR1220C 0.25
SRG1340-9G 0.125
AR1504-24T 0.125
AR129CV 0.125
AR1504-8S16T 0.125
AR1504-16S8T 0.125
AR1504-24S 0.125
AR151 0.125
AR156 0.125
AR151G-HSPA+7 0.125
AR151W-P 0.125
AR157VW 0.125
AR151G-C 0.125
AR151G-U-S 0.125
AR121-S 0.125
AR121 0.125
AR121W 0.125
AR121W-S 0.125
AR129GW-L 0.125
AR101-S 0.125
AR101GW-Lc-S 0.125
AR109W 0.125
AR129CVW 0.125
AR109GW-L 0.125
AR109 0.125

iMaster NCE-IP
AR101W-S 0.125
AR129CGVW-L 0.125
AR121GW-L 0.125
AR129W 0.125
AR129 0.125
AR156W 0.125
AR151-S 0.125
AR151W-P-S 0.125
AR158EVW 0.125
AR157W 0.125
AR157G-HSPA+7 0.125
AR158E 0.125
AR157 0.125
AR18-33E 0.25
AR18-13V 0.25
AR18-34E 0.25
AR18-10 0.25
AR18-35 0.25
AR18-20S 0.25
AR18-18V 0.25
AR18-21A 0.25
AR18-21 0.25
AR18-35E 0.25
AR18-32E 0.25
AR18-31E 0.25
AR18-30E 0.25
AR18-2224 0.25
AR18-13 0.25
AR18-20 0.25
AR18-33 0.25

iMaster NCE-IP
AR18-34 0.25
AR18-32 0.25
AR18-31 0.25
AR18-30 0.25
AR18-18 0.25
AR18-16 0.25
AR18-15 0.25
AR18-12 0.25
AR19-62 0.25
AR1915-I 0.25
AR1913-I 0.25
AR1910 0.25
AR19-61 0.25
AR651U-A4 0.125
AR151-S2 0.125
AR611W-LTE6EA 0.125
AR611-LTE4EA 1
AR611E-S 1
AR611 0.125
AR303W 0.125
AR303 0.125
AR611W-S 0.125
AR611-S 0.125
SRG1301 0.125
AR161FW-DGP 0.125
AR611W 0.125
AR617VW 0.125
AR611W-LTE4CN 0.125
AR617VW-LTE4EA 0.125
AR657 0.125

iMaster NCE-IP
AR651F-Lite 0.125
AR657W 0.125
AR651C 0.125
AR169JFVW-2S 0.125
AR502EGRz-L 0.125
AR502EG-L-PD 0.125
AR503EDGW-Lo 0.125
AR550C-2C6GE-2D 0.125
AR168F-4P 0.125
AR502EGRz-Lc 0.125
AR169JFVW-4B4S 0.125
AR161EGW-L 0.125
AR1610 0.125
AR161FG-Lc 0.125
AR550E 0.125
AR206 0.125
AR207V 0.125
AR208E 0.125
AR201-S 0.125
AR201VW-P 0.125
AR168F 0.125
AR531-2C-H 0.125
AR161F-S 0.125
AR161FG-L 0.125
AR169FVW 0.125
AR169FGVW-L 0.125
AR511GW-UAV2M5 0.125
AR531GPe-U-H 0.125
AR550-8FE-D-H 0.125
AR502G 0.125

iMaster NCE-IP
AR531GB-U-D-H 0.125
AR511GW-LM7 0.125
AR169FGW-L 0.125
AR161G-L 0.125
AR169-P-M9 0.125
AR503GW-LM7 0.125
AR169FV-8S 0.125
AR161FW 0.125
AR169W-P-M9 0.125
AR531GZ-U-D 0.125
AR515GW-LM9-D 0.125
AR161W 0.125
AR502G-L-D-H 0.125
AR531G-F 0.125
AR550C-2C6GE 0.125
AR509CG-Lt-N 0.125
AR503EW 0.125
AR532 0.125
AR502EGR-L 0.125
AR502EGW-L 0.125
AR511CGW-LAV2M3 0.125
AR509CG-Lc 0.125
AR502CG-L 0.125
AR161G-Lc 0.125
AR503EDGW-Lc3 0.125
AR169CVW-4B4S 0.125
AR169EGW-L 0.125
AR161EW 0.125
AR509GW-L-D-H 0.125
AR509CG-Lt-7 0.125

iMaster NCE-IP
AR161W-S 0.125
SRG550C-2C6GE 0.125
SRG550-24FE 0.125
SRG550C-4GE 0.125
SRG509CG-Lc 0.125
AR161GW-Lc-S 0.125
AR161-S 0.125
AR509CGW-L 0.125
AR161EW-M1 0.125
AR169EW 0.125
AR169CVW 0.125
AR502EGRb-L 0.125
AR201V 0.125
AR161FGW-Lc 0.125
AR502EGRc-Lc 0.125
AR509G-Lc 0.125
AR503GW-LcM7 0.125
AR111-S 0.125
AR502EG-L 0.125
AR502ER 0.125
AR503EDGW-Lc 0.125
AR503EQGW-L 0.125
AR509CG-Lt 0.125
AR550C-4GE 0.125
AR502GR-L-D-H 0.125
AR169W 0.125
AR161G-U 0.125
AR161FGW-La 0.125
AR169RW-P-M9 0.125
AR161FV-1P 0.125

iMaster NCE-IP
AR169BF 0.125
AR169FVW-8S 0.125
AR509G-L-D-H 0.125
AR169G-L 0.125
AR169 0.125
AR161 0.125
AR161F 0.125
AR513W-V3M8 0.125
AR511GW-L-B3 0.125
AR531GP-H 0.125
AR550-24FE-D-H 0.125
AR531GR-U-H 0.125
AR531G-U-D-H 0.125
AR511GW-LAV2M3 0.125
AR161FW-P-M5 0.125
AR162F 0.125
AR161FGW-L 0.125
AR531-F2C-H 0.125
AR169F 0.125
AR207VW 0.125
AR207-S 0.125
AR207G-HSPA+7 0.125
AR207V-P 0.125
AR207 0.125
AR201 0.125
AR6280C-S 0.25
AR6280K 0.25
AR6280-S 0.25
AR6280 0.25
AR651-X8 0.25

iMaster NCE-IP
AR651W-X4 0.25
AR2204XE 0.25
AR2240 0.25
AR2220L 0.25
AR2201-48FE 0.25
AR2204 0.25
AR2204-S 0.25
AR2540-H 0.25
AR2204-51GE-P 0.25
AR2204-27GE-P 0.25
AR2240C 0.25
AR2204E-D 0.25
AR2630 0.25
AR2204-51GE-R 0.25
AR2240C-S 0.25
AR2204-48GE-P 0.25
AR2204-24GE 0.25
AR2220E-S 0.25
AR2504-D-H 0.25
AR2204-51GE 0.25
AR2504E-H 0.25
AR2504-H 0.25
AR2204E 0.25
AR2204-27GE 0.25
AR2220E 0.25
AR2240-S 0.25
AR2201-48FE-S 0.25
AR2202-48FE 0.25
AR2230L 0.25
AR2220-S 0.25

iMaster NCE-IP
AR2220 0.25
AR28-09 0.25
AR2809B 0.25
AR28-14 0.25
AR28-13 0.25
AR28-12 0.25
AR28-80 0.25
AR28-40 0.25
AR28-31 0.25
AR28-30 0.25
AR28-11 0.25
AR28-10 0.25
AR29-01 0.25
AR29-11 0.25
AR29-61 0.25
AR29-41 0.25
AR29-21 0.25
AR6300C-S 0.25
AR6300K 0.25
SRG33X0 0.25
AR6300-S 0.25
AR6300 0.25
AR3560-H 0.25
AR3260E-S 0.25
AR3260-S 0.25
AR3260 0.25
AR3670 0.25
AR46-80E 0.25
AR46-40E 0.25
AR46-20E 0.25

iMaster NCE-IP
AR46-80 0.25
AR46-40 0.25
AR46-20 0.25
AR49-65 0.25
AR49-45 0.25
AR5510-H8P2TW1 0.25
AR5510-L5T-LTE4EA 0.125
AR5510-L5T 0.125
AR5510-H10T1 0.25
AR5710-H8T2TS1-T 1
AR5710-H8T2TS1 1
AR6510-L11T1X2 0.5
AR6500-10 1.0
AR6510-L5T4S4 0.5
AR6710-L8T3TS1X2-T 1
AR6710-L8T3TS1X2 1
AR6710-L50T2X4-T 1
AR6710-L26T2X4 1
AR6710-L26T2X4-T 1
AR6710-L50T2X4 1
ASG2100 0.25
ASG2200 0.25
ASG2600 0.75
ASG2800 0.75
ATN905A-P AC 0.25
ATN905 AC 0.25
ATN905-V AC 0.25
ATN905A-C 0.25
ATN905-E AC 0.25
ATN905-BM 0.25

iMaster NCE-IP
ATN905A-D 0.25
ATN905 DC 0.25
ATN905A-V AC 0.25
ATN905A AC 0.25
ATN905-S(V8) 0.25
ATN905-G(V8) 0.25
ATN905 DC(V8) 0.25
ATN905 AC(V8) 0.25
ATN910 0.5
ATN910B-D AC 0.5
ATN910B-E AC 0.5
ATN910B-D DC 0.5
ATN910B 0.5
ATN910B-F DC(V8) 0.5
ATN910B-F AC(V8) 0.5
ATN910B-E AC(V8) 0.5
ATN910B-D DC(V8) 0.5
ATN910B(V8) 0.5
ATN910B-D AC(V8) 0.5
ATN910B-F DC 0.5
ATN910B-F AC 0.5
ATN910C-M 0.5
ATN910C-K 0.5
ATN910C-H 0.5
ATN910C-S 0.5
ATN910C-F 0.5
ATN910C-D 0.5
ATN910C-B 0.5
ATN910C-A 0.5
ATN910C-G 0.5

iMaster NCE-IP
ATN910D-B 0.5
ATN910D-A 0.5
ATN910I-TC DC 0.5
ATN910I-C AC 0.5
ATN910I DC 0.5
ATN910I-D DC 0.5
ATN910I-B DC 0.5
ATN910I-E DC 0.5
ATN910I-D AC 0.5
ATN910I-P AC 0.5
ATN910I AC 0.5
ATN950 1.0
ATN950B 1.0
ATN950B(160G) 1.0
ATN950B(V8) 1.0
ATN950C 1.0
ATN950D 1
ATN980 1.0
ATN 980B 1.0
ATN 980C-PL 1.0
ATN 980C 1.0
ATN 980D 1.0
ATN990 1.0
ATN-IOT-905A-D 0.25
ATN-IOT-905A AC 0.25
ATN-IOT-905A-V AC 0.25
ATN-IOT-905 DC 0.25
ATN-IOT-905A-C 0.25
ATN-IOT-905-E AC 0.25
ATN-IOT-905-V AC 0.25

iMaster NCE-IP
ATN-IOT-905A-P AC 0.25
ATN-IOT-905 AC 0.25
ATN-IOT-905-G(V8) 0.25
ATN-IOT-905-DC(V8) 0.25
ATN-IOT-905C-AC(V8) 0.25
ATN-IOT-910 0.5
ATN-IOT-910B 0.5
ATN-IOT-910B-D AC 0.5
ATN-IOT-910B-F AC 0.5
ATN-IOT-910B-F DC 0.5
ATN-IOT-910B-E AC 0.5
ATN-IOT-910B-D DC 0.5
ATN-IOT-910B-E AC(V8) 0.5
ATN-IOT-910B-F DC(V8) 0.5
ATN-IOT-910B-F AC(V8) 0.5
ATN-IOT-910B-D AC(V8) 0.5
ATN-IOT-910B-D DC(V8) 0.5
ATN-IOT-910B(V8) 0.5
ATN-IOT-910C-A 1
ATN-IOT-910C-B 1
ATN-IOT-910C-D 1
ATN-IOT-910C-M 0.5
ATN-IOT-910C-K 0.5
ATN-IOT-910C-G 0.5
ATN-IOT-910C-H 0.5
ATN-IOT-910C-S 0.5
ATN-IOT-910C-F 0.5
ATN-IOT-910D-B 0.5
ATN-IOT-910D-A 0.5
ATN-IOT-910I AC 0.5

iMaster NCE-IP
ATN-IOT-910I-C AC 0.5
ATN-IOT-910I-P AC 0.5
ATN-IOT-910I-D AC 0.5
ATN-IOT-910I-E DC 0.5
ATN-IOT-910I-B DC 0.5
ATN-IOT-910I-D DC 0.5
ATN-IOT-910I-TC DC 0.5
ATN-IOT-910I DC 0.5
ATN-IOT-950 1.0
ATN-IOT-950B 1.0
ATN-IOT-950B(160G) 1.0
ATN-IOT-950C(V8) 1.0
ATN-IOT-950D 1
ATN-IOT-980C 1.0
BGW9916 5.0
CE12804 6.0
CE12812 10.0
CE12816 10.0
CE12808S 8.0
CE12808E 8.0
CE12816E 10.0
CE12816M 10.0
CE12812E 10.0
CE12804E 6.0
CE12804S 6.0
CE12808 8.0
CE16816 10.0
CE16808 8.0

iMaster NCE-IP
CE16804 6.0
CE5882-48T4S 1.25
CE5855F-48T4S2Q 1.25
CE5855E-48T4S2Q 1.25
CE5881-48T6CQ 1.25
CE5880-48T6Q-EI 1.25
CE5850-48T4S2Q-EI 1.25
CE5810-48T4S-EI 1.25
CE5850-48T4S2Q-HI 1.25
CE5810-24T4S-EI 1.25
CE5855-24T4S2Q-EI 1.25
CE5855-48T4S2Q-EI 1.25
CE6870-48S6CQ-EI-A 1
CE6863E-48S6CQ 1.25
CE6857F-48T6CQ 1.25
CE6857F-48S6CQ 1.25
CE6865E-48S8CQ 1.25
CE6857E-48T6CQ 1.25
CE6857E-48S6CQ 1.25
CE6881-48T6CQ-K 1.25
CE6881-48T6CQ 1.25
CE6881E-48S6CQ 1.25
CE6863-48S6CQ-K 1.25
CE6881-48S6CQ-K 1.25
CE6865-48S8CQ-SI 1.25
CE6820-48S6CQ 1.25
CE6881-48S6CQ 1.25
CE6863-48S6CQ 1.25
CE6857-48S6CQ-EI 1.25
CE6875-48S4CQ-HI 1.25

iMaster NCE-IP
CE6865-48S8CQ-EI 1.25
CE6875-48S4CQ-EI 1.25
CE6856-48T6Q-HI 1.25
CE6856-48S6Q-HI 1.25
CE6850-48S4Q-EI 1.25
CE6810-48S4Q-EI 1.25
CE6810-48S4Q-LI 1.25
CE6850U-48S6Q-HI 1.25
CE6810-32T16S4Q-LI 1.25
CE6810-24S2Q-LI 1.25
CE6855-48T6Q-HI 1.25
CE6860-48S18CQ-EI 1.25
CE6870-48S6CQ-EI 1.25
CE6880-48S4Q2CQ-EI 1.25
CE6880-48T4Q2CQ-EI 1.25
CE6870-48T6CQ-EI 1.25
CE6880-24S4Q2CQ-EI 1.25
CE6870-24S6CQ-EI 1.25
CE6860-48S8CQ-EI 1.25
CE6855-48S6Q-HI 1.25
CE6851-48S6Q-HI 1.25
CE6850U-24S2Q-HI 1.25
CE6850-48T6Q-HI 1.25
CE6850-48S6Q-HI 1.25
CE6810-48S-LI 1.25
CE6850-48T4Q-EI 1.25
CE7850-32Q-EI 1.25
CE7855-32Q-EI 1.25
CE8851-32CQ8DQ-P 2.5
CE8850E-32CQ-EI 1

iMaster NCE-IP
CE8850E-64CQ 2.5
CE8868-4C-EI 1.25
CE8861-4C-EI 1.25
CE8850-64CQ-EI 1.25
CE8860-4C-EI 1.25
CE8850-32CQ-EI 1.25
CE9860-4C-EI-A 2
CE9860-4C-EI 2.0
CISCO ASR 9922 7
Cisco12008 0
Cisco12012 0
Cisco12016 0
Cisco12816 0
Cisco3550 0
Cisco4006 0
Cisco7206 0
Cisco7209 0
Cisco7304 0
Cisco7507 0
Cisco7513 0
CiscoASR901 0
ciscoASR903 0
ciscoMe3400eg2csA 0
ciscoMe3400g12CsD 0
ciscoMe3600x24fsM 0
ciscoMe3400g12CsA 0
CX200C 0.625
CX200A 0.625
CX200B 0.625
CX200D 0.625

iMaster NCE-IP
CX200D-MC 0.625
CX200D-EA-MC 0.625
CX200D-EA 0.625
CX300A 1.25
CX300B 1.25
CX380 1.25
CX600-X3 1.25
CX600-X2 1.0
CX600-X8-DO 2.5
CX600-X16-DO 5.0
CX600-X3-DO 1.25
CX600-X2-DO 1.0
CX600-X1-DO 0.5
CX600-X1 0.5
CX600-X16 5.0
CX600-X8 2.5
CX600-4 1.25
CX600-16 5.0
CX600-8 2.5
CX600-X3(V8) 1.25
CX600-X16-DO 5.0
CX600-X2-M8A 1.0
CX600-M2K 0.5
CX600-X3A(V8) 1.25
CX600-X8-DO(V8) 2.5
CX600-X2-M16A 1.0
CX600-X1-M4 0.5
CX600-X2-M16 1.0
CX600-X2-M8-DO 1.0
CX600-X8(V8) 2.5

iMaster NCE-IP
CX600-X8A(V8) 2.5
CX600-M2E 0.5
CX600-M2F 0.5
CX600-X16A(V8) 5.0
CX600-X16(V8) 5.0
CX600-X2-M16-DO 1.0
CX600-X1-M4-DO 0.5
CX600-X2-M8 1.0
CX600-X16A-DO(V8) 5.0
CX600-X8A-DO(V8) 2.5
CX600-X3A-DO(V8) 1.25
CX600-X3-DO(V8) 1.25
CX600-M2K-B 0.5
CX600-F1A-14H24Q 0.5
CX600-M8A-DO 1.0
CX600-M2H 0.5
CX6608 5
CX6620 10
CX6601-14H24Q 0.5
CX6602 0.5
CX6602-B 0.5
DASAN M3000 0.5
E628 1.25
E628-X 1.25
E652 1.25
E652-X 1.25
EGW2130 0.25
EGW2112GW 0.25
EGW2130W 0.25
EGW2160DC 0.25

iMaster NCE-IP
EGW2112GW(VDF) 0.25
EGW2160W 0.25
EGW2160 0.25
EGW2210 0.25
EGW2220DC 0.25
EGW2220 0.25
EGW3240 0.25
EGW3250 0.25
EGW3260 0.25
EGW3240DC 0.25
EGW3230 0.25
ETN500-B 0.25
ETN500-C 0.25
ETN500-A 0.25
ETN500-F 0.25
ETN550-A 1.0
Eudemon1000 0.5
Eudemon1000E-G15-AC 0.75
Eudemon1000E-G1-DC 0.75

iMaster NCE-IP
Eudemon1000E-U3 0.75
Eudemon1000E-F01 1
Eudemon1000E-F05 1
Eudemon1000E-F08 1
Eudemon1000E-F85 1
Eudemon1000E-F125 1
Eudemon1000E-F205 1
Eudemon1000E-F15 0.25
Eudemon1000E-D 0.75
Eudemon1000E-I 0.75
Eudemon1000E-N8 0.75
Eudemon1000E-N7E 0.75
Eudemon1000E-V2 0.75

iMaster NCE-IP
Eudemon1000E-X5 0.75
Eudemon1000E-X2-D 0.75
Eudemon100E 0.25
Eudemon200 0.25
Eudemon200E-B 0.25
Eudemon200E-F 0.25
Eudemon200E-F-D 0.25
Eudemon200E-C 0.25
Eudemon200E-BW 0.25
Eudemon200E-N5 0.75
Eudemon200E-N2 0.75
Eudemon200E-N1 0.75
Eudemon200E-N3 0.75
Eudemon200E-N1D 0.75
Eudemon200E-X1 0.25
Eudemon200E-X1AGW-C 0.25

iMaster NCE-IP
Eudemon200E-X1AGW-W 0.25
Eudemon200E-X1AW 0.25
Eudemon200E-X1W 0.25
Eudemon200E-X2 0.25
Eudemon200E-X2NEW 0.25
Eudemon200E-X2W 0.25
Eudemon200E-X2WNEW 0.25
Eudemon200E-X3 0.25
Eudemon200E-X5 0.25
Eudemon200E-X5DC 0.25
Eudemon200E-X6 0.25
Eudemon200E-X6DC 0.25
Eudemon200E-X7 0.25
Eudemon200S 0.25
Eudemon300 0.5
Eudemon500 0.5
Eudemon6080E 4.0
Eudemon8000E-V 4
Eudemon8160E 8.0
Eudemon8080E 4.0
Eudemon8000E-X3 1.5
Eudemon8000E-C 4.0
Eudemon8000E-D 8.0
Eudemon8000E-B 1.5
Eudemon8000E-X8 4.0
Eudemon8040 3.0
Eudemon8080 6.0
Eudemon9000E-X16 10
Eudemon 9000E-F8 5

iMaster NCE-IP
Eudemon 9000E-F4 5
Eudemon9000E-X4-AC 1.5
Eudemon9000E-X4-AC-OVS 1.5
Eudemon9000E-X4-DC 1.5
Eudemon9000E-X4-DC-OVS 1.5
Eudemon9000E-X8-AC 4.0
Eudemon9000E-X8-AC-OVS 4.0
Eudemon9000E-X8-DC 4.0
Eudemon9000E-X8-DC-OVS 4.0
FM12816 10.0
FM12804 6.0
FM12808 8.0
FM5855E-48T4S2Q 1.25
FM6865E-48S8CQ 1.25
FM6857E-48T6CQ 1.25
FM6857E-48S6CQ 1.25
FM6865-48S8CQ-SI 1.25
FM6870-48T6CQ-EI 1.25
FM6870-48S6CQ-EI 1.25
FM6865-48S8CQ-EI 1.25
FM6857-48S6CQ-EI 1.25
FM8850E-32CQ-EI 1
FM8868-4C-EI 1.25
FM8861-4C-EI 1.25
FM8850-64CQ-EI 1.25
FM8850-32CQ-EI 1.25
FM9860-4C-EI 2.0
FM-S5735S-H24T4X-A 1.0
FM-S5736-S48U4XC 1.0
FM-S5736-S48T4XC 1.0

iMaster NCE-IP
FM-S5736-S24U4XC 1.0
FM-S5736-S24T4XC 1.0
FM-S5736-S24UM4XC 1.0
FM-S5735S-H48U4XC-A 1.0
FM-S5735S-H48T4XC-A 1.0
FM-S5735S-H24S4XC-A 1.0
FM-S5735S-H24U4XC-A 1.0
FM-S5735S-H24T4XC-A 1.0
FM-S5735S-S48T4S-A 1.0
FM-S5735S-S48T4X-A 1.0
FM-S5735-S48T4X 1.0
FM-S5735-S24T4X 1.0
FM-S5735S-L48P4X-A1 1.0
FM-S5735S-L48T4X-A1 1.0
FM-S5735S-L48P4S-A1 1.0
FM-S5735S-L48T4S-A1 1.0
FM-S5735S-L32ST4X-A1 1.0
FM-S5735S-L24P4X-A1 1.0
FM-S5735S-L24T4X-A1 1.0
FM-S5735S-L24P4S-A1 1.0
FM-S5735S-L24T4S-A1 1.0
FM-S5735S-L8P4S-A1 1.0
FM-S5735S-L8T4S-A1 1.0
FM-S5735-L8P4X-IA1 1.0
FM-S5735-L8T4X-IA1 1.0
FM-S5735-L48P4X-A1 1.0
FM-S5735-L48T4X-A1 1.0
FM-S5735-L48P4S-A1 1.0
FM-S5735-L48T4S-A1 1.0
FM-S5735-L32ST4X-D1 1.0

iMaster NCE-IP
FM-S5735-L24P4X-A1 1.0
FM-S5735-L24P4S-A1 1.0
FM-S5735-L24T4S-A1 1.0
FM-S5735-L8P4X-A1 1.0
FM-S5735-L8T4X-A1 1.0
FM-S5735-L8P4S-A1 1.0
FM-S5720I-28X-PWH-SI-AC 1.0
FM-S5720I-28X-SI-AC 1.0
FM-S5720I-12X-PWH-SI-DC 1.0
FM-S5720I-12X-SI-AC 1.0
FM-S5720S-28P-LI-AC 1.0
FM-S5720S-12TP-PWR-LI-AC 1.0
FM-S5720S-12TP-LI-AC 1.0
FM-S5720-52X-LI-48S-AC1 1.0
FM-S5720-28P-LI-AC 1.0
FM-S5720-12TP-PWR-LI-AC 1.0
FM-S5720-12TP-LI-AC 1.0
FM-S5735-L32ST4X-A1 1.0
FM-S5735-L24T4X-IA1 1.0
FM-S5735-L24T4X-D1 1.0
FM-S5735-L8T4S-A1 1.0
FM-S5736-S48S4XC 1.0
FM-S5736-S24S4XC 1.0
FM-S5735-L24T4X-A1 1.0
FM-S6735-S24X6C 1.0
HG-FM CPE-01 1.5
HG-FM CPE-02 1
HG-FM CPE-03 2
USR20-8 0.0
USR20-6 0.0

iMaster NCE-IP
IaaS 1.0
iCache NE 0.0
iCache9200 CSS-HTTP 1.0
iCache9200 CSS-EM 1.0
iCache9200 CSS-PPS 1.0
iCache9200 CSS-QQL 1.0
iCache9200 CSS-PPL 1.0
iCache9200 CSS-WEB 1.0
iCache9200 CSS-BT 1.0
iCache9200 DSS 1.0
iCache9200 MSS 1.0
iCache9200 RSS 1.0
IPS6610E-K 1.0
IPS6515E-B-AC 0.75
IPS6535E-AC 0.75
IPS6525E-AC 0.75
IPS6555E-DC 0.75
IPS6555ED-AC 0.75
IPS6555E-AC 0.75
IPS6515E-AC 0.75
IPS6315E-AC 0.75
IPS6309E-AC 0.75
CE-IPSA 0.75
IPS6625FD 1
IPS6615FD 1
IPS6585FD 1
IPS6525FD 1
IPS6525F 1
IPS6315F 1
IPS6309F 1

iMaster NCE-IP
IPS6520F-K 1
IPS12008F 5
IPS12004F 5
IPS6620F-K 1
IPS6655F 1
IPS6585F 0.25
IPS6615F 0.25
IPS6625F 0.25
IPS12004-DC 1.5
IPS12004-AC 1.5
IPS12008-AC 4.0
IPS12008-DC 4.0
JUNIPER MX480 2.5
MA5200 0.0
MA5200E 1.5
MA5200F 1.5
MA5200G-8 10.0
MA5200G-4 10.0
MA5200G-2 10.0
ME60-4 10.0
ME60-X16 10.0
ME60-X8 10.0
ME60-X3 10.0
ME60-8 10.0
ME60-16 10.0
ME60-X3 10.0
ME60-X8 10.0
ME60-X16 10.0
ME60-X2-M8 10.0
ME60-X2-M8A 10.0

iMaster NCE-IP
ME60-X2-M16A 10.0
ME60-X2-M16 10.0
ME60-X8A(V8) 10.0
ME60-X16A(V8) 10.0
NE05 0.75
NE05E-SM 0.5
NE05E-SL 0.5
NE05E-SK 0.5
NE05E-SJ 0.5
NE05E-SI 0.5
NE05E-SH 0.5
NE05E-SG 0.5
NE05E-SN 0.5
NE05E-S2 0.5
NE05E-SF 0.5
NE05E-SE 0.5
NE05E-SR 1.0
NE05E-S2(V8) 0.5
NE05E-SQ 1.0
NE08E 0.75
NE08 0.75
NE08E-S6 1.0
NE08E-S6E 1.0
NE08E-S9 1
NE16E 0.75
NE16 0.75
NE16EX-6 0.25
NE16EX 0.25
NE20-X3 2
NE20-8 1.25

iMaster NCE-IP
NE20-4 1.25
NE20-2 1.25
NE20E-S16B 1.0
NE20E-X6 1.25
NE20E-8 1.25
NE20E-S8 1.0
NE20E-S2E 0.5
NE20E-S8A 1.0
NE20E-S16A 1.0
NE20E-S2F 0.5
NE20E-S16 1.0
NE20E-S4 0.5
NE40-4 5.0
NE40-8 5.0
NE40-2 5.0
NE40E-X2 1.0
NE40E-X1 0.5
NE40E 2.5
NE40E-X16 5.0
NE40E-X16A 5.0
NE40E-X8 2.5
NE40E-X3 1.25
NE40E-4 1.25
NE40E-X2-M14-IOT 1
NE40E-X3 1.25
NE40E-X3A 1.25
NE40E-X4A-IOT(V8) 1.25
NE40E-X4A(V8) 1.25
NE40E-X8AK(V8) 2.5
NE40E-X8AK-IOT(V8) 2.5

iMaster NCE-IP
NE40E-X16C(V8) 5.0
NE40E-X8C(V8) 2.5
NE40E-X8C-IOT(V8) 2.5
NE40E-X2-M14 1
NE40E-F1A-14H24Q 0.5
NE40E-M16A 1.0
NE40E-M8A 1.0
NE40E-M2K 0.5
NE40E-X1-M4 0.5
NE40E-X2-M16 1.0
NE40E-X16(V8) 5.0
NE40E-X8A(V8) 2.5
NE40E-X2-M16A 1.0
NE40E-X2-M8A 1.0
NE40E-M2F 0.5
NE40E-M2E 0.5
NE40E-X16A(V8) 5.0
NE40E-X8(V8) 2.5
NE40E-X2-M8 1.0
NE40E-X16C-IOT(V8) 5.0
NE40E-M2K-B 0.5
NE80E-DPI 0.0
NE40E-DPI 0.0
NE40E80E-DPI Server 0.0
NE40E-FW 4.0
NE80E-FW 8.0
NE40E-M2H 0.5
NE40E-X16B 5
NE5000 0.0
NE5000E-BTB 10.0

iMaster NCE-IP
NE5000E-Multi 10.0
NE5000E 10.0
NE5000E-Multi-S(V8) 10.0
NE5000E-Multi(V8) 10.0
NE5000E(V8) 10.0
NE5000E-S 10.0
NE5000E-BTB(V8) 10.0
NE80 5.0
NE80E 5.0
NE9000-8-LS 5.0
NE9000-20-ADMIN 10.0
NE9000-20-LS 10.0
NE9000-8-ADMIN 5.0
NE9000 10.0
NE9000-8 5.0
NetEngine 8000E M4 1
NetEngine 8000 M4 2.5
NetEngine 8000E F8 5
NetEngine 8000E F8-Z 5
NetEngine 8000 M1D-B 2.5
NetEngine 8000 F8 5
NetEngine 8100 M14 5
NetEngine 8100 X8 5
NetEngine 8000E M14-Z 2.5
NetEngine 8000E X16 10
NetEngine 8000 X16 10
NetEngine 8000E M14 2.5
NetEngine 8000E M8 2.5
NetEngine 8000 M1A 0.5

iMaster NCE-IP
NetEngine 8000 F1A-8H20Q-E 0.5
NetEngine 8000 F2A-8K36H 1
NetEngine 8000 F1A-8H20Q 0.5
NetEngine 8000E X8 2.5
NetEngine 8000 M1D 0.5
NetEngine 8000 M6K 0.5
NetEngine 8000 M14K 1
NetEngine 8000 M8K 1
NetEngine 8000 X8 2.5
NetEngine 8000 X4 2.5
NetEngine 8000 M8 1
NetEngine 8000 M1C 0.5
NetEngine 8000E M4-PTN 1
NetEngine 8000 M4-PTN 2.5
NetEngine 8000E F8-PTN 5
NetEngine 8000 M1D-B-IOT 2.5
NetEngine 8000 F8-PTN 5
NetEngine 8100 X8-PTN 5
NetEngine 8000E X16-PTN 10
NetEngine 8000 X16-PTN 10
NetEngine 8000E M14-PTN 2.5
NetEngine 8000E M8-PTN 2.5
NetEngine 8000 X8-IOT 2.5
NetEngine 8000 M1A-IOT 0.5
NetEngine 8000 F1A-8H20Q-E- 0.5

PTN
NetEngine 8000 F2A-8K36H-PTN 1
NetEngine 8000 F1A-8H20Q-IOT 0.5

iMaster NCE-IP
NetEngine 8000E X8-IOT 2.5
NetEngine 8000 M1C-IOT 0.5
NetEngine 8000 M1D-IOT 0.5
NetEngine 8000 M6-IOT 0.5
NetEngine 8000 M6K-IOT 0.5
NetEngine 8000 M14K-IOT 1
NetEngine 8000 M8K-IOT 1
NetEngine 8000 X4-IOT 2.5
NetEngine 8000 M14-IOT 1.0
NetEngine 8000 M8-IOT 1
NetEngine A835 T 2.5
NetEngine A813 0.5
NetEngine A813 E 0.5
NetEngine A822 E 0.5
NetEngine A825 T 1
NetEngine A815 T 1
NetEngine A831 E 1
NetEngine A821 E 1
NetEngine A821 1
NetEngine A811 M 1
NetEngine A811 1
NetEngine A810 1
NetEngine A831 E-L2 1
NetEngine A811 M-IOT 1
NetEngine A811-IOT 1
NetEngine A810-IOT 1
NetEngine A810 M 1
NetEngine A813 M 1
NetEngine A850 M 1
CE-FWA 0.75

iMaster NCE-IP
LE1D2FW00S01 0.75
NIP6620E-DC 0.75
NIP6650ED-AC 0.75
NIP6620E 0.75
NIP6610E 0.75
NIP6550E 0.75
NIP6510E 0.75
NIP6310E 0.75
NIP6305E 0.75
NIP6610 0.75
NIP6320D 0.75
NIP6330D 0.75
NIP6620D 0.75
NIP6650D 0.75
NIP6860-DC 0.75
NIP6830 0.75
NIP6680 0.75
NIP6650 0.75
NIP6620 0.75
NIP6330 0.75
NIP6320 0.75
NOKIA 7750 SR-7 1.5
NSE1000 0.0
NSE1000-4 0.0
OP-ByPass 0.25
PTN 6900-1 0.5
PTN 6900-2 1.0
PTN 6900-3 1.25
PTN 6900-8 2.5
PTN 6900-16 5.0

iMaster NCE-IP
PTN2900-1 0.0
PTN6900-1 0.0
PTN 6900-2-M4-IOT 2.5
PTN 6900-2-M4 2.5
PTN 6900-2-M14-IOT 1.0
PTN 6900-2-M8C-IOT 0.5
PTN 6900-2-M16A 1.0
PTN 6900-2-M8A 1.0
PTN 6900-16A(V8) 5.0
PTN 6900-8A(V8) 2.5
PTN 6900-F1A-14H24Q 0.5
PTN 6900-2-M8C 0.5
PTN 6900-2-M14 1.0
PTN 6900-1-M4 0.5
PTN 6900-2-M16 1.0
PTN 6900-M2F 0.5
PTN 6900-3A(V8) 1.25
PTN 6900-8(V8) 2.5
PTN 6900-16(V8) 5.0
PTN 6900-3(V8) 1.25
PTN 6900-M2E 0.5
PTN 6900-2-M8 1.0
PTN 6900-M2K 0.5
PTN 6900-M2K-B 0.5
OptiX PTN 7900-32 5.5
OptiX PTN 7900-12 4.5
OptiX PTN 7900E-24 5
OptiX PTN 7900E-32 5.5
OptiX PTN 7900-24 5
OptiX PTN 7900E-12 4.5

iMaster NCE-IP
OptiX PTN 905D 0.4
OptiX PTN 905E 0.400
OptiX PTN 905G 0.400
OptiX PTN 910D-F 1
OptiX PTN 910E-F 0.5
OptiX PTN 916-F 0.5
OptiX PTN 917-F 1
OptiX PTN 91A-F 1
OptiX PTN 930 2.5
OptiX PTN 960(160G) 1.5
OptiX PTN 970 2.500
OptiX PTN 970C 2.5
OptiX PTN 980 2.0
OptiX PTN 980B 2.0
OptiX PTN 990 2.500
OptiX PTN 990B 2.5
OptiX PTN 990E 2.500
R1615 1.0
R1614 1.0
R1613 1.0
R1612 1.0
R1600[03][03E][04] 1.0
R1602 1.0
R1760 1.0
R2509 1.0
R2509E 1.0
R2501E 1.0
R2511 1.0
R2501 1.0
R2511E 1.0

iMaster NCE-IP
R2610[-RPS] 1.0
R2630[E] 1.0
R2631[E][E-RPS] 1.0
R2621 1.0
R2620 1.0
R2611[-RPS] 1.0
R3680[E][E-RPS] 1.0
R3640[E] 1.0
R4001 1.0
R4001E 1.0
RADIUS Proxy 0.25
RADIUS Proxy-DPI 0.25
RM9000 1.0
S12700E-4 6.0
S12710 6.0
S12700E-12 9.0
S12700E-8 6.0
S12708 6.0
S12704 6.0
S12712 9.0
S2026 0.125
S2026C 0.125
S2008CT 0.125
S2403H-HI 0.125
S2403TP-MI-AC 0.125
S2008TP-MI-AC 0.125
S2016TP-MI 0.125
S2016-HI 0.125
S2008-HI 0.125
S2008CP 0.125

iMaster NCE-IP
S2016-EI 0.125
S2008-EI 0.125
S2403H-EI 0.125
S2026Z 0.125
S2403H 0.125
S2403F 0.125
S2016 0.125
S2008 0.125
S2008B 0.125
S2026B 0.125
S2016B 0.125
S2024C 0.125
S2016C 0.125
S2008C 0.125
S2008TP-EA 0.125
S2403TP-EA 0.125
S2403TP-PWR-EA 0.125
S2016TP-PWR-EA 0.125
S2016TP-EA 0.125
S2320-52TP-EI-DC 0.625
S2x00_COMM 0.625
S2318P-SI 0.625
S2309P-SI 0.625
S2352P-SI 0.625
S2309TP-SI 0.625
S2318TP-SI 0.625
S2326TP-SI 0.625
S2309TP-PWR-EI 0.625
S2328P-EI-AC 0.625
S2350-28TP-PWR-EI-AC 1.25

iMaster NCE-IP
S2350-28TP-EI-DC 1.25
S2320-12TP-EI-DC 0.625
S2320-28P-PWR-EI-ACF 0.625
S2320-52TP-PWR-EI-AC 0.625
S2320-28TP-EI-AC 0.625
S2320-28TP-EI-DC 0.625
S2320-28TP-PWR-EI-AC 0.625
S2320-52TP-EI-AC 0.625
S2320-12TP-PWR-EI-AC 0.625
S2320-12TP-EI-AC 0.625
S2350-20TP-PWR-EI-AC 1.25
S2350-28TP-EI-AC 1.25
S2326TP-PWR-EI 0.625
S2326TP-EI 0.625
S2318TP-EI 0.625
S2309TP-EI 0.625
S2352P-EI 0.625
S2309P-EI 0.625
S2318P-EI 0.625
S2326P-EI 0.625
S2326P-SI 0.625
S200-48T4S 0.625
S200-24P4S 0.625
S200-24T4S 0.625
S200-8P4S 0.625
S200-8T4S 0.625
S1730S-S48P4S-A1 0.625
S1730S-S48T4X-A1 0.625
S1730S-S48T4S-A1 0.625
S1730S-S24P4S-A1 0.625

iMaster NCE-IP
S1730S-S24T4X-A1 0.625
S1730S-S24T4S-A1 0.625
S1730S-S8P4S-A1 0.625
S1730S-S8T4S-A1 0.625
S2730S-S48FT4S-A 0.625
S2730S-S16FP4S-A 0.625
S2730S-S24FP4S-A 0.625
S2730S-S16FT4S-A 0.625
S2730S-S24FT4S-A 0.625
S2730S-S8FP4S-A 0.625
S2730S-S8FT4S-A 0.625
S1730S-H24T4S-A 0.625
S1730S-S24T4X-A 0.625
S1730S-H48T4S-A 0.625
S1730S-S48P4S-A 0.625
S1730S-S24T4S-MA 0.625
S1730S-S24P4S-MA 0.625
S1730S-S48T4S-A 0.625
S1730S-S24P4S-A 0.625
S1730S-S24T4S-A 0.625
S2720S-28TP-EI-AC 0.625
S2720S-28TP-PWR-EI-AC 0.625
S2720S-28TP-PWR-EI-L-AC 0.625
S2720S-52TP-EI-AC 0.625
S2720S-12TP-EI-AC 0.625
S1720-10GW-2P-E 0.625
S2700-9TP-EI-AC 0.625
S2700-18TP-EI-AC 0.625

iMaster NCE-IP
S2700-26TP-EI-DC 0.625
S2700-9TP-SI-AC 0.625
S2700-26TP-SI-AC 0.625
S2700-26TP-PWR-EI 0.625
S2710-52P-SI-AC 0.625
S2700-52P-PWR-EI 0.625
S2750-28TP-EI-AC 0.625
S2750-28TP-PWR-EI-AC 0.625
S2720-12TP-EI-AC 0.625
S2720-52TP-EI-AC 0.625
S2720-28TP-PWR-EI-ACL 0.625
S2720-28TP-EI-V2-AC 0.625
S2720-28TP-PWR-EI-AC 0.625
S2720-52TP-PWR-EI-AC 0.625
S2720-12TP-PWR-EI-AC 0.625
S2750-20TP-PWR-EI-AC 0.625
S2751-28TP-PWR-EI-AC 0.625
S2710-52P-PWR-SI 0.625
S2710-26TP-PWR-SI 0.625
S2700-9TP-PWR-EI 0.625
S2700-18TP-SI-AC 0.625
S2700-52P-EI-AC 0.625
S2700-26TP-EI-AC 0.625
S2700-9TP-EI-DC 0.625
S3025[S2024] 0.125
S3026E-FM 0.125
S3026C-24[12FS] 0.125
S3026G-SI 0.125
S3026V 0.125
S3026PWR 0.125

iMaster NCE-IP
S3026S-SI 0.125
S3026C-SI 0.125
S3026T 0.125
S3026G 0.125
S3026C-24[12FM] 0.125
S3026C 0.125
S3050 0.125
S3026E-FS 0.125
S3026E 0.125
S3026FM[FS] 0.125
S3026 0.125
S3352P-EI 0.75
S3352P-EI-24S 0.75
S3352P-PWR-EI 0.75
S3300-52P-EI 0.75
S3326C-HI 0.75
S3318P-EI-MC 0.75
S3328TP-EI-MC 0.75
S3328TP-PWR-EI 0.75
S3352P-SI-48S 0.75
S3352P-EI-48S 0.75
S3328TP-EI-24S 0.75
S3328TP-EI 0.75
S3328TP-SI 0.75
S3352P-SI 0.75
S3526E 0.125
S3526FM[FS] 0.125
S3526 0.125
S3526C 0.125
S3552F-HI 0.125

iMaster NCE-IP
S3552F-EI 0.125
S3552F-SI 0.125
S3528P 0.125
S3528G 0.125
S3552P 0.125
S3552G 0.125
S3526C-24[12FM] 0.125
S3526C-24[12FS] 0.125
S3526E-FS 0.125
S3526E-FM 0.125
S3528P-EA 0.125
S3528F-EA 0.125
S3552F-EA 0.25
S3528TP-EA 0.125
S3552P-EA 0.125
S3700-28TP-EI-DC 0.75
S3700-52P-EI-AC 0.75
S3700-52P-EI-24S-AC 0.75
S3700-52P-EI-48S-AC 0.75
S3700-28TP-SI-AC 0.75
S3700-52P-SI-AC 0.75
S3700-52P-PWR-EI 0.75
S3700-26C-HI 0.75
S3700-28TP-PWR-SI 0.75
S3700-52P-PWR-SI 0.75
S3700-28TP-EI-MC-AC 0.75
S3700-28TP-PWR-EI 0.75
S3700-28TP-SI-DC 0.75
S3700-52P-EI-48S-DC 0.75
S3700-52P-EI-24S-DC 0.75

iMaster NCE-IP
S3700-52P-EI-DC 0.75
S3700-28TP-EI-24S-AC 0.75
S3700-28TP-EI-AC 0.75
S3900-52SI 0.125
S3928TP-SI 0.125
S3900-28SI 0.125
S3900-24SI 0.125
S3900-52EI 0.125
S3952P-PWR-EI 0.125
S3928P-SI-ACDC 0.125
S3928F-EI 0.125
S3928P-PWR-EI 0.125
S3900-28EI 0.125
S5012G 0.25
S5024G-24[20TP-DC] 0.25
S5024G-24[20TP] 0.25
S5012T-12[10GBC-DC] 0.25
S5012T-12[10GBC] 0.25
S5012G-DC 0.25
S5148P-EI 0.25
S5150C-EI 0.25
S5126C-EI 0.25
S5124P-EI 0.25
S5331-S24S8T4X-D 1.0
S5331-S24S8T4X-A 1.0
S5531-S32ST4X 1.0
S5531-H48HB4XZ 1.0
S5335-L8P2T4X-A-V2 1.0
S5335-S48U4XE-V2 1.0
S5335-S24U4XE-V2 1.0

iMaster NCE-IP
S5335-S48P4XE-V2 1.0
S5335-S48T4XE-V2 1.0
S5335-L48T4XE-A-V2 1.0
S5335-S24P4XE-V2 1.0
S5335-L24P4XE-A-V2 1.0
S5335-S24T4XE-V2 1.0
S5335-L24T4XE-D-V2 1.0
S5335-L24T4XE-A-V2 1.0
S5335-L16T4X-A-V2 1.0
S5335-L10T4X-D-V2 1.0
S5335-L10T4X-A-V2 1.0
S5320-52P-LI-AC-SEA 1.25
S5320-28P-LI-AC-SEA 1.25
S5331-S24N4X2Q-A 1.0
S5331-S24P4X 1.0
S5331-S48P4X 1.0
S5331-S24T4X-D 1.0
S5331-S24T4X-A 1.0
S5331-S48T4X-A 1.0
S5331-S24T4X 1.0
S5331-S48T4X 1.0
S5331-S32ST4X 1.0
S5331-S32ST4X-D 1.0
S5331-S32ST4X-A 1.0
S5331-S48S4X 1.0
S5331-S48S4X-D 1.0
S5331-S48S4X-A 1.0
S5335-L8T4X-A1 1.25
S5335-L8P4X-A1 1.25
S5335-L8T4X-D1 1.25

iMaster NCE-IP
S5335-L24T4X-A1 1.25
S5335-L24T4X-D1 1.25
S5335-L24P4X-A1 1.25
S5335-L48T4X-A1 1.25
S5335-L32ST4X-A1 1.25
S5335-L32ST4X-D1 1.25
S5336-S24S4X-D 1.25
S5320-52X-LI-24S-AC1 1.25
S5320-52X-LI-48S-DC1 1.25
S5320-52X-LI-48S-AC1 1.25
S5336-S48S4X-D 1.25
S5336-S48S4X-A 1.25
S5336-S48S4XC 1.25
S5336-S24S4XC 1.25
S5336-S48U4XC 1.25
S5336-S24U4XC 1.25
S5336-S48T4XC 1.25
S5336-S24T4XC 1.25
S5336-S24UM4XC 1.25
S5335-L32ST4X-D 1.25
S5335-L12T4S-D 1.25
S5335-L24T4X-D 1.25
S5332-H24UM2CC 1.25
S5335-L12T4S-A 1.25
S5332-H24S4Y4Q 1.25
S5335-L48T4X-A 1.25
S5335-S32ST4X 1.25
S5335-L32ST4X-A 1.25
S5335-S48S4X 1.25
S5335-S48P4X 1.25

iMaster NCE-IP
S5335-S48T4X 1.25
S5335-S24P4X 1.25
S5335-S24T4X 1.25
S5335-L24P4X-A 1.25
S5335-L12P4S-A 1.25
S5335-L24T4X-A 1.25
S5332-H48S6Q 1.25
S5332-H24S6Q 1.25
S5331-H48P4XC 1.25
S5331-H48T4XC 1.25
S5331-H24P4XC 1.25
S5331-H24T4XC 1.25
S5320-52X-SI-48S 1.25
S5320-52X-LI-48S-DC 1.25
S5320-52X-LI-48S-AC 1.25
S5330-36C-HI-24S 1.25
S5330-60C-HI-48S 1.25
S5330-68C-SI-DC 1.25
S5328C-EI-24S 1.25
S5328C-SI 1.25
S5328C-PWR-SI 1.25
S5352C-PWR-EI 1.25
S5328C-PWR-EI 1.25
S5352C-PWR-SI 1.25
S5348TP-PWR-SI 1.25
S5324TP-PWR-SI 1.25
S5352C-SI 1.25
S5348TP-SI 1.25
S5324TP-SI 1.25
S5352C-EI 1.25

iMaster NCE-IP
S5328C-EI 1.25
S5328C-HI 1.25
S5320-36PC-EI-DC 1.25
S5320-56C-EI-DC 1.25
S5320-56PC-EI-DC 1.25
S5320-36C-PWR-EI-DC 1.25
S5320-32X-EI-24S-AC 1.25
S5320-50X-EI-46S-AC 1.25
S5320-32X-EI-AC 1.25
S5320-32P-EI-AC 1.25
S5320-52X-EI-AC 1.25
S5320-52P-EI-AC 1.25
S5320-50X-EI-AC 1.25
S5321-28P-SI-AC 1.25
S5321-28X-SI-DC 1.25
S5321-52X-SI-AC 1.25
S5321-52X-SI-DC 1.25
S5320-28X-SI-AC 1.25
S5320-52X-SI-AC 1.25
S5320-52X-PWR-SI-AC 1.25
S5300-10P-PWR-LI-AC 1.25
S5320-28X-SI-DC 1.25
S5320-56C-HI-AC 1.25
S5320-32C-HI-24S-DC 1.25
S5320-12TP-LI-AC 1.25
S5321-28X-SI-24S-AC 1.25
S5320-28X-LI-AC 1.25
S5320-28P-PWR-LI-AC 1.25
S5320-52P-LI-AC 1.25
S5320-52X-LI-DC 1.25

iMaster NCE-IP
S5328C-HI-24S 1.25
S5300-28C-PWR-EI 1.25
S5300-28P-LI-AC 1.25
S5300-52P-LI-AC 1.25
S5300-10P-LI-AC 1.25
S5310-52C-EI 1.25
S5300-28X-LI-AC 1.25
S5300-28X-LI-24S-AC 1.25
S5300-28P-LI-BAT 1.25
S5300-28P-LI-24S-BAT 1.25
S5300-52X-LI-48CS-AC 1.25
S5300-52X-LI-AC 1.25
S5320-36C-EI-28S-AC 1.25
S5320-56C-EI-48S-AC 1.25
S5320-36C-EI-AC 1.25
S5320-52P-PWR-LI-AC 1.25
S5320-28X-LI-24S-AC 1.25
S5320-28X-PWR-SI-DC 1.25
S5320-28P-SI-DC 1.25
S5320-56C-PWR-EI-ACF 1.25
S5320-28X-PWR-SI 1.25
S5320-28P-SI 1.25
S5320-28X-SI 1.25
S5320-36C-EI 1.25
S5320-52P-PWR-LI-AC 1.25
S5320-28TP-LI-AC 1.25
S5320-28X-SI-24S-AC 1.25
S5330-68C-SI-AC 1.25
S5x00_L3_COMM 1.25
S5x00_MPLS_COMM 1.25

iMaster NCE-IP
S5330-68C-SI 1.25
S5320-28X-SI-24S-DC 1.25
S5320-12P-LI-BAT 1.25
S5320-12X-PWR-LI-AC 1.25
S5320-28P-PWR-LI-AC 1.25
S5320-36C-EI-28S 1.25
S5320-56C-EI 1.25
S5320-52X-SI 1.25
S5320-28P-LI-AC 1.25
S5320-52X-PWR-SI 1.25
S5320-12TP-LI-DC 1.25
S5320-52P-SI-DC 1.25
S5320-52X-PWR-SI-DC 1.25
S5320-28X-LI-24S-DC 1.25
S5320-52X-PWR-LI-AC 1.25
S5320-36C-EI-DC 1.25
S5320-56C-EI-48S-DC 1.25
S5320-36C-EI-28S-DC 1.25
S5300-52X-LI-DC 1.25
S5300-52X-LI-48CS-DC 1.25
S5300-28P-LI-24S-4AH 1.25
S5300-28P-LI-4AH 1.25
S5300-COMM 1.25
S5300-28X-LI-24S-DC 1.25
S5300-28X-LI-DC 1.25
S5310-28C-EI 1.25
S5300-52P-LI-DC 1.25
S5300-28P-LI-DC 1.25
S5300-52C-PWR-EI 1.25
S5306TP-LI-AC 1.25

iMaster NCE-IP
S5320-52X-LI-AC 1.25
S5320-28X-PWR-LI-AC 1.25
S5320-28X-LI-DC 1.25
S5321-28X-SI-24S-DC 1.25
S5320-12TP-PWR-LI-AC 1.25
S5320-32C-HI-24S-AC 1.25
S5320-56C-HI-DC 1.25
S5320-52X-SI-DC 1.25
S5320-52X-PWR-SI-ACF 1.25
S5320-28X-PWR-SI-AC 1.25
S5320-52P-SI-AC 1.25
S5320-28P-SI-AC 1.25
S5321-52P-SI-AC 1.25
S5321-28X-SI-AC 1.25
S5320-50X-EI-DC 1.25
S5320-52P-EI-DC 1.25
S5320-52X-EI-DC 1.25
S5320-32P-EI-DC 1.25
S5320-32X-EI-DC 1.25
S5320-50X-EI-46S-DC 1.25
S5320-32X-EI-24S-DC 1.25
S5320-56C-PWR-EI-AC 1.25
S5320-36C-PWR-EI-AC 1.25
S5320-56PC-EI-AC 1.25
S5320-56C-EI-AC 1.25
S5320-36PC-EI-AC 1.25
S5336-S24S4X-A 1.25
S5516 0.25
S5624P-PWR 0.25

iMaster NCE-IP
S5648P-PWR 0.25
S5628C-HI-AC/DC 0.25
S5652C-HI-AC/DC 0.25
S5652C-PWR-HI 0.25
S5628C-PWR-HI 0.25
S5628F-HI 0.25
S5624F 0.25
S5648P 0.25
S5624P 0.25
S5735I-S8U4XN-V2 1.0
S5735-S48P4XE-V2 1.0
S5735-S24P4XE-V2 1.0
S5735-L48T4XE-A-V2 1.0
S5735-L24T4X-QA-V2 1.0
S5735-L16T4X-QA-V2 1.0
S5735-L10T4X-A-V2 1.0
S5735-L8T4X-QA-V2 1.0
S5732-H48UM4Y2CZ-TV2 1.0
S5732-H24S4X6QZ-TV2 1.0
S5731S-S8UM16UN2Q-A 1.0
S5731S-S24UN4X2Q-A 1.0
S5731S-S24N4X2Q-A1 1.0
S5731-S8UM16UN2Q 1.0
S5731-S24UN4X2Q 1.0
S5731-S24N4X2Q-A 1.0
S5731-S48P4X-A 1.0
S5731-S24T4X-D 1.0
S5731S-S24T4X-A1 1.0
S5731-S24T4X-A 1.0
S5731S-S48T4X-A1 1.0

iMaster NCE-IP
S5731-S48T4X-A 1.0
S5731S-S48P4X-A1 1.0
S5731S-H24HB4XZ-A 1.0
S5731-H24HB4XZ 1.0
S5731S-H48HB4XZ-A 1.0
S5731-H48HB4XZ 1.0
S5731S-S32ST4X-A 1.0
S5731S-S32ST4X-A1 1.0
S5731S-S48S4X-A 1.0
S5731S-S48S4X-A1 1.0
S5731-S32ST4X 1.0
S5731-S32ST4X-D 1.0
S5731-S32ST4X-A 1.0
S5731-S48S4X 1.0
S5731-S48S4X-A 1.0
S5735-L8P4S-QA1 1.25
S5735S-L24P4S-MA 1.25
S5735-L24T4S-QA1 1.25
S5735-L24T4X-QA1 1.25
S5735-L8T4S-QA1 1.25
S5735-L24T4X-IA1 1.25
S5735-L8P4X-IA1 1.25
S5735-L8T4X-IA1 1.25
S5736-S48S4X-A 1.25
S5736-S48S4X-D 1.25
S300-48T4S 1.25
S300-16P4S 1.25
S300-24P4S 1.25
S300-16T4S 1.25
S300-24T4S 1.25

iMaster NCE-IP
S300-8P4S 1.25
S300-8T4S 1.25
S500-32ST4X 1.25
S500-48T4S 1.25
S500-16P4S 1.25
S500-24P4S 1.25
S500-16T4S 1.25
S500-24T4S 1.25
S500-8P4S 1.25
S500-8T4S 1.25
S5735S-L8T4S-A1 1.25
S5735S-L32ST4X-A1 1.25
S5735S-L48P4X-A1 1.25
S5735S-L48P4S-A1 1.25
S5735S-L48T4X-A1 1.25
S5735S-L48T4S-A1 1.25
S5735S-L24P4X-A1 1.25
S5735S-L24P4S-A1 1.25
S5735S-L24T4X-A1 1.25
S5735S-L24T4S-A1 1.25
S5735S-L8P4S-A1 1.25
S5735-L8T4X-A1 1.25
S5735-L8T4S-A1 1.25
S5735-L8P4X-A1 1.25
S5735-L8P4S-A1 1.25
S5735-L24T4X-D1 1.25
S5735-L24T4S-A1 1.25
S5735-L24P4X-A1 1.25
S5735-L24P4S-A1 1.25
S5735-L48T4X-A1 1.25

iMaster NCE-IP
S5735-L48T4S-A1 1.25
S5735-L48P4X-A1 1.25
S5735-L48P4S-A1 1.25
S5735-L24T4X-A1 1.25
S5735-L32ST4X-A1 1.25
S5735-L32ST4X-D1 1.25
S5720S-52X-LI-24S-AC1 1.25
S5720-52X-LI-24S-AC1 1.25
S5720-52X-LI-48S-DC1 1.25
S5720-52X-LI-48S-AC1 1.25
S5731-H48T4XC-B 1.25
S5736-S48S4XC 1.25
S5735S-H24S4XC-A 1.25
S5736-S24S4XC 1.25
S5735S-H48U4XC-A 1.25
S5736-S48U4XC 1.25
S5735S-H24U4XC-A 1.25
S5736-S24U4XC 1.25
S5735S-H48T4XC-A 1.25
S5736-S48T4XC 1.25
S5735S-H24T4XC-A 1.25
S5736-S24T4XC 1.25
S5736-S24UM4XC 1.25
S5732-H48UM2C-K 1.25
S5732-H24UM2C-K 1.25
S5735-L32ST4X-D 1.25
S5735-L12T4S-D 1.25
S5735-L24T4X-D 1.25
S5735S-S48T4X-A 1.25
S5731S-H24T4X-A 1.25

iMaster NCE-IP
S5735S-L48T4S-MA 1.25
S5735S-S48P4X-A 1.25
S5735S-S24T4X-A 1.25
S5731S-H48T4X-A 1.25
S5735S-S24P4X-A 1.25
S5735-S24T4X-I 1.25
S5732-H48XUM2CC 1.25
S5732-H24S4Y4Q 1.25
S5732-H48UM2CC 1.25
S5732-H24UM2CC 1.25
S5732-H48S6Q-K 1.25
S5732-H24S6Q-K 1.25
S5731-H24P4XC-K 1.25
S5731-H24T4XC-K 1.25
S5731-H48P4XC-K 1.25
S5731S-H48T4S-A 1.25
S5731S-H24T4S-A 1.25
S5735-S8P2X-IA200H1 1.25
S5735-S8P2X-IA200G1 1.25
S5735-S4T2X-IA150G1 1.25
S5735S-L48FT4S-A 1.25
S5735S-S32ST4X-A 1.25
S5735-S32ST4X 1.25
S5735S-L32ST4X-A 1.25
S5735-L32ST4X-A 1.25
S5735S-L12T4S-A 1.25
S5735-L12T4S-A 1.25
S5735S-L24FT4S-A 1.25
S5735S-L24T4S-MA 1.25
S5720-28P-PWR-LI-AC-SEA 1.25

iMaster NCE-IP
S5735-S48S4X 1.25
S5735S-L48P4S-A 1.25
S5735S-L48P4X-A 1.25
S5735-L48P4X-A 1.25
S5735-S48P4X 1.25
S5735S-S48T4S-A 1.25
S5735-S48T4X 1.25
S5735-S24P4X 1.25
S5735S-S24T4S-A 1.25
S5735-S24T4X 1.25
S5735S-L48T4X-A 1.25
S5735-L48T4X-A 1.25
S5735S-L48T4S-A 1.25
S5735-L48T4S-A 1.25
S5735S-L24P4X-A 1.25
S5735-L24P4X-A 1.25
S5735S-L24P4S-A 1.25
S5735-L24P4S-A 1.25
S5735S-L12P4S-A 1.25
S5735-L12P4S-A 1.25
S5735S-L24T4X-A 1.25
S5731S-H48T4XC-A 1.25
S5735-L24T4X-A 1.25
S5735S-L24T4S-A 1.25
S5735-L24T4S-A 1.25
S5731S-H24T4XC-A 1.25
S5732-H48S6Q 1.25
S5732-H24S6Q 1.25
S5731S-S48P4X-A 1.25
S5731-S48P4X 1.25

iMaster NCE-IP
S5731S-S48T4X-A 1.25
S5731-S48T4X 1.25
S5731S-S24P4X-A 1.25
S5731-S24P4X 1.25
S5731S-S24T4X-A 1.25
S5731-S24T4X 1.25
S5731-H48P4XC 1.25
S5731-H24P4XC 1.25
S5731-H48T4XC 1.25
S5731-H24T4XC 1.25
S5720SV2-52P-LI-AC 1.25
S5720SV2-28P-LI-AC 1.25
S5720-28X-PWR-LI-ACF 1.25
S5720I-6X-PWH-SI-AC 1.25
S5720-52X-SI-48S 1.25
S5720-52X-LI-48S-AC 1.25
S5730-60C-HI-48S 1.25
S5730-36C-HI-24S 1.25
S5730-68C-HI-48S 1.25
S5730-44C-HI-24S 1.25
S5720I-28X-SI-AC 1.25
S5720I-12X-PWH-SI-DC 1.25
S5720I-12X-SI-AC 1.25
S5730-68C-PWH-HI 1.25
S5730-60C-PWH-HI 1.25
S5730-68C-HI 1.25
S5730-60C-HI 1.25

iMaster NCE-IP
S5730-44C-PWH-HI 1.25
S5730-36C-PWH-HI 1.25
S5730-36C-HI 1.25
S5730-44C-HI 1.25
S5720-52X-PWR-LI-ACF 1.25
S5730S-68C-PWR-EI 1.25
S5730S-68C-EI-AC 1.25
S5730S-48C-PWR-EI 1.25
S5730S-48C-EI-AC 1.25
S5730-56C-PWH-SI-AC 1.25
S5730-32C-PWH-SI-AC 1.25
S5730-52X-PWH-SI-ACF 1.25
S5700-28C-EI 1.25
S5700-28C-SI 1.25
S5700-28C-EI-24S 1.25
S5700-52C-EI 1.25
S5700-24TP-SI-AC 1.25
S5700-48TP-SI-AC 1.25
S5700-28C-PWR-EI 1.25
S5700-24TP-PWR-SI 1.25
S5710-28C-EI 1.25
S5700-28P-LI-AC 1.25
S5700-52P-LI-AC 1.25
S5700-28C-HI 1.25
S5700-6TP-LI-AC 1.25
S5700-52P-PWR-LI-AC 1.25
S5700S-52P-LI-AC 1.25
S5700-52C-PWR-SI 1.25
S5710-52C-PWR-LI 1.25
S5710-52C-LI 1.25

iMaster NCE-IP
S5710-52C-PWR-EI-AC 1.25
S5700-10P-LI-AC 1.25
S5701-28X-LI-24S-AC 1.25
S5700-28P-LI-4AH 1.25
S5700-28P-LI-24S-4AH 1.25
S5720-56C-HI-AC 1.25
S5720-32C-HI-24S-AC 1.25
S5720-36C-EI-28S-AC 1.25
S5720-36C-EI-AC 1.25
S5720-56C-EI-AC 1.25
S5720-36C-PWR-EI-AC 1.25
S5720-56C-PWR-EI-AC1 1.25
S5720-50X-EI-46S-AC 1.25
S5720-32P-EI-AC 1.25
S5720-52P-EI-AC 1.25
S5720S-28P-SI-AC 1.25
S5720S-52P-SI-AC 1.25
S5720-28P-SI-AC 1.25
S5720-52P-SI-AC 1.25
S5720-28X-PWR-SI-AC 1.25
S5720-52X-PWR-SI-ACF 1.25
S5710-52X-LI-AC 1.25
S5700S-52X-LI-AC 1.25
S5720-14X-PWH-SI-AC 1.25
S5720-52X-PWR-SI-DC 1.25
S5720-52X-SI-DC 1.25
S5720S-52X-SI-DC 1.25
S5720-50X-EI-DC 1.25
S5720-50X-EI-46S-DC 1.25

iMaster NCE-IP
S5720-56C-EI-DC 1.25
S5720-56C-PWR-EI-DC 1.25
S5720-56C-EI-48S-DC 1.25
Huawei-S5700-8P-G 1.25
S5720S-12TP-LI-AC 1.25
S5720S-12TP-PWR-LI-AC 1.25
S5720-28X-SI-24S-DC 1.25
S5720S-28P-LI-AC 1.25
S5720-28X-LI-DC 1.25
S5720-28P-PWR-LI-AC 1.25
S5720-28X-PWR-LI-AC 1.25
S5720-52P-LI-AC 1.25
S5720S-52X-LI-AC 1.25
S5720-52X-LI-DC 1.25
S5720S-52P-PWR-LI-AC 1.25
S5720-52X-PWR-LI-AC 1.25
S5720S-28X-LI-24S-AC 1.25
S5720-28TP-PWR-LI-ACL 1.25
S5720-16X-PWH-LI-AC 1.25
S628X-PWR-E 1.25
S652X-E 1.25
S652X-PWR-E 1.25
S628-E 1.25
S5720-52P-PWR-LI-AC 1.25
S5721-28X-SI-24S-AC 1.25
S5730-48C-PWR-SI-AC 1.25
S5730-68C-PWR-SI-AC 1.25
S5730-68C-PWR-SI 1.25
S5730-68C-SI-AC 1.25

iMaster NCE-IP
S5730-48C-SI-AC 1.25
S5720-28X-PWH-LI-AC 1.25
S5720-52P-LI-AC 1.25
S5720-28P-LI-AC 1.25
S628-PWR-E 1.25
S652-PWR-E 1.25
S652-E 1.25
S628X-E 1.25
S5720-28TP-LI-AC 1.25
S5720S-28TP-PWR-LI-ACL 1.25
S5720-28X-LI-24S-DC 1.25
S5720-28X-LI-24S-AC 1.25
S5720S-52X-PWR-LI-AC 1.25
S5720-52P-PWR-LI-AC 1.25
S5720-52X-LI-AC 1.25
S5720S-52P-LI-AC 1.25
S5720S-28X-PWR-LI-AC 1.25
S5720S-28X-LI-AC 1.25
S5720-28X-LI-AC 1.25
S5720-28P-LI-AC 1.25
S5720-28X-SI-24S-AC 1.25
S5720-12TP-LI-AC 1.25
S5720-56C-PWR-HI-AC1 1.25
S5720-36C-EI-28S-DC 1.25
S5720-36C-PWR-EI-DC 1.25
S5720-36C-EI-DC 1.25
S5720-32X-EI-24S-DC 1.25
S5720-32X-EI-DC 1.25

iMaster NCE-IP
S5720S-28X-SI-DC 1.25
S5720-28X-SI-DC 1.25
S5720-28X-PWR-SI-DC 1.25
S5700S-28X-LI-AC 1.25
S5710-28X-LI-AC 1.25
S5720-52X-PWR-SI-AC 1.25
S5720-52X-SI-AC 1.25
S5720-28X-SI-AC 1.25
S5720S-52X-SI-AC 1.25
S5720S-28X-SI-AC 1.25
S5720-50X-EI-AC 1.25
S5720-52X-EI-AC 1.25
S5720-32X-EI-AC 1.25
S5720-32X-EI-24S-AC 1.25
S5720-56C-PWR-EI-AC 1.25
S5720-56PC-EI-AC 1.25
S5720-36PC-EI-AC 1.25
S5720-56C-EI-48S-AC 1.25
S5700-28TP-LI-AC 1.25
S5720-56C-PWR-HI-AC 1.25
S5700-52X-LI-48CS-AC 1.25
S5700-28P-LI-24S-BAT 1.25
S5700-28P-LI-BAT 1.25
S5701-28X-LI-AC 1.25
S5710-108C-PWR-HI 1.25
S5710-28C-PWR-EI-AC 1.25
S5710-28C-LI 1.25
S5710-28C-PWR-LI 1.25

iMaster NCE-IP
S5700-28C-PWR-SI 1.25
S5700S-28P-LI-AC 1.25
S5700-28P-PWR-LI-AC 1.25
S5700-28C-HI-24S 1.25
S5700-52P-LI-DC 1.25
S5700-28P-LI-DC 1.25
S5710-52C-EI 1.25
S5700-48TP-PWR-SI 1.25
S5700-52C-PWR-EI 1.25
S5700-48TP-SI-DC 1.25
S5700-24TP-SI-DC 1.25
S5700-52C-SI 1.25
S6330-H24X4Y 1.25
S6330-H24X4Y4C 1.25
S6330-H28Y4C 1.25
S6330-H24X6C 1.25
S6330-H48X6C 1.25
S6320-30L-HI-24S 1.25
S6320-50L-HI-48S 1.25
S6320-32C-PWH-SI 1.25
S6324-EI 1.25
S6320-30C-EI-24S-AC 1.25
S6320-54C-EI-48S-AC 1.25
S6320-26Q-EI-24S-AC 1.25
S6320-54C-EI-48S 1.25
S6320-26Q-EI-24S 1.25
S6320-26Q-EI-24S-DC 1.25
S6320-54C-EI-48S-DC 1.25
S6320-30C-EI-24S-DC 1.25
S6348-EI 1.25

iMaster NCE-IP
S6502 0.75
S6506R 0.75
S6506 0.75
S6503 0.75
S6735-S24X6C 1.0
S6735-S48X6C 1.0
S6720S-S24S28X-A 1.25
S6720S-S52X-A 1.25
S6730-H28Y4C-K 1.25
S6730S-H24X6C-A 1.25
S6730S-S24X4Y4Q-A 1.25
S6730S-H24X4Y4C-A 1.25
S6730-H24X4Y4C 1.25
S6730-H28Y4C 1.25
S6730-H24X6C-K 1.25
S6730-H48X6C-K 1.25
S6730S-S24X6Q-A 1.25
S6730-S24X6Q 1.25
S6730-H24X6C 1.25
S6730-H48X6C 1.25
S6720-30L-HI-24S 1.25
S6720-50L-HI-48S 1.25
S6700-48-EI 1.25
S6720-54C-EI-48S-AC 1.25
S6720S-26Q-EI-24S-DC 1.25
S6720-54C-EI-48S-DC 1.25
S6720-26Q-LI-24S-AC 1.25
S6720S-26Q-SI-24S-AC 1.25
S6720-16X-LI-16S-AC 1.25
S6720-32X-LI-32S-AC 1.25

iMaster NCE-IP
S6720-32X-SI-32S-AC 1.25
S6720-32C-SI-DC 1.25
S6720-32C-PWH-SI 1.25
S6720-56C-PWH-SI 1.25
S6720S-48Q-SI-48S-AC 1.25
S6720-52X-PWH-SI 1.25
S6720-52X-PWH-SI-ACF 1.25
S6720-48Q-SI-48S-AC 1.25
S6720-56C-PWH-SI-AC 1.25
S6720-32C-PWH-SI-AC 1.25
S6720-32C-SI-AC 1.25
S6720S-32X-LI-32S-AC 1.25
S6720S-16X-LI-16S-AC 1.25
S6720-26Q-SI-24S-AC 1.25
S6720S-26Q-LI-24S-AC 1.25
S6720S-26Q-EI-24S 1.25
S6720-30C-EI-24S-DC 1.25
S6720S-26Q-EI-24S-AC 1.25
S6720-30C-EI-24S-AC 1.25
S6700-24-EI 1.25
S7706 3.5
S7703 2.0
S7700_COMM 3.5
S7712 6.0
S7710 2.0
S7803 1.25
S7810 1.25
S7806-V 1.25
S7806 1.25
S7802 1.25

iMaster NCE-IP
S7905 2.0
S7908 3.5
S8016 1.25
S8505E 1.25
S8502 1.25
S8508 1.25
S8512 1.25
S8505 1.25
S8704 5.0
S9303 2.0
S9312 6.0
S9310 2.0
S9300_NEW_COMM 3.5
S9310X 2.0
S9300-COMM 2.0
S9306 3.5
S9306E 3.5
S9303E 2.0
S9312E 6.0
S9300XS-12 9.0
S9300X-8 6.0
S9300X-12 9.0
S9300X-4 6.0
S9303X 2.0
S9312X 6.0
S9306X 3.5
S9703 2.0
S9712 6.0
S9706 3.5
SeMG9811-X3 1.5

iMaster NCE-IP
SeMG9811-X8 4
SeMG9811-X16 8
SeMG9811-X8 4.0
SeMG9811-X16 8.0
SeMG9811-X3 1.5
SIG Server 4
SIG9810 4.0
SIG9820 8.0
SIG9800-X16A 8
SIG9800-X8A 4
SIG9800-X16 8.0
SIG9800-X3 1.5
SIG9800-X8 4.0
OptiX SPN A907 1
SPU 0.0
SR8805 0.125
SR8812 0.125
SRG1210 0.25
SRG1220 0.25
SRG1210-S 0.25
SRG1220W 0.25
SRG1210W 0.25
SRG1320V 0.25
SRG1320 0.25
SRG1320E 0.25
SRG1320W 0.25
SRG1320VW 0.25
SRG20-10 0.25
SRG20-11 0.25
SRG20-12 0.25

iMaster NCE-IP
SRG20-12W 0.25
SRG20-15 0.25
SRG20-15W 0.25
SRG20-20 0.25
SRG20-21 0.25
SRG20-30 0.25
SRG20-31 0.25
SRG20-31-D 0.25
SRG2220-D 0.25
SRG2210 0.25
SRG2220 0.25
SRG2320D 0.25
SRG2320E 0.25
SRG2340E 0.25
SRG2320EI 0.25
SRG2304 0.25
SRG2320 0.25
SRG3240 0.25
SRG3250 0.25
SRG3260 0.25
SRG3240-D 0.25
SRG3230 0.25
SRG3360 0.25
SRG3340 0.25
SSP1000 0.0
SSP2000 0.0
SSP3000 0.0
SSP5000-X8 0.0
SSP5000-X16 0.0
SVN5660 0.75

iMaster NCE-IP
SVN5850 0.75
SVN5880 0.75
SVN5880-C 0.75
SVN5860 0.75
SVN5830 0.75
SVN5630 0.75
SVN2260 0.25
SVN2230 0.25
SVN3000 0.25
SVN5300 0.75
SVN5530 0.75
SVN5560 0.75
Tellabs tellabs8609 0.5
UBIQUOSS E7124 0.5
URL Classify Server 0.25
URL Classify Server-DPI 0.25
USG12004F 5
USG12008F 5
USG12008-DC-OVS 4
USG12008-DC 4
USG12008-AC-OVS 4
USG12008-AC 4
USG12004-DC-OVS 1.5
USG12004-DC 1.5
USG12004-AC-OVS 1.5
USG12004-AC 1.5
USG2130 0.25
USG2130W 0.25
USG2120BSR 0.25
USG2130BSR-W 0.25

iMaster NCE-IP
USG2160BSR-W 0.25
USG2130HSR-W 0.25
USG2160HSR-W 0.25
USG2110-F-W 0.25
USG2110-A-GW-W 0.25
USG2110-A-GW-C 0.25
USG2110-A-W 0.25
USG2110-F 0.25
USG2160HSR 0.25
USG2130HSR 0.25
USG2160BSR 0.25
USG2130BSR 0.25
USG2160W 0.25
USG2160 0.25
USG2110 0.25
USG2220BSR-D 0.25
USG2220HSR 0.25
USG2220TSM 0.25
USG2260 0.25
USG2210 0.25
USG2230 0.25
USG2250-D 0.25
USG2205BSR 0.25
USG2250 0.25
USG2220 0.25
USG2250TSM 0.25
USG2220HSR-D 0.25
USG2205HSR 0.25
USG2220BSR 0.25
USG3030 0.25

iMaster NCE-IP
USG3040 0.25
USG50 0.25
USG5330 0.75
USG5360 0.75
USG5310 0.75
USG5350 0.75
USG5320 0.75
USG5120BSR 0.25
USG5120 0.25
USG5150BSR 0.25
USG5120HSR 0.25
USG5160 0.25
USG5150HSR 0.25
USG5150 0.25
USG5120-D 0.25
USG5120BSR-D 0.25
USG5300ADD 0.75
USG5300ADI 0.75
USG5530 0.75
USG5560 0.75
USG5520S 0.75
USG5530S 0.75
USG5550 0.75
USG6530F-DL 1
USG6510F-DL 1
USG6606F-C 1
USG6505F-C 1
USG6305F-C 1
USG6502F-C 1
USG6302F-C 1

iMaster NCE-IP
USG6510F-DK 1
USG6510F-D 1
USG6530F-D 1
USG6331F-D 1
USG6311F-D 1
USG6307F-D 1
USG6590F-K 1
USG6560F-K 1
USG6520F-K 1
USG6585F 1
USG6565F 1
USG6555F 1
USG6525F 1
USG6385F 1
USG6365F 1
USG6355F 1
USG6335F 1
USG6325F 1
USG6315F 1
USG6308F 1
USG6306F 1
USG6715-F 1
USG6391E-AC 0.75
USG6395E-AC 0.75
USG6365E-AC 0.75
USG6355E-AC 0.75
USG6335E-AC 0.75
USG6325E-AC 0.75
USG6315E-AC 0.75
USG6309E-AC 0.75

iMaster NCE-IP
USG6305E-AC 0.75
USG6385E-AC 0.75
USG6331E-AC 0.75
USG6311E-AC 0.75
USG6307E-AC 0.75
USG6308 0.75
USG6306 0.75
USG6310-M 0.75
USG6360 0.75
USG6350 0.75
USG6330 0.75
USG6310 0.75
USG6390 0.75
USG6380 0.75
USG6370 0.75
USG6320 0.75
USG6530E-AC 0.75
USG6510E-AC 0.75
USG6585E-AC 0.75
USG6565E-AC 0.75
USG6555E-AC 0.75
USG6525E-AC 0.75
USG6515E 0.75
USG6580E 0.75
USG6560E 0.75
USG6550E 0.75
USG6570 0.75
USG6550 0.75
USG6530 0.75
USG6510-SJJ 0.75

iMaster NCE-IP
USG6507 0.75
USG6620E-AC 0.75
USG6625E-AC 0.75
USG6615E-AC 0.75
USG6655E-AC 0.75
USG6635E-AC 0.75
USG6635E-DC 0.75
USG6630E-DC 0.75
USG6680E 0.75
USG6650E 0.75
USG6630E-AC 0.75
USG6630 0.75
USG6620 0.75
USG6680 0.75
USG6660 0.75
USG6650 0.75
USG6670 0.75
USG6610E-AC 0.75
USG9120 4.0
USG9110 2.0
USG9310 4.0
USG9320 8.0
USG9000V 1.5
USG9520 1.5
USG9580 8.0
USG9560 4.0
Virtual Cluster Chassis 0.0
VNE 9000(V8) 1.0
VNE 9000(vRR) 1.0
VNE 9000(vBRAS-CP) 1.0

iMaster NCE-IP
VNE1000(V8) 1.0
vRGW 0.5
vRouter6000V2 0.75
vRouter6000V4 0.75
vRouter6000V1 0.75
vRouter6000V8 0.75
VSIG9800(V8) 1.0

iMaster NCE-IP
Product Description (x86,enterprise) 13 Version Requirements
13 Version Requirements
NOTE
● The New Version column lists the NE versions newly supported by the current NCE
version.
● The Compatible Version column lists the NE versions supported by earlier NCE versions.
Unless otherwise specified, the current NCE version also supports these NE versions.
13.1 PTN Series

13.2 NE/ATN/CX/Multi-service gateways Series
13.3 R/AR Series
13.4 RM9000 Series
13.5 Switch Series
13.6 Security Series
13.7 iCache Series
13.1 PTN Series

NCE (IP Domain) Manager supports only PTN 6900 series products. To manage
other PTN products, deploy NCE-IP (Manager) + NCE-T (Manager) or NCE-IP
(Manager + Controller + Analyzer) plus the Trans component.
The following table lists the PTN series NE supported.
NOTE
Rules for defining commercial versions of NE software: a.bb.cc.dd. "a" indicates the NE
platform version. Currently, 4, 5 and 8 are supported. "bb" indicates the product name. "cc"
indicates the R version of the product. To be specific, 01 represents R001, 02 represents
R002, and so on. "dd" indicates the C version of the product. The following lists the version
mapping rules:
1. If the mapping table lists a.bb.cc.20 for NCE version A, all a.bb.cc.2x versions are
supported by NCE version A.
2. If the mapping table lists a.bb.cc for NCE version A, all a.bb.cc.xx versions are supported
by NCE version A.

iMaster NCE-IP
Table 13-1 PTN series
NE New Version Compatible Version
HG-FM CPE-01 V800R022C10 V800R022C00
HG-FM CPE-02 V800R022C10 V800R021C00
HG-FM CPE-03 V800R022C10 V800R022C00
NetEngine A810 M V800R022C10 V800R021C00,

V800R021C10,
V800R022C00
NetEngine A813 M V800R022C10 V800R022C00
NetEngine A850 M V800R022C10 V800R022C00
OptiX PTN 1900 N/A 5.58.01.10

(V100R001C01),
5.58.01.30
(V100R001C02),
5.58.01.50
(V100R001C03),
5.58.02.10
(V100R002C00),
5.58.02.30
(V100R002C01),
5.58.02.50
(V100R002C02),
5.58.02.60
(V100R002C03),
5.58.02.90
(V100R002C02SPC600),
5.58.03.20
(V100R003C01),
5.58.03.30
(V100R003C02),
5.58.05.10
(V100R005C00),
5.58.05.30
(V100R005C01),
5.58.06.30
(V100R006C10),
5.58.07.10
(V100R007C00),
5.58.07.30
(V100R007C10),
5.58.08.20
(V100R008C10)

iMaster NCE-IP
OptiX PTN 3900 N/A 5.59.01.10

(V100R001C01),
5.59.01.30
(V100R001C02),
5.59.01.50
(V100R001C03),
5.59.02.10
(V100R002C00),
5.59.02.30
(V100R002C01),
5.59.02.50
(V100R002C02),
5.59.02.60
(V100R002C03),
5.59.02.70
(V100R002C05),
5.59.02.90
(V100R002C02SPC600),
5.59.03.20
(V100R003C01),
5.59.03.30
(V100R003C02),
5.59.05.10
(V100R005C00),
5.59.05.30
(V100R005C01),
5.59.06.30
(V100R006C10),
5.59.07.10
(V100R007C00),
5.59.07.30
(V100R007C10),
5.59.08.20
(V100R008C10)

iMaster NCE-IP
OptiX PTN 3900-8 N/A 5.78.02.50

(V100R002C02),
5.78.02.60
(V100R002C03),
5.78.02.70
(V100R002C05),
5.78.02.90
(V100R002C02SPC600),
5.78.03.20
(V100R003C01),
5.78.03.30
(V100R003C02),
5.78.05.10
(V100R005C00),
5.78.05.30
(V100R005C01),
5.78.06.30
(V100R006C10),
5.78.07.10
(V100R007C00),
5.78.07.30
(V100R007C10),
5.78.08.20
(V100R008C10)
OptiX PTN 905 N/A 5.88.2.80 (V100R002C05)
OptiX PTN 905A N/A 5.123.05.30

(V100R005C01),
5.123.06.30
(V100R006C10),
5.123.07.10
(V100R007C00),
5.123.07.30
(V100R007C10),
5.123.08.20
(V100R008C10)

iMaster NCE-IP
OptiX PTN 905B N/A 5.124.05.30

(V100R005C01),
5.124.06.30
(V100R006C10),
5.124.07.10
(V100R007C00),
5.124.07.30
(V100R007C10),
5.124.08.20
(V100R008C10)
OptiX PTN 905D V800R022C10 V100R010C00,

V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 905E V800R022C10 V100R009C00,

V100R010C00,
V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 905G V800R022C10 V100R009C00,

V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 906A N/A 5.145.06.30

(V100R006C10),
5.145.07.10
(V100R007C00),
5.145.07.30
(V100R007C10),
5.145.08.20
(V100R008C10)

iMaster NCE-IP
OptiX PTN 906AI N/A 5.159.07.10

(V100R007C00),
5.159.07.30
(V100R007C10),
5.159.08.20
(V100R008C10)
OptiX PTN 906B N/A 5.146.07.30

(V100R007C10),
5.146.08.20
(V100R008C10)
OptiX PTN 910 N/A 5.64.01.10

(V100R001C00),
5.64.01.50
(V100R001C01),
5.64.02.10
(V100R002C00),
5.64.02.50
(V100R002C01),
5.64.02.60
(V100R002C03),
5.64.02.70
(V100R002C05),
5.64.02.80
(V100R002C01SPC800),
5.64.02.90
(V100R002C01SPC600),
5.64.03.20
(V100R003C01),
5.64.03.30
(V100R003C02),
5.64.05.10
(V100R005C00),
5.64.05.30
(V100R005C01),
5.64.06.30
(V100R006C10),
5.64.07.10
(V100R007C00),
5.64.07.30
(V100R007C10),
5.64.08.20
(V100R008C10)

iMaster NCE-IP
OptiX PTN 910-F N/A 5.91.03.30

(V100R003C02),
5.91.05.10
(V100R005C00),
5.91.05.30
(V100R005C01),
5.91.06.30
(V100R006C10),
5.91.07.10
(V100R007C00),
5.91.07.30
(V100R007C10),
5.91.08.20
(V100R008C10)
OptiX PTN 910D-F V800R022C10 V800R022C00
OptiX PTN 910E-F V800R022C10 V100R009C10,

V100R010C00,
V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 912 N/A 5.63.01.10

(V100R001C01),
5.63.01.50
(V100R001C02)
OptiX PTN 916-F V800R022C10 V800R021C00,

V800R021C10,
V800R022C00
OptiX PTN 917-F V800R022C10 V800R022C00
OptiX PTN 91A-F V800R022C10 V800R022C00

iMaster NCE-IP
OptiX PTN 930 V800R022C10 V100R010C00,

V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 950 N/A 5.65.01.10

(V100R001C00),
5.65.01.50
(V100R001C01),
5.65.02.10
(V100R002C00),
5.65.02.50
(V100R002C01),
5.65.02.60
(V100R002C03),
5.65.02.70
(V100R002C05),
5.65.02.80
(V100R002C01SPC800),
5.65.02.90
(V100R002C01SPC600),
5.65.03.20
(V100R003C01),
5.65.03.30
(V100R003C02),
5.65.05.10
(V100R005C00),
5.65.05.30
(V100R005C01),
5.65.06.30
(V100R006C10),
5.65.07.10
(V100R007C00),
5.65.07.30
(V100R007C10),
5.65.08.20
(V100R008C10)

iMaster NCE-IP
OptiX PTN 960 N/A 5.94.03.40

(V100R003C03),
5.94.05.10
(V100R005C00),
5.94.05.30
(V100R005C01),
5.94.06.30
(V100R006C10),
5.94.07.10
(V100R007C00),
5.94.07.30
(V100R007C10),
5.94.08.20
(V100R008C10)
OptiX PTN 960(160G) V800R022C10 V100R010C00SPC600,

V100R011C00,
V100R011C00SPC100,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 970 V800R022C10 V100R008C10,

V100R009C00,
V100R009C10,
V100R010C00,
V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 970C V800R022C10 V800R021C00,

V800R021C10,
V800R022C00

iMaster NCE-IP
OptiX PTN 980 V800R022C10 V100R011C00,

V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 980B V800R022C10 V800R021C00,

V800R021C10,
V800R022C00
OptiX PTN 990 V800R022C10 V100R007C10,

V100R008C00,
V100R008C10,
V100R008C10SPC300,
V100R008C10SPC500,
V100R009C10,
V100R010C00,
V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 990B V800R022C10 V800R021C00,

V800R021C10,
V800R022C00
OptiX PTN 990E V800R022C10 V100R012C00SPC300,

V800R021C00,
V800R021C10,
V800R022C00
OptiX SPN A907 V800R022C10 N/A

iMaster NCE-IP
Table 13-2 PTN7900 series

OptiX PTN 7900-12 V800R022C10 V100R007C00,

V100R007C10,
V100R008C00,
V100R008C10,
V100R009C10,
V100R010C00,
V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 7900-24 V800R022C10 V100R006C10,

V100R006C20,
V100R007C00,
V100R007C10,
V100R008C00,
V100R008C10,
V100R009C10,
V100R010C00,
V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
OptiX PTN 7900-32 V800R022C10 V100R006C00,

V100R006C10,
V100R006C20,
V100R007C00,
V100R007C10,
V100R008C00,
V100R008C10,
V100R009C10,
V100R010C00,
V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
OptiX PTN 7900E-12 V800R022C10 V100R010C00,

V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00

V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP

V100R010C00,
V100R010C00SPC600,
V100R011C00,
V100R011C00SPC300,
V100R012C00SPC300,
V800R021C00,
V800R021C10,
V800R022C00
Table 13-3 PTN6900 series

PTN 6900-1 N/A V600R003C02,

V600R005C00,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC600,
V600R009C20SPC900,
V600R009C20SPCa00,
V600R009C50,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10

iMaster NCE-IP
PTN 6900-1-M4 V800R022C10 V800R005C01,

V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-16 N/A V600R003C02,

V600R005C00,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC600,
V600R009C20SPC900,
V600R009C20SPCa00,
V600R009C50,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
PTN 6900-16(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-16A N/A V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
PTN 6900-16A(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
PTN 6900-2 N/A V600R005C00,

V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC600,
V600R009C20SPC900,
V600R009C20SPCa00,
V600R009C50,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10

iMaster NCE-IP
PTN 6900-2-M14 V800R022C10 V800R012C00,

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
PTN 6900-2-M16 V800R022C10 V800R005C01,

V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-2-M16A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
PTN 6900-2-M4 V800R022C10 N/A
PTN 6900-2-M4-IOT V800R022C10 N/A
PTN 6900-2-M8 V800R022C10 V800R005C01,

V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-2-M8A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
PTN 6900-2-M8C V800R022C10 V800R011C10,

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-3 N/A V600R003C02,

V600R005C00,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC600,
V600R009C20SPC900,
V600R009C20SPCa00,
V600R009C50,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
PTN 6900-3(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-3A N/A V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
PTN 6900-3A(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-8 N/A V600R003C02,

V600R005C00,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC600,
V600R009C20SPC900,
V600R009C20SPCa00,
V600R009C50,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
PTN 6900-8(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-8A N/A V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
PTN 6900-8A(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
PTN 6900-F1A-14H24Q V800R022C10 V800R011C00,

V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-M2E V800R022C10 V800R007C10,

V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
PTN 6900-M2F V800R022C10 V800R007C10,

V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
PTN 6900-M2K V800R022C10 V800R011C00,

V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
PTN 6900-M2K-B V800R022C10 V800R011C00,

V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
13.2 NE/ATN/CX/Multi-service gateways Series

Manageable NE/ATN/CX/Multi-service gateways series NE is listed as follows:
Table 13-4 NE series

NE05 N/A V100R007,

V300R002
NE05E-S2 N/A V200R006C00,

V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800,
V300R005C00,
V300R007C00

iMaster NCE-IP
NE05E-S2(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE05E-SE N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE05E-SF N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE05E-SG N/A V200R006C00,

V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE05E-SH N/A V200R006C00,

V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE05E-SI N/A V200R006C00,

V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800

iMaster NCE-IP
NE05E-SJ N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE05E-SK N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE05E-SL N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE05E-SM N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE05E-SN N/A V200R006C00,

V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800,
V300R005C10

iMaster NCE-IP
NE05E-SQ V800R022C10 V300R001C10,

V300R002C00,
V300R002C10,
V300R003C00,
V300R003C10,
V300R005C00,
V300R007C00,
V800R012C00,
V800R012C10,
V800R012C11,
V800R021C00,
V800R021C10,
V800R022C00
NE05E-SR V800R022C10 V300R001C10,

V300R002C00,
V300R002C10,
V300R003C00,
V300R003C10,
V300R005C00,
V300R007C00,
V800R012C00,
V800R012C10,
V800R012C11,
V800R021C00,
V800R021C10,
V800R022C00
NE08 N/A V100R007
NE08E N/A V100R007,

V300R002,
V300R003C10,
V300R005C00,
V300R006C10

iMaster NCE-IP
NE08E-S6 N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
NE08E-S6E V800R022C10 V300R001C10,

V300R002C00,
V300R002C10,
V300R003C00,
V300R003C10,
V300R005C00,
V300R007C00,
V800R012C00,
V800R012C10,
V800R012C11,
V800R021C00,
V800R021C10,
V800R022C00
NE08E-S9 V800R022C10 V300R003C10,

V300R005C00,
V300R007C00,
V800R012C00,
V800R012C10,
V800R012C11,
V800R021C00,
V800R021C10,
V800R022C00
NE16 N/A V100R007
NE16E N/A V100R007,

V300R002
NE16EX N/A V200R005C10,

V200R005C20,
V200R005C30
NE16EX-6 N/A V200R005C20,

V200R005C30

iMaster NCE-IP
NE20-2 N/A V200R003,

V200R005
NE20-4 N/A V200R003,

V200R005
NE20-8 N/A V200R003,

V200R005
NE20-X3 V800R022C10 N/A
NE20E-8 N/A V200R003,

V200R005
NE20E-S16 V800R022C10 V800R005C01,

V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE20E-S16A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE20E-S16B V800R022C10 V800R011C00,

V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE20E-S2E V800R022C10 V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE20E-S2F V800R022C10 V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE20E-S4 V800R022C10 V800R005C00,

V800R005C01,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE20E-S8 V800R022C10 V800R005C00,

V800R005C01,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE20E-S8A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE20E-X6 N/A V600R003C00,

V600R003C05,
V600R006C00,
V600R009C00,
V600R009C10,
V600R009C20

iMaster NCE-IP
NE40E-4 N/A V300R001,

V300R002,
V300R003,
V300R006,
V600R001,
V600R002,
V600R003,
V600R005,
V600R006,
V600R007,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V600R009C50
NE40E-F1A-14H24Q V800R022C10 V800R012C00,

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-M16A V800R022C10 V800R010C10,

V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-M2E V800R022C10 V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-M2F V800R022C10 V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-M2H V800R022C10 V800R010C10,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-M2K V800R022C10 V800R010C10,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-M2K-B V800R022C10 V800R012C10,

V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00,
V8R11C00,
V8R11C10
NE40E-M8A V800R022C10 V800R010C10,

V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X1 N/A V600R002C03,

V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC501,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10

iMaster NCE-IP
NE40E-X1-M4 V800R022C10 V800R005C00,

V800R005C01,
V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X16 N/A V600R001C00,

V600R001C01,
V600R002C00,
V600R002C01,
V600R002C02,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R006C00,
V800R006C10,
V800R006C30,
V800R007C00,
V800R008C00,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R010C10SPC800,
V800R011C00,
V800R011C10,
V800R012C10

iMaster NCE-IP
NE40E-X16(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-X16A N/A V600R001C00,

V600R001C01,
V600R002C00,
V600R002C01,
V600R002C02,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R006C10,
V800R006C30,
V800R007C00,
V800R008C00,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10SPC800,
V800R012C10

iMaster NCE-IP
NE40E-X16A(V8) V800R022C10 V800R011C00,

V800R011C10,
V800R012C10,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-X16B V800R022C10 V800R010C10,

V800R011C00,
V800R011C10,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-X16B(V8) N/A V800R009C10,

V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
NE40E-X16C N/A V800R011C10,

V800R012C10
NE40E-X16C(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X2 N/A V600R002C03,

V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC501,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
NE40E-X2-M14 V800R022C10 V800R012C00,

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X2-M16 V800R022C10 V800R005C01,

V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-X2-M16A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X2-M8 V800R022C10 V800R005C00,

V800R005C01,
V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-X2-M8A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X3 V800R022C10 V600R001C00,

V600R001C01,
V600R002C00,
V600R002C01,
V600R002C02,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R007C00,
V800R008C00,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10SPC800,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X3A V800R022C10 V800R007C00,

V800R008C00,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R010C10SPC800,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-X3A(V8) N/A V800R011C00,

V800R011C10
NE40E-X4A(V8) V800R022C10 V800R012C11,

V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X8 N/A V600R001C00,

V600R001C01,
V600R002C00,
V600R002C01,
V600R002C02,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R006C00,
V800R006C10,
V800R006C30,
V800R007C00,
V800R008C00,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10SPC800,
V800R012C10
NE40E-X8(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE40E-X8A N/A V800R006C10,

V800R006C30,
V800R007C00,
V800R008C00,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10SPC800,
V800R012C10
NE40E-X8A(V8) V800R022C10 V800R011C00,

V800R011C10,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-X8AK(V8) V800R022C10 V800R012C10,

V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE40E-X8C N/A V800R011C10,

V800R012C10
NE40E-X8C(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE5000E N/A V200R002,

V200R003,
V300R005,
V300R007C00

iMaster NCE-IP
NE5000E(V8) V800R022C10 V800R006C00,

V800R007C00,
V800R008C00,
V800R009C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R011C10SPC810,
V800R011C10SPC900,
V800R012C10,
V800R013C00,
V800R021C10,
V800R022C00
NE5000E-BTB(V8) V800R022C10 V800R006C00,

V800R007C00,
V800R008C00,
V800R009C00,
V800R009C10SPC800,
V800R011C00,
V800R011C10,
V800R011C10SPC800,
V800R011C10SPC900,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C10,
V800R022C00
NE5000E-Multi N/A V300R005,

V300R006C02,
V300R007C00

iMaster NCE-IP
NE5000E-Multi(V8) V800R022C10 V800R006C00,

V800R007C00,
V800R008C00,
V800R009C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R011C10SPC810,
V800R011C10SPC900,
V800R012C10,
V800R013C00,
V800R021C10,
V800R022C00
NE5000E-Multi-S(V8) V800R022C10 V800R012C10,

V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE5000E-S V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE80 N/A V100R002,

V300R002,
V300R005

iMaster NCE-IP
NE80E N/A V300R001,

V300R002,
V300R003,
V300R006,
V600R001,
V600R002,
V600R003,
V600R005,
V600R006,
V600R007,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V600R009C50
NE9000 V800R022C10 V800R008C10,

V800R009C00,
V800R009C10,
V800R010C00,
V800R012C00,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE9000-20 N/A V800R011C00,

V800R011C10,
V800R013C00

iMaster NCE-IP
NE9000-20-ADMIN V800R022C10 V800R011C00,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE9000-20-LS V800R022C10 V800R011C00,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE9000-8 V800R022C10 V800R010C00,

V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NE9000-8-ADMIN V800R022C10 V800R011C00,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NE9000-8-LS V800R022C10 V800R011C00,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8000 V800R022C10 V800R012C00,

F1A-8H20Q V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

F1A-8H20Q-E V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8000 V800R022C10 N/A

F1A-8H20Q-E-PTN

F2A-8K36H V800R021C10,
V800R022C00
NetEngine 8000 V800R022C10 N/A

F2A-8K36H-PTN
NetEngine 8000 F8 V800R022C10 V800R021C10,

V800R022C00
NetEngine 8000 M14 V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
NetEngine 8000 M14K V800R022C10 V800R012C10,

V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8000 M1A V800R022C10 V800R012C00,

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8000 M1C V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8000 M1D V800R022C10 V800R012C11,

V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8000 M1D-B V800R022C10 V800R022C00
NetEngine 8000 M1D-B- V800R022C10 N/A

IOT
NetEngine 8000 M4 V800R022C10 V800R022C00

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP

V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8000 X16 V800R022C10 V800R021C10,

V800R022C00
NetEngine 8000 X16- V800R022C10 N/A

PTN

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8000E F8 V800R022C10 V800R021C10,

V800R022C00

iMaster NCE-IP
NetEngine 8000E F8-Z V800R022C10 V800R021C10,

V800R022C00
NetEngine 8000E M14 V800R022C10 V800R021C00,

V800R021C10,
V800R022C00
NetEngine 8000E M14- V800R022C10 N/A

PTN
NetEngine 8000E M14-Z V800R022C10 V800R021C10,

V800R022C00
NetEngine 8000E M4 V800R022C10 V800R022C00
NetEngine 8000E M8 V800R022C10 V800R021C00,

V800R021C10,
V800R022C00
NetEngine 8000E M8- V800R022C10 N/A

PTN
NetEngine 8000E X16 V800R022C10 V800R021C10,

V800R022C00
NetEngine 8000E X16- V800R022C10 N/A

PTN
NetEngine 8000E X8 V800R022C10 V800R013C00,

V800R021C00,
V800R021C10,
V800R022C00

V800R022C00

V800R022C00

V800R021C00,
V800R021C10,
V800R022C00
NetEngine 8100 X8-PTN V800R022C10 N/A
NetEngine A810 V800R022C10 V800R021C00,

V800R021C10,
V800R022C00

iMaster NCE-IP

V800R021C10,
V800R022C00
NetEngine A811 M V800R022C10 V800R021C00,

V800R021C10,
V800R022C00
NetEngine A813 V800R022C10 V800R022C00
NetEngine A813 E V800R022C10 V800R022C00
NetEngine A815 T V800R022C10 V800R022C00

V800R022C00
NetEngine A821 E V800R022C10 V800R021C10,

V800R022C00
NetEngine A831 E-L2 V800R022C10 V800R022C00

iMaster NCE-IP
Table 13-5 ATN series

ATN 980B V800R022C10 V300R001C00,

V300R001C10,
V300R002C00,
V300R002C10,
V300R003C00,
V300R003C10,
V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN 980C V800R022C10 V300R006C00,

V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00,
V800R022C10
ATN 980C-PL N/A V800R022C00,

V800R022C10
ATN 980D V800R022C10 V300R007C00,

V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
ATN-905-AC(V8) V800R022C10 V300R003C10,

V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN-905-DC(V8) V800R022C10 V300R003C10,

V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN905 AC N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800,
V300R007C00
ATN905 AC(V8) V800R022C10 V300R006C00,

V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
ATN905 DC N/A V200R003C10,

V200R003C20,
V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800,
V300R007C00
ATN905 DC(V8) V800R022C10 V300R006C00,

V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN905-BM N/A V200R006C10
ATN905-E AC N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN905-G(V8) V800R022C10 V300R006C11,

V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN905-S V800R022C10 N/A
ATN905-S(V8) V800R022C10 V800R022C00
ATN905-V N/A V200R005C00

iMaster NCE-IP
ATN905-V AC N/A V200R003C10,

V200R003C20,
V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN905A AC N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN905A-C N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN905A-D N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN905A-P AC N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800

iMaster NCE-IP
ATN905A-V AC N/A V200R003C00,

V200R003C10,
V200R003C20,
V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910 N/A V200R001C00,

V200R001C01,
V200R001C02,
V200R002C00,
V200R002C01,
V200R003C00,
V200R003C20,
V200R005C00,
V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910B N/A V200R003C00,

V200R003C20,
V200R005C00,
V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800,
V300R003C10,
V300R005C00,
V300R005C10,
V300R006C10

iMaster NCE-IP
ATN910B(V8) V800R022C10 V300R003C00,

V300R003C10,
V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910B-D AC(V8) V800R022C10 V300R003C00,

V300R003C10,
V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910B-D DC(V8) V800R022C10 V300R003C00,

V300R003C10,
V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
ATN910B-E AC(V8) V800R022C10 V300R003C00,

V300R003C10,
V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910B-F AC(V8) V800R022C10 V300R003C00,

V300R003C10,
V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910B-F DC(V8) V800R022C10 V300R003C00,

V300R003C10,
V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910C N/A V300R003C10

iMaster NCE-IP
ATN910C-A V800R022C10 V300R001C10,

V300R002C00,
V300R002C10,
V300R003C00,
V300R003C10,
V300R006C00,
V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910C-B V800R022C10 V300R001C10,

V300R002C00,
V300R002C10,
V300R003C00,
V300R003C10,
V300R006C00,
V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910C-D V800R022C10 V300R001C10,

V300R002C00,
V300R002C10,
V300R003C00,
V300R003C10,
V300R006C00,
V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
ATN910C-F V800R022C10 V300R006C00,

V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910C-G V800R022C10 V300R006C00,

V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910C-H V800R022C10 V300R006C00,

V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910C-K V800R022C10 V300R007C00,

V800R021C00,
V800R021C10,
V800R022C00
ATN910C-M V800R022C10 V300R006C00,

V300R006C10,
V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910C-S V800R022C10 V300R006C00,

V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910D N/A V300R006C10

iMaster NCE-IP
ATN910D-A V800R022C10 V300R006C10,

V300R006C11,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN910D-B V800R022C10 V800R022C00
ATN910I AC N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910I DC N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910I-B DC N/A V200R003C20,

V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910I-C AC N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910I-D N/A V200R005C00

iMaster NCE-IP
ATN910I-D AC N/A V200R003C20,

V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910I-D DC N/A V200R003C20,

V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910I-E DC N/A V200R003C20,

V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910I-P AC N/A V200R006C00,

V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800
ATN910I-TC DC N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800

iMaster NCE-IP
ATN950 N/A V200R001C00,

V200R001C01,
V200R001C02,
V200R002C00,
V200R002C01,
V200R003C00,
V200R005C00,
V200R006C20SPC800
ATN950B N/A V200R001C02,

V200R002C00,
V200R002C01,
V200R003C00,
V200R003C20,
V200R005C00,
V200R005C10,
V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC600,
V200R006C20SPC800,
V300R003C10,
V300R005C00,
V300R005C10,
V300R006C10
ATN950B(160G) V800R022C10 V300R003C10,

V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
ATN950B(V8) V800R022C10 V300R003C00,

V300R003C10,
V300R005C00,
V300R005C10,
V300R006C00,
V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN950C V800R022C10 V300R001C10,

V300R002C00,
V300R002C10,
V300R003C00,
V300R006C00,
V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN950D V800R022C10 V300R006C00,

V300R006C10,
V300R007C00,
V800R021C00,
V800R021C10,
V800R022C00
ATN980 N/A V600R002C03,

V600R002C05,
V600R003C00,
V600R003C01,
V600R005C00,
V600R006C00

iMaster NCE-IP
ATN990 N/A V600R002C03,

V600R002C05,
V600R003C00,
V600R003C01,
V600R005C00,
V600R006C00
Table 13-6 ETN series

ETN500-A N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC800
ETN500-B N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC800
ETN500-C N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC800
ETN500-F V800R022C10 V300R003C10,

V300R006C00,
V300R006C10,
V300R006C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
ETN550-A N/A V200R005C10,

V200R006C00,
V200R006C10,
V200R006C20,
V200R006C20SPC800
Table 13-7 CX series

CX200A N/A V100R002,

V100R005
CX200B N/A V100R005
CX200C N/A V100R005
CX300A N/A V100R002,

V100R005
CX300B N/A V100R002,

V100R005

iMaster NCE-IP
CX600-16 N/A V100R001,

V200R001,
V200R002,
V300R006,
V600R001C00,
V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00

iMaster NCE-IP
CX600-4 N/A V100R001,

V200R001,
V200R002,
V300R006,
V600R001C00,
V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00

iMaster NCE-IP
CX600-8 N/A V100R001,

V200R001,
V200R002,
V300R006,
V600R001C00,
V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00
CX600-F1A-14H24Q V800R022C10 V800R012C00,

V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-M2 N/A V800R010C10

iMaster NCE-IP
CX600-M2E V800R022C10 V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-M2F V800R022C10 V800R007C00,

V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-M2H V800R022C10 V800R010C10,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-M2K V800R022C10 V800R010C10,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-M2K-B V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-M8A-DO V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X1 N/A V600R002C03,

V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10

iMaster NCE-IP
CX600-X1-M4 V800R022C10 V800R005C00,

V800R005C01,
V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-X1-M4-DO V800R022C10 V800R005C01,

V800R006C00,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X16 N/A V600R001C00,

V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R006C00,
V800R006C10,
V800R006C30,
V800R007C00,
V800R008C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
CX600-X16(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X16-DO V800R022C10 V600R001C00,

V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-X16A N/A V800R006C10,

V800R006C30,
V800R007C00,
V800R008C00,
V800R012C10

iMaster NCE-IP
CX600-X16A(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-X16A-DO N/A V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C10,
V800R013C00
CX600-X16A-DO(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X2 N/A V600R002C03,

V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
CX600-X2-M16 V800R022C10 V800R005C01,

V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X2-M16-DO V800R022C10 V800R005C01,

V800R006C00,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-X2-M16A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X2-M8 V800R022C10 V800R005C00,

V800R005C01,
V800R006C00,
V800R006C10,
V800R007C00,
V800R007C10,
V800R008C00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-X2-M8-DO V800R022C10 V800R005C00,

V800R005C01,
V800R006C00,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X2-M8A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X3 N/A V600R001C00,

V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R007C00,
V800R008C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10,
V800R013C00,
V800R022C00

iMaster NCE-IP
CX600-X3-DO N/A V600R001C00,

V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R007C00,
V800R008C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
CX600-X3-DO(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-X3A N/A V800R007C00,

V800R008C00,
V800R011C00,
V800R011C10,
V800R012C10

iMaster NCE-IP
CX600-X3A(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-X3A-DO N/A V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C10
CX600-X3A-DO(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X8 N/A V600R001C00,

V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R006C00,
V800R006C10,
V800R006C30,
V800R007C00,
V800R008C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
CX600-X8(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X8-DO N/A V600R001C00,

V600R001C01,
V600R002C00,
V600R002C02,
V600R002C05,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R007C00,
V800R008C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C10
CX600-X8-DO(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX600-X8A N/A V800R006C10,

V800R006C30,
V800R007C00,
V800R008C00,
V800R011C00,
V800R011C10,
V800R012C10
CX600-X8A(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX600-X8A-DO N/A V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R012C10
CX600-X8A-DO(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX6600 N/A V800R010C10,

V800R011C00,
V800R011C10,
V800R012C10

iMaster NCE-IP
CX6601-14H24Q V800R022C10 V800R011C00,

V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX6602 V800R022C10 V800R010C10,

V800R011C10,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX6602-B V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
CX6608 V800R022C10 V800R010C00,

V800R010C10,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00

iMaster NCE-IP
CX6620 V800R022C10 V800R010C00,

V800R010C10,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
Table 13-8 Multi-service gateways series

BGW9916 N/A V100R001C00,

V100R001C10,
V100R002C00,
V100R002C10,
V100R002C20,
V100R002C30,
V100R002C50,
V100R002C50SPC200
MA5200F N/A V100R007
MA5200G-2 N/A V200R003,

V300R002,
V300R003
MA5200G-4 N/A V200R003,

V300R002,
V300R003
MA5200G-8 N/A V200R003,

V300R002,
V300R003

iMaster NCE-IP
ME60-16 N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C05,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00
ME60-4 N/A V100R006C05,

V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00
ME60-8 N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C05,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00

iMaster NCE-IP
ME60-X16 V800R022C10 V600R002C00,

V600R002C02,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R010C10SPC800,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
ME60-X16A N/A V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R010C10SPC800,
V800R012C10

iMaster NCE-IP
ME60-X16A(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
ME60-X2-M16 V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10
ME60-X2-M16A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10

iMaster NCE-IP
ME60-X2-M8 V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10
ME60-X2-M8A V800R022C10 V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R011C00,
V800R011C10,
V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10

iMaster NCE-IP
ME60-X3 V800R022C10 V600R002C00,

V600R002C02,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R010C10SPC800,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10

iMaster NCE-IP
ME60-X8 V800R022C10 V600R002C00,

V600R002C02,
V600R003C00,
V600R003C01,
V600R003C05,
V600R006C00,
V600R007C00,
V600R008C00,
V600R008C10,
V600R008C20,
V600R009C00,
V600R009C10,
V600R009C20,
V600R009C20SPC500,
V600R009C20SPC900,
V600R009C20SPCa00,
V800R008C10,
V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R010C10SPC800,
V800R012C00,
V800R012C10,
V800R013C00,
V800R021C00,
V800R021C10
ME60-X8A N/A V800R008C10,

V800R008C11,
V800R009C00,
V800R009C10,
V800R010C00,
V800R010C10,
V800R010C10SPC800,
V800R012C10

iMaster NCE-IP
ME60-X8A(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10
Table 13-9 VNE series

VNE 1000 N/A V100R001C00,

V100R002C00
VNE 9000(V8) V100R022C10 V100R003C00,

V100R005C00,
V100R005C10,
V100R006C00,
V100R019C00,
V100R020C10,
V100R021C00,
V100R021C10,
V100R022C00,
V800R012C00,
V800R012C10,
V800R012C11
VNE 9000(vBRAS-CP) V100R022C10 V100R005C00,

V100R005C10,
V100R006C00,
V100R019C00,
V100R020C10,
V100R021C00,
V100R021C10,
V100R022C00,
V800R012C00,
V800R012C10,
V800R012C11

iMaster NCE-IP
VNE 9000(vRR) V100R022C10 V100R020C10,

V100R021C00,
V100R021C10,
V100R022C00,
V800R012C00,
V800R012C10,
V800R012C11
VNE1000(V8) V800R022C10 V100R005C00,

V800R012C00,
V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
VSIG9800 N/A V100R003C00,

V300R008C10
VSIG9800(V8) V800R022C10 V800R012C00,

V800R012C10,
V800R012C11,
V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
vRGW N/A V100R001C00
13.3 R/AR Series

The following table lists the R/AR series NE supported.
NOTE
NCE is insensitive to the software versions of R/AR series products (VRPv5 only). As long as a
software version of these products has been supported earlier, NCE inherently supports all
subsequent versions unless these versions involve incompatible changes.

iMaster NCE-IP
Table 13-10 R/AR series

AR10 N/A V300R021C00SPC100
AR1000V N/A V200R008C20,

V200R008C30,
V200R008C50
AR101-S N/A V200R008C20
AR101GW-Lc-S N/A V200R008C30,

V200R008C50
AR101W-S N/A V200R008C20
AR109 N/A V200R008C30,

V200R008C50
AR109GW-L N/A V200R008C30,

V200R008C50
AR109W N/A V200R008C30,

V200R008C50
AR111-S N/A V200R008C20,

V200R009C00
AR121 N/A V200R006C10
AR121-S N/A V200R005C10,

V200R005C20,
V200R005C30,
V200R006C10
AR121GW-L N/A V200R007C00
AR121W N/A V200R007C00
AR121W-S N/A V200R007C00

iMaster NCE-IP
AR1220 N/A V200R001C00,

V200R001C01,
V200R002C00,
V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR1220-D N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR1220-S N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR1220C N/A V200R007C00
AR1220E N/A V200R006C10,

V200R007C00,
V200R009C00

iMaster NCE-IP
AR1220E-S N/A V200R006C10,

V200R007C00,
V200R009C00
AR1220EV N/A V200R006C10,

V200R007C00,
V200R009C00
AR1220EVW N/A V200R006C10,

V200R007C00,
V200R009C00
AR1220F N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR1220F-S N/A V200R006C10,

V200R007C00,
V200R009C00
AR1220L-S N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00

iMaster NCE-IP
AR1220V N/A V200R001C00,

V200R001C01,
V200R002C00,
V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR1220VW N/A V200R001C01,

V200R002C00,
V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR1220W N/A V200R001C01,

V200R002C00,
V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00

iMaster NCE-IP
AR1220W-S N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR129 N/A V200R006C10,

V200R007C00
AR129CGVW-L N/A V200R008C20,

V200R010C00SPC200
AR129CV N/A V200R009C00
AR129GW-L N/A V200R007C00
AR129W N/A V200R007C00
AR1504-16S8T N/A V200R009C00
AR1504-24S N/A V200R009C00
AR1504-24T N/A V200R009C00
AR1504-8S16T N/A V200R009C00
AR151 N/A V200R002C00,

V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR151-S N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10

iMaster NCE-IP
AR151-S2 N/A V200R007C00,

V200R009C00
AR151G-C N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR151G-HSPA+7 N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR151G-U-S N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR151W-P N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR151W-P-S N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR156 N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10

iMaster NCE-IP
AR156W N/A V200R005C10,

V200R005C20,
V200R005C30,
V200R006C10
AR157 N/A V200R002C01,

V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR157VW N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR157W N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR158E N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10

iMaster NCE-IP
AR158EVW N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR161 N/A V200R006C10
AR161-S N/A V200R006C10
AR1610 N/A V200R009C00
AR161EGW-L N/A V200R009C00
AR161EW N/A V200R008C30,

V200R008C50
AR161EW-M1 N/A V200R008C30,

V200R008C50
AR161F N/A V200R005C30,

V200R006C10
AR161F-S N/A V200R005C10,

V200R005C20,
V200R005C30,
V200R006C10
AR161FG-L N/A V200R005C10,

V200R005C20,
V200R005C30,
V200R006C10
AR161FG-Lc N/A V200R009C00
AR161FGW-L N/A V200R005C10,

V200R005C20,
V200R005C30,
V200R006C10
AR161FGW-La N/A V200R007C00,

V200R009C00
AR161FGW-Lc N/A V200R008C30,

V200R008C50

iMaster NCE-IP
AR161FV-1P N/A V200R007C00,

V200R009C00
AR161FW N/A V200R006C10,

V200R007C00,
V200R008C20,
V200R009C00
AR161FW-P-M5 N/A V200R005C20,

V200R005C30,
V200R006C10
AR161G-L N/A V200R006C10
AR161G-Lc N/A V200R008C30,

V200R008C50
AR161G-U N/A V200R007C00,

V200R009C00
AR161W N/A V200R007C00,

V200R009C00
AR162F N/A V200R005C20,

V200R005C30,
V200R006C10
AR168F N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR168F-4P N/A V200R009C00
AR169 N/A V200R006C10,

V200R007C00,
V200R009C00
AR169-P-M9 N/A V200R006C10
AR169BF N/A V200R006C10
AR169CVW N/A V200R008C30,

V200R008C50
AR169CVW-4B4S N/A V200R008C30,

V200R008C50

iMaster NCE-IP
AR169EGW-L N/A V200R008C30,

V200R008C50
AR169EW N/A V200R008C30,

V200R008C50
AR169F N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR169FGVW-L N/A V200R005C20,

V200R005C30,
V200R006C10
AR169FGW-L N/A V200R005C30,

V200R006C10
AR169FV-8S N/A V200R006C10
AR169FVW N/A V200R005C20,

V200R005C30,
V200R006C10
AR169FVW-8S N/A V200R006C10
AR169G-L N/A V200R006C10
AR169JFVW-4B4S N/A V200R009C00
AR169RW-P-M9 N/A V200R007C00,

V200R009C00
AR169W N/A V200R007C00,

V200R009C00
AR169W-P-M9 N/A V200R007C00,

V200R009C00
AR18-12 N/A VRP 1.74,

Version 1.74 Release
0108
8040V200R007B06D467,
Bootrom Version is 5.27
VRP (R) software
AR18-18 N/A Version 1.74 Release

0108

iMaster NCE-IP
AR18-21 N/A VRP 3.4 R1711P04
AR201 N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR201-S N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR201V N/A V200R008C30,

V200R008C50
AR201VW-P N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR206 N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10

iMaster NCE-IP
AR207 N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR207-S N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10

V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR207V N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C30,
V200R006C10

iMaster NCE-IP
AR207V-P N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C30,
V200R006C10
AR207VW N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR208E N/A V200R002C00,

V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10
AR2201-48FE N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00

iMaster NCE-IP
AR2201-48FE-S N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR2202-48FE N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR2204 N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30
AR2204-27GE N/A V200R007C00,

V200R009C00
AR2204-27GE-P N/A V200R007C00,

V200R009C00
AR2204-51GE N/A V200R008C20
AR2204-51GE-P N/A V200R007C00,

V200R009C00
AR2204-51GE-R N/A V200R008C30,

V200R008C50

iMaster NCE-IP
AR2204-S N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR2204E N/A V200R007C00,

V200R009C00
AR2204E-D N/A V200R008C20
AR2220 N/A V200R001C00,

V200R001C01,
V200R002C00,
V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR2220E N/A V200R006C10,

V200R007C00,
V200R009C00
AR2220L N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30
AR2230L N/A V200R003C00,

V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30

iMaster NCE-IP
AR2240 N/A V200R001C00,

V200R001C01,
V200R002C00,
V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR2240-S N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR2240C N/A V200R007C00,

V200R009C00
AR2504-D-H N/A V200R008C30,

V200R008C50
AR2504-H N/A V200R007C00,

V200R008C20,
V200R009C00
AR2504E-H N/A V200R008C20
AR28-09 N/A V300R003
AR28-10 N/A V300R003
AR28-11 N/A V300R003
AR28-12 N/A V300R003
AR28-13 N/A V300R003
AR28-14 N/A V300R003

iMaster NCE-IP
AR28-30 N/A V200R007,

V300R003
AR28-31 N/A V200R007,

V300R003
AR28-40 N/A V300R003
AR28-80 N/A V300R003
AR2809B N/A V300R003
AR29-01 N/A V300R003
AR29-11 N/A V300R003
AR29-21 N/A V300R003
AR29-41 N/A V300R003
AR29-61 N/A V300R003
AR303 N/A V300R021C00SPC100
AR303W N/A V300R021C00SPC100
AR3260 N/A V200R001C00,

V200R001C01,
V200R002C00,
V200R002C01,
V200R002C02,
V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R007C00,
V200R009C00
AR3260-S N/A V200R006C10,

V200R007C00,
V200R009C00
AR3670 N/A V200R006C10,

V200R007C00,
V200R009C00
AR46-20 N/A V300R003

iMaster NCE-IP
AR46-20E N/A V300R003
AR46-40 N/A V300R003
AR46-40E N/A V300R003
AR46-80 N/A V300R003
AR46-80E N/A V300R003
AR49-45 N/A V300R003
AR49-65 N/A V300R003
AR502CG-L N/A V200R008C30,

V200R008C50
AR502EG-L N/A V200R008C20,

V200R009C00
AR502EG-L-PD N/A V200R009C00
AR502EGRb-L N/A V200R008C30,

V200R008C50
AR502EGRc-Lc N/A V200R008C30,

V200R008C50
AR502EGRz-L N/A V200R009C00
AR502EGRz-Lc N/A V200R009C00
AR502EGW-L N/A V200R008C20,

V200R009C00
AR502G N/A V200R005C70,

V200R007C00,
V200R009C00
AR502G-L-D-H N/A V200R007C00,

V200R009C00
AR502GR-L-D-H N/A V200R007C00,

V200R009C00
AR503EDGW-Lc N/A V200R008C20,

V200R009C00
AR503EDGW-Lc3 N/A V200R008C30,

V200R008C50
AR503EDGW-Lo N/A V200R009C00

iMaster NCE-IP
AR503GW-LcM7 N/A V200R008C20,

V200R009C00
AR509CG-Lc N/A V200R008C20,

V200R009C00
AR509CG-Lt N/A V200R008C20,

V200R009C00
AR509G-L-D-H N/A V200R007C00,

V200R009C00
AR509G-Lc N/A V200R008C30,

V200R008C50
AR511CGW-LAV2M3 N/A V200R008C20,

V200R009C00
AR511GW-L-B3 N/A V200R005C30,

V200R006C10
AR511GW-LAV2M3 N/A V200R005C30,

V200R006C10
AR511GW-LM7 N/A V200R005C30,

V200R006C10
AR513W-V3M8 N/A V200R005C30,

V200R006C10
AR515GW-LM9-D N/A V200R007C00,

V200R008C20,
V200R009C00
AR531-2C-H N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R008C20,
V200R009C00

iMaster NCE-IP
AR531-F2C-H N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30,
V200R006C10,
V200R008C20,
V200R009C00
AR531G-U-D-H N/A V200R005C70,

V200R008C20,
V200R009C00
AR531GB-U-D-H N/A V200R005C70
AR531GP-H N/A V200R005C70
AR531GPe-U-H N/A V200R005C70,

V200R008C20,
V200R009C00
AR531GR-U-H N/A V200R005C70,

V200R008C20,
V200R009C00
AR531GZ-U-D N/A V200R007C00,

V200R009C00
AR532 N/A V200R008C20,

V200R009C00
AR550-24FE-D-H N/A V200R005C70
AR550-8FE-D-H N/A V200R005C70
AR550C-2C6GE N/A V200R008C20,

V200R009C00
AR550C-2C6GE-2D N/A V200R009C00
AR550C-4GE N/A V200R008C20,

V200R009C00
AR550E N/A V200R009C00
AR5510-H10T1 V300R022C10 N/A
AR5510-H8P2TW1 V300R022C10 N/A
AR5510-L5T V300R022C10 N/A
AR5510-L5T-LTE4EA V300R022C10 N/A

iMaster NCE-IP
AR5710-H8T2TS1 V600R022C10 V600R022C00
AR5710-H8T2TS1-T V600R022C10 V600R022C00
AR611 N/A V300R021C00SPC100
AR611-LTE4EA N/A V300R022C00
AR611-S N/A V300R021C00SPC100
AR611E-S N/A V300R021C10,

V300R021C10SPC100,
V300R022C00
AR611W N/A V300R019C10
AR611W-LTE4CN N/A V300R019C10
AR611W-LTE6EA V300R022C10 V300R22C10
AR611W-S N/A V300R021C00SPC100
AR6120 N/A V300R019C00SPC200
AR6120-S N/A V300R019C10
AR6121 N/A V300R019C10
AR6121-S N/A V300R019C11
AR6121C-S N/A V300R019C11
AR6121E N/A V300R019C13SPC100
AR6121E-S N/A V300R021C00SPC100
AR6121EC-S N/A V300R021C00SPC100
AR6121K N/A V300R019C11
AR6140-16G4XG N/A V300R019C10
AR6140-9G-2AC N/A V300R019C10
AR6140-9G-R-2AC N/A V300R019C11
AR6140-S N/A V300R019C10
AR6140E-9G-2AC N/A V300R019C13SPC100
AR6140E-S N/A V300R021C00SPC100
AR6140H-S N/A V300R019C11
AR6140K-9G-2AC N/A V300R019C11
AR617VW N/A V300R019C10

iMaster NCE-IP
AR617VW-LTE4EA N/A V300R019C10
AR6280 N/A V300R019C00
AR6280-S N/A V300R019C11
AR6280C-S N/A V300R021C00SPC100
AR6280K N/A V300R019C11
AR6300 N/A V300R019C00
AR6300-S N/A V300R019C00
AR6300C-S N/A V300R021C00SPC100
AR6300K N/A V300R019C11
AR631I-LTE4CN V300R022C10 V300R22C10
AR631I-LTE4EA V300R022C10 V300R22C10
AR6500-10 V300R022C10 N/A
AR651-LTE6EA N/A V300R019C10
AR6510-L11T1X2 V300R022C10 N/A
AR6510-L5T4S4 V300R022C10 N/A
AR651C N/A V300R019C00
AR651F-Lite N/A V300R019C10
AR651K N/A V300R019C11
AR651U-A4-LTE4EA N/A V300R019C10
AR651U-A4-LTE6EA N/A V300R019C10
AR651W N/A V300R019C10
AR657 N/A V300R019C10
AR6710-L26T2X4 V600R022C10 V600R021C10,

V600R022C00
AR6710-L26T2X4-T V600R022C10 V600R021C10,

V600R022C00
AR6710-L50T2X4 V600R022C10 V600R021C10,

V600R022C00
AR6710-L50T2X4-T V600R022C10 V600R021C10,

V600R022C00
AR6710-L8T3TS1X2 V600R022C10 V600R022C00

iMaster NCE-IP
AR6710-L8T3TS1X2-T V600R022C10 V600R022C00
AR720 N/A V300R021C00SPC100
AR730 N/A V300R021C00SPC100
R1600 N/A V100R001,

V200R007
R2500 N/A V100R001
R2600 N/A V200R007
RU-5G-101 N/A V300R022C00,

V300R022C00SPC100
SRG1301 N/A V300R019C11
SRG1311 N/A V300R021C00SPC100
SRG1320 N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30
SRG1320E N/A V200R008C30,

V200R008C50
SRG1320V N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30
SRG1320VW N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30
SRG1320W N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30
SRG1321 N/A V300R019C11

iMaster NCE-IP
SRG1340-16G4XG N/A V300R019C11
SRG1340-9G N/A V300R019C10
SRG1340E N/A V300R021C00SPC100
SRG2304 N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30
SRG2320 N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30
SRG2320D N/A V200R005C00,

V200R005C10,
V200R005C20,
V200R005C30
SRG2320E N/A V200R005C20,

V200R005C30
SRG2320EI N/A V200R008C30,

V200R008C50
SRG2340E N/A V200R008C30,

V200R008C50
SRG3340 N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30
SRG3360 N/A V200R002C02,

V200R003C00,
V200R005C00,
V200R005C10,
V200R005C20,
V200R005C30

iMaster NCE-IP
SRG33X0 N/A V300R019C10
13.4 RM9000 Series

The following table lists the RM9000 series NE supported.
Table 13-11 RM9000 series
RM9000 Series N/A V300R002C02
13.5 Switch Series

The following table lists the switch NEs supported.
NOTE
● NCE is insensitive to the software version of S switches. If the old software version of
the S switch is matched, the new software version of the S switch is supported.
● Pay attention to the following for decoupled devices:
1. If NCE needs to support the new functions provided in new device versions, check
and upgrade NCE to the corresponding version.
2. If NCE needs to support the new alarms provided in new device versions, check and
upgrade NCE to the corresponding version.
3. If new device versions involve command line changes, check and upgrade NCE to the
corresponding version. Otherwise, the interaction between NCE and the devices may
be disrupted.
4. If new boards are added in new device versions, there is no need to upgrade NCE.
Table 13-12 S series
E628 N/A V200R008C00,

V200R009C00
E628-X N/A V200R008C00,

V200R009C00
E652 N/A V200R008C00,

V200R009C00
E652-X N/A V200R008C00,

V200R009C00

iMaster NCE-IP
FM-S5720-12TP-LI-AC N/A V200R021C00,

V200R021C00
FM-S5720-12TP-PWR-LI- N/A V200R021C00,

AC V200R021C00
FM-S5720-28P-LI-AC N/A V200R021C00,

V200R021C00
FM-S5720-52X-LI-48S- N/A V200R021C00,

AC1 V200R021C00
FM-S5720I-12X-PWH-SI- N/A V200R021C00,

DC V200R021C00
FM-S5720I-12X-SI-AC N/A V200R021C00,

V200R021C00
FM-S5720I-28X-PWH-SI- N/A V200R021C00,

AC V200R021C00
FM-S5720I-28X-SI-AC N/A V200R021C00,

V200R021C00
FM-S5720S-12TP-LI-AC N/A V200R021C00,

V200R021C00
FM-S5720S-12TP-PWR- N/A V200R021C00,

LI-AC V200R021C00
FM-S5720S-28P-LI-AC N/A V200R021C00,

V200R021C00
FM-S5735-L24P4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L24P4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L24T4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L24T4X-A1 N/A V200R021C00
FM-S5735-L24T4X-D1 N/A V200R020C30
FM-S5735-L24T4X-IA1 N/A V200R020C30

iMaster NCE-IP
FM-S5735-L32ST4X-A1 N/A V200R021C00
FM-S5735-L32ST4X-D1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L48P4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L48P4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L48T4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L48T4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L8P4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L8P4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L8P4X-IA1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L8T4S-A1 N/A V200R020C30
FM-S5735-L8T4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-L8T4X-IA1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735-S24T4X V200R022C10 V200R021C00,

V200R021C00,
V200R022C00

iMaster NCE-IP
FM-S5735-S48T4X V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-H24S4XC-A V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-H24T4X-A N/A V200R022C10
FM-S5735S-H24T4XC-A V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-H24U4XC-A V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-H48T4XC-A V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-H48U4XC-A V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L24P4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L24P4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L24T4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L24T4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L32ST4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00

iMaster NCE-IP
FM-S5735S-L48P4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L48P4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L48T4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L48T4X-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L8P4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-L8T4S-A1 V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-S48T4S-A V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5735S-S48T4X-A V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5736-S24S4XC N/A V200R021C10
FM-S5736-S24T4XC V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5736-S24U4XC V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5736-S24UM4XC V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5736-S48S4XC N/A V200R021C10

iMaster NCE-IP
FM-S5736-S48T4XC V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S5736-S48U4XC V200R022C10 V200R021C00,

V200R021C00,
V200R022C00
FM-S6735-S24X6C N/A V200R022C00,

V200R022C10
Huawei-S5700-8P-G N/A V200R010C00
S12700E-12 N/A V200R019C00SPC210
S12700E-4 N/A V200R019C00SPC210
S12700E-8 N/A V200R019C00SPC210
S12704 N/A V200R010C00
S12708 N/A V200R005C00,

V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00
S12710 N/A V200R010C00
S12712 N/A V200R005C00,

V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R019C10
S1730S-H24T4S-A N/A V200R019C10
S1730S-H48T4S-A N/A V200R019C10
S1730S-S24P4S-A N/A V200R019C00SPC210
S1730S-S24P4S-A1 N/A V200R020C10SPC100
S1730S-S24P4S-MA N/A V200R019C10
S1730S-S24T4S-A N/A V200R019C00SPC210
S1730S-S24T4S-A1 N/A V200R020C10SPC100

iMaster NCE-IP
S1730S-S24T4S-MA N/A V200R019C10
S1730S-S24T4X-A N/A V200R019C10
S1730S-S24T4X-A1 N/A V200R020C10SPC100
S1730S-S48P4S-A N/A V200R019C10
S1730S-S48P4S-A1 N/A V200R020C10SPC100
S1730S-S48T4S-A N/A V200R019C00SPC210
S1730S-S48T4S-A1 N/A V200R020C10SPC100
S1730S-S48T4X-A1 N/A V200R020C10SPC100
S1730S-S8P4S-A1 N/A V200R020C10SPC100
S1730S-S8T4S-A1 N/A V200R020C10SPC100
S200-24P4S N/A V200R020C10SPC100
S200-24T4S N/A V200R020C10SPC100
S200-48T4S N/A V200R020C10SPC100
S200-8P4S N/A V200R020C10SPC100
S200-8T4S N/A V200R020C10SPC100
S2016TP-EA N/A Release 2107P07,

Version 3.10
S2016TP-MI N/A Release

2107P03V200R001B60D0
10SP01
(COMWAREV300R002B1
6D019SP19),
Version 3.10,
VRP Software,
VRP310-R2107P01

iMaster NCE-IP
S2016TP-PWR-EA N/A Release 2107P07

Bootrom Version is 518
VRP Lanswitch Platform
Software Version
COMWAREV300R002B16
D019SP21 Quidway
S2016TP-PWR-EA
Software Version
V200R001B60D010SP06
Quidway S2016TP-PWR-
EA Product Version
S2016TP-PWR-
EA-2107P07 Web
Network Manager
Version
WNMV300R001B08D040
,
Version 3.10
S2309TP-EI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S2309TP-PWR-EI N/A V100R003,

V100R005,
V100R006,
V100R006C03,
V100R006C05
S2309TP-SI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S2318TP-EI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05

iMaster NCE-IP
S2318TP-SI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S2320-12TP-EI-AC N/A V200R011C10,

V200R012C00
S2320-12TP-EI-DC N/A V200R011C10,

V200R012C00
S2320-12TP-PWR-EI-AC N/A V200R011C10,

V200R012C00
S2320-28P-PWR-EI-ACF N/A V200R011C10,

V200R012C00
S2320-28TP-EI-AC N/A V200R011C10,

V200R012C00
S2320-28TP-EI-DC N/A V200R011C10,

V200R012C00

V200R012C00
S2320-52TP-EI-AC N/A V200R011C10,

V200R012C00

V200R012C00
S2326TP-EI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05

V100R005,
V100R006,
V100R006C03,
V100R006C05

iMaster NCE-IP
S2326TP-SI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S2328P-EI-AC N/A V100R006C05

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10
S2350-28TP-EI-AC N/A V200R003C00,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10
S2350-28TP-EI-DC N/A V200R005C00,

V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10

iMaster NCE-IP

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10
S2352P-EI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S2403H-EI N/A RELEASE 0018 VRP (tm)

Lanswitch Platform
Software Version
V100R003B23D002SP08
Quidway S2403H-EI
Software Version
V300R001B01D020
Bootrom Version is 150,
Version 3.10,
VRP (R) Software
S2403TP-PWR-EA N/A V200R001
S2700-18TP-EI-AC N/A V100R005,

V100R006
S2700-18TP-SI-AC N/A V100R005,

V100R006
S2700-26TP-EI-AC N/A V100R005,

V100R006
S2700-26TP-EI-DC N/A V100R005,

V100R006
S2700-26TP-PWR-EI N/A V100R005,

V100R006
S2700-26TP-SI-AC N/A V100R005,

V100R006

iMaster NCE-IP
S2700-52P-EI-AC N/A V100R005,

V100R006
S2700-52P-PWR-EI N/A V100R006
S2700-9TP-EI-AC N/A V100R005,

V100R006
S2700-9TP-EI-DC N/A V100R005,

V100R006
S2700-9TP-PWR-EI N/A V100R005,

V100R006
S2700-9TP-SI-AC N/A V100R005,

V100R006
S2710-52P-PWR-SI N/A V100R006
S2710-52P-SI-AC N/A V100R006
S2720-12TP-EI-AC N/A V200R011C10,

V200R012C00

V200R012C00
S2720-28TP-EI-V2-AC N/A V200R011C10,

V200R012C00

V200R012C00
S2720-28TP-PWR-EI-ACL N/A V200R011C10,

V200R012C00
S2720-52TP-EI-AC N/A V200R011C10,

V200R012C00

V200R012C00
S2730S-S16FP4S-A N/A V200R020C10SPC100
S2730S-S16FT4S-A N/A V200R020C10SPC100

iMaster NCE-IP
S2750-20TP-PWR-EI-AC N/A V200R003,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S2750-28TP-EI-AC N/A V200R003,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S300-16P4S N/A V200R020C10SPC100
S300-16T4S N/A V200R020C10SPC100
S300-24P4S N/A V200R020C10SPC100
S300-24T4S N/A V200R020C10SPC100
S300-48T4S N/A V200R020C10SPC100
S300-8P4S N/A V200R020C10SPC100
S300-8T4S N/A V200R020C10SPC100
S3000 N/A VRP3.10 R0040[02]
S3026S-SI N/A RELEASE 0020 (VRP

Version
V100R003B23D002SP02
)S3026S-SI Software
Version
V100R001B02D005SP02S
3026S-SI Product Version
S3026S-SI-0020,
Version 3.10,
VRP (R) Software
S3050C N/A Release 0033,

Version 3.10
S3300-52P-EI N/A V100R006C05
S3318TP-EI-MC N/A V100R005,

V100R006,
V100R006C03,
V100R006C05

iMaster NCE-IP
S3326C-HI N/A V100R006,

V200R001
S3328TP-EI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S3328TP-EI-24S N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S3328TP-EI-MC N/A V100R005,

V100R006,
V100R006C03,
V100R006C05

V100R005,
V100R006,
V100R006C03,
V100R006C05
S3328TP-SI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S3352P-EI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05

iMaster NCE-IP
S3352P-EI-24S N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S3352P-EI-48S N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S3352P-PWR-EI N/A V100R003,

V100R005,
V100R006,
V100R006C03,
V100R006C05
S3352P-SI N/A V100R002,

V100R003,
V100R005,
V100R006,
V100R006C03,
V100R006C05
S3352P-SI-48 N/A V100R006C03,

V100R006C05
S3352P-SI-48S N/A V100R005,

V100R006
S3528F-EA N/A Release 5303,

Version 5.20,
VRP Software
S3528G N/A Version 3.10
S3528P N/A Feature 1532L01,

Release 0025P03 Version
3.10,
Version 3.10

iMaster NCE-IP
S3528P-EA N/A Release 5303,

Version 5.20,
VRP Software
S3552F-EA N/A VRP3.1
S3552F-HI N/A S3552-VRP310-R0030
S3552P-EA N/A Release 5303 VRP

Platform Software
Version
COMWAREV500R002B36
D009 S3552P-EA
Software Version
V500R003B04D008SP02
Bootrom Version is 142,
Version 5.20,
VRP Software
S3700-26C-HI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003
S3700-28TP-EI-24S-AC N/A V100R005,

V100R006
S3700-28TP-EI-AC N/A V100R005,

V100R006
S3700-28TP-EI-DC N/A V100R005,

V100R006
S3700-28TP-EI-MC-AC N/A V100R005,

V100R006
S3700-28TP-PWR-EI N/A V100R005,

V100R006
S3700-28TP-PWR-SI N/A V100R005,

V100R006
S3700-28TP-SI-AC N/A V100R005,

V100R006
S3700-28TP-SI-DC N/A V100R005,

V100R006

iMaster NCE-IP
S3700-52P-EI-24S-AC N/A V100R005,

V100R006
S3700-52P-EI-24S-DC N/A V100R005,

V100R006
S3700-52P-EI-48S-AC N/A V100R005,

V100R006
S3700-52P-EI-48S-DC N/A V100R005,

V100R006
S3700-52P-EI-AC N/A V100R005,

V100R006
S3700-52P-EI-DC N/A V100R005,

V100R006
S3700-52P-PWR-EI N/A V100R005,

V100R006
S3700-52P-PWR-SI N/A V100R005,

V100R006
S3700-52P-SI-AC N/A V100R005,

V100R006
S3900 N/A VRP3.10 R1602[01]
S3928P-EI N/A Release 1602P10,

Release 1602P11,
S3900EI-VRP310-
R1602P06,
Version 3.10,
Version 3.10
S3928P-SI N/A Release 1602P10,

Version 3.10
S3952P N/A S3900EI-VRP310—

R1602P06
S3952P-EI N/A V100R002
S3952P-PWR-EI N/A Release 1602P10,

Version 3.10
S3952P-SI N/A Release 1602P10,

Version 3.10

iMaster NCE-IP
S500-16P4S N/A V200R020C10SPC100
S500-16T4S N/A V200R020C10SPC100
S500-24P4S N/A V200R020C10SPC100
S500-24T4S N/A V200R020C10SPC100
S500-32ST4X N/A V200R020C10SPC100
S500-48T4S N/A V200R020C10SPC100
S500-8P4S N/A V200R020C10SPC100
S500-8T4S N/A V200R020C10SPC100
S5124P-EI N/A Release 2201 VRP3.10

R2200,
Version 3.10
S5148P-EI N/A Release 2201,

Version 3.10
S5300-10P-LI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-10P-PWR-LI-AC N/A V200R008C10,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5300-28P-LI-24S-4AH N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-28P-LI-24S-BAT N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-28P-LI-4AH N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5300-28P-LI-AC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-28P-LI-BAT N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-28P-LI-DC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5300-28TP-PWR-LI-AC N/A V200R008C10,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-28X-LI-24S-AC N/A V200R003,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-28X-LI-24S-DC N/A V200R003,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-28X-LI-AC N/A V200R003,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5300-28X-LI-DC N/A V200R003,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-52P-LI-AC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-52P-LI-DC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5300-52X-LI-48CS-AC N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-52X-LI-48CS-DC N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-52X-LI-AC N/A V200R005C00,

V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5300-52X-LI-DC N/A V200R005C00,

V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5306TP-LI N/A V100R006
S5306TP-LI-AC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5310-28C-EI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5310-52C-EI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-12P-LI-BAT N/A V200R011C10,

V200R012C00

iMaster NCE-IP
S5320-12TP-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-12TP-LI-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00

V200R011C00,
V200R011C10,
V200R012C00
S5320-12X-PWR-LI-AC N/A V200R011C10,

V200R012C00
S5320-28P-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28P-PWR-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28P-SI N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28P-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-28P-SI-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-28TP-LI-AC N/A V200R011C10,

V200R012C00
S5320-28X-LI-24S-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28X-LI-24S-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28X-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28X-LI-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28X-PWR-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28X-PWR-SI N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-28X-PWR-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-28X-PWR-SI-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-28X-SI-24S-AC N/A V200R011C10,

V200R012C00
S5320-28X-SI-24S-DC N/A V200R011C10,

V200R012C00
S5320-28X-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-28X-SI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-32C-HI-24S-AC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-32C-HI-24S-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-32P-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-32P-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-32X-EI-24S-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-32X-EI-24S-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-32X-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-32X-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-36C-EI-28S-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-36C-EI-28S-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-36C-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-36C-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-36C-PWR-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-36C-PWR-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-36PC-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-36PC-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-50X-EI-46S-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-50X-EI-46S-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-50X-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-50X-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-52P-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-52P-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-52P-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-52P-PWR-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-52P-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-52P-SI-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-LI-24S-AC1 N/A V200R020C00
S5320-52X-LI-48S-AC N/A V200R013C00
S5320-52X-LI-48S-AC1 N/A V200R020C00
S5320-52X-LI-48S-DC N/A V200R013C00
S5320-52X-LI-48S-DC1 N/A V200R020C00
S5320-52X-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-52X-LI-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-PWR-LI-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-PWR-SI N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-PWR-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-PWR-SI-ACF N/A V200R008C10,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-PWR-SI-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-52X-SI-48S N/A V200R013C00
S5320-52X-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-52X-SI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-56C-EI-48S-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-56C-EI-48S-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-56C-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-56C-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5320-56C-HI-AC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-56C-HI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-56C-PWR-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-56C-PWR-EI-ACF N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5320-56PC-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5320-56PC-EI-DC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5321-28X-SI-24S-AC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5321-28X-SI-24S-DC N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S5321-28X-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5321-28X-SI-DC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5321-52P-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5321-52X-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5321-52X-SI-DC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5324TP-PWR-SI N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5324TP-SI N/A V100R003,

V100R005,
V100R006,
V200R012C00
S5324TP-SI-AC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5324TP-SI-DC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5328-HI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5328-HI-24S N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5328C-EI N/A V100R002,

V100R003,
V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5328C-EI-24 N/A V100R002
S5328C-EI-24S N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5328C-HI N/A V100R006
S5328C-HI-24S N/A V100R006

iMaster NCE-IP
S5328C-PWR-EI N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5328C-PWR-SI N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5328C-SI N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5330-36C-HI-24S N/A V200R013C00
S5330-48C-SI-AC N/A V200R012C00
S5330-56C-PWH-SI N/A V200R012C00
S5330-56C-PWH-SI-AC N/A V200R012C00
S5330-60C-HI-48S N/A V200R013C00
S5330-68C-SI N/A V200R011C10,

V200R012C00
S5330-68C-SI-AC N/A V200R011C10,

V200R012C00
S5331-H24P4XC N/A V200R019C00SPC210
S5331-H24P4XC-V1 V600R022C10 N/A
S5331-H24T4XC N/A V200R019C00SPC210
S5331-H48P4XC N/A V200R019C00SPC210
S5331-H48T4XC N/A V200R019C00SPC210
S5331-H48T4XC-V1 V600R022C10 N/A
S5331-S24N4X2Q-A N/A V200R022C00
S5331-S24P4X N/A V200R021C10,

V200R022C00
S5331-S24S8T4X-A V200R022C10 N/A

iMaster NCE-IP
S5331-S24S8T4X-D V200R022C10 N/A
S5331-S24T4X N/A V200R021C10,

V200R022C00
S5331-S24T4X-A N/A V200R021C10,

V200R022C00
S5331-S24T4X-A-V1 V600R022C10 N/A
S5331-S24T4X-D N/A V200R021C10,

V200R022C00
S5331-S32ST4X N/A V200R021C01
S5331-S32ST4X-A N/A V200R021C01
S5331-S32ST4X-D N/A V200R021C01
S5331-S48P4X N/A V200R021C10,

V200R022C00
S5331-S48S4X N/A V200R021C01
S5331-S48S4X-A N/A V200R021C01
S5331-S48S4X-D N/A V200R021C01
S5331-S48T4X N/A V200R021C10
S5331-S48T4X-A N/A V200R021C10,

V200R022C00
S5332-H24S4Y4Q N/A V200R020C00
S5332-H24S6Q N/A V200R019C00SPC210
S5332-H24UM2CC N/A V200R019C10SPC500
S5332-H48S6Q N/A V200R019C00SPC210
S5335-L10T4X-A-V2 N/A V200R022C00
S5335-L10T4X-D-V2 N/A V200R022C00
S5335-L12P4S-A N/A V200R019C00SPC210
S5335-L12T4S-A N/A V200R019C00SPC210
S5335-L12T4S-D N/A V200R020C00
S5335-L16T4X-A-V2 N/A V600R022C00
S5335-L24P4X-A N/A V200R019C00SPC210
S5335-L24P4X-A1 N/A V200R020C10SPC100

iMaster NCE-IP
S5335-L24P4XE-A-V2 N/A V600R022C00
S5335-L24T4X-A N/A V200R019C00SPC210
S5335-L24T4X-A1 N/A V200R020C10SPC100
S5335-L24T4X-D N/A V200R020C00
S5335-L24T4X-D1 N/A V200R020C10SPC100
S5335-L24T4XE-A-V2 N/A V200R022C00
S5335-L24T4XE-D-V2 N/A V200R022C00
S5335-L32ST4X-A N/A V200R019C00SPC210
S5335-L32ST4X-A1 N/A V200R020C10SPC100
S5335-L32ST4X-D N/A V200R020C00
S5335-L32ST4X-D1 N/A V200R020C10SPC100
S5335-L48T4X-A N/A V200R019C10
S5335-L48T4X-A1 N/A V200R020C10SPC100
S5335-L48T4XE-A-V2 N/A V200R022C00
S5335-L8P2T4X-A-V2 N/A V200R022C00
S5335-L8P4X-A1 N/A V200R020C10SPC100
S5335-L8T4X-A1 N/A V200R020C10SPC100
S5335-L8T4X-D1 N/A V200R020C10SPC100
S5335-S24P4X N/A V200R019C00SPC210
S5335-S24P4XE-V2 N/A V600R022C00
S5335-S24T4X N/A V200R019C00SPC210
S5335-S24T4XE-V2 N/A V200R022C00
S5335-S24U4XE-V2 N/A V200R022C00
S5335-S32ST4X N/A V200R019C00SPC210
S5335-S48P4X N/A V200R019C00SPC210
S5335-S48P4XE-V2 N/A V200R022C00
S5335-S48S4X N/A V200R019C00SPC210
S5335-S48T4X N/A V200R019C00SPC210
S5335-S48T4XE-V2 N/A V200R022C00
S5335-S48U4XE-V2 N/A V200R022C00

iMaster NCE-IP
S5336-S24S4X-A N/A V200R020C10SPC100
S5336-S24S4X-D N/A V200R020C10SPC100
S5336-S24S4XC N/A V200R020C00
S5336-S24T4XC N/A V200R020C00
S5336-S24U4XC N/A V200R020C00
S5336-S24UM4XC N/A V200R020C00
S5336-S48S4X-A N/A V200R020C00
S5336-S48S4X-D N/A V200R020C00
S5336-S48S4XC N/A V200R020C00
S5336-S48T4XC N/A V200R020C00
S5336-S48U4XC N/A V200R020C00
S5348TP-PWR-SI N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5348TP-SI N/A V100R003,

V100R005,
V100R006,
V200R008C00

iMaster NCE-IP
S5348TP-SI-AC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5348TP-SI-DC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5352C-EI N/A V100R002,

V100R003,
V100R005,
V100R006,
V200R001C00,
V200R005C00,
V200R005C00,
V200R008C00

iMaster NCE-IP
S5352C-PWR-EI N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5352C-PWR-SI N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5352C-SI N/A V100R003,

V100R005,
V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5531-H48HB4XZ V200R022C10 N/A
S5531-S32ST4X V200R022C10 N/A
S5624F N/A Feature 1532L01,

Release 1602P10 3.10,
VRP310-R1602P06,
Versio 3.10
S5624P N/A Release 1602P10 VRP

V3.10 R1510P15 3.10
Feature 1532L01,
Version 3.10
S5624P-PWR N/A Release 1602P10

S5624P-PWR Software
Version
V100R002B60D052SP01
VRP Version
COMWAREV300R002B16
D019SP21,
Version 3.10,
VRP Software
S5628C-HI-AC N/A V200R001
S5648P N/A Release 1602P10,

Version 3.10

iMaster NCE-IP
S5700-10P-LI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-10P-PWR-LI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-24TP-PWR-SI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-24TP-SI-AC N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S5700-24TP-SI-DC N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-26X-SI-12S-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-28C-EI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-28C-EI-24S N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-28C-HI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S5700-28C-HI-24S N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-28C-PWR-EI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-28C-PWR-SI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-28C-SI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-28P-LI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S5700-28P-LI-24S-4AH N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28P-LI-24S-BAT N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28P-LI-4AH N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28P-LI-AC N/A V200R001,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5700-28P-LI-BAT N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28P-LI-DC N/A V200R001,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28P-PWR-LI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-28P-PWR-LI-AC N/A V200R001,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28TP-LI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28X-LI-24CS-AC N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00
S5700-28X-LI-24CS-DC N/A V200R003C02,

V200R005C00,
V200R006C00,
V200R007C00
S5700-28X-LI-24S-AC N/A V200R003,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28X-LI-24S-DC N/A V200R003,

V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5700-28X-LI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28X-LI-DC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-28X-PWR-LI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5700-48TP-PWR-SI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-48TP-SI-AC N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-48TP-SI-DC N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-52C-EI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S5700-52C-PWR-EI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-52C-PWR-SI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-52C-SI N/A V100R005,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-52P-LI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-52P-LI-AC N/A V200R001,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5700-52P-LI-DC N/A V200R001,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-52P-PWR-LI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5700-52P-PWR-LI-AC N/A V200R001,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-52X-LI-48CS-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-52X-LI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5700-52X-LI-DC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-52X-PWR-LI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700-6TP-LI-AC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S5700S-28P-LI-AC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700S-28P-PWR-LI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700S-28X-LI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5700S-52P-LI-AC N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5700S-52X-LI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5701-28X-LI-24S-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5701-28X-LI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5710-108C-HI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-108C-PWR-HI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S5710-108C-PWR-HI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-28C-EI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-28C-LI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-28C-PWR-EI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-28C-PWR-EI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-28C-PWR-LI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S5710-28X-LI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5710-52C-EI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-52C-LI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-52C-PWR-EI N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-52C-PWR-EI-AC N/A V200R002,

V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S5710-52C-PWR-LI N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S5710-52X-LI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-12TP-LI-AC N/A V200R010C00
S5720-12TP-PWR-LI-AC N/A V200R010C00
S5720-12X-LI-AC N/A V200R012C00
S5720-12X-PWR-LI-AC N/A V200R012C00
S5720-14X-PWH-SI-AC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-16X-PWH-LI-AC N/A V200R010C00
S5720-28P-LI-AC N/A V200R010C00
S5720-28P-PWR-LI-AC N/A V200R010C00
S5720-28P-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-28TP-LI-AC N/A V200R010C00
S5720-28TP-PWR-LI-AC N/A V200R010C00
S5720-28TP-PWR-LI-ACL N/A V200R010C00
S5720-28X-LI-24S-AC N/A V200R010C00
S5720-28X-LI-24S-DC N/A V200R010C00
S5720-28X-LI-AC N/A V200R010C00
S5720-28X-LI-DC N/A V200R010C00
S5720-28X-PWH-LI-AC N/A V200R011C00,

V200R011C10,
V200R012C00

iMaster NCE-IP
S5720-28X-PWR-LI-ACF N/A V200R012C00
S5720-28X-PWR-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-28X-PWR-SI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-28X-SI-12S-AC N/A V200R012C00
S5720-28X-SI-24S-AC N/A V200R010C00
S5720-28X-SI-24S-DC N/A V200R010C00
S5720-28X-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-28X-SI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-30C-LI-AC N/A V200R012C00
S5720-30C-PWR-LI-AC N/A V200R012C00

iMaster NCE-IP
S5720-32C-HI-24S-AC N/A V200R006C00,

V200R007C00,
V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-32P-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-32X-EI-24S-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-32X-EI-24S-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00
S5720-32X-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-32X-EI-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5720-36C-EI-28S-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-36C-EI-28S-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00
S5720-36C-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-36C-EI-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00
S5720-36C-PWR-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-36C-PWR-EI-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00
S5720-36PC-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5720-50X-EI-46S-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-50X-EI-46S-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00
S5720-50X-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-50X-EI-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00
S5720-52P-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-52P-LI-AC N/A V200R010C00
S5720-52P-PWR-LI-AC N/A V200R010C00
S5720-52P-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5720-52X-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-52X-LI-24S-AC1 N/A V200R020C00
S5720-52X-LI-48S-AC N/A V200R013C00
S5720-52X-LI-48S-AC1 N/A V200R020C00
S5720-52X-LI-48S-DC1 N/A V200R020C00
S5720-52X-LI-AC N/A V200R010C00
S5720-52X-LI-DC N/A V200R010C00
S5720-52X-PWR-LI-ACF N/A V200R011C10,

V200R012C00
S5720-52X-PWR-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-52X-PWR-SI-ACF N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-52X-PWR-SI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-52X-SI-48S N/A V200R013C00

iMaster NCE-IP
S5720-52X-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-52X-SI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-54C-LI-AC N/A V200R012C00
S5720-54C-PWR-LI-AC N/A V200R012C00
S5720-56C-EI-48S-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-56C-EI-48S-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00
S5720-56C-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-56C-EI-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5720-56C-HI-AC N/A V200R006C00,

V200R007C00,
V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-56C-PWR-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-56C-PWR-EI-AC1 N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-56C-PWR-EI-DC N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00
S5720-56C-PWR-HI-AC N/A V200R006C00,

V200R007C00,
V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720-56C-PWR-HI-AC1 N/A V200R009C00,

V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5720-56PC-EI-AC N/A V200R007C00,

V200R008C00,
V200R009C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720I-12X-PWH-SI-DC N/A V200R012C00
S5720I-12X-SI-AC N/A V200R012C00
S5720I-28X-PWH-SI-AC N/A V200R012C00
S5720I-28X-SI-AC N/A V200R012C00
S5720S-12TP-LI-AC N/A V200R010C00
S5720S-12TP-PWR-LI-AC N/A V200R010C00
S5720S-28P-LI-AC N/A V200R010C00
S5720S-28P-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720S-28TP-PWR-LI- N/A V200R010C00

ACL
S5720S-28X-LI-24S-AC N/A V200R010C00
S5720S-28X-LI-AC N/A V200R010C00
S5720S-28X-PWR-LI-AC N/A V200R010C00
S5720S-28X-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720S-28X-SI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S5720S-52P-LI-AC N/A V200R010C00
S5720S-52P-PWR-LI-AC N/A V200R010C00
S5720S-52P-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720S-52X-LI-24S-AC1 N/A V200R020C00
S5720S-52X-LI-AC N/A V200R010C00
S5720S-52X-PWR-LI-AC N/A V200R010C00
S5720S-52X-SI-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5720S-52X-SI-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S5721-28X-SI-24S-AC N/A V200R011C10,

V200R012C00
S5730-36C-HI N/A V200R012C00
S5730-36C-HI-24S N/A V200R013C00
S5730-36C-PWH-HI N/A V200R012C00
S5730-44C-HI N/A V200R012C00
S5730-44C-HI-24S N/A V200R013C00
S5730-44C-PWH-HI N/A V200R012C00
S5730-48C-PWR-SI-AC N/A V200R011C10
S5730-48C-SI-AC N/A V200R011C10
S5730-56C-PWH-SI N/A V200R012C00

iMaster NCE-IP
S5730-60C-HI N/A V200R012C00
S5730-60C-HI-48S N/A V200R013C00
S5730-60C-PWH-HI N/A V200R012C00
S5730-68C-HI N/A V200R012C00
S5730-68C-HI-48S N/A V200R013C00
S5730-68C-PWH-HI N/A V200R012C00
S5730-68C-PWR-SI N/A V200R011C10
S5730-68C-PWR-SI-AC N/A V200R011C10
S5730-68C-SI-AC N/A V200R011C10
S5731-H24HB4XZ N/A V200R021C10
S5731-H24P4XC N/A V200R019C00SPC210
S5731-H24P4XC-K N/A V200R019C10
S5731-H24T4XC N/A V200R019C00SPC210
S5731-H24T4XC-K N/A V200R019C10
S5731-H48HB4XZ N/A V200R021C10
S5731-H48P4XC N/A V200R019C00SPC210
S5731-H48P4XC-K N/A V200R019C10
S5731-H48T4XC N/A V200R019C00SPC210
S5731-H48T4XC-B N/A V200R020C00
S5731-S24N4X2Q-A N/A V200R022C00
S5731-S24P4X N/A V200R019C00SPC210
S5731-S24T4X N/A V200R019C00SPC210
S5731-S24T4X-A N/A V200R021C10
S5731-S24T4X-D N/A V200R021C10
S5731-S24UN4X2Q N/A V200R022C00
S5731-S32ST4X N/A V200R021C01
S5731-S32ST4X-A N/A V200R021C01
S5731-S32ST4X-D N/A V200R021C01
S5731-S48P4X N/A V200R019C00SPC210

iMaster NCE-IP
S5731-S48P4X-A N/A V200R021C10
S5731-S48S4X N/A V200R021C01
S5731-S48S4X-A N/A V200R021C01
S5731-S48T4X N/A V200R019C00SPC210
S5731-S48T4X-A N/A V200R021C10,

V200R022C00
S5731-S8UM16UN2Q N/A V200R022C00
S5731S-H24HB4XZ-A N/A V200R021C10
S5731S-H24T4S-A N/A V200R019C00
S5731S-H24T4X-A N/A V200R019C10
S5731S-H24T4XC-A N/A V200R019C00SPC210
S5731S-H48HB4XZ-A N/A V200R021C10
S5731S-H48T4S-A N/A V200R019C00
S5731S-H48T4X-A N/A V200R019C10
S5731S-H48T4XC-A N/A V200R019C00SPC210
S5731S-S24N4X2Q-A1 N/A V200R022C00
S5731S-S24P4X-A N/A V200R019C00SPC210
S5731S-S24T4X-A N/A V200R019C00SPC210
S5731S-S24T4X-A1 N/A V200R021C10
S5731S-S24UN4X2Q-A N/A V200R022C00
S5731S-S32ST4X-A N/A V200R021C01
S5731S-S32ST4X-A1 N/A V200R021C01
S5731S-S48P4X-A N/A V200R019C00SPC210
S5731S-S48P4X-A1 N/A V200R021C10,

V200R022C00
S5731S-S48S4X-A N/A V200R021C01
S5731S-S48S4X-A1 N/A V200R021C01
S5731S-S48T4X-A N/A V200R019C00SPC210
S5731S-S48T4X-A1 N/A V200R021C10,

V200R022C00
S5731S-S8UM16UN2Q N/A V200R022C00

iMaster NCE-IP
S5732-H24S4X6QZ-TV2 V600R022C10 N/A
S5732-H24S4Y4Q N/A V200R020C00
S5732-H24S6Q N/A V200R019C00SPC210
S5732-H24S6Q-K N/A V200R019C10
S5732-H24UM2C-K N/A V200R020C00
S5732-H24UM2CC N/A V200R019C20
S5732-H48S6Q N/A V200R019C00SPC210
S5732-H48S6Q-K N/A V200R019C10
S5732-H48UM2C-K N/A V200R020C00
S5732-H48UM2CC N/A V200R019C20
S5732-H48UM4Y2CZ- V600R022C10 N/A

TV2
S5732-H48XUM2CC N/A V200R019C20
S5735-L10T4X-A-V2 V600R022C10 N/A
S5735-L12P4S-A N/A V200R019C00SPC210
S5735-L12T4S-A N/A V200R019C00SPC210
S5735-L12T4S-D N/A V200R020C00
S5735-L16T4X-QA-V2 V600R022C10 N/A
S5735-L24P4S-A N/A V200R019C00SPC210
S5735-L24P4S-A1 N/A V200R020C10SPC100
S5735-L24P4X-A N/A V200R019C00SPC210
S5735-L24P4X-A1 N/A V200R020C10SPC100
S5735-L24T4S-A N/A V200R019C00SPC210
S5735-L24T4S-A1 N/A V200R020C10SPC100
S5735-L24T4S-QA1 N/A V200R021C00
S5735-L24T4X-A N/A V200R019C00SPC210
S5735-L24T4X-A1 N/A V200R020C10SPC100
S5735-L24T4X-D N/A V200R020C00
S5735-L24T4X-D1 N/A V200R020C10SPC100
S5735-L24T4X-IA1 N/A V200R021C00

iMaster NCE-IP
S5735-L24T4X-QA-V2 V600R022C10 N/A
S5735-L24T4X-QA1 N/A V200R021C00
S5735-L32ST4X-A N/A V200R019C00SPC210
S5735-L32ST4X-A1 N/A V200R020C10SPC100
S5735-L32ST4X-D N/A V200R020C00
S5735-L32ST4X-D1 N/A V200R020C10SPC100
S5735-L48P4S-A1 N/A V200R020C10SPC100
S5735-L48P4X-A N/A V200R019C00SPC210
S5735-L48P4X-A1 N/A V200R020C10SPC100
S5735-L48T4S-A N/A V200R019C00SPC210
S5735-L48T4S-A1 N/A V200R020C10SPC100
S5735-L48T4X-A N/A V200R019C00SPC210
S5735-L48T4X-A1 N/A V200R020C10SPC100
S5735-L48T4XE-A-V2 V600R022C10 N/A
S5735-L8P4S-A1 N/A V200R020C10SPC100
S5735-L8P4S-QA1 N/A V200R021C00
S5735-L8P4X-A1 N/A V200R020C10SPC100
S5735-L8P4X-IA1 N/A V200R021C00
S5735-L8T4S-A1 N/A V200R020C10SPC100
S5735-L8T4S-QA1 N/A V200R021C00
S5735-L8T4X-A1 N/A V200R020C10SPC100
S5735-L8T4X-IA1 N/A V200R021C00
S5735-L8T4X-QA-V2 V600R022C10 N/A
S5735-S24P4X N/A V200R019C00SPC210
S5735-S24P4XE-V2 V600R022C10 N/A
S5735-S24T4X N/A V200R019C00SPC210
S5735-S24T4X-I N/A V200R019C10SPC500
S5735-S32ST4X N/A V200R019C00SPC210
S5735-S48P4X N/A V200R019C00SPC210
S5735-S48P4XE-V2 V600R022C10 N/A

iMaster NCE-IP
S5735-S48S4X N/A V200R019C00SPC210
S5735-S48T4X N/A V200R019C00SPC210
S5735-S4T2X-IA150G1 N/A V200R019C00SPC210
S5735-S8P2X-IA200G1 N/A V200R019C00SPC210
S5735-S8P2X-IA200H1 N/A V200R019C00SPC210
S5735I-S8U4XN-V2 V600R022C10 N/A
S5735S-H24S4XC-A N/A V200R020C00
S5735S-H24T4S-A N/A V200R019C00SPC210
S5735S-H24T4XC-A N/A V200R020C00
S5735S-H24U4XC-A N/A V200R020C00
S5735S-H48T4S-A N/A V200R019C00SPC210
S5735S-H48T4XC-A N/A V200R020C00
S5735S-H48U4XC-A N/A V200R020C00
S5735S-L12P4S-A N/A V200R019C00SPC210
S5735S-L12T4S-A N/A V200R019C00SPC210
S5735S-L24FT4S-A N/A V200R019C00SPC210
S5735S-L24P4S-A N/A V200R019C00SPC210
S5735S-L24P4S-A1 N/A V200R020C10SPC100
S5735S-L24P4S-MA N/A V200R019C00SPC210
S5735S-L24P4X-A N/A V200R019C00SPC210
S5735S-L24P4X-A1 N/A V200R020C10SPC100
S5735S-L24T4S-A N/A V200R019C00SPC210
S5735S-L24T4S-A1 N/A V200R020C10SPC100
S5735S-L24T4S-MA N/A V200R019C00SPC210
S5735S-L24T4X-A N/A V200R019C00SPC210
S5735S-L24T4X-A1 N/A V200R020C10SPC100
S5735S-L32ST4X-A N/A V200R019C00SPC210
S5735S-L32ST4X-A1 N/A V200R020C10SPC100
S5735S-L48FT4S-A N/A V200R019C00SPC210
S5735S-L48P4S-A N/A V200R019C00SPC210

iMaster NCE-IP
S5735S-L48P4S-A1 N/A V200R020C10SPC100
S5735S-L48P4X-A N/A V200R019C00SPC210
S5735S-L48P4X-A1 N/A V200R020C10SPC100
S5735S-L48T4S-A N/A V200R019C00SPC210
S5735S-L48T4S-A1 N/A V200R020C10SPC100
S5735S-L48T4S-MA N/A V200R019C10SPC500
S5735S-L48T4X-A N/A V200R019C00SPC210
S5735S-L48T4X-A1 N/A V200R020C10SPC100
S5735S-L8P4S-A1 N/A V200R020C10SPC100
S5735S-L8T4S-A1 N/A V200R020C10SPC100
S5735S-S24P4X-A N/A V200R019C10SPC500
S5735S-S24T4S-A N/A V200R019C00SPC210
S5735S-S24T4X-A N/A V200R019C10SPC500
S5735S-S32ST4X-A N/A V200R019C00SPC210
S5735S-S48P4X-A N/A V200R019C10SPC500
S5735S-S48T4S-A N/A V200R019C00SPC210
S5735S-S48T4X-A N/A V200R019C10SPC500
S5736-S24S4XC N/A V200R020C00
S5736-S24T4XC N/A V200R020C00
S5736-S24U4XC N/A V200R020C00
S5736-S24UM4XC N/A V200R020C00
S5736-S48S4X-A N/A V200R020C30
S5736-S48S4X-D N/A V200R020C30
S5736-S48S4XC N/A V200R020C00
S5736-S48T4XC N/A V200R020C00
S5736-S48U4XC N/A V200R020C00
S628-E N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S628-PWR-E N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S628X-E N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S628X-PWR-E N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S6320-26Q-EI-24S-AC N/A V200R009C00,

V200R010C00,
V200R012C00
S6320-26Q-EI-24S-DC N/A V200R009C00,

V200R010C00,
V200R012C00
S6320-26Q-SI-24S-AC N/A V200R012C00
S6320-30C-EI-24S-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R012C00
S6320-30C-EI-24S-DC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R012C00
S6320-30L-HI-24S N/A V200R012C00
S6320-32C-PWH-SI N/A V200R012C00
S6320-32C-SI-AC N/A V200R012C00
S6320-32C-SI-DC N/A V200R012C00
S6320-32X-SI-32S-AC N/A V200R012C00
S6320-48Q-SI-48S-AC N/A V200R012C00

iMaster NCE-IP
S6320-50L-HI-48S N/A V200R012C00
S6320-52X-PWH-SI-ACF N/A V200R012C00
S6320-54C-EI-48S N/A V200R010C00,

V200R012C00
S6320-54C-EI-48S-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R012C00
S6320-54C-EI-48S-DC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R012C00
S6320-56C-PWH-SI N/A V200R012C00
S6321-26Q-SI-24S-AC N/A V200R012C00
S6324-EI N/A V100R006,

V200R001C00,
V200R002C00,
V200R003C00,
V200R005C00,
V200R006C00,
V200R007C00
S6330-H24X4Y V200R022C00 N/A
S6330-H24X4Y4C N/A V200R020C00
S6330-H24X6C N/A V200R019C00SPC210
S6330-H28Y4C N/A V200R020C00
S6330-H48X6C N/A V200R019C00SPC210
S6348-EI N/A V100R006,

V200R001C00,
V200R002C00,
V200R003C00,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S6500 N/A VRP3.10 R2039[03]
S6502 N/A V200R005
S6503 N/A V200R005
S6506 N/A V200R005
S6506R N/A V200R005
S652-E N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S652-PWR-E N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S652X-E N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S652X-PWR-E N/A V200R010C00,

V200R011C00,
V200R011C10,
V200R012C00
S6700-24-EI N/A V100R006,

V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00
S6700-48-EI N/A V100R006,

V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00

iMaster NCE-IP
S6720-16X-LI-16S-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720-26Q-LI-24S-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720-26Q-SI-24S-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720-30C-EI-24S-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S6720-30C-EI-24S-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S6720-30L-HI-24S N/A V200R012C00
S6720-32C-PWH-SI N/A V200R011C00,

V200R011C10,
V200R012C00
S6720-32C-PWH-SI-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720-32C-SI-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720-32C-SI-DC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720-32X-LI-32S-AC N/A V200R011C00,

V200R011C10,
V200R012C00

iMaster NCE-IP
S6720-32X-SI-32S-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720-48Q-SI-48S-AC N/A V200R011C10
S6720-50L-HI-48S N/A V200R012C00
S6720-52X-PWH-SI N/A V200R011C10
S6720-52X-PWH-SI-ACF N/A V200R011C10
S6720-54C-EI-48S-AC N/A V200R008C00,

V200R009C00,
V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S6720-54C-EI-48S-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S6720-56C-PWH-SI N/A V200R011C10
S6720S-16X-LI-16S-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720S-26Q-EI-24S-AC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00
S6720S-26Q-EI-24S-DC N/A V200R009C00,

V200R010C00,
V200R011C00,
V200R011C10,
V200R012C00

iMaster NCE-IP
S6720S-26Q-LI-24S-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720S-26Q-SI-24S-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720S-32X-LI-32S-AC N/A V200R011C00,

V200R011C10,
V200R012C00
S6720S-48Q-SI-48S-AC N/A V200R011C10
S6720S-S24S28X-A N/A V200R020C00
S6720S-S52X-A N/A V200R020C00
S6730-H24X4Y4C N/A V200R020C00
S6730-H24X6C N/A V200R019C00SPC210
S6730-H24X6C-K N/A V200R019C10
S6730-H28Y4C N/A V200R020C00
S6730-H28Y4C-K N/A V200R020C00
S6730-H48X6C N/A V200R019C00SPC210
S6730-H48X6C-K N/A V200R019C10
S6730-S24X6Q N/A V200R019C00SPC210
S6730S-H24X4Y4C-A N/A V200R020C00
S6730S-H24X6C-A N/A V200R019C10
S6730S-S24X4Y4Q-A N/A V200R020C00
S6730S-S24X6Q-A N/A V200R019C00SPC210
S6735-S24X6C N/A V200R021C00SPC600
S6735-S48X6C N/A V200R021C00SPC600

iMaster NCE-IP
S7703 N/A V100R003,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R012C00
S7706 N/A V100R003,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R012C00
S7710 N/A V200R010C00
S7712 N/A V100R003,

V100R006,
V200R001,
V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R012C00

iMaster NCE-IP
S7810 N/A Release 6305,

Version 5.20
S8016 N/A V500R003
S8502 N/A VRP310-R1640P01
S8505 N/A S8500-VRP310-

R1632P07,
S8500-VRP310-
R1632P08,
S8500-VRP310-R1648,
V3.10 R1640P01

V100R006B01D028SP03,
VRP V3.10 R1278P07,
VRP V3.10 R1632P07,
Version 3.10

VRP310-R1640P01,
Version 3.10
S8704 V600R023C00 N/A
S9300X-12 N/A V200R019C00SPC210
S9300X-4 N/A V200R019C00SPC210
S9300X-8 N/A V200R019C00SPC210
S9300XS-12 N/A V200R020C00

iMaster NCE-IP
S9303 N/A V100R001,

V100R002,
V100R003,
V100R006,
V200R001C00,
V200R002C00,
V200R003C00,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R008C10,
V200R009C00,
V200R010C00,
V200R012C00
S9303E N/A V200R001C00,

V200R002C00,
V200R003C00,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R008C10,
V200R009C00,
V200R010C00,
V200R012C00

iMaster NCE-IP
S9306 N/A V100R001,

V100R002,
V100R003,
V100R006,
V200R001,
V200R001C00,
V200R002,
V200R002C00,
V200R003,
V200R003C00,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R008C10,
V200R009C00,
V200R010C00,
V200R012C00
S9306E N/A V200R001C00,

V200R002C00,
V200R003C00,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R008C10,
V200R009C00,
V200R010C00,
V200R012C00
S9310 N/A V200R010C00
S9310X N/A V200R010C00

iMaster NCE-IP
S9312 N/A V100R001,

V100R002,
V100R003,
V100R006,
V200R001C00,
V200R002C00,
V200R003C00,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R008C10,
V200R009C00,
V200R010C00,
V200R012C00
S9312E N/A V200R001C00,

V200R002C00,
V200R003C00,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R008C10,
V200R009C00,
V200R010C00,
V200R012C00
S9703 N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R012C00

iMaster NCE-IP
S9706 N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R012C00
S9712 N/A V200R001,

V200R002,
V200R003,
V200R005C00,
V200R006C00,
V200R007C00,
V200R008C00,
V200R009C00,
V200R010C00,
V200R012C00
Table 13-13 CX200D series

CX200D N/A V200R002,

V200R003
CX200D-EA N/A V200R002,

V200R003
CX200D-EA-MC N/A V200R002,

V200R003
CX200D-MC N/A V200R002,

V200R003

iMaster NCE-IP
Table 13-14 CE series

CE12804 V200R022C10 V100R001C00,

V100R002C00,
V100R003C00,
V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE12804E V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE12804S V200R022C10 V100R005C00,

V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE12808 V200R022C10 V100R001C00,

V100R002C00,
V100R003C00,
V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE12808E V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE12808S V200R022C10 V100R005C00,

V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE12812 V200R022C10 V100R001C00,

V100R002C00,
V100R003C00,
V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE12812E V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE12816 V200R022C10 V200R005C20,

V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE12816E V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE12816M V200R022C10 V200R002C01,

V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE16804 V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE16808 V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE16816 V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE5810-24T4S-EI V200R022C10 V100R002C00,

V100R003C00,
V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE5810-48T4S-EI V200R022C10 V100R002C00,

V100R003C00,
V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE5850-48T4S2Q-EI V200R022C10 V100R001C00,

V100R002C00,
V100R003C00,
V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE5850-48T4S2Q-HI V200R022C10 V200R005C20,

V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE5855-24T4S2Q-EI V200R022C10 V100R006C00,

V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE5855-48T4S2Q-EI V200R022C10 V100R006C00,

V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE5855E-48T4S2Q V200R022C10 V200R020C10,

V200R021C00,
V200R021C10,
V200R022C00
CE5855F-48T4S2Q V800R022C10 V200R021C10,

V200R022C00,
V800R022C00

iMaster NCE-IP
CE5880-48T6Q-EI V200R022C10 V200R005C10,

V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE5881-48T6CQ V200R022C10 V200R020C00,

V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE5882-48T4S V200R022C10 V200R022C00
CE6810-24S2Q-LI V200R022C10 V100R006C00,

V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6810-32T16S4Q-LI V200R022C10 V100R006C00,

V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6810-48S-LI V200R022C10 V200R005C20,

V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6810-48S4Q-EI V200R022C10 V100R003C00,

V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6810-48S4Q-LI V200R022C10 V200R005C20,

V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6820-48S6CQ V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6850-48S4Q-EI V200R022C10 V100R001C00,

V100R002C00,
V100R003C00,
V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6850-48S6Q-HI V200R022C10 V100R005C00,

V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6850-48T4Q-EI V200R022C10 V100R001C00,

V100R002C00,
V100R003C00,
V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6850-48T6Q-HI V200R022C10 V100R006C00,

V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6850U-24S2Q-HI V200R022C10 V100R006C00,

V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6850U-48S6Q-HI V200R022C10 V100R005C00,

V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6851-48S6Q-HI V200R022C10 V200R005C20,

V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6855-48S6Q-HI V200R022C10 V200R001C00,

V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6855-48T6Q-HI V200R022C10 V200R001C00,

V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6856-48S6Q-HI V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6856-48T6Q-HI V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6857-48S6CQ-EI V200R022C10 V200R005C10,

V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6857E-48S6CQ V200R022C10 V200R020C10,

V200R021C00,
V200R021C10,
V200R022C00
CE6857E-48T6CQ V200R022C10 V200R020C10,

V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6857F-48S6CQ V800R022C10 V200R021C10,

V200R022C00,
V800R022C00
CE6857F-48T6CQ V800R022C10 V200R021C10,

V200R022C00,
V800R022C00
CE6860-48S18CQ-EI V200R022C10 V200R002C20,

V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6860-48S8CQ-EI V200R022C10 V200R002C01,

V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6863-48S6CQ V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6863-48S6CQ-K V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6863E-48S6CQ V800R022C10 V200R021C10,

V200R022C00,
V800R022C00
CE6865-48S8CQ-EI V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6865-48S8CQ-SI V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6865E-48S8CQ V200R022C10 V200R020C10,

V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6870-24S6CQ-EI V200R022C10 V200R001C00,

V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6870-48S6CQ-EI V200R022C10 V200R001C00,

V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00,
V200R022C00
CE6870-48S6CQ-EI-A V800R022C10 V200R022C00

iMaster NCE-IP
CE6870-48T6CQ-EI V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6875-48S4CQ-EI V200R022C10 V200R005C20,

V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6875-48S4CQ-HI V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6880-24S4Q2CQ-EI V200R022C10 V200R002C10,

V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6880-48S4Q2CQ-EI V200R022C10 V200R002C10,

V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6880-48T4Q2CQ-EI V200R022C10 V200R002C10,

V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE6881-48S6CQ V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6881-48S6CQ-K V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6881-48T6CQ V200R022C10 V200R020C00,

V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6881-48T6CQ-K V200R022C10 V200R020C00,

V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE6881E-48S6CQ V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE7850-32Q-EI V200R022C10 V100R003C00,

V100R005C00,
V100R005C10,
V100R006C00,
V200R001C00,
V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE7855-32Q-EI V200R022C10 V200R001C00,

V200R002C01,
V200R002C10,
V200R002C20,
V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE8850-32CQ-EI V200R022C10 V200R002C20,

V200R005C00,
V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE8850-64CQ-EI V200R022C10 V200R005C00,

V200R005C10,
V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE8850E-32CQ-EI V800R022C10 V200R021C10,

V200R022C00,
V800R022C00
CE8850E-64CQ V200R022C10 V200R021C10,

V200R022C00
CE8860-4C-EI V200R022C10 V200R005C20,

V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00

iMaster NCE-IP
CE8861-4C-EI V200R022C10 V200R005C10,

V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE8868-4C-EI V200R022C10 V200R005C10,

V200R005C20,
V200R019C00,
V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE9860-4C-EI V200R022C10 V200R005C20,

V200R019C10,
V200R020C00,
V200R020C10,
V200R021C00,
V200R021C10,
V200R022C00
CE9860-4C-EI-A V200R022C10 N/A
FM8850E-32CQ-EI V800R022C10 V200R022C00
Table 13-15 FM series

FM12804 V800R022C10 V200R021C10,

V200R022C00,
V800R022C00

iMaster NCE-IP
FM12808 V800R022C10 V200R019C10,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00
FM12816 V800R022C10 V200R021C10,

V200R022C00,
V800R022C00
FM5855E-48T4S2Q V800R022C10 V200R021C00,

V200R021C10,
V200R022C00,
V800R022C00
FM6857-48S6CQ-EI V800R022C10 V200R019C10,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00
FM6857E-48S6CQ V800R022C10 V200R021C00,

V200R021C10,
V200R022C00,
V800R022C00
FM6857E-48T6CQ V800R022C10 V200R021C00,

V200R021C10,
V200R022C00,
V800R022C00
FM6865-48S8CQ-EI V800R022C10 V200R019C10,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00
FM6865-48S8CQ-SI V800R022C10 V200R021C00,

V200R021C10,
V200R022C00,
V800R022C00

iMaster NCE-IP
FM6865E-48S8CQ V800R022C10 V200R021C10,

V200R022C00,
V800R022C00
FM6870-48S6CQ-EI V800R022C10 V200R019C10,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00
FM6870-48T6CQ-EI V800R022C10 V200R019C10,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00
FM8850-32CQ-EI V800R022C10 V200R019C10,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00
FM8850-64CQ-EI V800R022C10 V200R019C10,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00
FM8861-4C-EI V800R022C10 V200R019C10,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00
FM8868-4C-EI V800R022C10 V200R021C10,

V200R022C00,
V800R022C00
FM9860-4C-EI V800R022C10 V200R020C00,

V200R021C00,
V200R021C10,
V200R022C00,
V800R022C00

iMaster NCE-IP
13.6 Security Series

The following table lists the security series NEs supported.
NOTE
NCE is insensitive to the software versions of V500R0XXCXX and V600R0XXCXX security devices.
The V500R0XXCXX and V600R0XXCXX security devices are supported only if the old software
versions of V500R0XXCXX and V600R0XXCXX security devices have been matched.
Table 13-16 Eudemon series
Eudemon 9000E-F4 V800R022C10 V600R021C10,

V600R022C00,
V600R022C00
Eudemon 9000E-F8 V600R022C10 V600R021C10,

V600R022C00
Eudemon1000 N/A V200R006C02
Eudemon1000E-F01 V600R022C10 N/A
Eudemon1000E-F125 V800R022C10 V600R021C10,

V600R022C00

V600R021C00,
V600R021C10,
V600R022C00

V600R022C00

V600R021C00,
V600R021C10,
V600R022C00

V600R021C00,
V600R021C10,
V600R022C00

iMaster NCE-IP

V600R021C00,
V600R021C10,
V600R022C00

V600R022C00
Eudemon1000E-G1-AC N/A V600R007C20
Eudemon1000E-G1-DC N/A V600R007C20
Eudemon1000E-G12-AC N/A V600R006
Eudemon1000E-G12-DC N/A V600R006
Eudemon1000E-G8-AC N/A V600R006,

V600R007C20,
V600R007C20
Eudemon1000E-G8-DC N/A V600R006,

V600R007C20,
V600R007C20
Eudemon1000E-V1 N/A V500R001C10

iMaster NCE-IP
Eudemon100E N/A V200R007C01
Eudemon200 N/A V200R001C01,

V200R001C03
Eudemon200E-B N/A V100R002C00,

V100R005C00,
V300R001C00
Eudemon200E-BW N/A V100R005C00,

V300R001C00
Eudemon200E-C N/A V100R002C00,

V100R005C00,
V300R001C00
Eudemon200E-F N/A V100R002C00,

V100R005C00,
V300R001C00
Eudemon200E-F-D N/A V100R002C00,

V100R005C00,
V300R001C00
Eudemon200E-X2 N/A V100R005C00,

V300R001C00
Eudemon200E-X2NEW N/A V100R005C00,

V300R001C00
Eudemon200E-X2W N/A V100R005C00,

V300R001C00
Eudemon200E-X2WNEW N/A V100R005C00,

V300R001C00

V300R001C00

iMaster NCE-IP

V300R001C00
Eudemon200E-X5DC N/A V100R005C00,

V300R001C00

V300R001C00
Eudemon200E-X6DC N/A V100R005C00,

V300R001C00

V300R001C00
Eudemon200S N/A V200R007C01
Eudemon8000E-V N/A V500R003C00

V200R001C01,
V300R001C00,
V500R001C00,
V500R001C10,
V500R001C20,
V500R001C30,
V500R001C50,
V500R001C80,
V500R002C00,
V500R002C10,
V500R003C00

iMaster NCE-IP

V200R001C01,
V300R001C00,
V500R001C00,
V500R001C10,
V500R001C20,
V500R001C30,
V500R001C50,
V500R001C80,
V500R002C00,
V500R002C10,
V500R003C00,
V500R005C00

V200R001C01,
V300R001C00,
V500R001C00,
V500R001C10,
V500R001C20,
V500R001C30,
V500R001C50,
V500R001C80,
V500R002C00,
V500R002C10,
V500R003C00

V300R001C05,
V300R001C06

V300R001C05,
V300R001C06

iMaster NCE-IP
Eudemon8080E N/A V100R001C01,

V100R001C05,
V100R002C00,
V100R003C00,
V200R001C00,
V200R001C01,
V500R001C00,
V500R003C00
Eudemon8160E N/A V100R001C01,

V100R001C05,
V100R002C00,
V100R003C00,
V200R001C00,
V200R001C01,
V500R001C00
Eudemon9000E-X16 V600R022C10 N/A
Eudemon9000E-X4-AC V600R022C10 V600R019C10,

V600R020C00,
V600R020C10,
V600R021C00,
V600R021C10,
V600R022C00,
V600R022C00
Eudemon9000E-X4-AC- V600R022C10 V600R019C10,

OVS V600R020C00,
V600R020C10,
V600R021C00,
V600R021C10,
V600R022C00,
V600R022C00
Eudemon9000E-X4-DC V600R022C10 V600R019C10,

V600R020C00,
V600R020C10,
V600R021C00,
V600R021C10,
V600R022C00,
V600R022C00

iMaster NCE-IP
Eudemon9000E-X4-DC- V600R022C10 V600R019C10,

OVS V600R020C00,
V600R020C10,
V600R021C00,
V600R021C10,
V600R022C00,
V600R022C00
Eudemon9000E-X8-AC V600R022C10 V600R019C10,

V600R020C00,
V600R020C10,
V600R021C00,
V600R021C10,
V600R022C00,
V600R022C00
Eudemon9000E-X8-AC- V600R022C10 V600R019C10,

OVS V600R020C00,
V600R020C10,
V600R021C00,
V600R021C10,
V600R022C00,
V600R022C00
Eudemon9000E-X8-DC V600R022C10 V600R019C10,

V600R020C00,
V600R020C10,
V600R021C00,
V600R021C10,
V600R022C00,
V600R022C00
Eudemon9000E-X8-DC- V600R022C10 V600R019C10,

OVS V600R020C00,
V600R020C10,
V600R021C00,
V600R021C10,
V600R022C00,
V600R022C00

iMaster NCE-IP
NE40E-FW N/A V500R008C00,

V500R008C01,
V500R008C02,
V500R008C03

V500R008C01,
V500R008C02,
V500R008C03
SeMG9811-X16 N/A V300R001C00,

V300R001C01
SeMG9811-X3 N/A V300R001C00,

V300R001C01
SeMG9811-X8 N/A V300R001C00,

V300R001C01
USG9310 N/A V100R001C01,

V100R001C05,
V100R003C00,
V200R001C00,
V500R001C00
USG9320 N/A V100R001C01,

V100R001C05,
V100R003C00,
V200R001C00,
V500R001C00
USG9520 N/A V200R001C00,

V200R001C01,
V300R001C00,
V500R001C00,
V500R001C10,
V500R001C20,
V500R001C30,
V500R001C50,
V500R001C80,
V500R003C00,
V500R003C10

iMaster NCE-IP
USG9560 N/A V200R001C00,

V200R001C01,
V300R001C00,
V500R001C00,
V500R001C10,
V500R001C20,
V500R001C30,
V500R001C50,
V500R001C80,
V500R003C00,
V500R003C10
USG9580 N/A V200R001C00,

V200R001C01,
V300R001C00,
V500R001C00,
V500R001C10,
V500R001C20,
V500R001C30,
V500R001C50,
V500R001C80,
V500R003C00,
V500R003C10
vRouter6000V1 N/A V500R001C10
Table 13-17 NGFW series

CE-FWA N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R003C00,
V500R003C10

iMaster NCE-IP
CE-IPSA N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R003C00,
V500R003C10
Eudemon1000E-N3 N/A V100R001C20,

V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

V100R001C20,
V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

V100R001C20,
V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

iMaster NCE-IP
Eudemon1000E-N7E N/A V100R001C10,

V100R001C20,
V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
Eudemon200E-N1D N/A V100R001C10,

V100R001C20,
V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

V100R001C20,
V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

iMaster NCE-IP

V100R001C20,
V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
LE1D2FW00S01 N/A V100R001C10,

V100R001C20,
V500R001C00,
V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10,
V500R003C00
NIP6320 N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6320D N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6330 N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6330D N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10

iMaster NCE-IP
NIP6610 N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6620 N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6620D N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6650 N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6650D N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6680 N/A V500R001C00,

V500R001C30,
V500R001C50,
V500R002C00,
V500R002C10
NIP6830 N/A V500R001C50,

V500R003C10
NIP6860-DC N/A V500R001C50,

V500R002C10

iMaster NCE-IP
Table 13-18 USG series

AntiDDoS12004-AC N/A V600R020C00,

V600R020C10
AntiDDoS12004-DC N/A V600R020C00,

V600R020C10
AntiDDoS12004F V800R022C10 V600R021C10,

V600R022C00
AntiDDoS12008-AC N/A V600R020C00,

V600R020C10
AntiDDoS12008-DC N/A V600R020C00,

V600R020C10
AntiDDoS12008F V800R022C10 V600R021C10,

V600R022C00
AntiDDoS12016 V600R022C10 N/A
AntiDDoS1500-D N/A V100R001C00,

V500R001C30,
V500R001C60
AntiDDoS1520 N/A V100R001C00,

V500R001C30,
V500R001C60

V500R001C30,
V500R001C60
AntiDDoS1820-N N/A V600R007C00
AntiDDoS1905 N/A V600R020C10
AntiDDoS1905-K N/A V600R021C10
AntiDDoS1905-N V600R022C10 V600R022C00
AntiDDoS1908 V800R022C10 V600R021C10,

V600R022C00
AntiDDoS1908-K V800R022C10 V600R021C10,

V600R022C00

iMaster NCE-IP

V500R001C00,
V500R001C30,
V500R001C60

V500R001C00,
V500R001C30,
V500R001C60

V500R001C00,
V500R001C30,
V500R001C60
AntiDDos1820 N/A V600R006
AntiDDos1825 N/A V600R007C00
AntiDDos1880 N/A V600R006
Eudemon1000E-D N/A V100R005C00
Eudemon1000E-I N/A V100R005C00
Eudemon1000E-U2 N/A V100R002C01,

V100R003C01,
V100R005C00,
V200R001C00

V100R003C01,
V100R005C00,
V200R001C00

V100R003C01,
V100R005C00,
V200R001C00

V100R003C01,
V100R005C00,
V200R001C00
Eudemon1000E-X2 N/A V300R001C00
Eudemon1000E-X2-D N/A V300R001C00

iMaster NCE-IP

V200R002C00,
V300R001C00

V200R002C00,
V300R001C00

V200R002C00,
V300R001C00

V300R001C00
Eudemon200E-X1AGW-C N/A V100R005C00,

V300R001C00
Eudemon200E-X1AGW- N/A V100R005C00,

W V300R001C00
Eudemon200E-X1W N/A V100R005C00,

V300R001C00
Eudemon6080E N/A V100R001C00
SRG20-10 N/A V100R001C03
USG12004-AC V600R022C10 V600R020C00,

V600R020C10,
V600R021C10,
V600R022C00
USG12004-AC-OVS V600R022C10 V600R020C00,

V600R020C10,
V600R021C10,
V600R022C00
USG12004-DC V600R022C10 V600R020C10,

V600R021C10,
V600R022C00

iMaster NCE-IP
USG12004-DC-OVS V600R022C10 V600R020C10,

V600R021C10,
V600R022C00
USG12004F V800R022C10 V600R021C10,

V600R022C00,
V600R022C00
USG12008-AC V600R022C10 V600R020C10,

V600R021C10,
V600R022C00
USG12008-AC-OVS V600R022C10 V600R020C10,

V600R021C10,
V600R022C00
USG12008-DC V600R022C10 V600R020C10,

V600R021C10,
V600R022C00
USG12008-DC-OVS V600R022C10 V600R020C10,

V600R021C10,
V600R022C00
USG12008F V800R022C10 V600R021C10,

V600R022C00,
V600R022C00
USG2110 N/A V100R001C03
USG2110-A-GW-C N/A V100R005C00,

V300R001C00
USG2110-A-GW-W N/A V100R005C00,

V300R001C00
USG2110-A-W N/A V100R005C00,

V300R001C00
USG2110-F N/A V100R005C00
USG2110-F-W N/A V100R005C00
USG2120BSR N/A V100R003C01
USG2130 N/A V100R003C01,

V300R001C00

iMaster NCE-IP
USG2130BSR-W N/A V100R003C01
USG2130W N/A V100R003C01
USG2160 N/A V100R003C01
USG2160BSR-W N/A V100R003C01
USG2160W N/A V100R003C01
USG2205HSR N/A V100R003C01,

V100R005C00,
V300R001C00
USG2210 N/A V100R003C01,

V100R005C00,
V300R001C00
USG2220 N/A V100R002C01,

V100R003C01,
V100R005C00,
V300R001C00
USG2220BSR-D N/A V300R001C00

V100R005C00,
V300R001C00
USG2220HSR-D N/A V100R003C01,

V100R005C00,
V300R001C00
USG2220TSM N/A V100R003C01
USG2230 N/A V100R003C01,

V100R005C00,
V300R001C00
USG2250 N/A V100R002C01,

V100R003C01,
V100R005C00,
V300R001C00

iMaster NCE-IP
USG2250-D N/A V100R002C01,

V100R003C01,
V100R005C00,
V300R001C00
USG2250TSM N/A V100R003C01
USG2260 N/A V300R001C00
USG3030 N/A V100R001C03
USG3040 N/A V100R001C03
USG50 N/A V100R001C03
USG5120 N/A V100R003C01,

V100R005C00,
V300R001C00
USG5120-D N/A V100R003C01,

V100R005C00,
V300R001C00
USG5120BSR N/A V100R003C01,

V100R005C00,
V300R001C00
USG5120BSR-D N/A V100R003C01

V300R001C00
USG5150 N/A V100R003C01,

V100R005C00,
V300R001C00
USG5150BSR N/A V100R003C01,

V100R005C00,
V300R001C00

V300R001C00
USG5160 N/A V100R005C00,

V300R001C00
USG5300ADD N/A V100R001C00
USG5300ADI N/A V100R001C00

iMaster NCE-IP
USG5310 N/A V100R002C01,

V100R003C01,
V100R005C00,
V200R001C00
USG5320 N/A V100R002C01,

V100R003C01,
V100R005C00,
V200R001C00
USG5330 N/A V100R002C01,

V100R003C01,
V100R005C00,
V200R001C00
USG5350 N/A V100R002C01,

V100R003C01,
V100R005C00,
V200R001C00
USG5360 N/A V100R002C01,

V100R003C01,
V100R005C00,
V200R001C00
USG5520S N/A V300R001C00
USG5530 N/A V200R001C00,

V200R002C00,
V300R001C00
USG5530S N/A V200R001C00,

V200R002C00,
V300R001C00
USG5550 N/A V200R001C00,

V200R002C00,
V300R001C00
USG5560 N/A V200R001C00,

V200R002C00,
V300R001C00
USG6302F-C V600R022C10 N/A
USG6305E-AC N/A V600R007C00

iMaster NCE-IP
USG6305F-C V600R022C10 N/A
USG6306F V600R022C10 N/A
USG6307F-D V600R022C10 N/A
USG6308F V600R022C10 N/A
USG6311F-D V600R022C10 N/A
USG6315F V600R022C10 N/A
USG6325F V600R022C10 N/A
USG6331F-D V600R022C10 N/A
USG6335F V600R022C10 N/A
USG6355F V600R022C10 N/A
USG6365F V600R022C10 N/A
USG6385F V600R022C10 N/A
USG6502F-C V600R022C10 N/A
USG6505F-C V600R022C10 N/A
USG6510F-D V600R022C10 N/A
USG6510F-DK V600R022C10 N/A
USG6510F-DL V600R022C10 N/A

iMaster NCE-IP
USG6515E N/A V600R006
USG6520F-K V600R022C10 N/A
USG6525F V600R022C10 N/A
USG6530F-D V600R022C10 N/A
USG6530F-DL V600R022C10 N/A
USG6550E N/A V600R006
USG6555F V600R022C10 N/A
USG6560E N/A V600R006
USG6560F-K V600R022C10 N/A
USG6565F V600R022C10 N/A
USG6580E N/A V600R006
USG6585F V600R022C10 N/A
USG6590F-K V600R022C10 N/A
USG6606F-C V600R022C10 N/A
USG6630E-AC N/A V600R006
USG6630E-DC N/A V600R006
USG6635E-DC N/A V600R007C00
USG6650E N/A V600R006
USG6680 N/A V100R001

iMaster NCE-IP
USG6680E N/A V600R006
USG6715F V600R022C10 N/A
USG9000V N/A V500R003C00
USG9110 N/A V100R001C00
USG9120 N/A V100R001C00
Table 13-19 SRG series
SRG1210 SRG1210W N/A V1R2C02,

SRG1210-S SRG1220 V1R2C01,
SRG1220W
V1R1C01
SRG20-11 SRG20-12 N/A V1R5C00,

SRG20-12W SRG20-15 V1R3C01,
SRG20-15W
V1R2C01
SRG20-20 SRG20-21 N/A V2R2C01,

SRG20-30 SRG20-31 V1R5C00
SRG20-31-D N/A V2R2C01,

V1R5C00
SRG2210 SRG2220 N/A V1R1C01

SRG2220-D
SRG2210SRG2220SRG22 N/A V1R2C02,

20- V1R2C01SPC200
D2U:SRG3230SRG3240SR
G3240-
D3U:SRG3250SRG3260
Table 13-20 ASG series
ASG2100 N/A V100R001C00
ASG2200 N/A V100R001C00
ASG2600 N/A V100R001C00
ASG2800 N/A V100R001C00

iMaster NCE-IP
Table 13-21 EGW series

EGW2112GW N/A V100R001C02,

V100R001C20
EGW2130 N/A V100R001C02,

V100R001C20
EGW2130W N/A V100R001C02,

V100R001C20
EGW2160 N/A V100R001C02,

V100R001C20
EGW2160DC N/A V100R001C20
EGW2160W N/A V100R001C02,

V100R001C20
EGW2210 N/A V100R001C02,

V100R001C20
EGW2220 N/A V100R001C20
EGW3230 N/A V100R001C02,

V100R001C20
EGW3240 N/A V100R001C20
EGW3250 N/A V100R001C02,

V100R001C20
EGW3260 N/A V100R001C02,

V100R001C20
Table 13-22 SIG series

DPI Server N/A V500R009C00,

V500R009C01,
V500R009C02
NE40E-DPI N/A V500R009C00,

V500R009C01,
V500R009C02

iMaster NCE-IP
NE80E-DPI N/A V500R009C00,

V500R009C01,
V500R009C02
RADIUS Proxy N/A V200R002C02,

V200R003C00,
V300R001C00,
V300R003C00,
V300R005C00,
V300R006C00,
V300R006C10,
V300R006C20,
V300R007C00,
V300R007C10,
V300R008C10,
V300R009C00
RADIUS Proxy-DPI N/A V500R009C02
SIG Server N/A V200R002C01,

V200R002C02,
V200R003C00,
V300R001C00,
V300R003C00,
V300R005C00,
V300R006C00,
V300R006C10,
V300R006C20,
V300R007C00,
V300R007C10,
V300R008C10,
V300R009C00
SIG9800-X16 N/A V300R001C00,

V300R005C00,
V300R006C00,
V300R006C20,
V300R007C10,
V300R008C10,
V300R009C00

iMaster NCE-IP
SIG9800-X16A V800R022C10 V600R022C00,

V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
SIG9800-X3 N/A V300R001C00,

V300R005C00,
V300R006C00,
V300R006C10,
V300R006C20,
V300R007C10,
V300R008C10,
V300R009C00
SIG9800-X8 N/A V300R001C00,

V300R005C00,
V300R006C00,
V300R006C20,
V300R007C00,
V300R009C00
SIG9800-X8A V800R022C10 V600R022C00,

V800R013C00,
V800R021C00,
V800R021C10,
V800R022C00
SIG9810 N/A V200R002C02,

V200R003C00,
V300R001C00,
V300R006C10,
V300R007C00
SIG9820 N/A V200R002C02,

V200R003C00,
V300R001C00,
V300R006C10,
V300R007C00
SRG1210 N/A V100R002C01
SRG1210-S N/A V100R001C01

iMaster NCE-IP
SRG1210W N/A V100R002C02
SRG1220W N/A V100R002C01
SRG20-11 N/A V100R002C01,

V100R003C01
SRG20-12 N/A V100R002C01,

V100R003C01
SRG20-12W N/A V100R002C01,

V100R003C01
SRG20-15 N/A V100R002C01,

V100R003C01,
V100R005C00
SRG20-15W N/A V100R002C01,

V100R003C01
SRG20-20 N/A V100R005C00,

V200R002C01
SRG20-21 N/A V100R005C00,

V200R002C01
SRG20-30 N/A V100R005C00,

V200R002C01
SRG20-31 N/A V100R005C00,

V200R002C01
SRG20-31-D N/A V100R005C00,

V200R002C01
SRG2210 N/A V100R001C01,

V100R002C01SPC200,
V100R002C02
SRG2220 N/A V100R001C01,

V100R002C01SPC200,
V100R002C02
SRG2220-D N/A V100R001C01,

V100R002C01SPC200,
V100R002C02
SRG3230 N/A V100R002C01SPC200,

V100R002C02

iMaster NCE-IP
SRG3240 N/A V100R002C01SPC200,

V100R002C02
SRG3240-D N/A V100R002C01SPC200,

V100R002C02
SRG3250 N/A V100R002C01SPC200,

V100R002C02
SRG3260 N/A V100R002C01SPC200,

V100R002C02
URL Classify Server N/A V100R002C01,

V300R001C00,
V300R005C00,
V300R007C10,
V300R008C10,
V300R009C00
Table 13-23 NE40E/80E-FW series


V500R008C02,
V500R008C01,
V500R008C00

V500R008C02,
V500R008C01,
V500R008C00
Table 13-24 OP-Bypass series

OP-Bypass N/A V100R001C00

iMaster NCE-IP
Table 13-25 SVN series

SVN2230 N/A V200R001C00,

V200R001C01
SVN2260 N/A V200R001C00,

V200R001C01
SVN3000 N/A V100R002C02
SVN5300 N/A V200R001C00
SVN5530 N/A V200R001C00,

V200R001C01
SVN5560 N/A V200R001C00,

V200R001C01
SVN5630 N/A V200R003C00
SVN5660 N/A V200R003C00
SVN5830 N/A V200R003C00
SVN5850 N/A V200R003C00
SVN5860 N/A V200R003C00
SVN5880 N/A V200R003C00
SVN5880-C N/A V200R003C00
Table 13-26 NIP series

IPS12004-AC N/A V600R020C00,

V600R020C10
IPS12004-DC N/A V600R020C00,

V600R020C10
IPS12004F V800R022C10 V600R021C10,

V600R022C00
IPS12008-AC N/A V600R020C00,

V600R020C10
IPS12008-DC N/A V600R020C00,

V600R020C10

iMaster NCE-IP
IPS12008F V800R022C10 V600R021C10,

V600R022C00
IPS6309E-AC N/A V600R007C00
IPS6309F V600R022C10 N/A
IPS6315F V600R022C10 N/A
IPS6515E-B-AC N/A V600R007C20
IPS6520F-K V600R022C10 N/A
IPS6525F V600R022C10 N/A
IPS6525FD V600R022C10 N/A
IPS6555E-DC N/A V600R007C20
IPS6555ED-AC N/A V600R007C00
IPS6585F N/A V600R020C10
IPS6610E-K N/A V600R007C20
IPS6615F N/A V600R020C10
IPS6620F-K V800R022C10 V600R021C10,

V600R022C00
IPS6625F N/A V600R020C10
IPS6655F V800R022C10 V600R021C10,

V600R022C00
NIP6305E N/A V600R006
NIP6310E N/A V600R006
NIP6510E N/A V600R006
NIP6550E N/A V600R006

iMaster NCE-IP
NIP6610E N/A V600R006
NIP6620E N/A V600R006
NIP6620E-DC N/A V600R006
NIP6650ED-AC N/A V600R006
Table 13-27 CE series

CE-FWA N/A V500R003C00
Table 13-28 SeMG9811 series

SeMG9811-X16 N/A V500R001C50
SeMG9811-X3 N/A V500R001C50
SeMG9811-X8 N/A V500R001C50
13.7 iCache Series

The following table lists the iCache series NEs supported.
Table 13-29 iCache series

iCache9200 CSS N/A V200R001C00
iCache9200 CSS N/A V100R002C00
iCache9200 DSS N/A V200R001C00,

V100R002C00
iCache9200 MSS N/A V200R001C00
iCache9200 MSS N/A V100R002C00
iCache9200 RSS N/A V200R001C00,

V100R002C00

iMaster NCE-IP
Product Description (x86,enterprise) A Standards Compliance
A Standards Compliance
NCE complies with ITU-T, IETF, and TM Forum recommendations, protocols, and
standards.
Table A-1 Standards compliance

Standard/ Description
Protocol
CIS Center for Internet Security Benchmarks
Sif99025 EML-NML interface models
TMF513 V2.0 Multi-Technology Network Management Business Agreement

NML-EML Interface Version 2.0
TMF518 MTOSI Business Agreement
TMF608 V2.0 Multi-Technology Network Management Information

Agreement NML-EML Interface Version 2.0
TMF612 MTOSI Information Agreement
TMF814 V2.0 Multi Technology Network Management Solution Set

Conformance Document Version 2.0
TMF814A MTNM Implementation Statement and Guidelines for MTNM

Release 3.5M
TMF864 MTOSI Interface Implementation Specifications
ISO Information Technology - Abstract Syntax Notation One (ASN.

8824-4-2000 1): Parameterization of ASN.1 Specifications Amendment 1:
ASN.1 semantic model
ISO Information Technology - ASN.1 Encoding Rules: Specification

8825-2-1998 of Packed Encoding Rules (PER) Second Edition; Technical
Corrigendum 1: 12/15/1999; Amendment 1: 12/01/2000
ITU-T G.707 Network node interface for the synchronous digital hierarchy
(SDH)

iMaster NCE-IP
Protocol
ITU-T G.7710 Common equipment management function requirements
ITU-T G.773 Protocol suites for Q-interfaces for management of

transmission systems
ITU-T G.774 Synchronous digital hierarchy (SDH) - Management

(01, 02, 03, information model for the network element view
04)
ITU-T G.783 Characteristics of synchronous digital hierarchy (SDH)

equipment functional blocks
ITU-T G.784 Synchronous digital hierarchy (SDH) management
ITU-T G.803 Architecture of transport networks based on the synchronous

digital hierarchy (SDH)
ITU-T G.831 Management capabilities of transport networks based on the

synchronous digital hierarchy (SDH)
ITU-T G.851.1 Management of the transport network - Application of the RM-

ODP framework
ITU-T G.852.1 Enterprise viewpoint for simple subnetwork connection

management
ITU-T G.852.2 Enterprise viewpoint description of transport network resource

model
ITU-T G.852.3 Enterprise viewpoint for topology management
ITU-T G.852.6 Enterprise viewpoint for trail management
ITU-T G.853.1 Common elements of the information viewpoint for the

management of a transport network
ITU-T G.853.2 Subnetwork connection management information viewpoint
ITU-T G.853.3 Information viewpoint for topology management
ITU-T G.853.6 Information viewpoint for trail management
ITU-T G.854.1 Computational interfaces for basic transport network model
ITU-T G.854.3 Computational viewpoint for topology management
ITU-T G.854.6 Computational viewpoint for trail management
ITU-T M.3000 Overview of TMN recommendations
ITU-T M.3010 Principles for a telecommunications management network
ITU-T M.3013 Considerations for a telecommunications management network
ITU-T M.3017 Framework for the integrated management of hybrid circuit/

packet networks

iMaster NCE-IP
Protocol
ITU-T M.3020 TMN interface specification methodology
ITU-T M.3100 Generic network information model
ITU-T M.3101 Managed Object Conformance statements for the generic

network information model
ITU-T M.3180 Catalogue of TMN management information
ITU-T M.3200 TMN management services and telecommunications managed

areas: overview
ITU-T M.3300 TMN F interface requirements
ITU-T M.3400 TMN management functions
ITU-T X.720 Management information model
ITU-T X.721 Definition of management information
ITU-T X.722 Guidelines for the definition of managed objects
ITU-T X.733 Information technology - Open Systems Interconnection -

Systems Management: alarm reporting function
ITU-T X.735 Information technology - Open Systems Interconnection -

Systems Management: log control function
ITU-T X.903 Information technology - Open distributed processing -

Reference Model: architecture
ITU-T Y.1701 Common equipment management function requirements
M.3016.0 Security for the management plane: Overview
M.3016.1 Security for the management plane: Security requirements
M.3016.2 Security for the management plane: Security services
M.3016.3 Security for the management plane: Security mechanism
M.3016.4 Security for the management plane: Profile proforma
M.3703 Common management services - Alarm management - Protocol

neutral requirements and analysis
MEF 15 Requirements for Management of Metro Ethernet Phase 1

Network Elements
Rational Rational Unified Process

Unified
Process 5.5
RFC793 Transmission Control Protocol (Darpa Internet Program Protocol

Specification)

iMaster NCE-IP
Protocol
RFC1155 Structure and Identification of Management Information for

TCP/IP-based Internets
RFC1212 Concise MIB Definitions
RFC1213 Management Information Base for Network Management of

TCP/IP-based internets: MIB-II
RFC1215 A Convention for Defining Traps for use with the SNMP
RFC1905 Protocol Operations for Version 2 of the Simple Network

Management Protocol
RFC1906 Transport Mappings for Version 2 of the Simple Network

Management Protocol
RFC1907 Management Information Base for Version 2 of the Simple

Network Management Protocol
RFC1908 Coexistence between Version 1 and Version 2 of the Internet-

standard Network Management Framework
RFC2011 SNMPv2 Management Information Base for the Internet

Protocol using SMIv2
RFC2012 SNMPv2 Management Information Base for the Transmission

Control Protocol using SMIv2
RFC2013 SNMPv2 Management Information Base for the User Datagram

Protocol using SMIv2
RFC2396 Uniform Resource Identifiers(URL)
RFC2544 Benchmarking Methodology for Network Interconnect Devices
RFC2571 An Architecture for Describing SNMP Management Frameworks
RFC2572 Message Processing and Dispatching for the Simple Network

Management Protocol
RFC2573 SNMP Applications
RFC2574 User-based Security Model (USM) for version 3 of the Simple

Network Management Protocol
RFC2576 Coexistence between Version 1, Version 2, and Version 3 of the

Internet-standard Network Management Framework
RFC2578 Structure of Management Information Version 2 (SMIv2)
RFC2579 Textual Conventions for SMIv2
RFC2580 Conformance Statements for SMIv2
RFC2616 Hypertext Transfer Protocol -- HTTP/1.1

iMaster NCE-IP
Protocol
RFC2617 HTTP- Authentication: Basic and Digest Access Authentication
RFC2818 HTTP Over TLS (HTTPS)
RFC2890 Key and Sequence Number Extensions to GRE
RFC3164 The BSD syslog Protocol
RFC3411 An Architecture for Describing Simple Network Management

Protocol (SNMP) Management Frameworks
RFC3412 Message Processing and Dispatching for the Simple Network

Management Protocol (SNMP)
RFC3413 Simple Network Management Protocol (SNMP) Applications
RFC3414 User-based Security Model (USM) for version 3 of the Simple

Network Management Protocol (SNMPv3)
RFC3415 View-based Access Control Model (VACM) for the Simple

Network Management Protocol (SNMP)
RFC3416 Version 2 of the Protocol Operations for the Simple Network

RFC3417 Transport Mappings for the Simple Network Management

Protocol (SNMP)
RFC3418 Management Information Base (MIB) for the Simple Network

RFC4271 A Border Gateway Protocol 4 (BGP-4)
RFC4346 Transport Layer Security(TLS) Protocol Version 1.1
RFC6241 Network Configuration Protocol (NETCONF)
RFC8040 RESTCONF Protocol
OpenStack.G The Group-based Policy (GBP) abstractions for OpenStack

BP provide an intent-driven declarative policy model that presents
simplified application-oriented interfaces to the user.
RFC7951 JSON Encoding of Data Modeled with YANG
RFC7936 Clarifying Registry Procedures for the WebSocket Subprotocol

Name Registry
RFC6455 The WebSocket Protocol
RFC8259 The JavaScript Object Notation (JSON) Data Interchange

Format

iMaster NCE-IP
Protocol
RFC6020 YANG - A Data Modeling Language for the Network

Configuration Protocol (NETCONF)
W3C.REC- Server-Sent Events, a server push technology enabling a

eventsource-2 browser to receive automatic updates from a server via HTTP
0150203 connection.
RFC8340 YANG Tree Diagrams
RFC8199 YANG Module Classification
RFC8071 NETCONF Call Home and RESTCONF Call Home
RFC7950 The YANG 1.1 Data Modeling Language
RFC5277 NETCONF Event Notifications
RFC4880 OpenPGP is the most widely used email encryption standard. It

is defined by the OpenPGP Working Group of the Internet
Engineering Task Force (IETF) as a Proposed Standard in RFC
4880. OpenPGP was originally derived from the PGP software,
created by Phil Zimmermann.
RFC7047 OVSDB Management Protocol
RFC3173 IP Payload Compression Protocol (IPComp)
RFC4627 JavaScript Object Notation (JSON)
RFC2460 Internet Protocol, Version 6 (IPv6)
RFC5988 Internet Engineering Task Force (IETF)
draft-ietf- sftp draft

secsh-
filexfer-13
RFC4253 The Secure Shell (SSH) Transport Layer Protocol
RFC1157 A Simple Network Management Protocol (SNMP)
RFC1902 Structure of Management Information for Version 2 of the

Simple Network Management Protocol (SNMPv2)
RFC2575 View-based Access Control Model (VACM) for the Simple

Network Management Protocol (SNMP)
draft-ietf- This document defines a YANG [RFC7950] module for alarm

ccamp-alarm- management.
module-01
SSE Server-Sent Events
RFC8231 Path Computation Element Communication Protocol (PCEP)

Extensions for Stateful PCE

iMaster NCE-IP
Protocol
draft-ietf-idr- BGP Link State Extensions for SRv6

bgpls-srv6-
ext-03
draft-ietf-idr- Flexible Algorithm Definition Advertisement with BGP Link-

bgp-ls-flex- State
algo-04
draft-ietf- Segment Routing Policy Architecture

spring-
segment-
routing-
policy-08
RFC8956 It specifies new Border Gateway Protocol [RFC4271] encoding

formats to enable "Dissemination of Flow Specification Rules"
[RFC8955] for IPv6.
draft-ietf-idr- Advertising Segment Routing Policies in BGP

segment-
routing-te-
policy-12
draft-ietf-idr- Distribution of Traffic Engineering (TE) Policies and State using

te-lsp- BGP-LS
distribution-1
2
draft-ietf-idr- BGP Link-State extensions for Segment Routing

bgp-ls-
segment-
routing-
ext-16
RFC8571 BGP-LS Advertisement of IGP Traffic Engineering Performance

Metric Extensions
RFC4655 A Path Computation Element (PCE) Based Architecture
RFC4657 Path Computation Element (PCE) Communication Protocol

Generic Requirements
RFC5440 Path Computation Element (PCE) Communication Protocol

(PCEP)
RFC5521 Extensions to the Path Computation Element Communication

Protocol (PCEP) for Route Exclusions
RFC7752 North-Bound Distribution of Link-State and Traffic Engineering

(TE) Information Using BGP

iMaster NCE-IP
Protocol
draft-ietf-idr- BGP Link-State extensions for Segment Routing

bgp-ls-
segment-
routing-
ext-16
RFC4724 Graceful Restart Mechanism for BGP
RFC8232 Optimizations of Label Switched Path State Synchronization

Procedures for a Stateful PCE
RFC8408 Conveying Path Setup Type in PCE Communication Protocol

(PCEP) Messages
RFC8051 Applicability of a Stateful Path Computation Element (PCE)
RFC7470 Conveying Vendor-Specific Constraints in the Path Computation

Element Communication Protocol
RFC7896 Update to the Include Route Object (IRO) Specification in the

Path Computation Element Communication Protocol (PCEP)
RFC8402 Segment Routing Architecture
RFC8664 PCEP Extensions for Segment Routing
draft-minei- PCEP Extensions for Establishing Relationships Between Sets of

pce- LSPs
association-
group-00
draft- Carrying Binding Label/Segment-ID in PCE-based Networks

sivabalan-
pce-binding-
label-sid-06
draft-li-idr- BGP Extensions for Routing Policy Distribution (RPD)

flowspec-
rpd-04
RFC5575 Dissemination of Flow Specification Rules
draft- PCEP Extensions for Associating Working and Protection LSPs

ananthakrish with Stateful PCE
nan-pce-
stateful-path-
protection-01

iMaster NCE-IP
Protocol
draft-ieft- This draft defines procedures and messages for SRv6-based BGP
bess-srv6- services including L3VPN, EVPN and Internet services. It builds
services-06 on
RFC4364 BGP/MPLS IP Virtual Private Networks (VPNs)" and
RFC7432
"BGP MPLS-Based Ethernet VPN".
RFC 8697 Path Computation Element Communication Protocol (PCEP)

Extensions for Establishing Relationships between Sets of Label
Switched Paths (LSPs)
RFC 8745 Path Computation Element Communication Protocol (PCEP)

Extensions for Associating Working and Protection Label
Switched Paths (LSPs) with Stateful PCE
draft-ieft- This draft defines procedures and messages for SRv6-based BGP
bess-srv6- services including L3VPN, EVPN and Internet services. It builds
services-08 on
RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and
RFC7432
"BGP MPLS-Based Ethernet VPN".
draft-ietf- Compressed SRv6 Segment List Encoding in SRH

spring-srv6-
srh-
compression-
02
draft-filsfils- Network Programming extension: SRv6 uSID instruction

spring-net-
pgm-
extension-
srv6-usid-12

iMaster NCE-IP
Product Description (x86,enterprise) B Glossary and Abbreviations
B Glossary and Abbreviations
Numerics
3G See Third Generation (3G)
4K See 4K resolution (4K)
4K resolution 4K is a digital video format defined by the International
(4K) Telecommunication Union (ITU). It is a new standard that
originated from digital movies produced by Hollywood movie
makers. 4K has become the common name for ultra high
definition or ultra HD, and its resolutions include 3840 x 2160
and 4096 x 2160. Compared with 1080p full HD content, 4K
content provides more refined details and greater texture,
bringing subscribers a better cinematic experience.
802.1Q in A VLAN feature that allows the equipment to add a VLAN
802.1Q (QinQ) tag to a tagged frame. The implementation of QinQ is to add
a public VLAN tag to a frame with a private VLAN tag to
allow the frame with double VLAN tags to be transmitted
over the service provider's backbone network based on the
public VLAN tag. This provides a layer 2 VPN tunnel for
customers and enables transparent transmission of packets
over private VLANs.
A
AAA See Authentication, Authorization and Accounting (AAA).
AB path A forwarding path simulated from node A to node B.
ACL See Access Control List (ACL)
ACTN Abstraction and Control of Traffic Engineered Networks
(ACTN) refers to the set of virtual network operations
needed to coordinate, control, and manage large-scale multi-
domain TE networks. ACTN helps to facilitate network
programmability, automation, efficient resource sharing, and
end-to-end virtual service-aware connectivity, and provides
network function virtualization services.

iMaster NCE-IP
ADMC automatically detected and manually cleared

ADSL See asymmetric digital subscriber line (ADSL)
ADSL2+ asymmetric digital subscriber line 2 plus
ALS Access license server
ANCP See Access Node Control Protocol (ANCP)
API See application programming interface (API)
APN Application-aware networking (APN) technology utilizes the
programmable space of IPv6 packets to transmit application-
side information and requirements to the network side. Then
service deployment and resource adjustment will be
performed accordingly to meet the SLA requirements of
applications.
APS automatic protection switching
AS See autonomous system (AS)
ASBR See autonomous system boundary router (ASBR)
ASG Aggregation Site Gateway. A role name on the mobile bearer
network. The role is located at the aggregation layer and is
responsible for aggregating Cell Site Gateway (CSG) service
flows at the access layer of the mobile bearer network.
ASM A multicast service mode. In ASM mode, any sender can
become the multicast source to send information to a
multicast group address. After joining the multicast group
identified by this address, multiple receivers can receive all
the information sent to this multicast group.
ASN.1 See Abstract Syntax Notation One (ASN.1)
ASON automatically switched optical network
ATM Rec. ITU-R F. 1499 - A protocol for the transmission of a
variety of digital signals using uniform 53 byte cells. Rec.
ITU-R M. 1224 - A transfer mode in which the information is
organized into cells; it is asynchronous in the sense that the
recurrence of cells depends on the required or instantaneous
bit rate. Statistical and deterministic values may also be used
to qualify the transfer mode.
ATN aeronautical telecommunications network
Abstract Syntax A syntax notation type employed to specify protocols. Many
Notation One protocols defined by the ITU-T use this syntax format. Other
(ASN.1) alternatives are standard text or Augmented Backus-Naur
Form (ABNF).
Access Control A list of entities, together with their access rights, which are
List (ACL) authorized to access a resource.

iMaster NCE-IP
Access Node An IP-based protocol that operates between the access node
Control (AN) and the network access server (NAS), over a DSL access
Protocol and aggregation network.
(ANCP)
Agile Controller The Agile Controller is the core component of a next-
generation network solution designed by Huawei for
enterprise markets. It can be deployed on agile campus
networks, agile branches, agile wired area networks (WANs),
and agile data centers to control policies for accessing to
these networks as well as interconnection between data
centers. Following the centralized control principle of
software defined networking (SDN), the Agile Controller
dynamically schedules network and security resources on the
entire network to allow these resources to migrate with
users.
acknowledged Alarms that are already handled. With the alarms
alarms acknowledged, you can identify the alarms that are not
handled so that you can handle these alarms in time.
active/standby A troubleshooting technology. When an active device
switchover becomes faulty, services and control functions are
automatically switched over to the standby device to ensure
the normal running of the services and functions.
administrator A user who has authority to access all EMLCore product
management domains. This user has access to the entire
network and all management functions.
administrator A combination of rights to access various elements on pages
role of the PortalONE management system. Different
administrator roles have different access rights.
alarm A message reported when a fault is detected by a device or
by the network system during the device polling process.
Each alarm corresponds to a clear alarm. After a clear alarm
is received, the corresponding alarm is cleared.
alarm ID The one and only alarm identifier consisting of four bytes.
Each alarm has an ID. Generally, allocate the alarm ID
according to the alarm category and alarm module.
alarm An operation performed on an alarm. Through this operation,
acknowledgme the status of an alarm is changed from unacknowledged to
nt acknowledged, which indicates that the user starts handling
the alarm. When an alarm is generated, the operator needs
to acknowledge the alarm and take the right step to clear
the alarm.
alarm severity The significance of a change in system performance or
events. According to ITU-T recommendations, an alarm can
have one of the following severities: Critical, Major, Minor,
Warning.

iMaster NCE-IP
alarm source A device that generates an alarm. To automatically report

alarms, the ECC system can receive alarms from multiple
alarm sources such as smoke detectors and alarming hosts.
alarm status Alarm states are defined based on alarm acknowledgement
and clearance. Alarms have four states based on alarm
acknowledgement and clearance, including unacknowledged
and uncleared, acknowledged and uncleared,
unacknowledged and cleared, acknowledged and cleared.
alarm When alarm synchronization is implemented, the EMS checks
synchronization the alarm information in its database and on the NEs. If the
alarm information on the two locations is inconsistent, the
alarm information on the NEs is synchronized to the EMS
database to replace the original records.
application A network plane on which cloud services, such as IAM and
plane CSB, run.
application An application programming interface is a particular set of
programming rules and specifications that are used for communication
interface (API) between software programs.
asymmetric A technology for transmitting digital information at a high
digital bandwidth on existing phone lines to homes and businesses.
subscriber line Unlike regular dialup phone service, ADSL provides
(ADSL) continuously-available, "always on" connection. ADSL is
asymmetric in that it uses most of the channel to transmit
downstream to the user and only a small part to receive
information from the user. ADSL simultaneously
accommodates analog (voice) information on the same line.
ADSL is generally offered at downstream data rates from 512
kbit/s to about 6 Mbit/s.
Authentication, A security architecture for distributed systems. Enables
Authorization control over which users are allowed access to which services
and Accounting and how much resources they can use.
(AAA)
autonomous A network set that uses the same routing policy and is
system (AS) managed by the same technology administration
department. Each AS has a unique identifier that is an
integer ranging from 1 to 65535. The identifier is assigned by
IANA. An AS can be divided into areas.
autonomous A router that exchanges routing information with other
system autonomous system boundary routers.
boundary
router (ASBR)
B
B/S Browser/Server
BC bandwidth calendar

iMaster NCE-IP
BER See basic encoding rule (BER)

BFD See Bidirectional Forwarding Detection (BFD)
BGP Border Gateway Protocol
BGP peer BGP peers are established between NCE and the forwarding
network.
BGP-EPE The BGP egress peer engineering (BGP-EPE) link list displays
information about cross-domain BGP-EPE links. BGP-EPE
allocates BGP peer SIDs to service paths, and these SIDs are
reported to controllers through a BGP-LS extension to
facilitate service path computation by the controllers.
BIOS See basic input/output system (BIOS)
Bit Error Rate The BER is measured by counting the number of bits in error
at the output of a receiver and dividing by the total number
of bits in the transmission.
BITS See building integrated timing supply (BITS)
BOD bandwidth on demand
BOM bill of materials
BRA See basic rate access (BRA)
BRAS See broadband remote access server (BRAS)
BSID Binding Segment Identifier, When traffic is diverted to an SR
Policy, for example, if the end-to-end stack is too deep, traffic
can be split into multiple segments and stitched using BSIDs.
BSS Business Support System
BWS backbone wavelength division multiplexing system
basic encoding A rule in the syntax structure of the ASN.1, which describes
rule (BER) how data is represented during transmission.
Bidirectional A fast and independent hello protocol that delivers
Forwarding millisecond-level link failure detection and provides carrier-
Detection class availability. After sessions are established between
(BFD) neighboring systems, the systems can periodically send BFD
packets to each other. If one system fails to receive a BFD
packet within the negotiated period, the system regards that
the bidirectional link fails and instructs the upper layer
protocol to take actions to recover the faulty link.
basic input/ Firmware stored on the computer motherboard that contains
output system basic input/output control programs, power-on self test
(BIOS) (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control
functions for the computer.

iMaster NCE-IP
basic rate An ISDN interface typically used by smaller sites and

access (BRA) customers. This interface consists of a single 16 kbit/s data
(or "D") channel plus two bearer (or "B") channels for voice
and/or data. Also known as Basic Rate Access, or BRI.
broadband A new type of access gateway for broadband networks. As a
remote access bridge between backbone networks and broadband access
server (BRAS) networks, BRAS provides methods for fundamental access
and manages the broadband access network. It is deployed
at the edge of network to provide broadband access services,
convergence, and forwarding of multiple services, meeting
the demands for transmission capacity and bandwidth
utilization of different users. BRAS is a core device for the
broadband users' access to a broadband network.
building In the situation of multiple synchronous nodes or
integrated communication devices, one can use a device to set up a
timing supply clock system on the hinge of telecom network to connect the
(BITS) synchronous network as a whole, and provide satisfactory
synchronous base signals to the building integrated device.
This device is called BITS.
C
CAPEX Capital expenditure (CAPEX) generally refers to the
investment of capital or fixed assets. For telecom operators,
the one-off expenditure on network devices, computers, and
instruments belongs to CAPEX, in which network devices
account for the largest share.
CAS See Central Authentication Service (CAS)
CBU See cellular backhaul unit (CBU)
CC See continuity check (CC)
CCC circuit cross connect
CES See circuit emulation service (CES)
CFS customer facing service
CIR committed information rate
CLEI common language equipment identification
CLI See command-line interface (CLI)
CO Central office (CO) is an office in a locality to which
subscriber home and business lines are connected on what is
called a local loop.
CORBA See Common Object Request Broker Architecture
(CORBA)
CPE See customer-premises equipment (CPE)
CPU See Central Processing Unit (CPU)

iMaster NCE-IP
CSG cell site gateway

CSV See comma separated values (CSV)
Central A single sign-on protocol for the web. Its purpose is to permit
Authentication users to access multiple applications by providing their
Service (CAS) credentials (such as user names and passwords) only once. It
also allows web applications to authenticate users without
gaining access to the users' security credentials (such as
passwords). CAS also refers to a software package that
implements this protocol.
Common A specification developed by the Object Management Group
Object Request in 1992 in which pieces of programs (objects) communicate
Broker with other objects in other programs, even if the two
Architecture programs are written in different programming languages
(CORBA) and are running on different platforms. A program makes its
request for objects through an object request broker, or ORB,
and therefore does not need to know the structure of the
program from which the object comes. CORBA is designed to
work in object-oriented environments.
Coordinated The world-wide scientific standard of timekeeping. It is based
Universal Time upon carefully maintained atomic clocks and is kept accurate
(UTC) to within microseconds worldwide.
cellular A network access unit used for access base transceiver
backhaul unit stations. It provides Ethernet, IP, and TDM services; has
(CBU) multiple Ethernet and 1PPS+ToD interfaces and optionally E1
interfaces. It is mainly applicable to backhaul in mobile base
transceiver stations.
circuit A function with which the E1/T1 data can be transmitted
emulation through ATM networks. At the transmission end, the
service (CES) interface module packs timeslot data into ATM cells. These
ATM cells are sent to the reception end through the ATM
network. At the reception end, the interface module re-
assigns the data in these ATM cells to E1/T1 timeslots. The
CES technology guarantees that the data in E1/T1 timeslots
can be recovered to the original sequence at the reception
end.
comma A CSV file is a text file that stores data, generally used as an
separated electronic table or by the database software.
values (CSV)
command-line A means of communication between a program and its user,
interface (CLI) based solely on textual input and output. Commands are
input with the help of a keyboard or similar device and are
interpreted and executed by the program. Results are output
as text or graphics to the terminal.

iMaster NCE-IP
continuity An Ethernet connectivity fault management (CFM) method

check (CC) used to detect the connectivity between MEPs by having
each MEP periodically transmit a Continuity Check Message
(CCM).
Central The computational and control unit of a computer. The CPU
Processing Unit is the device that interprets and executes instructions. The
(CPU) CPU has the ability to fetch, decode, and execute instructions
and to transfer information to and from other resources over
the computer's main data-transfer path, the bus.
customer- Customer-premises equipment or customer-provided
premises equipment (CPE) is any terminal and associated equipment
equipment located at a subscriber's premises and connected with a
(CPE) carrier's telecommunication channel at the demarcation
point ("demarc"). The demarc is a point established in a
building or complex to separate customer equipment from
the equipment located in either the distribution
infrastructure or central office of the communications service
provider. CPE generally refers to devices such as telephones,
routers, network switches, residential gateways (RG), set-top
boxes, fixed mobile convergence products, home networking
adapters and Internet access gateways that enable
consumers to access communications service providers'
services and distribute them around their house via a local
area network (LAN).
clock source A device that provides standard time for the NTP
configuration.
clock A process of synchronizing clocks, in which the signal
synchronization frequency traces the reference frequency, but the start points
do not need to be consistent. This process is (also known as
frequency synchronization).
clock tracing The method of keeping the time on each node synchronized
with a clock source in the network.
cluster In computer file systems, a cluster or allocation unit is a unit
of disk space allocation for files and directories. To reduce the
overhead of managing on-disk data structures, the file
system does not allocate individual disk sectors by default,
but contiguous groups of sectors, called clusters.
cluster mode Cluster mode is a server redundancy mode. A server cluster
consists of multiple servers that share data storage space.
These servers are connected among themselves by using the
internal local area network (LAN). When one server is faulty,
the server connected to this faulty server takes over all the
services.

iMaster NCE-IP
correlation A function of the network management system. This function

analysis is used to analyze reported alarms comprehensively and
effectively with rule-based correlation analysis technologies,
which helps to reduce network storms and enables the
maintenance personnel to quickly locate faults.
D
D-CCAP See Distributed Converged Cable Access Platform (D-
CCAP).
DB database
DC data center
DCC data communication channel
DCI See Data Center Interconnect (DCI).
DCM See dispersion compensation module (DCM).
DCN See data communication network (DCN)
DDoS See distributed denial of service (DDoS)
DES-CBC Data Encryption Standard-Cipher Block Chaining
DHCP See Dynamic Host Configuration Protocol (DHCP).
DNI PW Dual Node interconnection pseudo wire (DNI PW) is used for
inter-device communication between dual-homing nodes,
especially for active/standby communication on core
aggregation nodes to accelerate active/standby switchover.
DR system See disaster recovery system (DR system).
Dry Run dry run
DSCP Differentiated services code point (DSCP), as another traffic
diversion mode, identifies service packets and directs service
traffic into corresponding tunnels based on the mapping
between DSCP values in service packets and tunnel colors.
DSOE Dynamic Service Orchestration Engine
DSLAM See digital subscriber line access multiplexer (DSLAM)
DWDM See dense wavelength division multiplexing (DWDM)
Dynamic Host A client-server networking protocol. A DHCP server provides
Configuration configuration parameters specific to the DHCP client host
Protocol requesting information the host requires to participate on the
(DHCP) Internet network. DHCP also provides a mechanism for
allocating IP addresses to hosts.
Data Center DCI refers to network interconnection between two data
Interconnect centers for cross-DC service transmission and migration.
(DCI)

iMaster NCE-IP
DoS See denial of service (DoS)

data backup A method of copying key data to the backup storage area to
prevent data loss in case the original storage area is
damaged or a failure occurs.
data A communication network used in a TMN or between TMNs
communication to support the data communication function.
network (DCN)
data dictionary A reserved table within a database which is used to store
information about the database itself. The information
includes database design information, stored procedure
information, user rights, user statistics, database process
information, database increase statistics, and database
performance statistics.
denial of DoS attack is used to attack a system by sending a large
service (DoS) number of data packets. As a result, the system cannot
receive requests from the valid users or the host is suspended
and cannot work normally. DoS attack includes SYN flood,
Fraggle, and others. The DoS attacker only stops the valid
user from accessing resources or devices instead of searching
for the ingresses of the intranet.
dense The technology that utilizes the characteristics of broad
wavelength bandwidth and low attenuation of single mode optical fiber,
division employs multiple wavelengths with specific frequency
multiplexing spacing as carriers, and allows multiple channels to transmit
(DWDM) simultaneously in the same fiber.
device type Device types are used by carriers to manage subscribers'
devices. Through device management, carriers and CPs can
implement functions such as copyright protection and control
on subscribers' device quantity.
digital A network device, usually situated in the main office of a
subscriber line telephone company, that receives signals from multiple
access customer Digital Subscriber Line (DSL) connections and uses
multiplexer multiplexing techniques to put these signals on a high-speed
(DSLAM) backbone line.
disaster A system that consists of the production subsystem which
recovery system provides services, disaster recovery subsystem which provides
(DR system) the disaster recovery function when disasters occur, and NMS
subsystem which manages and monitors the disaster
recovery system and alarms.
dispersion A type of module that contains dispersion compensation
compensation fibers to compensate for the dispersion of the transmitting
module (DCM) fiber.

iMaster NCE-IP
Distributed Distributed converged cable access platform (D-CCAP) meets

Converged the requirements of triple-play network services over hybrid
Cable Access fiber coaxial (HFC) networks of multiservice operators
Platform (D- (MSOs) because of unique advantages of the D-CCAPs, such
CCAP) as high bandwidth and supporting HFC networks.
distributed Distributed Denial of Service attack is one in which a
denial of multitude of compromised systems attack a single target,
service (DDoS) therefore causing denial of service for users of the targeted
system. The flood of incoming messages to the target system
essentially and occupies the resources of it, therefore denying
services to legitimate users.
domain A logical group of IT basic resources for resource plan and
management. Domains are controlled by service level
agreements (SLAs), such as the number of concurrent
requests, computing capability, and storage volume.
dummy device Virtual NE. If some inter-domain devices cannot be managed
by NCE, you can create dummy devices on NCE to
supplement the network topology in support of visualized IP
traffic optimization.
dummy link Virtual link. If some inter-domain devices cannot be
managed by NCE, you can create dummy links on NCE to
supplement the network topology in support of visualized IP
traffic optimization.
E
E-LAN See Ethernet local area network (E-LAN)
E-Line See Ethernet line (E-Line)
E1 An European standard for high-speed data transmission at
2.048 Mbit/s. It provides thirty-two 64 kbit/s channels. A time
division multiplexing frame is divided in to 32 timeslots
numbered from 0 to 31. Timeslot 0 is reserved for frame
synchronization, and timeslot 16 is reserved for signaling
transmission. The rest 30 timeslots are use as speech
channels. Each timeslot sends or receives an 8-bit data per
second. Each frame sends or receives 256-bit data per
second. 8000 frames will be sent or received per second.
Therefore the line data rate is 2.048 Mbit/s.
E2E end to end
ECC See embedded control channel (ECC)
EDFA See erbium-doped fiber amplifier (EDFA)
E2E end to end
EMS See element management system (EMS).
EOS enterprise operation system

iMaster NCE-IP
EPL See Ethernet private line (EPL)

EPON See Ethernet passive optical network (EPON)
ERO explicit route object
ERPS Protection switching mechanisms for ETH layer Ethernet ring
topologies.
EVPL See Ethernet virtual private line (EVPL)
EVPN See Ethernet VPN.
EoO Ethernet over OTN
EoW Ethernet over WDM
Ethernet line A type of Ethernet service that is based on a point-to-point
(E-Line) EVC (Ethernet virtual connection).
Ethernet local A type of Ethernet service that is based on a multipoint-to-
area network multipoint EVC (Ethernet virtual connection).
(E-LAN)
Ethernet An Ethernet Passive Optical Network (EPON) is a passive
passive optical optical network based on Ethernet. It is a new generation
network broadband access technology that uses a point-to-multipoint
(EPON) structure and passive fiber transmission. It supports
upstream/downstream symmetrical rates of 1.25 Gbit/s and a
reach distance of up to 20 km. In the downstream direction,
the bandwidth is shared based on encrypted broadcast
transmission for different users. In the upstream direction,
the bandwidth is shared based on TDM. EPON meets the
requirements for high bandwidth.
Ethernet A type of Ethernet service provided by SDH, PDH, ATM, or
private line MPLS server layer networks. This service is carried over
(EPL) dedicated bandwidth between point-to-point connections.
Ethernet VPN Ethernet Virtual Private Network (EVPN) is a VPN technology
(EVPN) used for Layer 2 network interconnection. EVPN uses a
mechanism similar to BGP or MPLS IP VPN. By extending
BGP and using extended reachability information, EVPN
enables MAC address learning and advertisement between
Layer 2 networks at different sites to be transferred from the
data plane to the control plane.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or
private line MPLS server layer networks. This service is carried over
(EVPL) shared bandwidth between point-to-point connections.
element ITU-T compliant software that is used to manage one or
management more specific types of network element (NE). An EMS
system (EMS) enables a user to individually manage all the features of each
NE, but not the communication between NEs. This
communication is managed by the network management
system (NMS).

iMaster NCE-IP
embedded A logical channel that uses a data communications channel

control channel (DCC) as its physical layer to enable the transmission of
(ECC) operation, administration, and maintenance (OAM)
information between NEs.
enterprise A geographically dispersed network under the jurisdiction of
network one organization. It often includes several different types of
networks and computer systems from different vendors.
erbium-doped An optical device that amplifies optical signals. This device
fiber amplifier uses a short optical fiber doped with the rare-earth element,
(EDFA) Erbium. The signal to be amplified and a pump laser are
multiplexed into the doped fiber, and the signal is amplified
by interacting with doping ions. When the amplifier passes
an external light source pump, it amplifies the optical signals
in a specific wavelength range.
equipment A string of characters that identify a piece of equipment and
serial number ensures correct allocation of a license file to the specified
(ESN) equipment. It is also called "equipment fingerprint".
F
FCAPS fault, configuration, accounting, performance, security
FDN fixed dialing number
FI See FusionInsight (FI).
FIB See forwarding information base (FIB)
FPGA See field programmable gate array (FPGA)
FRR See fast reroute (FRR)
FTP See File Transfer Protocol (FTP)
FTTB See fiber to the building (FTTB)
FTTC See fiber to the curb (FTTC)
FTTH See fiber to the home (FTTH)
File Transfer A member of the TCP/IP suite of protocols, used to copy files
Protocol (FTP) between two computers on the Internet. Both computers
must support their respective FTP roles: one must be an FTP
client and the other an FTP server.
Flex-Algo Flexible Algorithm, the traditional SPF algorithm based on
the link cost value is fixed, which is inconvenient for user-
defined requirements to calculate the optimal path. With
Flex-Algo, an IGP can automatically compute paths based on
link costs, delay, and TE constraints, flexibly implementing TE
requirements.

iMaster NCE-IP
Frequency Frequency synchronization, also called clock synchronization,

synchronization refers to a strict relationship between signals based on a
constant frequency offset or a constant phase offset, in
which signals are sent or received at the same average rate
in a valid instance. In this manner, all devices on the
communications network operate at the same rate. That is,
the phase difference between signals remains a fixed value.
Full-mesh See full mesh topology (Full-mesh).
FusionInsight FI is an IT-class big-data platform that provides Apache
(FI) services, such as Spark, HDFS, and zookeeper.
fast reroute A technology which provides a temporary protection of link
(FRR) availability when part of a network fails. The protocol
enables the creation of a standby route or path for an active
route or path. When the active route is unavailable, the
traffic on the active route can be switched to the standby
route. When the active route is recovered, the traffic can be
switched back to the active route. FRR is categorized into IP
FRR, VPN FRR, and TE FRR.
fault detection The process of determining that a fault has occurred.
fiber to the A fiber-based networking scenario. There are two types of
building (FTTB) FTTB scenarios: multi-dwelling unit (MDU) and business
buildings. Each scenario includes the following service types:
FTTB to the MDU and FTTB to the business buildings.
fiber to the A fiber-based networking scenario. The FTTC scenario
curb (FTTC) provides the following services: asymmetric broadband
services (such as digital broadcast service, VOD, file
download, and online gaming), symmetric broadband
services (such as content broadcast, email, file exchange,
distance education, and distance medical care), POTS, ISDN,
and xDSL backhaul services.
fiber to the A fiber-based networking scenario. The FTTH scenario
home (FTTH) provides the following services: asymmetric broadband
services (digital broadcast service, VoD, file download, and
online gaming), symmetric broadband services (content
broadcast, email, file exchange, distance education, and
distance medical care), POTS, and ISDN services.
field A semi-customized circuit that is used in the Application
programmable Specific Integrated Circuit (ASIC) field and developed based
gate array on programmable components. FPGA remedies many of the
(FPGA) deficiencies of customized circuits, and allows the use of
many more gate arrays.

iMaster NCE-IP
forwarding A table that provides information for network hardware

information (bridges and routers) for them to forward data packets to
base (FIB) other networks. The information contained in a routing table
differs according to whether it is used by a bridge or a router.
A bridge relies on both the source (originating) and
destination addresses to determine where and how to
forward a packet.
full mesh All devices are fully connected in two directions.
topology (Full-
mesh)
G
G.HAO See Hitless adjustment of ODUflex(GFP) (G.HAO).
GE Gigabit Ethernet
GIS Geographic Information System, GIS is a system designed to
capture, store, manipulate, analyze, manage, and present all
types of geographical data.
GMPLS Generalized MultiProtocol Label Switching
GNE See gateway network element (GNE)
GNSS Global Navigation Satellite System. Satellite-based global
navigation system that continuously provides reliable
positioning, navigation and time services to global users.
GPON gigabit-capable passive optical network
GPS See Global Positioning System (GPS).
GR If NCE needs to communicate with the forwarding network
but itself is restarted, routes or links may be interrupted. To
address this issue, enable graceful restart (GR) when
configuring BGP. GR ensures that the routes received from
NCE are always on and the forwarding network forwards
traffic non-stop, thereby improving solution reliability.
GRE See Generic Routing Encapsulation (GRE)
G-SRv6 Generalized Segment Routing over IPv6, G-SRv6 is a general
mechanism compatible with SRv6. It supports multiple types
of SIDs with different lengths. These SIDs are called
Generalized SIDs (G-SIDs). G-SRv6 uses compressed general
SIDs to reduce the overhead of the SID list and reduce the
overhead of SRv6 packet headers.
GUI See graphical user interface (GUI)
Generic A mechanism for encapsulating any network layer protocol
Routing over any other network. GRE is used for encapsulating IP
Encapsulation datagrams tunneled through the Internet. GRE serves as a
(GRE) Layer 3 tunneling protocol and provides a tunnel for
transparently transmitting data packets.

iMaster NCE-IP
Global A global navigation satellite system that provides reliable

Positioning positioning, navigation, and timing services to users
System (GPS) worldwide.
gateway An NE that serves as a gateway for other NEs to
network communicate with a network management system.
element (GNE)
graphical user A visual computer environment that represents programs,
interface (GUI) files, and options with graphical images, such as icons,
menus, and dialog boxes, on the screen.
H
H-VPN See hierarchy VPN (H-VPN).
HA See high availability (HA)
HDD hard disk drive
HFC See high-level foundation classes (HFC)
HMAC See hash-based message authentication code (HMAC)
HQoS See hierarchical quality of service (HQoS)
HSB If all the segments of the primary path are faulty, candidate
path HSB switchover will be triggered to reduce impact on
services.
HSL See high-level script language (HSL)
HTML Hypertext Markup Language
HTTP See Hypertext Transfer Protocol (HTTP).
HTTPS See Hypertext Transfer Protocol Secure (HTTPS)
HVPLS hierarchical virtual private LAN service
Hitless HAO stands for Hitless adjustment of ODUflex. It is the
adjustment of standard of ODUflex resize procedure. But now the official
ODUflex(GFP) standard is ITU-T G.7044/Y.1347 (former G.HAO). For VBR
(G.HAO) services,N*TS will be allocated based on the bit rate of
accessed service, then ODUflex will be mapped into a HO-
ODUk. If the bit rate of the accessed service is changed, with
G.HAO, NMS will command all the nodes between source
and sink to adjust the number of allocated TS to adjust the
size of ODUflex, and also make sure the

iMaster NCE-IP
Hypertext An application-layer protocol used for communications

Transfer between web servers and browsers or other programs. HTTP
Protocol adopts the request-response mode. A client sends a request
(HTTP) to the server. The request consists of two parts: request
header and MIME-like message. The request header contains
request method, uniform resource locator (URL), and
protocol version. The MIME-like message contains request
modifiers, client information, and possible body content.
Upon receiving the request, the server responds with a status
line. The status line includes the message's protocol version,
a success or error code, and a MIME-like message, which
contains server information, entity meta-information, and
possible entity-body content. For details about HTTP, see
RFC2616.The protocol used to carry requests from a browser
to a Web server and to transport pages from Web servers
back to the requesting browser. Although HTTP is almost
universally used on the Web, it is not an especially secure
protocol.Hypertext Transfer Protocol (HTTP) - a networking
protocol for distributed, collaborative, hypermedia
information systems. HTTP is the foundation of data
communication for the World Wide Web.
Hypertext An HTTP protocol that runs on top of transport layer security
Transfer (TLS) and Secure Sockets Layer (SSL) for secured
Protocol Secure transactions. It is used to establish a reliable channel for
(HTTPS) encrypted communication and secure identification of a
network web server. HTTPS consists of communication over
Hypertext Transfer Protocol (HTTP) within a connection
encrypted by Transport Layer Security, or its predecessor,
Secure Sockets Layer. The main motivation for HTTPS is
authentication of the visited website and protection of the
privacy and integrity of the exchanged data.
hash-based In cryptography, a keyed-hash message authentication code
message (HMAC) is a specific type of message authentication code
authentication (MAC) involving a cryptographic hash function (hence the
code (HMAC) 'H') in combination with a secret cryptographic key. As with
any MAC, it may be used to simultaneously verify both the
data integrity and the authentication of a message. Any
cryptographic hash function, such as MD5 or SHA-1, may be
used in the calculation of an HMAC; the resulting MAC
algorithm is termed HMAC-MD5 or HMAC-SHA1 accordingly.
The cryptographic strength of the HMAC depends upon the
cryptographic strength of the underlying hash function, the
size of its hash output, and on the size and quality of the key.
hierarchical A type of QoS that controls the traffic of users and performs
quality of the scheduling according to the priority of user services.
service (HQoS) HQoS has an advanced traffic statistics function, and the
administrator can monitor the usage of bandwidth of each
service. Hence, the bandwidth can be allocated reasonably
through traffic analysis.

iMaster NCE-IP
hierarchy VPN An L3VPN networking type. Using the hierarchy technology,

(H-VPN) H-VPN distributes PE functions such as user access and
router management to multiple PEs to enhance network
scalability.
high A scheme in which two modules operate in active/standby
availability mode to achieve high availability. When the active module
(HA) fails, the standby module automatically takes over the
system functions of the active module.
high-level A group of encapsulated function databases provided by the
foundation iSStar. You can use the provided functions to accelerate script
classes (HFC) editing.
high-level A script language. Based on python, the HSL syntax is simple,
script language clear, and extendable.
(HSL)
historical alarm An alarm that is acknowledged and cleared.
hop A network connection between two distant nodes. For
Internet operation a hop represents a small step on the route
from one main computer to another.
I
IAM See Identity and Access Management (IAM).
IANA See Internet Assigned Numbers Authority (IANA)
IBMS See Integrated Business Management System (IBMS).
ICMP See Internet Control Message Protocol (ICMP)
IDC See Internet Data Center (IDC)
IDE See integrated development environment (IDE).
IDN See integrated digital network (IDN)
IEEE See Institute of Electrical and Electronics Engineers (IEEE).
IEEE 1588v2, defined by the Institute of Electrical and Electronics
1588v2/PTP Engineers (IEEE), is a standard for Precision Clock
Synchronization Protocol for Networked Measurement and
Control Systems. The Precision Time Protocol (PTP) is used
for short.
IETF Internet Engineering Task Force
IGP See Interior Gateway Protocol (IGP)
IOPS input/output operations per second
IoT Internet of Things
IP See Internet Protocol (IP)
IP RAN See IP radio access network (IP RAN)

iMaster NCE-IP
IP radio access A network that uses IP technology to achieve data backhaul

network (IP on a radio access network.
RAN)
IPTV See Internet Protocol television (IPTV)
IPv4 See Internet Protocol version 4 (IPv4)
IPv6 See Internet Protocol version 6 (IPv6)
ISDN Integrated Services Digital Network
ISP See Internet service provider (ISP)
iSStar See Integration Script Star (iSStar)
ITU-T International Telecommunication Union-Telecommunication
Standardization Sector
Identity and A security management service provided by the public cloud
Access system. This service includes identity management,
Management permission management, and access control functions.
(IAM)
Institute of A professional association of electrical and electronics
Electrical and engineers based in the United States, but with membership
Electronics from numerous other countries. The IEEE focuses on
Engineers electrical, electronics, and computer engineering, and
(IEEE) produces many important technology standards.
Integrated Business management platform of the PTT service. It
Business provides a data synchronization interface for the BOSS so
Management that enterprise administrators and members can perform
System (IBMS) operations such as registration, deregistration, modification,
and query.
Interior A routing protocol that is used within an autonomous
Gateway system. The IGP runs in small-sized and medium-sized
Protocol (IGP) networks. The IGPs are RIP, IGRP, EIGRP, OSPF, and IS-IS.
Internet A department operated by the IAB. IANA delegates authority
Assigned for IP address-space allocation and domain-name
Numbers assignment to the NIC and other organizations. IANA also
Authority maintains a database of assigned protocol identifiers used in
(IANA) the TCP/IP suite, including autonomous system numbers.
Internet A network layer protocol that provides message control and
Control error reporting between a host server and an Internet
Message gateway.
Protocol (ICMP)
Internet Data The telecommunications sector uses available Internet
Center (IDC) communication lines and bandwidth resources to establish a
standard and carrier-class equipment environment in which
comprehensive services such as server hosting, renting, and
other value-added services are provided for enterprises and
governments.

iMaster NCE-IP
Internet The protocol within TCP/IP that governs the breakup of data
Protocol (IP) messages into packets, the routing of the packets from
sender to destination network and station, and the
reassembly of the packets into the original data messages at
the destination. IP runs at the internetwork layer in the
TCP/IP model—equivalent to the network layer in the
ISO/OSI reference model. The IP provides a connectionless
datagram network layer and allows an application to
communicate transparently across several connected
networks.
Internet A system that provides TV services over the IP network. In
Protocol the IPTV system, media streams from satellites, terrestrial,
television and studios are converted by the encoder to the media
(IPTV) streams applicable to the IP network. Then the media
streams are transmitted to the terminal layer on the IP
network. Media content is displayed on a TV set after media
streams are processed by specified receiving devices (for
example, an STB).
Internet The current version of the Internet Protocol (IP). IPv4 utilizes
Protocol version a 32bit address which is assigned to hosts. An address
4 (IPv4) belongs to one of five classes (A, B, C, D, or E) and is written
as 4 octets separated by periods and may range from 0.0.0.0
through to 255.255.255.255. Each IPv4 address consists of a
network number, an optional subnetwork number, and a host
number. The network and subnetwork numbers together are
used for routing, and the host number is used to address an
individual host within the network or subnetwork.
Internet An update version of IPv4, which is designed by the Internet
Protocol version Engineering Task Force (IETF) and is also called IP Next
6 (IPv6) Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an
IPv4 address has 32 bits while an IPv6 address has 128 bits.
Internet service An organization that offers users access to the Internet and
provider (ISP) related services.
indicator group A specific measurement category consisting of one or more
indicators with similar properties. Examples include incoming
traffic, outgoing traffic, and loss statistics.
integrated An IDE is a software application that provides comprehensive
development facilities to computer programmers for software
environment development. An IDE will normally consist of a source code
(IDE) editor as well as facilities to access other development tools
such as compiler and/or interpreter, build automation tools, a
debugger etc. A model driven development (MDD) tool
based on the Eclipse framework. It is also an integration tool
for service life cycle management, which integrates service
design, development, debugging, and deployment.

iMaster NCE-IP
integrated A set of digital nodes and digital links that uses integrated
digital network digital transmission and switches to provide digital
(IDN) connections between two or more defined points.
Integration The enhanced platform of the Huawei OSS, which is
Script Star developed twice. You can complete specific services through
(iSStar) the provided HSL and HFC library program on the platform.
J
JSON See JavaScript Object Notation (JSON).
JavaScript A language-independent data format. It is derived from the
Object JavaScript scripting language and consists of name-value
Notation pairs (objects) and ordered collections of values (arrays).
(JSON)
jitter The measure of short waveform variations caused by
vibration, voltage fluctuations, and control system instability.
K
KPI key performance indicator
Kafka A distributed, partitioned, and replicated message releasing
and subscription system. It provides features similar to the
Java Message Service (JMS), but the design is different. The
Kafka provides features, such as message persistence, high
throughput, multi-client support, and real-time processing,
and applies to online and offline message consumption. The
Kafka applies to Internet service massive data collection
scenarios, such as conventional data ingestion, active website
tracking, aggregation of operation data in statistics systems
(monitoring data), and log collection.
L
L2TP Layer 2 Tunneling Protocol
L2VPN Layer 2 virtual private network
L3VPN Layer 3 virtual private network
LAG See link aggregation group (LAG)
LAN See local area network (LAN)
Latency Latency refers to the time it takes for the original data to go
through a series of processing steps such as coding, to be
transmitted through the channel, to arrive at the receiver,
and to be decoded.
LB See loopback (LB)

iMaster NCE-IP
LDP A Protocol defined for distributing labels in MPLS network. It

is the set of procedures and messages by which Label
Switched Routers (LSRs) establish Label Switched Paths
(LSPs) through a network by mapping network-layer routing
information directly to data-link layer switched paths.
LLDP See Link Layer Discovery Protocol (LLDP)
LSA link-state advertisement
LSP label switched path. The path created by the concatenation
of one or more label switched hops, allowing a packet to be
forwarded by swapping labels from an MPLS node to another
MPLS node.
LSR See label switching router (LSR)
LTE See Long Term Evolution (LTE)
LVS Linux Virtual Server
Label Stack A label stack is an ordered set of labels and is used to
identify a complete label switched path (LSP).
Link Layer The Link Layer Discovery Protocol (LLDP) is an L2D protocol
Discovery defined in IEEE 802.1ab. Using the LLDP, the NMS can rapidly
Protocol (LLDP) obtain the Layer 2 network topology and changes in
topology when the network scales expand.
Long Term LTE, an abbreviation for Long-Term Evolution, commonly
Evolution (LTE) marketed as 4G LTE, is a standard for wireless
communication of high-speed data for mobile phones and
data terminals. It is based on the GSM/EDGE and UMTS/
HSPA network technologies, increasing the capacity and
speed using a different radio interface together with core
network improvements.[1][2] The standard is developed by
the 3GPP (3rd Generation Partnership Project) and is
specified in its Release 8 document series, with minor
enhancements described in Release 9.
label switching Basic element of an MPLS network. All LSRs support the
router (LSR) MPLS protocol. The LSR is composed of two parts: control
unit and forwarding unit. The former is responsible for
allocating the label, selecting the route, creating the label
forwarding table, creating and removing the label switch
path; the latter forwards the labels according to groups
received in the label forwarding table.
license A permission that the vendor provides for the user with a
specific function, capacity, and duration of a product. A
license can be a file or a serial number. Usually the license
consists of encrypted codes. The operation authority granted
varies with the level of the license.

iMaster NCE-IP
license file The license file is an authorization for the capacity, functions,
and validity period of the installed software. The license file
is a .dat or an .xml file that is generated using the special
encryption tool according to the contract, and is delivered
electronically. The customer (e.g. carrier) needs to load the
license on the device or software before the functions
supported by the license are applicable.
link An aggregation that allows one or more links to be
aggregation aggregated together to form a link aggregation group so
group (LAG) that a MAC client can treat the link aggregation group as if it
were a single link.
link protection Protection provided by the bypass tunnel for the link on the
working tunnel. The link is a downstream link adjacent to the
point of local repair (PLR). When the PLR fails to provide
node protection, the link protection should be provided.
local area A network formed by the computers and workstations within
network (LAN) the coverage of a few square kilometers or within a single
building, featuring high speed and low error rate. Current
LANs are generally based on switched Ethernet or Wi-Fi
technology and run at 1,000 Mbit/s (that is, 1 Gbit/s).
local storage Storage space provided by a computing node agent (CNA).
loopback (LB) A troubleshooting technique that returns a transmitted signal
to its source so that the signal or message can be analyzed
for errors. The loopback can be a inloop or outloop.
M
MA maintenance association
MAC See Media Access Control (MAC)
MAC address A link layer address or physical address. It is six bytes long.
MBB mobile broadband
MBB Make Before Break, when the route changes, the node
deletes the original path after the new path is established to
minimize traffic loss.
MC-LAG Multi-chassis link aggregation group (MC-LAG) is a
supplement to the single-chassis link aggregation group (SC-
LAG) and allows aggregation of inter-chassis links. It provides
dual-homing protection for Ethernet services.
MC-PW APS Multi-chassis pseudo wire automatic protection switching
(MC-PW APS) can work with multi-chassis link aggregation
group (MC-LAG) or multi-chassis linear multiplex section
protection (MC-LMSP) to implement dual-homing protection
for ATM/CES emulation and private line services.
MD See maintenance domain (MD)

iMaster NCE-IP
MD5 See message digest algorithm 5 (MD5)

MDF See main distribution frame (MDF)
MDU See multi-dwelling unit (MDU)
ME See managed element (ME)
MEP maintenance association end point
MIB See management information base (MIB)
MIP maintenance association intermediate point
MO managed object
MOS mean opinion score
MLR-N multi-layer restoration by any node
MLR-P multi-layer restoration by router port
MP2MP See multipoint-to-multipoint (MP2MP).
MPLS See Multiprotocol Label Switching (MPLS)
MPLS TE multiprotocol label switching traffic engineering
MPLS-TP MPLS Transport Profile
MPLS VPN See multiprotocol label switching virtual private network
(MPLS VPN)
MS-PW See multi-segment pseudo wire (MS-PW)
MSAN multiservice access node
MSAP Multi-service access platform (MSAP).
MSTP See multi-service transmission platform (MSTP)
MTN FG The use of MTN channels (that is, FlexE channels) results in
Channel the minimum bandwidth granularity being 1 Gbit/s. However,
in many scenarios, bandwidth is less than 1 Gbit/s. Therefore,
MTN FG channels add an FGU layer to divide bandwidth at a
smaller granularity of N x 10 Mbit/s without affecting
features such as hard isolation and low latency.
MTOSI Multi-Technology Operations System Interface
MTTR See Mean Time to Repair (MTTR)
MTU Maximum transmission unit. Packets longer than the MTU
need to be fragmented. If the packets carry a "no
fragmentation" flag, they will be discarded.
Mean Time to The average time that a device will take to recover from a
Repair (MTTR) failure.

iMaster NCE-IP
Media Access A protocol at the media access control sublayer. The protocol
Control (MAC) is at the lower part of the data link layer in the OSI model
and is mainly responsible for controlling and connecting the
physical media at the physical layer. When transmitting data,
the MAC protocol checks whether to be able to transmit
data. If the data can be transmitted, certain control
information is added to the data, and then the data and the
control information are transmitted in a specified format to
the physical layer. When receiving data, the MAC protocol
checks whether the information is correct and whether the
data is transmitted correctly. If the information is correct and
the data is transmitted correctly, the control information is
removed from the data and then the data is transmitted to
the LLC layer.
Metro Metro Transport Network (that is, FlexE channel).Although
Transport FlexE Client interfaces implement physical isolation and
Network flexible bandwidth configuration, packet switching is still
(MTN) Channel used hop by hop, leading to complex processing. With the
MTN channel technology, services are directly cross-
connected at the shim layer when passing through
intermediate nodes. This technology eliminates IP forwarding
processes such as framing, packet assembly, table lookup,
and buffering, achieving low-latency low-jitter forwarding.
Multiprotocol A technology that uses short tags of fixed length to
Label Switching encapsulate packets in different link layers, and provides
(MPLS) connection-oriented switching for the network layer on the
basis of IP routing and control protocols.
mail server A server that can receive and send mails. In the report
system, the mail server can forward reports to the external
mail boxes of users.
main A device at a central office, on which all local loops are
distribution terminated.
frame (MDF)
main topology A basic component of a human-machine interface. It is the
default client interface of the NMS and intuitively displays
the structure of a network, NEs on the network, subnets in
the network as well as the NE communication and running
status, reflecting the overall network running status.
maintenance The network or the part of the network for which
domain (MD) connectivity is managed by connectivity fault management
(CFM). The devices in a maintenance domain are managed
by a single Internet service provider (ISP).
maintenance A time window during which the user can perform operations
window and maintenance on devices. During tunnel optimization, the
system bypasses devices and links requiring maintenance and
provides the user with this time window to perform it.

iMaster NCE-IP
managed A particular entity or resource in a networked system

element (ME) environment. It can also represent a physical piece of
equipment on the network, the components of the device on
the network, or parts of the network itself.
management A type of database used for managing the devices in a
information communications network. It comprises a collection of objects
base (MIB) in a (virtual) database used to manage entities (such as
routers and switches) in a network.
masked alarm An alarm whose correlation action is set to masked in alarm
correlation analysis.
message digest A hash function that is used in a variety of security
algorithm 5 applications to check message integrity. MD5 processes a
(MD5) variable-length message into a fixed-length output of 128
bits. It breaks up an input message into 512-bit blocks
(sixteen 32-bit little-endian integers). After a series of
processing, the output consists of four 32-bit words, which
are then cascaded into a 128-bit hash number.
multi-dwelling A network access unit used for multi-dwelling units. It
unit (MDU) provides Ethernet and IP services and optionally VoIP or
CATV services; has multiple broadband interfaces on the user
side and optionally POTS ports or CATV RF ports. It is mainly
applicable to FTTB, FTTC, or FTTCab networks.
multipoint-to- A transmission mode for delivering data from more than one
multipoint source to one or more receivers.
(MP2MP)
multi-segment A collection of multiple adjacent PW segments. Each PW
pseudo wire segment is a point-to-point PW. The use of MS-PWs to bear
(MS-PW) services saves tunnel resources and can transport services
over different networks.
multi-service A platform based on the SDH platform, capable of accessing,
transmission processing and transmitting TDM services, ATM services, and
platform Ethernet services, and providing unified management of
(MSTP) these services.
multiprotocol An Internet Protocol (IP) virtual private network (VPN) based
label switching on the multiprotocol label switching (MPLS) technology. It
virtual private applies the MPLS technology for network routers and
network (MPLS switches, simplifies the routing mode of core routers, and
VPN) combines traditional routing technology and label switching
technology. It can be used to construct the broadband
Intranet and Extranet to meet various service requirements.
N
NAT Network address translation (NAT) is a type of network
connection in hosted networking that enables you to connect
your VMs to an external network when you have only one IP
network address and the host computer uses that address.

iMaster NCE-IP
NBI See northbound interface (NBI)

NCE See Network Cloud Engine
NE See network element (NE)
NE Explorer The main operation interface, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can
query, manage, and maintain NEs, boards, and ports.
NE ID An ID that indicates a managed device in the system. In the
network, each NE has a unique NE ID.
NETCONF See Network Configuration Protocol (NETCONF)
Network side For the NMS, the Network side refers to the managed
network. The Agent defined in the SNMP protocol runs
among the network devices. In the datacom NMS, the
network side consists of routers, switches, firewall and many
other datacom devices.
NGFW See Next-Generation Firewall (NGFW)
NML See network management layer (NML)
NMS See network management system (NMS)
NNI Network node interface
NSAP See network service access point (NSAP)
NT1 See network termination 1 (NT1)
NTP See Network Time Protocol (NTP)
NetStream As a measurement and release technique based on network
stream information, NetStream can categorize and measure
the traffic on the network and the utilization of resources. It
performs management and charging for various services and
based on different QoS.
Network NETCONF is the communication management protocol. It
Configuration uses XML-based data encoding for the configuration data
Protocol and protocol messages, and provides a mechanism for
(NETCONF) installing, operating, and deleting NEs.

iMaster NCE-IP
Network Cloud NCE is the first in the industry to integrate management,

Engine control, analysis, and AI functions. It effectively connects
physical networks with business intents and implements
centralized management, control, and analysis of global
networks. NCE enables resource cloudification, full-lifecycle
automation, and data analytics-driven intelligent closed-loop
management according to business and service intents, while
also providing open network APIs for rapid integration with
IT systems. Mainly applied in carrier network, data center,
enterprise campus, and enterprise private line scenarios, NCE
accelerates service transformation and innovation for carriers
and enterprises by improving network simplicity, intelligence,
openness, and security.
Network Time The Network Time Protocol (NTP) defines the time
Protocol (NTP) synchronization mechanism. It synchronizes the time
between the distributed time server and the client.
Next- The Next Generation Firewall is a line-speed device specific
Generation to network security. It integrates intelligent interworking with
Firewall other network devices, visual application identification and
(NGFW) control, and legacy firewall functions, fulfilling the needs of
enterprises on network security.
narrowband Communication services that transmit over TDM timeslot.
The PSTN is normally a narrowband network. A
communication channel whose transmission rate is lower
than 2 Mbit/s is usually considered to be narrowband.
navigation tree Find a topic through the navigator tree. The navigator tree is
designed according to the habits of the operator when
performing routine operations and maintenance. You can
find a desired topic by using the navigator tree on the
Contents tab.
network An entity that contains hardware and software. An NE has at
element (NE) least one main control board that manages and monitors the
entire network element. The NE software runs on the main
control board.
network A management layer which is responsible for the
management management of network elements on an individual or
layer (NML) collective basis.
network A system in charge of the operation, administration, and
management maintenance of a network.
system (NMS)
network service A network address defined by ISO, at which the OSI Network
access point Service is made available to a Network service user by the
(NSAP) Network service provider.

iMaster NCE-IP
network A type of terminal device that provides U-interface and S/T

termination 1 interface, used to connect the ISDN terminals and ISDN
(NT1) exchange equipment. It mainly performs code switch
between the U-interface and the S/T interface, such as the
code switch between the 2B1Q and the AMI in Chinese
standards. The NT1 mostly work at only the physical layer,
without software intelligence; the devices, however, support
functions of line maintenance and performance monitoring,
and ensure the clock synchronization between the ISDN
terminals and the network.
network The configuration or layout of a network formed by the
topology connections between devices on a LAN (local area network)
or between two or more LANs.
node A virtual machine used for application or service deployment.
northbound An interface that connects to the upper-layer device to
interface (NBI) provision services and report alarms and performance
statistics.
O
O&M See operations and maintenance (O&M).
O&M analysis O&M analysis monitors services in the business system in
real time based on health analysis and capacity management
of the system, which helps carriers to know the system
running status of the system in a quantified and graphical
manner and detect potential risks in advance.
OAM See operation, administration and maintenance (OAM)
OCS optical core switching
OCh optical channel with full functionality
ODN optical distribution network
ODU Optical channel Data Unit
ODUk optical channel data unit - k
OLA optical line amplifier
OLT optical line terminal
OMC See Operation and Maintenance Center (OMC)
OMS optical multiplexing section
ONT See optical network terminal (ONT)
ONU See optical network unit (ONU)
OP OPerator variant algorithm configuration field
OPEX See operating expense (OPEX)

iMaster NCE-IP
OPS See optical physical section (OPS)

OS operating system
OSI open systems interconnection
OSN optical switch node
OSNR See optical signal-to-noise ratio (OSNR)
OSPF See Open Shortest Path First (OSPF)
OSPF-TE Open Shortest Path First-Traffic Engineering
OSS operations support system
OTN optical transport network
OTS See optical transmission section (OTS)
OTT over the top
OTSN Optical Transmission Slicing Network
OTUk Optical channel transport unit-k (OTUk).
OVPN Optical virtual private network (OVPN) divides optical
network resources into logically independent networks that
can be allocated to different users as dedicated networks.
Open Shortest A link-state, hierarchical interior gateway protocol (IGP) for
Path First network routing that uses cost as its routing metric. A link
(OSPF) state database is constructed of the network topology, which
is identical on all routers in the area.
OpenStack OpenStack is a free and open-source software platform for
cloud computing, mostly deployed as infrastructure-as-a-
service (IaaS), whereby virtual servers and other resources
are made available to customers.[2] The software platform
consists of interrelated components that control diverse,
multi-vendor hardware pools of processing, storage, and
networking resources throughout a data center.
operating An operating expense, operating expenditure, operational
expense (OPEX) expense, operational expenditure or OPEX is an ongoing cost
for running a product, business, or system.
Operation and An element within a network management system
Maintenance responsible for the operations and maintenance of a specific
Center (OMC) element or group of elements. For example an OMC-Radio
may be responsible for the management of a radio
subsystem where as an OMC-Switch may be responsible for
the management of a switch or exchange. However, these
will in turn be under the control of a NMC (Network
Management Centre) which controls the entire network.
operation log A list of information about operation events.

iMaster NCE-IP
operation set A collection of operations. Classifying operations into

operation sets helps to manage user operation rights.
Operations performed by different users have different
impacts on system security. Operations with similar impacts
are classified into an operation set. Users or user groups
entitled to an operation set can perform all the operations in
the operation set. The NMS provides some default operation
sets. If the default operation sets cannot meet the
requirements for right allocation, users can create operation
sets as required.
operation, A set of network management functions that cover fault
administration detection, notification, location, and repair.
and
maintenance
(OAM)
operations and Operations and maintenance (O&M) is responsible for
maintenance monitoring and managing the equipment in the
(O&M) communication network.
optical network A device that terminates the fiber optical network at the
terminal (ONT) customer premises.
optical network A form of Access Node that converts optical signals
unit (ONU) transmitted via fiber to electrical signals that can be
transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
optical physical A network segment in the physical layer of optical network.
section (OPS)
optical signal- The ratio of signal power to noise power in a transmission
to-noise ratio link. OSNR is the most important index for measuring the
(OSNR) performance of a DWDM system.
optical A section in the logical structure of an optical transport
transmission network (OTN). The OTS allows the network operator to
section (OTS) perform monitoring and maintenance tasks between NEs.
P
P2MP point-to-multipoint
P2P See point-to-point service (P2P)
PCE Path Computation Elemen, the PCE can calculate the optimal
E2E primary path for a tunnel based on the network
topology and LSP information.
PCEP Path Computation Element Communication Protocol, A
protocol that enables communication between the PCE
server and PCCs or between PCE servers in different domains.
PE See provider edge (PE)
PER packed encoding rules

iMaster NCE-IP
PIM Protocol Independent Multicast

PIR A parameter, indicating the peak traffic rate, in the unit of
bit/s.
PKI See public key infrastructure (PKI)
PMS performance management system
PON passive optical network
POTS See plain old telephone service (POTS)
PPP Point-to-Point Protocol
PPPoE Point-to-Point Protocol over Ethernet
PRA See primary rate access (PRA)
PSN See packet switched network (PSN)
PSTN See Public Switched Telephone Network (PSTN)
PTN packet transport network
PTP clock See Precision Time Protocol clock (PTP clock).
PVC permanent virtual channel
PW See pseudo wire (PW)
PWE3 See Pseudowire Emulation Edge-to-Edge (PWE3)
Packet Loss The ratio of total lost packet outcomes to total transmitted
Rate packets in a population of interest.
PnP See plug and play (PnP).
Precision Time A type of high-decision clock defined by the IEEE 1588 V2
Protocol clock standard. The IEEE 1588 V2 standard specifies the precision
(PTP clock) time protocol (PTP) in a measurement and control system.
The PTP protocol ensures clock synchronization precise to
sub-microseconds.
Pseudowire An end-to-end Layer 2 transmission technology. It emulates
Emulation the essential attributes of a telecommunication service such
Edge-to-Edge as ATM, FR or Ethernet in a packet switched network (PSN).
(PWE3) PWE3 also emulates the essential attributes of low speed
time division multiplexing (TDM) circuit and SONET/SDH.
The simulation approximates to the real situation.
packet A telecommunications network that works in packet
switched switching mode.
network (PSN)
patch An independent software unit used for fixing the bugs in
software.

iMaster NCE-IP
performance A limit for generating an alarm for a selected entity. When

threshold the measurement result reaches or exceeds the preset alarm
threshold, the performance management system generates a
performance alarm.
personal data Information that can help identify a natural person when
used alone or combined with other statistics.
physical layer Layer 1 in the Open System Interconnection (OSI)
architecture; the layer that provides services to transmit bits
or groups of bits over a transmission link between open
systems and which entails electrical, mechanical and
handshaking.
physical NE The communication equipment that is physically connected
to and managed by the management system.
physical A network of physical machines (plus cabling, switches,
network routers, and so on) that are connected so that they can send
data to and receive data from each other. See also virtual
network.
physical view The default view that is used to display all devices and the
topology partition (according to the area or the maintenance
relation) in the network.
ping A method used to test whether a device in the IP network is
reachable according to the sent ICMP Echo messages and
received response messages.
ping test A test that is performed to send a data packet to the target
IP address (a unique IP address on the device on the
network) to check whether the target host exists according
to the data packet of the same size returned from the target
host.
plain old The basic telephone service provided through the traditional
telephone cabling such as twisted pair cables.
service (POTS)
plug and play A Windows technology that automatically detects and
(PnP) configures most of the adapters and peripherals that can be
connected to a PC. For communication networks, fast
discovery of network topology can help the newly attached
devices communicate with the nodes on the network,
without the need to configure the new devices.
point-to-point A service between two terminal users. In P2P services,
service (P2P) senders and recipients are terminal users.
primary rate A standardized ISDN user-network interface structure
access (PRA) utilizing the capacity of the primary level of the digital
hierarchy, that is, 1544 kbit/s or 2048 kbit/s digit rate. Note:
The digit rate of any D-channel in this interface structure is
64 kbit/s.

iMaster NCE-IP
private line Private line services are the most important type of B2B
service for carriers.
protection path A path in a protection group that transports services when a
fault occurs on the working path.
provider edge A device that is located in the backbone network of the
(PE) MPLS VPN structure. A PE is responsible for managing VPN
users, establishing LSPs between PEs, and exchanging routing
information between sites of the same VPN. A PE performs
the mapping and forwarding of packets between the private
network and the public channel. A PE can be a UPE, an SPE,
or an NPE.
pseudo wire An emulated connection between two PEs for transmitting
(PW) frames. The PW is established and maintained by PEs
through signaling protocols. The status information of a PW
is maintained by the two end PEs of a PW.
public key A set of hardware, software, people, policies, and procedures
infrastructure needed to create, manage, distribute, use, store, and revoke
(PKI) digital certificates. In cryptography, a PKI is an arrangement
that binds public keys with respective user identities by
means of a certificate authority (CA).
Public Switched A telecommunications network established to perform
Telephone telephone services for the public subscribers. Sometimes it is
Network called POTS.
(PSTN)
Q
QinQ See 802.1Q in 802.1Q (QinQ)
R
RADIUS See Remote Authentication Dial In User Service (RADIUS)
RAID redundant array of independent disks
RAN See radio access network (RAN)
RD Routing distinguisher. A 8-byte field in a VPN IPv4 address.
An RD and a 4-byte IPv4 address prefix construct a VPN IPv4
address, which is used to differentiate the IPv4 prefixes using
the same address space.
REG See regenerator (REG)
REST See Representational State Transfer (REST)
RESTCONF See RESTCONF (RESTCONF)
RESTCONF An HTTP-based protocol that provides a programmatic
(RESTCONF) interface for accessing data defined in YANG, using the
datastore concepts defined in the Network Configuration
Protocol (NETCONF).

iMaster NCE-IP
RESTful RESTful is a software architecture style rather than a

standard. It provides a set of software design guidelines and
constraints for designing software for interaction between
clients and servers. RESTful software is simpler and more
hierarchical, and facilitates the implementation of the cache
mechanism.
RFC See Requirement For Comments (RFC)
RFS resource-facing service
RIP See Routing Information Protocol (RIP).
RM See redundancy machine (RM).
RMEP remote maintenance association end point
RMON remote network monitoring
RNC See radio network controller (RNC)
ROADM reconfigurable optical add/drop multiplexer
RPD route policy distribution
RPO See recovery point objective (RPO)
RSG radio network controller site gateway
RSVP-TE See Resource Reservation Protocol-Traffic Engineering
(RSVP-TE)
RT routing target
RTN radio transmission node
RTO See recovery time objective (RTO)
RX receive end
Representation Representational State Transfer (REST) is a style of software
al State architecture for distributed systems such as the World Wide
Transfer (REST) Web. REST has emerged as a predominant Web service
design model. REST facilitates the transaction between web
servers by allowing loose coupling between different services.
Requirement A document about standards, protocols, or other information
For Comments pertaining to the operation of the Internet. The RFC, under
(RFC) the control of the Internet Architecture Board (IAB), is
actually issued after discussion and serves as a standard
document. RFCs can be obtained from sources such as
InterNIC.
Resource An extension to the RSVP protocol for setting up label
Reservation switched paths (LSPs) in MPLS networks. The RSVP-TE
Protocol-Traffic protocol is used to establish and maintain the LSPs by
Engineering initiating label requests and allocating label binding
(RSVP-TE) messages. It also supports LSP rerouting and LSP bandwidth
increasing.

iMaster NCE-IP
Routing A simple routing protocol that is part of the TCP/IP protocol

Information suite. It determines a route based on the smallest hop count
Protocol (RIP) between the source and destination. RIP is a distance vector
protocol that routinely broadcasts routing information to its
neighboring routers and is known to waste bandwidth.
Routing prefix Part of network addresses. The length of this part determines
the size of the network, hence the number of subnets.
Routing prefixes are generally expressed in classless inter-
domain routing (CIDR) format.
radio access The network that provides the connection between CPEs and
network (RAN) the CN. It isolates the CN from wireless network.
radio network A device in a radio network subsystem that is in charge of
controller controlling the usage and integrity of radio resources.
(RNC)
recovery point RPO is a service switchover policy, minimizing data loss
objective (RPO) 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 A service switchover policy that ensures the shortest
objective (RTO) 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.
redundancy A machine that provides the redundancy function for the
machine (RM) production machine.
regenerator A piece of equipment or device that regenerates electrical
(REG) signals.
Remote A security service that authenticates and authorizes dial-up
Authentication users and is a centralized access control mechanism.
Dial In User
Service
(RADIUS)
route By simulating IGP/BGP/TE, the system analyzes route
simulation computation of IP devices, and generates protocol routes and
forwarding routes of the devices.
S
SAML See Security Assertion Markup Language (SAML)
SAN See storage area network (SAN)
SAS serial attached SCSI
SBI See southbound interface (SBI).
SBU See single business unit (SBU)

iMaster NCE-IP
SID list NCE simulates the SR-BE forwarding paths on devices based
reduction on the "least cost" principle. While ensuring that the SR-BE
forwarding paths are consistent with SR Policy paths, it does
not deliver co-routed link SIDs, minimizing the number of
SIDs.
SDH See synchronous digital hierarchy (SDH)
SDN See software-defined networking (SDN)
SFP See security function policy (SFP).
SFTP See Secure File Transfer Protocol (SFTP)
SHDSL See single-pair high-speed digital subscriber line (SHDSL)
SIG Service Intelligence Gateway
SLA See Service Level Agreement (SLA)
SM_TTI section monitoring trail trace identifier
SMS Service Management System
SMTP See Simple Mail Transfer Protocol (SMTP)
SN service node
SNCP subnetwork connection protection
SNMP See Simple Network Management Protocol (SNMP)
SOAP See Simple Object Access Protocol (SOAP)
SPE See superstratum provider edge (SPE)
SR See strict routing (SR)
SRv6 Segment Routing over IPv6.
SRG See shared risk group (SRG)
SRLG Shared Risk Link Group, as a constraint for TE path
calculation, the backup path and primary path cannot be
established on links with the same risk level. This further
enhances TE tunnel reliability.
SSH See Secure Shell (SSH)
SSM The Source-Specific Multicast is the technology that is
implemented by PIM-SM.
SSO single sign-on
STM synchronous transfer mode
STM-1 See Synchronous Transport Module level 1 (STM-1)
STelnet See Secure Telnet (STelnet)
SVN Secure Sockets Layer virtual private network

iMaster NCE-IP
Secure File A network protocol designed to provide secure file transfer

Transfer over SSH.
Protocol (SFTP)
Secure Shell SSH is a set of network protocols for securing connections
(SSH) between computers, as well as the utility suite that
implements these protocols.
Secure Telnet A basic interface on network management devices that is
(STelnet) used for remote login and device management. STelnet is a
secure version of Telnet that runs over SSH, providing
security functions such as encryption and enhanced
authentication.
Security Organization continue to manage their risks, potential
Management threats and system coordination activities.
Security An XML-based open standard for exchanging authentication
Assertion and authorization data between security domains.
Markup
Language
(SAML)
Service Level A service contract between a customer and a (SLA) service
Agreement provider that specifies the forwarding service a customer
(SLA) should receive. A customer may be a user organization
(source domain) or another DS domain (upstream domain).
A SLA may include traffic conditioning rules which constitute
a TCA in whole or in part.
Simple Mail The TCP/IP protocol which facilitates the transfer of
Transfer electronic-mail messages, specifies how two systems are to
Protocol interact, and the format of messages used to control the
(SMTP) transfer of electronic mail.
Simple An IETF protocol for monitoring and managing systems and
Network devices in a network. The data being monitored and
Management managed is defined by a MIB. The functions supported by the
Protocol protocol are the request and retrieval of data, the setting or
(SNMP) writing of data, and traps that signal the occurrence of
events.
Simple Object A type of protocol that is lightweight, simple, and XML-
Access Protocol based. It is designed to exchange structured information at
(SOAP) web.
Soft Pinning A tunnel path locking mode in which a tunnel always sticks
to the locked path as much as possible. If the locked path
cannot meet the tunnel constraints or encounters a link fault,
the tunnel can switch to another path.
Stitching Label A special MPLS label that associates LSPs that are split to
prevent the label stack of an SR-TE LSP from exceeding the
processing capability of a device.

iMaster NCE-IP
Synchronization On a modern communications network, in most cases, the

proper functioning of telecommunications services requires
network clock synchronization, meaning that the frequency
offset or time difference between devices must be kept in an
acceptable range. Network clock synchronization includes
frequency synchronization and time synchronization.
Synchronous Synchronous transfer mode at 155 Mbit/s.
Transport
Module level 1
(STM-1)
security A security strategy adopted to implement the functions
function policy required by the security factors of the security subsystem of
(SFP) the network (SSON).
security Performs vulnerability scans on hosts and middleware,
hardening analyzes OS and component versions, and fixes and hardens
components, all at the click of a button.
service Service assurance provides functions including the service call
assurance chain, call tracing, and log collection to facilitate fault
demarcation and proactive fault management, which ensure
quick system fault locating.
service Service monitoring is a business function, which includes
monitoring multidimensional service analysis, service health monitoring,
KPI collection, capacity monitoring, and capacity trend
prediction. Service monitoring helps detect potential risks in
advance through real-time service status monitoring.
service A measure that ensures that services can be received at the
protection receive end.
service provider A Service Provider is either a network operator or an other
entity that provides services to a subscriber (e.g. a MVNO)
shared risk A group of resources that share a common risk component
group (SRG) whose failure can cause the failure of all the resources in the
group.
single business A network access unit used for individual enterprise users or
unit (SBU) individual offices. It functions as a broadband access
terminal, provides Ethernet, IP, and TDM services and
optionally VoIP services; has Ethernet and E1 interfaces and
optionally POTS ports. It is mainly applicable to FTTO
networks.
single-pair A symmetric digital subscriber line technology developed
high-speed from HDSL, SDSL, and HDSL2, which is defined in ITU-T G.
digital 991.2. The SHDSL port is connected to the user terminal
subscriber line through the plain telephone subscriber line and uses trellis
(SHDSL) coded pulse amplitude modulation (TC-PAM) technology to
transmit high-speed data and provide the broadband access
service.

iMaster NCE-IP
site A group of IP systems with IP connectivity, which can be

achieved independent of SP networks.
software- Network functions are implemented through software
defined programming, so new functions are added quickly. Huawei
ENP + POF + open APIs implement a software-defined
network.
software- Software-defined networking (SDN) is an approach to
defined networking in which control is decoupled from hardware and
networking given to a software application called a controller.
(SDN)
southbound The interface that is used to connect the lower layer NMS to
interface (SBI) the device and implement the functions of providing services
and performance index data.
station A terminal, such as a laptop or a PC, with a wireless network
interface card (NIC).
storage area A storage area network (SAN) is a dedicated network that
network (SAN) provides access to consolidated, block level data storage.
SANs are primarily used to make storage devices, such as
disk arrays, tape libraries, and optical jukeboxes, accessible to
servers so that the devices appear like locally attached
devices to the operating system. A SAN does not provide file
abstraction, only block-level operations. However, file systems
built on top of SANs do provide file-level access, and are
known as SAN filesystems or shared disk file systems. An
architecture to attach remote computer storage devices such
as disk array controllers, tape libraries and CD arrays to
servers in such a way that to the operating system the
devices appear as locally attached devices.An architecture to
attach remote computer storage devices such as disk array
controllers, tape libraries and CD arrays to servers in such a
way that to the operating system the devices appear as
locally attached devices.
symphony A large orchestral composition consisting of several
movements, usually created for an orchestra. Here refers to
the orchestration service.
storage pool A method for managing storage resources. It virtualizes
bottom-layer storage resources, and automatically allocates
storage spaces based on users' demand. With a storage pool,
users do not need to know the physical position of data.
strict routing A routing mode in which the Request-URI specifies the next
(SR) destination address of a short message. Before delivering a
short message, each SIP Proxy replaces the Request-URI of
the short message with the address specified by the first
route header field, which ensures that the short message
passes by all required SIP Proxies.

iMaster NCE-IP
subnet A type of smaller network that forms a larger network

according to a rule, such as, forming a network according to
different districts. This facilitates the management of a large
network.
subnet mask The subnet mask is a binary pattern that is stored in the
device and is matched with the IP address. A subnet mask is
used by the IP protocol to determine to which network
segment packets are destined. Subnet mask (also known as
netmask or address mask) is a 32-bit binary value used over
the TCP/IP network.
superstratum Core devices that are located within a VPLS full-meshed
provider edge network. The UPE devices that are connected with the SPE
(SPE) devices are similar to the CE devices. The PWs set up
between the UPE devices and the SPE devices serve as the
ACs of the SPE devices. The SPE devices must learn the MAC
addresses of all the sites on UPE side and those of the UPE
interfaces that are connected with the SPE. SPE is sometimes
called NPE.
switchover A policy of selecting proper backup data to start the
policy database. In the Disaster Recovery (DR) system, the Recovery
Point Objective (RPO) or Recovery Time Objective (RTO)
switchover policy can be used.
synchronous A transmission scheme that follows ITU-T G.707, G.708, and
digital G.709. SDH defines the transmission features of digital
hierarchy signals, such as frame structure, multiplexing mode,
(SDH) transmission rate level, and interface code. SDH is an
important part of ISDN and B-ISDN.
system Integration as applied to systems.
integration
T
TCA threshold crossing alert
TCO See total cost of ownership (TCO)
TCP See Transmission Control Protocol (TCP)
TCP/IP Transmission Control Protocol/Internet Protocol
TDM See time division multiplexing (TDM)
TE Metric The TE metric attribute of a link.
TE Tunnel See Traffic Engineered Tunnel (TE Tunnel)
TFTP Trivial File Transfer Protocol
TL1 Transaction Language 1
TLS Transport Layer Security
TMN See telecommunications management network (TMN)

iMaster NCE-IP
TOPO Topology (TOPO) refers to a configuration or layout formed

by the connections between devices on one or more local
area networks (LANs).
TP terminal point
TSDN Transport Software Defined Networking
TTL See time to live (TTL).
TTM See time to market (TTM)
TTS Transparent transmission service, including CBR and VBR
services. TTS services are carried by FG channels through bit
transparent slicing and SDT encapsulation on user-side
boards.
TX transmit
Telnet A standard terminal emulation protocol in the TCP/IP
protocol stack. Telnet allows users to log in to remote
systems and use resources as if they were connected to a
local system. Telnet is defined in RFC 854.
Tenant A property of SmartMulti-Tenant. It represents a virtual
storage system in a physical storage system. The private and
independent logical resource of a tenant mainly includes disk
domain space, LUN, file system, and ports. Tenants receive
complete storage services, but also maintain resource and
network isolation with other tenants, avoiding service
interference.
Third The third generation of digital wireless technology, as defined
Generation by the International Telecommunications Union (ITU). Third
(3G) generation technology is expected to deliver data
transmission speeds between 144 kbit/s and 2 Mbit/s,
compared to the 9.6 kbit/s to 19.2 kbit/s offered by second
generation technology.
Time Time synchronization, also called phase synchronization,
synchronization refers to the consistency of both frequencies and phases
between signals. This means that the phase offset between
signals is always 0.
Traffic A combination of LSPs that is associated with a virtual tunnel
Engineered interface.
Tunnel (TE
Tunnel)
Transmission The protocol within TCP/IP that governs the breakup of data
Control messages into packets to be sent using Internet Protocol (IP),
Protocol (TCP) and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented,
reliable protocol (reliable in the sense of ensuring error-free
delivery), TCP corresponds to the transport layer in the
ISO/OSI reference model.

iMaster NCE-IP
telecommunica A protocol model defined by ITU-T for managing open

tions systems in a communications network. TMN manages the
management planning, provisioning, installation, and OAM of equipment,
network (TMN) networks, and services.
tenant Carriers' customers who purchase network services (such as
site-to-site and site-to-Internet services) from carriers.
time division A multiplexing technology. TDM divides the sampling cycle of
multiplexing a channel into time slots (TSn, n is equal to 0, 1, 2, 3...), and
(TDM) the sampling value codes of multiple signals engross time
slots in a certain order, forming multiple multiplexing digital
signals to be transmitted over one channel.
time to live A specified period of time for best-effort delivery systems to
(TTL) prevent packets from looping endlessly.
time to market The length of time it takes from a product being conceived
(TTM) until its being available for sale.
topology A technique to accurately determine the exact layout of a
discovery network using a few assumptions about the network
architecture and simple tools.
topology view A basic component for the man-machine interface. The
topology view directly displays the networking of a network
as well as the alarm and communication status of each
network element and subnet. The topology view reflects the
basic running conditions of the network.
total cost of Total cost of ownership (TCO) is a financial estimate whose
ownership purpose is to help consumers and enterprise managers
(TCO) determine direct and indirect costs of a product or system. It
is a management accounting concept that can be used in full
cost accounting or even ecological economics where it
includes social costs.
traceroute A program that prints the path to a destination. Traceroute
sends a sequence of datagrams with the time-to-live (TTL)
set to 1,2, and so on, and uses ICMP time exceeded messages
that return to determine routers along the path.
traffic A technology that is used to dynamically monitor the traffic
engineering of the network and the load of the network elements, to
adjust in real time the parameters such as traffic
management parameters, route parameters and resource
restriction parameters, and to optimize the utilization of
network resources. The purpose is to prevent the congestion
caused by unbalanced loads.
U
UNI See User-to-Network Interface (UNI)
UPE user-end provider edge

iMaster NCE-IP
URL See Uniform Resource Locator (URL)

USD Ultimate segment decapsulation (USD), a SID behavior. USD
SIDs are capable of decapsulating IPv6 headers, segment
routing headers (SRHs), and extension headers.
USM user-based security model
UTC See Coordinated Universal Time (UTC)
UUID Universally unique identifier
User-to- The interface between user equipment and private or public
Network network equipment (for example, ATM switches).
Interface (UNI)
Uniform A uniform resource locator (URL) is a reference to a resource
Resource that specifies the location of the resource on a computer
Locator (URL) network and acts as a mechanism for retrieving it. Each file
on the Internet has a unique URL.
user group A group of sub-users who share the same responsibilities.
After a sub-user is added to a user group, it has all of the
permissions that are assigned to the group. User groups help
improve the efficiency of permission management.
user Managing users, including: adding, querying, modifying, and
management deleting users and assigning or canceling user rights
V
VBR Variable bit rate. Different from CBR services, VBR services
support variable bandwidth and are therefore more suitable
for non-real-time transmission scenarios.
VC Virtual Concatenation
VDSL2 See very-high-speed digital subscriber line 2 (VDSL2)
VE virtual Ethernet
VIP very important person
VLAN See virtual local area network (VLAN)
VLL virtual leased line
VM See virtual machine (VM)
VP See virtual path (VP)
VPLS virtual private LAN segment
VPN virtual private network
VPWS See virtual private wire service (VPWS).
VR See virtual reality (VR).
VRF VPN routing and forwarding

iMaster NCE-IP
VRRP See Virtual Router Redundancy Protocol (VRRP)

VXLAN Virtual Extensible LAN
Virtual Router A protocol designed for multicast or broadcast LANs such as
Redundancy an Ethernet. A group of routers (including an active router
Protocol and several backup routers) in a LAN is regarded as a virtual
(VRRP) router, which is called a backup group. The virtual router has
its own IP address. The host in the network communicates
with other networks through this virtual router. If the active
router in the backup group fails, one of the backup routers in
this backup group becomes active and provides routing
service for the host in the network.
VoIP voice over IP
vCPU virtualized CPU
very-high-speed An extension of the VDSL technology, which complies with
digital ITU G.993.2, supports multiple spectrum profiles and
subscriber line encapsulation modes, and provides short-distance and high-
2 (VDSL2) speed access solutions to the next-generation FTTx access
service.
virtual NE An object similar to a common NE and is also displayed with
an icon on a view. A virtual NE, however, is only an NE
simulated according to the practical situation, which does not
represent an actual NE. Therefore, the actual status of this
NE cannot be queried and its alarm status cannot be
displayed with colors. Usually, a virtual NE provides the trail
management function for the NEs or subnetworks that
cannot be managed, or provides the end-to-end service
configuration method and the trail management capability
when the equipment is interconnected with third-party NEs.
virtual local A logical grouping of two or more nodes which are not
area network necessarily on the same physical network segment but which
(VLAN) share the same IP network number. This is often associated
with switched Ethernet.
virtual machine A special type of software in computer science, which creates
(VM) an environment between the computer platform and end
users. Based on the environment created by the software,
end users can perform operations on the software.
virtual path A bundle of virtual channels, all of which are switched
(VP) transparently across an ATM network based on a common
VPI.
virtual private A technology that bears Layer 2 services. VPWS emulates
wire service services such as ATM, FR, Ethernet, low-speed TDM circuit,
(VPWS) and SONET/SDH in a PSN.
virtual reality The computer simulates a 3D environment. The user usually
(VR) performs operations using only a pair of glasses and gloves.

iMaster NCE-IP
voice over IP An IP telephony term for a set of facilities used to manage

(VoIP) the delivery of voice information over the Internet. VoIP
involves sending voice information in a digital form in
discrete packets rather than by using the traditional circuit-
committed protocols
W
WAN wide area network
WDM Wavelength Division Multiplexing
Wi-Fi See Wireless Fidelity (Wi-Fi).
Wireless A short-distant wireless transmission technology. It enables
Fidelity (Wi-Fi) wireless access to the Internet within a range of hundreds of
feet wide.
what-if analysis What-If analysis is a simulation analysis and evaluation
method. It models and analyzes the outcome on the
assumption that different policies and solutions are used to
help you make optimal decisions. In the network simulation
analysis field, what-if analysis simulates possible network
changes (such as device/link faults and traffic changes) and
analyzes the impact of these changes on services to help
O&M personnel understand the impact scope and work out
necessary solutions to improve service reliability.
whitelist A list or register of items that, for one reason or another, are
being provided a particular privilege, service, mobility, access
or recognition.
X
XML NBI Extensible Markup Language northbound interface
xDSL x digital subscriber line
Y
Y.1731 The OAM protocol introduced by the ITU-T. Besides the
contents defined by IEEE802.1ag, ITU-T Recommendation Y.
173 also defines the following combined OAM messages:
Alarm Indication Signal (AIS), Remote Defect Indication
(RDI), Locked Signal (LCK), Test Signal, Automatic Protection
Switching (APS), Maintenance Communication Channel
(MCC), Experimental (EXP), and Vendor Specific (VSP) for
fault management and performance monitoring, such as
frame loss measurement (LM), and delay measurement
(DM).
YANG See Yet Another Next Generation (YANG).
YANG NE NE managed using a NETCONF YANG model.

iMaster NCE-IP
Yet Another A data modeling language used to define data sent over
Next NETCONF. YANG can be used to model both NEs'
Generation configuration and state data.
(YANG)
Z
ZTP Zero Touch Provisioning

Imaster NCE-IP V100R022C10 Product Description (x86) 03-E

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-IP V100R022C10 Product Description (x86) 03-E

Uploaded by

Copyright:

Available Formats

iMaster NCE-IP

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. i

About This Document

Indicates a hazard with a high level of risk which, if not

Indicates a hazard with a medium level of risk which, if not

Indicates a hazard with a low level of risk which, if not

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. ii

Indicates a potentially hazardous situation which, if not

Supplements the important information in the main text.

GUI Element Reference Conventions

Boldface Buttons, menus, parameters, tabs, windows, and dialog

> Multi-level menus are in boldface and separated by the ">"

Boldface Command keywords are in boldface.

Italic Command arguments are in Italic.

[] Items (keywords or arguments) in brackets ([ ]) are

{x | y |...} Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... } * Optional items are grouped in braces and separated by

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. iii

[ x | y | ... ] * Optional items are grouped in brackets and separated by

03 2023-08-15 This issue is the third official release.

02 2023-04-15 This issue is the second official release.

01 2023-01-10 This issue is the first official release.

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. iv

About This Document................................................................................................................ ii

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. v

6.4 Server Software Configurations....................................................................................................................................... 51

7 Functions and Features........................................................................................................ 58

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. vi

7.5.1.2.1 Introduction to Performance Overview............................................................................................................ 136

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. vii

7.7.1 Open API & Tool.............................................................................................................................................................. 247

8 Usage Scenarios ..................................................................................................................249

11 Personal Data and Privacy Protection......................................................................... 280

13 Version Requirements...................................................................................................... 383

A Standards Compliance....................................................................................................... 659

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. viii

Trends and Challenges

● Increasingly complex networks: A large number of sites need to be built or

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 1

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 2

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 3

NCE-IP leverages the intelligent cloud-map algorithm to associate network

2.1 Network Digital Map

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 4

2.2 Network Open Programmability Platform (AOC)

2.3 Incident View

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 5

2.4 Energy View

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 6

Table 3-1 New features of NCE-IP

Network Enhan Offer security or physical isolation for power differential

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 7

Function/ Type Description

Network Enhan BSID as a service enables cross-domain connections and

DR Enhan No DR site needs to be deployed, reducing deployment

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 8

4.1 Solution Architecture

4.1 Solution Architecture

Issue 03 (2023-08-15) Copyright © Huawei Technologies Co., Ltd. 9