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-LS

Configuring BGP-LS

BGP-LS provides a simple and efficient method of collecting topology information.

Usage Scenario

Without BGP-LS, the ME device uses an IGP (OSPF or IS-IS) to collect topology information of each AS, and the IGP reports the information to the controller. This topology information collection method has the following disadvantages:
  • The controller must have high computing capabilities and support the IGP and its algorithm.
  • The controller cannot gain the complete inter-AS topology information and therefore is unable to calculate optimal E2E paths.
  • Different IGPs report topology information separately to the controller, which complicates the controller's analysis and processing.
With powerful routing capabilities of BGP, BGP-LS has the following advantages:
  • Reduces computing capability requirements and spares the necessity of IGPs on the controller.
  • Facilitates route selection and calculation on the controller by using BGP to summarize process or AS topology information and report the complete information to the controller.
  • Requires only one routing protocol (BGP) to report topology information to the controller.

BGP-LS needs to be deployed on the controller and the devices connected to it.

Pre-configuration Tasks

Before configuring BGP-LS, configure basic IPv4 IS-IS functions or basic OSPF functions.

Procedure

  1. Enable IGP topology advertisement to BGP. You can determine to enable IS-IS topology advertisement to BGP, OSPF topology advertisement to BGP, or both based on network configurations.
    • Enable IS-IS topology advertisement to BGP.
      1. Run the system-view command to enter the system view.
      2. Run the isis [ process-id ] command to configure an IS-IS process.
      3. Run the bgp-ls enable [ level-1 | level-2 | level-1–2 ] command to enable IS-IS topology advertisement to BGP.
      4. (Optional) Run the bgp-ls identifier identifier command to configure a BGP-LS identifier.
      5. Run the commit command to commit the configuration.
    • Enable OSPF topology advertisement to BGP.
      1. Run the system-view command to enter the system view.
      2. Run the ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * command to configure an OSPF process.
      3. Run the bgp-ls enable command to enable OSPF topology advertisement to BGP.
      4. (Optional) Run the bgp-ls identifier identifier-value command to configure a BGP-LS identifier.
      5. Run the commit command to commit the configuration.
  2. Enable BGP-LS.

    1. Run the system-view command to enter the system view.
    2. Run the bgp { as-number-plain | as-number-dot } command to enable BGP and enter the BGP view.
    3. Run the peer { group-name | ipv4-address } as-number { as-number-plain | as-number-dot } command to specify the IP address and AS number of a BGP peer.

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

    4. Run the link-state-family unicast command to enable BGP-LS and enter the BGP-LS address family view.
    5. Run the peer { group-name | ipv4-address } enable command to enable BGP-LS route exchange with the specified peer or peer group.
    6. (Optional) Run the domain identifier domain-id command to 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 the domain as { domain as-plain | domain as-dot } command to configure a 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 the peer { group-name | ipv4-address } reflect-client command to 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 through the RR 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 the peer { group-name | ipv4-address } route-limit limit [ percentage ] [ alert-only | idle-forever | idle-timeout minutes ] command to set the maximum number of BGP-LS routes that can be received from a specified peer.

      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 the peer { group-name | ipv4-address } route-policy route-policy-name { import | export } command to 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 the peer { group-name | ipv4-address } route-update-interval interval command to 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 ME device sends Update messages to notify its peers. If a route changes frequently, to prevent the ME device 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. Run the commit command to commit the configuration.

Checking the Configurations

After configuring BGP-LS, check the configurations:

  • Run the display bgp link-state unicast peer command to check information about BGP-LS peers and their status.
  • Run the display bgp link-state unicast routing-table command to check BGP-LS route information.
  • Run the display bgp link-state unicast routing-table statistics command to check BGP-LS route statistics.

# Run the display bgp link-state unicast peer [ [ ipv4-address ] verbose ] command to view information about BGP-LS peers and their status.

<HUAWEI> display bgp link-state unicast peer

 BGP local router ID : 192.168.102.3
 Local AS number : 100
 Total number of peers : 1                 Peers in established state : 1

  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State  PrefRcv
  192.168.102.4   4         100       52       55     0 00:39:10 Established        4

# Run the display bgp link-state unicast routing-table [ peer ipv4-address received-routes ] [ type { node | link | ipv4-prefix | ipv6-prefix } | bgp-ls-prefix ] command to view BGP-LS route information.

<HUAWEI> display bgp link-state unicast routing-table
 BGP Local router ID is 11.1.1.2
 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


 Total Number of Node Routes: 5
 *>     Network  : [NODE][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.00]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [NODE][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.01]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [NODE][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.00]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [NODE][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.01]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [NODE][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0003.00]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?

 Total Number of Link Routes: 8
 *>     Network  : [LINK][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.00]][REMOTE[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.01]][LINK[if-address0.0.0.0][peer-address0.0.0.0][if-address::][peer-address::][mt-id0]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [LINK][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.01]][REMOTE[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.00]][LINK[if-address0.0.0.0][peer-address0.0.0.0][if-address::][peer-address::][mt-id0]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [LINK][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.01]][REMOTE[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0003.00]][LINK[if-address0.0.0.0][peer-address0.0.0.0][if-address::][peer-address::][mt-id0]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [LINK][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.00]][REMOTE[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.01]][LINK[if-address0.0.0.0][peer-address0.0.0.0][if-address::][peer-address::][mt-id0]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [LINK][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.01]][REMOTE[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.00]][LINK[if-address0.0.0.0][peer-address0.0.0.0][if-address::][peer-address::][mt-id0]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [LINK][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.01]][REMOTE[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0003.00]][LINK[if-address0.0.0.0][peer-address0.0.0.0][if-address::][peer-address::][mt-id0]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [LINK][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0003.00]][REMOTE[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.01]][LINK[if-address0.0.0.0][peer-address0.0.0.0][if-address::][peer-address::][mt-id0]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [LINK][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0003.00]][REMOTE[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.01]][LINK[if-address0.0.0.0][peer-address0.0.0.0][if-address::][peer-address::][mt-id0]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?

 Total Number of IPv4 Prefix Routes: 5
 *>     Network  : [IPV4-PREFIX][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0001.00]][PREFIX[mt-id0][ospf-route-type0][prefix11.1.1.0/24]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [IPV4-PREFIX][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0002.00]][PREFIX[mt-id0][ospf-route-type0][prefix11.1.2.0/24]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [IPV4-PREFIX][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0003.00]][PREFIX[mt-id0][ospf-route-type0][prefix11.1.1.0/24]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [IPV4-PREFIX][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0003.00]][PREFIX[mt-id0][ospf-route-type0][prefix11.1.2.0/24]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?
 *>     Network  : [IPV4-PREFIX][ISIS-LEVEL-1][IDENTIFIER0][LOCAL[as100][bgp-ls-identifier11.1.1.2][ospf-area-id0.0.0.0][igp-router-id0000.0000.0003.00]][PREFIX[mt-id0][ospf-route-type0][prefix192.158.0.0/24]]
        NextHop  : 0.0.0.0                                  LocPrf    :
        MED      : 0                                        PrefVal   : 0
        Path/Ogn :  ?

# Run the display bgp link-state unicast routing-table statistics [ peer ipv4-address received-routes ] [ type { node | link | ipv4-prefix | ipv6-prefix } ] statistics command to view BGP-LS route statistics.

<HUAWEI> display bgp link-state unicast routing-table statistics
 Total Number of Node Routes: 1
 Total Number of Link Routes: 2
 Total Number of IPv4 Prefix Routes: 3
 Total Number of IPv6 Prefix Routes: 4
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20923

Downloads: 15

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