Cisco SPRI 300-510 study materials
Cisco SPRI 300-510 study resources

Cisco SPRI 300-510 study plan

Cisco SPRI 300-510 · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Routing Protocol Implementation and Optimization (OSPF, IS-IS, and route redistribution)

  • Configure multi-area OSPFv2 and OSPFv3 in a lab with at least three areas and two ABRs, and verify each LSA type (1, 2, 3, 4, 5) appears where expected using show commands.

  • Diagram the OSPF path-selection order (intra-area, inter-area, external type 1, external type 2, NSSA) and predict the winning route for five constructed scenarios before testing them in the lab.

  • Compare OSPFv2 and OSPFv3 adjacency requirements (network types, authentication, address families) and document at least four operational differences that affect troubleshooting.

  • Tune OSPF convergence with hello/dead timers, SPF throttling, and stub/NSSA area design, then record adjacency and SPF event timings from lab logs.

Your checkpoint

A one-page OSPF LSA and path-selection cheat sheet plus lab output proving each LSA type and each selection rule was observed.

Week 2

Routing Protocol Implementation and Optimization (OSPF, IS-IS, and route redistribution)

  • Configure IS-IS at Level 1, Level 2, and Level 1-2 with narrow and wide metrics, and verify the attached bit and default route behavior on an L1-L2 router.

  • Map OSPF LSA types to IS-IS LSP, pseudonode, and TLV equivalents, and explain in writing how each protocol floods and ages topology information.

  • Build a redistribution policy between OSPF and IS-IS using route maps, seed metrics, and metric types, and prevent feedback loops with tags and distribute-lists.

  • Troubleshoot three injected faults (metric mismatch, missing passive interface, wrong area/level) using only show and debug output, logging the commands that isolated each fault.

Your checkpoint

A redistribution design document with route-map snippets and before/after routing tables showing correct metric, tag, and loop-prevention behavior.

Week 3

BGP Implementation and Troubleshooting (neighbors, attributes, path selection, route reflectors, confederations)

  • Establish eBGP and iBGP sessions with correct update-source, next-hop-self, and multihop settings, and verify each session reaches Established state after a router reload.

  • Manipulate the BGP best-path algorithm step by step (weight, local preference, AS-path, origin, MED, eBGP over iBGP, IGP metric) and prove each tiebreaker with a controlled lab change.

  • Configure route reflectors with multiple clusters and verify that originator ID and cluster list prevent loops, including a client-to-client reflection scenario.

  • Configure a BGP confederation with at least two member sub-ASs and compare its configuration and path attributes against an equivalent route-reflector design.

Your checkpoint

A best-path decision table mapping each of the eleven selection steps to the exact lab command that changed the outcome, with captured show bgp output for each step.

Week 4

BGP Implementation and Troubleshooting (neighbors, attributes, path selection, route reflectors, confederations)

  • Tune BGP timers, implement prefix limits, and apply route filtering with prefix lists, AS-path filters, and communities to harden a peering design.

  • Diagnose stuck-in-Active, Idle, and OpenSent neighbor states by matching symptoms to causes (ACL, MTU, authentication, AS mismatch) and verify fixes in the lab.

  • Configure BGP route dampening and soft reconfiguration, and measure the effect of each on convergence and CPU using show command counters.

  • Design and validate an outbound and inbound traffic-engineering policy using local preference, MED, and AS-path prepending across two providers.

Your checkpoint

A BGP troubleshooting runbook covering five neighbor failure modes with the exact verification commands and a lab transcript of each fix.

Week 5

MPLS and Segment Routing Implementation (LDP, MPLS TE, SR-MPLS, SRv6)

  • Configure LDP across an MPLS core with loopback-based router IDs, verify label bindings and LIB/LFIB entries, and explain the difference between liberal and conservative label retention.

  • Build an MPLS L3VPN with VRFs, MP-BGP VPNv4 address family, and per-VRF route targets, then verify end-to-end customer reachability across the provider core.

  • Configure RSVP-TE and a segment-routing MPLS tunnel, compare their signaling and path-control behavior, and verify explicit paths with show mpls traffic-eng output.

  • Enable SR-MPLS with segment routing global block, prefix SIDs, and adjacency SIDs, and trace a packet's label stack hop by hop across three routers.

Your checkpoint

A labeled packet-walk diagram for both an LDP-signaled L3VPN and an SR-MPLS path, with captured label stacks at each hop.

Week 6

MPLS and Segment Routing Implementation (LDP, MPLS TE, SR-MPLS, SRv6) & High Availability and Fast Convergence (NSR, NSR/NSF, BFD, TI-LFA, PIC)

  • Compare SRv6 locator, SID list, and endpoint behaviors against SR-MPLS, and configure a basic SRv6 policy in the lab where platform support allows.

  • Configure BFD for OSPF, IS-IS, and BGP neighbors, and measure detection and failover times with and without BFD.

  • Implement NSF/NSR for OSPF, IS-IS, and BGP, and verify that forwarding continues during a control-plane restart by capturing a continuous ping.

  • Configure TI-LFA and IP/LDP Fast Reroute, then measure reconvergence time after a primary link failure and compare it to baseline convergence.

Your checkpoint

A convergence benchmark table listing baseline, BFD, FRR, and TI-LFA failover times measured from captured ping and log timestamps.

Week 7

Multicast Routing Implementation (PIM-SM, PIM-SSM, MSDP, MLDP)

  • Configure PIM-SM with a static and a dynamic Rendezvous Point, verify shared-tree and shortest-path-tree transitions, and capture the (S,G) and (*,G) entries at each stage.

  • Configure PIM-SSM with IGMPv3 joins and verify that no RP is required, then compare its state and join behavior against PIM-SM.

  • Set up MSDP peering between two PIM-SM domains and verify source discovery across the inter-domain boundary.

  • Configure mLDP in a VRF for a multicast VPN and verify label mappings and traffic flow for a provider-tunneled stream.

Your checkpoint

A multicast state table showing (*,G) and (S,G) entries at each hop for PIM-SM, PIM-SSM, and mLDP scenarios, with the RP and MSDP role annotated.

Week 8

Routing Protocol Implementation and Optimization (OSPF, IS-IS, and route redistribution) & BGP Implementation and Troubleshooting (neighbors, attributes, path selection, route reflectors, confederations) & MPLS and Segment Routing Implementation (LDP, MPLS TE, SR-MPLS, SRv6) & Multicast Routing Implementation (PIM-SM, PIM-SSM, MSDP, MLDP) & High Availability and Fast Convergence (NSR, NSR/NSF, BFD, TI-LFA, PIC)

  • Complete a timed 60-question mixed practice set spanning all five domains and score each answer against the blueprint weighting to identify weak areas.

  • Reconfigure a full-stack lab (OSPF or IS-IS underlay, MP-BGP, MPLS or SR, PIM-SM, BFD) from a blank configuration without notes, within 90 minutes.

  • Review every missed practice question and write a corrected explanation for each, citing the specific command or attribute that resolves it.

  • Re-run the convergence benchmark and confirm that failover times still meet the targets set in week 6.

Your checkpoint

A scored practice exam report with a prioritized remediation list and a completed blank-config full-stack lab that passes all verification checks.

Milestones

Week 2: Can explain OSPF and IS-IS flooding, LSA/LSP types, and redistribution loop prevention without notes, and has lab output proving each point.

Week 4: Can walk through all eleven BGP best-path steps in order, name the command that changes each, and has fixed five neighbor failure modes in the lab.

Week 6: Has a working MPLS or SR-MPLS path plus a convergence benchmark table, and can explain TI-LFA and NSF/NSR behavior with measured failover times.

Week 8: Scores at least 80 percent on the mixed practice set and completes the blank-config full-stack lab within 90 minutes with all verification checks passing.