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).
Affinity Naming Function

Affinity Naming Function

The affinity naming function simplifies the configuration of tunnel affinities and link administrative group attributes. Using this function, you can query whether a tunnel affinity matches a link administrative group attribute.

Background

A tunnel affinity and a link administrative group attribute are 32-bit hexadecimal numbers. An IGP (IS-IS or OSPF) advertises the administrative group attribute to devices in the same IGP area. RSVP-TE advertises the tunnel affinity to downstream devices. CSPF on the ingress checks whether administrative group bits match affinity bits to determine whether a link can be used to establish a CR-LSP.

Hexadecimal calculations are complex during network deployment, and maintaining and querying tunnels established using hexadecimal calculations are difficult. Each bit in a hexadecimal-number affinity can be assigned a name. In this example, colors are used to name affinity bits. Naming affinity bits help verify that tunnel affinity bits match link administrative group bits, therefore facilitating network planning and deployment.

Implementation

An affinity name template can be configured to manage the mapping between affinity bits and names. Configuring the same template on all nodes on an MPLS network is recommended. Inconsistent configuration may cause a service provision failure. You can name each of 32 affinity bits differently. As shown in Figure 4-13,, the affinity bits are named using colors. The second affinity bit is "red", the fourth bit is "blue", and the sixth bit is "brown."
Figure 4-13 Affinity naming example

Bits in a link administrative group must also be configured the same names as the affinity bits.

Once affinity bits are named, you can then determine which links a CR-LSP can include or exclude on the ingress. Rules for selecting links are as follows:
  • include-any: CSPF includes a link when calculating a path, if at least one link administrative group bit has the same name as an affinity bit.
  • exclude: CSPF excludes a link when calculating a path, if any link administrative group bit has the same name as an affinity bit.
  • include-all: CSPF includes a link when calculating a path, only if each link administrative group bit has the same name as each affinity bit.

Usage Scenarios

The affinity naming function is used when CSPF calculates paths over which RSVP-TE establishes CR-LSPs.

Benefits

The affinity naming function allows you to easily and rapidly use affinity bits to control paths over which CR-LSPs are established.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055471

Views: 8095

Downloads: 7

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