You have been asked to deploy a Layer 2 VPN for a new customer.
What information will be present in the PE's associated VPN forwarding table? (Choose three.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.ACD
Sure, I can provide a detailed explanation for this question.
When deploying a Layer 2 VPN for a new customer, the Provider Edge (PE) router will create a VPN forwarding table for that customer. This table contains information about the customer's network and is used to forward traffic between the customer sites.
Here are the three pieces of information that will be present in the PE's associated VPN forwarding table:
Route distinguisher (RD): This is a unique identifier used to differentiate between multiple VPNs on the same PE router. The RD is added to the customer's prefix to create a unique route for that VPN in the VPN forwarding table.
Label base: In Layer 2 VPNs, traffic is forwarded using MPLS labels. The label base is a value used by the PE router to create labels for the customer's network. The label is added to the packet header to ensure that the traffic is delivered to the correct destination.
Interface encapsulation: This refers to the method used to encapsulate the customer's traffic when it is sent across the provider's network. The encapsulation type is configured on the PE router and is specific to the type of Layer 2 VPN being deployed. The most common encapsulation types are Ethernet over MPLS (EoMPLS) and Virtual Private LAN Service (VPLS).
The customer site ID and community name are not typically included in the PE's VPN forwarding table. The customer site ID is used to identify the customer's site within the VPN, but it is not necessary for forwarding traffic. The community name is used to group together multiple VPNs, but it is not specific to a single VPN and is therefore not included in the VPN forwarding table.
I hope this explanation helps you understand the key pieces of information that are present in a Layer 2 VPN forwarding table.