Configuring BGP Peer Relationships Between the Controller and Forwarder

This section describes how to configure BGP peer relationships between a controller and a forwarder, so that the controller can deliver SRv6 TE Policies to the forwarder. This improves SRv6 TE Policy deployment efficiency.

Context

The process for a controller to dynamically generate and deliver an SRv6 TE Policy to a forwarder is as follows:

The controller collects information, such as network topology and SID information, through BGP-LS. Network topology information includes link cost, latency, packet loss rate and more.
The controller and headend forwarder establish an IPv6 SR Policy address family-specific BGP peer relationship.
The controller computes an SRv6 TE Policy based on link cost, latency, packet loss rate and other factors, and then delivers the SRv6 TE Policy to the headend through a BGP peer relationship. The headend forwarder then generates SRv6 TE Policy entries.

To implement the preceding operations, you need to establish a BGP-LS peer relationship and a BGP IPv6 SR Policy peer relationship between the controller and the specified forwarder.

Procedure

Configure a BGP-LS peer relationship.
BGP-LS is used to collect network topology information, making topology information collection simpler and more efficient. You must configure a BGP-LS peer relationship between the controller and forwarder, so that topology information can be properly reported from the forwarder to the controller. This example provides the procedure for configuring BGP-LS on the forwarder. The procedure on the controller is similar to that on the forwarder.
1. Run system-view
  The system view is displayed.
2. Run bgp { as-number-plain | as-number-dot }
  BGP is enabled and the BGP view is displayed.
3. Run peer { group-name | ipv6-address } as-number { as-number-plain | as-number-dot }
  A BGP peer is created.
4. Run link-state-family unicast
  BGP-LS is enabled and the BGP-LS address family view is displayed.
5. Run peer { group-name | ipv6-address } enable
  A specified BGP-LS peer is enabled.
6. Run commit
  The configuration is committed.
Configure a BGP IPv6 SR Policy peer relationship.
This example provides the procedure for configuring a BGP IPv6 SR Policy peer relationship on the forwarder. The procedure on the controller is similar to that on the forwarder.
1. Run system-view
  The system view is displayed.
2. Run bgp { as-number-plain | as-number-dot }
  BGP is enabled and the BGP view is displayed.
3. Run peer { group-name | ipv6-address } as-number { as-number-plain | as-number-dot }
  A BGP peer is created.
4. Run ipv6-family sr-policy
  The BGP IPv6 SR Policy address family view is displayed.
5. Run peer ipv6-address enable
  A specified BGP IPv6 SR Policy peer is enabled.
6. Run commit
  The configuration is committed.