<?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: WSA high availability options in Web Security</title>
    <link>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914657#M191</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thank's a lot for the answer , so meaning we will not have clusterconfig on the WSA like ESA right ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 Jan 2008 17:55:50 GMT</pubDate>
    <dc:creator>denisp_ironport</dc:creator>
    <dc:date>2008-01-11T17:55:50Z</dc:date>
    <item>
      <title>WSA high availability options</title>
      <link>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914655#M189</link>
      <description>&lt;P&gt;Dear, all . &lt;BR /&gt;&lt;BR /&gt;just would like to have some help , other then WCCP and L4-L7 content switching for high availability with WSA what other methods can be used ?&lt;BR /&gt;secondly do you have any idea that WSA supporting configuration clustering as it does in the ESA appliances currently , if it doesn't support do you have some plans to support it in the future release ?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jan 2008 22:04:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914655#M189</guid>
      <dc:creator>denisp_ironport</dc:creator>
      <dc:date>2008-01-09T22:04:20Z</dc:date>
    </item>
    <item>
      <title>Re: WSA high availability options</title>
      <link>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914656#M190</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Denis,&lt;BR /&gt;&lt;BR /&gt;The only other method for deployement is explicitly configuring your clients to use the WSA as an HTTP proxy. This can be cumbersome depending on the type of clients and browsers being used. &lt;BR /&gt;&lt;BR /&gt;In an AD environment, Internet Explorer proxy settings can be forced when the user logs into the domain. This doesn't affect non IE browsers or non windows clients. &lt;BR /&gt;&lt;BR /&gt;It also depends on a single proxy, unless you have some form of load balancing setup.&lt;BR /&gt;&lt;BR /&gt;There is no clustering available for the WSA. Currently, the M-Series appliance has beta code to interact with the WSAs and push config files across appliance groups. &lt;BR /&gt;&lt;BR /&gt;Please contact your sales rep if you are interested in participating in this beta.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jan 2008 00:30:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914656#M190</guid>
      <dc:creator>jowolfer</dc:creator>
      <dc:date>2008-01-11T00:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: WSA high availability options</title>
      <link>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914657#M191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thank's a lot for the answer , so meaning we will not have clusterconfig on the WSA like ESA right ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jan 2008 17:55:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914657#M191</guid>
      <dc:creator>denisp_ironport</dc:creator>
      <dc:date>2008-01-11T17:55:50Z</dc:date>
    </item>
    <item>
      <title>Re: WSA high availability options</title>
      <link>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914658#M192</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is correct. The intention is to have the WSAs configured within the M-Series appliance to do all of your configuration changes and pushes from that device (centralized management).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jan 2008 23:29:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914658#M192</guid>
      <dc:creator>jowolfer</dc:creator>
      <dc:date>2008-01-11T23:29:25Z</dc:date>
    </item>
    <item>
      <title>Re: WSA high availability options</title>
      <link>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914659#M193</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hm , clusterconfig on ESA is very superior and advanced , having it on the &lt;BR /&gt;WSA making sense since all the configs are in XML , having M pushing configs adding lot of complexity&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jan 2008 23:44:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914659#M193</guid>
      <dc:creator>denisp_ironport</dc:creator>
      <dc:date>2008-01-11T23:44:49Z</dc:date>
    </item>
    <item>
      <title>Configuration Management roadmap</title>
      <link>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914660#M194</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are rolling out CM for the WSA in 2 phases. The first phase (AsysncOS for Mgmt 6.2) is a relatively simple implementation. You need to FTP the XML config file(s) off of the box or boxes you want to use as templates onto your laptop and  then FTP them onto the M-Series device. Then you can use the M-Series to push the files to various groups of WSAs you create. For customers with only 2-3 WSAs, it may not be a huge time saver. This version is due out by the first week of Feb.&lt;BR /&gt;&lt;BR /&gt;In the 2H of 2008, we plan to release a version on CM for the WSA closer to the CM that is available for the ESA. This allows complete control over which features are synced to which groups of WSAs and is a very powerful approach to CM.&lt;BR /&gt;&lt;BR /&gt;cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Jan 2008 00:58:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/wsa-high-availability-options/m-p/914660#M194</guid>
      <dc:creator>chhaag</dc:creator>
      <dc:date>2008-01-12T00:58:49Z</dc:date>
    </item>
  </channel>
</rss>

