<?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'm totally agree with you. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021943#M908224</link>
    <description>&lt;P&gt;I'm totally agree with you. Too high delta, unfortunately. Anyway, appreciate your opinion. Have a nice day.&lt;/P&gt;</description>
    <pubDate>Fri, 14 Apr 2017 08:17:51 GMT</pubDate>
    <dc:creator>sharlino</dc:creator>
    <dc:date>2017-04-14T08:17:51Z</dc:date>
    <item>
      <title>ASA 5508-X, FirePower, incorrect syslog timestamp</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021937#M908206</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;
&lt;P&gt;I have an ASA 5508-X with FirePower services managed via ASDM.&lt;BR /&gt;Versions are:&lt;BR /&gt;ASA: 9.6(2)13 &lt;BR /&gt;ASDM: 7.7(1)&lt;BR /&gt;FP: 6.2.0 (Build 362)&lt;BR /&gt;&lt;BR /&gt;I have configured access control policy with logging to external syslog server as well as internal log.&lt;BR /&gt;I have configured FirePower module to poll NTP servers. The &lt;STRONG&gt;show time&lt;/STRONG&gt; command displays correct time, ASDM displays correct time in every place where timestamp can be checked, linux box (Cisco Fire Linux OS) displays correct time.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Problem: the FirePower module is sending logs with incorrect timestamp to external syslog server. &lt;BR /&gt;Have I missed something important or it's possible yet another bug from Cisco ?&lt;/P&gt;
&lt;P&gt;Thank you in advance!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:03:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021937#M908206</guid>
      <dc:creator>sharlino</dc:creator>
      <dc:date>2020-02-21T14:03:06Z</dc:date>
    </item>
    <item>
      <title>Are you sure it isn't logging</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021938#M908211</link>
      <description>&lt;P&gt;Are you sure it isn't logging it in GMT+0?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 08:19:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021938#M908211</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2017-04-12T08:19:05Z</dc:date>
    </item>
    <item>
      <title>Are you sure it isn't logging</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021939#M908216</link>
      <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;Are you sure it isn't logging it in GMT+0?&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Excuse me, how can I verify that?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;By the way, for example, syslog shows "Apr 12 &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;08:34:51&lt;/STRONG&gt;&lt;/SPAN&gt;", but the FP CLI is much different:&lt;/P&gt;
&lt;PRE class="prettyprint"&gt; &amp;gt; show time&lt;BR /&gt;UTC -&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Wed Apr 12 &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;09:11:11&lt;/STRONG&gt;&lt;/SPAN&gt; UTC 2017&lt;BR /&gt;Localtime - Wed Apr 12 &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;12:11:14&lt;/STRONG&gt;&lt;/SPAN&gt; EEST 2017&lt;/PRE&gt;
&lt;P&gt;Because of this, the problem is not in the timezone, in my opinion.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 09:33:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021939#M908216</guid>
      <dc:creator>sharlino</dc:creator>
      <dc:date>2017-04-12T09:33:21Z</dc:date>
    </item>
    <item>
      <title>You can verify by going into</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021940#M908218</link>
      <description>&lt;P&gt;You can verify by going into expert mode on the module doing a quick tcpdump and looking at the content of a syslog message.&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;&amp;gt;expert&lt;BR /&gt;admin@Sourcefire3D:~$&amp;nbsp;sudo tcpdump -i eth0 -s 0 host &amp;lt;your syslog server&amp;gt;&lt;/PRE&gt;
&lt;P&gt;They're sent unencrypted via udp/514 (edit) so it's pretty easy to look at even in the cli.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Apr 2017 08:02:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021940#M908218</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-04-14T08:02:03Z</dc:date>
    </item>
    <item>
      <title>Hello Marvin! Thank you for</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021941#M908220</link>
      <description>&lt;P&gt;Hello Marvin! Thank you for your response.&lt;/P&gt;
&lt;P&gt;I did sniff the traffic, but 514/udp, not 161/udp (SNMP). I did capture on the syslog server side too and the timestamp is incorrect. &lt;/P&gt;</description>
      <pubDate>Fri, 14 Apr 2017 08:02:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021941#M908220</guid>
      <dc:creator>sharlino</dc:creator>
      <dc:date>2017-04-14T08:02:04Z</dc:date>
    </item>
    <item>
      <title>Whoops - edited my reply for</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021942#M908222</link>
      <description>&lt;P&gt;Whoops - edited my reply for the correct port. Thanks.&lt;/P&gt;
&lt;P&gt;I believe the log does lag a little bit but I'd expect maybe several seconds of delta - not over 30 minutes like you are seeing.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;That sounds like a bug. I'd recommend opening a TAC case.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Apr 2017 08:12:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021942#M908222</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-04-14T08:12:39Z</dc:date>
    </item>
    <item>
      <title>I'm totally agree with you.</title>
      <link>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021943#M908224</link>
      <description>&lt;P&gt;I'm totally agree with you. Too high delta, unfortunately. Anyway, appreciate your opinion. Have a nice day.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Apr 2017 08:17:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5508-x-firepower-incorrect-syslog-timestamp/m-p/3021943#M908224</guid>
      <dc:creator>sharlino</dc:creator>
      <dc:date>2017-04-14T08:17:51Z</dc:date>
    </item>
  </channel>
</rss>

