QuestionQ60

VerifiedLayer 2 VPNs

Refer to the exhibit.

Question Image

A customer connected to a service provider is operating VPLS. Client applications need Layer 2 extended between sites. However, the customer’s security team wants to prevent Layer 3 routing from being shared with the service provider. A service-provider engineer configured PE1 and PE2 as shown to support the customer’s traffic requirements, but the circuit is down. What action must the engineer take to resolve the issue?

Explanation

The two ends of a manually configured MPLS VPLS pseudowire must use the same VC ID to identify the emulated circuit. PE1 is configured with VC ID 12, whereas PE2 is configured with VC ID 11; changing PE2 to VC ID 12 allows the pseudowire to establish. The VPN ID and bridge-domain values already match and identify the VPLS service and local Layer 2 forwarding domain, respectively.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!