Cisco Nexus (NX-OS)
Device type
Section titled “Device type”Netmiko device_type: cisco_nxos
Set vendor: nexus in devices.csv.
Command files
Section titled “Command files”Nexus devices share the config/cisco/ command files and validation patterns —
no separate folder needed. Commands that only exist on one platform are safe to
mix in the same file: a command invalid on the connected platform returns
% Invalid input and is handled gracefully by read-only tasks.
The built-in health check (--healthcheck) already includes NX-OS commands:
show system resourcesshow vpc briefHealth check coverage
Section titled “Health check coverage”| Metric | Source |
|---|---|
| CPU % | show system resources — computed as 100 - idle |
| Memory % | show system resources — used / total |
| Virtual chassis | show vpc brief — peer status + keep-alive status |
A vPC peer that is not ok or a keep-alive that is not alive reports the
device as DEGRADED → CRIT in the health report.
Differences from IOS
Section titled “Differences from IOS”- No
enablesecret needed in most deployments — NX-OS users land at privileged exec. - Config save is
copy running-config startup-config(notwrite memory). - Stack detection (
show switch) does not apply; Nexus pairing is vPC, covered above.