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).
Using XPL to Filter the BGP Routes to Be Advertised

Using XPL to Filter the BGP Routes to Be Advertised

A BGP device can use a route-filter to filter the routes to be advertised and modify route attributes to control the network traffic forwarding path.

Usage Scenario

BGP is used to transmit routing information between ASs, and route advertisement directly affects traffic forwarding.

In most cases, a BGP routing table has a large number of routes. Transmitting them will intensify the load of a device. To address this problem, configure the device to advertise only desired routes.

In addition, multiple routes to the same destination may exist and travel through different ASs. To direct routes to specific ASs, you also need to filter the routes to be advertised.

You can use XPL route-filters to control the BGP routes to be advertised to all peers or peer groups or to a specified peer or peer group.

Pre-configuration Tasks

Before using XPL to filter the BGP routes to be advertised, configure basic BGP functions.

Procedure

  • Use XPL to filter the BGP routes to be advertised to all peers or peer groups.

    Perform the following steps on the BGP device:

    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 ipv4-family unicast

      The IPv4 unicast address family view is displayed.

    4. Run route-filter route-filter-name export [ direct | isis process-id | ospf process-id | rip process-id | static ]

      The BGP device is configured to filter the routes to be advertised to all peers or peer groups.

    5. Run commit

      The configuration is committed.

  • Use XPL to filter the BGP routes to be advertised to a specific peer or peer group.

    Perform the following steps on the BGP device:

    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 ipv4-family unicast

      The IPv4 unicast address family view is displayed.

    4. Run peer { group-name | ipv4-address } route-filter route-filter-name export

      The BGP device is configured to filter the routes to be advertised to the specified peer or peer group.

    5. Run commit

      The configuration is committed.

Checking the Configuration

Run the following commands to check configurations:

  • Run the display xpl route-filter state [ attached | unattached ] command to check information about the configured route-filter.
  • Run the display bgp routing-table [ peer ipv4-address advertised-routes [ statistics ] ] command to check the routes in the BGP routing table.

# Run the display xpl route-filter state command to view information about the configured route-filter.

<HUAWEI> display xpl route-filter state
Attached :Applied by at least one attach point
Unattached : Not applied by any attach point

Attached
---------------------------------------------------------------
r1

Unattached
---------------------------------------------------------------

# Run the display bgp routing-table peer ipv4-address advertised-routes command to view routes in the BGP routing table.

<HUAWEI> display bgp routing-table peer 1.1.1.1 advertised-routes
 BGP Local router ID is 3.3.3.3
 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
 RPKI validation codes: V - valid, I - invalid, N - not-found


 Total Number of Routes: 7
      Network            NextHop        MED        LocPrf    PrefVal Path/Ogn

 *>   3.3.3.3/32         1.1.1.2        0                     0      200?
 *>   1.1.1.0/30         1.1.1.2        0                     0      200?
 *>   1.1.1.1/32         1.1.1.2        0                     0      200?
 *>   1.3.1.0/30         1.1.1.2        0                     0      200?
 *>   1.3.1.1/32         1.1.1.2        0                     0      200?
 *>   1.4.1.0/30         1.1.1.2        0                     0      200?
 *>   1.4.1.1/32         1.1.1.2        0                     0      200?
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 48257

Downloads: 201

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