-- Exhibit --
[edit]
# show protocols bgp
group ibgp {
type internal;
local-address 3.3.3.3;
family inet;
neighbor 2.2.2.2;
}
[edit]
# show routing-instances
VRF {
instance-type vrf;
interface xe-0/0/1.0;
route-distinguisher 3.3.3.3:100;
vrf-target target:100:100;
vrf-table-label;
}
[edit]
# show protocols mpls
interface all;
[edit]
# show protocols rsvp
interface all;
-- Exhibit --
Click the Exhibit button.
Referring to the exhibit, what is missing in the configuration to make the Layer 3 VPN functional? (Choose two.)
[email protected]
[email protected]
[email protected]
[email protected]
Click on the arrows to vote for the correct answer
A. B. C. D.AD
Referring to the exhibit, the Layer 3 VPN configuration is incomplete, and two missing pieces of configuration are required to make it functional. These missing configurations are:
A. a label-switched path:
In MPLS, a label-switched path (LSP) is a unidirectional path that forwards data packets based on labels. In order to establish a Layer 3 VPN, a label-switched path (LSP) must be created between the provider edge (PE) routers that are connected to the VPN. The LSP is responsible for forwarding the labeled packets between the PE routers.
In the given exhibit, the MPLS protocol is configured, but there is no configuration for creating an LSP. Therefore, an LSP configuration is missing, which is required to make the Layer 3 VPN functional.
B. the LDP protocol configuration:
In MPLS, the Label Distribution Protocol (LDP) is used to distribute labels across the network. The LDP protocol establishes and maintains label bindings between the PE routers.
In the given exhibit, the MPLS protocol is configured, but there is no LDP protocol configuration present. Therefore, LDP protocol configuration is missing, which is required to make the Layer 3 VPN functional.
C. a virtual circuit ID and D. an NLRI of family inet-vpn unicast are not required for Layer 3 VPN functionality, and therefore, they are not the correct answers to this question.