<?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 WCS and High Availability in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754021#M23475</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My database takes about 20 minutes ... its SLLLLLOOOOOOOOOOOWWWWWWW&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Sep 2011 15:40:14 GMT</pubDate>
    <dc:creator>George Stefanick</dc:creator>
    <dc:date>2011-09-29T15:40:14Z</dc:date>
    <item>
      <title>WCS and High Availability</title>
      <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754014#M23468</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what are the requirements to run active and standby WCS-server in different locations?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found the following note from Release 7.0.172.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"A reliable high-speed wired network must exist between the primary WCS and its backup WCS"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Matthias&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 03:49:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754014#M23468</guid>
      <dc:creator>schuetzm</dc:creator>
      <dc:date>2021-07-04T03:49:53Z</dc:date>
    </item>
    <item>
      <title>WCS and High Availability</title>
      <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754015#M23469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You will want to make sure you have a reliable link between both boxes. I have a set up today with one box on the east coast and one on the west and it works just fine with a T1. I dont think I ever seen a specific spec sheet on the exact specs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do know there is a heart beat between the boxes. When that is lost, the seconadry kicks in.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Sep 2011 00:36:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754015#M23469</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-09-28T00:36:19Z</dc:date>
    </item>
    <item>
      <title>WCS and High Availability</title>
      <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754016#M23470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a note for you guys... when testing the failover, if you can't physically shut your server down and try stopping the WCS service it won't failover automatically by default.&lt;/P&gt;&lt;P&gt;﻿&lt;/P&gt;&lt;P&gt;﻿&lt;A href="http://www.cisco.com/en/US/docs/wireless/wcs/7.0/configuration/guide/7_0main.html#wp1072642"&gt;http://www.cisco.com/en/US/docs/wireless/wcs/7.0/configuration/guide/7_0main.html#wp1072642&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've seen WCS occasionally lock up and need to be manually stop/started to come back to life.&amp;nbsp; If this happens, the auto failover isn't actually automatic unless you run the command "nmsadmin.bat -switchover stop".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Surely auto failover on service down makes more sense than failover on server down?&amp;nbsp; &lt;/P&gt;&lt;P&gt;Anyone aware of any reasoning behind this not being default the behaviour?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2011 08:35:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754016#M23470</guid>
      <dc:creator>Rob Simkins</dc:creator>
      <dc:date>2011-09-29T08:35:20Z</dc:date>
    </item>
    <item>
      <title>WCS and High Availability</title>
      <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754017#M23471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;LOL.... I did know that Iblogged about it. I LOL becuase i wonder the same thing! &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.my80211.com/cisco-wcs/"&gt;http://www.my80211.com/cisco-wcs/&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2011 12:26:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754017#M23471</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-09-29T12:26:43Z</dc:date>
    </item>
    <item>
      <title>WCS and High Availability</title>
      <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754018#M23472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nice, I'm now following you on twitter and feedly - consider me a tech stalker...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also.... If you are upgrading a pair of primary WCS servers you'll need to merge all controllers onto a single SNMP community that covers both WCS servers.&amp;nbsp; This is because the secondary WCS inherits the community string from the primary.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What happens when several primary servers are on different subnets?&amp;nbsp; You need to open up the netmask on the SNMP community config. This could end up being 0.0.0.0 if you have a weird setup.&amp;nbsp; If you dont do this the controllers wont speak to the secondary WCS and will appear down...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Security concern?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2011 13:33:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754018#M23472</guid>
      <dc:creator>Rob Simkins</dc:creator>
      <dc:date>2011-09-29T13:33:29Z</dc:date>
    </item>
    <item>
      <title>WCS and High Availability</title>
      <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754019#M23473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I always lead with SNMP v3 so we limited the risk a bit rather then using 1 and 2 ...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2011 14:42:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754019#M23473</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-09-29T14:42:57Z</dc:date>
    </item>
    <item>
      <title>WCS and High Availability</title>
      <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754020#M23474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good point! I've just migrated, pretty simple task &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matthias - The traffic you need to worry about is going to be the sync and failover/failback.&amp;nbsp; This could be the full WCS database backup file which is usually 100mb+.&amp;nbsp; I'm not sure what the sync period is though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2011 15:35:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754020#M23474</guid>
      <dc:creator>Rob Simkins</dc:creator>
      <dc:date>2011-09-29T15:35:19Z</dc:date>
    </item>
    <item>
      <title>WCS and High Availability</title>
      <link>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754021#M23475</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My database takes about 20 minutes ... its SLLLLLOOOOOOOOOOOWWWWWWW&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2011 15:40:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-and-high-availability/m-p/1754021#M23475</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2011-09-29T15:40:14Z</dc:date>
    </item>
  </channel>
</rss>

