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

Reminder

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

upgrade

eSight V300R009C00 Operation Guide 10

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

FAQs

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

Question

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

Answer

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

Question

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

Answer

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

Question

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?

Answer

  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

Question

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

Answer

To rectify the exception, perform the following operations:

  1. Open the eSight upgrade processing switch.

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

    SyncFlag=1
  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\oms.pm, open the snycDevice.cfg file, and set SyncFlag to 0, as shown in the following:

    SyncFlag=0
  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

Question

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

Answer

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

Answer

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

Answer

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

Answer

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.

    Command:

    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

Answer

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 Ensure that WLAN Location Environment Meets Requirements

Question

How do I ensure that WLAN location environment meets requirements?

Answer

  1. Verify that all prerequisites for WLAN location are met.

    1. Ensure that you have installed the WLAN location component and purchased and imported the related license.

      Log in to eSight, Choose System > System Management > License Management from the main menu, and check whether the license function items and resource items of the WLAN location component meet requirements.

      • The names of function control items are WLAN Wireless Location Function and WLAN RTLS Data API, and they are in Yes state.
      • The name of the resource control item is Managed WLAN Wireless Location AP, and the number of remaining licenses should be equal to or larger than the number of APs on which WLAN location needs to be enabled.
    2. Ensure that the AC version exactly matches the AP version, and both the AC and AP support WLAN location.
      • The AC version must exactly match the AP version.
      • The WLAN location function applies only to APs and ACs running V200R003 and later versions.
      • Fat APs do not support WLAN location.
    3. Ensure that the network between the AC/AP and location engine is connected.
      • If the AC reports location packets, ensure that the network between the AC and location engine is connected.
        NOTE:

        If the AC has multiple IP addresses, ensure that the AC can communicate with the location engine through the IP address added to eSight.

      • If the AP reports location packets, ensure that the network between the AP and location engine is connected.
        NOTE:
        • If the location engine and eSight are deployed in integrated mode, the IP address of the location engine is the same as the IP address of the eSight server.
        • If the location engine and eSight are deployed in distributed mode, the IP address of the location engine is the IP address of the server where location engine is installed.
    4. Region topology design has been completed. For details on how to design the region topology, see Designing the Region Topology.
      • You have imported the background image to the region.
        NOTE:

        The resolution of the uploaded image (width x height x bit depth/8/1024/1024) is no more than 100M, and the image size is no more than 6 MB.

      • You have set the map scale for the region.
      • The background diagram should be the layout drawing of the building, with accurate scales and locations of walls, rooms, and obstacles. If the site layout drawing is unavailable, you need to measure the objects in the building at the site and draw a map.
      • The layout drawing should show only the building itself, without white or black margins. If the layout drawing contains redundant areas that should not be located, add rectangle obstacles in such areas to restrict the location results within the building.
    5. Ensure that APs are properly deployed. For details about how to add APs, see Adding Devices to the Topology.
      • APs are deployed at a distance of 8 to 12 meters.
      • APs are deployed using the recommended deployment mode.

    6. When the location engine is deployed in distributed mode, ensure that the time and time zone of the eSight server are the same as those of the location engine server.

  2. Optional: Use Location Planner to complete environment information collection.

    1. Obtain Location Planner.

      Copy all the content in eSight installation directory\AppBase\tools\Tools of the eSight server to a local computer.

      NOTE:

      JDK 1.7 or later must be installed on the local PC and Java environment variables are configured after the installation. Otherwise, the location tool cannot be used.

    2. Optional: Set the login whitelist verification function.

      The login whitelist verification function is disabled on eSight by default. To enable the login whitelist verification function, perform the following operations:

      1. Enable the login whitelist verification function.

        Open the ros_config_esight.xml file in eSight installation directory\AppBase\etc\oms.ros of the eSight server, and set roa.server.ip.white.list.enable to true.

      2. Set the whitelist.

        Open the ip-white-list-roaintegrated.properties file in eSight installation directory\AppBase\etc\iemp.framework\ip.white.list of the eSight server, and add the IP address of the computer allowed to use Location Planner to the file.

        NOTE:

        The whitelist is in the IP address@jetty.roaintegrated format. For example, if you add 10.137.59.16@jetty.roaintegrated to the file, you can use Location Planner on the computer with the IP address 10.137.59.16.

      3. Restart eSight to make the login whitelist verification function take effect.
    3. Log in to Location Planner.

      Click start.bat/sh in Directory where Location Planner is saved locally\bin to start Location Planner, and set related parameters.

      • Server IP address indicates the IP address of the eSight server.
      • User name and Password indicate the user name and password used to log in to eSight.

    4. Use Location Planner.

      After successful login, the Location Planner home page is displayed.

    • Set AP's location region.

      Click Set Regions with Strongest AP Signal, right-click an AP in the region topology, and select Set Location Range to set the locations where users associated with the AP may appear.

      NOTE:

      Double-click the region topology to complete the region drawing.

    • Set coverage holes.

      Click Set Coverage Holes, right-click any location in the region topology, and select Set Coverage Range to set the locations where users will not appear.

      NOTE:

      Double-click the region topology to complete the region drawing.

Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 310399

Downloads: 633

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