Click the Exhibit.
The exhibit shows the partial configurations of PE1 and PE2. PE2 is unable to forward VPN data to PE1.
What should be configured to solve this problem?
A.
Configure an MPLS LSP from PE2 to PE1.
B.
Configure a route on PE2 to PE1’s loopback address in inet 0.
C.
Configure a matching vrf-target statement on PE1 and PE2.
D.
Configure a static default route in inet 3 on PE2.
Explanation:
A label-switched path (LSP) is a path through an MPLS network.
Note:
Unusable path:
Path is not usable because of one of the following conditions:
The route is damped.
The route is rejected by an import policy.
The route is unresolved.Incorrect Answers:
C: The vrf-target statements are matching.
http://forums.juniper.net/t5/Routing/VPLS-MPLS-TE-problem/td-p/259975
Option A, final answer.
Step # 2 satisfied option A.
Follow this steps:
If routes from the local CE router are not present in the bgp.l3vpn.0 routing table on the remote PE router, do the following:
1. Check the VRF import filter on the remote PE router, which is configured in the vrf-import statement. (On the local PE router, you check the VRF export filter, which is configured with the vrf-export statement.)
2. Check that there is an operational LSP or an LDP path between the PE routers. To do this, check that the IBGP next-hop addresses are in the inet.3 table.
3. Check that the IBGP session between the PE routers is established and configured properly.
4. Check for “hidden” routes, which usually means that routes were not labeled properly. To do this, use the show route table bgp.l3vpn.0 hidden command.
5. Check that the inner label matches the inner VPN label that is assigned by the local PE router. To do this, use the show route table mpls command.
0
0