NETCONF Bulk Config Manager

YANG-schema validated NETCONF configuration management: candidate datastore transactions, edit-config with rollback-on-error, schema validation before push, batch multi-device transactions with atomic commit.

cisco-iosxr

juniper

arista

Open in Generator Open in Platform

You're viewing a preview

The full script, parameters, and execution console are available with a free account.

Already have access? Sign in →

Capabilities

NETCONF
YANG
ncclient
Candidate
Rollback
YANG schema validation

Required inputs

Parameters the script accepts. Defaults shown; some are vendor- or context-gated.

Parameter	Type	Default	Notes
Dry Run dry_run	bool	true	—
Rollback On Failure rollback_on_fail	bool	true	—

Hint 1 — Name your vendors and OS versions

Mention the exact platforms you run (cisco-iosxr, juniper, arista) so the generated analysis logic uses the right CLI/NETCONF syntax.

Hint 2 — State your real thresholds

Provide concrete values for Dry Run, Rollback On Failure instead of the defaults — they shape what counts as a fault.

Hint 3 — Prioritize the checks you need

This tool can nETCONF and yANG. Ask for the subset relevant to your incident to keep output focused.

Hint 4 — Describe your inventory format

Tell the assistant whether your device list is CSV, YAML, or JSON and which columns it has, so parsing matches your data.

Sample inventory schema

Authoritative shape of the device/policy data this script consumes.

No bundled inventory sample. The script accepts standard device lists (CSV/YAML) with hostname, mgmt IP, vendor, and credentials.

Expected output

Reference terminal output the script should produce — used as a stylistic and structural target.

terminal

[INFO] Targeting 24 devices with payload candidate.xml
[OK]   Validated against YANG model openconfig-interfaces
[INFO] Dry-run diffs computed for all 24 devices
[CRIT] R5: candidate-config validation FAILED — rolling back
[OK]   23/24 commits successful, 1 rolled back