Configuring the Reflector

This section describes how to configure a reflector, which loops traffic to an initiator. Parameters configured on the reflector vary according to a specific scenario.

Context

Devices performing an Ethernet service activation test play two roles: initiator and reflector. An initiator sends simulated service traffic to a reflector, and the reflector reflects the service traffic.

The reflector must be specified before a test is started.

A reflector can loop traffic based on either an interface or a flow.

  • Interface-based mode: A reflector loops all traffic that its interface receives.
  • Flow-based mode: A reflector loops only traffic meeting specified conditions. In flow-based mode, a test flow must have been configured.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run nqa test-flow flow-id

    A test flow is configured, and the test flow view is displayed.

  3. Configure service flow characteristics.

    1. Run:
      • traffic-type mac { destination destination-mac [ end-destination-mac ] | source source-mac [ end-source-mac ] }
      • traffic-type ipv4 { destination destination-ip [ end-destination-ip ] | source source-ip [ end-source-ip ] }

        A traffic type is configured, and the MAC or IP address of test packets is specified. An address range can be specified here.

      Services may be forwarded based on the MAC or IP address or using MPLS based on the service type, such as Ethernet, IP, L2VPN, L2VPN accessing L3VPN, and L3VPN. When testing a service network, you must determine the specific service forwarding mode before configuring a traffic type for the service flow to be tested.

      • For Ethernet Layer 2 switching and L2VPN services, a MAC address must be specified, and an IP address is optional.
      • For IP routing and L3VPN services, an IP address and a MAC address must be specified. If no IP address or MAC address is specified, the reflector will reflect all the traffic, which affects other service functions.
      • For L2VPN accessing L3VPN, both MAC and IP addresses must be specified.
    2. Configure the following parameters as needed:
      • Run vlan vlan-id [ end-vlan-vid ]

        A single VPN ID is specified for Ethernet packets in the NQA test flow view.

      • Run pe-vid pe-vid ce-vid ce-vid [ ce-vid-end ]

        Double VPN IDs are specified for Ethernet packets in the NQA test flow view.

      • Run udp destination-port destination-port [ end-destination-port ]

        A destination UDP port number or range is specified.

      • Run udp source-port source-port [ end-source-port ]
        A source UDP port number or range is specified.
        • For the same test flow, a range can be specified only in one of the traffic-type, vlan, pe-vid, udp destination-port, and udp source-port commands. In addition, the difference between the start and end values cannot be more than 127, and the end value must be greater than the start value.

        • In the traffic-type command, the start MAC or IP address has only one different octet from the end MAC or IP address. For example, the start IP address is set to 1.1.1.1, and the end IP address can only be set to an IP address in the network segment 1.1.1.0.

  4. Run quit

    Return to the system view.

  5. Run nqa reflector reflector-id interface { interface-name | interface-type interface-number } [ [ [ test-flow { testFlowId } &<1-16> ] | [ [ ipv4 ip-address | simulate-ipipv4 ip-address2 | mac mac-address ] [ pe-vid pe-vid ce-vid ce-vid | vlan vlan-id ] [ source-port source-port ] [ destination-port destination-port ] ] ] | exclusive ] [ exchange-port ] [ agetime agetime | endtime { endtime | enddateendtime } ]

    The reflector is specified.

    The test-flow flow-id & <1-16> command configures the reflector to reflect based on a specified flow. If the flow ID is not specified, the reflector performs interface-based reflection. The agetime age-time parameter is optional, and the default value is 14400s.

  6. Run commit

    The configuration is committed.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
Next topic >