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 BGP4+ Connection Parameters

Configuring BGP4+ Connection Parameters

By configuring BGP4+ connection parameters, you can optimize BGP4+ network performance.

Usage Scenario

BGP4+ can use various timers to minimize the impact of interface flapping or route flapping.

  • Timers for BGP4+ Peers

    After establishing a BGP4+ connection, two peers periodically send Keepalive messages to each other to detect the status of the BGP4+ peer relationship. If the router does not receive any Keepalive message or any other type of packets from its peer within a time of period called holdtime period, it considers the BGP4+ connection closed.

    When establishing a BGP4+ connection, two peers compare their holdtime periods and use the shorter one. If the used holdtime period is 0, no Keepalive message will be transmitted and the hold timer status will not be detected.

    If the timeout period of the hold timer changes, the BGP4+ connection may be interrupted for a short period of time. This is because the peers need to renegotiate the holdtime period.

  • BGP4+ ConnectRetry Timer

    After BGP4+ initiates a TCP connection, the ConnectRetry timer will be stopped if the TCP connection is established successfully. If the first attempt to establish a TCP connection fails, BGP4+ re-establishes the TCP connection after the ConnectRetry timer expires.

    Setting a short ConnectRetry interval reduces the period BGP4+ waits between attempts to establish a TCP connection, which speeds up the establishment of the TCP connection.

    Setting a long connectRetry interval suppresses routing flapping caused by peer relationship flapping.

Pre-configuration Tasks

Before configuring BGP4+ connection parameters, configure basic BGP4+ functions.

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring Timers for BGP4+ Peers

Configuring timers properly improves network performance. Changing the timeout periods of timers, however, will interrupt peer relationships.

Context

Changing the timeout period of a timer using the peer timer command will interrupt peer relationships between routers. Therefore, exercise caution when changing the timeout period of a timer.

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 peer { ipv6-address | group-name } timer keepalive keepalive-time hold hold-time

    The timeout periods of the holdtime timer and Keepalive timer are set on a peer or peer group.

    The value of hold-time must be at least three times that of keepalive-time.
    NOTE:

    Setting the Keepalive time to 20s is recommended. If the Keepalive time is smaller than 20s, sessions between peers may be closed.

    When setting the values of keepalive-time and hold-time, note the following points:

    • The values of keepalive-time and hold-time cannot both be set to 0. Otherwise, the BGP timers become invalid, and BGP4+ cannot detect link faults based on the timers.

    • The value of hold-time such as timer keepalive 1 hold 65535 is much greater than that of keepalive-time. If the value of hold-time is too large, BGP4+ cannot detect link faults rapidly.

  4. Run commit

    The configuration is committed.

Enabling Fast Reset of EBGP Connections

With fast reset of EBGP connections, BGP4+ rapidly detects EBGP link faults and resets EBGP connections on related interfaces.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run ebgp-interface-sensitive

    Fast reset of EBGP connections is enabled.

    After this function is enabled, BGP4+ rapidly detects EBGP link faults and resets EBGP connections on related interfaces.

    If an interface on which a BGP4+ connection is established alternates between Up and Down, run the undo ebgp-interface-sensitive command to prevent repeated re-establishment and deletion of the BGP4+ session in the case of route flapping. This saves network bandwidth.

  4. Run commit

    The configuration is committed.

Configuring a BGP4+ ConnectRetry Timer

You can control the speed at which BGP4+ peer relationships are established by changing the BGP4+ ConnectRetry timer value.

Context

After BGP4+ initiates a TCP connection, the ConnectRetry timer will be stopped if the TCP connection is established successfully. If the first attempt to establish a TCP connection fails, BGP4+ re-establishes the TCP connection after the ConnectRetry timer expires.
  • Setting a short ConnectRetry interval reduces the period BGP4+ waits between attempts to establish a TCP connection, which speeds up the establishment of the TCP connection.
  • Setting a long connectRetry interval suppresses routing flapping caused by peer relationship flapping.

A ConnectRetry timer can be configured either for all peers or peer groups, or for a specific peer or peer group. A ConnectRetry timer configured for a specific peer takes precedence over that configured for the peer group of this peer. In addition, a ConnectRetry timer configured for a specific peer or peer group takes precedence over that configured for all peers or peer groups.

Procedure

  • Configure a BGP4+ ConnectRetry timer for all peers or peer groups.

    Perform the following steps on a BGP4+ router:

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run timer connect-retry connect-retry-time

      A BGP4+ ConnectRetry timer is configured for all peers or peer groups.

    4. Run commit

      The configuration is committed.

  • Configure a ConnectRetry timer for a specific peer or peer group.

    Perform the following steps on a BGP4+ router:

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run peer { group-name | ipv6-address } timer connect-retry connect-retry-time

      A ConnectRetry timer is configured for a specific peer or peer group.

      The ConnectRetry timer configured for a peer or peer group takes precedence over that configured for all peers or peer groups.

    4. Run commit

      The configuration is committed.

Verifying the Configuration of BGP4+ Connection Parameters

After configuring BGP4+ connection parameters, check information about BGP4+ peers or peer groups.

Prerequisites

BGP4+ connection parameters have been configured.

Procedure

  • Run the display bgp ipv6 peer [ verbose ] command to check information about BGP4+ peers.

Example

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

<HUAWEI> display bgp ipv6 peer verbose
         BGP Peer is 2001:db8:10::1,  remote AS 10
         Type: EBGP link
         BGP version 4, Remote router ID 2.2.2.2

  Group ID : 1
         BGP current state: Established, Up for 00h00m17s
         BGP current event: RecvUpdate
         BGP last state: Established
         BGP Peer Up count: 1
         Port: Local - 3363        Remote - 179
         Configured: Active Hold Time: 180 sec   Keepalive Time:60 sec
         Received  : Active Hold Time: 180 sec
         Negotiated: Active Hold Time: 180 sec   Keepalive Time:60 sec
         Peer optional capabilities:
         Peer supports bgp multi-protocol extension
         Peer supports bgp route refresh capability
         Peer supports bgp 4-byte-as capability
         Address family IPv6 Unicast: advertised and received
 Received: Total 3 messages
                  Update messages                1
                  Open messages                  1
                  KeepAlive messages             1
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 3 messages
                  Update messages                1
                  Open messages                  1
                  KeepAlive messages             1
                  Notification messages          0
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received:2011-02-28 03:21:18
 Minimum route advertisement interval is 30 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Multi-hop ebgp has been enabled
 Peer Preferred Value: 0
 Routing policy configured:
 No routing policy is configured
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 55743

Downloads: 211

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