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 V300R010C00 Operation Guide 07

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).
Example for Obtaining Network Performance Trend Through Historical Data

Example for Obtaining Network Performance Trend Through Historical Data

This example illustrates how to obtain network performance trend by viewing historical data and to optimize network performance by taking corresponding measures when performance bottleneck occurs.

Networking Requirements

An enterprise builds both wired and wireless networks for the office area. Wired users complain about poor network quality in recent days. The network administrator Thomas needs to confirm whether the network performance can meet office needs.

Figure 6-2 Enterprise networking

Requirement Analysis

Thomas can analyze historical performance data to check whether the network performance can meet the office requirements. The real-time performance data at a specific time reflects whether network performance meets requirements at that time. To determine whether the overall network performance can meet requirements, Thomas needs to analyze performance data collected during a period of time. What historical performance counters need to be monitored?

  • Wired network:
    • Device average CPU/memory usage: If the value of this counter remains high, network adjustment or device capacity expansion is required.
    • Interface receiving/sending rate: If the value of this counter remains high, check whether high interface traffic is caused by increasing service volume.
    • Inbound/Outbound bandwidth usage on interface: If the value of this counter remains high, network adjustment or device capacity expansion is required.
    • Response duration: If the value of this counter remains high, network adjustment or device capacity expansion is required.
    • Daily ping failures: If the value of this counter remains high, network adjustment or device capacity expansion is required.
  • WLAN network:
    • AP CPU/memory usage and AC CPU/memory usage: View the running status of ACs and APs to check whether the devices are faulty.
    • Top N AP upstream interface traffic and channel usage: Check whether the uplink traffic of the APs exceeds the overall bandwidth requirements. If so, network bandwidth needs to be expanded.
    • Number of network-wide online users: View the trend of the access user count on the entire network to check whether the current network can provide access services for the increasing number of users. If the value of this counter is close to the maximum value, the network capacity needs to be expanded.
    • User statistics by terminal type: View the distribution of access users and adjust the network based on the information.

Recently, Thomas receives complaints on poor network quality from wired users. Thomas considers that an access switch on the wired network is faulty. Therefore, Thomas determines to monitor the following counters of the S2700 access switch: average CPU usage, average memory usage, response duration, daily ping failures, interface receiving rate, interface sending rate, inbound bandwidth usage, and outbound bandwidth usage.

Configuration Roadmap

  1. Determine whether performance collection tasks need to be created.

    eSight supports Default collection task for network devices and Link Interface Collection task, which cover counters to be checked for the wired network. Therefore, you do not need to create performance collection tasks.

  2. Save monitored counters of the access switches as home page Portlets. After customizing the home page, you can view historical performance data in the Portlets.
    NOTE:

    You need to perform this step only when you select monitored counters.

  3. Monitor historical performance data of monitored access switches after data collection for one day.

Prerequisites

  • You have operation rights for Custom Portlet Management and Performance Management.
  • Devices have been added to eSight.

Procedure

  1. Save monitored counters of the access switches as home page Portlets.

    1. Choose Performance > Performance Data from the main menu.
    2. When you add device-related counters, click Device in Overview, select the access switches to be monitored, and click Historical Data.

      When you add interface-related counters, click Network Device > Interface in Overview, select the access switches to be monitored, and click Historical Data.

    3. Click in the upper right corner of a historical performance view. In the Save As Home Page Portlet dialog box that is displayed, set the view name and description, and click OK.
    4. Choose Home from the main menu. Click Home to view the portlet of the target.

    The Portlet is displayed on the home page.

  2. Monitored counters are displayed in the home page Portlet. Monitor historical performance data of monitored access switches after data collection for a period of time.

    You can find that the average CPU usage of the access switch remains high, indicating that the switch capacity needs to be expanded.

Summary and Suggestions

In the Big Data era, performance becomes more and more important. The network administrator must check the historical performance data every week or every month to analyze the network performance trend and take corresponding measures to optimize the network performance when the performance bottleneck occurs.

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044378

Views: 58898

Downloads: 270

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