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

NE40E V800R010C00 Configuration Guide - System Monitor 01

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 NQA to Monitor VPNs

Configuring NQA to Monitor VPNs

Before configuring NQA to monitor virtual private networks (VPNs), familiarize yourself with the usage scenario and complete the pre-configuration tasks.

Usage Scenario

Table 4-3  NQA tests used to monitor VPNs
Test Type Usage Scenario
PWE3 ping test A PWE3 ping test helps detect the pseudo wire (PW) connectivity, packet loss rate, and delay on a virtual private wire service (VPWS) network.
VPLS PW ping test A virtual private local area network service (VPLS) pseudo wire (PW) ping test instance monitors the PW connectivity, packet loss ratios, and delay time on a VPLS network.
PWE3 trace test A pseudo wire emulation edge-to-edge (PWE3) trace test monitors the pseudo wire (PW) connectivity, packet loss ratios, and delay time on virtual private wire service (VPWS) networks.
VPLS PW trace test A virtual private local area network service (VPLS) pseudo wire (PW) trace test instance monitors the PW connectivity, packet loss ratios, and delay time on a VPLS network.

Pre-configuration Tasks

Before you configure NQA to check VPNs, configure basic VPN functions.

Configuring a PWE3 Ping Test

A PWE3 ping test helps detect the pseudo wire (PW) connectivity, packet loss rate, and delay on a virtual private wire service (VPWS) network.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and configure the test instance type as PWE3 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 pwe3ping

      The test instance type is configured as PWE3 ping.

    3. Run:

      description description

      A description is configured for the NQA test instance.

  3. (Optional) Run:

    fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. Set parameters for the L2VPN network to be tested.
    1. Run:

      local-pw-type { vlan | ethernet | cesopsn-basic | satop-e1 | hdlc | ip-interworking | ip-layer2 | ppp | atm-1to1-vcc | atm-1to1-vpc | atm-nto1-vcc | atm-nto1-vpc | atm-cell-transport }

      An encapsulation type is configured for the local PW.

    2. Run:

      label-type { control-word | { { label-alert | normal } [ no-control-word ] } }

      A packet encapsulation type is configured.

    3. Run:

      local-pw-id local-pw-id

      The local PW ID is configured.

  5. (Optional) Configure information about the remote PE when a multi-segment PW is to be tested.

    A multi-segment PW can be tested only when the label-type is control-word or normal.

    1. Run:

      destination-address ipv4 ip-address

      The IP address for the remote PE is configured.

    2. Run:

      remote-pw-id remote-pw-id

      The remote PW ID is configured.

    3. (Optional) Run:

      sender-address ipv4 ip-address

      The source IP address of the public network session between the device and the remote PE is configured. This IP address is the IP address of the adjacent SPE or UPE.

      
      

      The sender-address command is configured only when the device interworks with devices from other vendors.

    4. (Optional) Run:

      ttl-copymode { pipe | uniform }

      A time to live (TTL) copy mode is set.

  6. Set optional parameters for the test instance and simulate packets transmitted on an actual network.
    1. Run:

      lsp-exp exp

      The LSP EXP value is set for the NQA test instance.

    2. Run:

      lsp-replymode { level-control-channel | no-reply | udp | udp-via-vpls  }

      The reply mode in the NQA LSP test instance is configured.

    3. Run:

      datafill fillstring

      Padding characters in NQA test packets are configured.

    4. Run:

      datasize size

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

      Only supported when the icmp-jitter-mode is icmp-echo.

    5. Run:

      probe-count number

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

    6. Run:

      interval seconds interval

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

    7. Run:

      ttl number

      The TTL value in NQA test packets is set.

  7. (Optional) Configure test failure conditions.
    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 equal to or greater than the failure percentage, the test is regarded as a failure.

  8. Run:

    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.

  9. (Optional) Enable the system to send traps to the NMS.

    1. Run the probe-failtimes command to enable the system to send traps to the NMS when the number of consecutive probe failures reaches the specified threshold.

    2. Run the test-failtimes times command to enable the system to send traps to the NMS when the number of consecutive test failures reaches the specified threshold.

    3. Run the threshold rtd rtd-value command to configure an RTD threshold.
    4. Run the send-trap { all | [ rtd | testfailure | probefailure | testcomplete ]* } command to configure the condition for triggering a trap.

  10. Schedule the test instance.
    1. (Optional) Run:

      frequency interval

      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 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 start at [ 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 start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  11. Run:

    commit

    The configuration is committed.

Configuring a VPLS MAC Ping Test

A VPLS MAC ping test can detect the connectivity of Layer 2 links on a VPLS network.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and configure the test instance type as VPLS 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 vplsping

      The test instance type is set to VPLS MAC ping.

    3. Run:

      description description

      A description is configured for the NQA test instance.

  3. (Optional) Run:

    fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. Set the VPLS parameters to be checked.
    1. Run:

      vsi vsi-name

      The name of the VSI to be detected is specified.

    2. Run:

      destination-address mac mac-address

      The destination MAC address associated with the VSI is specified.

    3. (Optional) Run:

      vlan vlan-id

      A VLAN ID is specified for the NQA test instance.

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

      lsp-exp exp

      The LSP EXP value is set for the NQA test instance.

    2. Run:

      lsp-replymode { no-reply | udp | udp-via-vpls }

      The reply mode in the NQA LSP test instance is configured.

    3. Run:

      datafill fillstring

      Padding characters in NQA test packets are configured.

    4. Run:

      datasize size

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

    5. Run:

      probe-count number

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

    6. Run:

      interval seconds interval

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

    7. Run:

      ttl number

      The TTL value in NQA test packets is set.

  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 equal to or greater than the failure percentage, the test is regarded as a failure.

    3. Run:

      probe-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 times

      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 rtd-value

      The RTD threshold is configured.

    6. Run:

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

      The condition for triggering a trap is configured.

  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 agetime

    The aging time for the NQA test instance is set.

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

      frequency interval

      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 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 start at [ 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 start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  10. Run:

    commit

    The configuration is committed.

Configuring a VPLS PW Ping Test

A virtual private local area network service (VPLS) pseudo wire (PW) ping test instance monitors the PW connectivity, packet loss ratios, and delay time on a VPLS network.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to VPLS PW 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 vplspwping

      The test instance type is set to VPLS PW ping.

    3. (Optional) Run:

      description description

      A description is configured for the NQA test instance.

  3. (Optional) Run:

    fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. Set parameters for the VPLS network to be monitored.
    1. Run:

      vsi vsi-name

      The name of a virtual switching instance (VSI) to be monitored is specified.

    2. Run:

      destination-address ipv4 ip-address

      An IP address of the remote PE is specified.

    3. (Optional) Run:

      local-pw-id local-pw-id

      A PW ID is set on the local PE.

      NOTE:
      If the VSI configured using the vsi vsi-name command has a specified negotiation-vc-id, the local-pw-id local-pw-id command must be run.

  5. (Optional) Set parameters for the test instance and simulate packets.
    1. Run:

      lsp-exp exp

      The LSP EXP value is set for the NQA test instance.

    2. Run:

      lsp-replymode { level-control-channel | no-reply | udp | udp-via-vpls  }

      The reply mode in the NQA LSP test instance is configured.

    3. Run:

      datafill fillstring

      Padding characters in NQA test packets are configured.

    4. Run:

      datasize size

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

    5. Run:

      probe-count number

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

    6. Run:

      interval seconds interval

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

    7. Run:

      ttl number

      The TTL value in NQA test packets is set.

  6. (Optional) Configure test failure conditions.
    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 equal to or greater than the failure percentage, the test is regarded as a failure.

  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) Enable the device to send traps to the NMS.

    1. Run:

      probe-failtimes

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

    2. Run:

      test-failtimes times

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

    3. Run:
      threshold rtd rtd-value

      The RTD threshold is set.

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

      The condition for triggering a trap is configured.

  9. Schedule the test instance.
    1. (Optional) Run:

      frequency interval

      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 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 start at [ 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 start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  10. Run:

    commit

    The configuration is committed.

Configuring a PWE3 Trace Test

A pseudo wire emulation edge-to-edge (PWE3) trace test monitors the pseudo wire (PW) connectivity, packet loss ratios, and delay time on virtual private wire service (VPWS) networks.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to PWE3 trace.
    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 pwe3trace

      The test instance type is set to PWE3 trace.

    3. Run:

      description description

      A description is configured for the NQA test instance.

  3. (Optional) Run:

    fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. Set parameters for the Layer 2 virtual private network (L2VPN) to be monitored.
    1. Run:

      local-pw-type { vlan | ethernet | cesopsn-basic | satop-e1 | hdlc | ip-interworking | ip-layer2 | ppp | atm-1to1-vcc | atm-1to1-vpc | atm-nto1-vcc | atm-nto1-vpc | atm-cell-transport }

      An encapsulation type is set for the PW on the local PE.

    2. Run:

      label-type { control-word | { { label-alert | normal } [ no-control-word ] } }

      An encapsulation type is set for packets.

    3. Run:

      lsp-version { rfc4379 | ptn-mode }

      A protocol is configured for the LSP test instance.

    4. Run:

      local-pw-id local-pw-id

      A PW ID is set on the local PE.

  5. (Optional) Configure remote provider edge (PE) information for a multi-segment PW to be monitored.

    An MS-PW can be monitored only after you specify control-word or normal.

    1. Run:

      destination-address ipv4 ip-address

      An IP address is configured for the remote PE.

    2. Run:

      remote-pw-id remote-pw-id

      A PW ID is set for the remote PE.

    3. (Optional) Run:

      ttl-copymode { pipe | uniform }

      A time to live (TTL) propagation mode is set.

  6. (Optional) Set parameters for the test instance and simulate packets.
    1. Run:

      lsp-exp exp

      The LSP EXP value is set for the NQA test instance.

    2. Run:

      lsp-replymode { level-control-channel | no-reply | udp | udp-via-vpls  }

      The reply mode in the NQA LSP test instance is configured.

    3. Run:

      probe-count number

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

    4. Run:

      tracert-livetime

      The lifetime is set for the Traceroute test instance.

  7. (Optional) Configure test failure conditions.
    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 equal to or greater than the failure percentage, the test is regarded as a failure.

  8. (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.

  9. (Optional) Enable the device to send traps to the NMS.

    1. Run:

      probe-failtimes

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

    2. Run:

      test-failtimes times

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

    3. Run:
      threshold rtd rtd-value

      The RTD threshold is set.

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

      The condition for triggering a trap is configured.

  10. Schedule the test instance.
    1. (Optional) Run:

      frequency interval

      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 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 start at [ 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 start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  11. Run:

    commit

    The configuration is committed.

Configuring a VPLS PW Trace Test

A virtual private local area network service (VPLS) pseudo wire (PW) trace test instance monitors the PW connectivity, packet loss ratios, and delay time on a VPLS network.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to VPLS PW 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 vplspwtrace

      The test instance type is set to VPLS PW trace.

    3. (Optional) Run:

      description description

      A description is configured for the NQA test instance.

  3. (Optional) Run:

    fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. Set parameters for the VPLS network to be monitored.
    1. Run:

      vsi vsi-name

      The name of an virtual switching instance (VSI) to be monitored is specified.

    2. Run:

      destination-address ipv4 ip-address

      An IP address of the remote PE is specified.

    3. (Optional) Run:

      local-pw-id local-pw-id

      A PW ID is set on the local PE.

  5. (Optional) Set parameters for the test instance and simulate packets.
    1. Run:

      lsp-exp exp

      The LSP EXP value is set for the NQA test instance.

    2. Run:

      lsp-replymode { level-control-channel | no-reply | udp | udp-via-vpls  }

      The reply mode in the NQA LSP test instance is configured.

    3. Run:

      probe-count number

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

    4. Run:

      ttl number

      The TTL value in NQA test packets is set.

  6. (Optional) Configure test failure conditions.
    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 equal to or greater than the failure percentage, the test is regarded as a failure.

  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) Enable the device to send traps to the NMS.

    1. Run:

      probe-failtimes

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

    2. Run:

      test-failtimes times

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

    3. Run:
      threshold rtd rtd-value

      The RTD threshold is set.

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

      The condition for triggering a trap is configured.

  9. (Optional) Run:

    lsp-path full-display

    Enables all devices, including Ps along an LSP to be displayed in an NQA test result.

  10. Schedule the test instance.
    1. (Optional) Run:

      frequency interval

      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 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 start at [ 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 start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  11. Run:

    commit

    The configuration is committed.

Checking the Configurations

After the test is complete, view the test results.

Prerequisites

NOTE:
NQA test results are not displayed automatically on the terminal. To view test results, run the display nqa results command.

Procedure

  • Run the display nqa results [ collection ] [ test-instance admin-name test-name ] command to check NQA test results.

Example

Run the display nqa results command to view the NQA test results.

<HUAWEI> display nqa results test-instance admin pwe3ping 
NQA entry(admin, pwe3ping) :testflag is active ,testtype is pwe3ping
  1 . Test 1 result The test is finished 
   SendProbe:3                            ResponseProbe:3                       
   Completion:success                     RTD OverThresholds number:0           
   OWD OverThresholds SD number:0         OWD OverThresholds DS number:0        
   Min/Max/Avg/Sum RTT:3/152/53/159       RTT Square Sum:23129                  
   NumOfRTT:0                             Drop operation number:0               
   Operation sequence errors number:0     RTT Stats errors number:0             
   System busy operation number:0         Operation timeout number:0            
   Min Positive SD:0                      Min Positive DS:0                     
   Max Positive SD:0                      Max Positive DS:0                     
   Positive SD Number:0                   Positive DS Number:0                  
   Positive SD Sum:0                      Positive DS Sum:0                     
   Positive SD Square Sum:0               Positive DS Square Sum:0              
   Min Negative SD:0                      Min Negative DS:0                     
   Max Negative SD:0                      Max Negative DS:0                     
   Negative SD Number:0                   Negative DS Number:0                  
   Negative SD Sum:0                      Negative DS Sum:0                     
   Negative SD Square Sum:0               Negative DS Square Sum:0              
   Min Delay SD:0                         Min Delay DS:0                        
   Max Delay SD:0                         Max Delay DS:0                        
   Delay SD Square Sum:0                  Delay DS Square Sum:0                 
   Packet Loss SD:0                       Packet Loss DS:0                      
   Packet Loss Unknown:0                  Average of Jitter:0                   
   Average of Jitter SD:0                 Average of Jitter DS:0                
   Jitter out value:0.0000000             Jitter in value:0.0000000             
   NumberOfOWD:0                          Packet Loss Ratio:0 %                 
   OWD SD Sum:0                           OWD DS Sum:0                          
   ICPIF value:0                          MOS-CQ value:0                        
   Attempts number:1                      Disconnect operation number:0         
   Connection fail number:0               Destination ip address:1.1.1.1        
   Last Good Probe Time: 2015-07-13 18:43:20.9 
Download
Updated: 2018-07-12

Document ID: EDOC1100028538

Views: 29154

Downloads: 220

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