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).
Using Ping/Tracert on a VPN Network

Using Ping/Tracert on a VPN Network

The ping and tracert operations monitor VPN networks.

Using Ping to Monitor VPWS PW Connectivity

After you configure a virtual private wire service (VPWS) network, use pseudo wire (PW) ping to monitor PW connectivity on the VPWS network.

Prerequisites

Before testing pseudo wire (PW) connectivity using the ping vc command, ensure that the VPWS network has been configured correctly.

Context

To check whether a PW on the VPWS network is faulty, run the ping vc command. When the PW is Up, you can locate faults, such as forwarding entry loss or errors.

Table 5-1 describes check modes and usage scenarios.

Table 5-1  Check modes and usage scenarios
Detection Mode Usage Scenario Description
Control-word Supports Single-segment PW and multi-segment PW detection.
  • The MPLS echo request packet carries the control word between the PW label and the IP header. After the destination device receives the packet and finds that it carries the control word, the device sends the packet to the CPU for processing.

  • This detection mode applies only when you enable the control-word on both ends of the PW.
Label-alert Supports only Single-segment detection.
  • The MPLS echo request packet carries the label-alert tag between the PW label and the LSP label. After the destination device receives the packet and detects that it carries the label-alert tag, the device sends the packet to the CPU for processing.

  • This detection mode applies only when you enable the label-alert for both ends of the PW.
TTL Supports Single-segment and multi-segment PW detection.

A TTL specifies the expiration value. You must specify a TTL value to ensure that the TTL expires on the destination device so that the device sends the packet to the CPU for processing.

Procedure

  • Control-word mode:

    To monitor PW connectivity using the control-word mode, run the ping vc vc-type pw-id [ -c echo-number | -m time-value | -s data-bytes | -t timeout-value | -exp exp-value | -r reply-mode | -v | -g] * control-word [ remote remote-ip-address peer-pw-id [ sender sender-address ] ] [ ttl ttl-value ] [ pipe | uniform ] command.

    To monitor multi-segment PW connectivity, specify an IP address and a PW ID for the remote PE and a source IP address in the remote remote-ip-address peer-pw-id [ sender sender-address ] command.

  • Label-alert mode:

    To monitor PW connectivity using the label-alert mode, run the ping vc {vc-type pw-id [ -c echo-number | -m time-value | -s data-bytes | -t timeout-value | -exp exp-value | -r reply-mode | -v | -g ] * label-alert [ no-control-word ] command.

  • TTL mode:

    To monitor PW connectivity using the TTL mode, run the ping vc vc-type pw-id [ -c echo-number | -m time-value | -s data-bytes | -t timeout-value | -exp exp-value | -r reply-mode | -v | -g ] * normal [ no-control-word ] [ remote remote-ip-address peer-pw-id ] [ ttl ttl-value ] [ pipe | uniform ] command.

    To monitor multi-segment PW connectivity, specify an IP address and a PW ID for the remote PE and set a TTL value in the remote remote-ip-address peer-pw-id [ ttl ttl-value ] [ pipe | uniform ] command.

    The ping vc command output contains the following information:

    • Response to each ping VC packet: If no response packet is received after the corresponding timer expires, the message reading "Request time out" is displayed. If a response packet is received, the number of data bytes, packet sequence number, TTL, and response time are displayed.

    • Final statistics: include the number of sent packets, number of received packets, percentage of sent packets with failed responses, and minimum, maximum, and average response times.

    For example:

    <HUAWEI> ping vc ethernet 100 control-word 
       PW PING : FEC 128 PSEUDOWIRE (NEW). Type = ethernet, ID = 100 : 100 data bytes, press CTRL_C to break
        Reply from 10.10.10.10: bytes=100 Sequence=1 time = 140 ms    
        Reply from 10.10.10.10: bytes=100 Sequence=2 time = 40 ms    
        Reply from 10.10.10.10: bytes=100 Sequence=3 time = 30 ms    
        Reply from 10.10.10.10: bytes=100 Sequence=4 time = 50 ms    
        Reply from 10.10.10.10: bytes=100 Sequence=5 time = 50 ms 
    --- FEC: FEC 128 PSEUDOWIRE (NEW). Type = ethernet, ID = 100 ping statistics---
    
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 30/62/140 ms

Using PW Ping to Monitor PW Connectivity on a VPLS Network

After you configure a virtual private LAN service (VPLS) network, use pseudo wire (PW) ping to monitor PW connectivity on the VPLS network.

Prerequisites

Before you run the ping vpls command to check PW connectivity, ensure that the VPLS network has been configured correctly.

Context

To check whether a PW on the VPLS network is faulty, run the ping vpls command.

Procedure

  1. To locate the faulty node on the VPLS network, run either of the following commands as required:

    • In Kompella mode, run:
      ping vpls [ -c echo-number | -m time-value | -s data-bytes | -t timeout-value | -exp exp-value | -r reply-mode | -v | -g ] * vsi vsi-name local-site-id remote-site-id [ bypass -si interface-type interface-number ]
    • In Martini mode, run:

      ping vpls [ -c echo-number | -m time-value | -s data-bytes | -t timeout-value | -exp exp-value | -r reply-mode | -v | -g ] * vsi vsi-name peer peer-address [ negotiate-vc-id vc-id ] [ control-word [ remote remote-address remote-pw-id [ sender sender-address ] ] ] [ bypass -si interface-type interface-number ]

    The ping vpls command output contains the following information:

    • Response to each ping VPLS packet. If no response packet is received after the corresponding timer expires, the message reading "Request time out" is displayed. If a response packet is received, the number of data bytes, packet sequence number, TTL, and response time are displayed.

    • Final statistics: include the number of sent packets, number of received packets, percentage of sent packets with failed responses, and minimum, maximum, and average response times.

    For example:

    <HUAWEI> ping vpls vsi a2 peer 10.1.1.1
        PW PING : FEC 128 PSEUDOWIRE (NEW). Type = vlan, ID = 2 : 100 data bytes, press CTRL_C to break
        Reply from 10.1.1.1: bytes=100 Sequence=1 time=60 ms
        Reply from 10.1.1.1: bytes=100 Sequence=2 time=50 ms
        Reply from 10.1.1.1: bytes=100 Sequence=3 time=60 ms
        Reply from 10.1.1.1: bytes=100 Sequence=4 time=60 ms
        Reply from 10.1.1.1: bytes=100 Sequence=5 time=60 ms
    
      --- FEC: FEC 128 PSEUDOWIRE (NEW). Type = vlan, ID = 2 ping statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 50/58/60 ms
    
    

Using Tracert to Monitor PWE3 Network Connectivity

You can run the tracert command to obtain information about the SPEs and Ps through which packets pass from the source to the destination. Based on the command output, you can monitor PW connectivity and locate faulty nodes.

Context

Perform the following steps on the PE of a PWE3 network:

Procedure

  1. To locate the faulty node on a PWE3 network, run any of the following commands as required:

    • To monitor connectivity of the PWE3 network through the control word channel, run:

      tracert vc vc-type pw-id [ -exp exp-value | -f first-ttl | -m max-ttl | -r reply-mode | -t timeout-value | -g ] * control-word [ ptn-mode | full-lsp-path ] [ pipe | uniform ] [ detail ]
      tracert vc vc-type pw-id [ -exp exp-value | -f first-ttl | -m max-ttl | -r reply-mode | -t timeout-value | -g ] * control-word remote remote-ip-address [ ptn-mode | full-lsp-path ] [ pipe | uniform ] [ detail ]
    • To monitor connectivity of the PWE3 network through the label alert channel, run:

      tracert vc vc-type pw-id [ -exp exp-value | -f first-ttl | -m max-ttl | -r reply-mode | -t timeout-value | -g ] * label-alert [ no-control-word ] [ full-lsp-path ] [ pipe | uniform ] [ detail ]
    • To monitor check connectivity of the PWE3 network in ordinary mode, run:

      tracert vc vc-type pw-id [ -exp exp-value | -f first-ttl | -m max-ttl | -r reply-mode | -t timeout-value | -g ] * normal [ remote remote-ip-address ] } [ full-lsp-path ] [ pipe | uniform ] [ detail ]
    Before using the tracert vc command to monitor PWE3 network connectivity, perform the following operations:
    • Configure the PWE3 network correctly.
    • Configure the PW template and enable VCCV-PING. In addition, configure the following functions in the PW template view:
      • Control word channel: Run the control-word command to enable the control word function.
      • MPLS Router Alert channel: Run the label-alert command to enable the control word function.
      • Ordinary mode: Run the normal command to enable the control word function.

    <HUAWEI> tracert vc ppp 100 control-word remote 4.1.1.2 full-lsp-path
      TTL   Replier            Time    Type      Downstream
      0                                Ingress   1.1.1.2/[1025 ]
      1     1.1.1.2           230 ms  Transit    2.1.1.2/[1301 ]
      2     2.1.1.2           230 ms  Transit    3.1.1.2/[1208 ]
      3     3.1.1.2           100 ms  Transit    4.1.1.2/[3 ]
      4     4.1.1.2           150 ms  Egress
    

    The preceding command output contains information about each node along the PW and the response time of each hop.

Using Tracert to Monitor PW Connectivity on a VPLS Network

Context

Perform the following steps on a PE of a VPLS network:

Procedure

  1. To locate the faulty node on the VPLS network, run either of the following commands as required:

    • In Kompella mode, run:
      tracert vpls [ -exp exp-value | -f first-ttl | -m max-ttl | -r reply-mode | -t timeout-value | -g ] * vsi vsi-name local-site-id remote-site-id [ full-lsp-path ] [ detail ] [ bypass -si interface-type interface-number ]
    • In Martini mode, run:

      tracert vpls [ -exp exp-value | -f first-ttl | -m max-ttl | -r reply-mode | -t timeout-value | -g ] * vsi vsi-name peer peer-address [ negotiate-vc-id vc-id ] [ full-lsp-path ] [ control-word  ] [ pipe | uniform ] [ detail ] [ bypass -si interface-type interface-number ]

    Run the tracert vpls command to locate VPLS network faults.

    <HUAWEI>tracert vpls vsi test 10 10 full-lsp-path  
    PW Trace Route FEC: L2 VPN ENDPOINT. Sender VEID = 10, Remote VEID = 20, press CTRL_C to break 
    TTL    Replier            Time    Type      Downstream 
    0                                 Ingress   10.1.1.2/[294929 32894 32888 ] 
    1      10.1.1.2           93 ms   Transit   10.2.1.2/[32925 3 ] 
    2      10.2.1.2           1 ms    Transit   10.3.1.2/[32881 ] 
    3      4.4.4.4            2 ms    Egress 

    The preceding command output contains information about each node along the PW and the response time of each hop.

Using CE Ping to Monitor the Connectivity Between a PE and a CE on a VPLS Network

After you configure a virtual private LAN service (VPLS) network, use customer edge (CE) ping to monitor the connectivity between a provider edge (PE) and a CE on the VPLS network.

Prerequisites

The VPLS network has been correctly configured, and the specified virtual service instance (VSI) is Up.

Context

NOTICE:
When you specify a source IP address, note the following:
  • The source IP address must be on the same network segment as the destination IP address. If they are on different network segments, the destination node considers Address Resolution Protocol (ARP) request packets invalid and does not return ARP response packets.
  • The specified source IP address must be unique on the L2VPN network. If the specified source IP address is the same as a used IP address, packets cannot be properly forwarded. As a result, user packets with the specified source IP address cannot be sent to the network. If the specified source IP address is the same as the gateway IP address, no users cannot access the network.

After you run the ce-ping command, the device displays a message to prompt to confirm that you have specified a unused IP address as the source IP address. Enter Y.

Procedure

  1. Run the following command to monitor the connectivity between a PE and a CE:

    ce-ping ip-address vsi vsi-name source-ip source-ip-address [ mac mac-address ] [ interval interval | count count ] *

    For example:

    <HUAWEI> ce-ping 10.1.1.1 vsi abc source-ip 10.1.1.2 mac E024-7FA4-D2CB interval 2 count 5
    Info: If the designated source IP address is in use, it could cause the abnormal data transmission in VPLS network. Are you sure the source-ip is unused in this VPLS? [Y/N]:y
    Ce-ping is in process...
    
    10.1.1.1 is used by 00e0-2324-df4a 

Using CE Ping to Check the Connectivity Between a PE and a CE in an EVC Model

After configuring a Bridge Domain (BD), you can use CE ping to check the connectivity between a PE and a CE in an Ethernet Virtual Connection (EVC) model.

Prerequisites

The network has been correctly configured, and the specified BD is Up.

Context

An EVC model unifies the Layer 2 bearer service model and configuration model. In an EVC model, you can use CE ping to check the link reachability between a PE and a CE in a specified BD. For details about EVCs, see HUAWEI NetEngine40E Feature Description-Local Area Network. For configuration details, see EVC Configuration.

When using CE ping to check the link reachability between a PE and a CE, you must specify a source IP address that meets the following conditions:

  • The source IP address must be on the same network segment as the CE's IP address. If they are on different network segments, the CE considers received CE Ping packets invalid and discards them.
  • The source IP address must be an unused IP address in the specified BD. If you specify a used IP address for the source IP address, CE Ping packets cannot be properly forwarded. As a result, the user using the source IP address cannot access the Internet. If you specify a gateway IP address for the source IP address, all users cannot access the Internet.

To avoid this problem, do not specify a used IP address as the source IP address.

Procedure

  1. Run the ce-ping ip-address bd bd-id source-ip source-ip-address [ mac mac-address ] [ interval interval | count count ] * command in any view to check the link reachability between a PE and a CE.

    <HUAWEI> ce-ping 10.1.1.1 bd 123 source-ip 10.1.1.2 mac e024-7fa4-d2cb interval 2 count 5
    Info: If the designated source IP address is in use, it could cause the abnormal data transmission in EVC network. Are you sure the source-ip is unused in this EVC? [Y/N]:y
    Ce-ping is in process...
    
    10.1.1.1 is used by 00e0-2324-df4a 

Download
Updated: 2018-07-12

Document ID: EDOC1100028538

Views: 29306

Downloads: 220

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