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

NE20E-S2 V800R010C10SPC500 Feature Description - System Monitor 01

This is NE20E-S2 V800R010C10SPC500 Feature Description - 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).
NQA Detection on an MPLS Network

NQA Detection on an MPLS Network

LSP Ping Test

An NQA LSP ping test checks the reachability of Label Distribution Protocol (LDP) label switched paths (LSPs) and Traffic Engineering (TE) constraint-routed LSPs (CR-LSPs). Figure 4-12 illustrates a network on which an NQA LSP ping test is performed. The LSP ping test process is as follows:

  1. The NQA client (PE-A) constructs a UDP MPLS Echo Request message with the destination IP field set to an IP address on the network segment 127.0.0.0/8. Then, the NQA client searches for the LDP LSP using the configured remote LSR ID and forwards the message along the LDP LSP in the MPLS domain. For a TE LSP, the message can be sent by a tunnel interface and forwarded along a specified CR-LSP.

  2. The egress (PE-B) monitors port 3503 and replies with an MPLS Echo Reply message.

    The NQA client calculates the time it takes to communicate between the NQA client and the egress by subtracting the time the NQA client received the MPLS Echo Reply message from the time the NQA client sent the MPLS Echo Request message. The data obtained is used to evaluate the MPLS network status.

Figure 4-12 LSP ping test networking

LSP Trace Test

An NQA label switched path (LSP) trace test monitors the forwarding paths of Label Distribution Protocol (LDP) LSPs and TE LSPs and collects statistics about each router along each forwarding path. Figure 4-13 illustrates a network on which an LSP trace test is performed. The LSP trace test process is as follows:

  1. The NQA client (PE-A) constructs a UDP MPLS Echo Request message with the destination IP field set to an IP address on the network segment 127.0.0.0/8. After that, the NQA client searches for an LSP. For a TE LSP, the message can be sent by a tunnel interface and forwarded along a specified CR-LSP. The Echo Request message includes the downstream mapping TLV carrying downstream information, including the next-hop address and outgoing label value. The TTL of the first Traceroute Echo Request message sent is 1.

  2. The MPLS Echo Request message is forwarded through the specified LSP in the MPLS domain. After the message reaches the first hop of the LSP, its TTL expires. The first hop then replies with an MPLS Echo Reply message.

  3. The NQA client continues to send the same Echo Request message, with the TTL increasing by 1 each time. This process continues until all the routers along the LSP reply with their MPLS Echo Reply messages. Then, the LSP trace process ends.

    Using the MPLS Echo Reply messages received from each hop, the NQA client obtains the LSP forwarding path between the NQA client and the destination and collects statistics about each router along the forwarding path. The data obtained is used to evaluate the LSP status.

Figure 4-13 LSP trace test networking

LSP Jitter Test

An NQA label switched path (LSP) jitter test measures the jitter, delay, and packet loss ratio on Label Distribution Protocol (LDP) LSPs and TE LSPs using timestamped UDP packets. Figure 4-14 illustrates a network on which an LSP jitter test is performed. The LSP jitter test process is as follows:

  1. The NQA client (PE-A) constructs a UDP MPLS Echo Request message with the destination IP field set to an IP address on the network segment 127.0.0.0/8. After that, the NQA client searches for the LDP LSP based on the specified remote LSR ID and forwards the message through the LDP LSP in the MPLS domain. For a TE LSP, the message can be sent by a tunnel interface and forwarded along a specified CR-LSP.

  2. The egress of the LSP (PE-B) monitors port 3503, marks each received packet with a timestamp, and replies with an MPLS Echo Reply message.

  3. After receiving the MPLS Echo Reply message, the NQA client calculates the packet jitter by subtracting the interval between receipts of packets on the egress from the interval between transmissions of packets on the NQA client.

    Using the received MPLS Echo Reply message, the NQA client calculates the maximum, minimum, and average jitter time in the transmission of the UDP packet from the NQA client to the egress. The data obtained is used to evaluate the network status.

Figure 4-14 LSP jitter test networking

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055478

Views: 5149

Downloads: 2

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