<?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: commitVipRedundancy with ASR  in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/commitvipredundancy-with-asr/m-p/510787#M9646</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes. This is the accepted behaviour. When this command is executed on the active CSS in the ASR mode, the active CSS will not accept new connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Feb 2006 22:12:30 GMT</pubDate>
    <dc:creator>wong34539</dc:creator>
    <dc:date>2006-02-27T22:12:30Z</dc:date>
    <item>
      <title>commitVipRedundancy with ASR</title>
      <link>https://community.cisco.com/t5/application-networking/commitvipredundancy-with-asr/m-p/510786#M9645</link>
      <description>&lt;P&gt;Is it expected behavior when commitVipRedundancy is being run on active CSS in ASR mode, the active CSS doesn't accept new connections and backup can't be reached via telnet/ssh?  When command is completed CSS resumes accepting and switching new connections.&lt;/P&gt;&lt;P&gt;(tested with 7.50)&lt;/P&gt;</description>
      <pubDate>Wed, 22 Feb 2006 06:40:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/commitvipredundancy-with-asr/m-p/510786#M9645</guid>
      <dc:creator>savyer</dc:creator>
      <dc:date>2006-02-22T06:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: commitVipRedundancy with ASR</title>
      <link>https://community.cisco.com/t5/application-networking/commitvipredundancy-with-asr/m-p/510787#M9646</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes. This is the accepted behaviour. When this command is executed on the active CSS in the ASR mode, the active CSS will not accept new connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2006 22:12:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/commitvipredundancy-with-asr/m-p/510787#M9646</guid>
      <dc:creator>wong34539</dc:creator>
      <dc:date>2006-02-27T22:12:30Z</dc:date>
    </item>
    <item>
      <title>Re: commitVipRedundancy with ASR</title>
      <link>https://community.cisco.com/t5/application-networking/commitvipredundancy-with-asr/m-p/510788#M9647</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's the reason of that behavior?  Is there any way to allow new connecitons during a config sync?&lt;/P&gt;&lt;P&gt;Also, is Standby being inaccessible remotely acceptible   behavior as well?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Feb 2006 04:04:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/commitvipredundancy-with-asr/m-p/510788#M9647</guid>
      <dc:creator>savyer</dc:creator>
      <dc:date>2006-02-28T04:04:54Z</dc:date>
    </item>
  </channel>
</rss>

