Configuring BGP Multi-Instance

You can configure BGP multi-instance to achieve separate route management and maintenance.

Usage Scenario

By default, all BGP routes are stored in the BGP base instance, and separate route management and maintenance are impossible. To address this problem, BGP multi-instance is introduced. A device can simultaneously run the BGP base instance and BGP multi-instance, which are independent of each other and can have either the same AS number or different AS numbers. You can deploy different address families for the BGP base instance and BGP multi-instance as required to implement separate route management and maintenance.

Procedure

Run system-view
The system view is displayed.
Run ip vpn-instance vpn-instance-name
Run ipv4-family
Run route-distinguisher route-distinguisher
Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ]
Run quit
Exit the VPN instance IPv4 address family view.
Run quit
Exit the VPN instance view.
Run bgp as-number instance bgpName
The BGP multi-instance view is displayed.
Run ipv4-family vpn-instance vpn-instance-name
The BGP multi-instance VPN instance IPv4 address family view is displayed.
Run peer ipv4-address as-number as-number
The IP address of a peer and the number of the AS where the peer resides are specified.

The IP address of the peer can be one of the following types:
- IP address of the peer's interface that is directly connected to the local device
- IP address of a sub-interface on the peer's interface that is directly connected to the local device
- IP address of a reachable loopback interface on the peer
Run commit
The configuration is committed.