<?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 AIP-SSM update issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/aip-ssm-update-issue/m-p/1738081#M494822</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two ASA5540 firewalls working in active/standby failover. Both have AIP-SSM-40 modules. I have configured the update source for the signatures from cisco .com with my smartnet. The problem is the SSM only on the active firewall is updating regularly.I want to check if there is configuration problem and i changed the standby firewall to be active then it started to update and the other SSM module stopped updating. Is updating on SSM only works for the active device?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Mulu&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 21:42:21 GMT</pubDate>
    <dc:creator>mulugojjam abebe</dc:creator>
    <dc:date>2019-03-11T21:42:21Z</dc:date>
    <item>
      <title>AIP-SSM update issue</title>
      <link>https://community.cisco.com/t5/network-security/aip-ssm-update-issue/m-p/1738081#M494822</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two ASA5540 firewalls working in active/standby failover. Both have AIP-SSM-40 modules. I have configured the update source for the signatures from cisco .com with my smartnet. The problem is the SSM only on the active firewall is updating regularly.I want to check if there is configuration problem and i changed the standby firewall to be active then it started to update and the other SSM module stopped updating. Is updating on SSM only works for the active device?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Mulu&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:42:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/aip-ssm-update-issue/m-p/1738081#M494822</guid>
      <dc:creator>mulugojjam abebe</dc:creator>
      <dc:date>2019-03-11T21:42:21Z</dc:date>
    </item>
    <item>
      <title>AIP-SSM update issue</title>
      <link>https://community.cisco.com/t5/network-security/aip-ssm-update-issue/m-p/1738082#M494826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, I dont think there is anything wrong with the device, but is more like how it works. The Standby ASA Module should have the primary ASA IP as gateway in order to go and do the auto update. Remember that the standby ASA cannot pass traffic across it. So if you put the default gateway on the standby SSM module as the default gateway, it is not going to work. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, the other point (and I think this is the issue) would be routing, if you connect to the standby ssm module via CLI, can you ping the something on the internet? You need to make sure that the AIP have a path to reach the cloud. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Oct 2011 07:23:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/aip-ssm-update-issue/m-p/1738082#M494826</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-10-28T07:23:16Z</dc:date>
    </item>
  </channel>
</rss>

