Write or review a network switch configuration change
A vendor-aware switch config for your requirement, plus a pre-change review, rollback steps, and verification commands.
The prompt
Help me write or review a network switch configuration change.
Platform and OS version: [e.g. "Arista EOS 4.x", "Cisco IOS-XE", "Juniper Junos"]
What I need to achieve: [e.g. "add VLAN 120 to the access layer", "set up MLAG between two leaf switches", "add a BGP peer"]
Current setup: [topology, relevant interfaces, VLANs, routing, or paste the running-config section - remove passwords, keys, and SNMP communities first]
Constraints: [change window, redundancy requirements, naming standards, security policy]
Mode: [write a new config / review my proposed config]
Do this:
1. Restate the goal and list any assumptions or missing details that would change the config. Mark guesses with [CONFIRM].
2. Give the configuration in the correct syntax for my platform, in a code block, grouped and commented by purpose.
3. Review it (or my draft) against these checks: spanning-tree and loop risk, VLAN and trunk allowed lists, MTU consistency, LACP/MLAG peer consistency, routing filters and route leaks, management-plane access (ACLs, AAA, SSH only), logging and NTP, and anything that could cut off my own access.
4. A pre-change checklist: backups, commands to capture the before-state, and peer or upstream dependencies.
5. Rollback steps I can run quickly if it goes wrong (use config sessions or commit-confirm if the platform supports them).
6. Verification commands with what a healthy result looks like.
If a command or feature differs between OS versions, say so and tell me what to check in the vendor documentation. Recommend testing in a lab or on a single device first.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- e.g. "Arista EOS 4.x", "Cisco IOS-XE", "Juniper Junos"
- write a new config / review my proposed config
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Write a security finding for a penetration test reportTurns your notes on a vulnerability into a clear, professional finding with risk rating, evidence, impact, and fix steps.
- Vet an open-source library before adding itEvaluates a dependency for maintenance health, security, license fit, and lock-in so you can decide whether to adopt it.
- Make background jobs and webhooks safe to retryDesigns idempotency, retries, and dead-letter handling so jobs, queue consumers, and webhooks never double-charge or lose work.
- Write an incident postmortem and runbookA blameless postmortem with timeline, root cause, actions, and a runbook update.