<?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 I am actually getting a in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644057#M1027465</link>
    <description>&lt;P&gt;I am actually getting a similar message when eth1 is not present, though it is less frequent.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Apr 2015 18:42:47 GMT</pubDate>
    <dc:creator>Mark^</dc:creator>
    <dc:date>2015-04-23T18:42:47Z</dc:date>
    <item>
      <title>Unable to communicate with dynamic analysis cloud</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644056#M1027464</link>
      <description>&lt;P&gt;I have two interfaces on Defense Center.&amp;nbsp; One of them (eth1) is on a management vlan that does not have Internet access.&amp;nbsp; When AMP tries to connect to cloud it frequently tries via eth1 and I get the above message and a health monitoring alert.&amp;nbsp; I know this is the cause because it shows the IP address of eth1 in the message and, as I said, eth1 does not have Internet access.&lt;/P&gt;&lt;P&gt;How do I force updates to only use eth0?&amp;nbsp; My default route is on eth0 network.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 12:40:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644056#M1027464</guid>
      <dc:creator>Mark^</dc:creator>
      <dc:date>2019-03-12T12:40:05Z</dc:date>
    </item>
    <item>
      <title>I am actually getting a</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644057#M1027465</link>
      <description>&lt;P&gt;I am actually getting a similar message when eth1 is not present, though it is less frequent.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2015 18:42:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644057#M1027465</guid>
      <dc:creator>Mark^</dc:creator>
      <dc:date>2015-04-23T18:42:47Z</dc:date>
    </item>
    <item>
      <title>did you ever find an answer?</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644058#M1027466</link>
      <description>&lt;P&gt;did you ever find an answer?&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2016 17:02:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644058#M1027466</guid>
      <dc:creator>jlimmer14</dc:creator>
      <dc:date>2016-04-05T17:02:41Z</dc:date>
    </item>
    <item>
      <title>Negative, but I think I</title>
      <link>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644059#M1027467</link>
      <description>&lt;P&gt;Negative, but I think I misunderstood the problem in the first place.&amp;nbsp; I am now on 6.0 and get the message once in a while, but it never causes a health monitoring alert and doesn't seem to cause any other issue.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2016 17:35:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/unable-to-communicate-with-dynamic-analysis-cloud/m-p/2644059#M1027467</guid>
      <dc:creator>Mark^</dc:creator>
      <dc:date>2016-04-05T17:35:10Z</dc:date>
    </item>
  </channel>
</rss>

