You can configure BGP to generate a summary default route and then determine whether to advertise the default route to a peer by using a route policy.
On the network shown in Figure 1, a BGP-VPNv4 peer relationship is established between PE1 and PE2. In addition, an EBGP-VPN peer relationship is established between PE2 and the core network device, and another EBGP-VPN peer relationship is established between PE1 and CE1. The core network device advertises routes to PE2 through the EBGP-VPN peer relationship. PE2 then advertises the received routes to PE1 through the BGP-VPNv4 peer relationship. Upon receipt, PE1 leaks the routes to its VPN instance. A summary default route can be generated only if routes with a specific prefix exist among the leaked routes. You can configure BGP to generate a summary default route on PE1 so that PE1 matches the leaked routes against an IP prefix list and summarizes the matched routes into a default route. As a result, PE1 advertises only the summary default route to CE1. Traffic over the unmatched routes will not be diverted to PE1, thereby conserving PE1's bandwidth resources.
Before configuring BGP to generate a summary default route, configure basic BGP functions.
The system view is displayed.
An IPv4 prefix list is configured.
The BGP view is displayed.
The BGP-IPv4 unicast address family view is displayed.
BGP is enabled to generate a summary default route based on an IPv4 prefix list.
The configuration is committed.
After configuring BGP to generate a summary default route, verify the configuration.
Run the display bgp routing-table [ network [ mask | mask-length ] ] command to check information about the summary default route.