Using ios_command Instead of ios_config Flapped Every Trunk Port — Ansible Network Automation
A playbook used `ios_command` instead of `ios_config` to push 'vlan 100', and every trunk port flapped — a 15-minute outage for an entire east-coast data center. This is network automation with Ansible: the cisco.ios/network modules, ios_command vs ios_config, idempotent config push, check mode, and not treating config changes like show commands.
⏳ Timestamps:
0:00 - Cold open: 15-minute outage for entire east coast data center
0:14 - Intro
0:21 - What Is Ansible Network Automation?
0:44 - The network_cli Connection
1:09 - ios_command vs ios_config
1:36 - Wrong ios_command Usage
1:46 - Network-Agnostic Modules
2:07 - cli_command Example
2:13 - NAPALM Integration
2:35 - NAPALM Config Example
2:41 - Junos Management
2:57 - Junos Commit Confirm
3:06 - Arista EOS Management
3:23 - Cisco NXOS Management
3:39 - Idempotency Challenges
4:01 - Non-Idempotent Example
4:08 - 15-minute outage for entire east coast data center
4:32 - The Fix
4:51 - ⚠ Gotcha: Using ios_command for config changes
5:00 - ⚠ Gotcha: Using junos_command to send config commands
5:09 - ⚠ Gotcha: Configuring VLAN interface without enabling feature
5:18 - ⚠ Gotcha: Forgetting ansible_become for cli_config
5:29 - ⚠ Gotcha: Not setting ansible_connection to network_cli
5:39 - Version Compatibility: network_cli and FQCN
6:32 - Production Caveat: Backup Before Changes
6:53 - Debugging Guide
7:06 - Interview Questions
7:34 - FAQ
8:05 - Key Takeaways
8:25 - Next up
8:39 - Wrap-up
👉 Full article + code: https://thecodeforge.io/devops/ansibl...
⏭ Next up: Introduction to Google Cloud Platform
#ansible #devops #automation