Creates a new BGP peer.
| remoteaddr | Specifies an IP address of the BGP neighbor. |
| as-number | Specifies a remote AS number. The range is 1 to 4294967295. |
| multi-hop | Specifies to allow connections to EBGP peers that are not directly connected. |
N/A.
You can specify an IPv4 or IPv6 address for the BGP peer. The address can be a global unicast or a link-local address. IPv6 link-local remote addresses are supported only for EBGP single-hop peerings.
If the multihop keyword is not specified, the IP addresses of the EBGP speaker and peer must belong to the same subnet.
The AS number is a 4-byte AS number in either the ASPLAIN or the ASDOT format as described in RFC 5396, Textual Representation of Autonomous System (AS) Numbers.
If the AS number is the same as the AS number provided in the configure bgp as command, then the peer is consider an IBGP peer, otherwise the neighbor is an EBGP peer. The BGP session to a newly created peer is not started until the enable bgp neighbor command is issued.
The following command specifies a BGP peer AS number using the ASPLAIN 4-byte AS number format:
create bgp neighbor 10.0.0.1 remote-AS-number 65540
The following command specifies a BGP peer AS number using the ASDOT 4-byte AS number format:
create bgp neighbor 10.0.0.1 remote-AS-number 1.5
The following command specifies a BGP peer using an IPv6 address:
create bgp neighbor fe80::204:96ff:fe1e:a8f1%vlan1 remote-AS-number 200
The following example specifies how to create a neighbor peer group in a VRF (PE – CE neighbor session):
virtual-router <vr_vrf_name>
create bgp neighbor <remoteaddr> remote-AS-number <asNumber> {multi-hop}
create bgp neighbor <remoteaddr> peer-group <peer-group-name> {multi-hop}
delete bgp [{neighbor} <remoteaddr> | neighbor all ]
[create | delete] bgp peer-group <peer-group-name>
BGP maintains a separate RIB (RIB-In, RIB-Loc and RIB-Out) for each of the VRF it is configured to run. So routes received from a peer in VRF1 are not mixed up with routes from a peer in VRF2. Additionally, BGP routes in a VRF are regular IPv4 routes of address family ipv4. The BGP decision algorithm occurs inside a VRF and is not impacted by any BGP activity in other VRF.There can be two BGP neighbors with the same peer IP address in two different VRFs.
This command was first available in ExtremeXOS 10.1.
This command required a specific license in ExtremeXOS 11.1.
Support for 4-byte AS numbers was first available in ExtremeXOS 12.4.
Support for IPv6 was added in ExtremeXOS 12.6 BGP.
Support for L3 VPN was added in ExtremeXOS 15.3.
This command is available on platforms that support the appropriate license. For complete information about software licensing, including how to obtain and upgrade your license and which licenses support the BGP feature, see the Switch Engine 32.3 Feature License Requirements document.