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

Troubleshooting

SFTP Synchronization Failed

Symptom

After the AC is synchronized, the following information is displayed in the result list: ESS Profile failed to synchronize the features. Invalid SFTP server address. Delete one or more users and try again.

Common Causes

  • The ssh client first-time function is not enabled.
  • The SFTP authentication list for the device is full. You need to delete the unused IP addresses of the SFTP server.

Procedure

  1. Check whether the SFTP service is normal on eSight.

    FTP and TFTP may have potential security risks. Exercise caution when you use them. SFTP that is more secure than FTP and TFTP is recommended.

    • In the Windows scenario:
      1. Log in to the eSight server as the Administrator user.
      2. Check whether the value of enable corresponding to the SFTP protocol in the D:\eSight\AppBase\sysagent\etc\sysconf\svcbase\med_node_1_svc.xml file is true.
        NOTE:

        In the file name, D:\eSight must be changed to the actual installation directory.

        <config name="sftp">  
        <param name="enable">true</param> 
        </config>
        • If the parameter value is true, the SFTP server is normal.
        • If the parameter value is false, configure the SFTP server status by referring to Configuring the eSight File Transfer Protocol in the Maintenance Guide.
    • In the Linux scenario:
      1. Log in to the eSight server as the root user.
      2. Check whether the value of enable corresponding to the SFTP protocol in the /opt/eSight/AppBase/sysagent/etc/sysconf/svcbase/med_node_1_svc.xml file is true.
        NOTE:

        In the file name, /opt/eSight must be changed to the actual installation directory.

        <config name="sftp">  
        <param name="enable">true</param> 
        </config>
        • If the parameter value is true, the SFTP server is normal.
        • If the parameter value is false, configure the SFTP server status by referring to Configuring the eSight File Transfer Protocol in the Maintenance Guide.

  2. Run the display this command in the system-view view to check whether the ssh client first-time function is enabled.

    • If ssh client first-time enable is displayed, go to Step 3.
    • If ssh client first-time enable is not displayed, run the ssh client first-time enable command and perform synchronization again.
      • If the synchronization succeeds, the fault is rectified.
      • If the synchronization failed, go to Step 3.

  3. Run the following commands in the system-view view.

    display rsa peer-public-key brief  
    undo ssh client server IP assign rsa-key       //server IP indicates the SFTP server IP address to be deleted. 
    undo rsa peer-public-key server IP

    Perform synchronization again.

    • If the synchronization succeeds, the fault is rectified.
    • If the synchronization failed, contact technical support personnel.

  4. If the fault still persists, collect the following log files and contact technical support personnel.

    eSight installation directory \AppBase\var\iemp\log\enterprise\synchronization\sync_sftp.log

    eSight installation directory\AppBase\var\iemp\log\enterprise\synchronization\synchronization.log

WLAN Location Result Cannot Be Displayed

Common Causes

  1. The WLAN location component is not installed, or no license is imported for the WLAN location component.
  2. The AC version does not match the AP version, or the AC/AP does not support WLAN location.
  3. The network between the AC/AP and eSight is disconnected.
  4. No region background image is imported, or the scale is not set.
  5. The AP deployment is improper.
  6. When the location engine is deployed in distributed mode, the time or time zone of the eSight server differs from that of the location engine server.
  7. The AP's radio parameters are incorrect.
  8. The AC's location template parameters are incorrect.
  9. The switch does not deliver the configuration to the specified AP. In the embedded AC scenario, for switch V200R010 or earlier versions, after the user enables the network positioning function on eSight, the user needs to manually execute the commit command on the switch to deliver the configuration to the specified AP.

Procedure

  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, accurate to the B 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.

    • You have imported the background image to the region.
    • 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 the AP deployment is proper.

    • APs are deployed at a distance of 12 to 20 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.
  7. Modify radio configuration on location APs.

    1. Choose Resource > Network > Equipment > Network Device from the main menu.
    2. Click the AC that manages a location AP to display the AC manager.
    3. Choose WLAN Feature > Profile Management from the navigation tree.
    4. Create an air scan profile, and set Scan Interval to 1000 and Scan Period to 100 in the profile.

      If services are affected after Scan Interval is set to 1000, increase the interval gradually (with a recommended increment of 500 each time), until services are not affected.

    5. Create a radio profile and reference the air scan profile you have created.

      Create 2G and 5G radio profiles based on the site requirements.

    6. Deliver the new radio profile to the location APs. For details, see Configuring the WLAN Service.

  8. Modify the WLAN location profile on the AC.

    1. Choose Resource > Network > Equipment > Network Device from the main menu.
    2. Click the AC that manages a location AP to display the AC manager.
    3. Choose WLAN Feature > Profile Management from the navigation tree.
    4. Modify the WLAN location profile and apply to the AC again.

      Select the eSightLocation profile, click , and change Data Report Frequency to 2000.

      • If the location engine of eSight is used, set Server IP Address to the IP address of the eSight server and Server Port to 32180.
      • If another engine server is used, obtain the IP address and port number of the server from the server administrator and set Server IP Address and Server Port accordingly.
      NOTE:
      • If Data Report Frequency(ms) is set to AP Report Server, do not set Source IP address of outgoing packets.
      • If Data Report Frequency(ms) is set to AC Report Server, set Source IP address of outgoing packets to the IP address of an AC.

      If services are affected after Data Report Frequency is set to 2000, increase the interval gradually (with a recommended increment of 500 each time), until services are not affected.

  9. In the embedded AC scenario, for switch V200R010 or earlier versions, after the user enables the network positioning function on eSight, the user needs to manually execute the commit command on the switch to deliver the configuration to the specified AP.

    [S12712]wlan 
    [S12712-wlan-view]commit ap-id 0 
    Warning: Committing configuration may cause service interruption, continue?[Y/N]:Y 
    [S12712-wlan-view]

Why No Data Is Displayed on the AP Spectrum Chart

Symptom

Why no data is displayed on the AP spectrum chart?

Possible Causes

If the spectrum analysis parameters are set incorrectly on devices, the devices fail to send spectrum packets to the eSight server.

Procedure

  • Run the following commands on an AC of an earlier version than V2R6C00.
    1. Run the system-view command on the AC to enter the system view.
    2. Run the wlan command to enter the WLAN view.
    3. Run the spectrum-analysis ap-report-server ac port port-num command to specify the AC as the spectrum analysis server.
    4. Run the spectrum-analysis spectrogram-server ip-address ip-address port port-num command to specify the eSight server IP address to which spectrum packets are sent and the number of the port that receives spectrum packets from APs. The port number is 32181.
    5. Run the ap ap-id radio radio-id command to enter the radio view.
    6. Run the spectrum-analysis enable command to enable spectrum analysis for the APs.
    7. Run the spectrum-analysis spectrogram-server-report enable.
    8. Run the commit { all | ap ap-id } command to deliver the configurations to APs.
  • Run the following commands on an AC of V2R6C00 version.
    1. Run the system-view command on the AC to enter the system view.
    2. Run the wlan command to enter the WLAN view.
    3. Run the spectrum-profile name profile-name command to create a spectrum analysis profile.
    4. Run the spectrum-server ip-address ip-address port-num 32181 via-ac ac-port ac-port command to specify the eSight server IP address to which spectrum packets are sent and the number of the port that receives spectrum packets (UDP packets) from APs.
    5. Return to the WLAN view and run the ap-group name group-name and spectrum-profile profile-name radio radio-id commands to configure an AP group and bind the profile to the AP group.
    6. Return to the WLAN view and run the spectrum-report ap-name ap-name radio radio-id command to enable spectrum analysis for the APs.
  • Run the following commands on an AC of V2R6C10 or a later version.
    1. Run the system-view command on the AC to enter the system view.
    2. Run the wlan command to enter the WLAN view.
    3. Run the ap-system-profile name profile-name command to create an AP system profile and enter the profile view.
    4. Run the spectrum-analysis server ip-address ip-address port 32181 via-ac ac-port ac-port command to specify the eSight server IP address to which spectrum packets are sent and the number of the port that receives spectrum packets (UDP packets) from APs.
    5. Return to the WLAN view and run the ap-group name group-name and ap-system-profile profile-name command to bind the specified AP system profile to an AP group.
    6. Run the radio radio ID and spectrum-analysis enable commands to enter the radio view of the AP group and enable the spectrum analysis function on the specified radio.
    7. Return to the WLAN view and run the spectrum-report ap-name ap-name radio radio-id command to enable spectrum analysis for the APs.

WLAN Performance Collection Exception

Symptom

An exception occurs when I collect performance data about wireless devices (ACs and APs) on eSight.

Possible Causes

  • eSight and devices are disconnected because SNMP parameter are set incorrectly or tampered.
  • When eSight collects performance data about a lot of devices (for example, 1000 APs) and there are many WLAN counters, an exception may occur.
  • When multiple network adapters are deployed on the eSight server and the incorrect network adapter is selected during eSight installation, an exception may occur.
  • A fault occurred on devices.

Procedure

  • If the exception occurred due to incorrect SNMP parameter settings, perform the following operations:
    1. Run the ping command to check the network connection between eSight and devices.
    2. If the network connection is normal, verify SNMP parameter settings.
  • If the exception occurred because eSight needed to collect performance data about a lot of devices (for example, 1000 APs) and there were many WLAN counters, it is recommended that you:
    • Do not customize performance counters or create new performance tasks.
    • Do not shorten the default eSight collection interval.
  • If the exception occurred because an incorrect network adapter was selected during eSight installation, use the IP Address Tool to select the network adapter again.
  • If the exception occurred because a fault had occurred on devices, see the troubleshooting manual of the devices.

After a Laptop Running the Windows 7 Operating System Goes Online Through the WLAN, the Obtained IP Address Cannot Be Displayed on eSight

Symptom

After a laptop running the Windows 7 operating system goes online through the WLAN, it obtains an IP Address the same as the address obtained when it goes online last time. eSight displays only the MAC address but not the IP address of the laptop.

After a user enters the ipconfig or renew command in the CLI on the laptop, the IP address of the laptop is displayed on eSight.

Possible Causes

When the Windows 7 operating system uses the same IP address as that used during the last login, it does not send gratuitous ARP packets. Therefore, the DHCP server cannot obtain the IP address of the laptop.

Procedure

  1. On the DHCP server, run the following commands in the system view.

    dhcp server database enable 
    dhcp server database write-delay 36000 
    dhcp server database recover

Abnormal Status of ACs and APs in Performance Management on eSight

Description

After WLAN Manager is installed, the status of ACs and APs is abnormal in Performance Management where real-time performance and KPIs of ACs and APs are monitored. Based on statistics collected, the AP data caching function is not enabled on ACs whose status is abnormal. To solve this problem, you need to enable the AP data caching function on the ACs by running the ap-collect-time command.

Issue Description

After WLAN Manager is installed, the status of ACs and APs is abnormal in Performance Management where real-time performance and KPIs of ACs and APs are monitored.

Handling Process

Based on statistics collected, the AP data caching function is not enabled on ACs whose status is abnormal. To solve this problem, run the ap-collect-time (15 minutes by default) command in the WLAN view on the ACs to enable the AP data caching function. The command takes effect in half an hour after being delivered to the ACs.

Root Cause

eSight needs to periodically obtain performance statistics data (including AP and radio performance statistics and information about users on an AP) from an AC that obtains the data from the AP. If the links between the ACs and APs are faulty, eSight may fail to collect AP data periodically.

Suggestion and Summary

If the status of ACs and APs is abnormal in Performance Management where real-time performance and KPIs of ACs and APs are monitored, you are advised to enable the AP data caching function in the WLAN view.

Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 333116

Downloads: 667

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