{"id":1744,"date":"2026-05-02T09:17:03","date_gmt":"2026-05-02T09:17:03","guid":{"rendered":"https:\/\/www.examtopics.biz\/blog\/?p=1744"},"modified":"2026-10-20T09:39:38","modified_gmt":"2026-10-20T09:39:38","slug":"step-by-step-guide-to-junos-modes-and-command-prompt-structure","status":"publish","type":"post","link":"https:\/\/www.examtopics.biz\/blog\/step-by-step-guide-to-junos-modes-and-command-prompt-structure\/","title":{"rendered":"Step-by-Step Guide to JUNOS Modes and Command Prompt Structure"},"content":{"rendered":"<p>Junos OS separates operational inspection, candidate configuration and the underlying operating-system shell. That separation matters whenever a network change could interrupt the same session used to administer the device. A practical guide should show the command and its resulting state\u2014not simply repeat that the prompts look different.<\/p>\n<p>A Junos prompt conventionally uses <code>&gt;<\/code> in operational mode and <code>#<\/code> in configuration mode. A Unix-like shell prompt may use <code>%<\/code>, but shell prompts and accessibility depend on the platform, login method and account. The prompt identifies an interactive context; it does not establish what a user is permitted to do without reading the role and command.<\/p>\n<h2>Read the prompts before changing a live device<\/h2>\n<p>An operational prompt may look like <code>neteng@edge01&gt;<\/code>. From that context an engineer can inspect interfaces and routing state with commands such as <code>show interfaces terse<\/code> and <code>show route<\/code>. The configuration prompt changes to <code>neteng@edge01#<\/code> after entering <code>configure<\/code>. The hierarchy breadcrumb <code>[edit]<\/code> indicates that the cursor is at the root of the candidate configuration.<\/p>\n<p>Calling operational mode \u201cread-only\u201d is a dangerous simplification. Many <code>show<\/code> commands are observational, but Junos operational commands also include actions such as rebooting, clearing neighbors or taking an interface offline, subject to permissions. Classify an operation by the exact command and device role, not solely by the greater-than symbol.<\/p>\n<h2>The difference between the candidate and active configuration<\/h2>\n<p>When an engineer enters configuration mode, <code>set<\/code> and <code>delete<\/code> change a candidate representation. They do not instantly replace the active forwarding policy. Junos validates and activates a candidate on a successful <code>commit<\/code>. A syntactically valid commit can still create an unreachable management path or an unintended routing result; technical safety requires preflight and a post-change operational check.<\/p>\n<p>Use <code>show | compare<\/code> in configuration mode to inspect candidate differences before attempting a commit. If the candidate includes unrelated edits from another operator, do not assume they were intended for the current change. The collaboration mode\u2014shared, <code>configure private<\/code>, or <code>configure exclusive<\/code>\u2014affects lock behavior and how changes are reconciled.<\/p>\n<h2>A small operational versus configuration lab<\/h2>\n<p>On a disposable Junos lab node, record <code>show version<\/code>, <code>show interfaces terse<\/code>, and <code>show route summary<\/code> before making any changes. Check the intended interface and routing instance against the lab topology. This initial evidence prevents later confusion between a faulty change and an existing fault.<\/p>\n<p>Enter <code>configure<\/code> and inspect an interface description or a harmless lab setting already approved in the change plan. A typical workflow is shown below. The hostname, interface and text are examples; confirm the interface actually exists before testing.<\/p>\n<pre><code>neteng@edge01&gt; show interfaces terse\nneteng@edge01&gt; configure\n[edit]\nneteng@edge01# set interfaces ge-0\/0\/0 description \"lab-uplink\"\n[edit]\nneteng@edge01# show | compare\n[edit]\nneteng@edge01# commit check\n[edit]\nneteng@edge01# commit confirmed 5<\/code><\/pre>\n<p>A confirmed commit activates the proposed change temporarily and starts a rollback timer. It is a control for reachability-sensitive work, not permission to run an unreviewed command. After validating the management path and service behavior, explicitly confirm within the allowed time using the supported commit procedure; otherwise the system restores the preceding configuration when the confirmation timer expires. Version-specific commit-comment policies also require attention.<\/p>\n<p><strong>What commit check does\u2014and does not\u2014establish.<\/strong> <code>commit check<\/code> validates syntax and configuration consistency within the implementation. It does not prove that a routing policy will reach the destination, that a firewall filter allows the required traffic, or that a dependent application remains healthy. For those claims an engineer needs traffic tests, forwarding-table checks, service logs and explicit acceptance criteria.<\/p>\n<p>Treat <code>show system commit<\/code> and post-change interface\/routing observations as additional evidence. If another operator modifies a shared candidate simultaneously, resolve the overlap before committing rather than using commit simply because the syntax passes.<\/p>\n<h2>Rollback, discarded changes and access recovery<\/h2>\n<p><code>rollback 0<\/code> loads the current committed configuration into the candidate in the applicable context, effectively discarding uncommitted edits. <code>rollback 1<\/code> instead loads the most recent earlier saved configuration; that rollback still needs an explicit commit to become active. Do not confuse a saved rollback snapshot, a discarded candidate, and the automatic rollback of an unconfirmed commit.<\/p>\n<p>Junos retains numbered rollback configurations subject to platform\/version behavior. Before testing, document the running version, verified current state, remote or console recovery method, and which rollback number is appropriate. A previous configuration may reintroduce an older defect, so rollback is not a universal safety guarantee.<\/p>\n<p>The engineer should be able to produce one change record: proposed delta, <code>show | compare<\/code> output, commit\/confirmation record, operational tests and final state. If a change cannot be described and recovered this precisely, do not deploy it through an ad hoc CLI session.<\/p>\n<h2>Where the shell fits<\/h2>\n<p>The shell is a lower-level operating-system environment, historically reached via <code>start shell<\/code> on supported systems with appropriate privilege. It is not the standard place to modify a Junos router configuration. Shell access, the appearance of a percent-sign prompt, and return commands vary with Junos OS versus Junos OS Evolved, privileges and how the session was established. Ordinary troubleshooting should begin with documented Junos operational commands instead of relying on an assumed shell transition.<\/p>\n<p>Shell access deserves extra caution because file and process operations may bypass the validation and rollback afforded by the candidate configuration model. A training article should never portray direct filesystem edits as an interchangeable shortcut for supported configuration commands.<\/p>\n<h2>Use this workflow to prepare for current Junos studies<\/h2>\n<p>The current <a href=\"https:\/\/www.examtopics.biz\/jn0-106\">Juniper JNCIA-Junos JN0-106<\/a> pathway tests Junos user interfaces, software fundamentals, routing and monitoring along with networking basics. An aspiring network operator learns more by reproducing a controlled change, capturing routing-table evidence and safely backing out a mistake than by memorizing prompt symbols without understanding their effects.<\/p>\n<p>For context on a different operational problem, the existing <a href=\"https:\/\/www.examtopics.biz\/blog\/how-to-configure-lacp-between-cisco-ios-and-junos-for-network-redundancy\/\">Cisco\u2013Junos LACP setup<\/a> guide shows how a Junos configuration decision must be validated against a peer device. It is a separate applied networking task, not a requirement of every CLI lesson.<\/p>\n<p><strong>Operational and configuration command lookalikes.<\/strong> The word <code>show<\/code> is not enough to identify which configuration view an engineer will see. From an operational prompt, <code>show configuration<\/code> displays the active configuration. From a configuration prompt, <code>show<\/code> displays the candidate configuration at the selected hierarchy. To call an operational command while remaining in configuration mode, use <code>run show ...<\/code>, such as <code>run show interfaces terse<\/code>. If an operator compares those outputs without noting the prompt, an uncommitted candidate can be mistaken for live device state.<\/p>\n<p>A useful troubleshooting drill intentionally changes a lab interface description in the candidate, confirms that the running configuration still has the old description, and then inspects <code>show | compare<\/code>. This distinguishes configuration intent from actual interface state. The engineer should record the commands and both observations, because a screenshot showing only the new candidate text is not evidence of a completed change.<\/p>\n<p>In configuration mode, hierarchy matters as much as the command. <code>top<\/code> returns to the root of the configuration tree and <code>up<\/code> moves one level toward that root. <code>edit interfaces ge-0\/0\/0<\/code> changes context; an unqualified <code>show<\/code> from there is not necessarily the whole candidate. New operators should state their current hierarchy before deleting or renaming any statement.<\/p>\n<h2>Concurrency, configuration permissions and incident response<\/h2>\n<p>A shared configuration session allows multiple authorized operators to interact with candidate changes. That can produce surprising <code>show | compare<\/code> results when someone else stages a change. Private mode gives a user a separate candidate view, subject to its platform and model restrictions; exclusive mode reserves configuration access while the lock is held. Neither eliminates the need for a maintenance window, change ownership and conflict resolution. Read the constraints for your Junos version before choosing a mode.<\/p>\n<p>Junos permissions matter at the class and permission-flag level. A user who can inspect interfaces may not be allowed to enter configuration mode, and the presence of a prompt does not prove the user can commit. For a support runbook, identify which named role can perform operational diagnostics, who can stage a candidate, who may approve a commit and which credentials can access the emergency console.<\/p>\n<p>If a remote access change is in progress, maintain an independent console or out-of-band recovery route before relying on the same SSH session for confirmation. When an unconfirmed commit times out, record both the rollback event and resulting service behavior. A restored management path is not proof that every downstream routing and security function recovered; verify the original acceptance checks again.<\/p>\n<h2>Common lab failures and what they actually prove<\/h2>\n<p>A syntax error caught by <code>commit check<\/code> is a validation success, not a routing lesson. A commit that succeeds but changes a default route incorrectly tests a different control: the operator must compare route resolution and ping\/traceroute observations before and after. A policy change that blocks SSH tests the recovery path and whether the confirmed-commit timer truly returns the session to a known state.<\/p>\n<p>A discarded candidate is another distinct outcome: after <code>rollback 0<\/code>, run <code>show | compare<\/code> to check that the unintended delta is gone. A roll back to an older saved candidate can be operationally risky if it drops unrelated improvements made after that snapshot. Treat rollback numbers as dated configurations requiring review, not universal safe presets.<\/p>\n<p>When assessing progress, ask the learner to explain which configuration is authoritative at every step, to predict whether a command mutates running state, and to show independent post-change evidence. Those three demonstrations capture more real Junos competence than reciting twenty feature slogans.<\/p>\n<h2>Quick diagnostic checklist<\/h2>\n<p>Before: identify the active configuration, operator rights, affected interfaces, peer dependencies, maintenance window, required return path and rollback plan. During: inspect candidate differences, run a syntax check, use confirmed commit for risky lab changes and communicate concurrent edits. After: validate the management session, compare interface and route state, check the affected application and retain the change record.<\/p>\n<p>These controls make the Junos mode boundary practical: observation supplies evidence, candidate edits express intent, and the commit authorizes a tested new operating state. Prompt symbols are useful indicators only when paired with knowledge of the command and deployment context.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Junos OS separates operational inspection, candidate configuration and the underlying operating-system shell. That separation matters whenever a network change could interrupt the same session used [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32],"tags":[],"class_list":["post-1744","post","type-post","status-publish","format-standard","hentry","category-networking"],"_links":{"self":[{"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/posts\/1744","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/comments?post=1744"}],"version-history":[{"count":2,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/posts\/1744\/revisions"}],"predecessor-version":[{"id":5222,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/posts\/1744\/revisions\/5222"}],"wp:attachment":[{"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/media?parent=1744"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/categories?post=1744"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/tags?post=1744"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}