<?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 FWSM Software Upgrade (With Failover) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-software-upgrade-with-failover/m-p/231160#M1061757</link>
    <description>&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two Firewall Service Modules in two separate 6500 chassis, which run stateful failover. Does any know how to upgrade the two FWSM ios without service interruption?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 07:33:26 GMT</pubDate>
    <dc:creator>gchui</dc:creator>
    <dc:date>2020-02-21T07:33:26Z</dc:date>
    <item>
      <title>FWSM Software Upgrade (With Failover)</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-software-upgrade-with-failover/m-p/231160#M1061757</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two Firewall Service Modules in two separate 6500 chassis, which run stateful failover. Does any know how to upgrade the two FWSM ios without service interruption?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:33:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-software-upgrade-with-failover/m-p/231160#M1061757</guid>
      <dc:creator>gchui</dc:creator>
      <dc:date>2020-02-21T07:33:26Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Software Upgrade (With Failover)</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-software-upgrade-with-failover/m-p/231161#M1061785</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess IOS upgrade will be always disruptive. However, the downtime can be minimized. You could load the new software on both blades. Now, during a maintainence window, reload the primary. The standby will take over. About one minute later or so, reload the standby. This should see both the blades upgraded with minimal disruption. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Aug 2004 21:30:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-software-upgrade-with-failover/m-p/231161#M1061785</guid>
      <dc:creator>jsivulka</dc:creator>
      <dc:date>2004-08-13T21:30:59Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM Software Upgrade (With Failover)</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-software-upgrade-with-failover/m-p/231162#M1061830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm planning to upgrade FWSM blades in the same scenario...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is what happens when the Primary blade comes up with new image version number (version mismatch)? I assume this will create problem as 1.1.3 doesn't support different version numbers in failover scenario. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Should I remove the physical connections between two blades (failover VLAN) during the upgrade process?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also is it possible to upgrade from 1.1.3 to 2.2.1 or 2.3.x directly?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2005 20:44:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-software-upgrade-with-failover/m-p/231162#M1061830</guid>
      <dc:creator>sreddy</dc:creator>
      <dc:date>2005-03-17T20:44:49Z</dc:date>
    </item>
  </channel>
</rss>

