Study guide
12.7 Unified ISSU: Requirements and Verification
JNCIS-ENT Enterprise Routing and Switching Study Guide 2026 Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Junos Enterprise Fundamentals
1.1 JNCIS-ENT Exam Logistics & Blueprint Breakdown 1.2 Junos CLI, Enterprise Platforms & Interface Families 1.3 Layer 2 Bridging Mechanics & Packet Forwarding
2 Chapter 2: VLANs & Inter-VLAN Routing
2.1 VLAN Segmentation and 802.1Q Tags 2.2 Access, Trunk, Native and Voice VLANs 2.3 IRB Architecture and Interface Families 2.4 IRB Configuration and Packet Walk 2.5 VLAN Configuration, Verification & Troubleshooting
3 Chapter 3: Spanning Tree Protocols
3.1 Layer 2 Loops and Root Bridge Election 3.2 STP Costs, Port Roles, States and BPDUs 3.3 RSTP Rapid Convergence & Link Types 3.4 MSTP Architecture & Spanning Tree Operations
4 Chapter 4: Layer 2 Security & Feature Protection
4.1 Edge BPDU and Root Protection 4.2 Loop Protection and Diagnostic States 4.3 Port Security, MAC Limiting & Persistent MAC Learning 4.4 DHCP Snooping, Dynamic ARP Inspection (DAI) & IP Source Guard 4.5 Layer 2 Firewall Filters: Types, Order and Actions
5 Chapter 5: Advanced Layer 2 Features & Storm Control
5.1 Storm Control & Broadcast/Multicast Suppression 5.2 MACsec Link Security and Key Agreement 5.3 LLDP and LLDP-MED Operations & Verification
6 Chapter 6: Protocol-Independent Routing & Load Balancing
6.1 Static, Aggregate, and Generated Routes 6.2 Routing Instances and RIB Groups 6.3 Junos Load Balancing & Filter-Based Forwarding (FBF) 6.4 Martian Routes and Route Acceptance
7 Chapter 7: Junos Routing Policy & Firewall Filters
7.1 Routing Policy Framework & Term Evaluation 7.2 Prefix Lists & Route Filters 7.3 Firewall Filters & Policers
8 Chapter 8: Open Shortest Path First (OSPF) Operation
8.1 OSPF Architecture & Neighbor Adjacency Formation 8.2 OSPF Areas & LSA Types 8.3 OSPFv2 & OSPFv3 Configuration and Verification
9 Chapter 9: Advanced OSPF Features & Routing Policies
9.1 OSPF Special Area Types 9.2 Route Summarization & OSPF Authentication 9.3 OSPF Diagnostics & Common Failure Scenarios
10 Chapter 10: Intermediate System to Intermediate System (IS-IS)
10.1 IS-IS Encapsulation and NET Identity 10.2 IS-IS Levels, Areas and Default Routing 10.3 IS-IS PDU Families and Neighbor Exchange 10.4 IS-IS Database Synchronization and DIS 10.5 IS-IS Configuration, Metrics & Troubleshooting
11 Chapter 11: Border Gateway Protocol (BGP)
11.1 BGP Roles, AS Numbers and TCP Transport 11.2 EBGP/IBGP Sessions, State Machine and Messages 11.3 BGP Attributes & Junos Path Selection Algorithm 11.4 BGP Configuration & Policy Implementation 11.5 BGP Scaling with Route Reflection & Diagnostics
12 Chapter 12: IP Tunneling & High Availability
12.1 GRE & IP-IP Tunneling Architecture 12.2 Link Aggregation (LAG/LACP) & Redundant Trunk Groups (RTG) 12.3 Virtual Chassis Roles and Elections 12.4 Virtual Chassis Links, Splits and Provisioning 12.5 Routing Engine Redundancy: GRES, NSR, NSB and GR 12.6 BFD Detection and VRRP Gateway Redundancy 12.7 Unified ISSU: Requirements and Verification
12.7 Unified ISSU: Requirements and Verification
Key Takeaways Explain This Topic AI
Unified ISSU reduces upgrade disruption on supported hardware and release paths; it is not a promise of zero packet loss on every Junos device.
Validate the exact source/target release pair, hardware, protocols and configuration before starting the supported upgrade workflow.
GRES, NSR, NSB and configuration synchronization preserve different state and may be prerequisites; their presence alone does not prove ISSU support.
Check upgrade status and post-upgrade forwarding, protocol and service evidence before accepting the maintenance as complete.
Last updated: October 2026
What Unified ISSU Adds
Unified in-service software upgrade (ISSU) coordinates a supported move between Junos releases while maintaining control-plane service and minimizing traffic disruption. An ordinary reboot upgrade restarts the device through a software change. GRES preserves kernel/forwarding state during an RE switchover; NSR preserves supported routing protocol state; NSB preserves supported Layer 2 control state. ISSU uses the appropriate mechanisms as part of a software-upgrade sequence, including compatibility checks and staged component changes.
These mechanisms solve related but different problems. A chassis can be ready for GRES yet run a release pair that does not support ISSU. A valid software package can be installable using a disruptive method while incompatible with an in-service upgrade. A device with one RE or a particular line card may have a different upgrade procedure entirely. Exam questions often test this dependency reasoning, rather than the ability to recite a single upgrade command.
Establish the Supported Upgrade Path
Before a maintenance action, identify the exact hardware and source/target versions, then consult the platform’s release notes and unified ISSU requirements. Check supported REs, line cards, software packages, protocol features and configuration restrictions. Confirm that the target is a supported step from the current release; do not assume two releases with familiar version numbers can be connected directly.
- Readiness evidence Why it matters
- Supported source/target pair and package Determines whether the in-service method applies
- Healthy redundant control components A failed backup cannot take over the active workload
- GRES/NSR/NSB and synchronization where required Determines which state can survive each stage
- Stable protocol and forwarding state Provides a baseline against which disruptions can be detected
- Console/recovery access and saved configuration Provides an independent path if normal management fails
Use show version , show chassis hardware , show chassis alarms and applicable redundancy status views. Compare configuration synchronization and protocol readiness instead of treating a powered-on backup RE as ready. Check storage and package integrity through the platform’s supported workflow. Resolve an active alarm or unsynchronized standby before interpreting the system as safely redundant.
Validation Before Upgrade
On platforms supporting the unified ISSU command family, a separate validation command can detect compatibility issues before the upgrade action: request system software validate in-service-upgrade /var/tmp/<supported-package>.tgz
This command illustrates a platform-dependent maintenance workflow; it is not an instruction to run it on an arbitrary switch. Read validation output and investigate incompatibilities. A failed validation is evidence to repair the plan, rather than a reason to bypass validation with a convenient option. Some platforms and software families use different commands or package formats, so the requirements determine the syntax.
For the documented command family, the upgrade action has this shape: request system software in-service-upgrade /var/tmp/<supported-package>.tgz
The operation changes device software and can disrupt service. It should follow a reviewed maintenance plan with an appropriate fallback. A study guide can explain the sequence without claiming that this command has been tested on the reader’s hardware. Distinguish command syntax recognition from operational authorization and readiness.
Monitoring the Sequence
Monitor applicable upgrade status and logs during the operation. Determine which RE or component is active, which stage has completed and whether a reported condition is expected. An SSH session reconnecting does not prove the routing protocols or line cards recovered. Avoid issuing overlapping upgrades, reboots or switchovers simply because a stage takes longer than expected; use the documented status and recovery procedure for the current state.
Compare protocol observations with the baseline: OSPF and IS-IS adjacency counts, BGP session and route counts, STP port roles, LACP collecting/distributing state, VRRP ownership and BFD sessions. Do not assume NSR covers every enabled protocol on every release. If a timer is shorter than a supported interruption, a peer can still declare failure even though the local upgrade mechanism is working as designed.
Post-Upgrade Acceptance and Failure Analysis
Verify the intended version on all relevant components and that the backup is healthy and synchronized again. Check alarms, interface status, errors and forwarding-table installation. Send representative traffic through the real required paths, including large packets where MTU behavior matters. Compare sustained counters and protocol state with pre-upgrade observations; a single successful ping tests only a small part of the service.
If a validation fails because of an unsupported feature, choose a supported remediation or a planned disruptive upgrade instead of relabeling the task ISSU. If the upgrade reports completion but the backup remains unavailable, the service may be forwarding while redundancy is still degraded. Restore redundancy and verify it before declaring the maintenance complete.
Keep unified ISSU , platform-specific nonstop software upgrade (NSSU) and an ordinary reboot upgrade distinct. Similar names do not establish identical hardware requirements or interruption guarantees. The reliable exam answer states the desired outcome, required support and state-preservation dependencies, then selects the supported workflow.
Official references checked 2026-10-18: unified ISSU requirements , validation command , and upgrade command .