<?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 Re: write standby problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749854#M970542</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My PIX has 6 interfaces, 5 for traffic and 1 for failover. I gues, I cannot use a dedicated interface for managemente only. Is there any other solution? What if I try doing the "write stand" by console? Would I have the same problem? Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 29 Aug 2007 06:31:48 GMT</pubDate>
    <dc:creator>edimonted</dc:creator>
    <dc:date>2007-08-29T06:31:48Z</dc:date>
    <item>
      <title>write standby problem</title>
      <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749848#M970536</link>
      <description>&lt;P&gt;I have a Pix 515E active/failover IOS v7.2 The failover process works perfect. I test powering down one unit, and then the other en works perfect. But, as soon as I do "write stanby" in the active unit, the passive unit goes down (the insde interface). I remember that one time the ASDM aske something about a "peer" while trying to configure the failover. What is that? why goes down? Thanks in advanced.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:02:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749848#M970536</guid>
      <dc:creator>edimonted</dc:creator>
      <dc:date>2019-03-11T11:02:58Z</dc:date>
    </item>
    <item>
      <title>Re: write standby problem</title>
      <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749849#M970537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;is your inside interface also the failover interface?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2007 10:36:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749849#M970537</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-08-28T10:36:01Z</dc:date>
    </item>
    <item>
      <title>Re: write standby problem</title>
      <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749850#M970538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, I have a dedicated interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2007 10:37:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749850#M970538</guid>
      <dc:creator>edimonted</dc:creator>
      <dc:date>2007-08-28T10:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: write standby problem</title>
      <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749851#M970539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are you doing? Access firewall by inside interface and run that write standby command???&lt;/P&gt;&lt;P&gt; If you are doing that stop that and configure management IP address and access by that and run the command and see the result !!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dharmesh Purohit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2007 13:49:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749851#M970539</guid>
      <dc:creator>purohit_810</dc:creator>
      <dc:date>2007-08-28T13:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: write standby problem</title>
      <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749852#M970540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Second.. See where PIX Connected on Switch Interface IS IT PORTFAST SWITCH INTERFACE??????&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dharmesh Purohit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2007 13:52:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749852#M970540</guid>
      <dc:creator>purohit_810</dc:creator>
      <dc:date>2007-08-28T13:52:24Z</dc:date>
    </item>
    <item>
      <title>Re: write standby problem</title>
      <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749853#M970541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I encountered the same problem with ASA version 7.2. Upgrading to the latest interim release fixed the problem but then caused a worse problem, so waited until Cisco released a more stable version. It appears version 7.2 has a few bugs referring to failover/standby. You could always try upgrading to version 7.3.&lt;/P&gt;&lt;P&gt;Nevertheless, there is no need to issue the "write standby" command because configs are sync'd whenever the "write mem" command is submitted.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Aug 2007 21:59:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749853#M970541</guid>
      <dc:creator>russ</dc:creator>
      <dc:date>2007-08-28T21:59:23Z</dc:date>
    </item>
    <item>
      <title>Re: write standby problem</title>
      <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749854#M970542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My PIX has 6 interfaces, 5 for traffic and 1 for failover. I gues, I cannot use a dedicated interface for managemente only. Is there any other solution? What if I try doing the "write stand" by console? Would I have the same problem? Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Aug 2007 06:31:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749854#M970542</guid>
      <dc:creator>edimonted</dc:creator>
      <dc:date>2007-08-29T06:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: write standby problem</title>
      <link>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749855#M970543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, it is a portfast ethernet. Is a catalyst 2955.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Aug 2007 06:32:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/write-standby-problem/m-p/749855#M970543</guid>
      <dc:creator>edimonted</dc:creator>
      <dc:date>2007-08-29T06:32:55Z</dc:date>
    </item>
  </channel>
</rss>

