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 Basic BGP4+ Functions

Configuring Basic BGP4+ Functions

Basic BGP4+ functions must be configured before you configure subsequent BGP4 functions on a BGP4+ network.

Usage Scenario

Basic BGP4+ functions must be configured first when you configure BGP4+ for inter-AS communication.

Pre-configuration Tasks

Before configuring basic BGP4+ functions, configure link layer protocol parameters and IP addresses for interfaces to ensure that the link layer protocol on the interfaces is Up.

Configuration Procedures

Figure 11-2 Flowchart for configuring basic BGP4+ functions

Starting a BGP4+ Process

A BGP process must be started before configuring BGP4+ functions. When starting a BGP4+ process, specify the number of the AS to which the device belongs.

Context

Changing router IDs on BGP4+ peers will cause the reestablishment of the BGP4+ connection between ME devices.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    BGP4+ is enabled (the local AS number is specified), and the BGP4+ view is displayed.

  3. (Optional) Run router-id ipv4-address

    The router ID is set.

    NOTE:

    If the router ID of the ME device is the IP address of a physical interface, the change in the IP address will cause route flapping on the network. To enhance network stability, configuring the address of a loopback interface as the router ID is recommended.

  4. (Optional) Run shutdown

    All sessions between the device and its BGP peers are terminated.

    During the system upgrade, or maintenance, you can run the shutdown command to terminate all sessions between a device and its BGP peers to prevent possible BGP route flapping from affecting the network.

    After the upgrade or maintenance, run the undo shutdown command to restore the BGP peer sessions; otherwise, BGP functions will be affected.

  5. Run commit

    The configuration is committed.

Configuring IPv6 Peers

Devices can exchange BGP4+ routing information only after the IPv6 peer relationship is established among them.

Context

Because BGP4+ uses TCP connections, the IPv6 addresses for peers must be specified when you configure BGP4+. A BGP4+ peer may not be a neighboring ME device, and a BGP4+ peer relationship can be created by using a logical link. Using the addresses of loopback interfaces to set up BGP4+ peer relationships can improve the stability of BGP4+ connections and is recommended.

The devices in the same AS establish IBGP peer relationships, and the devices of different ASs establish EBGP peer relationships.

Procedure

  • Configure IBGP peers.

    Perform the following steps on the ME devices between which an IBGP peer relationship needs to be set up:

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run peer ipv6-address as-number as-number

      The address of the remote peer and the AS to which the remote peer belongs are configured.

      The number of the AS where the specified peer resides must be the same as that of the local AS.

      The IP address of the specified peer can be one of the following types:

      • IPv6 address of an interface on a directly connected peer

      • IP address of a loopback interface on a reachable peer

      • IPv6 address of a sub-interface on a directly connected peer

      • Link-local address of an interface on a directly connected peer

      If the IPv6 address used to set up a BGP4+ peer relationship is a loopback interface address, follow the procedure described in Configuring the Local Interface for the BGP4+ Connection.

    4. (Optional) Run peer { ipv6-address | group-name } listen-only

      The local peer (group) is configured to accept connection requests, but not to send connection requests.

      After this command is run, the existing peer relationship is interrupted. The local peer will wait for a connection request from the remote peer to reestablish a peer relationship. This command enables only one peer to send connection requests, preventing a connection request conflict.

      NOTE:

      This command can only be run on one of two peers. If this command is run on both peers, the connection between them cannot be reestablished.

    5. Run ipv6-family unicast

      The IPv6 unicast address family view is displayed.

    6. Run peer ipv6-address enable

      The IPv6 peer is enabled.

      After configuring a BGP4+ peer in the BGP view, enable the peer in the IPv6 unicast address family view.

    7. Run commit

      The configuration is committed.

  • Configure EBGP peers.

    Perform the following steps on the ME devices between which an EBGP peer relationship needs to be set up:

    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run peer ipv6-address as-number as-number

      The IPv6 address of the remote peer and the AS to which the remote peer belongs are configured.

      The number of the AS where the specified peer resides must be different from that of the local AS.

      The IP address of the specified peer can be one of the following types:

      • IPv6 address of an interface on a directly connected peer

      • IP address of a loopback interface on a reachable peer

      • IPv6 address of a sub-interface on a directly connected peer

      • Link-local address of an interface on a directly connected peer

      If the IP address used to set up a BGP4+ peer relationship is a loopback interface address, or a local-link address, follow the procedure described in Configuring the Local Interface for the BGP4+ Connection.

    4. Run peer { ipv6-address | group-name } ebgp-max-hop [ hop-count ]

      The maximum number of hops is configured for establishing an EBGP connection.

      A direct physical link must be available between EBGP peers. If such a link does not exist, the peer ebgp-max-hop command must be used to allow EBGP peers to establish a TCP connection over multiple hops.

      NOTE:

      If loopback interfaces are used to establish an EBGP peer relationship, the peer ebgp-max-hop command must be run with hop-count greater than or equal to 2; otherwise, the peer relationship cannot be established.

    5. (Optional) Run peer { ipv6-address | group-name } listen-only

      The local peer (group) is configured to accept connection requests, but not to send connection requests.

      After this command is run, the existing peer relationship is interrupted. The local peer will wait for the connection request from the remote peer to reestablish a peer relationship. This command enables only one peer to send connection requests, preventing a connection request conflict.

      NOTE:

      This command can only be run on one of two peers. If this command is run on both peers, the connection between them cannot be reestablished.

    6. Run ipv6-family unicast

      The IPv6 unicast address family view is displayed.

    7. Run peer ipv6-address enable

      The IPv6 peer is enabled.

      After configuring a BGP4+ peer in the BGP view, enable the peer in the IPv6 unicast address family view.

    8. Run commit

      The configuration is committed.

(Optional) Configuring the Local Interface for a BGP4+ Connection

When loopback interfaces are used to establish a BGP4+ connection between two peers, the local interface used for the BGP4+ connection needs to be configured on the devices.

Context

To improve the reliability and stability of a BGP4+ connection, the local interfaces used for the BGP4+ connection should be configured as loopback interfaces. When redundant links are available on the network, the BGP4+ connection will not be torn down if an interface or a link fails.

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 } connect-interface interface-type interface-number [ ipv6-source-address ]

    The source interface and source address used to set up a TCP connection are specified.

    BGP4+ uses the physical interface that is directly connected to the peer as the local interface of a TCP connection.

    NOTE:

    When multiple peer relationships between two ME devices are established through various links, running the peer connect-interface command to specify the local interface for a BGP4+ connection is recommended.

  4. Run commit

    The configuration is committed.

Verifying the Basic BGP4+ Configuration

After configuring basic BGP4+ functions, verify BGP4+ peer information.

Prerequisites

Basic BGP4+ functions have been configured.

Procedure

  • Run the display bgp ipv6 peer ipv6-address verbose command to check detailed information about BGP4+ peers.
  • Run the display bgp ipv6 peer ipv6-address log-info command to check the log information of BGP4+ peers.
  • Run the display bgp ipv6 routing-table command to check the information about BGP4+ routes.

Example

# Run the display bgp ipv6 peer command to view information about BGP4+ peers.

<HUAWEI> display bgp ipv6 peer
BGP Local router ID : 20.0.0.1 
local AS number : 100
 Total number of peers : 1                 Peers in established state : 1

 Peer            V    AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv
 2001:db8:20::21 4   200       17       19     0 00:09:59 Established       3
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20269

Downloads: 15

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