1. HUAWEI eSight iPCA Tech-level Main Slide

2. 1 Acronyms and Abbreviations Full Name MCPMeasurement Control Point DCPData Collecting Point TLPTarget Logical Port MP2MPmultipoint-to-multipoint IP PMIP performance monitoring NTPNetwork Time Protocol NQANetwork Quality Analysis OWAMPOne-Way Active Measurement Protocol TWAMPTwo-Way Active Measurement Protocol ENPEthernet Network Processor iPCAPacket Conservation Algorithm for Internet

3. 2 Content Impact of Packet Loss 1 1 2 2 Huawei eSight iPCA Solution

4. 3 Impact of Network Packet Loss WAN Video phone Pixelation, voice delay Application server Slow response in website browsing Packet loss 1. Affect customer experience 2. Lower work efficiency 3. Make fault location difficult Packet loss time, location, and type

5. 4 Traditional Network Quality Measurement Technologies and Limitation CategoryDescriptionTechnologyLimitation Direct measurement Measure the real service packets. Y.1731Only applies to L2 networks. IP PMOnly applies to P2P networks. Indirect measurement Insert the detection packets into service packets to calculate packet loss. Ping The object is not real service packets. The detection packets and service packets may use different paths. The measurement result is inaccurate, and cannot reflect real service performance. In addition, detection packets occupy the bandwidth of real service packets. NQA TWAMP / OWAMP Traditional measurement technologies are based on P2P paths and flows, and do not support MP2MP measurement. The following are two categories: The network needs a method to detect any faults on devices or links that affect service experience. In addition, the network must be able to quickly locate faults.

6. 5 Content Impact of Packet Loss 1 1 2 2 Huawei eSight iPCA Solution

7. 6 iPCA Concept Packet Conservation Algorithm for Internet (iPCA) is developed by Huawei. iPCA implements packet loss monitoring and fault location for connectionless IP networks by coloring real service packets and partitioning a network. It allows a network to perceive service quality and quickly locate faults. In addition, iPCA breaks the limitation of traditional measurement technologies. L2+L3 mixed network iPCA P2P, MP2MP Performance monitoring based on real service packets Question iPCA Who lost the packets? Where were the packets lost? When were the packets lost? Monitors the service flows with five specified attributes based on domains or link segments, and determines the type of services with packets lost. Partitions the network into multiple domains, provides device-level, link-level, and network-level monitoring, and automatically locates faults. Monitors real service flows, and sends alarms to the administrator immediately when faults occur.

8. 7 Topology-Centric Configuration and Monitoring 1 In the physical topology view, you can complete all iPCA- related configurations and show measurement results. 2 You can drag the mouse to select measurement objects and complete measurement on devices and links through one-click operations. Create device or link measurement tasks Create network-level measurement

9. 8 Network-Level Measurement View Shows Quality of All Lines Network-level measurement needs to be performed on the leased lines between headquarters and branches, and between branches. The network-level topology view shows all network-level measurement instances. You can view the quality of key services on the leased lines on WAN.

10. 9 Based on Real Service Flows, Without Increasing Load on Data Channels Traditional quality measurement technologies send simulated detection packets on the network. The simulated detection packets are different from real service packets in sizes and frequencies. Therefore, simulated detection packets cannot reflect real service quality, and occupy bandwidth. Service packets Simulated detection packets Service packets iPCA colors real service packets, which do not occupy additional bandwidth.

11. 10 Intelligent IP Path Tracing, Quickly Locating Failure Points Fault location process of traditional technologies: 1.To measure end-to-end service packet loss, the network administrator needs to check the path where service flows pass. 2.Configure ACL on device A to collect statistics on packets. 3.Configure ACL on device B to check whether packet loss occurs from device A to device B. 4.Configure ACL on device C to check whether packet loss occurs from device B to device C. 5.Configure ACL on device D to check whether packet loss occurs from device C to device D. The entire process lasts 15-30 minutes. The network administrator needs to log in to four devices. When there are more devices, the process lasts for a longer time. In addition, the ACL configuration may increase failure possibility. Fault location process of iPCA: 1.Open the service measurement page 2.Click DisCover Route. 3.Click Detect. After 2-3 minutes (dozens of seconds if network connection is in a good condition), packet loss on each node and line on the service flow path is displayed. Measurement point Device A Device B Device C Device D C1 C2 C3 C4 C5 C6 C7 C8

12. 11 Measurement Principle Measured system (device/link/carrier's network/service path) System core Internally terminated Internally generated iPCA quality measurement mechanism: A measured system is in the normal state if the following condition is met: Number of packets arriving at the system + Number of internally generated packets = Number of packets leaving the system + Number of packets internally terminated by the system If this condition is not met, some packets have been dropped in the system. Packets arriving at the system Packets leaving the system

13. 12 Device-Level Packet Loss Measurement Measurement domain: All ENP cards and SFUs form a packet conservation domain (excluding the CPU and non- ENP cards). Object: All incoming and outgoing IP unicast flows of the measurement domain. Measurement interval: 10 seconds Alarm: When the packet loss ratios in five consecutive intervals exceed 5%, the device sends an alarm to the NMS. When the packet loss ratios in five consecutive intervals fall below 1%, the device sends a clear alarm to the NMS. Incoming flowsOutgoing flows CPU Measurement domain Chassis Non-ENP SFU 1 Chassis Ingress TLPEgress TLP CPU Non-ENP card ENP card 1 C1-1 C1-2 C1-3C1-4 C1-5C1-6C1-7 C1-8C1-9C1-10 ENP card 2 C2-1 C2-3C2-4 C2-5C2-6C2-7 C2-8C2-9C2-10 SFU 2 Number of packets from other devices to ENP cards: C1-1 and C2-1 Number of packets from CPU to ENP cards: C1-5 and C2-5 Number of packets from non-ENP cards to ENP cards: C1-7 and C2-7 The number of packets entering the measurement domain Cin = C1-1 + C2-1 + C1-5 + C2-5 + C1-7 + C2-7 Number of packets from ENP cards to CPU: C1-2 and C2-2 Number of packets from ENP cards to non-ENP cards: C1-4 and C2-4 Number of packets from CPU to ENP cards and then other devices: C1-8 and C2-8 Number of packets from ENP card to ENP card and then other devices: C1-9 and C2-9 Number of packets from non-ENP card to ENP card and then other devices: C1-10 and C2-10 Number of packets leaving the measurement domain Cout = C1-2 + C2-2 + C1-4 + C2-4 + C1-8 + C2-8 + C1-9 + C2-9 + C1-10 + C2-10 Number of lost packets = Cin - Cout

14. 13 Link-Level Packet Loss Measurement Measurement domain: The physical link between directly connected devices is a packet conservation domain. The measurement range contains physical direct links, and TM chips and MAC chips on interfaces. Object: All incoming and outgoing IP unicast flows of the measurement domain. Unidirectional packet loss from device 1 to device 2 = C1_1 - C2_1 Unidirectional packet loss from device 2 to device 1 = C2_2 - C1_2 Note: The TM and MAC chips do not support iPCA. The measurement object is all packets. The measurement interval of TM and MAC chips is not synchronized with that of micro engine. Therefore, the statistics are only used as a reference for fault location. Device 1 Device 2 Micro engine MAC ENP card TM C1_1 C1_2 MAC ENP card Micro engine TM C2_1 C2_2 Ingress TLP Egress TLP Expected measurement range Actual measurement range

15. 14 Network-Level Packet Loss Measurement Measurement domain: A domain consisting of non-agile devices (including third-party devices) surrounded by agile devices and the links between agile devices and the measurement domain. Object: All incoming and outgoing IP unicast flows of the measurement domain. (The current version only supports measurement on the service flows with known directions.) Ingress TLP Egress TLP Device A Device B Device C Device E C1 C2 C3 C4 C5 Number of lost packets from devices A/B to devices C/D/E = (C1 + C2) - (C3 + C4 + C5) Incoming packets Outgoing packets Measurement domain Note: The measurement object in this example is a unidirectional service flow.

16. 15 Network-Level Packet Loss Measurement The iPCA system consists of NMS, MCP, DCPs, and TLPs, which have the following responsibilities: NMS: provides GUI Issues commands to configure measurement instances. Obtains real-time statistics and historical data from MCP, and displays measurement results. TLP (Target Logical Port): Executes iPCA measurement tasks, and corresponds to a logic interface on network device Colors and measures target service flows periodically. Reports statistics in each interval to DCPs. DCP (Data Collecting Point): Manages and controls TLPs (configures and issues ACL rules to TLPs). Collects statistics from TLPs. Reports statistics to the MCP. MCP (Measurement Control Point): Collects statistics from DCPs. Summarizes statistics and calculate results. Reports measurement results to the NMS. DCP MCP DCP TLP eSight Management data Measurement data report Real service flow

17. 16 Service Path Hop-by-Hop Measurement Service packet forwarding path detected by IP Tracert Service flow characteristics: Service packets must have known source and destination IP addresses. Path tracing: eSight searches for the source gateway according to the source IP address of the service flow. The source gateway performs IP Tracert to the destination IP address of the service flow to trace the forwarding path between source and destination gateways. The gateways deliver service flow characteristics to agile devices. The agile devices returns the service flow inbound interfaces (1, 3, 5, and 7) and outbound interfaces (2, 4, 6, and 8) to eSight. The Layer 3 IP path of the service flow is determined. Measurement method: Each agile device measures service packets on its inbound and outbound interfaces. Two neighboring interfaces can calculate the number of lost service packets on each segment (ACH). Constraint: The current version of iPCA only supports IP networks, but does not support MPLS VPN or GRE network. If load balancing paths or active/standby paths are configured, the measurement result on only the path obtained by IP Tracert is displayed. Terminal S57 (source gateway) S57 (destination gateway) S127 12 34 5678 ACH1ACH2ACH3ACH4ACH5ACH6ACH7 eSight

18. 17 Huawei Products Supporting iPCA ModelVersionRemarks eSightV200R005C00NMS,SLA S5720HIV200R006C00Box switch S7700V200R006C00Chassis switch,ENP S9700V200R006C00Chassis switch,ENP S12700V200R006C00Chassis switch,ENP The device must support iPCA and have an ENP card installed.

19. 18 Solution Overview 1.2 2.1 1.1 Object: Packet loss on the entire network, including all agile devices, links, and domains 2.1 2.2 Branch 2 Branch 1 Headquarters iPCA device Scenarios: Device-level A single agile device (excluding packet loss on non- ENP cards and CPU) Link-level Links between directly connected agile devices Network-level Agile devices surround the consecutive domains consisting of non-agile devices (including third-party devices) End-to-end link that transmits specified service flows

20. 19 iPCA network topology: The topology view involves two campus networks (Shenzhen headquarters and Beijing branch) and shows a typical Layer 3 network. The two networks use S12700 switches as the egress devices to connect to the carrier's network. iPCA measurement object: 1. Packet loss on the devices and links on the campus networks; 2. Packet loss in Telepresence service flows from building 6 in Shenzhen to building 1 in Beijing; 3. Packet loss on the carrier's network 1 2 Hop-by-hop service packet measurement 3 Packet loss measurement on carrier's network Service Quality Measurement on Enterprise Campus Network Packet loss measurement on devices and links on campus networks

21. 20 Service Quality Measurement on Devices and Layer 2 Links in Enterprise Campus Network Scenario: Select all devices and links in the topology view of the headquarters network and create an iPCA measurement task. Entry: Log in to eSight and choose Monitor > Topology Management. 1 Drag the mouse to select all devices and links in the topology view of the headquarters network, right-click the selected area, and choose iPCA > Create iPCATask 2 Display the latest packet loss measurement results of the devices and links. Identify non-agile devices and do not deliver configuration to them

22. 21 Scenario: Create network-level measurement tasks on the egress devices (Shenzhen core and Beijing core) of the headquarters and branch networks. The network-level topology shows packet loss on carrier's network. Entry: Log in to eSight and choose Monitor > Topology Management. 1 Right-click the device Shenzhen core and choose iPCA > iPCA Management. 2 Open the iPCA management page and create a network-level measurement task. 3 Display packet loss on carrier's network. Service Quality Measurement on Leased Lines

23. 22 Scenario: Select building 6 in Shenzhen and building 1 in Beijing in the topology view to create a network-level measurement task. eSight can discover service path, display each agile switch on the path, and show packet loss on the path. Entry: Log in to eSight and choose Monitor > Topology Management. 1 Perform hop-by-hop path measurement in the network-level view. 2 Click 寻路 to display the service forwarding path and agile switches. 3 Click 检测 to show packet loss statistics on egress node. Click a device on the path to show real-time packet loss statistics on the device Hop-by-Hop Measurement on Unicast IP Service Path

24. Copyright©2012 Huawei Technologies Co., Ltd. All Rights Reserved. The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice. HUAWEI ENTERPRISE ICT SOLUTIONS A BETTER WAY