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).
Network Device Basic Management Introduction

Network Device Basic Management Introduction

This section describes the definition, functions, application restrictions, and key indicators of network device addition, IP topology management, VLAN management, MIB management, and AR management.


  • Adding network devices

    Add devices to eSight.

  • IP topology management
    • eSight provides the IP topology management function. By dividing subnets by device network segment, eSight can monitor IP addresses of network devices.
    • Data in the eSight IP topology is synchronized from the devices. You cannot add or delete elements in the topology view.
  • VLAN management

    eSight allows users to view and manage VLANs, including network-wide VLAN management, device VLAN management, and VLAN topology management.

  • MIB management

    Management Information Base (MIB) management is a tool for managing MIBs. It displays MIB nodes in a tree structure, which facilitates the browsing of MIB nodes. In addition, it supports common operations on device MIBs, including the Get, GetNext, Walk, TableView, and Stop operations and operations for compiling and loading MIB files.

  • AR management

    Through eSight AR wireless interface management, you can manage the wireless interfaces of AR devices in a unified manner. For example, you can synchronize the AR wireless interface information to eSight and export the AR wireless interface information.


  • Adding network devices

    Three methods are available for adding devices to eSight.

    Single addition

    One device is added at a time. This method applies when you want to add one or a few devices to eSight during normal network running.

    Automatic discovery

    Devices in one or more network segments are added at a time. This method applies when devices are distributed in one or multiple network segments and devices in the same network segment have the same SNMP parameter settings.

    Batch import

    Multiple devices with different IP addresses are added at a time through an Excel file. This method applies in new site deployment scenarios where devices are dispersed in multiple network segments.

  • IP topology management

    You can use the IP topology to monitor IP addresses of network devices added to eSight in real time.

  • VLAN management

    After completing network planning based on the site requirements, you can create subnets or groups on eSight and add network devices to the subnets or groups through SNMP, facilitating unified device management and maintenance.





    Set protocol parameters on the device: SNMP

    SNMP parameters are used to add devices to eSight.


    Add devices to eSight.

    Select a proper device addition mode based on the site requirements.


    Create a VLAN.

    Create a VLAN and apply it to multiple devices.


    Create VLANs in batches.

    Create VLANs in batches and apply them to multiple devices.


    Configure port VLANs in batches.

    Modify the VLAN type and VLAN attributes of ports for one or multiple devices in batches.


    Create device VLANs.

    Create VLANs for a single device and view all VLANs of the device as well as the list of ports on which the VLANs are configured.


    Configure port VLANs.

    Modify the VLAN type and VLAN attributes of one or multiple ports in batches for a single device.


    Create VLANIF interfaces.

    Create VLANIF interfaces for a single device.


    Configure the voice VLAN.

    Configure the voice VLAN for a single device.


    Manage VLANs in the topology.

    VLANs on the entire network and involved devices and links are uniformly displayed in a topology view. You can view and modify network-wide VLANs in the topology view.

  • MIB management
    • MIB compilation

      You can select a MIB file to compile. After the compilation is complete, you can select a directory for saving the result file. The compilation result of the MIB file is displayed on the compilation result page.

    • MIB loading

      MIB node management allows users to upload, compile, load, uninstall, and delete MIB nodes and create file directories.

    • MIB operation

      After entering a device IP address in the device IP address box, you can use the SNMP device. After the device is connected, you can use tools to perform the operations such as Get, GetNext, Walk, and TableView on the device. To abort the operation, you can click Stop to stop obtaining data.

  • AR management

    To ensure information consistency between eSight and AR routers, you can synchronize cellular interface information about AR routers to eSight in manual or periodic synchronization mode.

    • Manual synchronization: If interface information about AR routers changes, you can manually synchronize the information to eSight immediately.
    • Periodic synchronization: You can configure polling parameters for cellular interfaces of AR routers, so that eSight periodically queries and obtains changed interface information from the AR routers.

Application Restrictions

  • Adding network devices
    • To ensure the page response efficiency, you need to manually specify the number of interfaces in an interface group. It is recommended that the number be fewer than 300,000.
    • When initiating an SNMP operation to a device, eSight uses a queue to store request tasks of the device. To ensure the protocol stack response efficiency, the task queue size is restricted. If the number of concurrent requests submitted by an application to a device exceeds the maximum of the task queue, the SNMP operation fails. The typical symptom is that performance indicators fail to be collected when a large number of performance collection tasks exist. The maximum number of tasks in the task queue is configured in the configuration file eSight installation directory/AppBase/etc/snmp/snmp.xml. If max-req-per-q-config is set to 1, the maximum number equals the value of max-req-per-q. If max-req-per-q-config is set to 0, the maximum number is determined based on the maximum number of CPU cores of the eSight server (Table 12-1). The default value of max-req-per-q-config is 0.
      Table 12-1 Relationship between the maximum number of task queues on a device and the number of CPU cores

      Number of eSight Server CPU Cores

      Maximum Number of Tasks in a Single-Device Task Queue

      8 cores or less


      9 to 16 cores


      17 cores or more


    • For the link discovery function, the LLDP and CDP link discovery algorithms are always enabled and cannot be configured. The SBS link discovery algorithm is enabled by default and is configurable. The discovery algorithms of the non-30-bit mask IP links and MAC links are disabled by default and is configurable.
  • IP topology management

    The IP topology does not support IPv6 addresses.

  • VLAN management
    • The VLAN management menu is unavailable in the NE Explorer for some devices.
    • The VLANIF menu on the NE Explorer does not support IPv6 addresses.
  • MIB management

    MIB management does not support the IPv6 address format.

  • AR management




Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 71275

Downloads: 378

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