Configuring a MAC Ping Test

MAC ping can test the connectivity, packet loss, and delay of links between devices on a Layer 2 network, facilitating fault locating.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Create an NQA test instance and specify the test instance type as MAC ping.
    1. Run nqa test-instance admin-name test-name

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

    2. Run test-type macping

      The NQA test instance type is set to MAC ping.

    3. Run description description

      A description is configured for the NQA test instance.

  3. Configure the MEP ID, MD name, and MA name based on the MAC ping type.
    1. Run mep mep-id mep-id

      The local MEP ID is configured.

    2. Run md md-name ma ma-name

      The names of the MD and MA for sending NQA test packets are configured.

  4. Perform either of the following steps to configure the destination address for the MAC ping test:

    If the destination address type is remote-mep, you must configure the mapping between the remote MEP and MAC address first.

  5. (Optional) Set optional parameters for the NQA test instance and simulate packets transmitted on an actual network.
    1. Run datasize datasizeValue

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

    2. Run probe-count number

      The number of probes in a test is set for the NQA test instance.

    3. Run interval seconds interval

      The interval at which NQA test packets are sent is set for the NQA test instance.

  6. (Optional) Configure detection failure conditions and enable the function to send traps to the NMS upon detection failures.
    1. Run timeout time

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

    2. Run fail-percent percent

      The failure percentage is set for the NQA test instance.

      If the percentage of failed probes is greater than or equal to the failure percentage, the test is regarded as a failure.

    3. Run probe-failtimes failTimes

      The system is enabled to send traps to the NMS after the number of consecutive probe failures reaches the specified threshold.

    4. Run test-failtimes failTimes

      The system is enabled to send traps to the NMS after the number of consecutive failures of the NQA test instance reaches the specified threshold.

    5. Run threshold rtd thresholdRtd

      The RTD threshold is configured.

    6. Run send-trap { all | [ rtd | testfailure | probefailure | testcomplete ]* }

      The condition for triggering a trap is configured.

    7. Run jitter-packetnum packetNum

      The number of test packets to be sent during each test is set.

  7. (Optional) Configure the NQA statistics function.

    Run records { history number | result number }

    The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

  8. (Optional) Run agetime ageTimeValue

    The aging time for the NQA test instance is set.

  9. Schedule the NQA test instance.
    1. (Optional) Run frequency frequencyValue

      The test period is set for the NQA test instance.

    2. Run start

      An NQA test is started.

      The start command has multiple formats. Choose one of the following as needed.

      • To start an NQA test instance immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time, run the startat [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance after a specified delay, run the start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time every day, run the startdailyhh:mm:sstohh:mm:ss [ beginyyyy/mm/dd ] [ endyyyy/mm/dd ] command.

  10. Run commit

    The configuration is committed.

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