No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - System Monitor 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - System Monitor
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).
Configuring an RFC 2544 General Flow Test Instance

Configuring an RFC 2544 General Flow Test Instance

This section describes how to configure a general flow test instance to monitor the performance of interconnected network devices.

Applicable Environment

An NQA general flow test is a standard traffic testing method for evaluating network performance and is in compliance with RFC 2544. This test can be used in various networking scenarios that have different packet formats. NQA general flow tests are conducted using UDP packets with source UDP port 49184 and destination UDP port 7.

Before a customer performs a service cutover, an NQA general flow test helps the customer evaluate whether the network performance counters meet the requirements in the design. An NQA general flow test has the following advantages:

  • Enables a device to send simulated service packets to itself before services are deployed on the device.

    Existing methods, unlike general flow tests, can only be used when services have been deployed on networks. If no services are deployed, testers must be used to send and receive test packets.

  • Uses standard methods and procedures that comply with RFC 2544 so that NQA general flow tests can be conducted on a network on which both Huawei and non-Huawei devices are deployed.

A general flow test measures the following counters:

  • Throughput: maximum rate at which packets are sent without loss.
  • Packet loss rate: percentage of discarded packets to all sent packets.

  • Latency: consists of the bidirectional delay time and jitter calculated based on the transmission and receipt timestamps carried in test packets. The transmission time in each direction includes the time the forwarding devices process the test packet.

A general flow test can be used in the following scenarios:

  • Layer 2: native Ethernet, L2VPN (VLL and VPLS), EVPN

    On the network shown in Figure 4-1, an initiator and a reflector perform a general flow test to monitor the forwarding performance for end-to-end services exchanged between two user-to-network interfaces (UNIs).

    Figure 4-1 General flow test in a Layer 2 scenario

  • Layer 3: native IP scenario and L3VPN scenario

    Layer 3 networking is similar to Layer 2 networking.

  • L2VPN accessing L3VPN: VLL accessing L3VPN scenario

    Figure 4-2 General flow test in an L2VPN accessing L3VPN scenario

    In the L2VPN accessing L3VPN networking shown in Figure 4-2, the initiator and reflector can reside in different locations to represent different scenarios.
    • If the initiator and reflector reside in locations 1 and 5 (or 5 and 1), respectively, or the initiator and reflector reside in locations 4 and 6 (or 6 and 4), respectively, it is a native Ethernet scenario.

    • If the initiator and reflector reside in locations 2 and 3 (or 3 and 2), respectively, it is a native IP scenario.

    • If the initiator resides in location 3 and the reflector in location 1, or the initiator resides in location 2 and the reflector in location 4, it is similar to an IP gateway scenario, and the simulated IP address must be configured on the L2VPN device.

    • If the initiator and reflector reside in locations 1 and 2 (or 2 and 1), respectively, or the initiator and reflector reside in locations 3 and 4 (or 4 and 3), respectively, it is an IP gateway scenario.

    • If the initiator resides in location 1 and the reflector in location 4, the initiator resides in location 1 and the reflector in location 3, or the initiator resides in location 4 and the reflector in location 2, it is an L2VPN accessing L3VPN scenario. In this scenario, the destination IP and MAC addresses and the source IP address must be specified on the initiator, and the destination IP address for receiving test flows must be specified on the reflector. If the initiator resides on the L2VPN, the simulated IP address must be specified as the source IP address.

  • IP gateway scenario

    Layer 2 interface access to a Layer 3 device: IP gateway scenario

    Figure 4-3 shows the networking of the Layer 2 interface's access to a Layer 3 device.

    Figure 4-3 General flow test in the scenario in which a Layer 2 interface accesses a Layer 3 device

Pre-configuration Tasks

Before configuring an NQA general flow test, complete the following tasks:

  • Layer 2:
    • In a native Ethernet scenario, configure reachable Layer 2 links between the initiator and reflector.
    • In an L2VPN scenario, configure reachable links between CEs on both ends of an L2VPN connection.
    • In an EVPN scenario, configure reachable links between CEs on both ends of an EVPN connection.
  • Layer 3:
    • In a native IP scenario, configure reachable IP links between the initiator and reflector.
    • In an L3VPN scenario, configure reachable links between CEs on both ends of an L3VPN connection.
  • L2VPN accessing L3VPN scenario: configure reachable links between the L2VPN and L3VPN.
  • IP gateway scenario: configure reachable Layer 2 links between an IP gateway and the reflector.

Configuration Procedure

Figure 4-4 Flowchart of configuring a General Flow Test Instance

Configuring a Reflector

This section describes how to configure a reflector, which loops traffic to an initiator. You can set reflector parameters based on each scenario.

Context

On the network shown in Figure 4-1 of the "Establishing the Configuration Task", the following two roles are involved in a general flow test:

  • Initiator: sends simulated service traffic to a reflector.

  • Reflector: loops the service traffic to the initiator.

    The reflector can loop all packets on a reflector interface or the packets matching filter criteria to the initiator. The filter criteria include a destination unicast MAC address or a port number.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Configure the reflector. The reflector settings vary according to usage scenarios.

    NOTE:
    • The reflector ID must be unique on a local node.
    • The aging time can be set for a reflector. The default aging time is 14400s.

    Usage Scenario

    Configuration Procedure

    Configuration Note

    Any scenario in which a reflector loops all packets

    nqa reflector reflector-id interface interface-type interface-number [ exclusive ] [ exchange-port ]

    On the network shown in Figure 4-1 of the "Establishing the Configuration Task", UNI-B is used as a reflector interface.

    Layer 2

    nqa reflector reflector-id interface interface-type interface-number [ mac mac-address ] [ pe-vid pe-vid ce-vid ce-vid | vlan vlan-id ] [ source-port source-port ] [ destination-port destination-port ] [ exchange-port ] [ agetime agetime | endtime { endtime | enddate endtime } ] [ share-mode ]

    On the network shown in Figure 4-1 of the "Establishing the Configuration Task", the MAC address of the reflector's UNI-B or a MAC address that has never been used is used as the MAC address.

    Layer 3

    nqa reflector reflector-id interface interface-type interface-number [ ipv4 ip-address ] [ pe-vid pe-vid ce-vid ce-vid | vlan vlan-id ] [ source-port source-port ] [ destination-port destination-port ] [ exchange-port ] [ agetime agetime | endtime { endtime | enddate endtime } ] [ share-mode ]

    On the network shown in Figure 4-1 of the "Establishing the Configuration Task", an IP address on the same network segment as the reflector's UNI-B is used as the IP address.

    IP gateway

    nqa reflector reflector-id interface interface-type interface-number [ ipv4 ip-address | mac mac-address | simulate-ip ipv4 ip-address2 ] [ pe-vid pe-vid ce-vid ce-vid | vlan vlan-id ] [ source-port source-port ] [ destination-port destination-port ] [ exchange-port ] [ agetime agetime | endtime { endtime | enddate endtime } ] [ share-mode ]

    NOTE:

    In the IP and IP gateway scenario, need to run the arp static ip-address mac-address command to configure a static ARP entry for the source IP address.

    On the network shown in Figure 4-1 of the "Establishing the Configuration Task", an IP address on the same network segment as the reflector's UNI-B is used as the simulated IP address.

  3. Run commit

    The configuration is committed.

Configuring an Initiator

This section describes how to configure an initiator that sends simulated service traffic. You can set initiator parameters based on usage scenarios and test counter types.

Context

On the network shown in Figure 4-1 of the "Establishing the Configuration Task", the following two roles are involved in a generalflow test:

  • Initiator: sends simulated service traffic to a reflector.

  • Reflector: loops the service traffic to the initiator.

The process of configuring the initiator is as follows:

  1. Create a generalflow test instance.

  2. Set basic simulated service parameters.

  3. Set key test parameters based on counters.

  4. Set generalflow test parameters.

  5. Start the generalflow test instance.

Procedure

  1. Create a generalflow test instance.
    1. Run system-view

      The system view is displayed.

    2. Run nqa test-instance admin-name test-name

      An NQA test instance is created, and the test instance view is displayed.

    3. Run test-type generalflow

      The test type is set to generalflow.

    4. Run measure { throughput | loss | delay }

      A test counter is specified.

  2. Set basic simulated service parameters.

    NOTE:

    The basic simulated service parameters on the initiator must be the same as those configured on the reflector.

    Table 4-5 Configurations in different usage scenarios

    Usage Scenario

    Configuration Procedure

    Configuration Note

    Layer 2

    1. Run the destination-address mac mac-address command to specify the destination MAC address of test packets.

    2. (Optional) Run the source-address mac mac-address command to specify the source IP address of test packets.

    3. Run the forwarding-simulation inbound-interface interface-type interface-number command to specify the inbound interface of simulated service packets.

    4. Run the vlan vlan-id or pe-vid pe-vid ce-vid ce-vid command to set VLAN IDs of simulated service packets.

    The initiator shown in Figure 4-1 of the "Establishing the Configuration Task" has the following parameters:

    • Destination MAC address: the MAC address of the reflector's UNI-B or a MAC address that has never been used

      NOTE:

      Destination MAC addresses are configured by the incremental addition of the last bit. The occupation of ports (In and Out) is based on the combinations of 0 and 1 and a certain period. Two adjacent MAC addresses occupy different ports, as shown in Figure 4-5. The port occupation configured remains unchanged after the device restarts.

      Figure 4-5 Destination MAC address hash mode
      NOTE:

      0 and 1 in the preceding table indicate the first and second physical interfaces bound to the trunk interface, respectively.


    • Source MAC address: the MAC address of the initiator's UNI-A or a MAC address that has never been used
    • Simulated inbound interface: UNI-A

    • VLAN ID: VLAN IDs configured on interfaces

    NOTE:

    The display nqa reflector command can be used on the reflector to display the configured destination MAC address.

    Layer 3
    1. Run the destination-address ipv4 ipv4-address command to specify the destination IP address of test packets.

    2. Run the source-address ipv4 ipv4-address command to specify the source IP address of test packets.

    3. Run the forwarding-simulation inbound-interface interface-type interface-number command to specify the inbound interface of simulated service packets.

    4. (Optional) Run the vlan vlan-id or pe-vid pe-vid ce-vid ce-vid command to set VLAN IDs of simulated service packets.

    NOTE:

    If the initiator does not have an ARP entry corresponding to the source IP address in test packets, run the arp static ip-address mac-address command to configure a static ARP entry for the source IP address.

    The initiator shown in Figure 4-1 of the "Establishing the Configuration Task" has the following parameters:

    • Destination IP address: an IP address on the same network segment as the reflector's UNI-B

    • Source IP address: an IP address on the same network segment as UNI-A's IP address
      NOTE:

      Source MAC addresses are configured by the incremental addition of the last bit. The occupation of ports (In and Out) is based on the combinations of 0 and 1 and a certain period. Two adjacent MAC addresses occupy different ports, as shown in Figure 4-6. The port occupation configured remains unchanged after the device restarts.

      Figure 4-6 Source IP address hash mode
      NOTE:

      0 and 1 in the preceding table indicate the first and second physical interfaces bound to the trunk interface, respectively.


    • Simulated inbound interface: UNI-A

    IP gateway
    1. Run the destination-address ipv4 ipv4-address command to specify the destination IP address of test packets.

    2. Run the source-address ipv4 ipv4-address command to specify the source IP address of test packets.

    3. Run the source-interface interface-type interface-number command to specify the outbound interface of test packets.

    4. (Optional) Run the vlan vlan-id or pe-vid pe-vid ce-vid ce-vid command to set VLAN IDs of simulated service packets.

    The initiator shown in Figure 4-1 of the "Establishing the Configuration Task" has the following parameters:

    • Destination IP address: the CE's IP address or an IP address on the same network segment as the CE.

    • Source IP address: an IP address on the same network segment as UNI-A's IP address
    L2VPN accessing L3VPN
    1. Run the destination-address ipv4 ipv4-address mac mac-address command to specify the destination IP and MAC addresses of test packets.

    2. Run the source-address ipv4 ipv4-address command to specify the source IP address of test packets.

    3. Run the forwarding-simulation inbound-interface interface-type interface-number command to specify the inbound interface of simulated service packets.

    The initiator shown in Figure 4-1 of the "Establishing the Configuration Task" has the following parameters:

    • Destination IP address: the CE's IP address or an IP address on the same network segment as the CE.

    • Destination MAC address: the MAC address of the reflector's UNI-B or a MAC address that has never been used

    • Source IP address: an IP address on the same network segment as UNI-A's IP address
    • Simulated inbound interface: UNI-A

  3. Set key test parameters based on counters.

    Table 4-6 Key test parameters

    Counter

    Configuration Procedure

    Throughput

    1. Run the rate rate-low rate-high command to set the upper and lower rate thresholds.
    2. Run the interval seconds interval command to set the interval at which test packets are transmitted at a specific rate.

      The default interval is 4s.

    3. Run the precision precision-value command to set the throughput precision.

      The default precision is 1000 Kbit/s.

    4. Run the fail-ratio fail-ratio-value command to set the packet loss rate during a throughput test. The value is expressed in 1/10000. If the actual packet loss rate is less than 1/10000, the test is successful and continues.

      The default packet loss rate is 0%.

    Latency
    1. Run the rate rate command to set the rate at which test packets are sent.
    2. Run the interval seconds interval command to set the interval at which test packets are sent.

      The default interval is 4s.

    Packet loss rate
    1. Run the rate rate command to set the rate at which test packets are sent.

  4. Configure common parameters for an NQA test instance.
    1. Run datasize size & <1-7>

      The size of the data field in an NQA test packet.

      The default size of a general flow test packet is tested based on seven typical packet lengths: 64 bytes, 128 bytes, 256 bytes, 512 bytes, 1024 bytes, 1280 bytes, and 1518 bytes.

      In Layer 2 and Layer 3 scenarios, the data size of a generalflow test packet cannot be greater than the maximum transmission unit (MTU) of the simulated inbound interface.

    2. Run duration duration

      The test instance duration is set.

      The default duration is 60s.

      NOTE:

      The duration value must be greater than twice the interval value in throughput and delay tests.

    3. Run records result number

      The maximum number of results that can be recorded is set.

      By default, the last five test results are recorded.

    4. Run priority 8021p priority-value

      The 802.1p priority is set for generalflow test packets in an Ethernet scenario.

      The default priority is 0.

    5. Run tos value

      The IP packet priority is set.

      The default priority is 0.

    6. (Optional) Run exchange-port enable

      A UDP source port number is enabled to be switched with a UDP destination port number.

  5. Run start now

    The NQA test instance is started.

    Running the start now command interrupts user services temporarily.

  6. Run commit

    The configuration is committed.

Verifying the Configuration of a General Flow Test Instance

After you configure the general flow test instance, you can verify the general flow test configuration and test results.

Prerequisites

All general flow test configurations are complete.
NOTE:
NQA test results cannot be displayed automatically on the terminal. Run the display nqa results command to view test results. By default, the command output shows the results of the latest five tests.

Procedure

  • Run the display nqa results [ test-instance admin-name test-name ] command on the initiator to view general flow test results.
  • Run the display nqa reflector [ reflector-id ] command on the reflector to view reflector information.

Example

# Run the display nqa results command to view throughput test results.

<HUAWEI> display nqa results test-instance admin generalflow
 NQA entry(admin, generalflow) :testflag is active ,testtype is generalflow                                                                       
   1 . Test 1 result: The test is finished, test mode is throughput
   ID Size Throughput(Kbps) Precision(Kbps) LossRatio Completion
   1  64   1000             1000            0.00%     success   
   2  128  1000             1000            0.00%     success   
   3  256  1000             1000            0.00%     success   
   4  512  1000             1000            0.00%     success   
   5  1024 1000             1000            0.00%     success   
   6  1280 1000             1000            0.00%     success   
   7  1518 1000             1000            0.00%     success   

# Run the display nqa results command to view packet loss ratio test results.

<HUAWEI> display nqa results test-instance admin generalflow
NQA entry(admin, generalflow) :testflag is inactive ,testtype is generalflow
  1 . Test 1 result: The test is finished, test mode is loss
   ID Size TxRate/RxRate(Kbps) TxCount/RxCount             LossRatio Completion
   1  64   200/200             2875/2875                   0.00%     finished  
   2  128  199/199             1648/1648                   0.00%     finished  
   3  256  200/200             892/892                     0.00%     finished  
   4  512  200/200             472/472                     0.00%     finished  
   5  1024 199/199             240/240                     0.00%     finished  
   6  1280 201/201             194/194                     0.00%     finished  
   7  1518 202/202             164/164                     0.00%     finished  

# Run the display nqa results command to view delay test results.

<HUAWEI> display nqa results test-instance admin generalflow
NQA entry(admin, generalflow) :testflag is inactive ,testtype is generalflow
  1 . Test 1 result: The test is finished, test mode is delay
   ID Size Min/Max/Avg RTT(us)     Min/Max/Avg Jitter(us)  Completion
   1  64   205/208/207             0/2/1                   finished  
   2  128  140/141/140             0/1/0                   finished  
   3  256  128/141/135             0/13/6                  finished  
   4  512  140/140/140             0/0/0                   finished  
   5  1024 148/151/149             0/2/1                   finished  
   6  1280 154/158/156             0/3/1                   finished  
   7  1518 150/155/152             0/4/2                   finished  

# Run the display nqa reflector command to view reflector information.

<HUAWEI> display nqa reflector
The total number of reflectors is 1
Reflector 1:
  Interface                     : GE0/1/0
  IP-address                    : --
  MAC-address                   : --
  Cevid                         : --
  Pevid                         : --
  Source-port                   : --
  Destination-port              : --
  Exchange-port                 : enable
  AgeTime(s)                    : 0
  SurvivalTime(s)               : --
  EndTime                       : --
  State                         : --
  RecommendedTestMac            : ac4e-9167-1f60
  TestFlow                      : 1
<HUAWEI> display nqa reflector
The total number of reflectors is 1
Reflector 1:
  Interface                     : Eth0/1/1
  IP-address                    : --
  MAC-address                   : --
  Cevid                         : --
  Pevid                         : --
  Simulate IP-address           : --
  Source-port                   : --
  Destination-port              : --
  Exchange-port                 : disable
  AgeTime(s)                    : 14400
  SurvivalTime(s)               : 13307
  Endtime                       : 2014-03-19 08:48:21
  State                         : --
  RecommendedTestMac            : 384d-d111-0011
  TestFlow                      : --
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058924

Views: 7027

Downloads: 24

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