<?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 Stealthwatch Architecture Question in Security Analytics</title>
    <link>https://community.cisco.com/t5/security-analytics/stealthwatch-architecture-question/m-p/3820407#M154</link>
    <description>&lt;P&gt;I am looking at architecture options for Stealthwatch 7.0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are looking a deploying virtual SMC and flow collectors.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If we have multiple data centers - is it supported to have a "primary" SMC and Flow Collector one data center - and a "secondary" SMC and Flow Collector at a backup data center?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If so - do I need a UDP director to send flow records to both flow collectors?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance for the help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bob&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I&lt;/P&gt;</description>
    <pubDate>Fri, 15 Mar 2019 20:12:13 GMT</pubDate>
    <dc:creator>reheindel</dc:creator>
    <dc:date>2019-03-15T20:12:13Z</dc:date>
    <item>
      <title>Stealthwatch Architecture Question</title>
      <link>https://community.cisco.com/t5/security-analytics/stealthwatch-architecture-question/m-p/3820407#M154</link>
      <description>&lt;P&gt;I am looking at architecture options for Stealthwatch 7.0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are looking a deploying virtual SMC and flow collectors.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If we have multiple data centers - is it supported to have a "primary" SMC and Flow Collector one data center - and a "secondary" SMC and Flow Collector at a backup data center?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If so - do I need a UDP director to send flow records to both flow collectors?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance for the help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bob&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 20:12:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/security-analytics/stealthwatch-architecture-question/m-p/3820407#M154</guid>
      <dc:creator>reheindel</dc:creator>
      <dc:date>2019-03-15T20:12:13Z</dc:date>
    </item>
    <item>
      <title>Re: Stealthwatch Architecture Question</title>
      <link>https://community.cisco.com/t5/security-analytics/stealthwatch-architecture-question/m-p/3823917#M155</link>
      <description>&lt;P&gt;Bob,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes.&amp;nbsp; I suggest that any telemetry you send to the primary Flow Collector you use UDP Director to duplicate that at the secondary Flow Collector.&amp;nbsp; UDP Director is the best way to do that rather than exporting flow to each Flow collector from each exporter.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would assume the back up data center has it's own Internet connection.&amp;nbsp; Send those network translation (NAT) logs to the secondary; not the primary.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you enable Cognitive Intelligence make sure that you only send from the primary flow collector.&amp;nbsp; You can add the second flow collector to your account but only enable that when the primary in down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You should be able to login to the Stealthwatch SMC at the backup facility and see just the traffic from the at site.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The SMC at the backup site will not be secondary.&amp;nbsp; Primary - secondary is used when you have 2 SMCs working with the same Flow Collector.&amp;nbsp; The primary will be admin for that deployment (where admin can make config changes) and the secondary will be useful for any other (than admin) user.&amp;nbsp; It allows the Stealthwatch UI to scale up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2019 18:18:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/security-analytics/stealthwatch-architecture-question/m-p/3823917#M155</guid>
      <dc:creator>brford</dc:creator>
      <dc:date>2019-03-21T18:18:23Z</dc:date>
    </item>
    <item>
      <title>Re: Stealthwatch Architecture Question</title>
      <link>https://community.cisco.com/t5/security-analytics/stealthwatch-architecture-question/m-p/3828493#M156</link>
      <description>&lt;P&gt;Excellent, thanks very much for the detailed response Brian!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 20:30:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/security-analytics/stealthwatch-architecture-question/m-p/3828493#M156</guid>
      <dc:creator>reheindel</dc:creator>
      <dc:date>2019-03-28T20:30:52Z</dc:date>
    </item>
  </channel>
</rss>

