srx-initial-setup

Automates Day-0 and Day-1 bring-up of Juniper SRX firewalls with staged, rollback-safe configuration.

9|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/fastrevmd-lab/fwskillsshare --skill srx-initial-setup-fastrevmd-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: srx-initial-setup
Source: https://github.com/fastrevmd-lab/fwskillsshare/tree/main/skills/srx-initial-setup
Command: npx skills add https://github.com/fastrevmd-lab/fwskillsshare --skill srx-initial-setup-fastrevmd-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? First-time setup of a Juniper SRX is error-prone: factory-default remnants like phone-home ZTP can reboot the device mid-session, hidden NTP statements silently break log onboarding, and a wrong interface change can lock the operator out entirely. This Skill replaces ad-hoc bring-up with a deterministic assess-first workflow that classifies device state, computes only the open gaps, and applies every lockout-risk change behind a confirmed-commit gate with automatic rollback. ## Core Features & Use Cases - Read-only entry-state assessment: Classifies any SRX as factory-default, bare, partial, configured, or unreachable using evidence commands like show configuration chassis and show security zones, then generates a dependency-ordered gap list. - Five gated configuration stages: Access and recovery, management plane (hostname, DNS, NTP), interfaces and zones with host-inbound-traffic, starter IDS screens, and a baseline global security policy with default-deny and logging. - Branch factory-default removal: Hardware-validated handling of SRX300/400 shipped configuration, including auto-image-upgrade removal, per-interface untrust services, and atomic policy cutover from zone-pair to global policies. - Entitlement readout: Reports licensed, configured, and active state for features like IDP and AppID without ever mutating licenses. - Use Case: An engineer unboxes an SRX345, connects via console, and asks the agent to bring it to a usable baseline. The Skill detects factory-default state, disables ZTP first, then walks each stage under commit confirmed, rolling back automatically if verification fails. ## Quick Start Use the srx-initial-setup skill to assess this SRX and bring it to a usable baseline with staged approvals.

Frequently Asked Questions about srx-initial-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a new Juniper SRX from factory default?

Run a read-only entry-state assessment first to classify the device, then close gaps in dependency order: access and recovery, management plane, interfaces and zones, starter screens, and baseline policy. On Branch SRX300/400, disable chassis auto-image-upgrade first because phone-home ZTP resets DHCP clients and can reboot the device unattended.

How do I safely remove factory-default config on an SRX345?

Remove factory elements only after the replacement management path is established and verified, since every factory gap carries lockout risk. Apply changes under commit confirmed so Junos rolls back automatically if reachability is lost, and delete factory zone-pair policies in the same commit as their global replacements.

Does this skill support SRX chassis cluster setup?

No. If the entry-state assessment detects cluster membership via show chassis cluster status, the skill stops immediately and routes to srx-chassis-cluster-proxmox or srx-mnha. It covers standalone SRXs and the pre-cluster baseline only.

What happens if a configuration change locks me out of the SRX?

Every lockout-risk change is applied with commit confirmed and a rollback timer. If verification fails or the session is lost, the timer expires and Junos automatically rolls back to the pre-change configuration, so out-of-band console access should be confirmed before gated writes.

Can this skill install or manage Juniper licenses?

No. It performs a read-only entitlement readout across three axes — entitled, configured, and active — and reports states like licensed but not configured. All license installation, modification, or removal routes to the srx-license-signature-maintenance skill.

Why is NTP configuration critical during SRX initial setup?

A skewed clock still completes mTLS to log collectors, so transport checks pass while logs never appear in Security Director. The hidden set system processes ntp enable statement does not tab-complete and is easily skipped, so verification uses show ntp associations rather than the statement's presence.