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).


Why 23 APs Are Displayed on the AC But Only 10 APs Are Displayed in the NMS


Why 23 APs are displayed on the AC but only 10 APs are displayed in the NMS?


Ensure that whether the number of managed APs is set on the License Management page. The setting of the number of managed APs determines the number of APs created by the WLAN Manager component.

Why No Error Message Is Displayed on eSight


When I encounter a task failure on eSight, no error message is displayed? Why?


If the NMS and managed device are Huawei devices, error codes are extended and more scenarios are defined after the function of sending extended error codes is enabled. As a result, users are enabled to locate and troubleshoot faults quickly and accurately.

Support of the MIB for the extended error code:

  • For the MIB that supports the extended error code, you can enable the SNMP extended error code function and use Huawei NMS to provide the NM station with various error codes.
  • For the MIB that does not support the extended error code, after the SNMP extended error code function is enabled, NM stations of either Huawei or other vendors can obtain only the standard error code.

Enable the function of sending extended error codes to the NM station on the device:

<Quidway> system-view 
[Quidway] snmp-agent extend error-code enable

Why Are the User Numbers Different on eSight and the Device


When I run the display access-user command to check the user number on the device, the user number is different from the user number I query on the WLAN management page. Why?


  1. On the User page of the WLAN management page, the user number is the number of wireless users, including authorized users and associated but unauthorized users.

    The user number obtained by running the display access-user command is the number of users that passed AAA authentication, including wired and wireless users. Meanwhile, wireless users contain only authorized users, excluding associated but unauthorized users.

    Therefore, the user numbers on eSight and the device are different when wired users or associated but unauthorized users exist on devices.

  2. Only after data on the device is synchronized to eSight, the user numbers on eSight and the device is the same. eSight supports instant and periodic synchronization. If the data is not synchronized to eSight, the user number on eSight is not the latest data. The user number obtained by running the display access-user command is the latest data. Therefore, the timeliness of user data also results in the difference of user numbers on eSight and the device.

What Do I Do When a CPU or Memory Collection Exception Occurs After AC6600 Upgrade


What do I do when a CPU or memory collection exception occurs after AC6600 upgrade from V200R200C00 to V200R300C00?


To rectify the exception, perform the following operations:

  1. Open the eSight upgrade processing switch.

    Access eSight\AppBase\etc\, open the snycDevice.cfg file, and set SyncFlag to 1, as shown in the following:

  2. Choose Resource > Network > Equipment > Network Device from the main menu. Select the AC6600 to upgrade to V200R300C00 from V200R200C00.
  3. Click Synchronize.
  4. Close the eSight upgrade processing switch.

    Access eSight\AppBase\etc\, open the snycDevice.cfg file, and set SyncFlag to 0, as shown in the following:

  5. On eSight, access the performance task management page, delete the original custom performance task, and create a custom performance task.

What Can I Do When the AC Fails to Collect Performance Data of APs


What can I do when the AC fails to collect performance data of APs?


The AC fails to collect performance data of APs because the APs are in offline state. Collect performance data of these APs after they go online.

After an AC Is Added to eSight, Can eSight Automatically Discover APs That Go Online from the AC


After an AC is added to eSight, eSight will automatically synchronize data including information of associated APs from the AC, even if there are no reachable routes between the APs and eSight.

After an AP Goes Offline and then Online, the AP and Links Connected to the AP Are Displayed in Grey in the Topology View. Why


This problem occurs because the alarm configuration on the AC is incorrect. eSight does not receive alarms reported by the AP; therefore, the AP status is not updated.

Run the snmp-agent trap source interface-type interface-number command on the AC to solve the problem.

Set the interface-type interface-number parameter to the AC's interface the IP address of which is added to eSight.

After an AC Is Added to eSight, eSight Fails to Discover Associated APs. Why


There are several causes for this problem.

  • The write community is not configured for the AC.

    Check whether a write community is configured for the AC. If not, configure a write community and synchronize it to eSight.

  • The SFTP channel between the AC and eSight is unreachable.

    Run the sftp eSight Server IP 31922 command on the AC to check whether the SFTP channel between the AC and eSight is reachable.

    If the firewall of the eSight server blocks the SFTP service of port 31922, the SFTP channel between the AC and eSight is unreachable.

  • The SSH client first authentication function is disabled.

    Run the ssh client first-time enable command on the AC to enable the SSH client first authentication function.

  • Check whether the VPN tunnel between eSight and the device is correctly configured.

    Set the VPN instance between the device and eSight to management VPN.


    set net-manager vpn-instance name (VPN instance between eSight and a device)

  • If devices are added before the WLAN component is installed, you need to delete the devices and add them to eSight again.
  • APs in·standby state are not displayed on eSight and require no licenses.
  • The AC cannot be added to eSight through NAT mapping. In such a network, APs cannot be discovered.
  • The number of APs managed by the WLAN device is limited on the license management page.

WLAN Top N Region Statistics and Top N SSID Statistics Are Different. Why


The two performance tasks use different collection intervals. To solve the problem, set the collection interval of the two tasks to the same value.

How Do I Calculate the Interface Traffic Usage of Top N APs


How is the interface traffic usage of top N APs calculated?


Calculate the AP interface traffic usage as follows: AP interface traffic usage = Actual AP interface traffic collected on the performance interface/AP interface bandwidth

The conversion relationships between traffic units are as follows:

1 KB = 1024 B

1 MB = 1024 KB

1 GB = 1024 MB

1 TB = 1024 GB


AP interface performance data is not collected. As a result, the interface traffic usage trend of top N APs is empty. You are advised to check whether the AP interface collection task is created.

How Can I Solve the Problem If AC Synchronization Fails and the Following Message Is Displayed: ssh connection failed ... may not configured command:ssh client first-time enable


This problem occurs because the IP address of the eSight server is a LAN IP address. Synchronization using FTP is not supported when an NAT device is deployed between the eSight server and the device you want to access.

What Is the Data Source of the WLAN Online User Statistics Portal in Region Monitor


The WLAN online user statistics Portal uses the Number of currently associated mobile terminals counter in the corresponding AP performance collection task as the data source. Data of different granularities is used based on the time dimension.

  • When the time dimension is 2 hours and day, the original performance data is used.
  • When the time dimension is month, the aggregated data of 6 hours is used.
  • When the time dimension is year, the aggregated data of one day is used.

Why Polling Fails After WLAN Devices Are Rolled Back from V200R006 to V200R005


WLAN V200R005 and earlier versions use a different device model than that used in V200R006 and later versions. Therefore, incompatibility will occur after rollback from WLAN V200R006 or later to V200R005 or earlier.

How Do I Solve the Problem that the Device CPU Usage Is High Because SNMP Synchronization Is Configured for the WLAN


How do I solve the problem that the device CPU usage is high because SNMP synchronization is configured for the WLAN?


  • You are advised to upgrade the version to V300R007C00SPC307 or later.
  • If the problem persists after the upgrade, perform the following operations:
    • Workaround on eSight:
      1. Choose System > System Settings > Southbound Devices from the main menu.

      2. Choose Network Equipment Poll Setting from the navigation tree on the left, deselect WLAN Inventory Information Polling Interval, and click Apply.

        After the operation is performed, the WLAN configurations, blacklist and whitelist, WIDS, and mesh information are not synchronized anymore. Therefore, you need to evaluate whether users are concerned about and use related services.

    • Workaround on the device:

      Traffic limiting needs to be configured on the device, which does not affect eSight functions.

      1. Configure the SNMP packet limiting on the device. The default value is 128pps.
        • system-view
        • cpu-defend policy snmplimitpolicy
        • packet-type snmp rate-limit 96 wired
        • quit
      2. Configure the SNMP packet limiting on the device.
        • system-view
        • cpu-defend policy snmp-defend
        • car packet-type snmp cir 12
        • y
Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 73053

Downloads: 383

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