<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cisco-Ios on PacketMind</title>
    <link>https://packetmind.dev/tags/cisco-ios/</link>
    <description>Recent content in Cisco-Ios on PacketMind</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 11 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://packetmind.dev/tags/cisco-ios/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Operator-Owned YAML for Configuration Backups</title>
      <link>https://packetmind.dev/posts/netpicker-file-transfer-yaml-workflows-configuration-backups/</link>
      <pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://packetmind.dev/posts/netpicker-file-transfer-yaml-workflows-configuration-backups/</guid>
      <description>&lt;h2 id=&#34;the-configuration-backup-problem&#34;&gt;The Configuration Backup Problem&lt;/h2&gt;
&lt;p&gt;Every network team has a story about a misconfiguration recovery that went sideways because the backup was stale, incomplete, or stored in some engineer&amp;rsquo;s home directory. Pulling configs from a multi-vendor environment shouldn&amp;rsquo;t require bespoke expect scripts for each platform — scripts where the TFTP timeout handling differs between your Cisco ASR edge routers and your Juniper QFX datacenter switches.&lt;/p&gt;
&lt;p&gt;When your backup logic lives inside imperative Python scripts or complex Ansible playbooks, every OS update becomes a risk. One changed CLI prompt can silently break your entire backup pipeline.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
