<?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 Hi, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953956#M1009093</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You are correct in saying that Access Control Policy needs to be pushed before upgrading a sensor. You will need to look at the logs to understand where exactly the upgrade fails.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Do you see the upgraded getting kicked off ?&lt;/P&gt;
&lt;P&gt;You can tail -f /var/log/action_queue.log on the FMC and the sensor.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;If you see it fail at a certain % then you need to see the logs on the sensor.&lt;/P&gt;
&lt;P&gt;cd /var/log/sf/&amp;lt;upgrade file name&amp;gt;&lt;/P&gt;
&lt;P&gt;less status.log&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Pujita Patni&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 13 Dec 2016 18:11:07 GMT</pubDate>
    <dc:creator>Pujita Patni</dc:creator>
    <dc:date>2016-12-13T18:11:07Z</dc:date>
    <item>
      <title>No Access Control Policy-Stuck Sensor</title>
      <link>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953955#M1009092</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I am attempting to upgrade an virtual device sensor that is stuck on 5.2.07. When I apply the update patch nothing happens. I notice in DC the sensor does not have Access Control Policy assigned and I believe that is the issue. Does anyone have an answers?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks, &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 13:13:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953955#M1009092</guid>
      <dc:creator>sholloway11</dc:creator>
      <dc:date>2019-03-12T13:13:16Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953956#M1009093</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You are correct in saying that Access Control Policy needs to be pushed before upgrading a sensor. You will need to look at the logs to understand where exactly the upgrade fails.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Do you see the upgraded getting kicked off ?&lt;/P&gt;
&lt;P&gt;You can tail -f /var/log/action_queue.log on the FMC and the sensor.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;If you see it fail at a certain % then you need to see the logs on the sensor.&lt;/P&gt;
&lt;P&gt;cd /var/log/sf/&amp;lt;upgrade file name&amp;gt;&lt;/P&gt;
&lt;P&gt;less status.log&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Pujita Patni&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2016 18:11:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953956#M1009093</guid>
      <dc:creator>Pujita Patni</dc:creator>
      <dc:date>2016-12-13T18:11:07Z</dc:date>
    </item>
    <item>
      <title>Thanks, Pujita,</title>
      <link>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953957#M1009094</link>
      <description>&lt;P&gt;Thanks, Pujita,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I checked the status log. It looks like the last patch never applied or launch. Should I remove an temp files?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2016 19:11:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953957#M1009094</guid>
      <dc:creator>sholloway11</dc:creator>
      <dc:date>2016-12-13T19:11:03Z</dc:date>
    </item>
    <item>
      <title>Also, Can I remove the</title>
      <link>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953958#M1009095</link>
      <description>&lt;P&gt;Also, Can I remove the virtual device from FC and add bad to get the AP to apply?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2016 19:12:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953958#M1009095</guid>
      <dc:creator>sholloway11</dc:creator>
      <dc:date>2016-12-13T19:12:07Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953959#M1009096</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I would suggest, you try to push the update again and tail -f /var/log/action_queue.log on both the FMC and the sensor.&lt;/P&gt;
&lt;P&gt;The logs should indicate what the problem is.&lt;/P&gt;
&lt;P&gt;You can share it with me and I can go over it.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Pujita&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2016 22:23:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/no-access-control-policy-stuck-sensor/m-p/2953959#M1009096</guid>
      <dc:creator>Pujita Patni</dc:creator>
      <dc:date>2016-12-14T22:23:06Z</dc:date>
    </item>
  </channel>
</rss>

