No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


eSight V300R010C00SPC200, 300, and 500 Operation Guide 09

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
eLTE eSE Management

eLTE eSE Management

This topic describes the definition, benefits, application scenarios, functions, principles, application restrictions, availability, and key indicators of eLTE eSE management.


The capability of managing the service engines in a unified manner is provided, implementing convergent management for wired and wireless networks.


Device Access

eSight allows users to add a single device, and manage the eSE connection status and management status in the topology or on the device overview page.

Device Management

  • Alarm Management

    For eLTE eSEs, eSight supports all the alarm management functions mentioned. eSight supports manual and automatic synchronization of current alarms, and allows users to clear specific current alarms.

  • Performance Management

    By default, eSight offers key, major, and minor performance indicator templates. After devices are connected to eSight, collection tasks about KPIs are automatically added to collect performance data about network-wide devices.

  • Topology Management

    All features are supported. Virtual connections between base stations and service engine devices are displayed in the physical topology view. In the topology view, NE connection status and alarm status are updated in real time. Right-click of an NE on the shortcut menu in the topology view, you can browse alarms, NE details, service channels, and MML commands. Users can manually create radio links between devices in the topology view and display them in the topology view. In addition, users can monitor the link status to learn about the network topology and monitor network changes.

  • NE Manager

    The NE manager allows users to check current and historical alarms about devices. Configuration resource information about devices can be viewed, excluding eCNS610.

Configuration Deployment

  • MML Command

    The MML Command allows users to deliver MML commands to NEs of the same type and version on eSight. The MML Client offers a function-specific command navigation tree, allows users to filter, search for, and sort NEs, supports MML command association and online help, and records executed historical commands. Before executing a command that may have severe negative effects, the MML CLI informs users of possible execution results and executes the command only after the users confirm the operation.

    eSight displays command execution results in real time.

  • MML Script

    eSight delivers MML scripts to multiple devices in batches. MML scripts contain MML commands and are used to perform service deployment for devices in batches. Users can manage script delivery tasks and view script execution reports to learn detailed results of each command executed on each device.

  • Configuration Data Synchronization

    To ensure configuration data consistency between eSight and NEs, eSight supports automatic data synchronization after an NE configuration change and manual data synchronization. Users can check synchronization task progresses on the synchronization task management page, and use the NE manager to check common configuration parameters synchronized to eSight.

Application Restrictions

This feature has no special restriction.

Key Parameters

  • When deployed on a standard-configuration server, eSight can manage a maximum of 50 service engines.
  • When deployed on a high-configuration server, eSight can manage a maximum of 200 service engines.
    • Standard-configuration server: 12-core 2 GHz CPU, 32 GB memory, and 500 GB hard disk.
    • High-configuration server: 40-core 2 GHz CPU, 64 GB memory, and 1 TB hard disk.
Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 84511

Downloads: 405

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next