— Exhibit —
user@router>show route advertising-protocol bgp 172.16.36.1
inet.0: 31 destinations, 31 routes (31 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref ASpath
* 10.200.17.0/24 Self I
* 10.200.19.0/24 Self I
— Exhibit —
Click the Exhibit button.
Referring to the exhibit, which three actions would summarize these routes to a BGP peer?
(Choose three.)
A.
Create a policy that accepts the more specific contributing routes.
B.
Create a route to 10.200.16.0/21 with a next hop of 172.16.36.1 under the [edit routing-options
static] hierarchy.
C.
Create a policy that rejects the more specific contributing routes.
D.
Create a policy to accept aggregate routes.
E.
Create a 10.200.16.0/22 route under the [edit routing-options aggregate] hierarchy.
Don’t Forget the Defaults!
!
Remember that the default BGP policy advertises
all active BGP routes
”
The more-specific contributing routes in our case
Modify the Policy
!
Add a term to the policy that rejects (doesn’t
send) the more-specific contributing routes
[edit policy-options policy-statement send-aggregate-route]
user@Tokyo#
set term suppress-specifics from route-filter 10.200/16 longer
user@Tokyo#
set term suppress-specifics then reject
[edit policy-options policy-statement send-aggregate-route]
user@Tokyo#
show
term send-aggregate {
from protocol aggregate;
then accept;
}
term suppress-specifics {
from {
route-filter 10.200.0.0/16 longer;
}
then reject;
0
0