Nokia VPLS study guide
Nokia VPLS · Work through your exam, one topic at a time.
The Nokia VPLS exam is a study target for network engineers working with Virtual Private LAN Service in Nokia service-router environments. This page is an independent preparation resource; it is not affiliated with, endorsed by, or sponsored by Nokia, and it does not reproduce any vendor exam content. The Nokia VPLS study guide has 6 sections and about 2,161 words.
01VPLS fundamentals and architecture
Domain 1 tests VPLS fundamentals and architecture: the multipoint service model, how Nokia SR OS represents a VPLS, and how the data plane behaves. A VPLS is one Layer 2 broadcast domain extended over an MPLS network.
364 words, about 2 min02VPLS service configuration and provisioning
Domain 2 tests VPLS service configuration and provisioning: the order of operations, required Nokia SR OS objects, and parameter consistency between PEs. Build the underlay: ports, network interfaces, IGP, and LDP or RSVP transport.
366 words, about 2 min03VPLS pseudowires
Domain 3 tests VPLS pseudowires: how Ethernet frames are carried between PEs, how pseudowires are signaled and identified, and how mesh and spoke bindings differ. A pseudowire is an emulated Ethernet circuit between two SDP bindings.
394 words, about 2 min04SAPs and SDPs
Domain 4 tests SAPs and SDPs: local customer attachment, remote service attachment, encapsulation, and binding rules in a Nokia VPLS. A SAP is the local service access point: port plus encapsulation, such as 1/1/1:100 for VLAN 100, a null SAP, or a QinQ SAP.
354 words, about 2 min05VPLS resiliency and redundancy
Domain 5 tests VPLS resiliency and redundancy: how Nokia designs prevent loops, provide dual-homed access, and recover from pseudowire or transport failures. VPLS multi-homing uses BGP-AD-based election to choose a designated forwarder for a multi-homed site.
350 words, about 2 min06VPLS operations, verification and troubleshooting
Domain 6 tests VPLS operations, verification, and troubleshooting: the order to check service, SAP, pseudowire, and transport state, and how to isolate common faults. Check the service: show service id <id base .
333 words, about 2 min