No relevant resource is found in the selected language.
Enterprise
Worldwide
Search
Support Documentation
S300, S500, S2700, S3700, S5700, S6700, S7700, and S9700 Series Switches Typical Configuration Examples

This document provides campus networks typical configuration examples and feature typical configuration examples. "Campus Networks Typical Configuration Examples" provides typical campus network networking modes and a variety of deployment examples."Feature Typical Configuration Examples" provides typical configuration examples of a single feature on a switch. You can configure required features after deploying a campus network.

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 iPCA Configuration

Typical iPCA Configuration

Locating Faults Using iPCA and Point by Point Detect Configured on eSight

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.

Configuring iPCA on eSight and delivering iPCA configuration to the switch can simplify configurations and make statistics result visible. Point by Point Detect can implement network-level hop-by-hop packet loss measurement. If packet loss occurs, the packet loss point is quickly detected.

Configuration Notes

  • This example applies to the following products and versions:

    • Modular switches and S5720-HI: V200R008C00 and later versions

    • S5730-HI, S5731-H, S5731-S, S5731S-S, S5731S-H, S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, S6730S-S: For the applicable versions, see Table 1 in the section "Applicable Products and Versions."
  • For modular switches, only the X series cards support iPCA.
  • This example shows how to configure iPCA on eSight to collect statistics on lost packets hop by hop. In this example, the switch version is V200R008C00 and eSight version is V300R005C00.
  • 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

On the network shown in Figure 3-290, Tester 1 repeatedly sends packets to Tester 2, and a QoS policy is configured in the outbound direction of GE0/0/1 on the device HUAWEI to discard some packets of the target flow. iPCA is configured on eSight. You can see the packet loss point in the topology view. In practice, you can quickly detect the failure point using this function.

Figure 3-290 Networking diagram of hop-by-hop packet loss measurement

Data Planning

Table 3-199 Basic Data Plan

Item

Interface

VLAN ID

IP Address

S12708 (In-point)

GE8/1/16

100

VLANIF100: 172.16.14.112/24

GE8/1/18

20

VLANIF20: 192.168.49.1/24

GE8/1/20

21

VLANIF21: 192.168.52.1/24

HUAWEI (Mid-point)

GE0/0/1

22

VLANIF22: 192.168.53.1/24

GE0/0/2

200

VLANIF200: 172.16.9.90/24

GE0/0/20

21

VLANIF21: 192.168.52.2/24

S12704 (Out-point)

GE3/1/1

22

VLANIF22: 192.168.53.2/24

GE3/1/2

200

VLANIF200: 172.16.9.91/24

GE3/1/7

23

VLANIF23: 192.168.54.1/24

Configuration Roadmap

  1. Configure the switches S12708, HUAWEI, and S12704:
    1. Allocate VLANs based on interfaces and assign IP addresses to VLANIF interfaces.
    2. Configure routes.
    3. Configure SNMP and Telnet.
    4. Configure NTP.
    5. Configure the MCP (HUAWEI).
  2. Configure the eSight:
    1. Add Resource.
    2. Configure iPCA.
    3. Check real-time statistics before QoS policy is delivered.
    4. Configure the QoS policy.
    5. Check real-time statistics after QoS policy is delivered.
    6. Perform Point by Point Detect.

Procedure

  1. Configure the switches S12708, HUAWEI, and S12704.
    1. Allocate VLANs based on interfaces and assign IP addresses to VLANIF interfaces.

      # Configure the S12708.
      <HUAWEI> system-view
[HUAWEI] sysname S12708
[S12708] vlan batch 20 21 100
[S12708] interface GigabitEthernet 8/1/16
[S12708-GigabitEthernet8/1/16] port link-type trunk
[S12708-GigabitEthernet8/1/16] port trunk pvid vlan 100
[S12708-GigabitEthernet8/1/16] port trunk allow-pass vlan 100
[S12708-GigabitEthernet8/1/16] quit
[S12708] interface GigabitEthernet 8/1/18
[S12708-GigabitEthernet8/1/18] port link-type access
[S12708-GigabitEthernet8/1/18] port default vlan 20
[S12708-GigabitEthernet8/1/18] quit
[S12708] interface GigabitEthernet 8/1/20
[S12708-GigabitEthernet8/1/20] port link-type trunk
[S12708-GigabitEthernet8/1/20] port trunk pvid vlan 21
[S12708-GigabitEthernet8/1/20] port trunk allow-pass vlan 21
[S12708-GigabitEthernet8/1/20] quit
[S12708] interface Vlanif100
[S12708-Vlanif100] ip address 172.16.14.112 24
[S12708-Vlanif100] quit
[S12708] interface Vlanif20
[S12708-Vlanif20] ip address 192.168.49.1 24
[S12708-Vlanif20] quit
[S12708] interface Vlanif21
[S12708-Vlanif21] ip address 192.168.52.1 24
[S12708-Vlanif21] quit
      # Configure the HUAWEI.
      <HUAWEI> system-view
[HUAWEI] vlan batch 21 22 200
[HUAWEI] interface GigabitEthernet 0/0/1
[HUAWEI-GigabitEthernet0/0/1] port link-type trunk
[HUAWEI-GigabitEthernet0/0/1] port trunk pvid vlan 22
[HUAWEI-GigabitEthernet0/0/1] port trunk allow-pass vlan 22
[HUAWEI-GigabitEthernet0/0/1] quit
[HUAWEI] interface GigabitEthernet 0/0/2
[HUAWEI-GigabitEthernet0/0/2] port link-type trunk
[HUAWEI-GigabitEthernet0/0/2] port trunk pvid vlan 200
[HUAWEI-GigabitEthernet0/0/2] port trunk allow-pass vlan 200
[HUAWEI-GigabitEthernet0/0/2] quit
[HUAWEI] interface GigabitEthernet 0/0/20
[HUAWEI-GigabitEthernet0/0/20] port link-type trunk
[HUAWEI-GigabitEthernet0/0/20] port trunk pvid vlan 21
[HUAWEI-GigabitEthernet0/0/20] port trunk allow-pass vlan 21
[HUAWEI-GigabitEthernet0/0/20] quit
[HUAWEI] interface Vlanif21
[HUAWEI-Vlanif21] ip address 192.168.52.2 24
[HUAWEI-Vlanif21] quit
[HUAWEI] interface Vlanif22
[HUAWEI-Vlanif22] ip address 192.168.53.1 24
[HUAWEI-Vlanif22] quit
[HUAWEI] interface Vlanif200
[HUAWEI-Vlanif200] ip address 172.16.9.90 24
[HUAWEI-Vlanif200] quit
      # Configure the S12704.
      <HUAWEI> system-view
[HUAWEI] sysname S12704
[S12704] vlan batch 22 23
[S12704] interface GigabitEthernet 3/1/1
[S12704-GigabitEthernet3/1/1] port link-type trunk
[S12704-GigabitEthernet3/1/1] port trunk pvid vlan 22
[S12704-GigabitEthernet3/1/1] port trunk allow-pass vlan 22
[S12704-GigabitEthernet3/1/1] quit
[S12704] interface GigabitEthernet 3/1/2
[S12704-GigabitEthernet3/1/2] port link-type trunk
[S12704-GigabitEthernet3/1/2] port trunk pvid vlan 200
[S12704-GigabitEthernet3/1/2] port trunk allow-pass vlan 200
[S12704-GigabitEthernet3/1/2] quit
[S12704] interface GigabitEthernet 3/1/7
[S12704-GigabitEthernet3/1/7] port link-type access
[S12704-GigabitEthernet3/1/7] port default vlan 23
[S12704-GigabitEthernet3/1/7] quit
[S12704] interface Vlanif22
[S12704-Vlanif22] ip address 192.168.53.2 24
[S12704-Vlanif22] quit
[S12704] interface Vlanif23
[S12704-Vlanif23] ip address 192.168.54.1 24
[S12704-Vlanif23] quit
[S12704] interface Vlanif200
[S12704-Vlanif200] ip address 172.16.9.91 24
[S12704-Vlanif200] quit

    2. Configure routes.

      # Configure the S12708.
      [S12708] ospf
[S12708-ospf-1] area 0
[S12708-ospf-1-area-0.0.0.0] network 192.168.49.0 0.0.0.255
[S12708-ospf-1-area-0.0.0.0] network 192.168.52.0 0.0.0.255
[S12708-ospf-1-area-0.0.0.0] quit
[S12708-ospf-1] quit
[S12708] ip route-static 0.0.0.0 0.0.0.0 172.16.14.1   //Configure a default route to the gateway.
      # Configure the HUAWEI.
      [HUAWEI] ospf
[HUAWEI-ospf-1] area 0
[HUAWEI-ospf-1-area-0.0.0.0] network 192.168.52.0 0.0.0.255
[HUAWEI-ospf-1-area-0.0.0.0] network 192.168.53.0 0.0.0.255
[HUAWEI-ospf-1-area-0.0.0.0] quit
[HUAWEI-ospf-1] quit
[HUAWEI] ip route-static 0.0.0.0 0.0.0.0 172.16.9.1
      # Configure the S12704.
      [S12704] ospf
[S12704-ospf-1] area 0
[S12704-ospf-1-area-0.0.0.0] network 192.168.53.0 0.0.0.255
[S12704-ospf-1-area-0.0.0.0] network 192.168.54.0 0.0.0.255
[S12704-ospf-1-area-0.0.0.0] quit
[S12704-ospf-1] quit
[S12704] ip route-static 0.0.0.0 0.0.0.0 172.16.9.1

    3. Configure SNMP and Telnet to ensure that the eSight can manage the switches. The configuration on S12708 is used as an example here. The configurations on the HUAWEI and S12704 are similar to the configuration on S12708, and are not mentioned here.

      # Configure SNMP.
      [S12708] snmp-agent   //Enable SNMP Agent. 
[S12708] snmp-agent protocol source-status all-interface  //Enable all interfaces to receive and respond to NMS requests. This configuration is mandatory in V200R020 and later versions.
[S12708] snmp-agent community read cipher public123   //Set the read community name to public123.
[S12708] snmp-agent community write cipher private123   //Set the write community name to private123.
[S12708] snmp-agent sys-info version all   //Enable all SNMP versions.
      # Configure Telnet.
      [S12708] telnet server enable   //Enable the Telnet server function. 
[S12708] telnet server-source all-interface  //Configure the source interface of the Telnet server to all interfaces configured with IPv4 addresses. This configuration is mandatory in V200R020 and later versions.
[S12708] user-interface vty 0 4
[S12708-ui-vty0-4] user privilege level 15   //Set the user level to 15.
[S12708-ui-vty0-4] protocol inbound telnet   //Set the login mode to Telnet.
[S12708-ui-vty0-4] authentication-mode password   //Set the authentication mode to password authentication.
[S12708-ui-vty0-4] set authentication password cipher Example@123   //Set the login password to Example@123.
[S12708-ui-vty0-4] quit

    4. Configure NTP.

      The iPCA devices must have time synchronized; therefore, NTP must be configured before iPCA is deployed.

      # Configure the HUAWEI as the NTP server.
      [HUAWEI] ntp-service source-interface Vlanif 21   //Set the local source interface that sends NTP packets to Vlanif21.
[HUAWEI] ntp-service refclock-master 1
[HUAWEI] undo ntp-service server disable   //Configure the switch as the NTP server.
      # Configure the S12708 as the NTP client.
      [S12708] ntp-service unicast-server 192.168.52.2   //Set the IP address of the NTP server to 192.168.52.2.
      # Configure the S12704 as the NTP client.
      [S12704] ntp-service unicast-server 192.168.52.2
      # Check whether time between the three switches is synchronized. For example, verify time synchronization on the S12704.
      [S12704] display ntp-service status
 clock status: synchronized   //The local clock has been synchronized with the NTP server.
 clock stratum: 2
 reference clock ID: 192.168.52.2   //The IP address of the NTP server is 192.168.52.2.
 nominal frequency: 100.0000 Hz
 actual frequency: 100.0000 Hz
 clock precision: 2^17
 clock offset: 19.8577 ms
 root delay: 2.25 ms
 root dispersion: 28.71 ms
 peer dispersion: 10.94 ms
 reference time: 20:18:31.232 UTC Dec 13 2016(DBFAD617.3B928E0C)
 synchronization state: clock synchronized

    5. Configure the MCP (HUAWEI).

      # Enable the SSH client.
      [HUAWEI] ssh client first-time enable

  2. Configure the eSight.
    1. Add Resource.

      # In this example, the eSight added S12708. The processes of adding HUAWEI and S12704 are similar, and are not mentioned here. Choose Resource > Add Resource in the upper navigation pane of the eSight. Configure the S12708 according to the figure. Set the Read community to public123, Write community to private123, and Password to Example@123, and click OK.

    2. Configure iPCA.

      # Choose Business > iPCA Management on the eSight homepage. Click Network-level on the left side and click Create on the right side to create the task 123. Configure the task according to the figure.

    3. Check real-time statistics before QoS policy is delivered.

      # Click the Query Real-time Data icon. In normal situations, there should be no packet loss between S12708 and S12704.

    4. Configure the QoS policy.

      1. Choose Configuration > Smart Configuration Tool on the eSight homepage. Click Template Deploy on the left side and choose Huawei > QoS Configuration > Interface QoS Configuration > Switch > Fixed Configuration Switch on the right side. Double-click Fixed Configuration Switch, after the configuration is complete, click Next.

        In this example, the QoS policy is used to simulate packet loss in order to show the hop-by-hop detection on the eSight. In practice, the QoS policy is not required.

      2. Click Add.

      3. Select HUAWEI (172.16.9.90) and click OK.

      4. Click Next.

      5. Select Instantly for Task type and click Deploy.

      6. Click Yes in the displayed dialog box to deliver the QoS policy.

    5. Check real-time statistics after QoS policy is delivered.

      # Click the Query Real-time Data icon. After the QoS policy is delivered, there is a severe packet loss between S12708 and S12704.

    6. Perform Point by Point Detect.

      1. When packet loss has happened, check each segment on the path to determine the packet loss point. Click Point by Point Detect.

      2. Click Detect Route.

      3. When the status changes to Route Detection Succeed, click Get Data.

      4. When the status changes to Collecting Data, you can see that the packet loss point between HUAWEI and S12704. Check the interface configurations. You can find that the packet loss point is on GE0/0/1 of HUAWEI, which is connected to S12704.

Configuration Files

  • S12708 configuration file
    #
sysname S12708
#
vlan batch 20 to 21 100
#
telnet server enable
//Configure the source interface of the Telnet server to all interfaces configured with IPv4 addresses. This configuration is mandatory in V200R020 and later versions.
telnet server-source all-interface 
#
ntp-service server disable
ntp-service ipv6 server disable
ntp-service unicast-server 192.168.52.2
#
interface Vlanif20
 ip address 192.168.49.1 255.255.255.0
#
interface Vlanif21
 ip address 192.168.52.1 255.255.255.0
#
interface Vlanif100
 ip address 172.16.14.112 255.255.255.0
#
interface GigabitEthernet8/1/16
 port link-type trunk
 port trunk pvid vlan 100
 port trunk allow-pass vlan 100
# 
interface GigabitEthernet8/1/18
 port link-type access
 port default vlan 20
 ipfpm tlp 9
# 
interface GigabitEthernet8/1/20
 port link-type trunk
 port trunk pvid vlan 21
 port trunk allow-pass vlan 21
 ipfpm tlp 15
#
ospf 1
 area 0.0.0.0
  network 192.168.49.0 0.0.0.255
  network 192.168.52.0 0.0.0.255
# 
ip route-static 0.0.0.0 0.0.0.0 172.16.14.1
#
snmp-agent
snmp-agent community read cipher %^%#eDeVP&K\5A,]8f$D4/C4y%h"2<w%4Y$*&bU2\$lXx7tHL5)y'W-<~SfGIFv98C):GzYCO[\,G"@e!%^%#
snmp-agent community write cipher %^%##t3d@h\k-4/vJqQPWih@"W+^MOv%RI@W056.3&oM"DiQY(m)C04qqcG*rl#Ps%`>4HF-O'Rb)eD,W.X$%^%#
snmp-agent sys-info version all
#
nqa ipfpm dcp
 dcp id 172.16.14.112
 mcp 172.16.9.90
 instance 4
  flow bidirectional source 192.168.49.0 24 destination 192.168.54.0 24
  tlp 9 in-point ingress
  tlp 15 mid-point flow bidirectional egress
  loss-measure enable continual
#
user-interface vty 0 4
 authentication-mode password
 user privilege level 15
 set authentication password cipher $1c$I",iD'G$4>$B+Ep3[K9!NFvdO$9s>B7E%q$T~E3l~s@dF6)OLEF$
 protocol inbound telnet
#
return
  • HUAWEI configuration file
    #
vlan batch 21 to 22 200
#
telnet server enable
//Configure the source interface of the Telnet server to all interfaces configured with IPv4 addresses. This configuration is mandatory in V200R020 and later versions.
telnet server-source all-interface 
#
ntp-service ipv6 server disable
ntp-service source-interface Vlanif21
ntp-service refclock-master 1
#
interface Vlanif21
 ip address 192.168.52.2 255.255.255.0
#
interface Vlanif22
 ip address 192.168.53.1 255.255.255.0
#
interface Vlanif200
 ip address 172.16.9.90 255.255.255.0
#
interface GigabitEthernet0/0/1
 port link-type trunk
 port trunk pvid vlan 22
 port trunk allow-pass vlan 22
 ipfpm tlp 17
 qos lr inbound cir 90000 cbs 11250000
#
interface GigabitEthernet0/0/2
 port link-type trunk
 port trunk pvid vlan 200
 port trunk allow-pass vlan 200
#
interface GigabitEthernet0/0/20
 port link-type trunk
 port trunk pvid vlan 21
 port trunk allow-pass vlan 21
 ipfpm tlp 16
#
ospf 1
 area 0.0.0.0
  network 192.168.52.0 0.0.0.255
  network 192.168.53.0 0.0.0.255
#
ip route-static 0.0.0.0 0.0.0.0 172.16.9.1
#
snmp-agent
snmp-agent community read cipher %^%#iPPB,G@4D4j/`oS}suRKw2l(Apd"z0Bx.3"7B(&A+b#v>G;4k~yOHWNbyB,7\y5fF!=E1*e{m~#kI28J%^%#
snmp-agent community write cipher %^%#+;QU),%}n:K`=v#EbI9M>f&PU+lo'C7[GMCx4^!#u^".-$l:@6b\tcB*dI"C@[ga+UgK~C<xO1F'FVm.%^%#
snmp-agent sys-info version all
//Enable all interfaces to receive and respond to NMS requests. This configuration is mandatory in V200R020 and later versions.
snmp-agent protocol source-status all-interface 
#
ssh client first-time enable                                                    
#
nqa ipfpm dcp
 dcp id 172.16.9.90
 mcp 172.16.9.90
 instance 4
  flow bidirectional source 192.168.49.0 24 destination 192.168.54.0 24
  tlp 16 mid-point flow bidirectional ingress
  tlp 17 mid-point flow bidirectional egress
#
nqa ipfpm mcp
 mcp id 172.16.9.90
 instance 4  
  dcp 172.16.9.90   
  dcp 172.16.9.91  
  dcp 172.16.14.112
  ach 1 
   flow forward 
   in-group dcp 172.16.14.112 tlp 9
   out-group dcp 172.16.14.112 tlp 15   
  ach 2 
   flow forward 
   in-group dcp 172.16.14.112 tlp 15    
   out-group dcp 172.16.9.90 tlp 16
  ach 3 
   flow forward 
   in-group dcp 172.16.9.90 tlp 16 
   out-group dcp 172.16.9.90 tlp 17
  ach 4 
   flow forward 
   in-group dcp 172.16.9.90 tlp 17 
   out-group dcp 172.16.9.91 tlp 18
  ach 5 
   flow forward 
   in-group dcp 172.16.9.91 tlp 18 
   out-group dcp 172.16.9.91 tlp 10
  ach 6 
   flow backward
   in-group dcp 172.16.9.91 tlp 10 
   out-group dcp 172.16.9.91 tlp 18
  ach 7 
   flow backward
   in-group dcp 172.16.9.91 tlp 18 
   out-group dcp 172.16.9.90 tlp 17
  ach 8 
   flow backward
   in-group dcp 172.16.9.90 tlp 17 
   out-group dcp 172.16.9.90 tlp 16
  ach 9 
   flow backward
   in-group dcp 172.16.9.90 tlp 16 
   out-group dcp 172.16.14.112 tlp 15   
  ach 10
   flow backward
   in-group dcp 172.16.14.112 tlp 15    
   out-group dcp 172.16.14.112 tlp 9    
#  
user-interface vty 0 4  
 authentication-mode password   
 user privilege level 15
 set authentication password cipher $1c$I",iD'G$4>$B+Ep3[K9!NFvdO$9s>B7E%q$T~E3l~s@dF6)OLEF$    
 protocol inbound telnet   
#  
return
  • S12704 configuration file
    #
sysname S12704
#
vlan batch 22 to 23 200
#
telnet server enable
//Configure the source interface of the Telnet server to all interfaces configured with IPv4 addresses. This configuration is mandatory in V200R020 and later versions.
telnet server-source all-interface 
#
ntp-service server disable
ntp-service ipv6 server disable
ntp-service unicast-server 192.168.52.2
#
interface Vlanif22
 ip address 192.168.53.2 255.255.255.0
#
interface Vlanif23
 ip address 192.168.54.1 255.255.255.0
#
interface Vlanif200
 ip address 172.16.9.91 255.255.255.0
# 
interface GigabitEthernet3/1/1
 port link-type trunk
 port trunk pvid vlan 22
 port trunk allow-pass vlan 22
 ipfpm tlp 18
#
interface GigabitEthernet3/1/2
 port link-type trunk
 port trunk pvid vlan 200
 port trunk allow-pass vlan 200
#  
interface GigabitEthernet3/1/7
 port link-type access
 port default vlan 23
 ipfpm tlp 10
#
ospf 1
 area 0.0.0.0
  network 192.168.53.0 0.0.0.255
  network 192.168.54.0 0.0.0.255
#
ip route-static 0.0.0.0 0.0.0.0 172.16.9.1
#
snmp-agent 
snmp-agent community read cipher %^%#$}!qC&[UR$>5i_1gJL*Q_HunMK88-JL%l[(1ABRP[5}n9dBKz%OM>QLRH+7IeAePK8u8$@/$xZQVHFxC%^%#
snmp-agent community write cipher %^%#RD%C78I\F&'asu>7~/P-ah]H-zwjMW}B7w3qJ8B&Gs/jF8*d%$aV^1H.g;j+-><p8//Y3;i4#j5Ro7w-%^%#
snmp-agent sys-info version all
//Enable all interfaces to receive and respond to NMS requests. This configuration is mandatory in V200R020 and later versions.
snmp-agent protocol source-status all-interface 
#
nqa ipfpm dcp
 dcp id 172.16.9.91
 mcp 172.16.9.90
 instance 4
  flow bidirectional source 192.168.49.0 24 destination 192.168.54.0 24
  tlp 10 out-point egress
  tlp 18 mid-point flow bidirectional ingress
  loss-measure enable continual 
#
user-interface vty 0 4
 authentication-mode password
 user privilege level 15
 set authentication password cipher $1c$I",iD'G$4>$B+Ep3[K9!NFvdO$9s>B7E%q$T~E3l~s@dF6)OLEF$
 protocol inbound telnet
#
return

Example for Configuring iPCA to Implement End-to-End 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.

End-to-end packet loss measurement: Statistics are collected on edge devices that are a part of the transit network. This method is applicable to packet loss measurement for a specialized service flow, such as a voice flow and a video flow, on an enterprise network.

Configuration Notes

  • This example applies to the following products and versions:

    • Modular switches: V200R006C00 and later versions

    • S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-S, S5731S-H, S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, S6730S-S: For the applicable versions, see Table 1 in the section "Applicable Products and Versions."
  • For modular switches, only the X series cards support iPCA.
  • 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 3-291, users in enterprise branches and headquarters encounter erratic display and delay when using the video conference service. The enterprise wants to obtain packet loss statistics of the video conference service and receive an alarm when the packet loss ratio exceeds 7% so that the network administrator can adjust service deployment in a timely manner.

Figure 3-291 Networking diagram of end-to-end packet loss measurement

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure a service flow between video terminals as a target flow. It is a bidirectional symmetrical flow, so is divided into two unidirectional flows logically.

  2. Configure Switch_1 as DCP1. Bind GE1/0/1 where the target flow passes to in-point ingress TLP of DCP1. Define instance 1 on DCP1 to collect statistics data of the target flow from TLPs.

  3. Configure Switch_2 as DCP2. Bind GE1/0/1 where the target flow passes to out-point egress TLP of DCP2. Define instance 1 on DCP2 to collect statistics data of the target flow from TLPs.

  4. Configure Switch_2 as the MCP to aggregate statistics data from DCP1 and DCP2 and export the statistics result. Configure packet loss alarm thresholds to help users predict network faults. When the packet loss ratio exceeds 7%, an alarm is reported; when the packet loss ratio falls back below 5%, a clear alarm is reported.

  5. Retain the default values of color bit, measurement interval, and UDP port number used for communication between DCPs and MCP.

Before configuring iPCA to implement end-to-end packet loss measurement, ensure that static routes or a dynamic routing protocol has been configured to implement network connectivity between Switch_1 and Switch_2. 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 end-to-end packet loss measurement, ensure that NTP has been configured to implement time synchronization between Switch_1 and Switch_2.

Procedure

  1. Configure Switch_1 as DCP1, set the DCP ID of Switch_1 to the router ID 10.1.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.1.1.1 //Set the DCP ID to 10.1.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.2.1.1 //Associate measurement instance 1 with an MCP.
[Switch_1-nqa-ipfpm-dcp-instance-1] flow bidirectional source 10.1.1.0 24 destination 10.2.1.0 24 //Configure the target flow in measurement instance 1 as a bidirectional symmetrical flow with the source address segment 10.1.1.0 and destination address segment 10.2.1.0.
[Switch_1-nqa-ipfpm-dcp-instance-1] tlp 1 in-point ingress //Set the TLP ID to 1 and configure the TLP to color the incoming 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.2.1.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.2.1.1
[Switch_2-nqa-ipfpm-dcp] instance 1
[Switch_2-nqa-ipfpm-dcp-instance-1] mcp 10.2.1.1
[Switch_2-nqa-ipfpm-dcp-instance-1] flow bidirectional source 10.1.1.0 24 destination 10.2.1.0 24
[Switch_2-nqa-ipfpm-dcp-instance-1] tlp 2 out-point egress
[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_2 as the MCP.

    [Switch_2] nqa ipfpm mcp //Enable the global MCP function.
[Switch_2-nqa-ipfpm-mcp] mcp id 10.2.1.1 //Set the MCP ID to 10.2.1.1.
[Switch_2-nqa-ipfpm-mcp] instance 1 //Create measurement instance 1 on the MCP.
[Switch_2-nqa-ipfpm-mcp-instance-1] dcp 10.1.1.1 //Associate measurement instance 1 with the DCP whose ID is 10.1.1.1.
[Switch_2-nqa-ipfpm-mcp-instance-1] dcp 10.2.1.1 //Associate measurement instance 1 with the DCP whose ID is 10.2.1.1.
[Switch_2-nqa-ipfpm-mcp-instance-1] loss-measure ratio-threshold upper-limit 7 lower-limit 5 //Set the packet loss alarm threshold to 7% and clear alarm threshold to 5%.
[Switch_2-nqa-ipfpm-mcp-instance-1] quit
[Switch_2-nqa-ipfpm-mcp] quit
[Switch_2] quit

  4. Verify the configuration.

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

    <Switch_2> 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) 
------------------------------------------------------------------------------------------
 127636768            381087               4.513306%     40395222             4.513306%    
 127636767            381129               4.513384%     40399674             4.513384%    
 127636766            381465               4.513444%     40435290             4.513444%    
 127636765            381087               4.513222%     40395222             4.513222%    
 127636764            381045               4.513272%     40390770             4.513272%    
 127636763            381381               4.513364%     40426386             4.513364%    
 127636762            381276               4.513435%     40415256             4.513435%    
 127636761            380961               4.513280%     40381866             4.513280%    
 127636760            381339               4.513574%     40421934             4.513574%    
 127636759            381045               4.513270%     40390770             4.513270%    
 127636758            381088               4.513226%     40395328             4.513226%    
 127636757            382409               4.513464%     40535354             4.513464%

Configuration Files

  • Configuration file of Switch_1

    #
sysname Switch_1
#
interface GigabitEthernet1/0/1
 ipfpm tlp 1
#
nqa ipfpm dcp
 dcp id 10.1.1.1
 instance 1
  mcp 10.2.1.1
  flow bidirectional source 10.1.1.0 24 destination 10.2.1.0 24
  tlp 1 in-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.2.1.1
 instance 1
  mcp 10.2.1.1
  flow bidirectional source 10.1.1.0 24 destination 10.2.1.0 24
  tlp 2 out-point egress
  loss-measure enable continual
#
nqa ipfpm mcp
 mcp id 10.2.1.1
 instance 1
  dcp 10.1.1.1
  dcp 10.2.1.1
  loss-measure ratio-threshold upper-limit 7.000000 lower-limit 5.000000
#
return

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

  • This example applies to the following products and versions:

    • Modular switches: V200R006C00 and later versions

    • S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-S, S5731S-H, S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, S6730S-S: For the applicable versions, see Table 1 in the section "Applicable Products and Versions."
  • For modular switches, only the X series cards support iPCA.
  • 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 3-292, 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 3-292 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

Example for Configuring iPCA to Implement Hop-by-Hop 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.

Hop-by-hop packet loss measurement: Statistics are collected on every device on the network. If you want to locate the network node where packet loss occurs, you can use this method.

Configuration Notes

  • This example applies to the following products and versions:

    • Modular switches: V200R006C00 and later versions

    • S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-S, S5731S-H, S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, S6730S-S: For the applicable versions, see Table 1 in the section "Applicable Products and Versions."
  • For modular switches, only the X series cards support iPCA.
  • 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 3-293, users in enterprise branches and headquarters encounter erratic display and delay when using the video conference service. Network-level end--to-end packet loss measurement has been deployed, and packet loss on the transit network has been detected. To find out where packets are lost in a specified network range, hop-by-hop packet loss measurement must be configured for the specified service flow.

Figure 3-293 Networking diagram of hop-by-hop packet loss measurement

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure hop-by-hop packet loss measurement between Switch_1 and Switch_3 to locate faults on the transit network based on network segments. According to the Atomic Closed Hop (ACH) rule, divide the link between Switch_1 and Switch_3 into two ACHs: ACH1 { TLP 100, TLP 200 } and ACH2 { TLP 200, TLP 310 }.

  2. Configure Switch_1 as the MCP to collect packet loss statistics from DCP1, DCP2, and DCP3, summarize and calculate the statistical data, and report the statistical results to user terminals or NMS.

  3. Configure the IP FPM packet loss alarm threshold and recovery threshold on Switch_1 so that Switch_1 can send alarms to the NMS and notify the NMS of link status in real time.

  4. Configure Switch_1, Switch_2, and Switch_3 as DCPs to control and manage TLP 100, TLP 200, and TLP 310, collect packet loss statistics, and send the statistics to the MCP.

  5. Retain the default values of UDP port number and authentication methods used by DCPs and MCP.

Before configuring iPCA network-level hop-by-hop packet loss measurement, ensure that static routes or dynamic routing protocols have been configured to implement network connectivity between Switch_1, Switch_2, and Switch_3. 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 network-level hop-by-hop 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 the MCP and set the MCP ID of Switch_1 to the router ID 10.10.1.1.

    <HUAWEI> system-view
[HUAWEI] sysname Switch_1
[Switch_1] nqa ipfpm mcp //Enable the global MCP function.
[Switch_1-nqa-ipfpm-mcp] mcp id 10.10.1.1 //Set the MCP ID to 10.10.1.1.
[Switch_1-nqa-ipfpm-mcp] instance 1 //Create measurement instance 1 on the MCP.
[Switch_1-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_1-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_1-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_1-nqa-ipfpm-mcp-instance-1] loss-measure ratio-threshold upper-limit 7 lower-limit 5 //Set the packet loss alarm threshold to 7% and clear alarm threshold to 5%.
[Switch_1-nqa-ipfpm-mcp-instance-1] ach 1 //Configure ACH 1.
[Switch_1-nqa-ipfpm-mcp-instance-1-ach-1] flow forward //Configure the target flow direction in the ACH view to forward.
[Switch_1-nqa-ipfpm-mcp-instance-1-ach-1] in-group dcp 10.10.1.1 tlp 100 //Set the ID of the DCP to which TLPs in the TLP in-group for the target flow belongs to 10.10.1.1 and set the TLP ID to 100.
[Switch_1-nqa-ipfpm-mcp-instance-1-ach-1] out-group dcp 10.10.2.1 tlp 200 //Set the ID of the DCP to which TLPs in the TLP out-group for the target flow belongs to 10.10.2.1 and set the TLP ID to 200.
[Switch_1-nqa-ipfpm-mcp-instance-1-ach-1] quit
[Switch_1-nqa-ipfpm-mcp-instance-1] ach 2 //Configure ACH 2.
[Switch_1-nqa-ipfpm-mcp-instance-1-ach-2] flow forward //Configure the target flow direction in the ACH view to forward.
[Switch_1-nqa-ipfpm-mcp-instance-1-ach-2] in-group dcp 10.10.2.1 tlp 200 //Set the ID of the DCP to which TLPs in the TLP in-group for the target flow belongs to 10.10.2.1 and set the TLP ID to 200.
[Switch_1-nqa-ipfpm-mcp-instance-1-ach-2] out-group dcp 10.10.3.1 tlp 310 //Set the ID of the DCP to which TLPs in the TLP out-group for the target flow belongs to 10.10.3.1 and set the TLP ID to 310.
[Switch_1-nqa-ipfpm-mcp-instance-1-ach-2] quit
[Switch_1-nqa-ipfpm-mcp-instance-1] quit
[Switch_1-nqa-ipfpm-mcp] quit

  2. Configure Switch_1 as DCP1 and configure TLP 100 on it.

    [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.1.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.1.0 24 //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.1.0.
[Switch_1-nqa-ipfpm-dcp-instance-1] tlp 100 in-point ingress //Set the TLP ID to 100 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 100 //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 time-range 30 //Enable statistics collection based on the time range for measurement instance 1 and set the time range for statistics collection to 30 minutes.
[Switch_1-nqa-ipfpm-dcp-instance-1] quit
[Switch_1-nqa-ipfpm-dcp] quit
[Switch_1] quit

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

    <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.1.1
[Switch_2-nqa-ipfpm-dcp-instance-1] flow forward source 10.1.1.0 24 destination 10.2.1.0 24
[Switch_2-nqa-ipfpm-dcp-instance-1] tlp 200 mid-point flow forward 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 200
[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 mid-point time-range 30
[Switch_2-nqa-ipfpm-dcp-instance-1] quit
[Switch_2-nqa-ipfpm-dcp] quit

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

    <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.1.1
[Switch_3-nqa-ipfpm-dcp-instance-1] flow forward source 10.1.1.0 24 destination 10.2.1.0 24
[Switch_3-nqa-ipfpm-dcp-instance-1] tlp 310 out-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 310
[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 time-range 30
[Switch_3-nqa-ipfpm-dcp-instance-1] quit
[Switch_3-nqa-ipfpm-dcp] quit

  5. Verify the configuration.

    # Run the display ipfpm statistic-type loss instance 1 ach 1 and display ipfpm statistic-type loss instance 1 ach 2 commands on Switch_1 that functions as the MCP to view the packet loss measurement result.

    The following uses ach 1 as an example. The values of Loss and LossRatio indicate whether packet loss occurs on ach 1.

    <Switch_1> display ipfpm statistic-type loss instance 1 ach 1

Latest loss statistics of forward flow:
Unit: p - packet, b - byte
------------------------------------------------------------------------------------------
 Period               Loss(p)              LossRatio(p)  Loss(b)              LossRatio(b)
------------------------------------------------------------------------------------------
 136190088            10                   10.000000%    1000                 10.000000%
 136190087            10                   12.000000%    1000                 12.000000%
 136190086            10                   10.000000%    1000                 10.000000%
 136190085            10                   12.000000%    1000                 12.000000%
 136190084            10                   10.000000%    1000                 10.000000%
 136190083            10                   11.000000%    1000                 11.000000%
 136190082            10                   10.000000%    1000                 10.000000%

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 100
#
nqa ipfpm dcp
 dcp id 10.10.1.1
 instance 1
  mcp 10.10.1.1
  flow forward source 10.1.1.0 24 destination 10.2.1.0 24
  tlp 100 in-point ingress
#
nqa ipfpm mcp
 mcp id 10.10.1.1
 instance 1
  dcp 10.10.1.1
  dcp 10.10.2.1
  dcp 10.10.3.1
  loss-measure ratio-threshold upper-limit 7.000000 lower-limit 5.000000
  ach 1
   flow forward
   in-group dcp 10.10.1.1 tlp 100
   out-group dcp 10.10.2.1 tlp 200
  ach 2
   flow forward
   in-group dcp 10.10.2.1 tlp 200
   out-group dcp 10.10.3.1 tlp 310
#
return

  • Configuration file of Switch_2

    #
sysname Switch_2
#
interface GigabitEthernet1/0/1
 ipfpm tlp 200
#
nqa ipfpm dcp
 dcp id 10.10.2.1
 instance 1
  mcp 10.10.1.1
  flow forward source 10.1.1.0 24 destination 10.2.1.0 24
  tlp 200 mid-point flow forward ingress
#
return

  • Configuration file of Switch_3

    #
sysname Switch_3
#
interface GigabitEthernet1/0/1
 ipfpm tlp 310
#
nqa ipfpm dcp
 dcp id 10.10.3.1
 instance 1
  mcp 10.10.1.1
  flow forward source 10.1.1.0 24 destination 10.2.1.0 24
  tlp 310 out-point egress
#
return

Example for Configuring iPCA to Implement Packet Loss Measurement on a Direct Link

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.

Statistics collection on a direct link: collects statistics on lost packets over the link between two directly connected devices.

Configuration Notes

  • This example applies to the following products and versions:

    • Modular switches: V200R006C00 and later versions

    • S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-S, S5731S-H, S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, S6730S-S: For the applicable versions, see Table 1 in the section "Applicable Products and Versions."
  • For modular switches, only the X series cards support iPCA.
  • The prerequisite of packet loss measurement for a direct link is time synchronization between iPCA devices. Therefore, before configuring iPCA, configure NTP on the devices.
  • You cannot specify target flows in packet loss measurement for direct links.
  • In device-level packet loss measurement for direct links, the device can color IP unicast packets (including known and unknown IP unicast packets) but not MPLS packets.

Networking Requirements

As shown in Figure 3-294, Switch_1, Switch_2, and Switch_3 are deployed on an enterprise network. Network-level packet loss measurement has been configured on the network, and the network administrator has known that packet loss occurred. To locate the packet loss point, the administrator wants to configure iPCA to implement packet loss measurement for direct links.

Figure 3-294 Networking diagram of packet loss measurement for direct links

Configuration Roadmap

The configuration roadmap is as follows:

  1. Enable packet loss measurement for direct links on interfaces at two ends of the link and configure the packet loss alarm so that you can know packet loss in a timely manner.

  2. Retain the default values of color bit and measurement interval.

Before configuring packet loss measurement for direct links, ensure that NTP has been configured to implement time synchronization between the directly connected devices.

The packet loss measurement configurations for the links between Switch_2 and Switch_3, and between Switch_1 and Switch_2 are the same. This example uses the link between Switch_1 and Switch_2 as an example.

Procedure

  1. Configure Switch_1.

    <HUAWEI> system-view
[HUAWEI] sysname Switch_1
[Switch_1] interface gigabitethernet 1/0/1
[Switch_1-GigabitEthernet1/0/1] iplpm link loss-measure alarm enable //Enable the alarm and clear alarm of the packet loss ratio for packet loss measurement on a direct link.
[Switch_1-GigabitEthernet1/0/1] iplpm link loss-measure enable //Enable packet loss measurement on a direct link.
[Switch_1-GigabitEthernet1/0/1] quit
[Switch_1] quit

  2. Configure Switch_2.

    <HUAWEI> system-view
[HUAWEI] sysname Switch_2
[Switch_2] interface gigabitethernet 1/0/1
[Switch_2-GigabitEthernet1/0/1] iplpm link loss-measure alarm enable
[Switch_2-GigabitEthernet1/0/1] iplpm link loss-measure enable
[Switch_2-GigabitEthernet1/0/1] quit
[Switch_2] quit

  3. Verify the configuration.

    # Run the display iplpm loss-measure statistics interface command on Switch_1 and Switch_2 to view packet loss measurement results.

    Switch_1 is used as an example here. The values of Loss Packets and LossRatio indicate whether packet loss occurs in the backward flows on GE1/0/1 of Switch_1.

    <Switch_1> display iplpm loss-measure statistics interface gigabitethernet 1/0/1
Latest forward loss statistics of interface GigabitEthernet1/0/1:
--------------------------------------------------------------------------------
 StartTime(DST)         Forward Loss Packets  Forward LossRatio   ErrorInfo     
--------------------------------------------------------------------------------
 2014-06-12 18:47:30    0                     0.000000%           OK            
 2014-06-12 18:47:20    0                     0.000000%           OK            
 2014-06-12 18:47:10    0                     0.000000%           OK            
 2014-06-12 18:47:00    0                     0.000000%           OK            
 2014-06-12 18:46:50    0                     0.000000%           OK            
 2014-06-12 18:46:40    0                     0.000000%           OK            
--------------------------------------------------------------------------------

Latest backward loss statistics of interface GigabitEthernet1/0/1:
--------------------------------------------------------------------------------
 StartTime(DST)         Backward Loss Packets  Backward LossRatio  ErrorInfo    
--------------------------------------------------------------------------------
 2014-06-12 18:47:30    344127                 4.513519%           OK           
 2014-06-12 18:47:20    381085                 4.513196%           OK           
 2014-06-12 18:47:10    381192                 4.513290%           OK           
 2014-06-12 18:47:00    381339                 4.513392%           OK           
 2014-06-12 18:46:50    381465                 4.513351%           OK           
 2014-06-12 18:46:40    381444                 4.513341%           OK           
--------------------------------------------------------------------------------

Configuration Files

  • Configuration file of Switch_1

    #
sysname Switch_1
#
interface GigabitEthernet1/0/1
 iplpm link loss-measure alarm enable
 iplpm link loss-measure enable
#
return

  • Configuration file of Switch_2

    #
sysname Switch_2
#
interface GigabitEthernet1/0/1
 iplpm link loss-measure alarm enable
 iplpm link loss-measure enable
#
return

Example for Configuring iPCA to Implement Packet Loss Measurement on a Device

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.

Statistics collection on a device: collects statistics on lost packets on all cards of a device.

Configuration Notes

  • This example applies to the following products and versions:

    • Modular switches: V200R006C00 and later versions

    • S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-S, S5731S-H, S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, S6730S-S: For the applicable versions, see Table 1 in the section "Applicable Products and Versions."
  • For modular switches, only the X series cards support iPCA.
  • You cannot specify target flows in packet loss measurement for a device.
  • In packet loss measurement for the entire device, the device can color known IP unicast packets but not MPLS packets or unknown IP unicast packets.
  • In MPLS L3VPN, packet loss measurement for the entire device is also supported if the device functions as only PE.

Networking Requirements

As shown in Figure 3-295, Switch_1, Switch_2, and Switch_3 are deployed on an enterprise network. Network-level packet loss measurement has been configured on the network, and the network administrator has known that packet loss occurred. To locate the device where packet loss occurred, the administrator wants to configure iPCA to implement packet loss measurement on a device.

Figure 3-295 Networking diagram of packet loss measurement on a device

Configuration Roadmap

The configuration roadmap is as follows:

  1. Enable iPCA on each device to implement packet loss measurement on the device so that you can know packet loss in a timely manner. Configure the packet loss alarm on each device.

  2. Retain the default values of color bit and measurement interval.

The packet loss measurement configuration on Switch_3 is the same as that on Switch_1 and Switch_2, and is not mentioned here.

Procedure

  1. Configure Switch_1.

    <HUAWEI> system-view
[HUAWEI] sysname Switch_1
[Switch_1] iplpm global loss-measure alarm enable //Enable the alarm and clear alarm of the packet loss ratio for device-level packet loss measurement.
[Switch_1] iplpm global loss-measure enable //Enable packet loss measurement for a device.
[Switch_1] quit

  2. Configure Switch_2.

    <HUAWEI> system-view
[HUAWEI] sysname Switch_2
[Switch_2] iplpm global loss-measure alarm enable
[Switch_2] iplpm global loss-measure enable
[Switch_2] quit

  3. Verify the configuration.

    # Run the display iplpm loss-measure statistics global command on Switch_1 and Switch_2 to view packet loss measurement results.

    Switch_1 is used as an example here. The values of Loss Packets and LossRatio indicate whether packet loss occurs on Switch_1.

    <Switch_1> display iplpm loss-measure statistics global
Latest global loss statistics:
--------------------------------------------------------------------------------
 StartTime(DST)        Loss Packets            LossRatio         ErrorInfo      
--------------------------------------------------------------------------------
 2014-06-12 18:47:30   344127                  4.513519%         OK 
 2014-06-12 18:47:20   381085                  4.513196%         OK 
 2014-06-12 18:47:10   381192                  4.513290%         OK 
 2014-06-12 18:47:00   381339                  4.513341%         OK 
 2014-06-12 18:46:50   381465                  4.513392%         OK 
 2014-06-12 18:46:40   381444                  4.513487%         OK 
 2014-06-12 18:46:30   381129                  4.513309%         OK 
--------------------------------------------------------------------------------

Configuration Files

  • Configuration file of Switch_1

    #
sysname Switch_1
#
iplpm global loss-measure alarm enable
iplpm global loss-measure enable
#
return

  • Configuration file of Switch_2

    #
sysname Switch_2
#
iplpm global loss-measure alarm enable
iplpm global loss-measure enable
#
return
Translation
Español 日本語 Русский 简体中文
Download
Updated: 2023-10-27

Document ID: EDOC1000069520

Views: 1928886

Downloads: 41883

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :