| Question ID 12162 | -- Exhibit --
user@router# run show route advertising-protocol bgp 192.168.12.1
user@router# run show route
inet.0: 11 destinations, 12 routes (11 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
2.2.2.2/32 *[Direct/0] 3w6d 03:57:51
> via lo0.0
192.168.12.0/24 *[Direct/0] 01:07:34
> via xe-0/0/0.0
192.168.12.2/32 *[Local/0] 01:07:34
Local via xe-0/0/0.0
200.1.0.0/16 *[Aggregate/130] 00:00:58
Reject
[IS-IS/165] 00:10:57, metric 10
> to 200.1.1.2 via xe-0/0/3.0
200.1.1.0/24 *[Direct/0] 00:29:21
> via xe-0/0/3.0
200.1.1.1/32 *[Local/0] 00:29:21
Local via xe-0/0/3.0
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
49.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 --
Click the Exhibit button.
Referring to the exhibit, why is the 200.1.0.0/16 prefix failing to be advertised in BGP?
|