Part I

Start here: AI for network engineers

Already automating?

Already scripting with Netmiko? You can skip this page. Labs Step 6 picks up where you are, and the agents page covers how I’d let a model near real gear.

Read this first

AI is good at the parts of our job that are mostly reading and writing. It'll summarize a pile of logs, turn a config into a handoff doc, draft the post-incident write-up, and remind you of syntax you only touch twice a year.

It's bad at being right on its own. It makes up commands, mixes up OS versions, and invents model numbers, and it says all of it with the same confidence. So I treat everything it gives me as a draft. I check it before anyone else sees it, and I wouldn't let anything it wrote near a production device until I'd put my name on it.

The never-paste rule

What I'd never paste into a free AI tool is anything from your network:

  • Your configs, hostnames, or IP addressing
  • Usernames, passwords, keys, or SNMP strings
  • Customer names, or anything from a ticket with names in it

Free tiers can train on what you type. If your company has an approved tool (plenty of shops are Copilot-only), use that one for real data, and check your policy first.

The one config I'll hand you below is different. It's from my home lab, and it's already on GitHub for anyone to read, lab passwords and all. There's nothing in it to leak, and that's exactly why I picked it.

Got told to use AI?

Here's one safe win you can get in about ten minutes with nothing but a browser.

  1. Open the core-rtr-01 config from my lab. It's public on GitHub, so pasting it doesn't break the rule above.
  2. Copy my documentation prompt into any AI chat tool.
  3. Paste the config under it and run it.
documentation handoff prompt
You are documenting a network device for an engineer handoff. From the
following running configuration, produce:
1) an interface table (name, IP, mask, description, state),
2) a routing summary (protocols, router-id, networks, passive interfaces),
3) a list of configuration risks or oddities worth an engineer's attention.
Config follows:

[PASTE RUNNING-CONFIG HERE]

You'll get an interface table, a routing summary, and a list of things worth a second look.

Then spend five minutes checking it against the config. That's the part I'd show your boss: the doc it drafted, the check you did, and anything it got wrong.

When you want to try it on your own gear, do it in your company's approved tool.

Start from a job