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


To have a better experience, please upgrade your IE browser.


NE20E-S2 V800R010C10SPC500 Feature Description - MPLS 01

This is NE20E-S2 V800R010C10SPC500 Feature Description - MPLS
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).
Checking the Source Interface of a Static CR-LSP

Checking the Source Interface of a Static CR-LSP

A device uses the static CR-LSP's source interface check function to check whether the inbound interface of labeled packets is the same as that of a configured static CR-LSP. If the inbound interfaces match, the device forwards the packets. If the inbound interfaces do not match, the device discards the packets.


A static CR-LSP is established using manually configured forwarding and resource information. Signaling protocols and path calculation are not used during the setup of CR-LSPs. Setting up a static CR-LSP consumes a few resources because the two ends of the CR-LSP do not need to exchange MPLS control packets. The static CR-LSP cannot be adjusted dynamically in a changeable network topology. A static CR-LSP configuration error may cause protocol packets of different NEs and statuses interfere one another, which adversely affects services. To address the preceding problem, a device can be enabled to check source interfaces of static CR-LSPs. With this function configured, the device can only forward packets if both labels and inbound interfaces are correct.


In Figure 2-11, static CR-LSP1 is configured, with PE1 functioning as the ingress, the P as a transit node, and PE2 as the egress. The P's inbound interface connected to PE1 is Interface1 and the incoming label is Label1. Static CR-LSP2 remains on PE3 that functions as the ingress of CR-LSP2. The P's inbound interface connected to PE3 is Interface2 and the incoming label is Label1. If PE3 sends traffic along CR-LSP2 and Interface2 on the P receives the traffic, the P checks the inbound interface information and finds that the traffic carries Label2 but the inbound interface is not Interface2. Consequently, the P discards the traffic.

Figure 2-11 Checking the source interface of a static CR-LSP

Updated: 2019-01-02

Document ID: EDOC1100055471

Views: 7300

Downloads: 6

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