In the core network, where the BGP sessions to the branch offices are use the command:
router bgp xxxx
aggregate-address 10.0.0.0 255.0.0.0
You will then want to follow up with applying a prefix-list outbound to your branch offices which will only permit the 10.0.0.0/8 network and will deny the /16's. If you have any other BGP sessions in your core, that are not going to branch offices, you may want to deny the /8 and permit the /16's, or permit both.
The main idea here is to create the network summary, but not to suppress the more specific prefixes. You could also do the following if you do not wish to use the aggregate-address command:
router bgp xxx
ip route 10.0.0.0 255.0.0.0 null0
Same rules apply with respect to filtering routes. If you do not filter the /16's from the branches, there is not much of a reason to generate the /8.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...