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 V800R010C10SPC500 Configuration Guide - IP Routing 01

This is NE40E V800R010C10SPC500 Configuration Guide - IP 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).
Configuring BGP RPD

Configuring BGP RPD

RPD provides a new method of distributing route-policies and allows the NCE-IP to efficiently and dynamically deploy route-policies.

Usage Scenario

In a MAN ingress or IGW scenario, uneven link resource usage or link faults may cause link congestion. To make full use of network bandwidth, you can deploy an inbound traffic optimization solution to adjust route priorities so that traffic is diverted to idle links. In such a scenario, the router functions as a forwarder, and RPD needs to be deployed on it.

In Figure 10-17, an inbound traffic optimization solution is deployed so that traffic from AS 200 to the backbone network is monitored and scheduled in real time. If the link from Device C to Device A is congested, the traffic enters AS 100 through Device B and reaches the backbone network by path of the PE.

Figure 10-17 Typical networking of inbound traffic optimization

In this scenario, forwarders receive RPD policies delivered by the NCE-IP and adjust route attributes and advertise routes based on the policies. The traffic optimization policy is configured on the NCE-IP based on the traffic application. The following section describes relevant configurations on the forwarders. For details about how to configure the NCE-IP, see the NCE-IP manual.

Pre-configuration Tasks

Before configuring BGP RPD, configure basic BGP functions and establish a connection between the forwarder and the NCE-IP to ensure route reachability between them.

Procedure

  • Configure basic RPD functions.
    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    3. Run rpd-family

      BGP RPD is enabled, and the BGP RPD address family view is displayed.

    4. Run peer enable

      BGP is enabled to exchange routing information with the specified peer.

    5. Run quit

      Return to the BGP view.

    6. Run ipv4-family unicast

      The IPv4 unicast address family view is displayed.

    7. Run peer ipv4-address rpd-policy export enable

      The RPD export route-policy function is enabled in the IPv4 unicast address family view.

    8. Run commit

      The configuration is committed.

  • (Optional) Configure GR to prevent the traffic interruption caused by a protocol restart.
    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    3. Run graceful-restart

      GR is enabled in the BGP view.

    4. Run rpd-family

      The BGP RPD address family view is displayed.

    5. Run peer ipv4-address peer graceful-restart static-timer restart-timer

      GR is enabled in the BGP RPD address family, and a GR restart timer is set.

    6. Run commit

      The configuration is committed.

  • (Optional) Configure router ID-based filtering on non-RRs in the RR scenario so that the non-RRs only accept the RPD routes that match the router ID of the local BGP process. If a large number of RPD routes are accepted, a large number of policy nodes are generated accordingly, which reduces the performance.
    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    3. Run rpd-family

      The BGP RPD address family view is displayed.

    4. Run router-id filter

      Router ID-based filtering is enabled.

  • (Optional) Configure a delay for protocols to apply an updated RPD route-policy if the original policy changes.
    1. Run ipv4-family unicast

      The IPv4 unicast address family view is displayed.

    2. Run rpd-policy change notify-delay delay-time

      A delay is configured for protocols to apply an updated RPD route-policy if the original policy changes.

Checking the Configurations

After completing the configurations, you can run the following commands to check the configurations.
  • Run the display bgp peer ipv4-address rpd export-policy command to check RPD route-policies.

  • Run the display bgp rpd routing-table command to check information about RPD routes.

# Run the display bgp peer ipv4-address rpd export-policy command to check RPD route-policies of a specified peer.

<HUAWEI> display bgp peer 10.1.1.1 rpd export-policy
 permit : 1  
  Match clauses:   
   if-match ip-prefix 0.0.0.0/24 match-network   
   if-match ip-prefix 1.1.1.0/24 ge 24 le 26    
   if-match ip-prefix 2.2.2.0/24 ge 25 le 26   
   if-match ip-prefix 3.3.3.0/24 ge 28 le 32    
   if-match community-filter internet    
   if-match community-filter no-advertise    
   if-match community-filter no-export   
   if-match community-filter no-export-subconfed  
   if-match community-filter 6000:8000   
   if-match community-filter 100:0   
   if-match community-filter 123 234 2342 35:48582   
   if-match as-path 1$ 2# 3% 4&     
   if-match as-path 5& 6*  
  Apply clauses:     
   apply as-path 123 23234 35.51474 35.48583 3.37626 additive   
   apply cost - 30 

# Run the display bgp rpd routing-table command to check information about RPD routes.

<HUAWEI> display bgp rpd routing-table
 Total number of Routes : 1
 BGP Local router ID is 1.1.1.1
 Status codes: * - valid, > - best, d - damped, x - best external, a - add path,
               h - history,  i - internal, s - suppressed, S - Stale
               Origin : i - IGP, e - EGP, ? - incomplete
        Network                        Peer           MED        LocPrf    PrefVal Path/Ogn 
 *>     1/1.1.1.1/1                    192.168.1.1    60                   0       100?
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 48966

Downloads: 201

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