< Home

Example for Configuring iPCA to Implement Regional Network Packet Loss Measurement

iPCA Overview

Packet Conservation Algorithm for Internet (iPCA) technology is used to measure IP network performance. It directly marks service packets to implement network-level and device-level packet loss measurements.

In the all-IP era, various services sensitive to packet loss, such as voice and video services, are transmitted through an IP network. To detect packet loss and find out packet loss points on the network, Huawei developed iPCA technology. Huawei iPCA has the following characteristics:

  • iPCA applies to both Layer 2 and Layer 3 networks.
  • iPCA directly marks service packets to obtain the packet loss ratio and number of lost packets, without increasing loads on devices.
  • iPCA supports packet loss statistics collection on multipoint-to-multipoint networks.

Regional network packet loss measurement: Statistics are not collected on edge devices that are out of the transit network. This method is applicable to packet loss measurement on a WAN when an enterprise has multiple networks connected through the WAN or on an enterprise campus network consisting of devices that do not support iPCA.

Configuration Notes

  • The prerequisite of network-level packet loss measurement is time synchronization between iPCA devices. Therefore, before configuring iPCA, configure NTP on the devices.
  • In network-level packet loss measurement, the device can color known IP unicast packets but not MPLS packets or unknown IP unicast packets.
  • Network-level packet loss measurement is based on target flows, you can specify target flows. If the packet content is modified (for example, NAT is performed on packets, packets are encapsulated in tunnels, and packet priority is changed), the device cannot precisely match the packets, so the measurement result may be inaccurate.
  • In an MPLS L2VPN scenario, network-level packet loss measurement cannot be configured, including end-to-end packet loss measurement, regional network packet loss measurement, and network-level hop-by-hop packet loss measurement.
  • In an MPLS L3VPN scenario, end-to-end packet loss measurement can be configured on private network interfaces of PEs, regional network packet loss measurement can be configured on the CEs, and network-level hop-by-hop packet loss measurement cannot be configured.
  • End-to-end and regional network packet loss measurement support on-demand and proactive packet loss measurement. Network-level hop-by-hop packet loss measurement only supports on-demand packet loss measurement.

Networking Requirements

As shown in Figure 1, an enterprise leases the dedicated line from the carrier to transmit important services between headquarters and branches over the WAN. The source address segment is 10.1.1.0/24 and destination address segment is 10.2.0.0/16. The service packets of the enterprise need to pass a large number of carrier routing and switching devices. The dedicated line expensive, and the enterprise requires the packet loss data of the WAN to request the carrier to improve service quality.

Figure 1 Networking diagram of regional network packet loss measurement

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure the important service flow (source address segment 10.1.1.0/24 and destination address segment 10.2.0.0/16) transmitted over the dedicated line as the target flow. It is a unidirectional service flow.

  2. Configure egress devices Switch_1 and Switch_2 as DCPs. Bind GE1/0/1 where the target flow passes to out-point ingress TLPs of DCPs. Define measurement instance 1 on Switch_1 and Switch_2 to collect statistics data of the target flow from TLPs.

  3. Configure egress device Switch_3 as a DCP. Bind GE1/0/1 where the target flow passes to in-point egress TLP of the DCP. Define instance 1 on Switch_3 to collect statistics data of the target flow from TLPs.

  4. Configure Switch_4 in the headquarters network management center as the MCP to collect the statistics data from DCPs. Configure packet loss alarm and clear alarm thresholds. When the packet loss ratio exceeds 5%, an alarm is reported; when the packet loss ratio falls back below 3%, a clear alarm is reported.

  5. Retain the default values of color bit, measurement interval, and UDP port number.

Before configuring iPCA to implement regional network packet loss measurement, ensure that static routes or dynamic routing protocols have been configured to implement network connectivity between Switch_1, Switch_2, Switch_3, and Switch_4. The DCP ID or MCP ID of each switch must be an existing IP address, and the IP addresses must be reachable to each other.

Before configuring iPCA to implement regional network packet loss measurement, ensure that NTP has been configured to implement time synchronization between Switch_1, Switch_2, and Switch_3.

Procedure

  1. Configure Switch_1 as DCP1, set the DCP ID of Switch_1 to the router ID 10.10.1.1, and configure TLP 1. 

    <HUAWEI> system-view
[HUAWEI] sysname Switch_1
[Switch_1] nqa ipfpm dcp //Enable the global DCP function.
[Switch_1-nqa-ipfpm-dcp] dcp id 10.10.1.1 //Set the DCP ID to 10.10.1.1.
[Switch_1-nqa-ipfpm-dcp] instance 1 //Create measurement instance 1 on the DCP.
[Switch_1-nqa-ipfpm-dcp-instance-1] mcp 10.10.4.1 //Associate measurement instance 1 with an MCP.
[Switch_1-nqa-ipfpm-dcp-instance-1] flow forward source 10.1.1.0 24 destination 10.2.0.0 16 //Configure the target flow in measurement instance 1 as a forward flow with the source address segment 10.1.1.0 and destination address segment 10.2.0.0.
[Switch_1-nqa-ipfpm-dcp-instance-1] tlp 1 out-point ingress //Set the TLP ID to 1 and configure the TLP to color the outgoing target flow. The target flow arrives at the TLP.
[Switch_1-nqa-ipfpm-dcp-instance-1] quit
[Switch_1-nqa-ipfpm-dcp] quit
[Switch_1] interface gigabitethernet 1/0/1
[Switch_1-GigabitEthernet1/0/1] ipfpm tlp 1 //Bind the interface to the TLP.
[Switch_1-GigabitEthernet1/0/1] quit
[Switch_1] nqa ipfpm dcp 
[Switch_1-nqa-ipfpm-dcp] instance 1 
[Switch_1-nqa-ipfpm-dcp-instance-1] loss-measure enable continual //Enable continual packet loss measurement.
[Switch_1-nqa-ipfpm-dcp-instance-1] quit
[Switch_1-nqa-ipfpm-dcp] quit

  2. Configure Switch_2 as DCP2, set the DCP ID of Switch_2 to the router ID 10.10.2.1, and configure TLP 2. 

    <HUAWEI> system-view
[HUAWEI] sysname Switch_2
[Switch_2] nqa ipfpm dcp
[Switch_2-nqa-ipfpm-dcp] dcp id 10.10.2.1
[Switch_2-nqa-ipfpm-dcp] instance 1
[Switch_2-nqa-ipfpm-dcp-instance-1] mcp 10.10.4.1
[Switch_2-nqa-ipfpm-dcp-instance-1] flow forward source 10.1.1.0 24 destination 10.2.0.0 16
[Switch_2-nqa-ipfpm-dcp-instance-1] tlp 2 out-point ingress
[Switch_2-nqa-ipfpm-dcp-instance-1] quit
[Switch_2-nqa-ipfpm-dcp] quit
[Switch_2] interface gigabitethernet 1/0/1
[Switch_2-GigabitEthernet1/0/1] ipfpm tlp 2
[Switch_2-GigabitEthernet1/0/1] quit
[Switch_2] nqa ipfpm dcp
[Switch_2-nqa-ipfpm-dcp] instance 1
[Switch_2-nqa-ipfpm-dcp-instance-1] loss-measure enable continual
[Switch_2-nqa-ipfpm-dcp-instance-1] quit
[Switch_2-nqa-ipfpm-dcp] quit

  3. Configure Switch_3 as DCP3, set the DCP ID of Switch_3 to the router ID 10.10.3.1, and configure TLP 3. 

    <HUAWEI> system-view
[HUAWEI] sysname Switch_3
[Switch_3] nqa ipfpm dcp
[Switch_3-nqa-ipfpm-dcp] dcp id 10.10.3.1
[Switch_3-nqa-ipfpm-dcp] instance 1
[Switch_3-nqa-ipfpm-dcp-instance-1] mcp 10.10.4.1
[Switch_3-nqa-ipfpm-dcp-instance-1] flow forward source 10.1.1.0 24 destination 10.2.0.0 16
[Switch_3-nqa-ipfpm-dcp-instance-1] tlp 3 in-point egress
[Switch_3-nqa-ipfpm-dcp-instance-1] quit
[Switch_3-nqa-ipfpm-dcp] quit
[Switch_3] interface gigabitethernet 1/0/1
[Switch_3-GigabitEthernet1/0/1] ipfpm tlp 3
[Switch_3-GigabitEthernet1/0/1] quit
[Switch_3] nqa ipfpm dcp
[Switch_3-nqa-ipfpm-dcp] instance 1
[Switch_3-nqa-ipfpm-dcp-instance-1] loss-measure enable continual
[Switch_3-nqa-ipfpm-dcp-instance-1] quit
[Switch_3-nqa-ipfpm-dcp] quit

  4. Configure Switch_4 as the MCP and set the MCP ID of Switch_4 to the router ID 10.10.4.1. 

    <HUAWEI> system-view
[HUAWEI] sysname Switch_4
[Switch_4] nqa ipfpm mcp //Enable the global MCP function.
[Switch_4-nqa-ipfpm-mcp] mcp id 10.10.4.1 //Set the MCP ID to 10.10.4.1.
[Switch_4-nqa-ipfpm-mcp] instance 1 //Create measurement instance 1 on the MCP.
[Switch_4-nqa-ipfpm-mcp-instance-1] dcp 10.10.1.1 //Associate measurement instance 1 with the DCP whose ID is 10.10.1.1.
[Switch_4-nqa-ipfpm-mcp-instance-1] dcp 10.10.2.1 //Associate measurement instance 1 with the DCP whose ID is 10.10.2.1.
[Switch_4-nqa-ipfpm-mcp-instance-1] dcp 10.10.3.1 //Associate measurement instance 1 with the DCP whose ID is 10.10.3.1.
[Switch_4-nqa-ipfpm-mcp-instance-1] loss-measure ratio-threshold upper-limit 5 lower-limit 3 //Set the packet loss alarm threshold to 5% and clear alarm threshold to 3%.
[Switch_4-nqa-ipfpm-mcp-instance-1] quit
[Switch_4-nqa-ipfpm-mcp] quit
[Switch_4] quit

  5. Verify the configuration.

    # Run the display ipfpm statistic-type loss instance 1 command on Switch_4 that functions as the MCP to view the packet loss measurement result.

    <Switch_4> display ipfpm statistic-type loss instance 1

Latest loss statistics of forward flow:
Unit: p - packet, b - byte
------------------------------------------------------------------------------------------
 Period               Loss(p)              LossRatio(p)  Loss(b)              LossRatio(b) 
------------------------------------------------------------------------------------------
 127636768            381549               4.514649%     40444194             4.514649%    
 127636767            381528               4.514620%     40441968             4.514620%    
 127636766            381318               4.514996%     40419708             4.514996%    
 127636765            381192               4.514686%     40406352             4.514686%    
 127636764            381381               4.514679%     40426386             4.514679%    
 127636763            381402               4.514748%     40428612             4.514748%    
 127636762            381081               4.514797%     40394586             4.514797%    
 127636761            381324               4.514702%     40420344             4.514702%    
 127636760            381549               4.514870%     40444194             4.514870%    
 127636759            381066               4.514638%     40392996             4.514638%    
 127636758            381570               4.514836%     40446420             4.514836%    
 127636757            382452               4.514757%     40539912             4.514757%    

Latest loss statistics of backward flow:
Unit: p - packet, b - byte
------------------------------------------------------------------------------------------
 Period               Loss(p)              LossRatio(p)  Loss(b)              LossRatio(b) 
------------------------------------------------------------------------------------------

Configuration Files

  • Configuration file of Switch_1

    #
sysname Switch_1
#
interface GigabitEthernet1/0/1
 ipfpm tlp 1
#
nqa ipfpm dcp
 dcp id 10.10.1.1
 instance 1
  mcp 10.10.4.1
  flow forward source 10.1.1.0 24 destination 10.2.0.0 16
  tlp 1 out-point ingress
  loss-measure enable continual
#
return

  • Configuration file of Switch_2

    #
sysname Switch_2
#
interface GigabitEthernet1/0/1
 ipfpm tlp 2
#
nqa ipfpm dcp
 dcp id 10.10.2.1
 instance 1
  mcp 10.10.4.1
  flow forward source 10.1.1.0 24 destination 10.2.0.0 16
  tlp 2 out-point ingress
  loss-measure enable continual
#
return

  • Configuration file of Switch_3

    #
sysname Switch_3
#
interface GigabitEthernet1/0/1
 ipfpm tlp 3
#
nqa ipfpm dcp
 dcp id 10.10.3.1
 instance 1
  mcp 10.10.4.1
  flow forward source 10.1.1.0 24 destination 10.2.0.0 16
  tlp 3 in-point egress
  loss-measure enable continual
#
return

  • Configuration file of Switch_4

    #
sysname Switch_4
#
nqa ipfpm mcp
 mcp id 10.10.4.1
 instance 1
  dcp 10.10.1.1
  dcp 10.10.2.1
  dcp 10.10.3.1
  loss-measure ratio-threshold upper-limit 5.000000 lower-limit 3.000000
#
return

Applicable product models and versions

Product

Product Model

Software Version

S5700

S5720-HI

V200R006C00, V200R007(C00&C10), V200R008C00, V200R009C00, V200R010C00, V200R011C00, V200R011C10, V200R012C00, V200R013C00, V200R019C00, V200R019C10

S5730-HI

V200R012C00, V200R013C00, V200R019C00, V200R019C10

S5731-H

V200R013C02, V200R019C00, V200R019C10

S5731-S, S5731S-S

V200R019C00, V200R019C10

S5731S-H

V200R019C00, V200R019C10

S5732-H

V200R019C00, V200R019C10

S6700

S6720-HI

V200R012C00, V200R013C00, V200R019C00, V200R019C10

S6730-H

V200R013C02, V200R019C00, V200R019C10

S6730S-H

V200R019C10

S6730-S, S6730S-S

V200R019C00, V200R019C10

S7700

S7703, S7706, S7712

V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00, V200R013C00, V200R013C02, V200R019C00, V200R019C10

S7703 PoE

V200R013C00, V200R019C00, V200R019C10

S7706 PoE

V200R013C00, V200R019C00, V200R019C10

S9700

S9703, S9706, S9712

V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00, V200R013C00

For modular switches, only the X series cards support iPCA.

Parent Topic: Typical iPCA Configuration
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >