cisco-ios-patterns
affaan-m/ecc
Cisco IOS/IOS-XE review patterns for config, ACLs, wildcard masks, and safe change verification.
What is cisco-ios-patterns?
Patterns and checklists for reviewing Cisco IOS and IOS-XE configurations, troubleshooting with read-only commands, and validating changes safely. Use this when building change windows, checking ACL placement and wildcard masks, or collecting evidence from routers and switches without making problems worse.
- Provides mode reference and command syntax for IOS configuration hierarchy (global, interface, routing process, line modes)
- Lists read-only show commands for safe troubleshooting without modifying device state
- Explains wildcard mask conversion and common mistakes in ACL and routing statements
- Guides ACL placement review with direction, management access, and rollback validation
- Offers before/after verification commands for routing and ACL changes
- Documents interface hygiene patterns including descriptions, switchport modes, and native VLAN documentation
How to install cisco-ios-patterns
npx skills add null --skill cisco-ios-patterns- Access to a Cisco IOS or IOS-XE device (physical or lab)
- Understanding of basic networking concepts (subnets, ACLs, routing)
- Out-of-band or console access for safe testing
How to use cisco-ios-patterns
- 1.Capture current state using the provided read-only show commands before making any changes
- 2.Review the exact candidate configuration and compare against the current running-config
- 3.Confirm management access cannot be locked out by the planned change
- 4.Apply the smallest change in a maintenance window, following the mode reference
- 5.Re-read state with the provided verification commands and compare to baseline
- 6.Save the change to startup-config only after validation passes
Use cases
- Reviewing IOS or IOS-XE configuration before a planned maintenance change
- Choosing safe read-only show commands to troubleshoot without risking lockout
- Validating ACL wildcard masks and interface direction before deployment
- Building a change-window checklist with pre-change and post-change verification steps
- Collecting specific config sections for review without exposing secrets or topology in tickets
- Network engineers reviewing Cisco device configurations
- Operations teams building change-window checklists
- Incident responders troubleshooting routers and switches safely
- Anyone validating ACL placement and wildcard mask correctness before deployment
cisco-ios-patterns FAQ
running-config is the active configuration in memory; startup-config is what persists after a reload. Do not save a change just because a command was accepted—validate behavior first, then use 'copy running-config startup-config' only after approval.
Subtract each octet of the subnet mask from 255. For example, subnet mask 255.255.255.0 becomes wildcard mask 0.0.0.255. A common mistake is using a subnet mask where IOS expects a wildcard mask, which can match far more traffic than intended.
Verify the traffic direction (in or out), confirm management traffic is explicitly permitted, ensure required routing/DNS/NTP/monitoring traffic is permitted, check that hit counters can be read from a safe test source, and confirm a rollback command and out-of-band access are available.
Use read-only show commands to collect evidence first. Never troubleshoot by disabling ACLs, route policies, or authentication. Read counters, logs, and route state before testing reachability.
Do not apply a generated config without a device-specific diff, save configuration before post-change checks pass, use a subnet mask where IOS expects a wildcard mask, apply an ACL to the wrong interface direction, or paste full configs into public tools without sanitizing secrets and topology.
Full instructions (SKILL.md)
Source of truth, from affaan-m/ecc.
name: cisco-ios-patterns description: Cisco IOS and IOS-XE review patterns for show commands, config hierarchy, wildcard masks, ACL placement, interface hygiene, and safe change-window verification. metadata: origin: community
Cisco IOS Patterns
Use this skill when reviewing Cisco IOS or IOS-XE snippets, building a change-window checklist, or explaining how to collect evidence from a router or switch without making the incident worse.
When to Use
- Reviewing IOS or IOS-XE configuration before a planned change.
- Choosing read-only
showcommands for troubleshooting. - Checking ACL wildcard masks and interface direction.
- Explaining global, interface, routing process, and line configuration modes.
- Verifying that a change landed in running config and was saved intentionally.
Operating Rules
Treat IOS examples as patterns, not paste-ready production changes. Confirm the platform, interface names, current config, rollback path, and out-of-band access before making changes on a real device.
Prefer this workflow:
- Capture current state with read-only commands.
- Review the exact candidate config.
- Confirm management access cannot be locked out.
- Apply the smallest change in a maintenance window.
- Re-read state, compare to the baseline, then save only after validation.
Mode Reference
Router> enable
Router# show running-config
Router# configure terminal
Router(config)# interface GigabitEthernet0/1
Router(config-if)# description UPLINK-TO-CORE
Router(config-if)# no shutdown
Router(config-if)# exit
Router(config)# end
Router# show running-config interface GigabitEthernet0/1
running-config is active memory. startup-config is what survives reload.
Do not save a change just because a command was accepted; validate behavior
first, then use copy running-config startup-config if the change is approved.
Read-Only Collection
show version
show inventory
show processes cpu sorted
show memory statistics
show logging
show running-config | section line vty
show running-config | section interface
show running-config | section router bgp
show ip interface brief
show interfaces
show interfaces status
show vlan brief
show mac address-table
show spanning-tree
show ip route
show ip protocols
show ip access-lists
show route-map
show ip prefix-list
Collect the specific section you need instead of dumping full config into a ticket when the config may contain secrets, customer names, or private topology.
Wildcard Masks
IOS ACL and many routing statements use wildcard masks, not subnet masks.
Subnet mask Wildcard mask
255.255.255.255 0.0.0.0
255.255.255.252 0.0.0.3
255.255.255.0 0.0.0.255
255.255.0.0 0.0.255.255
Review wildcard masks before deployment. A subnet mask accidentally used as a wildcard can match far more traffic than intended.
ip access-list extended WEB-IN
10 permit tcp 192.0.2.0 0.0.0.255 any eq 443
999 deny ip any any log
Every ACL has an implicit deny at the end. Add an explicit logged deny when the operational goal includes observing misses, and confirm logging volume is safe.
ACL Placement Review
Before applying an ACL to an interface, answer these questions:
- Which traffic direction is being filtered,
inorout? - Is management traffic sourced from a known jump host or management subnet?
- Is there an explicit permit for required routing, DNS, NTP, monitoring, or application traffic?
- Are hit counters available from a safe test source?
- Is there a rollback command and an active console or out-of-band path?
Do not test reachability by removing firewall or ACL protections. Read counters, logs, and route state first.
Interface Hygiene
interface GigabitEthernet0/1
description UPLINK-TO-CORE
switchport mode trunk
switchport trunk allowed vlan 10,20,30
switchport trunk native vlan 999
no shutdown
Use clear descriptions, explicit switchport mode, and documented native VLANs. On routed interfaces, confirm the mask, peer addressing, and routing process before assuming link state means forwarding is correct.
Change-Window Verification
Use before/after checks that match the actual change.
show running-config | section interface GigabitEthernet0/1
show interfaces GigabitEthernet0/1
show logging | include GigabitEthernet0/1|changed state|line protocol
show ip route <prefix>
show ip access-lists <name>
For routing changes, also capture neighbor state and route tables before and after the change. For ACL changes, compare hit counters from a planned test source rather than relying on a generic ping.
Anti-Patterns
- Applying a generated config without a device-specific diff.
- Saving configuration before post-change checks pass.
- Using a subnet mask where IOS expects a wildcard mask.
- Applying an ACL to the wrong interface direction.
- Troubleshooting by disabling ACLs, route policies, or authentication.
- Pasting full configs into public tools without sanitizing secrets and topology.
See Also
- Agent:
network-config-reviewer - Agent:
network-troubleshooter - Skill:
network-config-validation - Skill:
network-interface-health
Related skills
More from affaan-m/ecc and the wider catalog.
ck
Persistent per-project memory for Claude Code with auto-loaded context and git-aware session tracking.
claude-api
Agent skill from affaan-m/ecc.
claude-devfleet
Orchestrate parallel Claude Code agents on coding tasks with dependency chains and isolated worktrees.
click-path-audit
Trace button handlers through state changes to find bugs where functions cancel each other out or leave UI inconsistent.
clickhouse-io
ClickHouse patterns for high-performance analytics, query optimization, and data engineering.
code-tour
Create CodeTour `.tour` files with real file anchors for guided codebase walkthroughs.