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 V300R010C00SPC200, 300, and 500 Self-Service Integration 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).
Third-Party System Applications

Third-Party System Applications

Synchronizing Device Resource Information

  1. The periodical data synchronization mode is recommended. The recommended period is 12 hours (if the network scale is small, the 6-hour period can be used). The third-party system periodically invokes the Open API resource query interface to obtain resource data from eSight and updates the third-party resource data after data comparison.
  2. It is recommended that users be allowed to manually trigger synchronization of all resources on the third-party system interfaces.
  3. It is recommended that users be allowed to manually trigger synchronization of some resources that meet specified conditions on the third-party system interfaces.
  4. It is recommended that users subscribe to eSight system resource change notifications in the third-party system. In addition, users can receive and process the change notifications and update resource information in the third-party system.

Monitoring Device Performance Indicators

  1. Users can select devices and enable monitoring over performance indicators of the devices on the third-party system interfaces.
  2. The third-party system can periodically update performance indicator data. The update period is the same as the performance collection period (5 minutes, 15 minutes, 30 minutes, 1 hour, or 1 day) configured on eSight.
    • Performance data of virtual resources can be collected at an interval of 5 or 15 minutes.
    • For details about how to configure the performance task period, see "Virtual Resources > Global Settings > Setting Performance Parameters" in the eSight Operation Guide.
  3. Within each specified period, the third-party system uses the FTP client to obtain the performance result file generated in the latest collection period in pull mode. The following describes the detailed execution logic:

    For example, the performance collection period configured on eSight is 5 minutes. The current UTC time is 16:35 on September 9, 2014.

    (1) Use the FTP client to log in to the eSight FTP server.

    (2) Go to the path PerformanceFiles\20140909, where performance result files generated on the current day are stored, from the root path of the FTP client.

    (3) Run the ls command to obtain all file names under the current path.

    (4) Filter all files whose names start with PM_IGifXTrafficStat_5_20140909_1630. (Generally, only one file can be filtered. Multiple files may be filtered if delayed data files exist.)

    (5) Parse the result file.

  4. The following describes the result file format:
    1. CSV file that is opened using EXCEL

    2. CSV file that is opened in text mode

      First line:

      "Interface Traffic Statistics","Interface Traffic Statistics","53",

      Second line:

      "DeviceID","DeviceName","ResourceID","ResourceName","CollectionTime","GranularityPeriod","ifOutBandRate","ifHCInOctetsSpeed","ifHCOutOctetsSpeed","ifInBandRate",

      Third line and lines after the third line:

      "NE=34603118","SMM","Ethernet0/0/3","Ethernet0/0/3","1409900400000","15","0.00","143.03","75.73","0.00",

      "NE=34603118","SMM","Ethernet0/0/0","Ethernet0/0/0","1409900400000","15","0.00","18.33","18.41","0.00",

    3. First line: displays the indicator group name, indicator group description, and total number of measurement objects.
    4. Second line: displays the name of each attribute in the third line and lines after the third line. The first six attributes are fixed: device DN, device name, resource DN, resource name, collection time (absolute UTC time, in milliseconds), and collection period (in minutes). Lines after the seventh line display the performance counter names. For details, see the Performance Counter List of eSight.
    5. Third line and lines after the third line: display the actual values of the attributes displayed in the second line.
    6. File segmentation: presses Enter to break a line, uses the double quotation marks ("") to enclose each cell in the CSV table, and uses commas (,) to separate cells in the same line.
    7. Unique ID of each measurement object: consists of the NE DN in the first column and the resource DN in the third column. The resource DN in the third column corresponds to the measurement object DN returned by the Open API query interface that is invoked.
Translation
Download
Updated: 2019-10-30

Document ID: EDOC1100044386

Views: 17827

Downloads: 87

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