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

Restrictions

Performance task

  • When indicators of collection objects are collected by collection tasks in different periods, the task created last collects the indicators. If a task created later is stopped but the task created earlier is not stopped, the data is not collected. The task created earlier takes effect only when the task created later is deleted.
  • The performance collection unit can be used as reference for the processing capability of the performance framework collection indicators. When the number of collection units reaches or exceeds the maximum, the data processing capability of the performance framework cannot meet the requirements. However, the number of collection units cannot be used as reference when there is a large number of 30-second or one-minute periodical collection tasks. More data is reported when the collection period is shorter, which affects the system I/O greatly. Therefore, it is recommended that the number of monitored objects do not exceed 50 for 30-second and 1-minute periodical collection tasks. Otherwise, the system I/O may stay at a high level and some data is not collected.

Performance data

  • If the task name column in the performance data table is empty, the possible cause is that the task delivery is not completed or the task is being created for the collection objects. Wait for several minutes and check the performance data again.
  • If some objects (including non-Huawei devices managed by eSight) are not collected in the performance data table, verify that the corresponding performance task is started or verify that the device type matches with the version of the corresponding collection objects. If no data is displayed, troubleshoot the fault as prompted.

Monitoring settings

  • The maximum number of performance collection units is determined by the physical memory space. The mapping is as follows.

    Physical Memory

    Maximum Number of Collection Units

    32G

    640000

    64G

    1280000

  • If the number of used collection units exceeds the maximum, the performance collection is affected greatly and the following exceptions may occur: collection missing, data processing delay, and real-time performance collection exception. It is recommended that the number of used collection units do not exceed the maximum and tasks and indicators requiring no monitoring be deleted in time.
  • It is recommended that collection tasks whose period is less than five minutes not be created. Frequent collection consumes a large number of device resources and has great impact on device performance and device services.
  • It is recommended that proper indicators be selected during task creation. Irrelevant indicators will consume eSight resources and affect device performance.
  • When performance data of WLAN devices is collected, ensure that the eSight time is not later than the device time. It is recommended that the eSight time is one minute earlier than the device time.

SFTP task setting

  • The device performance is affected when the collection period of the SFTP performance task is short or the device has many tasks. It is recommended that the period of the SFTP performance task be not less than 15 minutes.
  • It is recommended that a device be managed only by one eSight and irrelevant SFTP performance tasks be deleted from the device in time.

Northbound performance API

  • It is recommended that the northbound performance open API be not invoked frequently. To obtain a large amount of performance data, you are advised to invoke the northbound SFTP API.
  • When northbound performance files are generated, you are advised to configure required device types and indicators instead of configuring all device types and indicators.
  • When the northbound performance function is enabled and the northbound performance file generation policy is configured on eSight, the configuration files for_export_template.xml and for_export_rule_north.xml in eSight installation directory\AppBase\etc\oms.nbi\pm file exist as examples. You can modify the files so that northbound performance files can be generated normally. However, the two files cannot be inherited in the upgrade scenario. After upgrade, the two files are overwritten by those in the new version. Therefore, to inherit the configuration for generating northbound performance files, you need to create the *_north.xml and template files. The two files can be inherited in the upgrade scenario.
Download
Updated: 2019-05-17

Document ID: EDOC1100011877

Views: 284479

Downloads: 544

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