0000.0020.0200.2002/72
*[Direct/0] 3w4d 21:07:32
> via lo0.0
inet6.0: 3 destinations, 4 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both
2:2:2::2/128 *[Direct/0] 3w4d 21:22:24
> via lo0.0
[edit]
user@router# show policy-options
policy-statement adv-route {
term t1 {
from {
protocol isis;
route-filter 200.1.0.0/16 exact;
}
then accept;
}
term t2 {
then reject;
}
}
[edit]
user@router# show protocols bgp
group ebgp {
type external;
export adv-route;
neighbor 192.168.12.1 {
peer-as 65000;
}
}
— Exhibit —
Referring to the exhibit, why is the 200.1.0.0/16 prefix failing to be advertised in BGP?
A . BGP needs a next-hop self policy.
B . The aggregate route is set to reject.
C . The policy works for internal BGP only.
D . The IS-IS route is less preferred than the aggregate route.
Answer: D
Leave a Reply