Operational Monitoring and Maintenance · Topic 1 of 4

Show and Monitor Commands

Learn Junos show and monitor commands for JNCIA-Junos JN0-106: common show commands, detail levels, monitor interface, monitor traffic and live log files.

  • 5 min
In a nutshell
  • show gives a snapshot; monitor gives a live view.
  • show interfaces levels: terse, brief, default, detail, extensive.
  • monitor interface = live counters; monitor traffic interface = capture of RE traffic only.

What it is

Show commands display a snapshot of the device's state at the moment you run them: interfaces, routes, hardware, alarms, logs and more. Monitor commands display a live view that keeps updating until you stop it.

Both run in operational mode, at the user@router> prompt. In configuration mode, show displays the candidate configuration instead, so to run an operational show command from there you prefix it with run.

Operational modeuser@routershowSnapshotstate right nowOperational modeuser@routermonitorLive viewuntil you stop it

How it works

Common show commands

CommandShows
show versionHostname, model and Junos OS release
show chassis hardwareInstalled hardware and serial numbers
show chassis alarmsActive chassis alarms, such as a failed fan or power supply
show system alarmsActive system alarms, such as a missing rescue configuration
show system uptimeCurrent time, boot time and time since the last configuration change
show system storageFile system usage
show system usersWho is logged in
show interfaces terseOne line per interface with admin and link status and addresses
show routeThe routing table
show log messagesThe main system log file
show configurationThe active configuration, from operational mode

Detail levels

Many show commands take a level keyword that controls how much you see. show interfaces is the best example.

LevelWhat you get
terseOne line per interface: Admin, Link, Proto, Local and Remote
briefA short summary for each interface
(none)The default, with key status and traffic figures
detailMore counters and per logical unit information
extensiveEverything, including all error counters

Start with terse to find the problem interface, then use extensive on that one interface to see why.

Filtering long output

Output can be long, so you pipe it through a filter with |:

user@router> show interfaces terse | match ge-
user@router> show log messages | last 20
user@router> show route | count

| match shows lines that contain a pattern, | except hides them, | count counts lines, | last shows the end of the output and | no-more prints everything without pausing. The User Interfaces chapter covers filtering in full.

Monitor commands

CommandWhat it does
monitor interface ge-0/0/0Live counters and rates for one interface, updated continuously
monitor interface trafficLive packet and byte counts for all interfaces
monitor traffic interface ge-0/0/0Live packet capture of traffic to and from the Routing Engine on that interface
monitor start messagesShows new lines of a log file on screen as they are written
monitor listLists the files being monitored
monitor stopStops monitoring log files

Inside monitor interface you use single keys: n moves to the next interface, f freezes the display, t thaws it, c clears the counters and q quits.

monitor interfacelive counterskey nNext interfacekey qBack toCLI prompt

monitor traffic is not a transit capture

monitor traffic interface works like a packet sniffer, but it sees only packets sent to or from the Routing Engine, such as routing protocol packets, pings to the device and management sessions. Transit packets forwarded by the PFE do not appear.

user@router> monitor traffic interface ge-0/0/0 no-resolve

The no-resolve option stops the device from trying to resolve addresses to names, which keeps the output fast and clean. Press Ctrl+C to stop the capture.

Watching log files live

monitor start messages prints each new entry of the messages log file as it arrives, which is useful while you bring up a link or a neighbor. It keeps running in the background while you type other commands.

user@router> monitor start messages
user@router> monitor stop

A worked example

Users report that a branch link is slow. The engineer runs show interfaces terse and sees ge-0/0/1 up. Next, monitor interface ge-0/0/1 shows the input rate close to the link speed and the error counters rising.

To see whether OSPF hellos still arrive, the engineer runs monitor traffic interface ge-0/0/1 no-resolve and sees the hellos. The routing is fine; the problem is congestion and errors on the link itself.

How the exam asks about this

  • "Which command shows live statistics for one interface?" → monitor interface ge-0/0/0.
  • "Which command shows log entries as they are written?" → monitor start messages.
  • "Why does monitor traffic not show traffic passing through the router?" → It captures only traffic to and from the Routing Engine.

Common mistakes

Confusing monitor interface and monitor traffic interface. The first shows live counters for all traffic on an interface. The second captures packets, but only host traffic to and from the RE.

Running operational commands at the # prompt without run. In configuration mode, show shows the configuration. Type run show interfaces terse to see operational state from there.

Forgetting to stop log monitoring. monitor start keeps printing until you enter monitor stop, and the output can interrupt your typing.

What to remember for the exam

  • show gives a snapshot; monitor gives a live view.
  • show interfaces levels: terse, brief, default, detail, extensive.
  • monitor interface = live counters; monitor traffic interface = capture of RE traffic only.
  • monitor start messages follows a log file; monitor stop ends it.
  • Use run to execute an operational command from configuration mode.
Exam tip

When a question asks how to watch a problem "in real time", look for an answer that starts with monitor. When it asks for full error counters, look for show interfaces extensive.

Check yourself

  • Which show interfaces level gives one line per interface?

    terse, which lists Admin and Link status, protocol family and addresses for each interface.

  • Will monitor traffic interface ge-0/0/0 show transit packets passing through the router?

    No, it captures only packets sent to or from the Routing Engine.

  • How do you stop the live display started with monitor start messages?

    Enter monitor stop.

Topic 1 of 4 in Operational Monitoring and Maintenance

Test yourself on Operational Monitoring and Maintenance

The full Juniper JNCIA-Junos JN0-106 question bank has 1,155 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.