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).
Controlling Route Advertisement

Controlling Route Advertisement

BGP4+ can filter or apply routing policies to the routes to be advertised to a peer or peer group.

Usage Scenario

BGP4+ advertises routes to peers based on the network plan to exchange routing information between devices. The routes can be filtered or processed based on a routing policy before being advertised to a peer or peer group.

Pre-configuration Tasks

Before controlling route advertisement, configure basic BGP4+ functions.

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring BGP4+ Route Summarization

Configuring route summarization can reduce the size of a routing table on a peer.

Context

On a large-scale BGP4+ network, configuring route summarization can reduce the number of advertised route prefixes and improve BGP4+ stability.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run ipv6-family unicast

    The IPv6 unicast address family view is displayed.

  4. Run one of the following commands to configure route summarization as needed.

    • To advertise all summarized routes and specific routes, run aggregate ipv6-address { mask | mask-length }

    • To advertise only summarized routes, run aggregate ipv6-address { mask | mask-length } detail-suppressed

    • To advertise some of the specific routes, run aggregate ipv6-address { mask | mask-length } suppress-policy route-policy-name

      Using the peer route-policy command can also advertise some of the specific routes.

    • To generate a summarized route used for loop detection, run aggregate ipv6-address { mask | mask-length } as-set

    • To configure the attributes of summarized routes, run aggregate ipv6-address { mask | mask-length } attribute-policy route-policy-name

      Using the peer route-policy command can also configure the attributes of summarized routes.

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

    • To generate summarized routes based on some of the specific routes, run aggregate ipv6-address { mask | mask-length } origin-policy route-policy-name

    Manual summarization is valid for routing entries in the local BGP4+ routing table. For example, if a route with a mask longer than 64, such as 9:3::1/128, does not exist in the BGP4+ routing table, BGP4+ does not advertise the summarized route after the aggregate 9:3::1 64command is used to summarize routes.

  5. Run commit

    The configuration is committed.

Configuring BGP4+ to Advertise Default Routes to Peers or peer groups

A device sends a default route with the local address as the next hop address to the specified peer for load balancing, regardless of whether there are default routes in the local routing table. This greatly reduces the number of routes on the network.

Context

Default routes can be used on networks that have the following characteristics:
  • There are multiple EBGP peers, and each peer can receive full Internet routes.

  • There are multiple Route Reflectors (RRs), and each RR can receive full Internet routes.

When load balancing is not performed on the network, a BGP4+ peer receives at most one copy of active full Internet routes. After load balancing is performed on the network, the number of active routes received by the BGP4+ peer doubles, which causes the number of routes on the network to sharply increase. In this case, you can configure the local device to advertise only default routes to its BGP4+ peer and use default routes for load balancing, which can greatly reduce the number of routes on the network.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run ipv6-family unicast

    The IPv6 unicast address family view is displayed.

  4. Run peer { ipv4-address | ipv6-address | group-name } default-route-advertise [ route-policy route-policy-name | route-filter route-filter-name ] [ conditional-route-match-all { ipv6-address1 ipv6-mask-length1 } &<1-4> | conditional-route-match-any { ipv6-address2 ipv6-mask-length2 } &<1-4> ]

    Default routes are sent to a remote peer or peer group.

    If route-policy route-policy-name or route-filter route-filter-name is set, the BGP device changes attributes of the default route based on the specified route policy.

    If conditional-route-match-all { ipv6-address1 ipv6-mask-length1 } &<1-4> is set, the BGP device sends the default route to the peer only when routes that match all the all specified conditions exist in the local IPv6 routing table.

    If conditional-route-match-any { ipv6-address2 ipv6-mask-length2 } &<1-4> is set, the local device sends a default route to the peer when routes that match any of the specified conditions exist in the local IPv6 routing table.

    NOTE:

    After the peer default-route-advertise command is run, BGP4+ sends a default route with the local address as the next hop to the specified peer, regardless of whether there are default routes in the routing table.

  5. Run commit

    The configuration is committed.

Configuring BGP4+ to Advertise the Community Attribute

The community attribute is used to simplify routing policy management. Compared with a peer group, the community attribute has a larger management scope. It can control routing policies for multiple BGP4+ devices.

Context

The community attribute is transmitted between BGP4+ peers, and its transmission is not restricted within ASs. With the community attribute, a group of routes can share the same routing policy. Before sending a route with the community attribute to peers, BGP4+ can change the original community attribute carried by the route.

Procedure

  • Configure BGP4+ to send the community attribute to peers.

    Perform the following steps on a BGP4+ device:

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv6-family unicast

      The IPv6 unicast address family view is displayed.

    4. Run the following command as needed.

      • To send the standard community attribute to a peer group, run peer { ipv4-address | ipv6-address | group-name } advertise-community

      • To send the extended community attribute to a peer group, run peer { ipv4-address | ipv6-address | group-name } advertise-ext-community

    5. Run commit

      The configuration is committed.

  • Apply a routing policy to the routes to be advertised.

    Perform the following steps on a BGP4+ device:

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv6-family unicast

      The IPv6 unicast address family view is displayed.

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

      An export routing policy is configured.

    5. Run commit

      The configuration is committed.

    NOTE:
    • When configuring a BGP4+ community, use a routing policy to define a specific community attribute. After that, apply the routing policy to the routes to be advertised.

    • For details on routing policy configurations, see Routing Policy Configuration.

Setting the Interval at Which Update Packets Are Sent

When routes change, the ME device sends Update packets to notify its peers. If a route changes frequently, set an interval at which Update packets are sent to prevent the ME device from sending Update packets for every change.

Context

Perform the following steps on a BGP4+ device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run ipv6-family unicast

    The IPv6 unicast address family view is displayed.

  4. Run peer ipv6-address route-update-interval interval

    The interval at which Update packets are sent is set.

  5. Run commit

    The configuration is committed.

Verifying the Configuration of Route Advertisement

After controlling route advertisement, check information about filtered and advertised routes.

Prerequisites

Configurations have been performed to control route advertisement.

Procedure

  • Run the display bgp ipv6 network command to check routing information advertised by BGP4+.
  • Run the display bgp routing-table cidr command to check Classless InterDomain Routing (CIDR) information.
  • Run the display bgp ipv6 routing-table community [ aa:nn &<1-13> ] [ internet | no-advertise | no-export | no-export-subconfed ] * [ whole-match ] command to check information about the routes carrying the specified BGP4+ community attribute.
  • Run the display bgp ipv6 peer ipv4-address verbose command to check information about BGP4+ peers.
  • Run the display bgp ipv6 peer ipv6-address { log-info | verbose } command to check the log information about BGP4+ peers.

Example

# Run the display bgp ipv6 network command to check routing information advertised by BGP4+. For example:

<HUAWEI> display bgp ipv6 network
BGP Local Router ID is 5.5.5.5
Local AS Number is 100(PublicV6)
Network          Mask            Route-policy

100::            64
200::            64

# Run the display bgp ipv6 peer command to view information about BGP4+ peers. For example:

<HUAWEI> display bgp ipv6 peer
BGP Local router ID : 20.0.0.1 
local AS number : 100
 Total number of peers : 1                 Peers in established state : 1

 Peer            V    AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv
 2001:db8:20::21 4   200       17       19     0 00:09:59 Established       3
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20946

Downloads: 15

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