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-M2 V800R010C10SPC500 Feature Description - Segment Routing 01

This is NE40E-M2 V800R010C10SPC500 Feature Description - Segment Routing
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).
SR OAM

SR OAM

SR Operation, Administration, and Maintenance (OAM) monitors LSP connectivity and rapidly detects faults. SR OAM is implemented using ping and tracert.

SR-BE Ping

On the network shown in Figure 2-61, PE1, P1, P2, and PE2 are all capable of SR. An SR LSP is established between PE1 and PE2.
Figure 2-61 SR-BE ping/tracert
The process of initiating an SR IPv4 ping test from PE1 is as follows:
  1. PE1 initiates a ping test and checks whether the specified tunnel type is SR-BE IPv4.
    • If the specified tunnel type is not SR-BE IPv4, PE1 reports an error message indicating a tunnel type mismatch and stops the ping test.
    • If the specified tunnel type is SR-BE IPv4, the following operations are performed:
  2. PE1 constructs an MPLS Echo Request packet encapsulating the outer label of the initiator and carrying destination address 127.0.0.0/8 in the IP header of the packet.
  3. PE1 forwards the packet to P1. After receiving the packet, P1 swaps the outer MPLS label of the packet and forwards the packet to P2.
  4. Similar to P1, P2 swaps the outer MPLS label of the received packet and determines whether it is the penultimate hop. If yes, P2 removes the outer label and forwards the packet to PE2. PE2 sends the packet to the Rx/Tx module for processing.
  5. PE2 returns an MPLS Echo Reply packet to PE1 and generates the ping test result.

SR-BE Tracert

On the network shown in Figure 2-61, the process of initiating an SR-BE IPv4 tracert test from PE1 is as follows:
  1. PE1 initiates a ping test and checks whether the specified tunnel type is SR-BE IPv4.
    • If the specified tunnel type is not SR-BE IPv4, PE1 reports an error message indicating a tunnel type mismatch and stops the tracert test.
    • If the specified tunnel type is SR-BE IPv4, the following operations are performed:
  2. PE1 constructs an MPLS Echo Request packet encapsulating the outer label of the initiator and carrying destination address 127.0.0.0/8 in the IP header of the packet.
  3. PE1 forwards the packet to P1. After receiving the packet, P1 determines whether the TTL–1 value in the outer label of the received packet is 0.
    • If the TTL–1 value is 0, an MPLS TTL timeout occurs. P1 sends the packet to the Rx/Tx module for processing and returns a reply packet to PE1.
    • If the TTL–1 value is greater than 0, P1 swaps the outer MPLS label of the packet, searches the forwarding table for the outbound interface, and forwards the packet to P2.
  4. Similar to P1, P2 also performs the following operations:
    • If the TTL–1 value is 0, an MPLS TTL timeout occurs. P2 sends the packet to the Rx/Tx module for processing and returns a reply packet to PE1.
    • If the TTL–1 value is greater than 0, P2 swaps the outer MPLS label of the received packet and determines whether it is the penultimate hop. If yes, P2 removes the outer label, searches the forwarding table for the outbound interface, and forwards the packet to PE2.
  5. PE2 sends the packet to the Rx/Tx module for processing, returns an MPLS Echo Reply packet to PE1, and generates the tracert test result.

SR-TE Ping

On the network shown in Figure 2-62, PE1, P1, and P2 all support SR. An SR-TE tunnel is established between PE1 and PE2. The devices assign adjacency labels as follows:
  • PE1 assigns adjacency label 9001 to PE1-P1 adjacency.
  • P1 assigns adjacency label 9002 to P1-P2 adjacency.
  • P2 assigns adjacency label 9005 to P2-PE2 adjacency.
Figure 2-62 SR-TE ping and tracert
The process of initiating an SR-TE ping test from PE1 is as follows:
  1. PE1 initiates a ping test and checks whether the specified tunnel type is SR-TE.
    • If the specified tunnel type is not SR-TE, PE1 reports an error message indicating a tunnel type mismatch and stops the ping test.
    • If the specified tunnel type is SR-TE, the following operations are performed:
  2. PE1 constructs an MPLS Echo Request packet encapsulating label information about the entire tunnel and carrying destination address 127.0.0.0/8 in the IP header of the packet.
  3. PE1 forwards the packet to P1. P1 removes the outer label (9002) of the received packet and forwards the packet to P2.
  4. P2 removes the outer label (9005) of the received packet and forwards the packet to PE2 for processing.
  5. PE2 returns an MPLS Echo Reply packet to PE1.

SR-TE Tracert

On the network shown in Figure 2-62, the process of initiating an SR-TE tracert test from PE1 is as follows:
  1. PE1 initiates a tracert test and checks whether the specified tunnel type is SR-TE.
    • If the specified tunnel type is not SR-TE, PE1 reports an error message indicating a tunnel type mismatch and stops the tracert test.
    • If the specified tunnel type is SR-TE, the following operations are performed:
  2. PE1 constructs an MPLS Echo Request packet encapsulating label information about the entire tunnel and carrying destination address 127.0.0.0/8 in the IP header of the packet.
  3. PE1 forwards the packet to P1. After receiving the packet, P1 determines whether the TTL-1 value in the outer label is 0.
    • If the TTL-1 value is 0, an MPLS TTL timeout occurs. P1 sends the packet to the Rx/Tx module for processing and returns an MPLS Echo Reply packet to PE1.
    • If the TTL-1 value is greater than 0, P1 removes the outer MPLS label of the packet, buffers the TTL-1 value, copies the value to the new outer MPLS label, searches the forwarding table for the outbound interface, and forwards the packet to P2.
  4. Similar to P1, P2 also determines whether the TTL-1 value in the outer label of the received packet is 0.
    • If the TTL-1 value is 0, an MPLS TTL timeout occurs. P2 sends the packet to the Rx/Tx module for processing and returns an MPLS Echo Reply packet to P1.
    • If the TTL-1 value is greater than 0, P2 removes the outer MPLS label of the packet, buffers the TTL-1 value, copies the value to the new outer MPLS label, searches the forwarding table for the outbound interface, and forwards the packet to PE2.
  5. P2 forwards the packet to PE2, and PE2 returns an MPLS Echo Reply packet to PE1.
Download
Updated: 2019-01-02

Document ID: EDOC1100058411

Views: 2815

Downloads: 12

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