PermitANY
JuniperConfig834 downloads

Juniper JunOS Base / Day-0 Config

Day-zero configuration for Juniper routers and switches: hostname, root password, system services, NTP, DNS, syslog, SNMP, and management interface via JunOS set commands.

↓ example.txt

What is it?

The Juniper base config establishes Day-0 essentials on JunOS: hostname, management access, NTP, syslog, and hardened defaults. JunOS uses a candidate configuration model — changes are staged in a candidate config and only activate when you run 'commit'. This is fundamentally different from Cisco IOS where changes take effect immediately. JunOS organizes config in a hierarchical tree ('set' commands build that tree). Every JunOS device has a routing engine (RE) for control plane and a packet forwarding engine (PFE) for data plane — the management interface lives on the RE.

When to use

  • ·First-time setup of any Juniper device (MX, QFX, SRX, EX series)
  • ·Standardizing Day-0 config before deployment
  • ·After a factory reset — base config must be applied before adding any routing or security config

When NOT to use

  • ·This is a prerequisite — all other Juniper templates depend on base config being in place first

How it compares

vs Cisco IOS base-configIOS changes apply immediately. JunOS stages changes in candidate config and requires 'commit' to activate. JunOS 'rollback 1' instantly reverts to the previous committed config — much safer for production changes.
vs Palo Alto base-configBoth use a commit model. PAN-OS commit validates and pushes to running config. JunOS 'commit confirmed 5' activates for 5 minutes then auto-reverts unless you run 'commit' again — excellent for risky changes.

Prerequisites

  • →Console access for initial setup
  • →Management IP, subnet, and default gateway decided before starting
  • →NTP server IPs available — JunOS requires accurate time for commit logs and certificates
  • →Root password must be set before the first commit or JunOS will reject it

Config Generator

JunOS hashes this with MD5 automatically.

Verification commands

show system uptime

Verify hostname and system uptime after config

ExpectedShows current hostname, JunOS version, and time since last reboot

show ntp associations

Verify NTP sync status with all configured servers

ExpectedShows * (synced), + (candidate), or - (rejected). At least one server should show *.

show log messages | last 20

Verify syslog is capturing events locally

ExpectedShows recent system events. If empty, syslog file configuration may be missing.

Debug commands

show system commit

Show commit history with user, timestamp, and log message

Common mistakes & fixes

SymptomCommit fails with 'must change root password'
CauseJunOS requires root password to be set before first commit
FixIn configuration mode: 'set system root-authentication plain-text-password' and enter a password when prompted. Then commit.
SymptomCannot SSH to management interface
CauseSSH not enabled or management interface not configured
FixVerify 'show interfaces <mgmt-if>' shows the IP. Check 'show configuration system services ssh' exists. Verify route to management gateway.
SymptomNTP not synchronizing
CauseUDP 123 blocked or wrong NTP server IP
FixTest reachability: 'ping <ntp-server> routing-instance mgmt_junos'. Add NTP server via IP if hostname resolution fails.

Further learning

Recommended books to go deeper on this topic.

CCNA 200-301 Official Cert Guide Library

Wendell Odom · Cisco Press · Best starting point for Cisco IOS fundamentals — CLI, interfaces, basic routing

CCNP Enterprise Core ENCOR 350-401 Official Cert Guide

Brad Edgeworth et al. · Cisco Press · For engineers ready to go deeper — routing, switching, security, automation

Related configs