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 - 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).
Static Bidirectional Co-routed LSPs

Static Bidirectional Co-routed LSPs

A co-routed bidirectional static CR-LSP is an important feature that enables LSP ping messages, LSP tracert messages, and OAM messages and replies to travel through the same path.

Background

Service packets exchanged by two nodes must travel through the same links and nodes on a transport network without running a routing protocol. Co-routed bidirectional static CR-LSPs can be used to meet the requirements.

Definition

A co-routed bidirectional static CR-LSP is a type of CR-LSP over which two flows are transmitted in opposite directions over the same links. A co-routed bidirectional static CR-LSP is established manually.

A co-routed bidirectional static CR-LSP differs from two LSPs that transmit traffic in opposite directions. Two unidirectional CR-LSPs bound to a co-routed bidirectional static CR-LSP function as a single CR-LSP. Two forwarding tables are used to forward traffic in opposite directions. The co-routed bidirectional static CR-LSP can go Up only when the conditions for forwarding traffic in opposite directions are met. If the conditions for forwarding traffic in one direction are not met, the bidirectional CR-LSP is in the Down state. If no IP forwarding capabilities are enabled on the bidirectional CR-LSP, any intermediate node on the bidirectional LSP can reply with a packet along the original path. The co-routed bidirectional static CR-LSP supports the consistent delay and jitter for packets transmitted in opposite directions, which guarantees QoS for traffic transmitted in opposite directions.

Implementation

A bidirectional co-routed static CR-LSP is manually established. A user manually specifies labels and forwarding entries mapped to two FECs for traffic transmitted in opposite directions. The outgoing label of a local node (also known as an upstream node) is equal to the incoming label of a downstream node of the local node.

A node on a co-routed bidirectional static CR-LSP only has information about the local LSP and cannot obtain information about nodes on the other LSP. A co-routed bidirectional static CR-LSP shown in Figure 4-46 consists of a CR-LSP and a reverse CR-LSP. The CR-LSP originates from the ingress and terminates on the egress. Its reverse CR-LSP originates from the egress and terminates on the ingress.

Figure 4-46 Co-routed bidirectional static CR-LSP
The process of configuring a co-routed bidirectional static CR-LSP is as follows:
  • On the ingress, configure a tunnel interface and enable MPLS TE on the outbound interface of the ingress. If the outbound interface is Up and has available bandwidth higher than the bandwidth to be reserved, the associated bidirectional static CR-LSP can go Up, regardless of the existence of transit nodes or the egress node.
  • On each transit node, enable MPLS TE on the outbound interface of the bidirectional CR-LSP. If the outbound interface is Up and has available bandwidth higher than the bandwidth to be reserved for the forward and reverse CR-LSPs, the associated bidirectional static CR-LSP can go Up, regardless of the existence of the ingress, other transit nodes, or the egress node.
  • On the egress, enable MPLS TE on the inbound interface. If the inbound interface is Up and has available bandwidth higher than the bandwidth to be reserved for the bidirectional CR-LSP, the associated bidirectional static CR-LSP can go Up, regardless of the existence of the ingress node or transit nodes.
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055471

Views: 8031

Downloads: 7

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