What is the difference between sending default routes to a peer and controlling BGP route advertisement

The difference between the following functions is as follows: The implementation is different, but the configurations do not conflict.

- After a BGP device is configured to send a default route to its peer, the BGP device sends a default route with the local address as the next hop address to its peer, regardless of whether there is a default route in the local routing table. This greatly reduces the number of routes on the network and lowers consumption of memory and network resources on the peer.
Run the peer { group-name | ipv4-address | ipv6-address } default-route-advertise [ route-policyroute-policy-name ] [ conditional-route-match-all { ipv4-address1 { mask1 | mask-length1 } } &<1-4> | conditional-route-match-any { ipv4-address2 { mask2 | mask-length2 } } &<1-4> ] command to configure the AR to send the default route to the peer or peer group.

- After control of BGP route advertisement is configured, you can configure the AR to advertise only routes that the AR wants to advertise or routes that the peer requires. The AR can be configured to control the BGP routes that are advertised globally or to a specified peer (group).
- Run the filter-policy { acl-number | acl-nameacl-name | ip-prefixip-prefix-name } export [ protocol [ process-id ] ] command to configure the AR to control the BGP routes that are advertised globally.
- Run the peer { group-name | ipv4-address | ipv6-address } filter-policy { acl-number | acl-nameacl-name | acl6-number | acl6-nameacl6-name } { import | export } command to configure the AR to control the BGP routes that are advertised to a specified peer (group).

Scroll to top