Nokia NRS II Composite (IS-IS) study plan
Nokia NRS II Composite (IS-IS) · Give each week a clear focus.
8 weeks · About 7 hours per week
IS-IS fundamentals and protocol operation & IS-IS adjacency formation and neighbor state machine
Diagram the IS-IS packet types (IIH, LSP, CSNP, PSNP) and label which PDU carries which TLVs and at which level
Trace the three-way adjacency handshake step by step and state exactly which TLVs (point-to-point adjacency, protocols supported, area address) must match or mismatch for each outcome
Explain DIS election and pseudonode LSP creation on a broadcast LAN, including why there is no backup DIS
Compare Level 1, Level 2 and Level 1-2 interface behaviour and predict which adjacencies form on each pairing
Your checkpoint
A one-page adjacency decision table listing every TLV/parameter (area address, level capability, MTU, authentication, protocol support) with the resulting adjacency state when it matches or fails
Link-state database, LSP flooding and synchronization & SPF computation and route selection
Describe the LSP ID structure (system ID, pseudonode ID, fragment number) and the role of the remaining lifetime, sequence number and checksum
Walk through the CSNP/PSNP database synchronisation process on point-to-point and broadcast links and identify who sends what
Explain the SRM/SSN flag mechanism on Nokia SR OS and how it drives flooding and acknowledgement
List the ordered steps of the SPF calculation, including the two-pass behaviour when a router is attached to multiple areas
Distinguish internal, external and inter-area route preference and describe how route preference values break ties in SR OS
Your checkpoint
A written 15-step walkthrough of an LSP from origination to SPF insertion, annotated with the SR OS show commands that expose each step
IS-IS addressing, NSAP/NET structure and area design & IS-IS levels, area boundaries and inter-area routing
Construct valid NSAP and NET addresses and verify the system ID length, area address and AFI rules
Design a two-area topology and justify which links are Level 1, Level 2 or Level 1-2
Explain how Level 1 routers reach other areas via the closest attached bit and default route, and where route leaking changes that
Configure and verify route leaking between levels on SR OS and state when it is appropriate
Your checkpoint
A worked addressing plan for a three-router, two-area lab with every NET, level assignment and leaked prefix documented, plus the expected routing table on each router
IS-IS metrics, wide metrics and traffic engineering extensions & IPv6 and multi-topology IS-IS
Compare narrow and wide metric encoding, state the maximum values and explain when wide metrics are mandatory
Configure metric styles and per-level interface metrics on SR OS and predict the resulting path selection
Explain how TE extensions (traffic engineering TLVs, administrative groups, bandwidth) are carried and which router role originates them
Describe multi-topology IS-IS, the MT TLVs and how IPv4 and IPv6 topologies are kept separate
Configure IPv6 and multi-topology on SR OS and verify separate SPF trees
Your checkpoint
A lab report showing an asymmetric-metric scenario where narrow and wide metrics select different paths, with captured LSP TLVs proving the metric encoding
IS-IS on Nokia SR OS: configuration, verification and troubleshooting
Build a working SR OS IS-IS configuration from scratch covering area, level capability, interface and authentication
Use show router isis adjacency, database, spf-log and interface commands to verify each layer of protocol operation
Trigger and diagnose at least three deliberate failures: MTU mismatch, authentication mismatch and area mismatch
Apply and verify LSP pacing, hello timers and overload bit behaviour
Your checkpoint
A troubleshooting log of the three induced failures, each with the symptom observed, the command that isolated the cause, and the fix applied
Link-state database, LSP flooding and synchronization & SPF computation and route selection & IS-IS on Nokia SR OS: configuration, verification and troubleshooting
Reproduce a fragmented LSP scenario and explain fragment zero rules and the overload bit's effect on SPF
Analyse an SPF log and correlate a topology change with the recomputed routes
Verify database synchronisation after a link flap using CSNP/PSNP counters
Explain prefix attributes, route tags and how SR OS applies route preference to IS-IS versus other protocols
Your checkpoint
A before-and-after capture set (database and routing table) for a link flap, with a written explanation of every changed LSP and route
IS-IS fundamentals and protocol operation & IS-IS adjacency formation and neighbor state machine & IS-IS levels, area boundaries and inter-area routing
Re-derive the adjacency state machine from memory and correct any gaps against your week 1 notes
Explain Graceful Restart and BFD interaction with IS-IS adjacencies at a conceptual level
Compare IS-IS area boundary behaviour with OSPF to lock in the differences that exam questions exploit
Review all domain 1, 3 and 6 objectives and write a short summary of each
Your checkpoint
A closed-book concept map of domains 1, 3 and 6 with every gap marked and then filled in, dated
IS-IS addressing, NSAP/NET structure and area design & IS-IS metrics, wide metrics and traffic engineering extensions & IPv6 and multi-topology IS-IS & IS-IS on Nokia SR OS: configuration, verification and troubleshooting
Run a timed mixed-topic review covering addressing, metrics, IPv6/MT and SR OS operations
Re-perform the week 5 failure scenarios without notes and confirm correct diagnosis each time
Consolidate all weak points from weeks 1-7 into a single revision sheet
Verify command syntax recall for the ten most-used SR OS IS-IS show and config commands
Your checkpoint
A final one-page revision sheet plus a scored self-assessment listing every objective still below confident level
Milestones
Week 2: Can explain the full LSP lifecycle and SPF trigger sequence from memory and name the SR OS command that shows each stage
Week 4: Can design a two-area addressing plan and predict route selection under both narrow and wide metrics without referring to notes
Week 6: Can diagnose an adjacency or flooding failure in the lab in under ten minutes using only SR OS show commands
Week 8: Scores at least 80 percent on a mixed self-test across all nine domains with no domain below 70 percent