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).
Configuring BGP Route Attributes

Configuring BGP Route Attributes

Configuring route attributes can change route selection results.

Usage Scenario

BGP has many route attributes. You can change route selection results by configuring attributes for routes.

  • BGP priority

    Setting the BGP priority can control route selection between BGP routes and routes of other routing protocols.

  • Preferred values

    After preferred values are set for BGP routes, the route with the greatest value is preferred when multiple routes to the same destination exist in the BGP routing table.

  • Local_Pref

    The Local_Pref attribute has the same function as the preferred value of a route. If both of them are configured for a BGP route, the preferred value takes precedence over the Local_Pref attribute.

  • MED

    The MED attribute is used to determine the optimal route for traffic that enters an AS. The route with the smallest MED value is selected as the optimal route if the other attributes of the routes are the same.

  • Next_Hop

    BGP route selection can be controlled by changing Next_Hop attributes for routes.

  • AS_Path

    The AS_Path attribute is used to prevent rooting loops and control route selection.

  • AIGP

    BGP prefers the route with the smallest AIGP value during BGP route selection.

Pre-configuration Tasks

Before configuring BGP route attributes, configure basic BGP functions.

Configuration Procedures

Perform one or more of the following configurations as required.

Setting the BGP Priority

Setting the BGP priority can control route selection between BGP routes and routes of another routing protocol.

Context

Multiple dynamic routing protocols can be run on a device. In this case, there is a problem of route sharing and selecting among routing protocols. To address this problem, the system sets a default priority for each routing protocol. If different protocols have routes to the same destination, the protocol with the highest priority is selected to forward IP packets.

Procedure

  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 preference { external internal local | route-policy route-policy-name | route-filter route-filter-name }

    The BGP preference is set.

    The smaller the value, the higher the priority.

    BGP has the following types of routes:

    • Routes learned from external peers (EBGP)

    • Routes learned from internal peers (IBGP)

    • Routes generated locally using the summary automatic or aggregate command.

    You can set different priorities for the three types of routes.

    You can also apply routing policies to set preferences for the specified routes that meet the requirements. You can set default preferences for the routes that do not meet the requirements.

    NOTE:

    Currently, you cannot run the peer route-policy or peer route-filter command to apply routing policies to set the priority for BGP.

  5. Run commit

    The configuration is committed.

Setting the Preferred Values for BGP Routes

After the preferred values are set for BGP routes, the route with the largest preferred value is preferred when multiple routes to the same destination exist in the BGP routing table.

Procedure

  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 peer { group-name | ipv4-address } preferred-value value

    The preferred values of all the routes learned from a specified peer are set.

    After the peer preferred-value command is run, all the routes learned from a peer have the same preferred value.

  5. Run commit

    The configuration is committed.

Setting the Default Local_Pref Attribute for the Local Device

The function of the Local_Pref attribute is similar to that of the preferred value. The priority of the Local_Pref attribute, however, is lower than that of the preferred value.

Context

The Local_Pref attribute is used to determine the optimal route for the traffic that leaves an AS. When a BGP device obtains multiple routes to the same destination address but with different next hops from different IBGP peers, the BGP device prefers route with the largest Local_Pref.

Procedure

  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 default local-preference local-preference

    The default Local_Pref attribute is set for the local device.

  5. Run commit

    The configuration is committed.

Configuring MED Attributes for BGP Routes

The MED attribute equals the metric used by an IGP. After the MED attributes of routes are set, an EBGP peer selects the route with the smallest MED value for the traffic that enters an AS if the other attributes of the routes are the same.

Context

If a BGP device obtains multiple routes from different EBGP peers and these routes have different next hops but the same destination, the BGP device selects the route with the smallest MED value.

Procedure

  • Set the default MED value on a device.
    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 default med med

      The default MED value is set.

      NOTE:

      The default med command is valid only for routes imported using the import-route command and BGP summarized routes on the local device.

    5. Run commit

      The configuration is committed.

  • Compare the MED values of the routes from different ASs.
    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 compare-different-as-med

      The MED values of routes from different ASs are compared.

      By default, the BGP device compares the MED values of only routes from different peers in the same AS.

    5. Run commit

      The configuration is committed.

  • Configure the deterministic-MED function.
    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 deterministic-med

      The deterministic-MED function is enabled.

      If the deterministic-MED function is not enabled and the device receives multiple routes with the same prefix from different ASs, the sequence in which routes are received determines the route selection. After the deterministic-MED function is enabled, these routes are first grouped based on the leftmost AS number in the AS_Path attribute. Routes with the same leftmost AS number are grouped together and compared, and an optimal route is selected in the group. The optimal route in this group is then compared with the optimal routes from other groups to determine the final optimal route. With the deterministic-MED function, the route selection result is independent of the sequence in which routes are received.

    5. Run commit

      The configuration is committed.

  • Configure the maximum MED value (4294967295) as the MED during route selection when a route carries no MED.
    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 bestroute med-none-as-maximum

      The maximum MED value is used as the MED when a route carries no MED.

      If the bestroute med-none-as-maximum command is not run and a route carries no MED, 0 is used as the MED value of the route.

    5. Run commit

      The configuration is committed.

  • Compare the MED values of routes in a confederation.
    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 bestroute med-confederation

      The MED values of routes in a confederation are compared.

    5. Run commit

      The configuration is committed.

  • Compare the sums of MED multiplied by a MED multiplier and IGP cost multiplied by an IGP cost multiplier.
    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 bestroute med-plus-igp [ igp-multiplier igp-multiplier | med-multiplier med-multiplier ]

      The sums of MED multiplied by a MED multiplier and IGP cost multiplied by an IGP cost multiplier are compared.

    5. Run commit

      The configuration is committed.

  • Enable BGP to remove the MED attribute from the imported routes that are locally crossed and are to be advertised to a specified peer after an export policy for which the apply cost-type command is run is applied to the peer.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run local-cross-routing non-med

      BGP is enabled to remove the MED attribute from the imported routes that are locally crossed and are to be advertised to a specified peer after an export policy for which the apply cost-type command is run is applied to the peer.

      Run the local-cross-routing non-med command to removes the MED attribute from the imported routes that are locally crossed and are to be advertised to a specified peer after an export policy for which the apply cost-type command is run is applied to the peer.

    4. Run commit

      The configuration is committed.

Setting Next_Hop Attributes for Routes

Setting Next_Hop attributes for routes controls BGP route selection.

Procedure

  • Configure a device to change the next hop address of a route when the device advertises the route to an IBGP peer.

    By default, a device does not change the next hop address of a route learned from an EBGP peer before forwarding the route to IBGP peers. The next hop address of a route advertised by an EBGP peer to this device is the address of the EBGP peer. After being forwarded to IBGP peers, this route is not active because the next hop is unreachable. The relevant ASBR must be configured to change the next hop address of the route to the ASBR's own IP address before the ASBR advertises the route to an IBGP peer. The route is active on the IBGP peer if the next hop is reachable.

    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 { ipv4-address | group-name } next-hop-local

      The device is configured to change the next hop address of a route to the device's own IP address before the device advertises the route to an IBGP peer.

      NOTE:

      If BGP load balancing is configured, the local router changes the next hop address of a route to its own IP address when advertising the route to IBGP peers or peer groups, regardless of whether the peer next-hop-local command is used.

    5. Run commit

      The configuration is committed.

  • Prevent a device from changing the next hop address of a route imported from an IGP when the device advertises the route to an IBGP peer.
    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 { ipv4-address | group-name } next-hop-invariable

      The device is prevented from changing the next hop address of a route imported from an IGP before advertising the route to an IBGP peer.

    5. Run commit

      The configuration is committed.

  • Prevent an ASBR from changing the next hop address of a route when the ASBR advertises the route to an EBGP peer.
    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 vpnv4 [ unicast ]

      The BGP-VPNv4 sub-address family view is displayed.

    4. Run peer { group-name | ipv4-address } next-hop-invariable

      The device is prevented from changing the next hop address of a route when advertising the route to an EBGP peer.

      In the inter-AS VPN option C networking where RRs are used, the peer next-hop-invariable command needs to be run to prevent the RRs from changing the next hop address of a route when the RRs advertise the route to EBGP peers. This ensures that the remote PE iterates a route to the BGP LSP destined for the local PE during traffic transmission.

    5. Run commit

      The configuration is committed.

  • Configure route-policy-based next hop iteration.
    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 nexthop recursive-lookup { route-policy route-policy-name | route-filter route-filter-name }

      Route-policy-based next hop iteration is configured.

      Next-hop iteration based on a specified route-policy can control the iterated next hop based on specific conditions. If a route fails to match the specified route-policy, the route cannot be iterated.

    5. Run commit

      The configuration is committed.

Setting the AS_Path Attribute

The AS_Path attribute is used to prevent routing loops and control route selection.

Procedure

  • Allow repeated local AS numbers.

    Multiple dynamic routing protocols can be run on a device at the same time. In this case, there is a problem of route sharing and selecting among routing protocols. To address this problem, the system sets a default priority for each routing protocol. If different protocols have routes to the same destination, the protocol with the highest preference is selected to forward IP packets.

    Perform the following steps on a device running BGP.

    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 peer { ipv4-address | group-name } allow-as-loop [ number ]

      Repeated local AS numbers are allowed.

      In most cases, a BGP router checks the AS_Path attribute of a route received from a peer. If the local AS number is carried by the route, the BGP router discards this route to avoid routing loops.

      In some special applications, you can use the peer { ipv4-address | group-name } allow-as-loop [ number ] command to allow the AS_Path attribute of a route received from a peer to contain the local AS number. You can also set the allowed number of repeated local AS numbers.

    5. Run commit

      The configuration is committed.

  • Prevent the local device from using the AS_Path attribute as a route selection rule.
    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 bestroute as-path-ignore

      The local device is prevented from using the AS_Path attribute as a route selection rule.

    5. Run commit

      The configuration is committed.

  • Configure a fake AS number.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run peer { ipv4-address | group-name } fake-as fake-as-number [ dual-as ] [ prepend-global-as ] [ prepend-fake-as ]

      A fake AS number is configured.

      This command is used to hide the actual AS number. EBGP peers in other ASs can learn only this fake AS number. The peers in other ASs use the fake AS number as the AS number of the local peer.

      NOTE:

      The peer fake-as command is applicable only to EBGP peers.

    4. Run commit

      The configuration is committed.

  • Substitute the AS number in the AS-Path attribute.

    If the AS_Path attribute of a route to be advertised to a peer contains the number of the AS where the peer resides, the local router substitutes the AS number of the peer with the local AS number before advertising the route. On a BGP network, two devices have the same AS number and the same EBGP peer. After one of the two devices learns a route of the other device from the EBGP peer, the route is discarded because it carries an AS number that is the same as the local one. To address this problem, run the peer substitute-as command on the EBGP peer.

    Configuring the peer substitute-as command may cause a routing loop. Therefore, exercise caution when running this command.

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run ipv4-family { vpn-instance vpn-instance-name | unicast }

      The BGP-VPN instance IPv4 address family view or BGP-IPv4 unicast address family view is displayed.

    4. Run peer { ipv4-address | group-name } substitute-as

      The AS number in the AS_Path attribute of a route is substituted with the local AS number.

    5. Run commit

      The configuration is committed.

  • Configure the AS_Path attribute to carry only the public AS number.
    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 peer { ipv4-address | group-name } public-as-only [ force [ replace ] [ include-peer-as ] | limited [ replace ] [ include-peer-as ] ]

      The AS_Path attribute is configured to carry only the public AS number.

      In most cases, the AS number ranges from 1 to 4294967295. The public AS number ranges from 1 to 64511, and from 65536 (1.0 in the format of x.y) to 4294967295 (65535.65535 in the format of x.y), and the private AS number ranges from 64512 to 65534. 65535 is a reserved AS number.
      NOTE:

      If the 4-byte private AS number function is enabled using the private-4-byte-as enable command, private AS numbers range from 64512 to 65534 and from 4200000000 to 4294967294 (64086.59904 to 65535.65534 in the format of x.y).

      The public AS number can be used on the Internet, because Internet addresses are managed and assigned by the Internet Assigned Number Authority (IANA). The private AS number cannot be advertised to the Internet and is used only in an internal routing domain.

      In most cases, the route advertised by a BGP router to its peer carries an AS number (either public or private AS number). If you do not want to transmit the private AS number, run the command so that the AS_Path attribute carries only the public AS number.

    5. Run commit

      The configuration is committed.

  • Set the maximum number of AS numbers in the AS-Path attribute.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run as-path-limit as-path-limit-num

      The maximum number of AS numbers in the AS-Path attribute is set.

      By default, the maximum number of AS numbers in the AS_Path attribute is 255.

      After the as-path-limit command is run, a router checks whether the number of AS numbers in the AS-Path attribute of a received route exceeds the maximum value. If the number of AS numbers exceeds the maximum value, the router discards the route. Therefore, if the maximum number of AS numbers in the AS-Path attribute is set too small, routes may be discarded.

    4. Run commit

      The configuration is committed.

  • Prevent a BGP device from checking the first AS number contained in the AS_Path attribute of an Update message received from an EBGP peer.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run undo check-first-as

      The BGP device is prevented from checking the first AS number contained in the AS_Path attribute of an Update message received from an EBGP peer.

      By default, a BGP device checks whether the first AS number contained in the AS_Path attribute of an Update message received from an EBGP peer is the same as the number of the AS where the EBGP peer resides. If the numbers are not the same, the BGP device discards the Update message and terminates the EBGP connection with the EBGP peer.

      Exercise caution when running the undo check-first-as command because use of this command may cause routing loops.

    4. Run commit

      The configuration is committed.

      After the configuration is complete, run the refresh bgp command to check the received routes again.

  • Enable the device to check or disable the device from checking the first AS number in the AS_Path attribute contained in the update messages received from a specified EBGP peer or peer group.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run peer { group-name | ipv4-address } check-first-as { enable | disable }

      The device is enabled to check or disabled from checking the first AS number in the AS_Path attribute contained in the update messages received from a specified EBGP peer or peer group.

      If the peer check-first-as enable command is run, the device checks whether the first AS number in the AS_Path attribute contained in the update messages received from the specified EBGP peer or peer group is the number of the AS where the EBGP peer or peer group resides. If the two AS numbers are different, the local device discards the update messages and disconnects the EBGP connection. If the peer check-first-as disable command is run, the device accepts all update messages received from the specified EBGP peer or peer group, regardless whether the two AS numbers are the same. If the undo peer check-first-as disable command is run, the default configuration takes effect.

      The check function can be configured for a specified EBGP peer, peer group, or for BGP as a whole. If the function is not configured for a specified EBGP peer, the device checks whether the function is configured for the related peer group; if the function is not configured for the peer group, the device checks whether the function is configured in the BGP view.

    4. Run commit

      The configuration is committed.

      After the configuration is complete, run the refresh bgp command to check the received routes again.

Configuring AIGP Attributes for Routes

The Accumulated Interior Gateway Protocol Metric (AIGP) attribute allows devices in an AIGP administrative domain to use the optimal routes to forward data.

Context

An AIGP administrative domain is a set of autonomous systems (ASs) in a common administrative domain.

Routing protocols that have been designed to run within a single administrative domain, such as various IGPs, generally assign a metric to each link, and then choose the path for which the total distance (sum of the metric of each link along the path) is minimized as the optimal path between two nodes. BGP, designed to provide routing over a large number of independent administrative domains, does not select paths based on metrics. If a single administrative domain runs several contiguous BGP networks, it is desirable for BGP to select paths based on metrics, just as an IGP does.

The AIGP attribute enables BGP to select routes based on metrics in an AIGP administrative domain. As a result, all devices in the AIGP administrative domain can use the optimal routes to forward data.

Procedure

  1. Enable AIGP capability for a BGP peer or peer group.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run the ipv4-family unicast command to enter the BGP-IPv4 unicast address family view, or run the ipv4-family labeled-unicast command to enter the BGP-labeled address family view, or run the ipv4-family vpnv4 command to enter the BGP-VPNv4 address family view.
    4. Run peer { group-name | ipv4-address | ipv6-address } aigp

      The AIGP capability is enabled for a BGP peer or peer group.

      BGP allows you to enable the AIGP capability for either a BGP peer or a BGP peer group. If a BGP peer with the AIGP capability joins a BGP peer group that does not have the AIGP capability, the BGP peer still retains the AIGP capability. If a BGP peer without the AIGP capability joins a BGP peer group that has the AIGP capability, the BGP peer inherits the AIGP capability of the BGP peer group. After a BGP peer inherits the AIGP capability of a BGP peer group, you can run the undo peer aigp command to delete the AIGP configuration from the BGP peer.

    5. Run commit

      The configuration is committed.

  2. (Optional) Allow VPN routes to participate in route selection using the AIGP attribute of the BGP LSP through which they are transmitted.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run the ipv4-family vpn-instance vpn-instance-name command to enter the BGP-VPN instance IPv4 address family view.
    4. Run bestroute nexthop-resolved aigp

      VPN routes are allowed to participate in route selection using the AIGP attribute of the BGP LSP through which they are transmitted.

    5. Run commit

      The configuration is committed.

Configuring Attr_Set Attribute Encapsulation or Parsing

Configuring Attr_Set attribute encapsulation or parsing ensures that the attributes of the routes sent by CEs are transparently transmitted over the backbone network.

Context

On BGP MPLS/VPN networks, EBGP peer relationships are established between PEs and CEs in most cases. Attributes of the routes advertised by CEs are modified during transmission over the intermediate backbone network, or the attributes affect the backbone network. In this case, BGP has been extended to allow the intermediate backbone network to transparently transmit the routes advertised by CEs. After receiving a route from a CE, the local PE encapsulates the attributes of the route in the Attr_Set attribute and then sends the route to the remote PE. Upon receipt of the route, the remote PE parses the Attr_Set attribute. This process ensures that the route attributes are transparently transmitted over the backbone network.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run the ipv4-family vpn-instance vpn-instance-name command to enter the BGP-VPN instance IPv4 address family view or run the ipv6-family vpn-instance vpn-instance-name command to enter the BGP-VPN instance IPv6 address family view.
  4. Run attr-set { both | send | receive }

    The device is configured to encapsulate the Attr_Set attribute when sending VPN routes, parse the Attr_Set attribute when receiving VPN routes, or encapsulate the Attr_Set attribute when sending VPN routes and parse the Attr_Set attribute when receiving VPN routes.

  5. Run commit

    The configuration is committed.

Verifying the BGP Route Attribute Configuration

After configuring BGP route selection, verify information about route attributes.

Prerequisites

BGP route attributes have been configured.

Procedure

  • Run the display bgp routing-table different-origin-as command to check routes with different source ASs but the same destination address.
  • Run the display bgp routing-table regular-expression as-regular-expression command to check routes matching the AS regular expression.
  • Run the display bgp routing-table [ network ] [ mask | mask-length ] [ longer-prefixes ] command to check information about the BGP routing table.
  • Run the display bgp routing-table community [ community-number | aa:nn ] &<1-13> [ internet | no-advertise | no-export | no-export-subconfed ] * [ whole-match ] command to check routes matching a specified BGP community attribute.
  • Run the display bgp routing-table community-filter { { community-filter-name | basic-community-filter-number } [ whole-match ] | advanced-community-filter-number } command to check the routes matching a specified BGP community filter.

Example

# Run the display bgp routing-table regular-expression as-regular-expression command to check routes matching the AS regular expression. For example:

<HUAWEI> display bgp routing-table regular-expression ^1
 BGP Local router ID is 1.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
 RPKI validation codes: V - valid, I - invalid, N - not-found

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

 *    1.1.1.0/24         1.1.1.1         0                     0      100?
 *    1.1.1.2/32         1.1.1.1         0                     0      100?
 *>   5.1.1.0/24         1.1.1.1         0                     0      100?
 *>   100.1.1.0/24       1.1.1.1         0                     0      100?

# Run the display bgp routing-table [ network ] [ mask | mask-length ] [ longer-prefixes ] command to check information about the BGP routing table. For example:

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

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

 *    1.1.1.0/24         1.1.1.1         0                     0      100?
 *    1.1.1.2/32         1.1.1.1         0                     0      100?
 *>   5.1.1.0/24         1.1.1.1         0                     0      100?
 *>   100.1.1.0/24       1.1.1.1         0                     0      100?

# Run the display bgp routing-table community [ community-number | aa:nn ] &<1-13> [ internet | no-advertise | no-export | no-export-subconfed ] * [ whole-match ] command to check routes matching a specified BGP community attribute. For example:

<HUAWEI> display bgp routing-table community
 BGP Local router ID is 1.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
 RPKI validation codes: V - valid, I - invalid, N - not-found

 Total Number of Routes: 4
      Network            NextHop        MED        LocPrf    PrefVal Community

 *    1.1.1.0/24         1.1.1.1         0                     0      no-export
 *    1.1.1.2/32         1.1.1.1         0                     0      no-export
 *>   5.1.1.0/24         1.1.1.1         0                     0      no-export
 *>   100.1.1.0/24       1.1.1.1         0                     0      no-export
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 49946

Downloads: 205

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