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).
Typical Configuration Examples

Typical Configuration Examples

This section describes typical configuration examples in typical application scenarios, helping users complete various operations based on the actual scenarios.

Example for Using SLA to Monitor the IP Voice Quality

This example illustrates how to use SLA to monitor the network quality in a timely manner and detect network faults in advance.

Applicable Products and Versions

V200R005C00 or later versions

Networking Requirements

The network administrator Thomas receives a complaint that LAN IP phone calls are intermittently interrupted, and works are negatively affected. Thomas requires that eSight provide a warning of network faults before customers complain about the faults.

Figure 12-55 Company's voice service networking

Requirement Analysis

  • Thomas requires that eSight provide a warning of degrading network quality before faults occur on the network.
  • SLA tasks can be used to monitor quality of the voice service. When the SLA compliance degree or any counter value of the voice service does not meet requirements, eSight sends alarms to the administrator.
  • The enterprise has high requirements on the IP voice quality; therefore, the threshold of the compliance degree should be improved from the default value 80 to 90, and the weight of the packet loss ratio be improved to 80.

Data Plan

IP Address of the Source Device

IP Address of the Destination Device

SLA Task Name

SLA Service

Execution Date of the SLA Task

Alarm Policy

10.137.34.62

10.11.55.37

IP voice test task

High quality voice service

Monday to Friday

Counter alarm and compliance degree alarm

Voice Quality Monitoring Process

  1. Create a periodic SLA task for the voice service on eSight.
  2. Devices send simulated voice flows.
  3. The test result is displayed on eSight.
  4. The network administrator view counters whose values exceed the thresholds on the alarm board.

Configuration Roadmap

  1. Adjust the counter threshold and weight for the high quality voice service in pre-defined SLA services.
  2. Create an SLA task and set basic parameters.
  3. Set the execution policy for the SLA task.
  4. Set the alarm policy for the SLA task.

Prerequisites

  • You have the operator user rights or higher.
  • Communication has been established between eSight and the devices, and eSight can manage and maintain the devices. For details, see Example for Using SNMPv3 to Import Network Devices in a Batch.
  • The devices have built-in NQA probes.
  • You have obtained a license for the NQA feature.

Procedure

  1. Adjust the alarm threshold of the IP voice service.

    1. Choose Resource > Network > Business > SLA Management from the main menu.

    2. In the navigation tree, choose SLA Management > SLA Service.
    3. Click next to High quality voice service in the Service Name list. The High quality voice service page is displayed.
    4. Set Compliance threshold (%) to 90, Weight of Packet loss rate (%) in UDP Jitter to 80, and Weight of Average RTD (ms) and Average jitter (ms) to 10, and click OK.

  2. Create an SLA task and set basic parameters.

    1. In the navigation tree, choose SLA Management > SLA Task and click Create.
    2. Set Task name to IP voice test task.
    3. Set Service name to High quality voice service, and click OK.
    4. Set Source device and Destination IP1 to 10.137.34.62 and 10.11.55.37.

  3. Configure the execution policy of the SLA monitoring task. Set From and To, as shown in the following figure. Set Execution period to 30 minutes and Execution days to Monday to Friday.

  4. Set the alarm policy for the SLA task. Set Trigger compliance alarms to Yes, Trigger indicator alarms to Yes, and Alarm generation count to 3.
  5. Retain the default values of the other parameters and click Test to check link connectivity between Source device and Destination IP.
  6. Click OK. An SLA task is created.

Verification

When the IP phone communications are intermittently interrupted, click in the upper right corner of the eSight home page. You can view counter alarms and compliance alarms in the current alarm list.

Summary and Suggestions

  • If an enterprise does not have high requirements on the IP voice service, select the default SLA service High quality voice service but do not modify parameters of the SLA service.
  • If a similar SLA task has been created, click next to the target task to quickly create an SLA task.
  • Click next to the target task to view task details.

Example for Using the SLA Quick Diagnosis Function to Locate IP Voice Quality Issues

This example illustrates how to use the SLA quick diagnosis function to locate IP voice quality issues when no SLA task is created.

Applicable Products and Versions

V200R005C00 or later versions

Networking Requirements

The network administrator Thomas receives a complaint that an IP voice conference is intermittently interrupted, and is asked to locate the fault quickly.

Figure 12-56 Company's voice service networking

Requirement Analysis

  • The IP voice service is a frequently used service of the company and should be guaranteed; therefore, the SLA service type should be high quality voice service.
  • A large number of devices exist between the two voice gateways and no SLA task is created for the devices. The SLA quick diagnosis function can be used to determine the network segment on which the fault occurs.

Configuration Roadmap

  1. Use the quick diagnosis function to check the high quality voice service between devices A and B to determine whether the links between the LAN 1 and the WAN are normal.
  2. Use the quick diagnosis function to check the high quality voice service between devices B and C to determine whether the voice service is correctly transmitted over the WAN.
  3. Use the quick diagnosis function to check the high quality voice service between devices C and D to determine whether the links between the LAN 2 and the WAN are normal.

Prerequisites

  • You have the operator user rights or higher.
  • Communication has been established between eSight and the devices, and eSight can manage and maintain the devices. For details, see Example for Using SNMPv3 to Import Network Devices in a Batch.
  • The devices have built-in NQA probes.
  • You have obtained a license for the NQA feature.

Procedure

  1. Use the quick diagnosis function to check the high quality voice service between devices A and B to determine whether the links between the LAN 1 and the WAN are normal.

    1. Choose Resource > Network > Business > SLA Management from the main menu.

    2. In the navigation tree, choose SLA Management > Quick Diagnosis.
    3. Set Service name to High quality voice service, and click OK.
    4. Set Source device and Destination IP to 10.137.240.133 and 10.137.240.131.

    5. Click Diagnose and wait for a few seconds. The diagnosis result is displayed on the page shown as follows, indicating that links between devices A and B are normal.

  2. Use the quick diagnosis function to check the high quality voice service between devices B and C to determine whether the voice service is correctly transmitted over the WAN.

    1. In the navigation tree, choose SLA Management > Quick Diagnosis.
    2. Set Service name to High quality voice service, and click OK.
    3. Set Source device and Destination IP to 10.137.240.131 and 10.137.240.132.
    4. Click Diagnose and wait for a few seconds. The diagnosis result is displayed on the page shown as follows, indicating that severe packet loss occurs on the WAN.

  3. Use the quick diagnosis function to check the high quality voice service between devices C and D to determine whether the links between the LAN 2 and the WAN are normal.

    1. In the navigation tree, choose SLA Management > Quick Diagnosis.
    2. Set Service name to High quality voice service, and click OK.
    3. Set Source device and Destination IP to 10.137.240.132 and 10.137.240.133.
    4. Click Diagnose and wait for a few seconds. The diagnosis result is displayed on the page shown as follows, indicating that links between devices C and D are normal.

Verification

  • The diagnosis result shows that packet loss occurs on the WAN. The network bandwidth is limited and quality of the key voice service needs to be guaranteed; therefore, the WAN administrator is advised to configure QoS to guarantee the voice quality.
  • Perform the quick diagnosis operation again to ensure that the fault is recovered.

Summary and Suggestions

  • Quick diagnosis: Temporarily initiate diagnosis on the links between the source and destination devices and services transmitted over the links to determine network quality counters such as the packet loss ratio and delay.
  • Compliance degree: Calculate the SLA compliance degree based on the counters, thresholds, and weights, and display the information in graphs.
  • If you have created SLA tasks for the faulty links, you can view data exceptions on the Dashboard.
Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 313153

Downloads: 635

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