Configuring BGP MVPN Peers
Context
To exchange BGP A-D and BGP C-multicast routes, different PEs on an NG MVPN must be able to discover other PEs on the MVPN. The discovery process is called MVPN membership autodiscovery. An NG MVPN uses BGP to implement this process. To support MVPN membership autodiscovery, BGP defines a new BGP-MVPN address family. In an IPv4 Layer 3 multicast over VXLAN Scenario, all PEs functioning as VXLAN gateways must establish a BGP MVPN peer relationship between one another.
Procedure
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
- Run peer ipv4-address as-number as-number
A BGP peer IP address is specified.
- (Optional) Run peer ipv4-address connect-interface interface-type interface-number [ ipv4-source-address ]
A source interface and a source address are specified to set up a TCP connection with the BGP peer.
By default, BGP uses the outbound interface of packets as the source interface.
![]()
NOTE: When loopback interfaces are used to establish a BGP connection, running the peer connect-interface command on both ends is recommended to ensure the connectivity. If this command is run on only one end, the BGP connection may fail to be established.
- (Optional) Run peer ipv4-address ebgp-max-hop [ hop-count ]
The maximum number of hops allowed for an EBGP connection is configured.
hop-count defaults to 255.
In a scenario where an NG MVPN crosses different ASs, it is necessary to establish EBGP peers. Generally, EBGP peers are directly connected. If they are not directly connected, run the peer ebgp-max-hop command so that they can establish a connection over multiple hops.
![]()
NOTE: If loopback interfaces are used to establish an EBGP connection, run the peer ebgp-max-hop command with hop-count greater than or equal to 2. Otherwise, the EBGP connection cannot be established.
- Run ipv4-family mvpn
The BGP-MVPN address family view is displayed.
- Run peer { ipv4-address | group-name } enable
The device is specified as a BGP MVPN peer.
- (Optional) Run c-multicast ad-route-ignore
The device is configured not to check whether local A-D routes exist after it receives C-multicast routes from its BGP MVPN peers.
By default, after a device receives C-multicast routes from its BGP MVPN peers, the device checks whether local A-D routes exist.
A multichassis link aggregation group (M-LAG) is used to implement active-active gateways on an inter-AS VXLAN, and different RD values are configured for the VPN instance IPv4 address families on the two nodes that act as active-active gateways. After receiving a C-multicast route, both nodes check the validity of the C-multicast route. If one node checks that the RD value contained in the C-multicast route is different from that in a local A-D route, the node sets the C-multicast route to be invalid. As a result, the M-LAG function cannot take effect. To prevent the preceding situation, perform this step on the two nodes that act as active-active gateways.
- Run commit
The configuration is committed.
Follow-up Procedure
Configure the following BGP functions in the BGP-MVPN address family view as needed. For details, see "BGP Configuration".
Configuring a BGP Peer Group
Configuring a Route Reflector and Specifying Clients
Configuring a MinRouteAdvertisementIntervalTimer
Setting Next_Hop Attributes for Routes
In the BGP-MVPN address family view, a device can be configured to use its own IP address as the next-hop address of routes only when advertising these routes.
Configuring BGP Community Attributes
In the BGP-MVPN address family view, only standard community attributes can be sent to peers or peer groups.
Previous
