352-001 · Question #795
VPLS is implemented in a Layer 2 network with 2000 VLANs. What is the primary concern to ensure successful deployment of VPLS?
The correct answer is B. PE scalability. VPLS with 2000 VLANs creates a significant scalability burden on PE routers, which must maintain separate MAC tables, flooding domains, and pseudowires per VLAN.
Question
VPLS is implemented in a Layer 2 network with 2000 VLANs. What is the primary concern to ensure successful deployment of VPLS?
Options
- AFlooding is necessary to propagate MAC address reachability information
- BPE scalability
- CThe underlying transport mechanism
- DVLAN scalability
How the community answered
(47 responses)- A15% (7)
- B55% (26)
- C6% (3)
- D23% (11)
Why each option
VPLS with 2000 VLANs creates a significant scalability burden on PE routers, which must maintain separate MAC tables, flooding domains, and pseudowires per VLAN.
Flooding for MAC learning is a standard, expected behavior in VPLS and not a deployment concern specific to large VLAN counts.
With 2000 VLANs, each PE router must instantiate and maintain a separate VPLS instance per VLAN, including individual MAC address tables, split-horizon groups, and pseudowire meshes to every remote PE. This multiplies the memory, CPU, and signaling overhead on PE devices dramatically, making PE scalability the primary deployment concern.
The underlying MPLS transport is a prerequisite addressed before VPLS deployment and is not a scaling concern introduced by adding more VLANs.
VLAN scalability refers to the number of VLANs supported by the network, but the real limiting factor is whether the PE hardware and software can handle the per-VLAN VPLS state - which is the PE scalability problem.
Concept tested: VPLS scalability and PE resource constraints
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_l2_vpns/configuration/xe-16/mp-l2-vpns-xe-16-book/mp-vpls-config.html
Topics
Community Discussion
No community discussion yet for this question.