Devices can exchange BGP4+ routing information only after BGP4+ peers are configured and the BGP4+ peer relationship is established.
bgp { as-number-plain | as-number-dot }
peer ipv4-address as-number { as-number-plain | as-number-dot }
The number of the AS where the specified peer resides should be the same as the number of the local AS.
peer ipv6-address connect-interface interface-type interface-number [ ipv6-source-address ]
Usually, BGP4+ uses the physical interface that is directly connected to the peer as the session interface used for the TCP connection.
To increase the reliability and stability of the BGP4+ connections, configure the local interface used for the BGP4+ connection as the loopback interface. In this way, when there are redundant links on the network, the BGP4+ connections are not interrupted due to the failure of a certain interface or a link.
peer ipv6-address listen-only
After this command is used, the existing peer relationship is interrupted. The peer on which this command is used waits for the connection request from its peer to reestablish the neighbor relationship. This configuration can prevent the conflict of sending connection requests.
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.
ipv6-family [ unicast ]
peer ipv6-address enable
After configuring the BGP4+ peers in the BGP view, you need to enable these peers in the BGP IPv6 unicast address family view.
bgp { as-number-plain | as-number-dot }
peer ipv4-address as-number { as-number-plain | as-number-dot }
The number of the AS where the specified peer resides should be the same as the number of the local AS.
peer ipv6-address connect-interface interface-type interface-number [ ipv6-source-address ]
Usually, BGP4+ uses the physical interface that is directly connected to the peer as the session interface used for the TCP connection.
To increase the reliability and stability of the BGP4+ connections, configure the local interface used for the BGP4+ connection as the loopback interface. In this way, when there are redundant links on the network, the BGP4+ connections are not interrupted due to the failure of a certain interface or a link.
peer ipv6-address ebgp-max-hop [ number ]
By default, a direct physical link must be available between EBGP peers. If such a link does not exist, run the peer ebgp-max-hop command to allow EBGP peers to establish a TCP connection over multiple hops.
If hop-count is not specified in the peer ebgp-max-hop command, 255 is used as the maximum number of hops in EBGP connections.
If loopback interfaces are used to establish an EBGP peer relationship, the peer ebgp-max-hop command (hop-count ≥ 2) must be run. Otherwise, the peer relationship cannot be established.
peer ipv6-address listen-only
After this command is used, the existing peer relationship is interrupted. The peer on which this command is used waits for the connection request from its peer to reestablish the neighbor relationship. This configuration can prevent the conflict of sending connection requests.
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.
ipv6-family [ unicast ]
peer ipv6-address enable
After configuring the BGP4+ peers in the BGP view, you need to enable these peers in the BGP IPv6 unicast address family view.