Study guide
5.3 Model-Driven CLI (MD-CLI) and Datastore Management
Nokia Network Routing Specialist I NRS I, 4A0-100
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: OSI and TCP/IP Networking Models
1.1 OSI Reference Model and Layer Functions 1.2 TCP/IP Protocol Stack and Data Encapsulation 1.3 Network Architecture and Device Planes
2 Chapter 2: Ethernet Technology and LAN Switching
2.1 Ethernet Framing and Physical Standards 2.2 Bridging, Switching, and Collision/Broadcast Domains 2.3 VLANs and IEEE 802.1Q Tagging 2.4 Ethernet Redundancy, Spanning Tree, and LAGs
3 Chapter 3: IP Addressing and Subnetting
3.1 IPv4 Addressing Architecture and Classes 3.2 IPv4 Subnetting, CIDR, and VLSM 3.3 IPv6 Addressing Fundamentals 3.4 IP in Homes and Small Businesses
4 Chapter 4: IP Forwarding and Host Resolution
4.1 IPv4 Header Architecture and Packet Forwarding 4.2 Address Resolution Protocol (ARP) and IPv6 Neighbor Discovery 4.3 ICMP and Network Troubleshooting
5 Chapter 5: Nokia Service Router Hardware and Management
5.1 Nokia Service Router Hardware Architecture 5.2 SR OS Classic CLI Navigation and Operations 5.3 Model-Driven CLI (MD-CLI) and Datastore Management 5.4 Boot Process and Configuration Recovery
6 Chapter 6: Routing Fundamentals and Static Routing
6.1 Routing Concepts, RIB vs FIB, and Route Preference 6.2 Static Route Configuration and Next-Hop Resolution 6.3 Dynamic Routing Protocols Overview
7 Chapter 7: Interior Gateway Protocols: OSPF and IS-IS
7.1 OSPF Fundamentals and Adjacency Formation 7.2 OSPF Multi-Area Architecture and LSA Types 7.3 IS-IS Protocol Architecture and Operations
8 Chapter 8: BGP and Internet Architecture
8.1 BGP Architecture and Peering 8.2 BGP Path Attributes and Route Selection 8.3 IBGP Split-Horizon and Scaling Solutions 8.4 Internet Components, Peering, and Transit
9 Chapter 9: MPLS Architecture and Signaling
9.1 MPLS Concepts and Label Operations 9.2 Label Distribution Protocol (LDP) 9.3 RSVP-TE and Traffic Engineering
10 Chapter 10: Nokia VPN Services: Layer 2 and Layer 3
10.1 Nokia Service Architecture and Building Blocks 10.2 Layer 2 Services: VPWS/VLL and VPLS 10.3 Layer 3 Services: IES and VPRN
5.3 Model-Driven CLI (MD-CLI) and Datastore Management
Key Takeaways Explain This Topic AI
MD-CLI stages changes in a candidate; commit activates accepted configuration.
The mode code ex means exclusive; ! means the candidate baseline is out of date.
A leading * marks uncommitted candidate edits.
Commit and persistence are distinct; inspect auto-config-save and the BOF startup location.
A named Layer 3 interface binds addressing to connectivity; a system /32 is a logical endpoint.
Last updated: October 2026
Configuration as a transaction
The Model-Driven Command Line Interface (MD-CLI) uses SR OS data models and a candidate configuration. The current Nokia IP Networks and Services Fundamentals course uses MD-CLI for its exercises. Learn its workflow directly rather than translating Classic commands word by word.
The running configuration governs the active device. A candidate holds proposed edits. Editing a candidate does not activate the proposed interface, route, or service. A successful commit applies accepted changes to running configuration. Persistence is another concern: a restart loads the saved configuration selected by boot settings.
- State or object Meaning
- Candidate Proposed edits awaiting activation
- Running Configuration currently applied to the router
- Saved configuration File intended for startup or backup
- BOF Boot settings, including image/configuration locations
- Operational state What hardware and protocols are actually doing
A BOF is not the entire running service configuration. Likewise, an enabled configuration leaf does not prove an interface is operationally Up.
Enter and inspect a candidate
MD-CLI supports private, exclusive, and global configuration modes. A private workspace separates an operator's edits from another private candidate, but concurrent changes can still require reconciliation at commit. Exclusive mode obtains the configuration lock used by its workflow. Global mode shares a candidate, so an operator must understand whose edits are present before committing.
- An implicit private workflow can begin with: configure private
- /configure system name "R1-lab"
- compare
- validate
- commit
This changes an illustrative system name. It is a command example, not evidence that a router was configured during this review. compare shows differences against the relevant baseline/running configuration. validate checks candidate constraints; commit activates a valid transaction. discard abandons pending changes according to the selected workflow. Use help to check scope before discarding shared work.
Validation cannot know whether a chosen IP address belongs to the intended customer or whether a remote peer has matching configuration. A schema-valid change can still be operationally wrong.
Read the prompt correctly
The MD-CLI prompt normally spans two lines. The context line identifies configuration mode and location; the following line identifies the user and router. In an implicit workflow, a context can resemble [pr:/configure router "Base"] .
The mode indicators are pr for private, ex for exclusive, gl for global, and ro for read-only. A leading * indicates uncommitted candidate changes. An exclamation mark ! indicates an out-of-date baseline . It is not the exclusive-lock symbol: ex identifies exclusive mode.
If another session changes running configuration, a candidate's baseline may become stale. Inspect differences and use the documented update/reconciliation workflow. Do not clear a warning by blindly discarding changes or assuming exclusive mode solves an already-stale comparison.
Configure a Layer 3 interface
A physical port and a named IP interface are different objects. The port provides connectivity; the IP interface supplies Layer 3 addressing and binds to a port or LAG. A system interface is a logical endpoint normally assigned a unique /32 IPv4 address in this course's examples.
The following MD-CLI fragment assumes supported hardware and an already enabled network port 1/1/1 . Enter configuration mode first. /configure router "Base" interface "system" ipv4 primary address 10.10.10.1
- /configure router "Base" interface "system" ipv4 primary prefix-length 32
- /configure router "Base" interface "to-R2" port 1/1/1
- /configure router "Base" interface "to-R2" ipv4 primary address 192.0.2.1
- /configure router "Base" interface "to-R2" ipv4 primary prefix-length 30
- /configure router "Base" interface "to-R2" admin-state enable
- compare
- validate
- commit
The address and prefix length are separate modeled leaves. Do not append Classic address 192.0.2.1/30 syntax to this MD-CLI path. The peer can use 192.0.2.2/30 ; 192.0.2.0 is the subnet and 192.0.2.3 is its conventional broadcast address.
After commit, inspect /show router interface , /show router route-table , and /show router arp . The local connected prefix should appear when the interface is operational. A missing ARP response is a separate issue from candidate validation. An operational interface still needs correct routing and a working return path to reach remote destinations.
Activation, saving, and recovery
commit applies changes to running configuration. The auto-config-save setting can save automatically after a successful commit. When automatic saving is disabled, use /admin save to persist the committed running configuration to its startup location. Inspect the actual setting and BOF instead of assuming that every successful commit was saved.
A confirmed commit provides automatic rollback unless accepted within its configured window. It can help protect remote changes, but it does not replace a recovery path or prove the proposed routing policy is correct. A commit may legitimately flap an interface or restart a protocol whose configuration changed; transactional configuration is not a universal “hitless” guarantee.
Rollback checkpoints and loading an older configuration also require care. In MD-CLI, a rollback can load earlier configuration into the candidate for comparison and commit. Do not treat a Classic admin rollback revert example as an interchangeable MD-CLI candidate command.
For lab review, record four outcomes separately: the candidate validates, the commit succeeds, the intended operational state appears, and the intended startup configuration is saved. This prevents the common mistake of checking only the command's success message.
Primary references
Nokia MD-CLI prompt documentation and configuration editing and saving , checked October 20, 2026. Use the matching release reference for additional features.