<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Access Point Multiple Partitions in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/access-point-multiple-partitions/m-p/5522261#M308518</link>
    <description>&lt;P&gt;We are trying to see if Meraki AP has two partitions for firmware images. Two partitions help in surviving a failed upgrade.&lt;BR /&gt;&lt;BR /&gt;Do Meraki APs have two partitions, one to store the current image as the backup &amp;amp; the other to store the new one being upgraded to?&lt;/P&gt;</description>
    <pubDate>Mon, 21 Jul 2025 12:35:56 GMT</pubDate>
    <dc:creator>flyingframes</dc:creator>
    <dc:date>2025-07-21T12:35:56Z</dc:date>
    <item>
      <title>Access Point Multiple Partitions</title>
      <link>https://community.cisco.com/t5/wireless/access-point-multiple-partitions/m-p/5522261#M308518</link>
      <description>&lt;P&gt;We are trying to see if Meraki AP has two partitions for firmware images. Two partitions help in surviving a failed upgrade.&lt;BR /&gt;&lt;BR /&gt;Do Meraki APs have two partitions, one to store the current image as the backup &amp;amp; the other to store the new one being upgraded to?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jul 2025 12:35:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/access-point-multiple-partitions/m-p/5522261#M308518</guid>
      <dc:creator>flyingframes</dc:creator>
      <dc:date>2025-07-21T12:35:56Z</dc:date>
    </item>
    <item>
      <title>Re: Access Point Multiple Partitions</title>
      <link>https://community.cisco.com/t5/wireless/access-point-multiple-partitions/m-p/5522262#M308519</link>
      <description>&lt;P&gt;They do, see here under how do upgrades work&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Cisco_Meraki_Firmware_FAQ" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Cisco_Meraki_Firmware_FAQ&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jul 2025 12:55:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/access-point-multiple-partitions/m-p/5522262#M308519</guid>
      <dc:creator>mloraditch</dc:creator>
      <dc:date>2025-07-21T12:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: Access Point Multiple Partitions</title>
      <link>https://community.cisco.com/t5/wireless/access-point-multiple-partitions/m-p/5522263#M308520</link>
      <description>&lt;P&gt;Hey;&lt;BR /&gt;In the event of issues arising from new firmware you can Rollback directly from the Dashboard.&lt;BR /&gt;&lt;BR /&gt;They do &lt;STRIKE&gt;not&lt;/STRIKE&gt; give details as far as how it is performed on the device itself if thats what you are wondering.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Managing_Firmware_Upgrades#Rolling_Back_a_Recent_Firmware_Upgrade" target="_blank" rel="noopener nofollow noreferrer"&gt;https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Managing_Firmware_Upgrades#Rolling_Back_a_Recent_Firmware_Upgrade&lt;/A&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;H3 id="toc-hId-1454774464"&gt;Rolling Back a Recent Firmware Upgrade&lt;/H3&gt;&lt;P&gt;Firmware upgrades can be rolled back to their previous version up to 14 days after an upgrade takes place. Follow the steps below to roll back a firmware upgrade.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Navigate to &lt;STRONG&gt;Organization &amp;gt; Monitor &amp;gt; Firmware upgrades&lt;/STRONG&gt;.&lt;/LI&gt;&lt;LI&gt;From the &lt;STRONG&gt;Overview&lt;/STRONG&gt; tab, view the &lt;STRONG&gt;Most recent upgrades&lt;/STRONG&gt; section and find the applicable upgrade entry.&lt;/LI&gt;&lt;LI&gt;Click on the applicable upgrade entry where it lists the number of networks and devices that were upgraded.&lt;/LI&gt;&lt;LI&gt;Click the &lt;STRONG&gt;Rollback&lt;/STRONG&gt; button.&lt;/LI&gt;&lt;LI&gt;Select a reason for the rollback and enter a brief description.&lt;/LI&gt;&lt;LI&gt;Select &lt;STRONG&gt;Perform the upgrade now&lt;/STRONG&gt; or &lt;STRONG&gt;Schedule the upgrade for&lt;/STRONG&gt;, specifying a date and time for the rollback. &lt;/LI&gt;&lt;LI&gt;Click &lt;STRONG&gt;Submit&lt;/STRONG&gt; to schedule the rollback. &lt;/LI&gt;&lt;/OL&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Best Deployment strategy is to move a handful (or single) of APs into their own Network Dashboard to roll out firmware upgrades as it cannot be done per device but per network.&lt;BR /&gt;Example from docs:&lt;BR /&gt;&lt;A href="https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practices_for_Meraki_Firmware" target="_blank" rel="noopener nofollow noreferrer"&gt;https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practices_for_Meraki_Firmware&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;In the case of failure then a Support Ticket should be raised anyways.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jul 2025 13:02:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/access-point-multiple-partitions/m-p/5522263#M308520</guid>
      <dc:creator>nicdc01</dc:creator>
      <dc:date>2025-07-21T13:02:53Z</dc:date>
    </item>
  </channel>
</rss>

