<?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>Catalyst 8000 on Barash Helvadzhaoglu</title><link>https://barashhelvadzhaoglu.com/en/tags/catalyst-8000/</link><description>Recent content in Catalyst 8000 on Barash Helvadzhaoglu</description><generator>Hugo -- 0.170.1</generator><language>en</language><lastBuildDate>Thu, 22 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://barashhelvadzhaoglu.com/en/tags/catalyst-8000/index.xml" rel="self" type="application/rss+xml"/><item><title>Cisco IOS and IOS-XE Upgrade Guide: Catalyst Switches and ISR Routers</title><link>https://barashhelvadzhaoglu.com/en/posts/cisco-ios-xe-upgrade-guide/</link><pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate><guid>https://barashhelvadzhaoglu.com/en/posts/cisco-ios-xe-upgrade-guide/</guid><description>Step-by-step Cisco IOS and IOS-XE software upgrade for Catalyst switches (2960, 3560, 3850, 9200, 9300, 9500) and routers (ISR 4000, ISR 1100, Catalyst 8000) — flash checks, ROMMON, install mode, bundle mode, MD5 and rollback.</description><content:encoded><![CDATA[<p>Most Cisco upgrades fail before the first command is typed: the wrong image for the platform, too little space in flash, a ROMMON that is too old for the target release, or a boot variable that points nowhere. This guide puts the checks first and the commands second.</p>
<p>It covers both families you meet in practice:</p>
<table>
	<thead>
			<tr>
					<th>Family</th>
					<th>Typical models</th>
					<th>Software</th>
					<th>File system</th>
					<th>Upgrade method</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Classic Catalyst switches</td>
					<td>2960, 2960-X, 3560, 3750</td>
					<td>IOS</td>
					<td><code>flash:</code></td>
					<td><code>archive download-sw</code> or <code>.bin</code> + <code>boot system</code></td>
			</tr>
			<tr>
					<td>IOS-XE Catalyst switches</td>
					<td>3650, 3850, 9200, 9300, 9400, 9500</td>
					<td>IOS-XE</td>
					<td><code>flash:</code> (on some models <code>bootflash:</code>)</td>
					<td>Install mode (<code>packages.conf</code>)</td>
			</tr>
			<tr>
					<td>IOS-XE routers</td>
					<td>ISR 4000, ISR 1100, Catalyst 8200/8300, Catalyst 8000V</td>
					<td>IOS-XE</td>
					<td><code>bootflash:</code></td>
					<td>Install mode or bundle mode</td>
			</tr>
			<tr>
					<td>Classic IOS routers</td>
					<td>ISR G2, C900</td>
					<td>IOS</td>
					<td><code>flash:</code></td>
					<td><code>.bin</code> + <code>boot system</code></td>
			</tr>
	</tbody>
</table>
<p>The commands are the ones I use in the field on Catalyst switches and ISR routers. IP addresses and paths in the examples are placeholders.</p>
<h2 id="1-check-the-platform-before-anything-else">1. Check the Platform Before Anything Else</h2>
<h3 id="file-system-flash-or-bootflash">File System: flash: or bootflash:?</h3>
<p>Do not assume. Ask the device:</p>
<pre tabindex="0"><code>show file systems
dir
</code></pre><p>Classic Catalyst switches and Catalyst 9200/9300 use <code>flash:</code>. ISR and Catalyst 8000 routers use <code>bootflash:</code>. On many IOS-XE platforms one name is an alias for the other. Use whatever the device shows. Every command in this guide works with either name.</p>
<h3 id="model-version-and-boot-mode">Model, Version and Boot Mode</h3>
<pre tabindex="0"><code>show version
show inventory
show boot            ! switches
show bootvar         ! routers
show install summary ! IOS-XE only
</code></pre><p>Write down:</p>
<ul>
<li><strong>Exact model and platform family.</strong> An image for an ISR 4300 does not boot on an ISR 4400. The platform family is in the file name, for example <code>isr4300-universalk9</code>, <code>c1100-universalk9</code>, <code>cat9k_iosxe</code>.</li>
<li><strong>Current version.</strong></li>
<li><strong>Boot mode on IOS-XE.</strong> If the boot variable points to <code>packages.conf</code>, the device runs in <strong>install mode</strong>. If it points to a <code>.bin</code> file, it runs in <strong>bundle mode</strong>.</li>
</ul>
<h3 id="free-space">Free Space</h3>
<p><code>dir</code> shows the free bytes at the bottom. An IOS-XE image is large, and install mode needs extra space to extract the packages. If space is tight, clean up first:</p>
<pre tabindex="0"><code>install remove inactive   ! IOS-XE install mode: removes unused packages
delete flash:&lt;old-image&gt;.bin
</code></pre><h2 id="2-read-the-release-notes-upgrade-path-and-rommon">2. Read the Release Notes: Upgrade Path and ROMMON</h2>
<p>Two things in the release notes decide whether the upgrade works:</p>
<ul>
<li><strong>Upgrade path.</strong> Some jumps are not supported directly. Cisco documents, for example, that Catalyst 9500 switches in bundle mode should go from 16.x to 17.x through an intermediate release, while install mode supports the direct jump.</li>
<li><strong>Minimum ROMMON version.</strong> Every IOS-XE release needs a minimum ROMMON (boot loader) version. If the device has an older ROMMON, the new image may not boot and the device stops at the <code>rommon</code> prompt.</li>
</ul>
<p>Check the current ROMMON version:</p>
<pre tabindex="0"><code>show rom-monitor r0          ! ISR 4000 and similar routers
show version | include ROM   ! most platforms
</code></pre><h3 id="does-rommon-need-a-separate-upgrade">Does ROMMON Need a Separate Upgrade?</h3>
<ul>
<li><strong>Catalyst 9000:</strong> Usually not by hand. When a new release contains a newer ROMMON, the switch upgrades its primary ROMMON automatically at the first boot. The golden (backup) ROMMON is upgraded manually with the <code>upgrade rom-monitor capsule golden</code> command. The exact arguments differ by model, so check the upgrade guide for your platform.</li>
<li><strong>ISR 4000 and similar routers:</strong> Check it every time. A well-known case is ISR 4000 routers that need ROMMON 16.12(2r) before they boot 17.x releases.</li>
</ul>
<h3 id="upgrading-rommon-on-an-isr-4000">Upgrading ROMMON on an ISR 4000</h3>
<p>ROMMON is upgraded from the running IOS-XE, not from the ROMMON prompt. Copy the ROMMON package, verify it, then:</p>
<pre tabindex="0"><code>copy ftp://192.0.2.10/images/isr4200_4300_rommon_1612_2r_SPA.pkg bootflash:
verify /md5 bootflash:isr4200_4300_rommon_1612_2r_SPA.pkg
upgrade rom-monitor filename bootflash:isr4200_4300_rommon_1612_2r_SPA.pkg R0
reload
show rom-monitor r0
</code></pre><p>Do the ROMMON upgrade <strong>before</strong> the software upgrade. If you get it wrong and the device no longer boots, see <a href="/en/posts/cisco-rommon-recovery/">Cisco ROMMON Recovery</a>.</p>
<h3 id="secure-boot-and-signed-images">Secure Boot and Signed Images</h3>
<p>IOS-XE images are signed. The <code>.SPA</code> in the file name stands for a signed production image. The device verifies the signature at boot. An image for the wrong platform or a corrupted file fails this check and does not boot. Only use images from Cisco Software Download and always verify the checksum.</p>
<h2 id="3-copy-the-image-and-verify-it">3. Copy the Image and Verify It</h2>
<p>FTP is faster and more reliable than TFTP for large IOS-XE images:</p>
<pre tabindex="0"><code>copy ftp://192.0.2.10/images/isr4300-universalk9.17.12.08.SPA.bin bootflash:
copy ftp://192.0.2.10/images/c1100-universalk9.17.12.08.SPA.bin bootflash:
copy tftp://192.0.2.10/cat9k_iosxe.&lt;version&gt;.SPA.bin flash:
</code></pre><p>Setting up the server, credentials, the double slash in FTP paths and the management VRF are covered in <a href="/en/posts/tftp-ftp-server-cisco-upgrades/">TFTP, FTP and SCP Servers for Cisco Upgrades</a>.</p>
<p>Verify the MD5 checksum against the value on the Cisco download page:</p>
<pre tabindex="0"><code>verify /md5 bootflash:c1100-universalk9.17.12.08.SPA.bin
</code></pre><p>If the values differ, delete the file and copy it again. Never install an image that failed verification.</p>
<h2 id="4-upgrade-in-install-mode-ios-xe">4. Upgrade in Install Mode (IOS-XE)</h2>
<p>Install mode is the recommended mode for Catalyst 9000 switches and current ISR and Catalyst 8000 routers. One command adds, activates and commits the new software:</p>
<pre tabindex="0"><code>install add file bootflash:isr4300-universalk9.17.12.08.SPA.bin activate commit
</code></pre><p>The device asks whether it may reload. Answer <code>y</code>. After the reload:</p>
<pre tabindex="0"><code>show version
show install summary
install remove inactive
</code></pre><p><code>show install summary</code> should show the new version as <code>Committed</code>. <code>install remove inactive</code> removes the old packages and frees space.</p>
<p>On Catalyst 9000 switches the command is the same, with the switch file system:</p>
<pre tabindex="0"><code>install add file flash:cat9k_iosxe.&lt;version&gt;.SPA.bin activate commit
</code></pre><h3 id="several-hops-in-a-row">Several Hops in a Row</h3>
<p>If the release notes require an intermediate release, repeat the sequence per hop: copy, verify, <code>install add ... activate commit</code>, check, <code>install remove inactive</code>. For example 17.9 first, then 17.12. Clean up between the hops so there is room for the next image.</p>
<h3 id="from-bundle-mode-to-install-mode">From Bundle Mode to Install Mode</h3>
<p>A device in bundle mode boots a <code>.bin</code> file directly. To switch to install mode:</p>
<ol>
<li>Run <code>install add file &lt;image&gt;.bin activate commit</code> as above. This extracts the packages and creates <code>packages.conf</code>.</li>
<li>Make sure the boot variable points to <code>packages.conf</code>:</li>
</ol>
<pre tabindex="0"><code>configure terminal
no boot system
boot system flash:packages.conf
end
write memory
show boot
</code></pre><p>On routers, use <code>bootflash:packages.conf</code>.</p>
<h2 id="5-bundle-mode-and-classic-ios">5. Bundle Mode and Classic IOS</h2>
<h3 id="ios-xe-in-bundle-mode-isr-g2-c900">IOS-XE in Bundle Mode, ISR G2, C900</h3>
<pre tabindex="0"><code>configure terminal
no boot system
boot system bootflash:&lt;image&gt;.bin
end
write memory
show bootvar
reload
</code></pre><p>On classic IOS routers like the C900 series, the file system is <code>flash:</code> and the image name has the old format, for example <code>c900-universalk9-mz.SPA.&lt;version&gt;.bin</code>.</p>
<h3 id="classic-catalyst-switches-2960-3560-3750">Classic Catalyst Switches (2960, 3560, 3750)</h3>
<p>These switches offer <code>archive download-sw</code>. It transfers a <code>.tar</code> file, extracts it, sets the boot variable and can reload:</p>
<pre tabindex="0"><code>archive download-sw /overwrite /reload tftp://192.0.2.10/c3560-ipservicesk9-tar.&lt;version&gt;.tar
</code></pre><ul>
<li><code>/overwrite</code> replaces the current image when flash has room for only one.</li>
<li><code>/leave-old-sw</code> keeps the old image when there is room for both. Rollback is then just a boot variable change.</li>
</ul>
<p>Alternatively, copy the <code>.bin</code> file, verify it and set <code>boot system flash:&lt;image&gt;.bin</code> as above.</p>
<h2 id="6-after-the-upgrade">6. After the Upgrade</h2>
<pre tabindex="0"><code>show version
show install summary          ! IOS-XE install mode
show interfaces status        ! switches
show ip interface brief
show power inline             ! PoE switches
show logging
</code></pre><p>On stacks and redundant systems, check every member: <code>show switch</code> on Catalyst stacks, <code>show redundancy</code> on dual-supervisor systems.</p>
<h2 id="7-rollback">7. Rollback</h2>
<ul>
<li><strong>Install mode:</strong> <code>show install rollback</code> lists the rollback points.</li>
<li><strong>Bundle mode and classic IOS:</strong> point <code>boot system</code> back to the old image, if it is still in flash, and reload.</li>
<li><strong>Device stops at ROMMON or the <code>switch:</code> prompt:</strong> see <a href="/en/posts/cisco-rommon-recovery/">Cisco ROMMON Recovery</a>.</li>
</ul>
<h2 id="common-mistakes">Common Mistakes</h2>
<ul>
<li><strong>Image for the wrong platform family.</strong> It fails signature or platform checks and does not boot.</li>
<li><strong>ROMMON not checked.</strong> The new image needs a newer ROMMON, and the device stops at the <code>rommon</code> prompt.</li>
<li><strong>No space for install mode.</strong> The extraction fails halfway. Run <code>install remove inactive</code> first.</li>
<li><strong>Boot variable still points to the old <code>.bin</code> after moving to install mode.</strong> The device boots the old version in bundle mode.</li>
<li><strong>No console access during the reload.</strong> A console server makes this possible remotely: <a href="/en/posts/next-gen-console-server-architecture/">Next-Gen Console Server Architecture</a>.</li>
</ul>
<h2 id="related-articles">Related Articles</h2>
<ul>
<li><a href="/en/posts/cisco-rommon-recovery/">Cisco ROMMON Recovery: Boot from Flash, TFTP or USB</a></li>
<li><a href="/en/posts/tftp-ftp-server-cisco-upgrades/">TFTP, FTP and SCP Servers for Cisco Upgrades</a></li>
<li><a href="/en/posts/cisco-switch-password-recovery/">Cisco Switch and Router Password Recovery</a></li>
<li><a href="/en/posts/cisco-nexus-nxos-upgrade-guide/">Cisco Nexus NX-OS Software Upgrade Guide</a></li>
</ul>
<p>Sources: <a href="https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9500-series-switches/222279-upgrading-catalyst-9500-switches.html">Cisco: Upgrading Catalyst 9500 Switches</a> · <a href="https://www.cisco.com/c/de_de/support/docs/switches/catalyst-9300-series-switches/222280-upgrading-catalyst-9300-switches.html">Cisco: Upgrading Catalyst 9300 Switches</a></p>
]]></content:encoded></item></channel></rss>