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 Multicast 01

This is NE40E V800R010C10SPC500 Configuration Guide - IP Multicast
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 MBGP Load Balancing

Configuring MBGP Load Balancing

MBGP load balancing improves network resource usage.

Usage Scenario

Traffic can be balanced among BGP routes only when the first nine attributes described in "BGP Route Selection Rules" and the AS_Path of the routes are the same.

Pre-configuration tasks

Before configuring MBGP load balancing, configure MBGP peers.

Procedure

  • Configure MBGP peer or peer group-based load balancing.

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-family multicast

      The BGP-IPv4 multicast address family view is displayed.

    4. Run peer { ipv4-address | group-name } load-balancing [ as-path-ignore | as-path-relax ]

      MBGP peer or peer group-based load balancing is configured.

      After the peer load-balancing command is run, BGP peer-based load balancing is implemented only when the following conditions are met:
      • The routes are received from the specified peer or peer group.
      • The optimal route and optimal equal-cost routes exist.
      • The AS_Path attribute is the same as that of the optimal route, or as-path-ignore or as-path-relax is specified in the peer load-balancing command.
        • If as-path-ignore is specified, the device ignores comparing AS_Path attributes when selecting routes for load balancing. In this case, routes can participate in load balancing even if their AS_Path attributes are different.
        • If as-path-relax is specified, the device ignores comparing the AS_Path attributes of the same length when selecting routes for load balancing. In this case, routes cannot participate in load balancing if their AS_Path attributes are of different lengths. For example, the AS_Path attribute of route A is 10, and the AS_Path attribute of route B is 10, 20. Because the two AS_Path attributes are of different lengths, the two routes cannot participate in load balancing.
    5. Run commit

      The configuration is committed.

  • Configure global MBGP load balancing.

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-family multicast

      The BGP-IPv4 multicast address family view is displayed.

    4. Run maximum load-balancing [ ebgp | ibgp ] number

      The maximum number of MBGP routes for load balancing is set.

    5. Run commit

      The configuration is committed.

Checking the Configurations

After configuring MBGP load balancing, check the configurations.

  • Run the display bgp multicast routing-table command to check the information about the MBGP routing table.

# Run the display bgp multicast routing-table command. The command output shows the MBGP routes for load balancing.

<HUAWEI>display bgp multicast routing-table 1.1.1.1
 BGP local router ID : 1.1.1.1
 Local AS number : 100
 Paths : 2 available, 1 best, 2 select
 BGP routing table entry information of 8.1.1.0/24:
 From: 200.1.1.2 (2.2.2.2)
 Route Duration: 0d00h03m55s
 Direct Out-interface: GigabitEthernet1/0/0
 Original nexthop: 200.1.1.2
 Qos information : 0x0
 AS-path 200 300, origin igp, pref-val 0, valid, external, best, select, pre 255
 Advertised to such 2 peers
    200.1.1.2
    200.1.2.2

 BGP routing table entry information of 8.1.1.0/24:
 From: 200.1.2.2 (3.3.3.3)
 Route Duration: 0d00h03m56s
 Direct Out-interface: GigabitEthernet2/0/0
 Original nexthop: 200.1.2.2
 Qos information : 0x0
 AS-path 200 300, origin igp, pref-val 0, valid, external, select, pre 255, not preferred for router ID
 Not advertised to any peers yet
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 44171

Downloads: 97

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