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

Configuration Guide - IP Unicast Routing

CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.

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).
Enable BGP-LS

Enable BGP-LS

Context

BGP-LS needs to be deployed on the controller and the devices connected to it. The Switch will summarize process or AS topology information and report the complete information to the controller by using the bgp after the BGP-LS is enabled.

Procedure

  1. Run system-view

    The system view is displayed.

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

    BGP is started, the local AS number is specified, and the BGP view is displayed.

  3. Run peer { group-name | ipv4-address } as-number { as-number-plain | as-number-dot }

    The IP address and AS number of a BGP peer is specified.

    A BGP-LS peer relationship needs to be established between each switch that collects topology information and the controller, and between switches on which BGP-LS is enabled.

  4. Run link-state-family unicast

    The BGP-LS address family view is displayed.

  5. Run peer { group-name | ipv4-address } enable

    The BGP-LS route exchange with the specified peer or peer group is enabled.

  6. (Optional)Run domain identifier domain-id

    Configure a BGP-LS domain ID.

    A BGP-LS domain ID indicates that BGP-LS is enabled on a device. If no BGP-LS domain ID is configured, a BGP router ID is used as the BGP-LS domain ID by default. One BGP-LS domain ID can be configured for multiple devices so that the controller calculates routes based on the combined topology information reported by the devices.

  7. (Optional)Run domain as { domain as-plain | domain as-dot }

    Configure a BGP-LS domain AS number.

    By default, a BGP AS number is used as the BGP-LS domain AS number. Two devices with different BGP AS numbers must have the same BGP-LS domain AS number configured using the domain as command so that the controller can obtain combined topology information about the two ASs for route calculation.

  8. (Optional)Run peer { group-name | ipv4-address } reflect-client

    Configure an RR and specify a client for it.

    The device where the peer reflect-client command is run functions as the RR, and the specified peer or peer group functions as a client.

    NOTE:

    If the clients of an RR are fully meshed, you can run the undo reflect between-clients command to disable route reflection among these clients to reduce bandwidth consumption.

    If a cluster has multiple RRs configured, run the reflector cluster-id cluster-id command to configure the same cluster ID for all the RRs. This command is applicable only to RRs.

  9. (Optional)Run peer { group-name | ipv4-address } route-limit limit [ percentage ] [ alert-only | idle-forever | idle-timeout minutes ]

    The maximum number of BGP-LS routes that can be received from a specified peer is set.

    In most cases, the BGP-LS routing table contains a large number of BGP-LS routes. If a lot of BGP-LS routes are received from peers, many system resources will be consumed. To reduce system resource consumption, you can configure the maximum number of routes that a router can receive from a BGP-LS peer.

  10. (Optional)Run peer { group-name | ipv4-address } route-policy route-policy-name { import | export }

    Specify a route-policy for the BGP-LS routes to be received from or advertised to a specified BGP peer or peer group.

    After a route-policy is created, you can run the peer route-policy command to use the route-policy to filter the BGP-LS routes to be received from or advertised to a specified BGP peer or peer group. The command configuration ensures that only desired routes are accepted or advertised, which helps manage routes and reduces the BGP-LS routing table size and system resource consumption.

  11. (Optional)Run peer { group-name | ipv4-address } route-update-interval interval

    Configure an interval at which the device sends Update messages carrying the same route prefix to a specified peer or peer group.

    When BGP-LS routes change, the switch sends Update messages to notify its peers. If a route changes frequently, to prevent the switch from sending Update messages for every change, you can run this command to set an interval at which the device sends Update messages carrying the same route prefix to a specified peer or peer group.

  12. (Optional)Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166601

Views: 272232

Downloads: 161

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next