<?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>Firmware-Upgrade on PacketMind</title>
    <link>https://packetmind.dev/tags/firmware-upgrade/</link>
    <description>Recent content in Firmware-Upgrade 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/firmware-upgrade/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Operator-Owned YAML Workflows for Firmware Upgrades</title>
      <link>https://packetmind.dev/posts/netpicker-file-transfer-yaml-workflows-firmware-upgrades/</link>
      <pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://packetmind.dev/posts/netpicker-file-transfer-yaml-workflows-firmware-upgrades/</guid>
      <description>&lt;h2 id=&#34;the-file-transfer-bottleneck-in-firmware-upgrades&#34;&gt;The File Transfer Bottleneck in Firmware Upgrades&lt;/h2&gt;
&lt;p&gt;Pushing a 2GB firmware image to 120 Arista switches shouldn&amp;rsquo;t feel like playing Russian roulette with your SSH session. Yet, most network engineers still babysit brittle Python scripts, praying a minor EOS or Junos update doesn&amp;rsquo;t break the regex parsing their pre-transfer disk space checks.&lt;/p&gt;
&lt;p&gt;Consider a typical maintenance window: you need to deploy an emergency patch across a multi-vendor spine-leaf fabric. Your automation script breaks at device 47 because an EOS update altered the &lt;code&gt;dir&lt;/code&gt; command&amp;rsquo;s output format, causing your pre-transfer free-space check to fail. Each vendor demands bespoke expect scripts, and every OS update becomes a maintenance window risk.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
