Implementing Cisco Service Provider VPN Services (300-515 SPVI) Exam Guide
The 300-515 SPVI exam validates implementation skills for service-provider VPN services across Layer 2, Layer 3, and IPv6 technologies. It is intended for network professionals working with MPLS-based VPN environments and forms the concentration-exam path for the CCNP Service Provider certification. This guide helps you decide whether your current experience is sufficient, which blueprint areas deserve the most study time, and how to turn the official topics into a practical preparation plan.
What the 300-515 SPVI exam validates
SPVI tests whether you can implement and support service-provider VPN services rather than merely recognize terminology. Cisco’s stated coverage includes Layer 2, Layer 3, and IPv6 VPN solutions, with the training context extending to MPLS infrastructure, multicast, shared services, and multi-provider VPN designs.
The exam is identified by Cisco as Implementing Cisco Service Provider VPN Solutions v1.1 and is associated with the CCNP Service Provider certification. Passing it earns the Cisco Certified Specialist – Service Provider VPN Services Implementation certification and satisfies the concentration-exam requirement for CCNP Service Provider.
That distinction matters when planning your certification route. A candidate pursuing CCNP Service Provider can treat SPVI as the concentration exam requirement, while a candidate focused on VPN implementation may value the specialist certification independently. Cisco also states that the exam can be used toward recertification.
Who should consider this exam
The strongest candidates are engineers who design, deploy, operate, or troubleshoot provider VPN services and already understand the relationship between the MPLS underlay, VPN control plane, and customer-facing forwarding. The blueprint is more useful to someone who can reason through a broken service than to someone studying isolated command syntax.
Cisco states that the SPVI training has no prerequisites, although recommended background knowledge is listed separately. That training statement should not be read as proof that the exam is suitable for a beginner. Before scheduling, assess whether you can explain PE, P, CE, VRF, MP-BGP, MPLS labels, and service-provider routing behavior without relying on memorized definitions.
What the credential relationship means
Cisco states that passing 300-515 SPVI satisfies the concentration-exam requirement for the CCNP Service Provider certification. It is therefore a focused component of a broader certification path, not a replacement for every other CCNP Service Provider requirement. Review Cisco’s current certification requirements before committing to a complete pathway.
If recertification is part of your decision, Cisco states that SPVI can be used toward recertification. Completing the associated SPVI training is a separate activity; Cisco states that the training earns 40 Continuing Education credits toward recertification. Do not assume that taking the exam and completing the training produce the same recertification outcome.
How the blueprint should control your study time
Use the official domain weights to establish priority, but study dependencies rather than percentages alone. Layer 3 VPNs has the largest share, yet its troubleshooting and multi-provider topics depend on sound VPN architecture, MPLS forwarding, and control-plane reasoning. A sensible plan starts with foundations, then concentrates practice on the two largest domains.
The v1.1 blueprint assigns 25% to VPN Architecture, 30% to Layer 2 VPNs, 35% to Layer 3 VPNs, and 10% to IPv6 VPNs. These are official domain labels and weights; they are not a promise about the exact number or style of questions in a particular sitting.
VPN Architecture: 25%
The VPN Architecture domain covers Layer 2 versus Layer 3 VPNs, Inter-AS versus Intra-AS designs, underlay troubleshooting, Layer 2 service architecture, and Layer 3 VPN control- and data-plane operation. Study this domain as the system model that explains why later services work or fail.
Build a one-page comparison for Layer 2 and Layer 3 services. Include what the provider transports, where customer routes or MAC information are learned, which control-plane exchanges are required, and how the data plane identifies the correct service. Then add an underlay fault checklist: reachability, label distribution, next-hop resolution, route-target or service signaling, and forwarding-table state.
A common mistake is to jump directly into EVPN or inter-AS variants without tracing a basic packet through the provider network. Correct that by drawing the ingress PE, transit P routers, egress PE, and CE devices. For each hop, record the expected control-plane state and the forwarding decision. This makes later troubleshooting questions less dependent on recall.
Layer 2 VPNs: 30%
The Layer 2 VPNs domain includes E-LAN, E-Line, E-Tree, EVPN concepts, Ethernet OAM, EVPN IRB, EVPN VPWS, and native EVPN. Because these services have different connectivity models, organize preparation around service behavior and failure isolation rather than treating every acronym as a separate chapter.
For E-Line, focus on point-to-point service behavior and the boundaries between attachment circuits and the provider transport. For E-LAN, reason about multipoint connectivity, MAC learning, and split-horizon or loop-prevention implications. For E-Tree, identify how root and leaf roles constrain communication. The aim is to predict which endpoints should communicate before looking at implementation details.
Give EVPN a dedicated study map. Separate route-based control-plane learning from data-plane forwarding, then connect EVPN VPWS, native EVPN, EVPN IRB, and Ethernet OAM to the operational problem each addresses. When practicing, ask what information is advertised, which device consumes it, and what symptom appears when that information is missing or inconsistent.
Do not collapse EVPN IRB into ordinary Layer 3 VPN study. EVPN IRB involves integrated Layer 2 and Layer 3 service behavior, so practice tracing both the bridged segment and the routed interface. A useful exercise is to write separate checks for endpoint discovery, MAC or IP advertisement, gateway behavior, and forwarding across the provider network.
Layer 3 VPNs: 35%
The Layer 3 VPNs domain deserves the largest study allocation because it includes PE-CE and PE-PE troubleshooting, multicast VPN, extranet and shared-services designs, Inter-AS options A, B, AB, and C, and CSC concepts. These topics reward a layered troubleshooting method: isolate the customer edge, provider edge, provider core, route exchange, and label forwarding in sequence.
For a basic L3VPN, be able to explain the roles of VRFs, route distinguishers, route targets, MP-BGP, and MPLS labels without treating them as interchangeable. A route distinguisher makes otherwise overlapping routes unique; route-target policy controls import and export. Your notes should show how a customer prefix moves from CE learning through PE control-plane exchange to remote PE forwarding.
PE-CE troubleshooting should begin with the customer-facing routing relationship. Check the intended routing protocol or static design, adjacency or session state where applicable, route presence in the correct VRF, and policy effects. PE-PE troubleshooting then moves inward: VPN route exchange, label information, transport reachability, and the forwarding entry used to carry the packet across the core.
Multicast VPN, extranet, and shared-services scenarios require policy and replication reasoning in addition to unicast reachability. Draw the participating VPNs and mark which routes or services are intentionally shared. This prevents a frequent error: assuming that importing a route automatically grants every form of connectivity or that a unicast fix resolves multicast behavior.
Inter-AS options A, B, AB, and C should be studied comparatively, but not as bare labels. For each option, record where the AS boundary occurs, what is exchanged across it, which devices need VPN awareness, and what operational dependency is introduced. Then test your understanding by identifying the likely fault domain when a route exists in one autonomous system but not the other.
CSC concepts belong in the same multi-provider reasoning framework. Map the customer, carrier supporting the customer, and higher-level provider roles before tracing route and label exchange. If your diagram cannot show which network owns each control-plane relationship, return to the architecture material before memorizing the option names.
IPv6 VPNs: 10%
The IPv6 VPNs domain covers MP-BGP for 6VPE and 6PE, PE-CE routing, and troubleshooting at PE-PE and PE-CE interfaces. Its smaller blueprint weight does not make it safe to ignore: targeted review can close a knowledge gap, while treating IPv6 as a simple vocabulary extension can leave important control-plane differences unexplained.
Study 6PE and 6VPE as distinct design ideas and write down what is being transported, how MP-BGP carries the information, and where IPv6 routing is established. Include PE-CE routing separately from PE-PE troubleshooting. During review, identify whether a symptom originates at the customer interface, in VPN route exchange, or in the provider transport.
A practical final check is to take an IPv6 VPN diagram and label every interface with its expected address family, routing relationship, and forwarding role. This exposes accidental assumptions such as using an IPv4-only troubleshooting sequence without checking the IPv6 control plane.
What to confirm before scheduling
Confirm the exam identity, version, language, duration, cost, and result policy on Cisco’s current exam page before booking. The supplied Cisco information identifies the exam as 300-515 SPVI v1.1, lists English as the available language, and states a 90-minute exam duration. Cisco lists the exam price as US$300 and says Cisco Learning Credits are accepted.
Cisco states that SPVI is graded pass/fail and that results are available online within 48 hours. These details help with scheduling and certification planning, but they do not describe the question format or guarantee a particular result. Use the official booking and certification pages for any delivery or appointment details that may change.
A short scheduling decision rule
Schedule when you can explain the major service models, troubleshoot a basic L3VPN from CE to CE, compare the named inter-AS options, and account for the Layer 2 and IPv6 topics in the blueprint without depending on answer memorization. If you can only define terms but cannot trace control-plane and data-plane behavior, continue preparation.
Check the official exam page immediately before purchase for current availability, registration conditions, and delivery information. The supplied sources verify the exam language, duration, price, and pass/fail policy, but they do not establish a permanent delivery format or a fixed appointment process.
A practical preparation sequence
Prepare in dependency order: establish the provider underlay, model VPN architecture, build Layer 2 services, deepen Layer 3 VPN troubleshooting, then close the IPv6 gap. Use the blueprint to adjust emphasis, but make each stage produce something concrete, such as a diagram, decision table, troubleshooting flow, or lab validation.
This sequence is a recommendation, not an official Cisco schedule. It is designed to reduce a common inefficiency: spending early study sessions on advanced service variants before the underlying route, label, and service-signaling behavior is clear.
Stage 1: Establish the baseline
Begin by inventorying your existing knowledge. Write brief explanations of MPLS forwarding, provider IGP reachability, label distribution, VRFs, MP-BGP, route distinguishers, route targets, PE, P, and CE roles. Mark each explanation as confident, partial, or unknown. This gives you a targeted starting list instead of an undifferentiated reading backlog.
Use the VPN Architecture objectives to connect the terms. Draw an Intra-AS design and an Inter-AS design, then annotate where VPN information is created, exchanged, and used. Add a packet path and a control-plane path to the same diagram. If the two paths are indistinguishable in your notes, revise them until their purposes are clear.
Stage 2: Build the Layer 2 service map
Study E-Line, E-LAN, and E-Tree by comparing their intended endpoint relationships. Follow that with EVPN concepts, EVPN VPWS, native EVPN, EVPN IRB, and Ethernet OAM. For each item, keep four headings in your notes: service topology, endpoint learning or signaling, forwarding behavior, and failure indicators.
If you have a lab environment, create small scenarios rather than one oversized topology. Validate one service model at a time, introduce a controlled fault, and record which operational evidence changes. If a lab is unavailable, perform the same exercise with topology diagrams and expected-state tables. Treat the resulting predictions as study work, not as evidence of access to live exam questions.
Stage 3: Make Layer 3 troubleshooting systematic
Move from basic L3VPN operation to PE-CE and PE-PE troubleshooting. Use a fixed order: customer routing, VRF route presence, VPN route exchange, transport reachability, label or forwarding state, and return path. The order is a practical recommendation; adapt it when the symptom clearly identifies a different layer.
Then add multicast VPN, extranet and shared services, Inter-AS options A, B, AB, and C, and CSC concepts. For each advanced topic, create a failure card with the intended design, the expected control-plane evidence, the expected data-plane evidence, and the first two checks you would perform. This turns broad objectives into decisions you can rehearse.
Stage 4: Close IPv6 gaps and integrate
Review MP-BGP for 6VPE and 6PE, PE-CE routing, and PE-PE and PE-CE troubleshooting after the core VPN model is stable. Avoid studying IPv6 as a detached glossary. Reuse your earlier route-trace method and explicitly mark which address family and control-plane relationship applies at every step.
Finish with mixed scenarios that require you to identify the service type before choosing a troubleshooting path. A good review prompt describes a symptom without naming the technology; your task is to infer whether it points to a Layer 2 service, L3VPN, IPv6 VPN, multicast, or an inter-provider boundary.
How to use the official topic list effectively
Treat the Cisco topic list as a coverage control, not as a substitute for technical understanding. Convert every listed subject into an observable capability: explain it, draw it, distinguish it from a related option, and diagnose one plausible failure. This approach also exposes topics that a passive reading session might overlook.
The official blueprint is the authority for scope. Cisco’s learning-network topic page identifies the Layer 2 and IPv6 areas, while the v1.1 exam-topics document details the VPN Architecture and Layer 3 VPN areas. Keep the current source beside your notes in case Cisco updates the blueprint.
A four-question review method
For each blueprint item, answer four questions. What problem does the technology solve? Where does its state live? What must be true for traffic to forward? What evidence would distinguish a control-plane fault from a data-plane fault? If you cannot answer the fourth question, your knowledge is probably descriptive rather than operational.
For comparison topics, add a fifth question: what design constraint separates this option from its nearest alternative? This is especially useful for Layer 2 service types, 6PE versus 6VPE, and Inter-AS options A, B, AB, and C. The goal is to make selection and troubleshooting defensible rather than based on acronym recognition.
A useful evidence table
Create columns for component, expected state, verification evidence, likely fault, and corrective direction. Use separate rows for CE-PE routing, VRF membership, VPN route exchange, provider transport, labels or forwarding, and return traffic. For Layer 2 services, add attachment-circuit state, endpoint learning, service signaling, and OAM observations.
Do not fill the table with commands copied without interpretation. A command is useful only when you know what state it should reveal and how an unexpected result changes your next step. Keep vendor documentation available for syntax, but make the reasoning independent of a memorized command sequence.
Common preparation mistakes and how to correct them
The most damaging mistakes are strategic: studying all topics with equal depth, memorizing configuration fragments without tracing traffic, and postponing troubleshooting until the end. Correct them by weighting the official domains, practicing state-based diagnosis from the beginning, and reviewing mistakes by root cause rather than by topic name alone.
Mistake: treating the exam as a terminology test
Knowing that a route distinguisher, route target, or label exists is not enough. Ask what changes when the value or relationship is wrong. A route-target problem, for example, should lead you to examine import and export behavior, not simply to repeat the definition of a VRF. Build explanations around observable consequences.
Mistake: overfocusing on the largest domain
Layer 3 VPNs carries 35% of the blueprint, but its advanced topics rely on architecture and underlay knowledge. Allocate the most time there while still completing the 25% VPN Architecture, 30% Layer 2 VPNs, and 10% IPv6 VPNs domains. Do not turn the official percentages into permission to skip a smaller domain.
Mistake: confusing training with an exam requirement
Cisco states that the SPVI training has no prerequisites, but training attendance is not presented in the supplied sources as a prerequisite for sitting the exam. Decide separately whether you need formal instruction, self-study, or a combination. If you choose the training, remember that Cisco separately associates completion with 40 Continuing Education credits toward recertification.
Mistake: relying on dumps or recalled questions
Exam dumps and leaked-question claims are not a reliable preparation method, and memorizing purported answers does not establish implementation skill or guarantee a pass. Use the official blueprint, Cisco training information, technical documentation, diagrams, and legitimate hands-on practice. Your checkpoint should be whether you can justify an answer from service behavior and evidence.
Mistake: ignoring language and scheduling constraints
Cisco lists English as the available exam language and identifies the exam as 90 minutes. Factor that into your practice: rehearse reading dense technical scenarios in English and make decisions without spending the session reconstructing basic terminology. Verify current booking details on Cisco’s exam page before scheduling, because the supplied sources do not establish every delivery condition.
A final review plan for the last study cycle
Use the final review cycle to find weak decisions, not to reread every page. Start with a blueprint audit, then run mixed troubleshooting drills and explain each conclusion aloud or in writing. Finish with a short list of unresolved concepts and resolve those from official material before booking or sitting the exam.
A practical sequence is to review architecture first, then Layer 3 troubleshooting, Layer 2 service distinctions, and IPv6 integration. This order is a recommendation based on topic dependencies and blueprint emphasis. Avoid introducing an unfamiliar technology at the last moment unless it is a clearly identified gap in the official objectives.
The readiness check
You are closer to ready when you can draw a complete provider VPN path, identify the control-plane exchange that should create the relevant state, and name the next verification step when traffic fails. You should also be able to distinguish service intent: point-to-point, multipoint, root-leaf, routed VPN, multicast, shared-services, or IPv6 VPN.
Use the official domain list as a final checklist. Confirm that you have addressed E-LAN, E-Line, E-Tree, EVPN concepts, Ethernet OAM, EVPN IRB, EVPN VPWS, native EVPN, 6PE, 6VPE, PE-CE and PE-PE troubleshooting, multicast VPN, shared services, and the named inter-AS and CSC concepts.
What to bring into the exam decision
Bring a realistic view of your strengths and gaps, not an assumption that a completed course equals readiness. If your weakness is configuration syntax, consult documentation and practice implementation. If your weakness is diagnosis, spend more time on expected-state tables and fault isolation. If your weakness is architecture, return to the provider and VPN diagrams before adding more advanced variants.
Where to verify current information
Use Cisco’s exam page for the current exam identity, price, language, certification relationship, and recertification information; use the official v1.1 topic documents to control technical scope. Use Cisco’s training page and course document when evaluating formal instruction and Continuing Education credit. The pages below are the official sources used for this guide.
Because exam policies, registration information, and course details can change, verify time-sensitive details directly with Cisco before payment or scheduling. This guide does not add delivery claims that are not supported by the supplied sources.
Official source selection
The learning-network topic page is useful for the domain weights and the Layer 2 and IPv6 topic groupings. The Cisco v1.1 exam-topics document provides the exam title, duration, architecture scope, and detailed Layer 3 coverage. Cisco’s exam and certification pages provide the credential, language, price, recertification, and result-policy information.
For training decisions, Cisco’s SPVI course page states that the training has no prerequisites and describes its MPLS VPN implementation context. Cisco’s course document states the Continuing Education credit associated with completing that training.
Conclusion
The best preparation decision for 300-515 SPVI is evidence-based: confirm that the exam matches your service-provider role, map your study to the official domains, and practice tracing both control-plane state and data-plane forwarding. Give priority to Layer 3 VPNs while building the architecture needed to understand it, cover the Layer 2 service families deliberately, and reserve targeted review for IPv6 VPNs. Before scheduling, verify Cisco’s current exam information and use a readiness check based on troubleshooting decisions rather than memorized answers.
Related exams
- 300-510 exam — Implementing Cisco Service Provider Advanced Routing Solutions
- Automating and Programming Cisco Service Provider Solutions (300-535 SPAUTO)
- 300-540 exam — Designing and Implementing Cisco Service Provider Cloud Network Infrastructure (SPCNI)
- Implementing and Operating Cisco Service Provider Network Core Technologies (350-501 SPCOR)
