V300R001C10 Issue 01 Date 2013-12-10 HUAWEI TECHNOLOGIES CO., LTD.
2013. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd. Address: Website: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://enterprise.huawei.com i
About This Document About This Document Purpose This document describes the esight SLA tool, data collecting method, and general processing process, providing guidance for users to learn about and use esight SLA. Intended Audience This document is intended for: Technical support personnel Maintenance personnel Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury. Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury. Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results. NOTICE is used to address practices not related to personal injury. Calls attention to important information, best practices and tips. NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration. ii
About This Document Change History Changes between document issues are cumulative. The latest document issue contains all the changes made in earlier issues. This issue is the first official release. iii
Contents Contents About This Document... ii 1 Executive Summary... 1 2 Introduction... 1... 2 3.1 Overview... 2 3.2 Implementation... 3 3.2.1 Data Collection Process... 3 3.2.2 SLA Data Aggregation Policy... 4 3.2.3 Intelligent Collection Period Policy... 4 3.3 Function Constraints... 5 3.3.1 Applicable Device Types... 5 3.3.2 Application Scenarios... 6 3.3.3 Technical Constraints... 6 3.4 Typical Applications... 7 3.4.1 Monitoring the Network Quality... 7 3.4.2 Monitoring the QoS Service Quality... 10 3.4.3 Diagnosing an SLA Service Efficiently... 13 3.4.4 Service Diagnosis... 14 4 Experience... 16 5 Conclusion... 17 6 Acronyms and Abbreviations... 18 iv
1 Executive Summary 1 Executive Summary A Service Level Agreement (SLA) is an agreement between a service provider and a customer to ensure service performance and reliability at specified costs. esight SLA is a network performance diagnosis tool that instructs NEs to send diagnosis packets to each other for network performance statistics. esight SLA provides the following functions: SLA service management SLA task management SLA historical data display Quick diagnosis Service diagnosis 1
2 Introduction 2 Introduction With an increasing number of services on the IP network, the IP network operation and maintenance face the following challenges: Lack of performance deterioration prewarnings due to incomplete network performance monitoring mechanism Lack of efficient fault diagnosis SLA checks the quality for various services on the network periodically and displays check results as data graphs, alarms, and reports, providing network maintenance personnel with network quality data and ensuring differentiated service verification. In addition, SLA provides the quick diagnosis and service diagnosis function to help users diagnose faults efficiently. 1
3.1 Overview SLA can monitor the quality for various services. Currently, SLA supports 13 test instances and 24 predefined services. SLA provides network maintenance personnel with network quality data and ensures differentiated verification of services and applications. Figure 3-1 shows the SLA solution. Figure 3-1 SLA solution esight Voice Voice Video Data Video Data Voice service Data service Counter collection Built-in NQA probe NOTE A Network Quality Analysis (NQA) probe is a built-in module of a Huawei device and the foundation for implementing SLA functions. An NQA probe can simulate packets of more than 20 protocols and send them to a destination device to check service operating status on the network. 2
The process of implementing SLA functions is as follows: 1. Maintenance personnel select key services to monitor from services such as voice, video, and data services running on the IP network based on the site scenario. 2. Locate network devices nearest service terminals on the service link (the source device must be a Huawei device with a built-in NQA probe), and create an SLA task. 3. esight collects service quality data based on the configured interval. 4. Maintenance personnel view the compliance degree, historical data, alarms, and reports to check the service quality and performance. 3.2 Implementation 3.2.1 Data Collection Process Figure 3-2 shows the process of collecting VoIP service quality data from device A to device B. Figure 3-2 Process of collecting VoIP service quality data esight Router A Voice service Router B Send a collection command to devices configured with an NQA probe Router A sends analog voice packets to router B Built-in NQA probe 1. esight uses SNMP to send a collection command to router A that is configured with a built-in NQA probe. (esight must have the SNMP-based set permission on router A.) 2. Router A sends analog VoIP packets to router B. 3. Router B sends response packets to router A. 4. Router A analyzes the response packets and calculates the performance counters such as latency, jitter, and packet loss rate. 5. esight collects the performance counters calculated by router A and displays them to maintenance personnel through historical data charts and graphs. 3
3.2.2 SLA Data Aggregation Policy SLA data is collected periodically and stored in the database. Many coexisting SLA tasks will collect a mass of data that may use up the database space quickly. To solve this problem, esight automatically consolidates data to reduce the database space. A piece of consolidation data is a record of the average value of all data generated in a specified period. At 00:00 on the first day of each month, esight deletes all original data generated in the month before last, for example, at 00:00 on March 1, it deletes all original data generated throughout January. Data consolidation is controlled by the following parameters. Data consolidation granularity Data consolidation granularity can be an hour, a day, a week, or a month. Data consolidation time Hourly: Data is consolidated on the hour. Daily: Data is consolidated at 00:00 every day. Weekly: Data is consolidated at 00:00 each Monday. Monthly: Data is consolidated at 00:00 on the first day of each month. Data consolidation source Hourly data: Original SLA data is used as the consolidation source. Daily data: Hourly data is used as the consolidation source. Weekly data: Daily data is used as the consolidation source. Monthly data: Weekly data is used as the consolidation source. Consolidation data saving policy Original data: saved for the number of remaining days in the current month at the time of the data generation plus the number of days in the next month. For example, a data record generated on March 8 will be saved for the number of remaining days in March (23 days) plus the number of days in April (30 days), altogether 53 days. Hourly data: saved for one year Daily data: saved for one year Weekly data: saved for three years Monthly data: saved permanently 3.2.3 Intelligent Collection Period Policy The intelligent collection period policy automatically lowers the collection interval when detecting abnormal counters. This helps maintenance personnel to determine whether the abnormal counter is temporary or is caused by network quality deterioration. Configure the intelligent collection period policy during task creation, as shown in Figure 3-3. 4
Figure 3-3 Configuring the intelligent collection period policy 3.3 Function Constraints 3.3.1 Applicable Device Types Device Device Type Device Version Huawei devices that support and enable the NQA function H3C devices that support and enable the NQA function AR150, AR200, AR1200, AR2200 and AR3200 NE20, NE20E, NE40, NE40E, NE80 and NE80E S23, S27, S33, S37, S53, S57, S63, S67, S77, S93 and S97 AC6600 ME60 MSR20, MSR30 and MSR50 SR66 and SR88 AR29, AR28, AR46 and AR49 S125, S95, S85, S75, S58, S55, S3610, S51, S3600, S31, S7806, S6506R, S3952P-SI and S3050C Operating system version: VRP5.50 or later 5
3.3.2 Application Scenarios Device Device Type Application Scenario Huawei devices that support and enable the NQA function H3C devices that support and enable the NQA function AR150, AR200, AR1200, AR2200 and AR3200 NE20, NE20E, NE40, NE40E, NE80 and NE80E S23, S27, S33, S37, S53, S57, S63, S67, S77, S93 and S97 AC6600 ME60 CE5800,CE6800,CE12800 MSR20, MSR30 and MSR50 SR66 and SR88 AR29, AR28, AR46 and AR49 S125, S95, S85, S75, S58, S55, S3610, S51, S3600, S31, S7806, S6506R, S3952P-SI and S3050C Currently the following test instances are supported: ICMP Echo ICMP Jitter UDP Echo UDP Jitter TCP Connect SNMP DNS DHCP HTTP FTP LSP Ping LSP Jitter LSP Trace Currently the following test instances are supported: ICMP Echo UDP Echo UDP Jitter TCP Connect 3.3.3 Technical Constraints Device Device Type Technical Constraint Huawei devices that support and enable the NQA function AR150, AR200, AR1200, AR2200 and AR3200 NE20, NE20E, NE40, NE40E, NE80 and NE80E S23, S27, S33, S37, S53, S57, S63, S67, S77, S93 and S97 AC6600 ME60 CE5800,CE6800,CE12800 A source device must be a Huawei device with a built-in NQA probe. The required service must be enabled on a destination device. For example, the UDP service must be enabled on a destination device in the UDP Echo test instance. 6
Device Device Type Technical Constraint H3C devices that support and enable the NQA function MSR20, MSR30 and MSR50 SR66 and SR88 AR29, AR28, AR46 and AR49 S125, S95, S85, S75, S58, S55, S3610, S51, S3600, S31, S7806, S6506R, S3952P-SI and S3050C A source device must be a Huawei device with a built-in NQA probe. The required service must be enabled on a destination device. For example, the UDP service must be enabled on a destination device in the UDP Echo test instance. 3.4 Typical Applications Currently, SLA supports 13 test instances and 24 predefined services. In addition, SLA allows users to customize services. This section describes the typical application scenarios. 3.4.1 Monitoring the Network Quality Figure 3-4 Monitoring the network quality Regions A and B in an enterprise are connected through the carrier network. The enterprise and the carrier sign an SLA agreement on the network quality. esight SLA can monitor the network quality for enterprises 24-7 round the clock. To create an SLA task, perform the following steps: Step 1 Choose SLA Management > SLA Task Management. Step 2 On the SLA Task Management page that is displayed, click Create, as shown in Figure 3-5. 7
Figure 3-5 SLA Task Management page Step 3 Set related parameters, as shown in Figure 3-6. Figure 3-6 Setting related parameters The task name, service, source device, and destination device IP address are mandatory. When the task is created successfully, esight collects network quality counters based on the configured interval. For the UDP Echo, UDP Jitter, and TCP Connect test instances, the TCP and UDP services must be enabled on the destination device. 8
Figure 3-7 Entrance for viewing counter values Step 4 View counter values, as shown in Figure 3-8. Figure 3-8 Viewing counter values Users can determine whether the network service provided by the network carrier reaches the promised service quality. NOTE In Figure 3-8, red lines indicate thresholds. Users can understand service quality by comparing counter values with thresholds. In addition, the queried historical data can be exported to an Excel file and stored on a Web client. Figure 3-9 Exporting historical data to an Excel file 9
----End 3.4.2 Monitoring the QoS Service Quality Figure 3-10 Monitoring the QoS service quality EF AF BE Voice Video Data esight Router A Router B Detection device Voice Monitor service quality of each QoS queue in each channel Voice Video Data Video Data Packet detection Counter collection Built-in NQA probe Egress routers A and B zones are configured with a QoS policy respectively. Voice streams are transmitted through the EF queue to meet requirements of low latency. Video streams are transmitted through the AF queue to ensure that they are transmitted with a high bandwidth. Data streams are transmitted through the BE queue to send service data that does not impose high requirements on QoS. SLA can monitor the service quality of each QoS queue in regions A and B and compare service quality based on historical task data. 10
To create SLA tasks for the EF, AF, and BE queues and view counter values, perform the following steps: Step 1 On the task creation page, create an SLA task for monitoring the EF queue from router A to router B, and set Packet TOS to 184, as shown in Figure 3-11. Figure 3-11 Creating an SLA task for the EF queue Step 2 Create an SLA task for monitoring the AF queue, and set Packet TOS to 104, as shown in Figure 3-12. 11
Figure 3-12 Creating an SLA task for the AF queue Step 3 Create an SLA task for monitoring the BE queue, and set Packet TOS to 0. Step 4 View SLA counter values of QoS queues, as shown in Figure 3-13. Figure 3-13 Viewing SLA counter values of QoS queues Maintenance personnel can select multiple tasks, view historical data, and compare counter values of multiple queues to determine whether QoS configurations are correct in the case of network congestion. 12
Figure 3-14 Viewing the latency of the EF, AF, and BE queues Figure 3-14 shows the impact on the latency of each queue when the AF queue is congested. The increase of the latencies of the AF and BE queues does not affect the EF queue. Figure 3-15 Monitoring the packet loss rates of the EF, AF, and BE queues Figure 3-15 shows the impact of the traffic congestion in the AF queue on the packet loss rate. Only the packet loss rate of the AF queue is affected when the AF queue is congested. ----End 3.4.3 Diagnosing an SLA Service Efficiently If no SLA task has been created for a faulty service, maintenance personnel can use the quick diagnosis function to check the service quality instantly. Figure 3-16 Quick Diagnosis page 13
On the Quick Diagnosis page, set Service name, Source device, and Destination IP, and retain the default values for parameters in the Test Case Settings area or change the values as required. Then click Diagnosis. The diagnosis result is displayed, as shown in Figure 3-17. Figure 3-17 Diagnosis result 3.4.4 Service Diagnosis Diagnoses the network quality of telepresence systems and desktop cloud systems, and allows users to quickly and efficiently locate faults and assess network quality. Figure 3-18 Service Diagnosis 14
On the Service Diagnosis page,set Template Name,Source Device,Destination IP,Source Port and Destination Port. and retain the default values for parameters in the Diagnose Parameter area or change the values as required. Then click Diagnosis. Figure 3-19 Service Diagnosis Result 15
4 Experience 4 Experience Service and network quality monitoring SLA uses industry-leading counters to monitor quality for various services such as video, voice, data, and IP network. SLA generates periodical reports to dynamically reflect network and service health status, helping enterprise network operators to understand the network condition and user experience on services in real time. Fault locating SLA provides more than 12 test instances to meet different service and network monitoring requirements. It uses built-in NQA probes on devices to monitor service and network quality with high precision and frequency, helping maintenance personnel to quickly locate faults. 16
5 Conclusion 5 Conclusion SLA periodically provides feedback on the dynamic network and service health status and displays the service quality through charts, alarms, and reports. This helps enterprise network maintenance personnel to understand network condition and user experience on services in real time and optimize the network. 17
6 Acronyms and Abbreviations 6 Acronyms and Abbreviations Table 6-1 Acronyms and abbreviations Acronyms Abbreviations DNS DHCP FTP HTTP ICMP NQA SLA SNMP TCP UDP LSP and Full Spelling Domain Name System Dynamic Host Configuration Protocol File Transfer Protocol Hypertext Transfer Protocol Internet Control Message Protocol Network Quality Analysis Service Level Agreement Simple Network Management Protocol Transmission Control Protocol User Datagram Protocol Label Switched Path 18