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 the BGP4+ GR Helper

Configuring the BGP4+ GR Helper

A BGP4+ GR helper helps its neighbor complete BGP4+ GR.

Usage Scenario

BGP4+ restart causes re-establishment of peer relationships and traffic interruption.

BGP4+ GR needs to be enabled to prevent traffic interruption in the event of BGP4+ restart. A GR restarter and its BGP4+ peer negotiate the GR capability to establish a GR-capable BGP4+ session.

Pre-configuration Tasks

Before configuring BGP4+ GR helper, configure basic BGP4+ functions.

Configuration Procedures

Figure 11-5 Flowchart for configuring BGP4+ GR helper

Enabling BGP4+ GR

Enabling or disabling BGP4+ GR may delete and re-establish all BGP4+ sessions and instances.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run graceful-restart

    BGP4+ GR is enabled.

  4. Run commit

    The configuration is committed.

Configuring BGP4+ GR Session Parameters

Changing the BGP4+ restart period re-establishes BGP4+ peer relationships.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run graceful-restart timer wait-for-rib timer

    The period during which the restarting speaker and receiving speaker wait for End-Of-RIB messages is set.

    NOTE:

    You can adjust BGP4+ GR session parameter values as needed. However, retaining default BGP4+ GR session parameter values is recommended.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of BGP4+ GR Helper

After configuring BGP4+ GR helper, check the BGP4+ GR status.

Prerequisites

The BGP4+ GR helper has been configured.

Procedure

  • Run the display bgp ipv6 peer verbose command to check the BGP4+ GR status.

Example

Run the display bgp ipv6 peer verbose command to view the BGP4+ GR status.

<HUAWEI> display bgp ipv6 peer verbose

BGP Peer is 10:1::1,  remote AS 200
         Type: EBGP link
         BGP version 4, Remote router ID 4.4.4.4

  Group ID : 1
         BGP current state: Established, Up for 00h00m11s
         BGP current event: RecvUpdate
         BGP last state: Established
         BGP Peer Up count: 2
         Port: Local - 179        Remote - 36664
         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
        Graceful Restart Capability: advertised
         Address family IPv6 Unicast: advertised and received
 Received: Total 108 messages
                  Update messages                4
                  Open messages                  2
                  KeepAlive messages             102
                  Notification messages          0
                  Refresh messages               0
 Sent: Total 124 messages
                  Update messages                4
                  Open messages                  18
                  KeepAlive messages             101
                  Notification messages          1
                  Refresh messages               0
 Authentication type configured: None
 Last keepalive received: 2010-08-20 10:32:32
 Minimum route advertisement interval is 30 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Peer Preferred Value: 0
 Routing policy configured:
 No routing policy is configured
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20732

Downloads: 15

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