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

ME60 V800R010C10SPC500 Configuration Guide - IP Routing 01

This is ME60 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 Route Aggregation

Configuring BGP Route Aggregation

Configuring BGP Route Aggregation on a device can reduce the sizes of routing tables on the peers of the device.

Usage Scenario

The BGP routing table of a device on a medium or large BGP network contains a large number of routing entries. Storing the routing table consumes a large number of memory resources, and transmitting and processing routing information consume lots of network resources. Configuring route aggregation can reduce the size of a routing table, prevent specific routes from being advertised, and minimize the impact of route flapping on network performance. BGP route aggregation and routing policies enable BGP to effectively transmit and control routes.

BGP supports automatic and manual aggregation. Manual aggregation takes precedence over automatic aggregation.

Pre-configuration Tasks

Before configuring BGP route aggregation, complete the following task:

Procedure

  • Configure automatic route aggregation.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-family unicast

      The IPv4 unicast address family view is displayed.

    4. Run summary automatic

      Automatic aggregation is configured for imported routes.

      The summary automatic command aggregates routes imported by BGP. The routes can be direct routes, static routes, RIP routes, OSPF routes, or IS-IS routes. After this command is run, BGP aggregates routes based on natural network segments. The command, however, cannot aggregate routes imported using the network command.

    5. Run commit

      The configuration is committed.

  • Configure manual route aggregation.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-family unicast

      The IPv4 unicast address family view is displayed.

    4. Configure manual aggregation according to the actual networking.

      • To advertise both the aggregated route and specific routes, run the aggregate ipv4-address { mask | mask-length } command.

      • To advertise only the aggregated route, run the aggregate ipv4-address { mask | mask-length } detail-suppressed command.

      • To advertise a specific route, run the aggregate ipv4-address { mask | mask-length } suppress-policy route-policy-name command.

        To advertise a specific route, you can also run the peer route-policy command.

      • To generate an aggregated route used to detect a loop, run the aggregate ipv4-address { mask | mask-length } as-set command.

      • To set the attributes of an aggregated route, run the aggregate ipv4-address { mask | mask-length } attribute-policy route-policy-name command.

        To set the attributes of an aggregated route, you can also run the peer route-policy command.

        If as-set is set in the aggregate command and the apply as-path command is run to set the AS_Path attribute, the AS_Path attribute does not take effect.

      • To generate an aggregated route according to certain specific routes, run the aggregate ipv4-address { mask | mask-length } origin-policy route-policy-name command.

      Manual aggregation is valid for the existent routing entries in the local BGP routing table. For example, if the route with the mask length longer than 16 such as 10.1.1.1/24, does not exist in the BGP routing table, BGP does not advertise the aggregated route after the aggregate 10.1.1.1 16 command is used to aggregate routes.

    5. Run commit

      The configuration is committed.

Checking the Configurations

After route aggregation is configured, you can check whether the configuration is correct.

  • Run the display bgp routing-table [ network [ mask | mask-length ] ] command to check information about BGP aggregated routes.

# Run the display bgp routing-table network command to view information about BGP aggregated routes.

<HUAWEI> display bgp routing-table 192.168.0.0
 BGP local router ID : 2.2.2.2
 Local AS number : 10
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 192.168.0.0/16:
 From: 10.2.1.2 (3.3.3.3)
 Route Duration: 1d09h07m46s
 Relay IP Nexthop: 10.2.1.2
 Relay IP Out-interface: GigabitEthernet1/0/0
 Original nexthop: 10.2.1.2
 Qos information : 0x0
 AS-path 100, origin incomplete, pref-val 0, valid, external, best, select, pre 255
 Aggregator: AS 100, Aggregator ID 3.3.3.3, Atomic-aggregate
 Advertised to such 2 peers:
    10.1.1.1
    10.2.1.2  
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 22407

Downloads: 15

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