Which two changes must you implement to resolve the problem?
Refer to the Exhibit.
— Exhibit –[edit]
user@router# show protocols bgp
group myEBGP {
import noTransit;
peer-as 318;
neighbor ;
}
[edit]
user@router# show policy-options
policy-statement noTransit {
term rejectAS1524 {
from as-path AS1524;
then accept;
}
}
as-path AS1524 *1524*;
— Exhibit —
To block transit traffic from AS1524, you have configured and committed the configuration as
shown in the exhibit. However, traffic from AS1524 is still flowing through your AS.
Which two changes must you implement to resolve the problem? (Choose two.)
what is causing the problem?
Refer to the Exhibit.
— Exhibit –[edit]
user@router# show protocols bgp
group ebgp {
import block-martian;
family inet {
unicast;
}
peer-as 65530;
neighbor 172.22.135.37;
}
[edit]
user@router# show policy-options
policy-statement block-martian {
term 1 {
from {
route-filter 0.0.0.0/8 orlonger reject;
route-filter 127.0.0.0/8 orlonger reject;
route-filter 191.255.0.0/16 orlonger reject;
route-filter 192.0.0.0/24 orlonger reject;
route-filter 223.255.255.0/24 orlonger reject;
route-filter 240.0.0.0/4 orlonger reject;
}
}
then reject;
}
[edit]
You have established a peering with an EBGP neighbor, but the peer’s 172.0.0.0/8 routes show as
hidden.
Referring to the exhibit, what is causing the problem?
which configuration is required on router R2 to advertise labels corresponding to direct routes?
What is causing the problem?
Refer to the Exhibit.
— Exhibit –user@router# show policy-options
policy-statement isis-export {
term 1 {
from {
route-filter 172.22.135.0/8 orlonger reject;
route-filter 172.22.135.0/24 orlonger accept;
}
then reject;
}
term 2 {
from {
protocol isis;
route-filter 10.0.0.0/8 longer;
route-filter 10.0.0.0/24 longer accept;
}
then reject;
}
}
— Exhibit —
You are asked to block the 10.0.0.0/8 IS-IS routes from being redistributed into other protocols.
You still want the existing 10.0.0.0/25 IS-IS routes to continue to be redistributed. You have
applied an export policy as shown in the exhibit, however, the 10.0.0.0/8 routes are still being
redistributed.
What is causing the problem?
What is the problem?
Refer to the Exhibit.
— Exhibit –user@P1# show policy-options policy-statement imp-bgp1 term 1 {
from {
protocol bgp;
route-filter 0.0.0.0/0 orlonger;
}
then {
preference 245;
}
}
user@P1# show protocols bgp group IBGP
local-address 172.24.255.1;
family inet {
unicast;
}
family inet-vpn {
unicast;
}
cluster 172.24.255.1;
peer-as 50;
neighbor 172.24.255.3;
neighbor 172.24.255.2 {
local-preference 200;
import imp-bgp1;
}
neighbor 172.24.255.4;
— Exhibit —
The operator of the network shown in the exhibit wants to make 172.24.255.2 the preferred path
for routes. However, the router still prefers a different peer.
What is the problem?
what should you do on PE2 to resolve the problem?
Refer to the Exhibit.
You are asked to troubleshoot a new Layer 3 VPN implementation. Each PE is not receiving
routes from the other PE or the remote CE network.
Referring to the exhibit, what should you do on PE2 to resolve the problem?
what is the reason for the failed connection?
Refer to the Exhibit.
Your company is connecting a third VPLS site to your existing VPLS core. The new connection is
not working and you have been asked to resolve the problem.
Referring to the exhibit, what is the reason for the failed connection?