netmiko-ssh-automation
affaan-m/everything-claude-code
Safe Python Netmiko patterns for read-only SSH collection, batch automation, TextFSM parsing, and guarded config changes.
What is netmiko-ssh-automation?
Use this skill when writing Python automation that connects to network devices via Netmiko SSH. It provides safe patterns for read-only command collection, bounded batch operations, structured parsing, and guarded configuration changes with proper timeout and error handling.
- Read-only connection patterns with credential management and timeout configuration
- Bounded batch SSH collection across multiple devices with per-device error reporting
- TextFSM/TTP/Genie structured parsing of command output with fallback to raw results
- Guarded configuration change patterns requiring explicit operator flags and dry-run modes
- Exception handling for authentication, timeout, and read failures
- Before/after capture and verification patterns for config changes
How to install netmiko-ssh-automation
npx skills add https://github.com/affaan-m/everything-claude-code --skill netmiko-ssh-automation- Python 3.6+
- netmiko library installed
- Network device credentials (via environment variables or secrets manager)
- TextFSM/TTP/Genie libraries optional for parsing
How to use netmiko-ssh-automation
- 1.Set up device dictionary with connection parameters and timeouts from environment variables or getpass
- 2.Use ConnectHandler context manager with read-only send_command() for initial collection
- 3.For batch operations, use ThreadPoolExecutor with max_workers set conservatively (8 or lower)
- 4.Enable structured parsing with use_textfsm=True and raise_parsing_error=False when templates exist
- 5.For config changes, require APPLY_NETWORK_CHANGES=1 environment variable and implement dry-run mode
- 6.Capture before/after state and verify changes before calling save_config() as a separate step
Use cases
- Collecting show command output across routers, switches, or firewalls for auditing
- Building inventory scripts to gather interface, routing, or configuration evidence
- Adding timeouts and exception handling to existing network SSH scripts
- Parsing structured data from device commands when templates exist
- Reviewing and validating automation before production deployment
- Network engineers writing Python automation
- DevOps engineers managing network device fleets
- Security teams auditing network device configurations
- Infrastructure teams building change management workflows
netmiko-ssh-automation FAQ
No. Use environment variables, getpass(), or a secrets manager. Never hardcode passwords, enable secrets, or private keys in source code.
Keep it low (8 or lower) unless your device estate and AAA systems are known to handle higher connection volume. This prevents overloading older devices.
Use raise_parsing_error=False to fall back to raw output when no parser template matches. Store both raw and parsed results so operators can inspect mismatches.
Never call save_config() immediately after send_config_set(). Make it a separate approval step after verifying the changes are correct and have been reviewed.
Set conn_timeout (10s), auth_timeout (20s), banner_timeout (15s), and read_timeout_override (30s) at minimum, with command-level read_timeout adjusted per device type.
Full instructions (SKILL.md)
Source of truth, from affaan-m/everything-claude-code.
name: netmiko-ssh-automation description: Safe Python Netmiko patterns for read-only collection, bounded batch SSH, TextFSM parsing, guarded config changes, timeouts, and network automation error handling. metadata: origin: community
Netmiko SSH Automation
Use this skill when writing or reviewing Python automation that connects to network devices with Netmiko. Keep the default path read-only; config changes need a separate change window, peer review, and rollback plan.
When to Use
- Collecting
showcommand output across routers, switches, or firewalls. - Building a small audit script for interface, routing, or config evidence.
- Adding timeouts and exception handling to network SSH scripts.
- Parsing command output with TextFSM when a template exists.
- Reviewing automation before it touches production devices.
Safety Defaults
- Start with read-only
send_command()collection. - Keep inventory small and explicit; do not sweep whole address ranges.
- Use environment variables, a vault, or
getpass; never hardcode credentials. - Set connection and read timeouts.
- Limit concurrency so older devices are not overloaded.
- Require an explicit operator flag before
send_config_set(). - Do not call
save_config()until the change has been verified and approved.
Read-Only Connection Pattern
import os
from getpass import getpass
from netmiko import ConnectHandler
from netmiko.exceptions import (
NetmikoAuthenticationException,
NetmikoTimeoutException,
ReadTimeout,
)
device = {
"device_type": "cisco_ios",
"host": "192.0.2.10",
"username": os.environ.get("NETMIKO_USERNAME") or input("Username: "),
"password": os.environ.get("NETMIKO_PASSWORD") or getpass("Password: "),
"secret": os.environ.get("NETMIKO_ENABLE_SECRET"),
"conn_timeout": 10,
"auth_timeout": 20,
"banner_timeout": 15,
"read_timeout_override": 30,
}
try:
with ConnectHandler(**device) as conn:
if device.get("secret") and not conn.check_enable_mode():
conn.enable()
output = conn.send_command("show ip interface brief", read_timeout=30)
print(output)
except NetmikoAuthenticationException:
print("Authentication failed")
except NetmikoTimeoutException:
print("SSH connection timed out")
except ReadTimeout:
print("Command read timed out")
Use placeholder addresses from documentation ranges in examples. Keep real inventory in an ignored local file or a secrets-managed system.
Batch Collection
from concurrent.futures import ThreadPoolExecutor, as_completed
from typing import Any
def collect_show(device: dict[str, Any], command: str) -> dict[str, Any]:
host = device["host"]
try:
with ConnectHandler(**device) as conn:
output = conn.send_command(command, read_timeout=45)
return {"host": host, "ok": True, "output": output}
except (NetmikoAuthenticationException, NetmikoTimeoutException, ReadTimeout) as exc:
return {"host": host, "ok": False, "error": type(exc).__name__}
results = []
with ThreadPoolExecutor(max_workers=8) as pool:
futures = [pool.submit(collect_show, device, "show version") for device in devices]
for future in as_completed(futures):
results.append(future.result())
Keep max_workers low unless the device estate and AAA systems are known to
handle higher connection volume.
Structured Parsing
Netmiko can ask TextFSM, TTP, or Genie to parse supported command output. Treat parser output as an optimization, not the only evidence path.
with ConnectHandler(**device) as conn:
parsed = conn.send_command(
"show ip interface brief",
use_textfsm=True,
raise_parsing_error=False,
read_timeout=30,
)
if isinstance(parsed, str):
print("No parser template matched; store raw output for review")
else:
for row in parsed:
print(row)
If parsing drives a blocking decision, keep the raw command output alongside the parsed result so an operator can inspect mismatches.
Guarded Config Pattern
import os
commands = [
"interface GigabitEthernet0/1",
"description CHANGE-1234 UPLINK-TO-CORE",
]
apply_changes = os.environ.get("APPLY_NETWORK_CHANGES") == "1"
if not apply_changes:
print("Dry run only. Candidate commands:")
print("\n".join(commands))
else:
with ConnectHandler(**device) as conn:
conn.enable()
before = conn.send_command("show running-config interface GigabitEthernet0/1")
output = conn.send_config_set(commands)
after = conn.send_command("show running-config interface GigabitEthernet0/1")
print(before)
print(output)
print(after)
print("Verify behavior before saving startup config.")
Saving the config is a separate approval step. In production, include a rollback snippet and capture before/after evidence in the change record.
Review Checklist
- Does the script identify an explicit inventory source?
- Are credentials absent from source, logs, and exception messages?
- Are
conn_timeout,auth_timeout, and commandread_timeoutset? - Are failures reported per device without stopping the whole batch?
- Does the script avoid broad scans and unbounded concurrency?
- Are config changes behind a dry-run or explicit operator flag?
- Is
save_config()separate from the initial push and tied to verification?
Anti-Patterns
- Hardcoding passwords, enable secrets, or private keys in source.
- Sending config commands as the default code path.
- Running automation against a CIDR range instead of a reviewed inventory.
- Logging full running configs to shared systems without sanitization.
- Treating parser success as proof that the device state is correct.
See Also
- Skill:
cisco-ios-patterns - Skill:
network-config-validation - Skill:
network-interface-health
Related skills
More from affaan-m/everything-claude-code and the wider catalog.

network-bgp-diagnostics
Read-only BGP troubleshooting for neighbor state, route exchange, and policy inspection.

network-config-validation
Pre-deployment validation for Cisco IOS/IOS-XE configs: dangerous commands, IP conflicts, credential exposure, and security hygiene.

network-interface-health
Diagnose physical link, duplex, and interface counter issues on network devices.

nextjs-turbopack
Next.js 16+ incremental bundler with Rust-powered Turbopack for faster dev startup and HMR.

nodejs-keccak256
Use Ethereum's Keccak-256, not Node's NIST SHA3, to prevent silent hashing bugs in selectors, signatures, and storage slots.

nutrient-document-processing
Convert, extract, OCR, redact, sign, and fill documents via Nutrient DWS API.