Click the Exhibit button.
[edit]
user@PE-1# show protocols
rsvp {
interface all;
}
mpls {
label-switched-path p1 {
from 1.1.1.1;
to 4.4.4.4;
no-cspf;
}
interface all;
}
bgp {
group Int {
type internal;
local-address 1.1.1.1;
family inet {
unicast;
}
family inet-vpn {
unicast;
}
neighbor 2.2.2.2;
neighbor 3.3.3.3;
neighbor 4.4.4.4;
}
}
ospf {
area 0.0.0.0 {
interface ge-0/0/2.0;
interface lo0.0;
}
}
[edit]
user@PE-1# show routing-instances CE-1
instance-type vrf;
interface ge-0/0/1.0;
route-destinguisher 65305:395;
vrf-target target:65412:100;
routing-options {
static {
route 100.100.100.0/24 next-hop
192.168.1.100;
}
}
[edit]
user@P-1# show protocols
rsvp {
interface all;
}
mpls {
interface all;}
ospf {
area 0.0.0.0 {
interface ge-0/0/1.0;
interface ge-0/0/2.0;
interface lo0,0;
}
}
[edit]
user@P-2# show protocols
rsvp {
interface all;
}
mpls {
interface all;
}
ospf {
area 0.0.0.0 {
interface ge-0/0/1.0;
interface ge-0/0/2.0;
interface lo0,0;
}
}
[edit]
user@PE-2# show protocols
rsvp {
interface all;
}
mpls {
label-switched-path p2 {
from 4.4.4.4;
to 1.1.1.1;
no-cspf;
}
interface all;
}
bgp {
group Int {
type internal;
local address 4.4.4.4;
family inet {
unicast;
}
family inet-vpn {
unicast;
}
neighbor 2.2.2.2;
neighbor 3.3.3.3;
neighbor 1.1.1.1;
}
}
ospf {
area 0.0.0.0 {
interface ge-0/0/2.0;
interface lo0.0;
}}
[edit]
user@PE2# show routing-instances CE-2
instance-type vrf;
interfcae ge-0/0/1.0;
route-distinguisher 65305:395;
vrf-target target:64512🐺100;
routing-options {
static {
route 200.200.200.0/24 next-hop
10.1.1.100;
}
}
Referring to the exhibit, you have configured an L3VPN that connects Site-1 and Site-2 together, but the BGP
routes are not showing up on the PE routers. The topology in this scenario is shown below.
Site-1 > PE-1 > P-1 > P-2 > PE-2 > Site-2
Which action should you take to allow communication between Site-1 and Site-2?
A.
Enable LDP for all interfaces on all routes.
B.
Change the route distinguisher to be different on PE-1 and PE-2.
C.
Change the route target to match on PE-1 and PE-2.
D.
Configure BGP on P-1 and P-2.
Explanation:
Hidden” routes usually means that routes were not labeled properly.
Label Distribution Protocol (LDP) is a protocol in which routers capable of Multiprotocol Label Switching (MPLS)
exchange label mapping information. Two routers with an established session are called LDP peers and the
exchange of information is bi-directional.
https://www.juniper.net/documentation/en_US/junos14.2/topics/task/troubleshooting/layer-threevpns-diagnosing-common-problems.html
C is correct
0
0
Agree, C is correct, there is a missmatch in target about VRFs
0
0
Agree C
0
0
C, final answer.
In a shared services network to multiple customers, a Route Target (RT), which is a 64-bit value used to identify the final egress PE device for customer routes in a particular VRF, enables complex sharing of routes. This must match on both local and remote PEs. PE1: vrf-target target:65412:100; PE2: vrf-target target:65412:100, and not this (vrf-target target:64512:100).
ldp is very useful in the core and not usually on the Edge routers.
The Junos OS implementation of LDP supports LDP version 1. The Junos OS supports a simple mechanism for tunneling between routers in an interior gateway protocol (IGP), to eliminate the required distribution of external routes within the core. The Junos OS allows an MPLS tunnel next hop to all egress routers in the network, with only an IGP running in the core to distribute routes to egress routers. Edge routers run BGP but do not distribute external routes to the core. Instead, the recursive route lookup at the edge resolves to an LSP switched to the egress router. No external routes are necessary on the transit LDP routers.
0
0