<?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>Juniper-Junos on PacketMind</title><link>https://packetmind.dev/tags/juniper-junos/</link><description>Recent content in Juniper-Junos 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/juniper-junos/index.xml" rel="self" type="application/rss+xml"/><item><title>Netpicker File Transfer: Operator-Owned YAML Network Automation Workflows</title><link>https://packetmind.dev/posts/netpicker-file-transfer-operator-owned-yaml-network-automation-workflows/</link><pubDate>Thu, 11 Jun 2026 00:00:00 +0000</pubDate><guid>https://packetmind.dev/posts/netpicker-file-transfer-operator-owned-yaml-network-automation-workflows/</guid><description>&lt;h2 id="the-file-transfer-bottleneck-in-modern-networks"&gt;The File Transfer Bottleneck in Modern Networks&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. The next morning, your Cisco ASR edge routers need a network configuration backup, but the TFTP timeout handling differs from your Juniper QFX datacenter switches. Each vendor demands bespoke expect scripts, and every OS update becomes a maintenance window risk.&lt;/p&gt;</description></item></channel></rss>