Configuring BGP-LS (IPv6)
BGP-LS (IPv6) provides a simple and efficient method of collecting topology information.
Usage Scenario
- The controller must have high computing capabilities and support the IGP and its algorithm.
- The controller cannot gain the complete inter-area topology information and therefore is unable to calculate optimal E2E paths.
- Different IGPs report topology information separately to the controller, which complicates the controller's analysis and processing.
- Reduces computing capability requirements and spares the necessity of IGPs on the controller.
- Facilitates route selection and calculation on the controller by using BGP to summarize process or AS topology information and report the complete information to the controller.
- Requires only one routing protocol (BGP) to report topology information to the controller.
BGP-LS needs to be deployed on the devices connected to the controller.
Procedure
- To enable IGP topology advertisement, perform the following steps:
- Enable IS-IS topology advertisement.
- Run system-view
The system view is displayed.
- Run isis [ process-id ]
An IS-IS process is configured.
- Run cost-style { narrow | wide | wide-compatible | { compatible | narrow-compatible } [ relax-spf-limit ] }
A cost style is set for the routes to be accepted and sent by the IS-IS device.
- Run traffic-eng [ level-1 | level-2 | level-1-2 ]
TE is enabled at a specified level for the IS-IS process.
- Run ipv6 traffic-eng [ level-1 | level-2 | level-1-2 ]
IPv6 TE is enabled at the specified level for the IS-IS process.
- Run segment-routing ipv6 locator locator-name [ auto-sid-disable ]
IS-IS SRv6 is enabled.
- Run bgp-ls enable [ level-1 | level-2 | level-1–2 ]
IS-IS topology advertisement is enabled.
- (Optional) Run bgp-ls identifier identifier-value
A BGP-LS identifier is configured.
- Run commit
The configuration is committed.
- Run system-view
- Enable IS-IS topology advertisement.
Enable BGP-LS.
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain | as-number-dot }
BGP is enabled, and the BGP view is displayed.
Run peer ipv6-address as-number { as-number-plain | as-number-dot }
The IP address and AS number of a BGP peer are specified.
- Run link-state-family unicast
BGP-LS is enabled, and the BGP-LS address family view is displayed.
- Run peer ipv6-address enable
BGP-LS route exchange with the specified peer is enabled.
(Optional) Run domain identifier domain-id
A BGP-LS domain ID is configured.
A BGP-LS domain ID identifies a device with BGP-LS enabled. If no BGP-LS domain ID is configured, a BGP router ID is used as the BGP-LS domain ID by default. The same BGP-LS domain ID can be configured for multiple devices so that the controller calculates routes based on the combined topology information reported by the devices.
(Optional) Run domain as { domain as-plain | domain as-dot }
A BGP-LS domain AS number is configured.
Two devices with different BGP AS numbers must have the same BGP-LS domain AS number configured using the domain as command so that the controller can obtain combined topology information about the two ASs for route calculation.
(Optional) Run peer ipv6-address reflect-client
An RR is configured, and an RR client is specified.
The router on which the peer reflect-client command is run functions as the RR, and the specified peer functions as a client.
If the clients of an RR are fully meshed, you can run the undo reflect between-clients command to disable route reflection among these clients through the RR to reduce bandwidth consumption.
If a cluster has multiple RRs configured, you can run the reflector cluster-id cluster-id command to configure the same cluster ID for all the RRs. This command is applicable only to RRs.
(Optional) Run peer ipv6-address route-limit limit [ percentage ] [ alert-only | idle-forever | idle-timeout minutes ]
The maximum number of BGP-LS routes that the local device can receive from a specified peer is set.
In most cases, the BGP-LS routing table contains a large number of BGP-LS routes. If a lot of BGP-LS routes are received from peers, excessive system resources will be consumed. To minimize system resource consumption, configure the maximum number of routes that the device can receive from a BGP-LS peer.
(Optional) Run peer ipv6-address route-policy route-policy-name { import | export }
A route-policy is specified for the BGP-LS routes to be received from or advertised to a BGP peer.
After a route-policy is created, you can run the peer route-policy command to use the route-policy to filter the BGP-LS routes to be received from or advertised to a specified BGP peer. The command configuration ensures that only desired routes are accepted or advertised, which helps manage routes and reduces the BGP-LS routing table size and system resource consumption.
(Optional) Run peer ipv6-address route-update-interval interval
An interval at which the device sends Update messages carrying the same route prefix to a specified peer is set.
When BGP-LS routes change, the router sends Update messages to notify its peers. If a route changes frequently, to prevent the router from sending Update messages for every change, run this command to set an interval at which the router sends Update messages carrying the same route prefix to a specified peer.
- Run commit
The configuration is committed.
- Run system-view
Verifying the Configuration
After configuring BGP-LS (IPv6), verify the configuration.
- Run the display bgp link-state unicast peer command to check information about BGP-LS peers and their status.
- Run the display bgp link-state unicast routing-table command to check BGP-LS route information.
- Run the display bgp link-state unicast routing-table statistics command to check BGP-LS route statistics.