Configuring BGP-EPE
Enabling SRv6 BGP-EPE
About this task
BGP-EPE allocates BGP peer SIDs to inter-AS segments. The device advertises the peer SIDs to a network controller through BGP LS messages. The controller orchestrates the IGP SIDs and BGP peer SIDs to realize optimal inter-AS traffic forwarding.
With this feature, the device can allocate SRv6 SIDs to its connected BGP peers or peer groups to identify its connected BGP peers or links.
Restrictions and guidelines
If you do not specify any parameters for the peer egress-engineering srv6 command, the device will dynamically allocate SRv6 SIDs to peers. The SRv6 SIDs belong to the locator specified by using the segment-routing ipv6 egress-engineering locator command in BGP instance view.
When you use the peer egress-engineering srv6 command for a peer, follow these restrictions and guidelines:
•
If you use this command to specify multiple locators for that peer, only the most recent configuration takes effect.
•
If you use this command to specify multiple static SRv6 SIDs and the SIDs belong to different types, all types of SRv6 SIDs can take effect. For the same type of SRv6 SIDs, only the most recent configuration takes effect.
If you specify a static SRv6 SID for a peer, the specified static SRv6 SID must belong to the locator specified by using the segment-routing ipv6 egress-engineering locator command in BGP instance view.
The static SRv6 SIDs specified by using the following commands cannot be the same:
• peer egress-engineering srv6 .
• egress-engineering srv6 peer-set .
Procedure
1. Enter system view. system-view
2. Enter BGP instance view. bgp as-number [ instance instance-name ]
3. Enable SRv6 BGP-EPE.
peer group-name egress-engineering srv6
peer ipv6-address [ prefix-length ] egress-engineering srv6 [ locator
locator-name | static-sid { psp psp-sid | no-psp-usp no-psp-usp-sid }
* ]
By default, SRv6 BGP-EPE is disabled.
133
