reestablish the neighbor relationship. This configuration can prevent the conflict of
sending connection requests.
NOTE
This command can be used on only one of two peers. If this command is used on the two peers,
the connection between the two peers cannot be established.
5. Run:
ipv6-family [ unicast ]
The BGP IPv6 unicast address family view is displayed.
6. Run:
peer { ipv6-address | group-name } enable
The IPv6 peers are enabled.
After configuring the BGP4+ peers in the BGP view, you need to enable these peers
in the BGP IPv6 unicast address family view.
l Configuring an EBGP Peer
Do as follows on the switch on which the EBGP connection 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 | group-name } as-number as-number
The IP address and the AS number of a specified BGP peer are specified.
The AS number of the specified BGP peer should be different from the local AS
number.
If the IP address of the specified peer is that of a loopback interface on the reachable
peer or that of a sub-interface on the directly connected peer, you need to complete
the task of Configuring the Local Interfaces Used for BGP4+ Connections to
ensure that the peer is correctly established.
4. Run:
peer { ipv6-address | group-name } ebgp-max-hop [ hop-count ]
The maximum number of hops in the EBGP connections is set.
Usually, a direct physical link should be available between the EBGP peers. If this
requirement cannot be met, you can use the peer ebgp-max-hop command to
configure the EBGP peers to establish the TCP connections through multiple hops.
NOTE
When establishing the EBGP connection through loopback interfaces, you must use the peer
ebgp-max-hop command specifying that hop-count is greater than or equal to 2. Otherwise,
BGP cannot set up the EBGP connection with the peer.
5. (Optional) Run:
peer { ipv6-address | group-name } listen-only
S6700 Series Ethernet Switches
Configuration Guide - IP Routing 8 BGP4+ Configuration
Issue 01 (2012-03-15) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
501